Parameters - Attributes send by GPS device but not received by Traccar

Hi,

Some parameters attributes, from Teltonika FMC640, are send by the device (as tested using the TCPListener log files) but are not received by Traccar. Actually, parameters io181, 182, 183, 184 were able to be received beforehand, but not anymore, whereas parameters io195 and io196 were never able to be received.

i.e. for parameter io184 (Driver 1 Working State) which is send by FMC640, while using the Traccar - computed parameters, it does not receive the parameter and gives the following error:

org.traccar.handler.ComputedAttributesHandler.computeAttribute@102![0,5]: 'io184;' undefined variable io184 - Variable (... < ComputedAttributesHandler:102 < AttributeResource:57 < ...)

and parameter io196 (Driver 1 ID LSB) which again gives the error:

org.traccar.handler.ComputedAttributesHandler.computeAttribute@102![0,5]: 'io196;' undefined variable io196 - Variable (... < ComputedAttributesHandler:102 < AttributeResource:57 < ...)

Can you please advice how can these parameters received by traccar?

Thanks

That's a question to Teltonika. You don't need to configure anything on the server side to receive them.

Andreas, how you set the parameters in FMC640 ?
If your settings is to send the parameters "On change" then you must set copy attributes in Traccar server config file. Otherwise computed attributes will working only when drivers really change.
Other options is to set IO196 as "Monitoring" then the device allways will send this parameter and Traccar will not calculate errors in log file.

Hello,

The parameters are set as monitoring. We can see the parameters using Flespi, but they do not seem to arrive on traccar.
I have contacted Teltonika support and their response was: "Since the device is successfully sending these AVLs to the platform as Flespi, there are no issues with the generation of these IDs from the device side. In this case, you would need to check if the Codec 8 protocol is correctly implemented on the server side."

In the link you can see the parameters received using flespi:
https://www.dropbox.com/s/4pvmfp298wmflf8/HEX%20Decoded%20Received.pdf?dl=0

Any support is very welcomed!
Thanks

It is implemented correctly. If you think it's not, please provide evidence, like a HEX breakdown.

Dear Anton,

Thanks for your reply.

The HEX breakdown, which if you decode, you will see that parameters 195, 195, 184 etc. are send from FMC640 and exist in the code:

[00000000000001618E02000001872BE129B50113E0CC8814F0743000D000BE09001D00B8000B0001001F2B0005271903E8006C10090023040A001903AC008F000000030021000B470D00240A90276B000C00002F70000200D90000000000000000000D006D00B70E2030300000000001872BE129B40113E0CC8814F0743000D000BE09001D00B8002F001100B70100BA0000B80300BB0100BD0000DE0B00300329050F290600290E0000160500470300F00100150400B20200C80000EF01000E00BF001C00380082003A0000003C000000450809290B0082290C0298290D02BD004325F80044003300B5000C00B60008004268D50018001C000B00C26423CF1F00C00A90276B00C1003EB0D92907666E2B0029086423A05029096420FE40290A6417CF0000C70000CE2C00F100006D6A004C0000000000D800E9782B000300C4303032583930303000C3323030303030303000CF0000000000000000000229160001072917000107020000E580]

Please advice.

I see the HEX, but where's the breakdown?

Hi Anton,

The HEX breakdown, (the decoding of a HEX code) can be found on this link here:
https://www.dropbox.com/s/4pvmfp298wmflf8/HEX%20Decoded%20Received.pdf?dl=0

where you can see that the device sends parameter id195 as: 3474589996675200560 and id196 as: 3544385890265608240 etc.

Please let me know, if you need the HEX breakdown in any other form.

Thanks

I just tested your sample locally and I do get all those parameters in Traccar.

Hi,
This is good news! However I cannot receive it on the traccar on our server.
This see error: https://www.dropbox.com/s/sykljwtaxbb3wwg/io196error.JPG?dl=0

Is there any setting that I have done wrong or missing in order to see these parameters? Please note that parameters id183, id184 etc I can receive them very rarely on traccar, and as mentioned before parameters id195 and id196 never.

Thanks for the support!

Your sample has two messages inside. One of them does have the attributes and the other doesn't. If it's not included in every message, it's expected that it might be failing if the one you're looking at doesn't have it.

Hm, I am a bit confused now.

You mean that FMC640 tracker sends two messages (with hexadecimal codes) every time, one with the parameters and the other without them?
or I have understand it wrong?

Is this a setting that has to be solved by Teltonika support correct?

Thanks a lot for the support.

You understood correctly. You can even see it in your breakdown PDF. If that's not what you want to happen, probably contact Teltonika.

To be honest I am confused with how I can identify in the breakdown PDF the fact that there are 2 messages.

Anyway, I will contact Teltonika for support on this, hoping that they can assist in sending the required HEX data that can be received as expected by traccar.

Thanks!

You have two "AVL data" elements there, each with their own GPS info and additional parameters.