mapping issue FMC650 TRACCAR 6.11
Please link to the documentation.
Reverted the mapping for those.
Hi Anton, I'm willing to step up and own this problem if it helps, since our business uses teltonika hardware exclusively. I previously reached out via Teltonika helpdesk to ask about the parameter differences across the entire teltonika product set and they told me "they don't have one single repository", which made me pull my hair out, but with enough time the data can be found.
For example, Teltonika kindly wrote one for the difference between FM and the new FT series:
https://wiki.teltonika-gps.com/view/AVL_ID_differences_between_FMB_and_FT_platforms
I should add, for context, and as a Teltonika user - I do not believe that Traccar should be responsible for mapping all of the Teltonika attributes. My view is:
- Only common, or "used by a large percentage of teltonika + traccar users" attributes should be automatically mapped.
- Other attributes should be handled as Computed Attributes
For the endless list of potential computed attributes for Teltonika devices - and the associated JEXL to make them work - a repository of these can be maintained, by the community, rather than the Traccar developers. If that means a github repo elsewhere, then so be it. We would be happy to host this in our github account.
For Khaled, and for the rest of the community, the deeper you go with attributes that are not exposed in Traccar, the more work you may need to put into the code. By this I mean:
- Traccar has a limited set of Notification types and Alarms: New notification names and alarm names means getting into the code to create these.
- Traccar has a limited set of built-in attributes: You can create an unlimited number of Custom Attributes but they don't appear in drop-down selection boxes in all parts of the GUI. In some areas of the GUI you just have to type the attribute name and make sure you typed it correctly.
If you want to help with mapping, that's always welcome.
Hello,
I would like to report an issue with the FMC650 device integration. Currently, FMC650 is treated as fmbXXX because of the condition m.startsWith("FM") in TeltonikaProtocolDecoder.java (line 197).
As a result, IO elements such as:
io233 (Vehicle Identification Number Part1 – 8 bytes)
io234 (Vehicle Identification Number Part2 – 8 bytes)
are incorrectly mapped to cngStatus and cngUsed, which should only apply to FMC150 models. For FMC650, these IOs should represent VIN parts instead.
Could you please review this logic and confirm if an update can be implemented to differentiate FMC650 from FMC150?
Thank you for your support.
Khaled