drforsythe

MrPLC Member
 View profile  See their activity

  • Content count

    210

  • Joined

  • Last visited

Posts posted by drforsythe

  2. Posted

    Often times, nobody thinks of the handshaking signals between equipment until the programmer(s) get involved.  I learned quite quickly that the mechanical engineers or salespeople or the process engineers involved with the equipment will have SOME idea of what is needed, but it is the programmer who will know exactly what is needed.  After getting put into tight situations in the past, I learned to insert myself the process early and state my requirements for I/O and handshake info.  I would often have to plead my case when I first started out, but after proving myself , it is much easier now.  So, the response you got to "sort it out on your end" is quite normal.  What you would do to "sort it out" would be to develop a list of the signals you need and then determine how you will get them (order from machine vendor, outsource or just do it yourself).  If you are a programmer only, without resources to design and install the additional hardware, then you would need to find another source to add the necessary I/O.  Ultimately, the programmer may have to compensate for shortcomings in mechanical or process design, so it is best to be assertive when telling others what you need to make the project successful.

    1 person likes this

  3. Posted

    Again, Inntele has the answer.  I have not used the software in over 15 years.  I knew there was something out there, but did not realize (or remember) that it was in the design software.  Thanks for the update, Inntele.

  4. Posted

    Inntele has it.  It doesn't get any simpler than that.  I thought I remember seeing (many years ago) a template for filling out those strips, but I could not find it just now.  I remember using the trial and error approach to creating my first strip.  You will have to create your legend, print it, compare it to the size and available space for each LED, then adjust.  Repeat as necessary.  Good luck.  The Beijer terminals were always easy to use and robust in my past experience.

  5. Posted

    I have done it both ways.  I have placed orders for the components for one machine and then simply copied the requisitions in our purchasing system.  This was helpful to our accounting department, as well.  I have also placed one large order where you simply divide all of the quantities (and costs) by the number of identical machines being built.  For machines that are not identical, it is easier to track if you issue separate orders for the components for each individual machine.

  6. Posted

    We use an Excel spreadsheet.  We have several rows that explain the breakdown of the budget (mechanical, purchased equipment, electrical, outside services, etc).  Then in the columns, I put the dollar amounts budgeted and the actual spend.  I calculate a running total to show where we are in the budget.  Another helpful thing is to add a column with the PO number and an explanation of what was purchased, who purchased it and from what company.  That way, if you have overruns, you can quickly look back at the chart to see where your money went.

  7. Posted

    To help clarify:  If you need the software to communicate and program your device, you will need to contact your local distributor of Mitsubishi automation equipment.  For Washington state, it is:

    BUCHANAN AUTOMATION, INC.

    1920 Bickford Avenue

    Snohomish, Washington 98291

    800-426-8313

    For more info from Mitsubishi, you can check out their website: 

    https://us.mitsubishielectric.com/fa/en

     

     

  8. Posted

    I will second IndeckTech's statement.  We had problems with the processors losing their programs w/o notice even with good batteries.  It was firmware related.  If I recall correctly, there was even a KB article on A-B's website about it. It was some time ago that I had the problem.  The firmware levels involved were 15 and 16 and the KB article numbers are 45709 & 38430.  There was another issue relating to the type of memory that was used on the device, but I think that problem was with communication cards, and not the processors.

    Kaiser_will is also correct when he states that a good PM system must be in place to replace old batteries.  In the case of the problems we had, the batteries were only a couple of weeks old when we were losing programs.  This is what led me to find another cause.  Please let us know your resolution.  Cheers.

  9. Posted

    A quick Google search resulted in a device from API.  Their website is www.api-usa.com. The device I saw is APD 5393.  I would opt for a signal splitter, like this device rather than actually breaking the load cell signal with a mechanical device.  The nice thing about signal splitters is that they provide complete isolation and each channel can typically be calibrated individually without affecting the other.

    1 person likes this

  10. Posted

    I used to have a ton of trouble with BOOTP-DHCP server program.  It would always take the IP, but disabling BOOTP would often fail.  Now I rarely have a problem.  The only difference is that once I set my IP address, I wait for the IP address to show up next to the MAC address in the 'Request History' window (the top one).  Then I select it from that list and click the disable button.  Maybe that is what I was supposed to do from the start, but I was not taught that.  By trial, I was able to learn the above pattern.  It has been working well since I figured that out.

  13. Posted

    Thanks, Gambit. It seems everything I correct causes more issues when I rebuild. I was able to get the password from the machine builder and I uploaded into GXWorks2. However, when I verify what has been uploaded to the PLC memory, it fails. I need to view what was uploaded and compare it to the converted file. They do not look the same.

  17. Posted

    I am still fighting with this. I was able to do the conversion from the Melsec Medoc Plus project to a GX IEC Developer project, and then open it in GXWorks 2. The problem is when I try a Rebuild All, there are key words used that GX Works does not like (Pointer, Out). I was able to change those tags, but now it is stuck with an undefined ladder label. I have not been able to get past that issue. The Gambit did not have that issue when I sent him the file. I had GXW2 v1.91 originally; I upgraded to 1.536 and still have the issue. The next thing I tried was an upload directly from the controller, but now I find it is password protected. I waited to do this step last because I wanted a documented copy of the program. I am awaiting word back from the original manufacturer to see what the password is. With the age of the machine and the fact that the OEM had a partnership with a third party on the controls, I am not expecting a quick response. The OEM has been helpful, but I just don't think they have the personnel any more that are familiar with this machine.

  18. Posted

    I am working on creating an archive file of the original documented program for a piece of purchased equipment. The original program for this FX-series plc was written in Medoc (the IEC version). With the help of The Gambit, I was able to convert the project from Medoc to GX IEC Developer, and then finally to GX Works. The problem I am having is when I compile the program in GX Works. I had a couple of labels that were reserved words and I changed them. The (hopefully) final problem I have is that I am getting Error Code C2019 which states "A ladder block label has not been defined.(Ladder Block No.16)". When I navigate to this label, I see it is called "Loop:". I do not know how to define this label to make the software happy. I tried to rename it (thinking "Loop" is a reserved word), but that did not help. I was a Mitsubishi user a long time ago, but Medoc and the dedicated programming units were the only reliable programming devices at that time. I have searched this forum and the user manuals, but have not found info. Any help you can give would be greatly appreciated. Thanks for your consideration.

  19. Posted

    Gambit: Thanks for the response. I had not tried that function. I tried it just now and it looked as though it was working, but after a few seconds, I got an error message. It said "This project version is not supported by this function. Cannot open project." I am running GX Works2 Version 1.91V. The vendor cannot even tell me what software the plc was programmed with.

  20. Posted

    I have a machine with a FX family controller that was provided by an OEM. The machine was built in 1999. I was able to get a copy of the PLC source code from the vendor, but I believe it may have been programmed using the IEC software that was tried many years ago. The manufacturer has since moved on to a different design as well as a different controls vendor, so their memory is a little unclear. The file names I have are as follows: CUSTOM.SYS EDM.EDM LRUBOXES.SYS SOFTCTRL.PRO I have copies of Medoc, GX Works 2 and GX Developer, but none of these will open the project. Is there someone out there who could open this project and do a file conversion for me? I will try to pull the program using GXWorks and GX Developer, but I am not sure if the software I have will read ALL of the PLC memory and get me enough info to provide an emergency backup. In the past, I used to help customers who tried uploading a file using Medoc when the machine was programmed with one of the dedicated GPP units. The GPP unit had access to all parameters, but Medoc did not. When the program was downloaded with Medoc, functions such as MELSECNET/MINI would no longer work and I would have to develop the TO/FROM logic to get the network functioning. I don't want to have the same issue here. It has been many, many years since I used Mitsubishi on a daily basis. I can either post the files, or you can PM me and I can send them directly. Thanks in advance for reading this. Derek

  22. Posted

    That is the generic message to make you stop and think before adding a new module. Yes, adding any new module online COULD affect the running system, but the risk is lower when adding a communication module. If it is a new ENBT card, your risk is really low. The main risk when adding used or previously-configured modules is when there could be a duplicate IP address. You can avoid this risk by NOT connecting the comm cable to the new card until AFTER you have verified it is properly configured.

  23. Posted · Edited by drforsythe

    By songs, do you mean a recorded tone pattern to annunciate the start or end of shift or break times? Or audio files that contain a full song? If you are looking to annunciate the start/end of shifts and break times, check out the Werma line. They are a German company who makes stack lights, horns, light modules and other annunciation devices. I remember seeing in the past where they have a recorded tone module. You record the sound you want to play when an input goes active. I believe you could record multiple tones. Start your search at www.werma.de. If you search for the word "vocal" or for 844 or 645, I think you will find an option for you. These are light stack modules that play multiple audio files based on an input. You record or store the sounds to the module.
    1 person likes this

  24. Posted

    Please describe how the drive is commanded to start. Is it from a plc, pushbutton, network connection? If it is controlled by a plc or other controller, is the drive being commanded to stop? Sometimes we monitor the current feedback from the drive and will command the drive to stop if current is above a programmed set point for a certain amount of time.