FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

4167 questions

4739 answers

3460 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
1,646 views
in Vehicle tracking by anonymous
We are using FM3001 devices. I have one that has new firmware: FW 03.18.21 - and it does not seem to read OBD data properly - just the VIN.
The older firmware: FW 03.10.02 seems to read fine on the truck. Is there a way to downgrade the firmware, or any reason this might be? The old one shows OBD IC Version of 0.0.3.10 and the new one is 0.0.8.1.

They both show using protocol ISO 15765-4 CAN

I am logged directly into the device, and I can see fuel level, and other OBD data on the older FW, but, the new it's all just zeros.

Thanks
by
Hi, which protocol was detected? CAN, but what baud rate was detected 29/250, 29/250, 11/250, 11/500?

0.0.8.1 is not error tolerant (very strictly) and have nominal bit sample point inaccuracy (CAN). Are you able to test the 0.0.8.2 (in progress now) with enabled logging?

Please provide "obdinfo" and "obdinfo1" SMS responses of both versions (3.10 and 8.1)

Thanks

1 Answer

0 votes
by anonymous

Hello,

Thanks for the response. It is using 11/500. Now that I have had the 0.0.8.1 running for a few days - I do find it very intermittently provides some data. I would say about 20% of the time. I have it set to report just a few things, the VIN, the fuel amount left, and a couple other data points. Periodically it will send the VIN, and the right numbers, but, often it just sends zeros and no VIN. I sent the commands this morning on my truck, and these are the results: (2 different times I sent them). Even when it provides the VIN, it usually just has zeroes for most of the other values if it reports them. 
 

P1:0x90180013,P2:0x8003A001,P3:0xC4C0801D,P4:0x10000000,C1:0x0,C2:0x0,C3:0x0,C4:0x0,Hdr:7E8,Phy:1,CFG:7E0,v100.801.100

P1:0x90180013,P2:0x8003A001,P3:0xC4C0801D,P4:0x10000000,C1:0x90180002,C2:0x8002A000,C3:0x4440001C,C4:0x0,Hdr:7E8,Phy:1,CFG:7E0,v100.801.100

Prot:6,VIN:1FT8W3BT2GEA18216,TM:20,CNT:15,ST:DATA REQUESTING,P1:0x90180013,P2:0x8003A001,P3:0xC4C0801D,P4:0x10000000,MIL:0,DTC:0,ID3,Hdr:7E8,Phy:1

Prot:6,VIN:1FT8W3BT2GEA18216,TM:20,CNT:15,ST:DATA REQUESTING,P1:0x90180013,P2:0x8003A001,P3:0xC4C0801D,P4:0x10000000,MIL:0,DTC:0,ID3,Hdr:7E8,Phy:1

And, when it's not working, I will just get N/A for the VIN and other details.
P1:0x0,P2:0x0,P3:0x0,P4:0x0,C1:0x0,C2:0x0,C3:0x0,C4:0x0,Hdr:0,Phy:1,CFG:7DF,v100.801.100

The older firmware version is on a different truck now, but, same style truck as mine that I was testing. Here is the details from that one:

Prot:6,VIN:1FT8W3BT3JEC15564,TM:20,CNT:23,ST:DATA REQUESTING,P1:0x983B0017,P2:0xA01BA015,P3:0xC4C080DD,P4:0x0,MIL:0,DTC:0,ID3,Hdr:7E8,Phy:1
P1:0x983B0017,P2:0xA01BA015,P3:0xC4C080DD,P4:0x0,C1:0x983B0002,C2:0xA01AA000,C3:0x4440009C,C4:0x0,Hdr:7E8,Phy:1,CFG:7E0,v100.310.100

If you would like me to try a new testing version, that is no problem - if you can send me details, I can test it on the one unit running in my truck.

Thanks.

by
Thanks for provided info.

Please, wait a little bit. I will provide new FW for tests when it will be ready.
by
Hi,

new FW is ready: https://drive.google.com/file/d/16AGO3AxhWESFJky4Ma97NxjXkm5pWM1W/view?usp=sharing

Please, test it and give feedback. If issue is still reproducible, please make log, with enabled filters - SMS command: "log2sdfilterset:0;4" (use configurator to download the logs/dumps)
by anonymous
Thankyou very much - I tried the new firmware yesterday, and so far it seems to work perfect. It reads the OBD data without any issues.
by
Thanks for feedback! Changes already pushed to base version.