Share this post

Link to post

Share on other sites

Whether you need a terminating resistor will depend on the OBD2 device you are using and the wiring distance the OBD2 port is from the ECU. I suspect the OBD2 device does not have a terminating resistor, and that the distance is not sufficient for you to need to install one.

Torque will work with the 'ISO 15764-4' output of the Link G4+ ECU, I tested this last week using Torque. I did find that I could not get this working at a bit rate of 1 MBPS, but 500 KBPS worked well. I let Torque auto detect the protocol.

Share this post

Link to post

Share on other sites

I'm finding even just getting a connection to be very inconsistent, I wanted to try my phone out running torque and the Kiwi3 to eliminate the tablet from being to slow, but it wont connect to the ecu now, and nothing has changed in the ecu settings.

Share this post

Link to post

Share on other sites

I tried my phone again (Nexus 5X android 7) and still no go, i think plx have an issue (torque wont talk to ecu) with android 7, the tablet (nexus 7 2013 android 6) connected fine again and worked.

I was trying to get my phone going to eliminate the tablet from causing the lag, so i tried another way by getting an app running on windows via the Kiwi 3, it looks responsive, I think it points finger at the nexus 7 not being fast enough as certainly doesn't appear to have the same delay. (hard to tell without gauges)

Share this post

Link to post

Share on other sites

I have heard some users have trouble with torque on certain phones. It seems to connect ok for most of our users and I just tried it here on a samsung S5 without drama. Can you borrow another phone/tablet off someone to try?

Share this post

Link to post

Share on other sites

I can't help with Kiwi4 but I've played around with quite a few ODB2 bluetooth devices in the past including the Kiwi3.

The gotcha with the Kiwi3 is that it used "low energy bluetooth" which isn't compatible with everything (which is why some of the other threads talk about working on this device but not that). Seems someone in their wisdom took a working bluetooth spec and split it into a few different versions that don't work with each other.

Cheap ebay Chinese ODB-II devices are hit and miss and I've had a really good one that worked till it randomly stopped.

Don't know where on the planet you are but in AU/NZ the Jaycar ones work well on everything I've tried them on without lag.https://www.jaycar.com.au/obd-ii-engine-code-reader-with-bluetooth-technology/p/PP2145
...and they have a good return policy if for some reason it doesn't work on your setup. They also sell a wireless one that I've not tried but it might suit your setup better if you are using a external GPS or another device on bluetooth at hte same time.

A bit off topic but Race Chrono is a killer app for ODB-II bluetooth. Race track video with odb-ii data overlay, lots of tracks in there or you can mark-out your own. You will get best results using a higher frequency external GPS (10hz) as phones typically use a 1Hz GPS.