Cisco switch to Controllogix communications

[Michaelb]

Hello all,
Just posting to see if anyone is aware of ways to get the switch status from a Cisco switch. Of course we all know that Stratix works.....
More specifically we use Cisco IE4010 switches and L81E PLCs
Thanks,
Mike

 

[PreLC]

Not familiar with this switch, but, does it have a CIP object associated with it?

Can you try typing the gateway/configuration IP address into RSLinx and see if it is a visible device? That might let you at least find out if it's possible to maybe create a generic object?

On ODVA's website, this switch does have an EDS file associated with it. If you can add this on the PLC tree and then doing a GSV, or even just do a message(After looking into what messaging capabilities are present) you should be square.

Regards,
-PreLC

 

[Michaelb]

I did indeed find the EDS files for the IE 4010(Rack mount) and the IE4000 on the ODVA wesite.
This is all great but is there any documentation on what is available once the switch is in the hardware tree?
Like and assembly and instance type document?

Mike

 

[PreLC]

Like and assembly and instance type document?

Mike

I signed up on Cisco.com, but there are no documents of this exact type available. There are CIP troubleshooting guides, but no guides on the PLC-Switch interaction.

I then also tried adding the CIP Object to the PLC tree, that yielded better results. The tags already had names on them, I don't claim to understand what all of them mean, but that has a lot of information already. Also, before adding the module to the tree, while adding the module, there are options to change the object size for more module defined tags.

The next step might be to get with Cisco on that, due to a lack of available documentation.

 

[Michaelb]

I have also added the IE-4010 into the hardware tree but I get generic tagging as follows:
Cisco:I1.Data[0]
Cisco:I1.Data[1]
etc.....
Did you get actual names?

Mike

 

[PreLC]

For inputs and outputs, no, but for the config tags, I did get exact names:

TestSwitch:C
TestSwitch:C.Gi1_1_Fault_Action
TestSwitch:C.Gi1_2_Fault_Action
TestSwitch:C.Gi1_3_Fault_Action
TestSwitch:C.Gi1_4_Fault_Action
TestSwitch:C.Gi1_5_Fault_Action
TestSwitch:C.Gi1_6_Fault_Action
TestSwitch:C.Gi1_7_Fault_Action
TestSwitch:C.Gi1_8_Fault_Action
TestSwitch:C.Gi1_9_Fault_Action
TestSwitch:C.Gi1_10_Fault_Action
TestSwitch:C.Gi1_11_Fault_Action
TestSwitch:C.Gi1_12_Fault_Action
TestSwitch:C.Gi1_13_Fault_Action
TestSwitch:C.Gi1_14_Fault_Action
TestSwitch:C.Gi1_15_Fault_Action
TestSwitch:C.Gi1_16_Fault_Action
TestSwitch:C.Gi1_17_Fault_Action
TestSwitch:C.Gi1_18_Fault_Action
TestSwitch:C.Gi1_19_Fault_Action
TestSwitch:C.Gi1_20_Fault_Action
TestSwitch:C.Gi1_21_Fault_Action
TestSwitch:C.Gi1_22_Fault_Action
TestSwitch:C.Gi1_23_Fault_Action
TestSwitch:C.Gi1_24_Fault_Action
TestSwitch:C.Gi1_25_Fault_Action
TestSwitch:C.Gi1_26_Fault_Action
TestSwitch:C.Gi1_27_Fault_Action
TestSwitch:C.Gi1_28_Fault_Action
TestSwitch:C.pad_byte1
TestSwitch:C.pad_byte2
TestSwitch:C.pad_byte3
TestSwitch:C.pad_byte4
TestSwitch:C.pad_byte5
TestSwitch:C.pad_byte6
TestSwitch:C.pad_byte7
TestSwitch:C.pad_byte8
TestSwitch:C.pad_byte9
TestSwitch:C.pad_byte10
TestSwitch:C.pad_byte11
TestSwitch:C.pad_byte12
TestSwitch:C.pad_byte13
TestSwitch:C.pad_byte14
TestSwitch:C.pad_byte15
TestSwitch:C.pad_byte16
TestSwitch:C.pad_byte17
TestSwitch:C.pad_byte18
TestSwitch:C.pad_byte19
TestSwitch:C.pad_byte20
TestSwitch:C.pad_byte21
TestSwitch:C.pad_byte22
TestSwitch:C.pad_byte23
TestSwitch:C.pad_byte24
TestSwitch:C.pad_byte25
TestSwitch:C.pad_byte26
TestSwitch:C.pad_byte27
TestSwitch:C.pad_byte28
TestSwitch:C.pad_byte29
TestSwitch:C.pad_byte30
TestSwitch:C.pad_byte31
TestSwitch:C.pad_byte32
TestSwitch:C.pad_byte33
TestSwitch:C.pad_byte34
TestSwitch:C.pad_byte35
TestSwitch:C.pad_byte36
TestSwitch:C.Gi1_1_Idle_Action
TestSwitch:C.Gi1_2_Idle_Action
TestSwitch:C.Gi1_3_Idle_Action
TestSwitch:C.Gi1_4_Idle_Action
TestSwitch:C.Gi1_5_Idle_Action
TestSwitch:C.Gi1_6_Idle_Action
TestSwitch:C.Gi1_7_Idle_Action
TestSwitch:C.Gi1_8_Idle_Action
TestSwitch:C.Gi1_9_Idle_Action
TestSwitch:C.Gi1_10_Idle_Action
TestSwitch:C.Gi1_11_Idle_Action
TestSwitch:C.Gi1_12_Idle_Action
TestSwitch:C.Gi1_13_Idle_Action
TestSwitch:C.Gi1_14_Idle_Action
TestSwitch:C.Gi1_15_Idle_Action
TestSwitch:C.Gi1_16_Idle_Action
TestSwitch:C.Gi1_17_Idle_Action
TestSwitch:C.Gi1_18_Idle_Action
TestSwitch:C.Gi1_19_Idle_Action
TestSwitch:C.Gi1_20_Idle_Action
TestSwitch:C.Gi1_21_Idle_Action
TestSwitch:C.Gi1_22_Idle_Action
TestSwitch:C.Gi1_23_Idle_Action
TestSwitch:C.Gi1_24_Idle_Action
TestSwitch:C.Gi1_25_Idle_Action
TestSwitch:C.Gi1_26_Idle_Action
TestSwitch:C.Gi1_27_Idle_Action
TestSwitch:C.Gi1_28_Idle_Action
TestSwitch:C.pad_byte37
TestSwitch:C.pad_byte38
TestSwitch:C.pad_byte39
TestSwitch:C.pad_byte40
TestSwitch:C.pad_byte41
TestSwitch:C.pad_byte42
TestSwitch:C.pad_byte43
TestSwitch:C.pad_byte44
TestSwitch:C.pad_byte45
TestSwitch:C.pad_byte46
TestSwitch:C.pad_byte47
TestSwitch:C.pad_byte48
TestSwitch:C.pad_byte49
TestSwitch:C.pad_byte50
TestSwitch:C.pad_byte51
TestSwitch:C.pad_byte52
TestSwitch:C.pad_byte53
TestSwitch:C.pad_byte54
TestSwitch:C.pad_byte55
TestSwitch:C.pad_byte56
TestSwitch:C.pad_byte57
TestSwitch:C.pad_byte58
TestSwitch:C.pad_byte59
TestSwitch:C.pad_byte60
TestSwitch:C.pad_byte61
TestSwitch:C.pad_byte62
TestSwitch:C.pad_byte63
TestSwitch:C.pad_byte64
TestSwitch:C.pad_byte65
TestSwitch:C.pad_byte66
TestSwitch:C.pad_byte67
TestSwitch:C.pad_byte68
TestSwitch:C.pad_byte69
TestSwitch:C.pad_byte70
TestSwitch:C.pad_byte71
TestSwitch:C.pad_byte72
TestSwitch:C.Power_Sources_present
TestSwitch:C.Power_Source_A_Present
TestSwitch:C.Power_Source_B_Present
TestSwitch:C.UndefinedData
TestSwitch:C.Base_module
TestSwitch:C.Expansion_module_1
TestSwitch:C.Expansion_module_2
TestSwitch:C.Password_Check_I_O_config
TestSwitch:O1
TestSwitch:O1.Data
TestSwitch:I2
TestSwitch:I2.ConnectionFaulted
TestSwitch:I2.Data
TestSwitch:I1
TestSwitch:I1.ConnectionFaulted
TestSwitch:I1.Data

 

[Michaelb]

Yes same here for the config tags. I guess I will have to sift through the EDS file to come up with what useful input data is available.
Quick glance tells me that you can get faulted and connected port status.
Thanks again,
Mike

 

[mk42]

A protocol called SNMP is often used on the IT side to get data out of switches. I've done it in Siemens with a provided libary, but no idea if sample code is available for Logix.

 

[PreLC]

A protocol called SNMP is often used on the IT side to get data out of switches. I've done it in Siemens with a provided libary, but no idea if sample code is available for Logix.

Tried to look into the Rockwell literature section, no code available...

But for this switch, we should be able to add it on the controller tree and do a GSV to get the module status, apart from being able to use the .ConnectionFaulted bit.