Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations MintJulep on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Getting 1756-CNB diagnostics through CIP

Status
Not open for further replies.

panoskart

Automotive
Oct 30, 2009
4
I am new in the PLC programming stuff and I am working with an AB PLC Logix5000 series. I am trying to access the diagnostics of the ControlNet module through a cip message in order to monitor some alarms in case of a network problem. I have found some references up to now but they dont seem to work..Please see the attached picture for the configuration of my MSG command (the path is to the CNet module). The fault that I get is '16#005 no connection' and ' wrong class or attribute'. In the source tag I have set the 0000000400 in a Dint and 02 in an INT. In addition is there a similar way to get diagnostics for the PLC processor in case of a fault? Any help is appreciated. Thanks
 
Replies continue below

Recommended for you

Try this for a test. Also what parameters are you trying to get with your msg? For the example below create a UDT with the following;
SMAC_Version = SINT
Station_Status = INT
Vendor_Specific = SINT
LED_Status = SINT

Then create a tag channel_status of the UDT data type above.

Also is the controlnet network connected when you are testing you msg? I know some will fail is the network is not connected.

SERVICE CODE: E SOURCE: Leave blank
OBJECT TYPE: F0 NUM OF ELEMENTS: 0
OBJECT ID: 1 DESTINATION: Channel_Status (Tag you created)
OBJECT ATTRIBUTE: 83


Newer message layout (Logix revs 10 + )
Service Type = Service Code
Class = Object type
Instance = Object ID
Attribute = Object Attribute

Under the Communications tag, put in the path to your CNB module or ControlNet device. (e.g. 1,2 (Backplane, Slot 2))

Then click APPLY.


Channel_Status.SMAC_Version is the version of the SMAC chip in the device.


The LED STATUS is layed out as follows:

The first 3 bits of Channel_Status.LED_Status contain the Status of Channel A on the device:
(bits 0,1,2)
0 = OFF
1 = SOLID GREEN
2 = Flashing GREEN-OFF
3 = FLASHING RED-OFF
4 = FLASHING RED-GREEN
5 = RAILROAD RED-OFF (ALTERNATING between ChA and ChB)
6 = RAILROAD RED-GREEN (ALTERNATING between ChA and ChB)
7 = SOLID RED


The bits 3-5 represent the Status of Channel B on the device:
(bits 3,4,5)
0 = OFF
1 = SOLID GREEN
2 = Flashing GREEN-OFF
3 = FLASHING RED-OFF
4 = FLASHING RED-GREEN
5 = RAILROAD RED-OFF (ALTERNATING between ChA and ChB)
6 = RAILROAD RED-GREEN (ALTERNATING between ChA and ChB)
7 = SOLID RED

Bit 6 is the REDUNDANCY WARNING
0 = NORMAL
1 = WARNING

Bit 7 is the ACTIVE CHANNEL
0 = CHANNEL B
1 = CHANNEL A


 
Panoskart were you able to successfully complete the msg?
 
Hi jde777

Sorry but I just saw the messages..Thanks for replying. Actually the panel were taken from me for function test so I wont have the chance to test that till Monday. The info that I try to retrieve with the msg are simple ControlNet diagnostic alarms for my HMI, so for example if the line is down or one of the nodes is faulted thus the CNet will be down as well. I had a try with the GSV command (Module/Fault code) and I got a code of 335 or smth when I unplug one node which I use as a temporary solution but I dont quite like this approach since I dont know what this code stands for..Do you have any info of a list of faults-codes?
 
Controlnet is unlike devicenet in that all the modules fault data can be obtained directly from the modules predefined tags in rslogix 5000. So you can write your alarm/fault code utilizing each modules predefined fault data tags in rs5k. You also can use a msg or gsv to each module to get fault info but most of the time it is already there in the tags.
If you are specifically speaking of just cnb's status then yes a message or gsv will have to be used.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor