Repeated locations tracker J16

Lucas Bezerra8 months ago

Hello, I have a J16 tracker version J16-MASCSA-B38 2023-06-10-1 V4.41 which I am having problems with repeated positions with the ignition off, as shown in the log!

2024-04-11 12:41:11  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a13450604000100827bf60d0a
2024-04-11 12:41:11  INFO: [T6b740ed5: gt06 > 187.60.53.254] 7878051300825f620d0a
2024-04-11 12:41:11  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:41:21  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004f6008394b30d0a
2024-04-11 12:41:21  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:44:11  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a13450604000100841ec00d0a
2024-04-11 12:44:11  INFO: [T6b740ed5: gt06 > 187.60.53.254] 7878051300843a540d0a
2024-04-11 12:44:11  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:44:21  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004ec0085076a0d0a
2024-04-11 12:44:21  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:47:11  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a13450604000100863dd20d0a
2024-04-11 12:47:11  INFO: [T6b740ed5: gt06 > 187.60.53.254] 78780513008619460d0a
2024-04-11 12:47:11  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:47:21  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004ec008724780d0a
2024-04-11 12:47:21  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:50:12  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a1345060400010088d4ac0d0a
2024-04-11 12:50:12  INFO: [T6b740ed5: gt06 > 187.60.53.254] 787805130088f0380d0a
2024-04-11 12:50:12  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:50:22  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004f600893be90d0a
2024-04-11 12:50:22  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 11:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:52:08  INFO: [T6b740ed5: gt06 < 187.60.53.254] 7878262218040b0c3404c9008538e7043efb280018ef02d40297d6001001000000000000c8008a10b20d0a
2024-04-11 12:52:08  INFO: [T6b740ed5: gt06 > 187.60.53.254] 78780522008a0f580d0a
2024-04-11 12:52:08  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:53:12  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a134506040001008be6370d0a
2024-04-11 12:53:12  INFO: [T6b740ed5: gt06 > 187.60.53.254] 78780513008bc2a30d0a
2024-04-11 12:53:12  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:53:22  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004ec008c9aab0d0a
2024-04-11 12:53:22  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:56:12  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a134506040001008d83010d0a
2024-04-11 12:56:12  INFO: [T6b740ed5: gt06 > 187.60.53.254] 78780513008da7950d0a
2024-04-11 12:56:12  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:56:22  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004ec008eb9b90d0a
2024-04-11 12:56:22  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:59:12  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a134506040001008fa0130d0a
2024-04-11 12:59:12  INFO: [T6b740ed5: gt06 > 187.60.53.254] 78780513008f84870d0a
2024-04-11 12:59:12  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 12:59:22  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004f60090b6a90d0a
2024-04-11 12:59:22  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 13:02:12  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a134506040001009159ec0d0a
2024-04-11 13:02:12  INFO: [T6b740ed5: gt06 > 187.60.53.254] 7878051300917d780d0a
2024-04-11 13:02:12  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 13:02:22  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004f6009295bb0d0a
2024-04-11 13:02:22  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 13:05:12  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a13450604000100937afe0d0a
2024-04-11 13:05:12  INFO: [T6b740ed5: gt06 > 187.60.53.254] 7878051300935e6a0d0a
2024-04-11 13:05:12  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 13:05:22  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004f60094f08d0d0a
2024-04-11 13:05:22  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 13:08:12  INFO: [T6b740ed5: gt06 < 187.60.53.254] 78780a13450604000100951fc80d0a
2024-04-11 13:08:12  INFO: [T6b740ed5: gt06 > 187.60.53.254] 7878051300953b5c0d0a
2024-04-11 13:08:12  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0
2024-04-11 13:08:22  INFO: [T6b740ed5: gt06 < 187.60.53.254] 79790008940004f60096d39f0d0a
2024-04-11 13:08:22  INFO: [T6b740ed5] id: 868022033644035, time: 2024-04-11 12:52:04, lat: -4.85048, lon: -39.57577, course: 239.0

In other words, with each ping that the tracker sends to the platform, it shows the same position and the same time.

I would like to know how to solve this problem, my version of traccar is 5.5, protocol used GT06, any solution?

Anton Tananaev8 months ago

This is expected. That's how most GT06-based devices work. They don't send location when stationary.

Lucas Bezerra8 months ago

It is repeatedly sending the same location, wasting chip data and generating unnecessary positions in traccar.

Image

Anton Tananaev8 months ago

Chip data? It doesn't actually send location, as I said.

Lucas Bezerra8 months ago

This generates unnecessary internet data consumption!
But wasn't it only supposed to send the location to the platform once according to the time set on the tracker?

Anton Tananaev8 months ago

Read what I said earlier.

Lucas Bezerra8 months ago

I read it my friend, but I want to solve the problem that every 180 seconds it sends the same location, with the time set on the tracker being 3600 seconds, disturbing the route when I use the traccar replay.

Anton Tananaev8 months ago

That's a device problem, not server.

Adriano Miranda7 months ago

Lucas Bezerra try this:

Device side:

  • Increase the heartbeat time

Server side:

  • time.override
  • Som filter like filter.distance and/or filter.static
Lucas Bezerra7 months ago

I tried to use filter.duplicate to filter this repeated data but without success!

<entry key='filter.duplicate'>true</entry>
<entry key='filter.enable'>true</entry>

according to the configuration file documentation: Filter duplicate records (duplicates are detected by time value).

Anton Tananaev7 months ago

Are you sure you don't have any other parameters in the config?

Lucas Bezerra7 months ago

My Traccar.xml file:

<entry key='config.default'>./conf/default.xml</entry>


<entry key='database.driver'>com.mysql.cj.jdbc.Driver</entry>
<entry key='database.url'>jdbc:mysql://localhost/traccar?serverTimezone=UTC>
<entry key='database.user'>XXXXXX</entry>
<entry key='database.password'>XXXXXX</entry>

<entry key='notificator.types'>web,mail,traccar</entry>
<entry key='notificator.traccar.key'>XXXXXXX>


<entry key='filter.duplicate'>true</entry>
<entry key='filter.enable'>true</entry>
Anton Tananaev7 months ago

This is all? And you haven't changed anything in default.xml? If yes to all, then the filtering should work. Remember that filtering applies to the new data only. What's already in the database won't be deleted.

Lucas Bezerra7 months ago

My default.xml:

<properties>

    <!--

    DO NOT MODIFY THIS FILE. Use traccar.xml instead.

    -->

    <entry key='web.port'>8082</entry>
    <entry key='web.path'>./web</entry>
    <entry key='web.override'>./override</entry>
    <entry key='web.sanitize'>false</entry>
    <entry key='web.persistSession'>false</entry>
    <entry key='web.showUnknownDevices'>true</entry>

    <entry key='geocoder.enable'>true</entry>
    <entry key='geocoder.type'>locationiq</entry>
    <entry key='geocoder.key'>pk.689d849289c8c63708068b2ff1f63b2d</entry>
    <entry key='geocoder.onRequest'>true</entry>
    <entry key='geocoder.ignorePositions'>true</entry>

    <entry key='logger.level'>info</entry>
    <entry key='logger.file'>./logs/tracker-server.log</entry>
    <entry key='logger.rotate'>true</entry>

    <entry key='filter.enable'>true</entry>
    <entry key='filter.future'>86400</entry>

    <entry key='event.ignoreDuplicateAlerts'>true</entry>

    <entry key='media.path'>./media</entry>

    <entry key='notificator.types'>web,mail,command</entry>

    <entry key='server.statistics'>https://www.traccar.org/analytics/</entry>

    <entry key='commands.queueing'>true</entry>

    <entry key='database.ignoreUnknown'>true</entry>
    <entry key='database.changelog'>./schema/changelog-master.xml</entry>

    <entry key='gps103.port'>5001</entry>
...
    <entry key='valtrack.port'>5255</entry>

</properties>
Lucas Bezerra7 months ago

I didn't change anything in the default, it continues like this even placing the filter and restarting the server to apply it