Bug in Flespi protocol for large decimal numbers?

MO-Paul

Hi Flespi team,

I'm encountering something strange with the Teltonika FMC640. I'm using the manual CAN bus input, where I have selected several messages to log in it's entirety (all 8 bytes).
It seems that the Teltonika FMC640 uploads this data as decimal numbers. However, in Flespi, these numbers do not arrive identically. Examples:

Decimal number 18446744073709551615 is received in field MANUAL.CAN.1 as decimal number 18446744073709500000 (notice the difference in the last 5 digits).

Decimal number 3472896760919512129 is received in field MANUAL.CAN.2 as decimal number 3472896760919510000 (notice the difference in the last 4 digits).

However, when the original number is small, it does work. Example: Decimal number 39911424 comes over ok.

Do you know what's going on? And more importantly: is there a quick way to fix this?

Kind regards,
Paul

baja

MO-Paul , this is caused by a known problem that json can't hold number that exceeds 53 bits. With this protocol update we've added indexed manual.can.hex parameter for every Manual CAN field. It is string in HEX representation, so no data would be missed.
You may check this article to see how to extract desired bits or bytes from such values with PVM plugin.

Or just start from this code sample

optional .manual.can.hex.1 ==> %hexstr ==> $can_serial_1
optional .manual.can.hex.4 ==> %hexstr ==> $can_serial_4
format["%s%s", $can_serial_1, $can_serial_4] ==> #can.serial.number

optional .manual.can.hex.0 ==> %hex ==> bits:
	16 ==> skip
	16 ==> #can.engine.load // for example

optional .manual.can.hex.2 ==> %hex ==> bits:
	1 ==> %boolean ==> #can.somewhat.flag.1
	1 ==> %boolean ==> #can.somewhat.flag.2