Freematics Forum

I have just bought a Version 4 unit and I'm having problems. Connecting the unit to my car today resulted in it writing 392 empty files to the SD card - not a single character in any of them. I have connected the unit to my pc and downloaded the example Datalogger sketch from git hub and this is what I see in the serial monitor

#FREEMATICS
Firmware Version 0
SD 7856MB
MEMS OK
OBD NO
GPS NO
FILE 1
ACC,0,0,0
ACC,0,0,0
ACC,0,0,0
ACC,0,0,0
ACC,0,0,0
ACC,0,0,0
ACC,0,0,0

What ever I do I cannot get anything but zero's out of the MEMS and should the firmware version be 0??

Tried this unit again today on a short return trip and I have 14 csv files on the sd card 11 of which are empty. The three that contain some data (files 6, 12 & 14) don't contain any GPS data OR MEMS data (snippet below)

#0 ACC 0 0 0
0 ACC 0 0 0
19197 10F 14
0 ACC 0 0 0
0 ACC 0 0 0
0 ACC 0 0 0
30407 105 22
0 ACC 0 0 0
10150 10F 16
0 ACC 0 0 0
0 ACC 0 0 0
0 ACC 0 0 0
30376 105 29
0 ACC 0 0 0
10150 10F 17
0 ACC 0 0 0
0 ACC 0 0 0
0 ACC 0 0 0
30396 105 35
0 ACC 0 0 0
10130 10F 17
0 ACC 0 0 0
0 ACC 0 0 0
0 ACC 0 0 0
30366 105 40
0 ACC 0 0 0
10130 10F 17
0 ACC 0 0 0
0 ACC 0 0 0
0 ACC 0 0 0

I must admit that at this point I'm thinking or returning it for a refund as it's not fit for purpose and doesn't even make a good paper weight!!!!

OBD NO means OBD is not connected. Make sure you car's protocol is within the support list. The latest datalogger sketch allows logging of MEMS and GPS data even when OBD is not connected.

OBD NO means OBD is not connected.

That's because it was connected to my pc and not the car!

The latest datalogger sketch allows logging of MEMS and GPS data even when OBD is not connected.

Which confirms that the MEMS sensor is defective!

Have you solved the problem yet?
I ordered the V4 Datalogger today and my CSV Output looks nearly the same as yours.

Thanks in advance

This issue was solved. Please update the code to latest revision.

Hi,

I bought a Freematics ONE and I'm dealing with the same problem. My device is not recording OBD data. The .csv files saved on the SD card are empty or just ACC data appears.

stanley wrote:This issue was solved. Please update the code to latest revision.

I tried uploading the datalogger.h, datalogger.ino and config.h files from github which is updated 26 days ago but this doesn’t solve my problem. I’ve connected the Freematics ONE to the computer with the USB cable and opened Serial Monitor though Arduino IDE. It shows this:

Firmware Version 0
SD 15549MB
MEMS OK
OBD NO
GPS OK
ACC,-4,1,-99
ACC,-4,1,-98
(…)

Should the Firmware version be 0? Why is OBD not connected? I am doing some test plugging it to an OBD ECU emulator (Ozen elektronik), but I also tried in the car and the result was the same.

Please help me, I'm stuck with this issue ...

I got the same problem. I just bought the Datalogger and plugged into my car. There were no data. After uploading the datalogger sketch from github I only get the following data:

I believe most people are having the device working well since 300+ of this product has been shipped already. This issue normally happens when the device is plugged in a car which uses an unsupported protocol (mostly legacy ISO9141-2).

I've used your emulator (MK-II) and changed speed and rpm for each of the protocol provided by the Freematics GUI

EDIT: but I always get the data above. Furthermore I've plugged in the GPS receiver and waited for an quater hour without data. But GPS-Satelites were available.