Page 1 of 1

Freematics ONE+ Model B sniffer example not working

Posted: Sun Dec 22, 2019 10:40 am
by tsprog
The sniffer example program only returns the following on the serial monitor:
Firmware: R14
NO PID MAP CAN sniffer started
[90453] 00 00 07 E8 08 06 41 00 BF 9F A8 93 00
[99452] 00 00 07 E8 08 06 41 00 BF 9F A8 93 00
[103954] 00 00 07 E8 08 06 41 00 BF 9F A8 93 00
repeat of the above hex output with different time stamps

The sniffer only starts after the car is started.
I even commented out the setHeaderFilter an setHeaderMask lines and still got the above results
// we are interested in CAN messages with header 7E*
//obd.setHeaderFilter(0x7E0);
//obd.setHeaderMask(0xFFFFFFF0);
Why is the sniffer only returning one CAN message repeatedly?
I started the sniffer to find 4 different CAN messages; engine on of off, door ajar status of driver, passenger, rear left, and rear right doors.
Also, is there a way to have the sniffer work when the engine is off?

Re: Freematics ONE+ Model B sniffer example not working

Posted: Fri Jan 24, 2020 1:36 am
by anna30
Did you find a solution for this? I am trying to receive 6 specific CAN messages and got the same problem with just receiving the ECU response.

Re: Freematics ONE+ Model B sniffer example not working

Posted: Tue Jan 28, 2020 3:11 pm
by stanley
When engine is off, OBD port might have no traffic.

Re: Freematics ONE+ Model B sniffer example not working

Posted: Sun Jul 05, 2020 5:41 am
by Mastodon2K
Same issue for me with the UART v2.1. Doesn't matter if the engine's on or not, after running ATM1 I keep getting that same HEX string every few seconds.

00 00 07 E8 08 06 41 00 BF 9F A8 93 00

Other commands seem to work. At least 0902 gives me the HEX version of the VIN and I have no issue reading the RPM. But, I can't get the sniffer to work.

For what it's worth, this is on a 2016 Ford Mustang.