[Magnus Hansson <mah.mailinglist@xxxxxxxxx>]

Hello,

These service codes does not only need to be class specific, they also need to be vendor specific. The classes that use the listed services are vendor specific and in this case defined by Allen-Bradley, other vendors could use the same service codes for other purposes in their own objects using the same class number.

Information about vendor is not present in the telegram so I'm not sure how this could be added.

Best regards
Magnus Hansson

Jaap Keuter skrev:

Hi,

Question: in which class do these SC's fall? Looking at the currently
implemented SC's:
0x03 = "Get Attribute List"
0x0A = "Multiple Service Packet"
0x4E = "Forward Close"
0x52 = "Unconnected Send"

So the CIP dissector needs to become class aware first IMHO.

Thanx,
Jaap


On Thu, 12 Jan 2006, Gordon Stewart wrote:

  

Allen Bradley defines the following Service Codes for Logix5000 Data Access
in the Common Industrial Protocol.

0x03 - Multi-request service
0x0A - Get Attributes list service
0x4B - Execute PCCC Service
0x4C - CIP Read Data Service
0x4D - CIP Write Data Service
0x4E - RMW (Read/Modify/Write) Service
0x52 - CIP Read Data Fragmented Service
0x53 - CIP Write Data Fragmented Service

These Service codes are documented the the Logix5000 Data Access manual
Publication 1756-RM005A-EN-E-March 2000

Except the Execute PCCC and RMW services are documented in
Communicating with RA Products Using EtherNet/IP Explicit Messaging
(Rev. 1.2), Appendix C

If anyone has the time or inclination it would be great to get these
service codes added
to the CIP dissector.

Gord Stewart
Porter Engineering Ltd.
Email: gord@xxxxxxxxxxxxx
    

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev