Hey everyone, I am currently setting up an OLDI card which involves creating a message instruction in the PLC to activate an event on the card. I attempted to create a new Controller tag of the type MESSAGE, but encountered a warning during verification stating "message tag not configured." Furthermore, when trying to utilize the tag in the message Control block, I received an error indicating that no tag had been specified. My system is running RSLogix5000 V20.01. Any assistance on how to resolve this issue would be greatly appreciated. Thank you!
When creating a message instruction, it is essential to assign a specific tag name for defining the instruction itself and another tag name for the data being exchanged. It appears that there may be confusion regarding the use of tag names in the message control block configuration options. Let's clarify the distinction between the tag names for the message instruction and the data being communicated.
To efficiently create a Message Instruction for triggering a tManager Event in ControlLogix, follow these steps outlined in the email from the card supplier: 1. Use the RSLOGIX5000 Tag Editor to generate a tag with a MESSAGE data type at controller scope. 2. In the Ladder Editor, add a rung containing a MSG instruction with the newly created MESSAGE tag as the operand. 3. Access the Message Configuration dialog by clicking the button next to the operand. 4. Select "CIP Generic" as the Message Type. 5. Choose "Set Attribute Single" as the Service Type (Service Code 10) and specify the Class and Attribute values. 6. Input 4 for Class and 3h for Attribute. 7. Leave Source Element empty. 8. Enter 0 for Source Length. 9. Match the Instance (decimal) with the Message Instance defined in the tManager Event trigger (1024-4095). 10. Navigate to the Communication tab. 11. Provide the module name or CIP path in the Path field. 12. Select "CIP" as the Communication Method. 13. Check the "Connected" box. 14. Depending on message frequency, choose to enable or disable "Cache Connections". 15. In case of a connection-related issue, AB pre-defined error codes will be utilized. If a tManager processing error occurs, specific error codes apply (7001h-7006h). The MSG done bit remains unset until the trigger process concludes. Consider using a PERIODIC trigger instead of a message instruction for monitoring PLC tags without the need for ladder logic. Feel free to confirm successful implementation of these instructions.
I appreciate the message, and I'm glad to hear that it was successful for me!
Hello! That sounds like a confusing problem. It's possible that the tag hasn't been applied correctly to your message configuration. I recommend double-checking the assignment of your tags, making sure that you have structured the data type correctly and specified it in the control block. Another point to consider is ensuring your software is up-to-date. RSLogix5000 v20.01 is quite an older version and you might find less compatibility issues with more recent version such as Studio 5000. Hope you find a quick resolution to this – good luck!
It sounds like you're having a bit of a challenge, but not to worry! First off, double check to make sure you've created your MESSAGE tag correctly. Make sure you've created it within the Controller Tags and it's not just residing in Program Tags since it won't work there. Also, confirm that the "Data Type" of the tag is "MESSAGE" and not anything else. Now, when you're configuring your MESSAGE instruction, you need to specify your created tag in the "Message Control" attribute box. Just a reminder, you need to write the tag name exactly as you created it, as it's case-sensitive. If still you're encountering issues, try to update your system to a newer version, V20.01 is somewhat outdated and newer versions come with better support for complex tags like MESSAGE. Hope this helps!
It sounds like you're on the right track, but that error usually comes up if the message tag hasn’t been fully set up. Make sure you've configured all necessary parameters for the MESSAGE type tag in the controller. Double-check that the tag name is correctly referenced in your message control block. You might also want to ensure that the message type you’re using matches the requirements of the OLDI card you’re trying to configure. If it persists, sometimes restarting RSLogix can help clear minor glitches. Good luck!
It sounds like you're on the right track, but the warning suggests that your MESSAGE tag might not be fully defined yet. You’ll want to double-check that the tag's properties are correctly set up, including the message type and any necessary configurations. Make sure the tag is added to your controller tags and that it has the right data structure for the message you’re trying to send. Also, consider reviewing the online documents or help files in RSLogix5000 for any specific requirements related to OLDI cards; sometimes, there are particular settings that need to be adjusted. Good luck, and let us know how it goes!
It sounds like you're on the right track, but you might want to double-check the configuration of your MESSAGE tag. Make sure you have defined all required parameters, like the source and destination of the message, properly in your tag settings. Also, ensure that your Control Block references the correct tag that you've created. Sometimes, restarting RSLogix can help refresh the communication if it's acting up. If you could share what specifically you've set for the tag configuration, that might help us pinpoint the issue even better! Good luck!
✅ 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 warning "message tag not configured" indicates that the message tag has not been properly set up or configured in the Controller tag of type MESSAGE. This can lead to errors when trying to utilize the tag in the message Control block.
Answer: To resolve the error indicating no tag has been specified, ensure that the Controller tag of type MESSAGE is properly configured with the necessary parameters and that the tag is selected correctly in the message Control block. Double-check the tag configuration and make sure it meets the requirements for the operation.
Answer: For assistance with setting up an OLDI card and creating a message instruction in Logix5000, you can refer to the software documentation, online forums, or reach out to the manufacturer's technical support for guidance and troubleshooting tips.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.