Command Endianness and Parameter Endianness

[jtlobdell]

Does COSMOS support parameter-specific endainness? Example: a command is big endian and has 4 parameters of which the last two are little endian.

Looking at packet_item_parser.rb (specifically get_usage and get_endianness) it seems like this is supported. I did a basic test of modifying the demo cmd config like get_usage shows (just adding LITTLE_ENDIAN after the parameter description), sending the command and viewing the raw command packet but I see no indication that the endianness is actually different.

If it isn't a feature then I'm going to take a stab at implementing it.

If it is already a feature then:
--It is undocumented, at least on the "Command and Telemetry Configuration" page
--Whether it is working is not obvious
--I didn't see any tests for this (to be fair I didn't dig for more than a minute)

[ghost]

It is supported.
It is undocumented (will leave this ticket open until that gets fixed).
It is tested (see packet_item_parser_spec.rb lines 136 and 270)

If it is not working for some specific case please let me know.

[donaldatball]

@ryanatball @jasonatball - I added documentation of the endian parameter to all the item/parameter keywords in the cmd/tlm section of the website. I think that is all that needed to happen for this ticket.

Someone want to review the changes?

[ghost]

Looks good. 👍

[donaldatball]

Closed with website updates only (2971e24)