Freematics Forum

Hello everyone;

I'm working with 3 OBD Data Logger I bought last month.

Until now I have not been able to make the Loggers receive any information from the car values. They are simple not reading information coming from the OBD port. I can only make the GPS and the Accelerometer work.

So my 1st questions is: is there anyone who has made it work? In that case I will start comparing what I've done against what other people did.

I need your help. Thank you in advance.

Miguel

Hello Miguel,

you are not alone. I have 2 loggers and have problems, too.
The Freematics Datalogger is only able to read data via CAN 11/500.
I guess the firmware of the STM32F has a few bugs.

I_Code_do_this wrote:Hello Miguel,

you are not alone. I have 2 loggers and have problems, too.
The Freematics Datalogger is only able to read data via CAN 11/500.
I guess the firmware of the STM32F has a few bugs.

Thanks for your answer. I'm glad to see that I'm not making such a big mistake that I'm the only one who doesn't make the device work. However, it doesn't solve the problem. Any idea about how to solve it if we don't receive the support from the developer?

Am I the only one who receives very short and non-helping answers by Stanley?

Regards,

Miguel

You are not alone, Miguel.

Although I'm currently using the device just for an accelerometer implementation, I've asked quite a few questions on the forums, and most have remained unanswered. Those few answers, however, solved nothing and turned out useless...

There is a change in OBD library about timeout value which may cause unexpected timeout for slower protocols. Please update the library and give another try.
https://github.com/stanleyhuangyc/Freem ... raries/OBD

Have the same issue with Hyudai Accent 2007.
I've tried the updated libraries also, but not luck.

Hi all,
I got a Data Logger last week. I'm using the latest firmware version (v3) on a Ford Fiesta 2006.
I only get files with very few lines for a 10 minute trip, like this:

0 10C 0
$GPGSV 1 1 00*793706 20 946 0 -360
0 21 28 49 -3
0 22 -3 3 -5
0 10D 0
$GPGSV 1 1 00*79120 20 945 -36 -384
0 21 14 18 1
0 22 -3 3 -4
0 104 0
$GPGLL V N*64121 20 1053 -12 -289
0 21 8 -150 24
0 22 -2 3 -2
0 111
$GPGLL V N*641426 20 926 -1 -413
0 21 10 -4 2
0 22 -3 3 -6
0 105

I will appreciate if anyone has any idea how to solve it.
Thanks
Dave

- The first line "0 10C 0" is a PID Reading, meaning the time passed (0 ms), mode (mode 1), PID (0C meaning engine RPM) and the PID value (0 rpm).
- Then you have this: "$GPGSV 1 1 00*793706". I don't know what is...
- And then, on the same line, "20 946 0 -360". That would be the accelerometer reading (as PID 20), values 946, 0 and -360).
- The next two lines go with the previous one, as they are the gyroscope (PID 21) and magnetometer (PID 22) readings, in the same format (time PID 3values).
- Then, you have "0 10D 0", which means 0ms, mode 1, PID 0D (vehicle speed) and value 0 (km/h).
- The next lines read the same as the rest, you can look up what each PID code means at https://en.wikipedia.org/wiki/OBD-II_PIDs

About that gibberish I don't know the meaning of (on the second line of data you posted), let's hope the god-almighty-and-allknowing-but-never-giving-useful-answers-Stanley gives you help!

PS: There seems to be some problem with the clock, it's strange that all measures clock at 0ms from the previous one... Also, all your PID readings read 0, and even if you were stopped, engine load (04) and rpm (0C) should at least give something more tan 0...

Thank you very much Xavali7.
Now the meaning of each signal is clear to me.
But I still have to solve the problem that it saves only one file with few lines out of 10 minutes recording. And the issue with the clock too.

It is definitely not right for the timestamp to be 0 all the time. Did you modify anything in the source code?

Xavali7 wrote:- The first line "0 10C 0" is a PID Reading, meaning the time passed (0 ms), mode (mode 1), PID (0C meaning engine RPM) and the PID value (0 rpm).