OBD II Data Slow

[JMat]

I have a late year '98 SR5 and have been using the Torque Pro app with the same OBD II bluetooth adaptor for about 5 years now. I 've always wondered why the data only feeds to the Torque app about every 1.25 seconds, it makes it impossible to graph oxygen sensor info and the like, because when the same equipment is used on other cars the data is, for all intents an purposes, live. I had always just chocked this delay up to the earlier 4runners until a few weeks ago when I picked up a '97. Long story short... The data from the '97 feeds over to the Torque app immediately, I can graph fuel trims and oxygen sensor voltage with no issues. This is with the same adaptor, phone and using the same profile that I use for my '98.

Any ideas why this is happening? Thanks.

 

[Moonoffroad]

I've been eyeing getting a live feed recently as well. I got a 98 base so im curious if its delayed as well

 

[MStudt]

It's not the app that causing you the delay. It's the OBD2 reader you're using. The app is going to refresh based on the PID rate of the reader. The higher the PID rate the faster the refresh. The ELM327 is one of the better readers.

Do you know what the PID rate of your reader is? Or, what reader you have?

Mike

 

[JMat]

It's not the app that causing you the delay. It's the OBD2 reader you're using. The app is going to refresh based on the PID rate of the reader. The higher the PID rate the faster the refresh. The ELM327 is one of the better readers.

Do you know what the PID rate of your reader is? Or, what reader you have?

Mike

Thanks for responding Mike.

I have the ELM327 and I've used the same one in all the vehicles but for some reason the refresh rate is slow only on my '98. I even used my '98 Torque app vehicle profile with the '97(thinking there might be a setting linked to '98 vehicle profile) but it refreshes fast, much differnt that when it's plugged in to the '98.

 

[DaMonkey]

I’m pulling PID (lol) with an ELM327 interface into Arduino on my 98. One PID pull is 120 milliseconds. Including o2. In the world of OBDII that is slooow. So I had to code around that to separate time sensitive PIDs.

1.25 seconds will be from how it’s coded the from unit. OBD is limited 120ms for 1 pull. If it’s real time for 10 PIDs 1.25 secs is right, maybe you can isolate just the one and the code will ignore others to speed up o2? I had to be very aware of how code loops in order to have functionality I wanted.