RealDash CAN XML startbit method and endianess

Connectivity RealDash CAN
1

@realdashdev the Mazda canbus I am working on is big endian, but the results I got using startbit trialling both endians left me a little confused; both bits were set, so should have resulted in 3, which the little endian version did, but the big endian version gave me 1. Does RealDash amend the direction of the startbit location based upon the endianness i.e. aligned with the DBC format?

RealDash

value name=“MZ: ccs_le” startbit=“1” bitcount=“2” endianess=“little” signed=“false”
value name=“MZ: ccs_be” startbit=“2” bitcount=“2” endianess=“big” signed=“false”

DBC

SG_ ccs_le : 1|2@1+ (1,0) [0|0] “” Vector__XXX
SG_ ccs_be : 2|2@0+ (1,0) [0|0] “” Vector__XXX

1 Like
2

Thank you for reporting, will investigate.

3

@realdashdev hi, just wondering if you managed to look at this

4

Not yet, its on todo list though.

1 Like
5

It seems like whenever startbit/bitcount is used, its always interpreted as little endian by RealDash XML parser.

6

That was my conclusion also, which explains why I was unable to do anything with multi byte data using this method earlier

7

Hi @realdashdev just wondering if there are any plans to correct this?

8

I was thinking about it, but I think risk of breaking something that already uses a workaround for that is maybe too big.

9

@realdashdev noted, but perhaps it should then be clarified the process of uploading a DBC file to Garage for conversion to XML will not work for big endian unless its single bits