Are you a new Kepware user struggling to collect OEE data from a ControlLogix PLC through another ControlLogix backplane? If you're encountering "invalid device id" errors, it might be due to incorrect formatting. The path we've set is <10.1.ww.yy>.1.2.2 <192.168.xx.zz>.1.010.1.ww.yy, which involves an EWEB card, the backplane, the ENET card in slot 2, and the other PLC. While it seems right, there could be an issue. Any insights? - Justin
In my opinion, the information appears to be accurate. Just remember to include a "." before the second IP address. It's important to note that ControlLogix slots always begin at Slot 0. Assuming that the second Ethernet module is in the third physical slot (2) of the chassis and the ControlLogix CPU is in the first physical slot (0), have you been able to replicate this setup in RSLinx Classic? Setting up an OPC Topic and testing it with the Test Client could also be beneficial.
Yes, I manually entered that pathway and accidentally forgot to include the ".". I am able to access the processor through Linx. My next inquiry involves DH+ on the same 10.1 chassis, which also has DH+ cards. Can anyone provide guidance on the structure of the pathway through the backplane and out through a DH+ card?
I am unsure about how Kepware interprets the 1756-DHRIO.MSG instructions from PLCs, which are designed for the DHRIO module and include a command payload to execute a PCCC/DH+ command on a specific channel with a target node, gateway node, and link ID. Unlike in RSLinx Classic, there is no CIP path that directly incorporates the channel, node, gateway, and link ID. This could be a unique configuration issue specific to Kepware that I may not be able to address.
Despite my efforts, I have been unsuccessful in achieving the desired outcome. I am able to communicate via Ethernet using a physical connection from Rack 1 Slot 4. Rack 1 and Rack 2 are linked through EN2Ts installed in Slot 2 of their respective racks. The EN2T in Rack 1 has an address of a.b.c.d. My goal is to establish a connection to the PLC in Rack 2 Slot 1 by utilizing the EN2T in Rack 2 Slot 2, which has an IP address of w.x.y.z. In KepServer, I have configured the following path:
Hey Justin, this indeed sounds like a tricky problem. From my experience, the "invalid device id" error usually arises from incorrect routing. Your structure seems logically correct, but I would suggest checking the slot numbers just to be sure. The slot number for your EWEB card might not match the arrangement set. You could also try re-setting the path by removing and re-adding the devices. Additionally, make sure your controllogix PLCs and your backplane are updated with the latest firmware. It's always these small details that we tend to overlook!
Hey Justin, I once faced a similar issue and the problem was very subtle. In my situation, the issue lied within the separator for the IP address. Instead of using a dot, use a forward slash (/) after the PLC IP address. Secondly, I wouldn't use the colon for the slot address. Just put the slot number in parentheses immediately following the IP address. For instance, <10.1.ww.yy>/1(2). Hopefully, this will work for you as well. Keep us posted!
Hey Justin, I've had similar issues in the past and it did indeed relate to incorrect formatting. If you have a ControlLogix gateway, ensure that your path in Kepware reflects the actual physical path the data is taking, right down to the rack and slot number. Also, remember that Kepware starts numbering slots from zero, so adjust your slot numbers accordingly. In your case, you might want to try <192.168.xx.zz>.1.010.
Hey Justin, I totally get the frustration with those "invalid device id" errors! One thing to double-check is if the IP addresses and path formatting are exactly as specified in the documentation for both the EWEB and ENET cards. Sometimes, even a small typo or incorrect slot reference can mess things up. Also, make sure that the routing table is properly configured for communications between the two PLCs. If your devices have different firmware versions, there might be compatibility issues as well. Hang in there—it can be tricky!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - The "invalid device id" errors could be due to incorrect formatting of the path being used for data collection.
Answer: - The path that should be set is <10.1.ww.yy>.1.2.2 <192.168.xx.zz>.1.010.1.ww.yy, involving an EWEB card, the backplane, the ENET card in slot 2, and the other PLC.
Answer: - You can start by ensuring that the path formatting is correct and verifying the configuration of the devices involved in the data collection process.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.