juleq

Was probably me. Was on a wrong branch. The right one for me required

Reopening because I have another platform (lpc1768) that requires a >= 1.6.x toolchain, pio resolves to 1.9.x and that does not seem to be available for linux_arm7l. Since I am...

You are misunderstanding scaling. Scaling for a choice value is usually offset=0, factor=1 but _it does exist_.

With respect to the backslash formatting: @eerimoq as the BDFL did a good job demanding consistent formatting throughout the code base. I would argue that good citizenship would include adherence...

Did you get my other point? Scaling is almost always true. Only in a very specific circumstance, when the user wants to have the raw value, he can opt to...

Vector does it the same. The spec tells you that value tables deliver descriptions for raw values. But nothing would stop you from defining e.g. a factor of 2 even...

Problem 1 is not a problem. CANdb++ in its standard setting will display the start of a signal different from what the representation in the dbc file looks like. You...

Yes. Further, since you are already debugging, you could inspect the dbc_specifics object. You should find the attribute GenSigStartValue associated with your signal in the attributes there. If so, the...

Try this function to convert the start bit representation from dbc to CANdb++. It is C# but easy to adapt: ``` private static uint GetStartBitInVectorCANdbppStyle(Signal signal) { uint startbit =...

The dbc does contain an attribute definition for the signal type (SG_) that is of value type FLOAT and has a default value of 0. However, there is no signal...