Updated to 3.10 on windows getting some exceptions in log file
Your device sends some invalid data, so it is something to worry about.
Ok thanks for info. But due to this, I am facing another problem, device status is blinking, I mean its turning green and again its, turning back to red. I think this is happening because of this reason.
I read somewhere I can configure timeout, does this problem can be solved with that or is this new behaviour?
It's like device is sending data and for the moment when server is reading new data it is green but soon after reading data it is going to red.
And I would like to donate some money(for a beer) let me know how where do to this.
No, timeout won't solve the problem. There is some issue with your device.
You can donate here:
done, cheers (Y)
Anton, this same device was working fine before upgrading to the new version, it's happening with almost all devices.
Devices are getting disconnected and connected automatically. Don't know how to fix it :X
It is probably just luck that devices worked properly before. I would recommend getting protocol documentation from vendor to check if it's expected behaviour.
Ok, testing on version 3.9 with same device and network operator, will send HEX messages from both servers after testing. I think there is something wrong with hex decoder itself.
What makes you think that?
that warning from the logs.
Are you sure you mean HEX decoder and not protocol decoder?
Anton, I don't know if there is anything wrong with protocol decoder or hex. Something is wrong in this new version. Need your help to get it fixed.
Here is how I can conclude this.
I have two different versions of traccar server running on two different IPs.
On first IP I have traccar version 3.9 running. And on 2nd IP I have running 3.10 version.
I took brand new device, configured it for tracking with first IP where I have 3.9 running, everything was working fine, it was green all the time when I was observing its behaviour.
Then, I changed device IP address to 2nd IP which is running version 3.10. It worked fine for less then 1 minute and went offline again.
One thing I noticed in both cases is that, when device was connected to 3.9 version server I sent command to device to check its GPRS status and it responded positive but in case of version 3.10 it closes down the GPRS on device too. I checked GPRS status by sending status command and it responded negative.
This means version 3.10 is closing down GPRS on device ( which does sound like impossible or server send some commands automatically to devices?).
One important thing to note here is that, although version 3.10 server shows gprs status disconnected but device location is being updated regularly.
Let me know if you need logs for more investigation. I am using H02 protocol on port 5013 (if that helps)
As far as I can tell so far, your device sends invalid data. If you think it's not a device issue, I would need protocol documentation for your device.
sent you protocol and manual document @gmail.
I have the exact problem with my GPS since i updated to 3.10.
*HQ,355488020977891,V1,000018,A,5734.42187,N,01205.36405,E,0.00,81,010615,FFFFFFFF#
Hi Anton,
Congratulations on the release of new version.
I am getting some exceptions in my log file like this.
Is there anything to worry about? I am not seeing anything on map in the dashboard, what could be the reason for this?