Good Morning, hope you all have a fantastic day. I'd like to share some details about the current situation we're addressing on our site involving Allen Bradley 5555. The issue arose when I traced a digital signal (a switch) entering the DC INPUT card 1756-IB16 RE5-6/0. My goal is to track this input signal within the RSLOGIX system to observe the corresponding outputs and identify a GSV. The GSV class name is Module, instance name is SP_RE5_ETOR6, and attribute name is faultcodedest: defaut_cartes [53]. Apologies for the lengthy explanation, but I need assistance with the GSV instruction. After tracing the Destination (defaut cartes 53), I reached a dead end and am unsure of its purpose. Upon cross-referencing the destination, it led me to: OTEcontainer: communication_CNET, routine: Tables N1N2_BOOL. It appears that this may be used for display purposes or for communication with other PLCs. I believe you may have the solution to this mystery.
The GSV instruction is utilized for monitoring the connectivity between the controller and a specific I/O module. It is important to note that this instruction does not relate to the ON/OFF status of individual inputs or outputs. This particular GSV, focusing on the "Module" class and "FaultCode" attribute, captures any fault codes generated by the controller due to its connection with the module. It is crucial to understand that the GSV reads the controller's fault code when attempting to communicate with the module, not the fault code of the I/O module itself. For instance, if a module is removed, the controller will not receive any information from that module, indicating a lack of response. Therefore, the GSV instructions gather status information from the controller and store it in tags for usability, excluding input or output data.
Thank you for your explanation. I initially cross-referenced the input module in hopes of finding the connection inputs, but it did not provide the correct information. I would greatly appreciate your guidance in defining all inputs to that specific module. Each input is tagged in Rslogix, which is precisely what I am searching for. Thank you for your help.
Hi there, your explanation was very thorough, no need to apologize. For starters, the GSV (Get System Value) instruction is often used to extract system data or information about how the PLC is performing. From your description, it seems like the "defaut_cartes [53]" is a fault code destination. Generally in the RSLOGIX system, fault codes provide key diagnostic information. Since it led you to "communication_CNET", it tells me it's likely related to the networking or communication aspect of the PLC, possibly identifying a fault or issue in communication. "Tables N1N2_BOOL" could be a data table used for storing boolean values derived from this process, possibly mapping fault statuses. Though, without the full context it's a bit hard to say with certainty. Would you mind sharing more about what's tied to the input component and how this fault would affect your system?
Good Morning! This is indeed an interesting mystery. It sounds like you've done a great job tracing the problem so far. From my experience with Allen Bradley PLCs and RSLOGIX, your interpretation of the OTEcontainer "communication_CNET" possibly being used for display or communication purposes is plausible. However, the Tables N1N2_BOOL appears to be related to boolean value storage. As for the GSV class name, instance name, and attribute name, could they be possibly involved in error handling or diagnostics? It would be helpful if you can check the GSV's attribute value when the fault occurs. Also, consider reviewing the comments within the program (especially by the previous programmer), as they may offer additional clues. Sometimes a solution is just hidden in plain sight. Keep us posted on your findings!
Good morning! It sounds like you're diving deep into some challenging troubleshooting with the Allen Bradley setup. The way you traced the digital signal is solid, and your insight about the GSV’s role in retrieving the fault code is spot-on. Regarding that destination you mentioned, it often helps to check if the other PLCs or devices that interact with it are configured correctly. Sometimes the communication aspects can lead to unexpected behavior if there's a mismatch in the expected data types or formats. Have you also looked into the specific parameters for the communication_CNET container? It might shed some light on how that data is utilized. Let me know if you need any more ideas—happy to help!
Hi there! It sounds like you've done quite a bit of detective work already! The GSV instruction can definitely be a bit tricky, especially when tracing specific attributes. Based on what you mentioned about the `faultcodedest`, it indeed seems like it’s tied to how the system handles errors or status communications, possibly for monitoring or reporting purposes. It might be worth checking if there are any active connections or mappings with the `communication_CNET` routine as well, as that could give you insight into how faults are being processed. Have you looked into the documentation for the `Modules` class in RSLOGIX? That might provide some clarity on how that fault code is intended to be used. Good luck!
Good morning! It sounds like you're diving deep into a complex setup with the Allen Bradley components. The GSV instruction can be quite tricky, especially when tracing inputs and outputs in RSLOGIX. From what you described, it seems like you're on the right track with the OTEcontainer pointing towards communication aspects. It might be worth probing into other attributes of the GSV within that module or checking any associated tags for more insight. Sometimes, digging into the documentation for the specific components can reveal nuances that might not be immediately apparent. Keep us posted on what you find!
✅ 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 issue involves tracing a digital signal entering the DC INPUT card 1756-IB16 RE5-6/0 within the RSLOGIX system to observe corresponding outputs and identify a GSV.
Answer: - The GSV class name is Module, instance name is SP_RE5_ETOR6, and attribute name is faultcodedest: defaut_cartes [53].
Answer: - The destination led to OTEcontainer: communication_CNET, routine: Tables N1N2_BOOL, suggesting it may be used for display purposes or communication with other PLCs.
Answer: - Assistance is needed to understand the purpose of the destination (defaut cartes 53) and its relevance in the context of the RSLOGIX system.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.