Quantcast
Channel: Allen Bradley / Rockwell Automation Latest Topics
Viewing all articles
Browse latest Browse all 3755

Understand service data

$
0
0

I have 0x4c requests from my ipc to the controller, with request path: Class - 0xB2, Instance - 0x004C.

And 0x4c responses from the same path, and then "Command Specific Data":

example 1 (of the command specific data):

0100a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00a6409d00

example 2:

0100a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00a7409d00

example 3:

0100a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00a8409d00

Looks like it always starts with 0100, then repeating some value. In the first one the repeating value is 00a6409d, and then in the end 00. Or maybe it's 01 and then just repeating values surrounded with 00 or something similar.

Is it values surrounded with 00, written using little-endian?

Does the variable in request have a name?

 


Viewing all articles
Browse latest Browse all 3755

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>