ASPEP - help to interpret telegram on BEACON message as example

[j-fischer-gundlach]

I´m not 100% sure how to interpret and thereby implement ASPEP on an own controller to talk to the performer

So I want to ask if someone can tell if I´m on the right way on the example of the BEACON message

The documentation says least significant bits are send first and the BEACON message is

I recorded the inital traffic when connecting the Motor Pilot and the first message is

I currently think to fit this reording in the documented scheme, I have to "mirror the bytes around the vertical axis", so fittet in the scheeme the message would be
10100000 11100011 10000000 00101000
?

If that is correct, what suprises me is that the CRC bit is zero indicating no crc is supported by the performer, but somehow the last 4 CRCH bits are not zero. 

[GMA]

Hello @j-fischer-gundlach,

Refer to Motor Control Protocol Suite chapter of User Manual documentation available through "Workbench tool">About>Documentations>Documentation>"User manual" tab. 
The 4-bit CRCH field contains the result of a cyclic redundancy check computation performed on the first 28 bits of the header.
CRC bit indicates supports for computing a CRC on the payload of ASPEP packets.