When looking at the bits in the message visualization, they are shown backwards when in little endian mode. When I enter bits 0 and 1 in byte 1, I see the first 2 bits from left to right labled as 0 and 1 becoming filled. The problem is that the actual CAN message has the real bits 0 and 1 filled, which are the first 2 bit from right to left.

In other words, what I see visually in the message visualization in the configurator is only valid if the big endian box is checked. There is no change to the visualization when the box is checked, but the actual CAN message is certainly changed.

By default, the byte-ordering is Little Endian (least-significant byte first). Checking the Big Endian box will change the byte-ordering so that the most-significant byte is first (where the leftmost byte is ‘first’).
This setting only applies at the byte level, and does not change the bit-ordering within a byte.

Are you seeing the two-bit variable packing change position within the byte on the CAN bus depending on the Big Endian setting? If so, that is definitely unintended since the Big Endian setting should only affect byte-ordering.


Known Issue:
The Message Visualization in the configuration tool doesn’t match the bit-ordering typically displayed in CAN diagnostic tools.
The bytes in the Message Visualization are displayed from least-significant bit to most-significant bit, while most CAN diagnostic tools typically display each CAN byte from most-significant bit to least-significant bit.
However, the bit numbering between the Message Visualization and the actual CAN packet will match, even though the Message Visualization appears that it is transposing the bit positions.

In the next release, we plan on addressing the disconnect between the Message Visualization and how CAN bytes are typically displayed in CAN diagnostic tools and generally cleaning up the Message Visualization so that it adds clarity while creating Free-Form CAN messages.