pcmccartney1

MrPLC Member
  • Content count

    321
  • Joined

  • Last visited

Community Reputation

41 Excellent

About pcmccartney1

Profile Information

  • Gender Male
  • Location Colorado
  • Country United States
  • Interests Family, Golf, Lacrosse
  1. communicate with PLC melsec Q (mitsubishi)

    I strongly suggest the use of a Red Lion DSP along with Crimson 3 software.  Easiest, simplest solution.
  2. Kinetix 300 Hard Limits

    I'm not sure there is an overall answer to your question. I've had to hardware or short the hard travels limits occasionally.  I would strongly suggest that you do enable and set the soft limits to prevent damage to the machine and the servo. Keep in mind that these might also have to be dynamic as you may be "Homing" and zeroing your axis based upon external means, i.e. a proximity switch or limit switch.  If someone were to change the position of this switch and you don't re-evaluate the soft limits, you might introducing a possible crash condition.  I would also ensure that any positional motion commands can not execute if the position is outside the soft limits.  I would expect the drive to realize this and fault on it's own to protect the machine and the servo.
  3. 1769 SDN Devicenet Scanner

    looks correct to me.
  4. 1769 SDN Devicenet Scanner

    Karim, Hopefully, the backup file you have is a *.DNT file. You'll need "RSNetworks for DeviceNet" and the "DeviceNet Commissioning Tool" (it is usually accessible from within the RSNetwroks for DeviceNet). You'll need to be able to access the DeviceNet scanner via RSLinx and generally via EtherNet port on your PLC. Please understand that all DeviceNet products are set at the factory at Node address 63.  From your DNT file and "RSNetworks for DeviceNet", you should be able to determine that actual address of your old scanner module. Then using the "Commissioning Tool", you need to change it's address and baud rate to match the current settings for the old scanner.  Before doing so, I would probably also leave the fieldbus cable unattached from the front of the SDN to make sure the new scanner (factory default address of 63) does not collide with another node on the network.  After the change of address and baud rate are completed, you should be able to re-attach you fieldbus cabling.  Also, be aware, that dependant upon your actual network fieldbus cabling, you might need a terminator resistor on the fron of the module to be installed. At this point you should then be able to go online with the module and download the scanner's configuration.  The caveat is that the PLC that hosts the SDN will need to be in REMOTE PROGRAM mode.  Meaning you will have to stop your process.  Once the configuration is downloaded, you should be able to put your PLC back into REMOTE RUN.  Hopefully, the PLC has some code to do a delayed startup and "Enable" the scanner and then the scanner should start reading and writing to the VFDs. The alternate method, if you can't stop your process, would be to have a duplicate setup of your current PLC and associated IO modules in a test bench arrangement.  Then move the programmed scanner to your live system.
  5. Controllogix Prog .ACD to PDF

    Harsh, Looked at the program, I see that you are an admin for the machine.  I also see the name of the original company that created the logic and the programmer.  I checked and that person exists.  Have you contacted them and him to get a pdf of the program?  I'm concerned that you are asking us to print this program and go around the OEM of the equipment and possible intellectual property rights.
  6. Retrofitting old PLC5

    I would think it would be dependent on the size and scope of the system, it's I/O content, comms interfaces required to support.  Then there's the cost.  To minimize downtime, sometimes it's better to go with the ControlLogix route and maintain the existing IO and wiring through the use of the original swing arms and I/O modules.  Of course, this gets you into newer controllers with a future, but the I/O is still tied to the old PLC5.  While much can still be found but are fewer and fewer, the prices for these components is sky rocketing.  Other times, it's better to go the complete replacement direction. There are migration tools for both the software and the hardware.  They vary in completeness, you might still have to rewrite some code.  Pay particular attention to the RSView (assumed to be 32).  Look long and hard at various comms networks and how you would need to maintain them or consider newer comms protocols. Personally, I'm a proponent of the complete replacement route for total life cycle of the machine and future support. You need to evaluate all these things to make an informed decision.  Maybe your customer only needs to extend the life span of the machine by a few years.  Maybe your deems this machine (work horse) and needs to extend the life span for a decade or longer.  This should help to make the wisest solution for this machine and your customer and your company.
  7. CLX to Fanuc Remote Start

    Will, You always have the most amazing work instructions.  Thanks. As stated earlier, I'm past establishing comms.  It was more a question of basic UOP signal exchange, then timing and the sequence of the signal exchange to get the desired response and action from the robot.  @jstolaruk was able to PM me some links and find some timing charts and descriptions that have me well on my way.
  8. Retrofitting old PLC5

    Just goto Rockwell's website, and search for PLC5 migration. You see everything you need to know. On the RSView, need more detail.  Is it PC based RSView32?  With some extra logic, you should be able to maintain the majority of your original application.
  9. CLX to Fanuc Remote Start

    This might be the wrong forum, so be patient. I've done interfaces, via multiple protocols, to multiple Robot controllers over the years, Kuka, ABB, Espon, Mic, Motoman... Seems like it should, would or could be easy to accomplish for Fanuc via E/IP. The setup is easy enough, no issues with Generic EtherNet module configuration, establishing connection and exchanging data. My question is how to get the robot to start, stop, pause or hold remotely.  Normally, I've searched for and found manuals from the various robot manufacturers and they have a written description and or timing charts for a sequence of operations or events to accomplish the remote starting, stopping, etc...  To date, I've googled that stuff, with no solution...  Has any one here, got an example, or a manual or a link to a manual that might describe this in some detail? Thanks in advance
  10. Unsupported processor

    Here you go.   BALL TRAVERSE RIG.pdf
  11. 1771-IAD A, B, C, D Terminals

    Beau, Wondering if you go look at your electrical drawings (focused on the MCC buckets) that they used the A as an intermediate point to get the 120VAC (interrogation voltage) out to the bucket and thru the status contacts and then back to the input card?  They probably then "jumpered" the 120VAC to other buckets in the area that needed to send status back to the same input module.
  12. 1771-IAD A, B, C, D Terminals

    Seems he would have a fault on the module or the PLC5 were the wrong module be installed in the slot and differ from the program? But as the others have said, those terminals are not used for the IAD.
  13. Stratix Switch Data Type

    Seems to me that RA documentation (and the physical tag in the tag database) generally shows the DINT, in this case .Fault, then shows tags directly below it for a breakout of DINT as BOOLs.  But in this case, there are 33 individual bits listed.  I think it's just a matter of testing to see what bits turn on when and what the DINT value shows. Just for giggles, I added a 6, 10, 12 & 20 port switches, then looked in the tag database.  The tag changes along with the definition of the BOOLs.  It it obvious for the 6 Port, not so obvious for the 10 port and above.
  14. New Laptop for PLC's and control works

    VMWare is the way to go.  It is not free, but Workstation Pro is about $275. I have multiple images to support different control vendors software - Rockwell, Siemens, Automation Direct, Omron, etc... Minor demonstration of it's power - I had three different images open and running.  The first was online via VPN to a Siemens based robotic cell to help troubleshoot an issue.  The second was online with an Omron system during testing.  The third was open with Rockwell offline while my machine was being built and writing code. 
  15. ControlLogix DLL File

    Neech, when I read the thread it says it's only valid for SoftLogix Controllers.