LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ethernet/IP: ControlLogix Reports Bad Class with Demo.vi

Solved!
Go to solution

Downloaded Demo from...

http://forums.ni.com/ni/board/message?board.id=nilabs&message.id=279#M279

 

Which is just about exactly what I had tried on my cRIO (got "Invalid Segment Type" on the cRIO). So I punted and ran the demo on my PC.

 

Configured ControlLogix 1756-L55 (V16.03 Firmware) per the demo thusly...

 

 

Untitled.jpg

 

Yet as you can see Clx reports bad class. The Demo indeed sets the Assembly Instances to 100 and 101 via constants. There is nothing more to configure. What am I missing?

 

More Info:

1756-ENBT is Rev 4.3.2 @ 192.168.1.2

cRIO: 192.168.1.1

PC:192.168.1.199

NI Industrial Communications for EtherNet/IP: V1.2.0 (MAX shows it installed on cRIO target)

 

0 Kudos
Message 1 of 2
(3,107 Views)
Solution
Accepted by topic author S1ack

For future stabs in the dark...

 

PC-Wise:

For whatever reason. Deleting the Generic Ethernet Module, Re-adding to Controllogix project and re-downloading got it to work.

 

cRIO Wise:

My initial config had a Real (SGL), a DINT (I32), and a SINT (U8) bundled into a cluster, and then flattened into a 9 byte array. This was produced for ControlLogix on instance 100. A symmetrical instance 101 was consumed. When this executed on the cRIO - the ControlLogix reported an electronic Keying error - mismatched product code. Not exactly helpful (thanks Rockwell).

 

So I disabled keying everywhere I could - with no improvement.

 

On a whim I remove the SINT (U8) from the cluster, this changed the byte array to 8 bytes in length. I adjusted the size constants in LV and deployed. I adjusted the ControlLogix side accordingly and downloaded. It started working without issue?

 

Go figure. Someone at NI might want to look at that because I can't fathom a reason why you would need to limit a config to sending even numbers of  bytes.

 

0 Kudos
Message 2 of 2
(3,099 Views)