CINF message and byte order of SupportedMSEXVersions ...

Bits and byte level questions, ideas and suggestions for the CITP protocol.
Lao
Posts: 3
Joined: Mon Oct 22, 2012 1:55 pm

CINF message and byte order of SupportedMSEXVersions ...

Postby Lao » Sat Feb 02, 2013 5:35 am

How shoul i read incoming Cinf message and byte order of SupportedMSEXVersions. According specification this is uint16 and LSB=minor version and MSB=major version and byte order in structures should be little-endian. But this is a incoming network packet and i expext that uint16 coming in network byte order? Or Not? This question is because now i have two lighting desk - MagicQ and GrandMA2 sending Cinf with different order of bytes. May be easier to redeclare uint16 variable as structure of two bytes?

User avatar
lasso
Site Admin
Posts: 72
Joined: Sat Sep 25, 2010 7:44 am
Location: Gothenburg, Sweden
Contact:

Re: CINF message and byte order of SupportedMSEXVersions ...

Postby lasso » Sun Feb 03, 2013 8:16 pm

Hi Lao,

As according to section 2.1 - Data types, all fields are little endian - not network byte order. Once in the memory of the application, the MSB carries the major version and the LSB the minor version of the support MSEX versions.

So in this case, the first incoming byte is the minor version and the second incoming byte is the major version.
Lars Wernlund
Technical Manager, Capture Sweden


Return to “Design - For developers”

Who is online

Users browsing this forum: No registered users and 2 guests

cron