Experiencing difficulties with a Generic CIP Message on a Rockwell processor? Despite prior experience with messaging, encountering errors can be frustrating. The device in question provides Service/Class/Instance/Attribute data, with specific requirements for retrieving device status. By populating the CIPAPPCFG with the necessary information and sending a value of 550, the device should respond with its status. However, persistent errors like ErrorID: 224SubErrorID: 5ExtErrorID:0StatusBits: 13 can be puzzling. While communication with the device is confirmed, troubleshooting error 224 and its SubErrorID remains a challenge. Could a conversion issue be causing the error in the COP instruction? Any insights or solutions on this matter are greatly appreciated.
What type of data should be sent to the device - DINT or REAL?
Error code 0xE0 or 224 appears to fall within the Reserved for Object Class Specific Errors range, indicating that it is not a generic Ethernet/IP error but rather specific to your device. To access the data from the device, you need to send a value of 550 and it will provide you with the device's status. Could you kindly provide a link to the device manual for further reference?
This is a 32-bit DINT data type.
Unfortunately, all I received was an example program for Studio5000 and a brief explanation text, which does not seem complete. I have successfully done this before with a 1769 PLC, but I am facing issues with a Micro800 now. Could there be limitations on CIP objects in the Micro800? Is it possible that it does not support a "Custom" CIP configuration, despite the specifications in the AppCfg suggesting otherwise? I am still questioning its compatibility with this feature.
Would you be able to share the Studio5k sample code for others to access?
From my understanding, Error 224 usually points to 'service not supported,' and SubErrorID 5 may relate to 'attribute not settable.' Thus, it looks like a conversion or configuration issue might be the root of the problem. Have you verified that the Service/Class/Instance/Attribute configuration is correctly set up for your specific device? Sometimes, a slight misconfiguration or an unsupported feature can cause such issues. It might also be worth checking that the data type in the COP instruction matches the expected data type of the target device. Additionally, it's important to remember firmware versions may play a role in these situations. All of this should help narrow down your troubleshooting process.
This is a tricky one indeed! It seems like you're tackling an issue where the generic message doesn't execute as expected. I'm thinking the problem might lie within the connection path; maybe there's a slight mismatch with the network adapter. Another possibility could be the data type. Not all device attributes support all data types. An incorrect class, instance, or attribute value could lead to such errors. The ErrorID you provided typically signifies an invalid parameter. Also, make sure your processor firmware is up-to-date. A firmware upgrade might be the solution. Keep us posted!
✅ 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: Answer: Common causes of Generic CIP Message errors can include issues with data population in CIPAPPCFG, incorrect values being sent, communication errors, or problems with the instruction set.
Answer: Answer: Troubleshooting ErrorID 224 and its SubErrorID may involve checking for conversion issues in the COP instruction, verifying the data being sent and received, and ensuring all required information is correctly configured.
Answer: Answer: To retrieve device status, populate the CIPAPPCFG with the necessary information, send the appropriate value (e.g., 550), and the device should respond with its status. If errors persist, further troubleshooting may be required.
Answer: Answer: Addressing persistent communication errors may involve verifying the connection setup, checking for network issues, ensuring proper configuration of the messaging parameters, and reviewing the error codes for clues on the root cause of the problem.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.