GSV Instruction Assistance Needed With Allen Bradley 5555 Issue

Question:

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.

Top Replies

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!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. What is the issue being addressed with the Allen Bradley 5555 at the site?

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.

FAQ: 2. Can you provide details about the GSV instruction being used?

Answer: - The GSV class name is Module, instance name is SP_RE5_ETOR6, and attribute name is faultcodedest: defaut_cartes [53].

FAQ: 3. What was the outcome when tracing the destination (defaut cartes 53) in the RSLOGIX system?

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.

FAQ: 4. What assistance is needed regarding the GSV instruction?

Answer: - Assistance is needed to understand the purpose of the destination (defaut cartes 53) and its relevance in the context of the RSLOGIX system.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’