Telelogger sketch, Freematics ONE+ H shows up as online but in the middle of atlantic ocean.

M10 months ago

Hi everyone,

I recently received my Freematics One+ H gps tracker onto which I installed the Telelogger sketch and configured it to connect to my cell APN.

The device shows up in Traccar as online (right away which is awesome) however, it seems like actual GPS coordinates are not making it to Traccar since the device shows up in the middle of the ocean right next to Africa.

If anyone has any guidance as to how I can debug this issue I would greatly appreciate it.

Anton Tananaev10 months ago

in the middle of the ocean right next to Africa

That's zero coordinates, which usually means no GPS signal. Are you outside with a clear sky visibility for the GPS antenna? Also note that first fix might take 10 minutes or even more in some cases.

M10 months ago

Yes my device is outside and with a clear view of the sky. It's debug output is the following which seems to show GPS coordinates are being gathered but I am not positive.

[NET] 01:28.6 | Packet #28 | Out: 1 KB | In: 23 bytes
RSSI:-75dBm
[BUF] 3 samples | 30 bytes | 1/1024
UCFLFXXX#0:112389,24:362,20:0.01;0.04;0,82:43*A9
[CELL] 48 bytes being sent
[NET] 01:33.6 | Packet #29 | Out: 1 KB | In: 23 bytes
[BUF] 3 samples | 30 bytes | 1/1024
UCFLFXXX#0:117390,24:368,20:0.01;0.04;0,82:43*AC
[CELL] 48 bytes being sent
[NET] 01:38.6 | Packet #30 | Out: 1 KB | In: 23 bytes
RSSI:-75dBm
[BUF] 3 samples | 30 bytes | 1/1024
UCFLFXXX#0:122391,24:369,20:0.01;0.04;0,82:43*AA
[CELL] 48 bytes being sent
[NET] 01:43.6 | Packet #31 | Out: 1 KB | In: 23 bytes
[BUF] 3 samples | 30 bytes | 1/1024
UCFLFXXX#0:127392,24:369,20:0;0.04;0,82:43*21
[CELL] 45 bytes being sent
[NET] 01:48.6 | Packet #32 | Out: 1 KB | In: 23 bytes
RSSI:-75dBm
M10 months ago

Confirmed the device is fixed to a GPS signal, output is the following in the debug console, but still shows in the ocean in Traccar.

[NET] 00:08.1 | Packet #5 | Out: 0 KB | In: 23 bytes
RSSI:-73dBm
[GPS] 59.125130 -119.158150 0km/h Course:0 2023-06-04T22:38:29.100Z
UCFLFXXX#0:27164,81:-73,24:364,20:0;0;0,10:22382910,82:46*21
[CELL] 60 bytes being sent
[NET] 00:11.0 | Packet #6 | Out: 0 KB | In: 23 bytes
[GPS] 59.125126 -119.158150 0km/h Course:0 2023-06-04T22:38:31.800Z
[BUF] 4 samples | 38 bytes | 1/1024
UCFLFXXX#0:30051,24:369,20:0;0;0,10:22383183,82:46*B8
[CELL] 53 bytes being sent
[NET] 00:13.9 | Packet #7 | Out: 0 KB | In: 23 bytes
Track-trace210 months ago

You might show what actually is the raw data in your traccar log.

M10 months ago

I can see that my device is showing as having sent coordinates in zeroes, and there also seems to be an IO error of sorts. Output from Traccar logs is the following:

2023-06-04 22:54:10  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a32343237352c32343a3336392c32303a303b303b302c31303a32323534313035322c38323a34332a4237
2023-06-04 22:54:10  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:10, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-04 22:54:13  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a32373136332c38313a2d37392c32343a3336372c32303a303b303b302c31303a32323534313334352c38323a34332a3235
2023-06-04 22:54:13  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:13, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-04 22:54:16  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a33303034392c32343a3336372c32303a303b303b302c31303a32323534313632382c38323a34332a4241
2023-06-04 22:54:16  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:16, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-04 22:54:19  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a33323933362c32343a3336372c32303a303b303b302c31303a32323534313932312c38323a34332a4244
2023-06-04 22:54:19  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:19, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-04 22:54:22  INFO: [Tac8d4330] connected
2023-06-04 22:54:22  INFO: [Tac8d4330: meitrack < 35.203.210.7] 474554202f20485454502f312e310d0a486f73743a2033352e3138332e3137312e34373a353032300d0a557365722d4167656e743a20457870616e73652c20612050616c6f20416c746f204e6574776f726b7320636f6d70616e792c207365617263686573206163726f73732074686520676c6f62616c2049507634207370616365206d756c7469706c652074696d6573207065722064617920746f206964656e7469667920637573746f6d657273262333393b2070726573656e636573206f6e2074686520496e7465726e65742e20496620796f7520776f756c64206c696b6520746f206265206578636c756465642066726f6d206f7572207363616e732c20706c656173652073656e64204950206164647265737365732f646f6d61696e7320746f3a207363616e696e666f4070616c6f616c746f6e6574776f726b732e636f6d0d0a0d0a
2023-06-04 22:54:22  INFO: [Tac8d4330] error - For input string: " / HTTP/1.1
Host: 35.183.171.47:5020
User-Agent: Expanse" - NumberFormatException (... < MeitrackFrameDecoder:37 < BaseFrameDecoder:29 < ... < WrapperInboundHandler:57 < ...)
2023-06-04 22:54:22  INFO: [Tac8d4330] disconnected
2023-06-04 22:54:22  INFO: [Tac8d4330] error - For input string: " / HTTP/1.1
Host: 35.183.171.47:5020
User-Agent: Expanse" - NumberFormatException (... < MeitrackFrameDecoder:37 < BaseFrameDecoder:29 < ... < WrapperInboundHandler:50 < ...)
2023-06-04 22:54:22  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a33353832322c32343a3336352c32303a303b303b302c31303a32323534323230332c38323a34332a4232
2023-06-04 22:54:22  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:22, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-04 22:54:28  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a34313539342c32343a3336372c32303a303b303b302c31303a32323534323738392c38323a34332a4341
2023-06-04 22:54:28  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:27, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-04 22:54:31  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a34343438312c32343a3336372c32303a303b303b302c31303a32323534333037322c38323a34342a4242
2023-06-04 22:54:31  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:30, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-04 22:54:33  INFO: [U65a04d6d: freematics < 74.198.149.120] 5543464c4641594d23303a34373336382c32343a3336372c32303a303b303b302c31303a32323534333336352c38323a34342a4337
2023-06-04 22:54:33  INFO: [U65a04d6d] id: UCFLFXXX, time: 2023-06-04 22:54:33, lat: 0.00000, lon: 0.00000, course: 0.0

Even though the output in the debug console (PlatformIO) is:

RSSI:-69dBm
[GPS] 59.125103 -119.158127 0km/h Course:0 2023-06-04T22:56:46.600Z
[BUF] 5 samples | 46 bytes | 1/1024
UCFLFXXX#0:180488,81:-69,24:367,20:0;0;0,10:22564667,82:45*6C
[CELL] 61 bytes being sent
[NET] 02:44.3 | Packet #43 | Out: 2 KB | In: 47 bytes
[GPS] 59.125103 -119.158127 0km/h Course:0 2023-06-04T22:56:51.700Z
[BUF] 4 samples | 38 bytes | 1/1024
UCFLFXXX#0:185490,24:359,20:0;0;0,10:22565172,82:45*F8
[CELL] 54 bytes being sent
[NET] 02:49.3 | Packet #44 | Out: 2 KB | In: 47 bytes
RSSI:-75dBm
[GPS] 59.125107 -119.158127 0km/h Course:0 2023-06-04T22:56:56.700Z
[BUF] 5 samples | 46 bytes | 1/1024
Anton Tananaev10 months ago

Looks like the device is not reporting any location data.

M10 months ago

What would be the best way to debug this? I don't understand how the console for the device shows the correct GPS coordinates but then those coordinates don't make it to the Traccar server.

Anton Tananaev10 months ago

You can probably add some logging on the device to see why it doesn't send location to the server. It must be some configuration.

M10 months ago

I installed an older version of the freematics telelogger firmware and Traccar reports the following when the device attempts to send its location:

2023-06-05 00:34:23  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a32363737302c32343a3330302c38323a35332e3030303030302c2a4642
2023-06-05 00:34:23  INFO: [U65a04d6d] error - For input string: "53.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-06-05 00:34:24  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a32373737302c32343a3330302c38323a35322e3030303030302c2a4642
2023-06-05 00:34:24  INFO: [U65a04d6d] error - For input string: "52.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-06-05 00:34:25  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a32383737302c32343a3330302c38323a35322e3030303030302c2a4643
2023-06-05 00:34:25  INFO: [U65a04d6d] error - For input string: "52.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-06-05 00:34:26  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a32393737302c32343a3330302c38323a35332e3030303030302c2a4645
2023-06-05 00:34:26  INFO: [U65a04d6d] error - For input string: "53.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-06-05 00:34:27  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a33303737302c32343a3330302c38323a35332e3030303030302c2a4636
2023-06-05 00:34:27  INFO: [U65a04d6d] error - For input string: "53.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-06-05 00:34:28  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a33313737302c32343a3330302c38323a35332e3030303030302c2a4637
2023-06-05 00:34:28  INFO: [U65a04d6d] error - For input string: "53.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-06-05 00:34:29  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a33323737302c32343a3330302c38323a35332e3030303030302c2a4638
2023-06-05 00:34:29  INFO: [U65a04d6d] error - For input string: "53.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-06-05 00:34:30  INFO: [U65a04d6d: freematics < 74.198.149.119] 5543464c4641594d23303a33333737302c32343a3330302c38323a35332e3030303030302c2a4639
2023-06-05 00:34:30  INFO: [U65a04d6d] error - For input string: "53.000000" - NumberFormatException (... < FreematicsProtocolDecoder:156 < *:206 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
M10 months ago

You can probably add some logging on the device to see why it doesn't send location to the server. It must be some configuration.

Thanks I will try that

Anton Tananaev10 months ago
M10 months ago

Thank you for that patch, I'm not sure how to apply the patch to a Traccar container but I will not bother you with those details :)

On the other hand, I added extra logging to the Firmware V5 Telelogger for Freematics and confirmed that the GPS device is attempting to send the following packet to Traccar, I am not sure if this is well formed or not but this is exactly what it is trying to send:

Actual Packet:
UCFLFAYM#0:274036,24:369,20:0;0;0,10:1043307,82:48*BB
Anton Tananaev10 months ago

That's exactly what's received in Traccar, as you can see in the logs.

M10 months ago

In the Traccar logs, I see Traccar receiving:

2023-06-05 01:07:28  INFO: [U65a04d6d] id: UCFLFAYM, time: 2023-06-05 01:07:28, lat: 0.00000, lon: 0.00000, course: 0.0

Maybe I am misunderstanding something?