MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

30 Excellent


  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender Male
  • Location Carolinas
  • Country United States

Recent Profile Visitors

3927 profile views
  1. Studio 5000 and different PLC versions

    It's really not as bad as it sounds for versions over 20.  You do have to install the separate versions; however, once installed you run the same program and you dont have to go through some selection process to use different versions.  It's more like you install the capability to interface with different versions of firmware.  Where it gets squirrelly (technical term) is when you have to work with a version 20 or below.  Then you will need a separate software package (RSLogix5000 instead of Studio5000).  The software will automatically switch between the required packages with those two also.  So if you open something with Studio 5000 that requires RSLogix5000, it will automatically close Studio5000 and open the file in RSLogix5000. 
  2. Periodic Tasks Effects on Communication

    Yes those scan times can limit or knock you off of online programming.  Early on, I inadvertently changed my scan time at one of Rockwell's road shows to 1ms and completely locked myself out of the PLC.  Had to take the PLC to program mode to be able to get online and change it back.  The 3ms scan time is probably the one that is killing you as there is very little time in between for comms.  You may want to see if one of your routines might be better served by an event rather than fast scan times.  Rockwell does recommend using periodic tasks, but they do need to be setup with realistic scan times.
  3. plc5 conversion

    Are you referring to the S2 file with the first scan bit, error bits and such?  If so there is not really a comparable group of data like that in the logix.  There are ways to get information that is similar in the logix.
  4. FX2N Battery replacement

    Thanks - I have no idea how the battery is being monitored, but I am purchasing the software to make sure I have a backup so I can check that out. 
  5. FX2N Battery replacement

    I have run across a Mitsubishi FX2N with a battery light on.  I have never worked with Mitsubishi before, but the manual describes changing the battery and indicates the controller must be powered down for the change.  You have to beat the clock and change the battery within 20 seconds.  Has anyone changed these batteries while powered?  Used to do that with PLC5's but I have never dealt with this processor before. 
  6. Ok, a quick way to evaluate this is to go to your input data file and click on usage to see if any inputs are used.  Doing this I see 4 inputs used in the program.  I can right click on any of those inputs and select cross reference or find all and I will get information on exactly where in the program those inputs are located.  I find inputs in program files 6 and 8.  Keep in mind that the PanelView can also directly access such inputs so such inputs may be directly accessed by the PV screen.
  7. How to move an Array ? (CompactLogix)

    The COP instruction is the correct instruction for this.  You were on the right track with Array1[0] to Array2[0].  You just need to put in the number of elements to copy as the length.  You cant leave off the [0]  part as the starting location.  Array1 is not a valid location  - Array1[0] is.
  8. So if that is the PLC program that they forwarded to you then that is unfortunate as it also does not have any descriptions in it.  I would again request they send you a copy of the program with descriptions.  If you get it, make sure you put it somewhere safe so that it will be available in the future.  In addition, I would ask them to send you a copy of the Panelview configuration or backup.  With that you can restore the existing HMI configuration to a new Panelview.  While panic is a little harsh, his primary points are valid.  I understand that your facility probably does not have experienced controls people that might have been aware that this was an issue.  Now that you do understand this, I would suggest you go through your plant and catalog other machines that may be lacking proper documentation.  Get ahead of the next problem by making sure there is a documented copy of each program and configuration files for all of the configured electronics in your facility.  On this system, if you cannot get a documented copy of the program, you at least have a copy of the drawings so documentation can be added.  Your fist step there is to go to each input and each output in your program and add the description shown in the electrical prints.  Nobody on this forum is going to do that for you.  They will answer questions and some may be willing to take care of it for a fee.  I would suggest locating a local integrator to help you work through this issue.  It sounds like you really need someone to look over your shoulder as you work through this.
  9. Retentive OTE

    Ok I'm not really sure what the exact method Ron proposed way back when as it is no longer available.  In fact I'm kinda surprised that his posts all have "Guest" by them.  All of that aside, they do discuss something that I was going to suggest you try and it looks like one person has used it successfully in the PLC5.  Keep in mind that as we have mentioned earlier, all memory locations associated with OTE instructions will be reset upon power up or return from program mode.  The way you may get around this is to store all of your outputs in INT tags continuously in order to save their operating value.  Upon return from power up or run mode, you would use the first scan bit to copy from those storage registers into your output registers effectively restoring the output word values to your outputs.  Obviously this move instruction would need to be processed before any output instructions to work properly but otherwise it should work.  I've never tried this before and it sounds like a good way to get into trouble from a safety point of view.  You generally dont want things starting up from a power outage without some sort of operator intervention.  If you only have a few outputs that you need to do this with you could use a masked move to only enable the outputs you are interested in restoring on power up. 
  10. I'm not sure what you are looking for, but I see a program with absolutely no documentation.   That usually happens when someone uploads from the PLC without having an existing program file on the PC.  Until recently with the later Logix controllers, all documentation was stored in the program file created in the programming software.  Uploading without that will just give what you have shown.  I would suggest trying to find an existing program file on a PC.  If this was contracted out, you may be able to contact the integrator.  Most of us keep files from our previous projects.  Other than that, your only option is to go to (hopefully existing) drawings.  You will have to methodically go to each real world input/output and document their purpose.  From there you have to work backwards in the program determining what each register and bit does and documenting along the way.  I did notice real world outputs in ladder 5 and many of the N register bits are just buffer bits and directly activate those outputs.  Figure out one and you get the other!  Two for the price of one.  Unfortunately this is a long and drawn out process that could take days to complete.   In addition, without information on the real world I/O there is no way for anyone to really be able to help you figure out what does what.  Unfortunately you have a lot of work ahead of you!   I'm sure if you get stuck anyone on this forum would be happy to help.  The program looks to be fairly straight forward so you dont have to worry about complexity.  Could be a good learning experience.  I'm sure that's what you wanted to hear!
  11. Retentive OTE

    Keep in mind that you will need to pair each OTL with an OTU (latch and unlatch) in order to turn the output off.
  12. Constants value in PLC 5/20

    Yes you can change the value of a data table item by placing your cursor on the value in a statement as you have shown and just changing the value.  As Armadillo points out, you should do a cross reference of that value to make sure it is not overwritten somewhere else.  Keep in mind that it may be overwritten conditionally and may not immediately overwrite the value you put there but may do so when required by other logic. 
  13. Setting up Compact to work with Yaskawa VFD over Ethernet

    Yeah I'm not sure about that.  We have a custom AOI where I am using this so it would not be the same.  If you are using a Yaskawa AOI, then it should be documented in one of their manuals.  It should not care about the size of your drive or any about your motor characteristics.  That is all stuff that is configured in the drive.  You just care about start, stop, speed, faults, etc.
  14. Allen Bradley SLC 5/01 processor unit

    Not too familiar with the 5/01, but that sounds like you have lost the program.   Can you go online?
  15. Setting up Compact to work with Yaskawa VFD over Ethernet

    What AB PLC are you using and what Yaskawa drive?  Third party drives are actually pretty easy to setup on the logix platforms also - you just need to use a generic ethernet module.  All the settings in the module are in the Yaskawa Ethernet I/P manual if you are interfacing with a compact or controllogix.  You will have to get out the manual to discover the best way to start/stop and control speed as well as how to get feedback information.  Attached is an example of the Ethernet module setup for the A1000.  Pay careful attention to the comm format data time.  Choose the wrong one and you will have problems.   Not that I have ever done that....