Andreas Lauser

I had the same problem and your patch made it work perfectly. thanks! can you open a pull request to avoid having it to apply manually? @ThomasWaldmann: I suppose that...

cantools only supports those parts of ARXML that deal with CAN frame descriptions (i.e., the in stuff described by CAN-FRAME-TRIGGERING elements). Support for this should be pretty robust by now,...

> 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...

hm, I'm not opposed to this per-se, but I suppose the cantools ought to be split into a "core" and "fringe" tools in the future where the code generators would...

> hope that's ok (?) no problem. I just wanted to inform you that the chances of getting something like this merged are rather slim with the current monolithic repository...

> now - 0 might not actually be in the valid range for a given signal, You could add a [` VALGRIND_MAKE_MEM_UNDEFINED` valgrind client request](https://valgrind.org/docs/manual/mc-manual.html#mc-manual.clientreqs) to mark the object as...

as far as I'm aware, that's not possible out of the box. That said, it should not be too difficult to write your custom code generator for the particular language...

@juleq probably wanted to say that we would appreciate if you boiled down your DBC file to something which shows the problem and that can be shared freely (i.e., containing...

I also agree in principle, but I'm not sure if an overflow can actually happen here because when converting physical (float) to internal (integer) values, the physical values need to...

> @andlaus Can still overflow. even if the value of the physical signal is in range [signal.minimum, signal.maximum]?