Fuel Increase Notification Issues
prova ora dovrebbe andare
It says FMA120 protocol, not FMB.
This is precisely the problem.
Initially, it was thought that for the CANBUS part, FMA and FMB were identical in terms of both IDs and multiplier values.
Then, as you suggested, I spoke with the CANBUS manufacturer, who knew how the values were provided—1:1 with a precision of 0.1, for example, 50.0—but didn't know how Teltonika had defined the IDs.
Contacting Teltonika, they clarified that FMA could have different IDs and multipliers. In fact, by providing the FMA protocol, it was clear that specifically, the ID is the same for io83, io84, io107, and io110, but the multiplier is different. For ENGINE OIL and CNG, the IDs are different.
io83 LVCAN Total fuel used in liters multiplied by 10, L*10 Fuel level
io84 (liters) Value in liters, L
io107 LVC Fuel consumed (counted) Total fuel consumed, liters * 10
io110 LVC Fuel 2 Fuel, liters *10
FMA io190 CNG Status / FMB io232 CNG Status
FMA io191 CNG used / FMB io233 CNG used
FMA io192 CNG Level / FMB io234 CNG Level
FMA io193 Oil Level / FMB io235 Oil Level
So if you currently use Traccar and enter "FMA" on the device, it sees it as FMB and therefore the values are incorrect.
This should fix the problem:
https://github.com/traccar/traccar/commit/671118d814ee214b40f55b45f17895eb0af5e8d0
I think we need to exclude all FMA devices before those are legacy ones.
non penso sia la soluzione giusta se fosse cosi dovremmo escludere anche FM che e' obsoleto e a breve sara anche FMB.
Penso si piu' corretto far riconoscere se mettiamo FMA gli id corretti con i relativi moltiplicatori
Can you please provide some evidence beyond just your thoughts.
I say this because I spoke with the sales manager who supplies us with the devices.
I can also confirm this from their EOL Product
https://www.teltonika-gps.com/support/eol-products
As you can see, the FMB120 replaced the FMA120 and other similar devices.
The FMA120 and FMB120 are identical except for Bluetooth.
They discontinued production of the FMA because the market had developed Bluetooth accessories.
At the time, they had sold an excessive number until 2021.
So, there are thousands of FMAs in circulation today.
I personally have 500-600 of these that work great.
I thought I understood that the old models should be kept for compatibility, and I think that's correct.
I'm not arguing that FMB devices might be discontinued. The evidence I need is that something is not decoded correctly after my fix.
So if we add FMA, they'll be encoded.
Okay, I'll do some tests and update you.
Thanks
All devices will be decoded, but not all IO values.
As I imagined and said, even looking at the code, FMA has been removed from the advanced conversion, including CANBUS, cell ID, etc.
Essentially, it's like having the encoding only for very old devices.
As I reiterated, I don't find the correct solution because, as I said, only some multipliers of the same ID are different, as I specified (ID83, ID84, ID107, ID110), which have a multiplier of 1 instead of 0.1.
Essentially, we've gone back to version 6.5.
OK.
It is not possible to find a solution to have the advanced part of the FMAs decoded correctly, which have been excluded to date.
Why not? You can always use computed attributes.
No access.