Mortoch

MrPLC Member
 View profile  See their activity

  • Content count

    30

  • Joined

  • Last visited

Posts posted by Mortoch

  5. Posted

    13 hours ago, kaare_t said:

    Be aware that I personally find this topic a bit "complex" in terms of language so if anything is unclear, or just far off in my post feel free to let me know and I'll try to explain in a different way.

    I can understand your issue. Regarding the HMI I think that layout designs should be easy to specify when dealing with a machine builder. However, examples of code might be a bit more difficult. The biggest challenge is of course that the developer(s) dealing with the code have their own way of doing their job. I've debugged a lot of applications coded by other developers and all have their own way of thinking. This, of course, makes everything harder to understand and debug. My point here is that the code itself might be hard to specify.

    Basic circuits can be specified of course (code itself). Logical units of code (like physical I/O, fault handling, HMI code, communication code, machine units and so on) should be separated to files/POU's which in should be structured as specified (by you). Again, the HMI layout should be easy to specify.

    You should be specific in regards to the logical "unit layout" of the code. Make sure the producer separates code into units and subunits. I highly, highly recommend to make use of labels (even if you don't use names in your main program) just to be able to use functions and function blocks. That way the code can be further segmented into pieces for easier debugging (and more importantly reuse of equal code). Structure in the code together with good documentation will make debugging and/or modification a lot easier, and honestly I think that is what you can expect to get from a supplier.

    I wholeheartedly agree with the labeling. Make them label, and I even specify that the labeling conforms to our standard. It is a big pain to have wade through a program of ambiguous labels trying to find what each does and then relabeling, especially while troubleshooting.

  6. Posted

    Understand that confidentiality agreements are only as good as the people on both sides of the agreement. The country where I spend the majority of my time working is notorious for stealing and reusing anything they get their hands on.

    Just saying the only true way to insure proprietary security is to keep it in house.

  7. Posted

    I have a generic program for most of the machines I will order. I will specify that they use a certain type of hardware for the flame safety and a familiar processor as my people must be able to use the programs and understand the flame safety equipment for troubleshooting etc.

    I will specify that certain aspects of the machines must work in a certain way that we have found through the years to work the best. This will sometimes lead to some lengthy discussions because they have their canned ways also. Stick to your guns because you are the buyer and they want what you have, (money).

    If their are proprietary aspects of your programs that you wish to keep to yourself merely cut them out of the program you provide to them and reinstall when the machine is in house. This will entail accepting a base operating machine at delivery with the contractual addendum that your company will complete programming.

    Good Luck.

     

  8. Posted

    If you are asking what your maximum counter counts are this is what I found in my manuals:

    Setting ranges for counters:
    • 16bit counters: -32,768 to +32,767
    • 32bit counters: -2,147,483,648 to +2,147,483,647
     

  10. Posted

    Curiosity question and off topic.

    Does EMS stand for emergency medical services like it does in the US?

    If so, are there no HIPA, (privacy),  concerns with using wifi to communicate with these carts?

  14. Posted

    The temp sounds crucial to the process so there will need to be conditions to monitor and reengage the heater to maintain that temp as the solution cools due to the parts being introduced. You will also want to monitor and interrupt the various motors for overload conditions.

    Think of everything that can go wrong and include safeguards to protect the machine.

  16. Posted

    The third party alternatives are an ify proposition. The ones I have used are spotty and sometimes fail completely. I finally purchased a Mitsubishi SC-09 and all the problems vanished.

    Just my humble.

  21. Posted

    Again I  had this problem with the SC09 cables. Transfer set up would see the PLC and confirm successful connection but downloads or uploads would fail. Purchased an FX-USB-AW set up and the problem was solved. Your local mitsu dealer should be able to hook you up or they are out there on ebay if you are careful not to buy a knock off.

  22. Posted · Edited by Mortoch

    If you go to Mitsubishi website and register your software the website will then tell you there is a version update for your software and offer the download. I just went through this about 3 weeks ago. You will have to register a user, etc, but it was easy. Currently using GX Developer-FX VErsion  8.91 for the same reason as you describe.

  23. Posted

    Not sure with Mitsubishi but with the ab's I cut my teeth on there is a setting to include so that the HMI's  mimic each other. In other words if the button is activated on HMI 1 it also shows activated on HMI 2, saves on confusion. Just teaching myself the Mitsubishi components so not real sure of the need for this.