Harry's GPS Suite Forum

roqyBT4 requires a jailbroken iPhone to work. It works around the limitations Apple adds to the Bluetooth stack. So an ELM327 compatible BT OBD II dongle + roqyBT4 + jailbroken iPhone + LapTimer work together. The standard way is to go for a compatible WLAN OBD II dongle + LapTimer (and no jailbreak).

- Harry

Hi guys. My ELM327 bluetooth OBD II dongle not found by Harry's Laptimer Pro, both of which I purchased today. The ELM device is this one I purchased http://www.ebay.com.au/itm/280842989865 ... 1497.l2649

Connects to roqbBT4 licenced bluetooth perfectly through 127.0.0.1 port 35000 which is on a Jailbroken iphone. It stays connected but when I go into laptimer pro I don't see the device. If I go into sensor list I see Iphone Accelerometer, Iphone video, Iphone GPS. All the OBD Sensors do a search then come up with not available. I also don't see any bluetooth OBD devices listed.

I read on this thread that someone had their BT device working.

Please help.

You need to configure a custom OBD in Expert Settings (OBD Tweaks).

- Harry

Wow man, what super service. Yes got it going I can now see engine revs.

How can I see the other engine parameters like, temperature, MAF, boost pressure?

Please check this one: http://www.gps-laptimer.de/OBD_II.html

- Harry

Harry,

Can you provide some guidance on how to adjust the OBD Tweaks parameters to get optimum performance when using a BT device and roqyBT4? I have intermittent connectivity issues, similar to what has been posted before, but I feel like I am guessing in the dark when changing the OBD Tweaks parameters since I don't know what they mean or have any methodology on how to adjust them for optimal performance.

On a related note, I think that my problem may be that my ELM327 BT device (the blue, orange, black type) may be too old as I know it is not a current v1.5

Update: Apparently the latest ELM327 version is 1.4b according to the creators of the ELM327 chip. Also according to their site, there is no v1.5 (or 1.4a), as is seen from many eBay vendors. I actually have v1.3a which might be contributing to my problem. I have ordered a new one (v1.4b) from another eBay vendor for $20 to give it a shot based on the success of another user posted earlier in this thread.

Not from my side. I do not actively support any activities on jailbroken iPhone. Maybe someone else reading this can jump in.

- Harry

Harry wrote:Not from my side. I do not actively support any activities on jailbroken iPhone. Maybe someone else reading this can jump in.

- Harry

Ok, I understand from that perspective.....

But since this is your app, could you at least define/tell me what the following parameters do (as far as how Lap Timer interprets the OBD data signal) so that I can methodically adjust them while attempting to achieve optimum performance?

Speed Multiplier
Pause Between PIDs

Right now I feel like I am randomly changing them without knowing what the expected effect should be following the adjustment. Also, when making changes to these parameters (specifically the OBD Tweaks), will they take effect immediately or do you have close Lap Timer (permanently by hitting the red "x") and then re-open in order for the changes to take effect?

Yes, that's fine.

Speed multiplier allows correction of speed values read in from the car's bus. I had several user either with too high or too low speeds delivered. Setting the multiplier to 1.1 will add 10% speed on top of the speed delivered by OBD as an example.

Pause Between PIDs is more technical. LapTimer requests OBD datain a sequence. E.g. first speed, then throttle position, then rpms. The Pause is simply added between each request. The default 0.01 means 10ms. High values will degrade overall update rate. The setting has been introduced while searching for the reason some wifi dongles lost connection. Actually, the reason has been another one and is fixed.

Both settings should have immediate effect.

- Harry

Harry wrote:Yes, that's fine.

Speed multiplier allows correction of speed values read in from the car's bus. I had several user either with too high or too low speeds delivered. Setting the multiplier to 1.1 will add 10% speed on top of the speed delivered by OBD as an example.

Pause Between PIDs is more technical. LapTimer requests OBD datain a sequence. E.g. first speed, then throttle position, then rpms. The Pause is simply added between each request. The default 0.01 means 10ms. High values will degrade overall update rate. The setting has been introduced while searching for the reason some wifi dongles lost connection. Actually, the reason has been another one and is fixed.

Both settings should have immediate effect.

- Harry

Thanks! Your info above helps to explain some of the results I was seeing while I was experimenting (I noticed the "speed" of the TX/RX LEDs on the OBD device changed when I adjusted those parameters). I think I need to make smaller adjustments thought based on what you posted.