Joe E.

I'm not really a communications guru with these, so I'm not sure what the Passthru Link ID is. On mine, they're set to 2 and 1. You should be able to repeat the autoconfigure in RSLinx to re-establish communications after you change the channel 0 settings.

You need to know the COM port settings of the HMI. Baud rate, parity, handshaking, stop bits, etc. Basically, look at the channel 0 settings dialog box in the PLC project. You need that information for the HMI so you know what to set the PLC to.

That looks like the normal way to do it. Was there a part of it you had a specific question about?

You can also add the target device to the I/O tree of the device with the MSG instruction and browse to it. Here's an example using a 1756-L71 ControlLogix to read data from a 1769-L33ER CompactLogix:

You may be able to use a managed switch to isolate the devices, but I'm not an expert at all and can't help you with that. It may be easier to add a second network card to the PC. There are a bunch out there that plug into a USB port if your PC doesn't have any free expansion slots. We've done that to have a PC connected to 2 different networks.

What change do you have to make to channel 0 in the PLC to make it work? When you download the change, your PC will probably lose comms with the PLC but you should be able to repeat the autoconfigure in RSLinx to get it back. Of course, your PLC will only be able to talk to either the HMI or your PC if they're both using the serial port. I would recommend getting a USB-DH485 adapter so your PC can be online with the PLC at the same time as the HMI. I've done it before where I had to switch between HMI and PC when making changes and it was a pain when I was troubleshooting since I couldn't look at the code online while seeing what the HMI was displaying. Rockwell calls theirs the 1747-UIC. Here are 2 sources for a 3rd party cable that we've had very good results from: https://www.theautomationstore.com/allen-bradley-slc-500-programming-cable-usb-to-dh485-1747-uic/ https://www.plccable.com/allen-bradley-1747-uic-usb-to-dh485-usb-version-1747-pic-slc-500/ That would let the HMI use the serial port while your PC uses the DH485 port.

Ok, inside the PLC program, check the COM port settings. In the project tree, double-click on "Channel Configuration" under "Controller". Check the Channel 0 settings and make sure your device is set the same way. If they don't match, make them match by changing either the PLC or your device. For an HMI, I think you can just use the Chan. 0 - System settings.

If you connect to the serial port and autoconfigure a DF1 driver in RSLinx, does it see the 5/03?

I've had similar experiences as PLCMentor with the SLC 5/xx power supplies. They can cause the PLC to randomly dump its program and can also cause it to fault, thinking that a module is failing. I've seen it where we replaced each module one at a time (the fault code couldn't identify which module it was) until replacing the power supply fixed it. I've had similar behavior caused by the chassis.

Do you have the project file for the 5/03? It will have an "RSS" extension. The current archive will have the COM port settings in it. Your field device will need to match those settings.

The KB article refers to a manual: MOTION-RM003I. I glanced at it quickly and it looks like the information you need is in there, but I've never done it so I can't guarantee it.   Actually, I think the manual was attached to a different article that was linked to from the one Ken Roach provided. It was also a TechConnect only article.

The round mini-DIN connector and the 3-pin Phoenix connector are both connected to the Data Highway Plus (DH+) communications port. It takes a special adapter to communicate through that channel. The Rockwell adapter is 1784-U2DHP. In our experience, it's very expensive and not very robust. We've had several fail in normal use. ProSoft makes a gateway module as well, the AN-X2-AB-DHRIO. We've found the ProSoft module to be a lot more robust and cost effective, but it requires an external power supply and is a little more cumbersome to configure in RSLinx (not bad at all, just not as easy as the U2DHP). I'm a little surprised you damaged the power supply but not the CPU. You may have killed the DH+ port without affecting the rest of the CPU. I'm not aware of any additional protection inside the power supply, just the fuse on the front.

RSLogix 5000 changed names around v20 or so to Studio 5000. Other than that, for your purposes here, it's the same software. It looks like you only have v21 installed.  You need v20 of RSLogix/Studio 5000. Be sure to download the latest minor revision of v20. This major revision broke with Rockwell's normal practice with major/minor revisions in that you needed to match the minor revision of the software to the hardware, not just the major revision. And the minor revisions couldn't be installed together. The latest minor revision of v20 fixes that so that you can use the latest v20.x software with any v20 project and hardware. If you convert the project to v21, you will also need to convert the hardware, which requires flashing the firmware and downloading the new project. This will wipe the processor memory. If at all possible, get hold of the correct version of the software and install it. It should install alongside your existing software with no issues.Then you will be able to support the machine as-is. You can upgrade if you want, but there's probably no benefit to doing so.    

Is the L35E the older family without USB? If so, it may be easier to use the serial port and the DF1 driver in RSLinx.If it has a USB port, I would use the USB port. Once you establish communications, you can go online and determine the IP address. If the previous machine and programmers didn't use Ethernet, there's a chance it still has BOOTP/DHCP enabled. Use a BOOTP utility to see if it's broadcasting BOOTP/DHCP requests. Rockwell has one that's kind of reliable. Phoenix Contact has one too. If it already has a static IP address, you need to know at least what subnet it's on. If you're lucky, the Ethernet/IP driver in RSLinx will find it as soon as your PC's IP address and subnet mask are compatible, as long as it's not the same address as your PC. There is some setting that our IT folks have changed in our group policies that keeps the Ethernet/IP driver working on our laptops. We have to use the Ethernet Devices driver, which requires that we know the IP address ahead of time. You can use Nmap/Zenmap (portable version here) to run a ping scan to identify the IP address of the PLC. You will likely need to try several subnets to find the correct one if you can't make an educated guess as to what the address is. The user manual for this processor includes some information about the RS232 and Ethernet ports, starting on page 25.  

Interesting.... The first thing the compare tool does, if you watch closely, is export the flies to *.L5K.  

Are the machines all on the same subnet? If so, do they need to be? If you can change subnets, you can then lock down the IP address configuration of the PC so it can only see that machine.   If the machines are (and have to be) on the same subnet, a subnetting expert may be able to work some magic with the subnet mask to block access, even if the machines are on the same subnet but I'm not that expert.

For the ML1200, you can probably use the cheapest version of RSLogix 500 (not the free one, alas, that one only supports the 1000 and 1100). A good USB-serial adapter is the Keyspan USA-19HS ($25 on Amazon). You'll need a cable too. If you get it from Rockwell, it will be expensive, but this one from Industrial Concepts should be fine. We've used other cables from them with no issues.

ProTool/WinCC are for Siemens HMIs, not AB. OP: Since your original HMIs are at version 5.x there's a chance they can be flashed to v10. Neither part number is configuring as a current product, though, so I can't confirm that. You may have to contact your local Rockwell distributor to find out for sure. Do you have a project file for the HMI? It would be a *.apa file. If so, you can create a new runtime file from it at whatever firmware version you want. If not, you MAY be able to decompile the runtime file (*.mer) into a project file if the original developer was kind and selected the option to allow it. You will need FactoryTalk View Studio for ME to do this. I'm not aware of any way to update the FW version of the runtime file directly, but someone else on here may know of a way.

I pulled up my XP VM and found CLR.DLL with a date modified 2014-01-08. It's in the directory C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ Would it help if I sent you that file? There is a Windows procedure for registering DLLs that you may have to do: http://xperiencexp.blogspot.com/2006/01/how-to-register-dll-files-in-xp.html ETA: the file itself is 6.6MB but it zipped to 3.19MB so I think I can PM it to you. ETA2: I just sent it in a PM, so hopefully that helps.

You can either download the old firmware to the PLC or, in the v10 project, go to the controller properties and select "change controller". There will be a place to change the processor version. It will convert the project and save it as a copy, which you can then download. In your other post, you mentioned a ControlNet module in the chassis. We have a system with ControlNet as well. I originally upgraded the -L55M12 from v13 to v16 without having to do anything to the ControlNet network and then from an -L55M12 to an -L81E (v30) with no issues. Your results may vary, however. You may have to change the firmware of the ControlNet module and/or re-schedule the ControLNet network using RSnetworx for ControlNet. If upgrading the processor causes issues with the ControlNet network, and you don't have the software or expertise to reschedule it, I would probably re-flash the processor back to v10 to get your system back running.

I'm 99% sure the -L55 supports back to v10. I know that v16 is the newest it supports. We have about a dozen of these in service right now. Here is what your CPU LEDs mean: Run = solid green: PLC is in run mode I/O = off: Either no I/O is configured or there is no program in the PLC RS232 = solid red: ????, manual just says off or solid green OK = solid red: non-recoverable fault, CPU has cleared the program BAT = Off: battery is ok Force = Off: no tags contain I/O force values and I/O forces are inactive   Here is an older version of the ControlLogix user manual that covers the -L55: AB_ControlLogix_UserManual_2007-01.pdf There is a KnowledgeBase article (278692) on this but it requires TechConnect access and really isn't that helpful for figuring out what happened, just how to recover, which you've already done. there's another manual here: https://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm014_-en-p.pdf It says that if it persists, to contact Rockwell support. If you don't have a support contract, I would reach out to your local distributor for assistance. Ours has always been very helpful. I remember having something weird happen once, but I can't find my notes from that far back (2011). It turned out to be the memory module. This processor has been out of production for a very long time, but you can probably find the CPU and/or memory module on the secondary market if you want to try a straight replacement instead of an upgrade.     AB_ControlLogix_UserManual_2007-01.pdf

I sent you a PM with a download link. Let me know if that doesn't work and we'll try something else.

I converted and archived it but it's 4.6MB, which is too large for the board. Let me try something else after this meeting...

Well, that escalated quickly... I hope that Google translate caused the response to be amplified further than intended, but it's possible it didn't. Sajadh: What have you done so far? I'm not familiar with that particular hardware, but some concepts carry over between hardware brands very well. Is x1 a physical hardware input to the PLC? If so, writing to it with the HMI will almost certainly not have the results you're looking for. The HMI should be writing to an internal memory location in the PLC that will then be used to control the output.  

Google Translate: You will need RSLogix 500 or RSLogix Micro. There is a free version of Micro (Starter Lite) and a relatively cheap paid version. RSLogix 500 is more expensive but also covers the SLC 500 series processors. Contact your local distributor for your pricing. If you don't have a project archive file for the PLC, you can upload it but you won't have any symbols, comments, or other documentation. The project file will have an "RSS" extension.