Freematics Forum

protomor wrote: > What year/model car are you polling? Older care are always just plain > slower. 400ms isn't an abnormal return time for a single PID from an early > 2000s car. Even some later 2000s cars. > > The chip used by the freematics unit is the same as the sparkfun (ELM327 > IIRC). So the c...

Just an update on this. Using the Sparkfun UART I was able to increase speed significantly by turning off adaptive timing and lowering the timeout to 1 AT AT0 AT ST 01 However when I tried these commands with the freematics they were not recognized. Most other AT commands work fine with the Freemati...

I am polling 8 PIDs most with only 2 byte responses. It takes 400ms+ to return responses for all 8 PIDS. I tried speeding things up with changing the baud rate to 115200 but the results were exactly the same, so I don't think it's just serial speed issue. I use other devices to data log my ECU with ...

stanley wrote:
> You can request any PIDs but it varies whether they will be responded or
> whether new code needs to be added for parsing the response.

I have a PID that is 0x11B3. The standard freematics library cannot handle a two byte command. Can you provide some direction?

I am having trouble determining what to do in the library files to handle a 4 byte response. I'd like to scan PIDs like 0x00 to determine which PIDs are supported in the ECU.

Thanks for posting the solution to this. You saved me a ton of time!

I got the OBD-II UART working easily enough with the pre-loaded PIDs. There are some PIDs that are above the 0xXXh range. For example some of these PIDs 0x11XXh range (am guessing this is still hex). Any easy way to support these or will I need to dig into the libraries more?