V4 Not working?

Inquiry and support for Freematics products
oipa
Posts: 2
Joined: Wed Jul 06, 2016 6:36 pm

Re: V4 Not working?

Post by oipa »

After uploading once again the code my results have changed, now I get this on the serial monitor:

Code: Select all

Firmware Version 11
SD 15549MB
MEMS OK
OBD OK
GPS OK
ACC,-12,0,-99
DTE,130716
UTC,8435060
LAT,43304111
LNG,-2009253
ALT,62
SPD,0
SAT,7
FILE 7130843
ACC,-12,0,-98
DTE,130716
UTC,8435090
LAT,43304112
LNG,-2009254
ALT,62
SPD,0
SAT,7
(...)


As you can see something has changed (firmware version is different) and OBD state is OK now . Even so, I continue without getting any data from the OBD...
Could this be a protocol problem? I'm using an emulator which uses CAN protocol (ISO 15765-4).

PD.: My GPS signal is working well since I put the receptor close to the window.
Phoenix0205
Posts: 3
Joined: Thu Jul 07, 2016 10:46 pm

Re: V4 Not working?

Post by Phoenix0205 »

I've changed the verbose state to 1, uploaded the sketch again and changed it back to 0 and uploaded the sketch. Since then I get data like this:

Code: Select all

Firmware Version 0
SD 15432MB
MEMS OK
OBD NO
GPS NO
FILE 35
ACC,0,0,110
ACC,0,0,110


At least I am a little bit surprised by the Firmware Version, but maybe it is not relevant. BUT now I know, that the connected GPS Receiver (M8030 - 10 HZ GPS + Glonass) was not detected by the V4. The Baudrate of the Library FreematicsONE seams to be correct (afaik each baudrate is supported by the M8030)

Any Idea why the GPS Receiver cannot be detected?
VelaJul
Posts: 1
Joined: Wed Mar 01, 2017 7:25 pm

Re: V4 Not working?

Post by VelaJul »

Hi,

after doing some research, I noticed that the car I've been testing the datalogger uses this unsupported protocol mentioned (volvo v70, not my car though).

Is there any workaround to this?

I only got a single 32kb DATA file dated as 1.1.2000 on my sd card after multiple tries.

[quote="stanley"]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).[/quote]

Here is what I get in serial monitor
Firmware Ver. 11
MEMS OK
OBD NO
Standby
245156741

I am using the github code as instructed on the website.

Plan was to test that this works with the datalogger and then use some version of the telelogger to atleast send location data to a server. I have the sim card model with external gps and antenna.

Appreciate any help.
protomor
Posts: 99
Joined: Wed Oct 14, 2015 9:17 am

Re: V4 Not working?

Post by protomor »

What year volvo v70 is it? I actually found this funny thing with the ISO9141-2 cars that I tested. Plug in the freematics unit with the car on. Wait for it to try to connect and fail out, then unplug it and plug it back in without turning the car off. I think the ELM327 chip responds too quickly for the old protocol to properly trip all of the setup calls. So plugging it in a second time helps the rest of the stack of commands to get run.

What PIDs are you trying to run? 9141-2 is pretty old and only runs the bare minimum PIDs. On top of that. It's slow as hell.

The dates on the SD card files are always going to be that date time. The freematics unit has no idea about date until the GPS unit connects. But by that point, the file is already being written. Does your log file at least print out accelerometer and gps data? If not, you might not have the right version of the sketch.
stanley
Site Admin
Posts: 1018
Joined: Sat Mar 01, 2014 3:15 am

Re: V4 Not working?

Post by stanley »

Make sure to use latest library (has a longer timeout value). Some ISO9141-2 cars can be connected though very slow.
trigonix
Posts: 1
Joined: Thu Apr 22, 2021 2:25 am

Re: V4 Not working?

Post by trigonix »

Did you resolve it?

I do have the same issue.
Post Reply