Hello,
We have the same device CRX3 Mini (GT06 protocol) with different behaviour based on server.timeout. We have set up and configured the device and server with same configuration except for this config on the traccar.xml file
Situation 1:
timeout = 60
Result: Experienced considerable amount of bandwidth used containing positions each 1min even when vehicle is stopped and configured to send data each 5 min
Situation 2:
timeout = 300
Result: Experienced less bandwidth used containing positions each 5min when vehicle is stopped and same configuration of Situation 1. Also we have noticed the device has frozen on a specific location for apx. 40 minutes and then returned to its functional behaviour
Situation: 3:
no timeout configured, default of Ubuntu 18.04 server
Result: Experienced same behaviour as "Situation 2"except for the "frozen behaviour"
We use currently the Situation 1 configuration but we experience an unfeasible usage of bandwidth for the device. Does someone has a suggestion for us to prevent excessive bandwidth spent and safely configure a timeout spec for gt06?
Not sure I understand how server timeout affects location frequency, but that's not how you are supposed to use it.
That's the thing. We have set up this configuration because we experienced this high frequency on gt06 devices on our servers which were on the Situation 1 so we wanted to compare with and without it. Then, we stated this variation.
We use server.timeout on this server primarily to control the open connections and spare resources but it ended up consuming too much M2M bandwidth causing us to investigate it deeper
It is probably consuming more because of the way your SIM card provider bills data. Some providers will have 1kb minimum. Others can have 10kb or more. It means that even if you only used 1kb in a single connection, you will be charged for 10kb. That means more frequent re-connects result in more used data.
Hello,
We have the same device CRX3 Mini (GT06 protocol) with different behaviour based on
server.timeout. We have set up and configured the device and server with same configuration except for this config on thetraccar.xmlfileSituation 1:
timeout = 60
Result: Experienced considerable amount of bandwidth used containing positions each 1min even when vehicle is stopped and configured to send data each 5 min
Situation 2:
timeout = 300
Result: Experienced less bandwidth used containing positions each 5min when vehicle is stopped and same configuration of Situation 1. Also we have noticed the device has frozen on a specific location for apx. 40 minutes and then returned to its functional behaviour
Situation: 3:
no timeout configured, default of Ubuntu 18.04 server
Result: Experienced same behaviour as "Situation 2"except for the "frozen behaviour"
We use currently the Situation 1 configuration but we experience an unfeasible usage of bandwidth for the device. Does someone has a suggestion for us to prevent excessive bandwidth spent and safely configure a timeout spec for gt06?