I recently got a Kiwi2 BT, the iMFD adapter, EGT and fuel pressure sensors and modules to use with Torque. The iMFD stuff works well as do most of the rest of the PCM supplied inputs. However, Torque will randomly lose some of the PCM inputs. I have a Ford 6.0 diesel so I monitor EOT, VGT%, FICM voltages, battery/charging voltage and others, but I mention those specifically because they are the ones that I’ve noticed dropping out. Usually it’s EOT, but battery voltage drops pretty often too. Normally I’ll get the “Faulty OBD Adapter” message, but not always, or at least not right away. I’ve already setup an RMA with PLX to get the Kiwi2 checked out, but I was wondering if this is a common problem with the Kiwi2 and/or if anyone has had experience with the device or company. I know they advertise that their device is Torque compatible.

Bump.

I appreciate the response. I’ll get the log to you as soon as I can. I have tried it with ‘Faster Communications’ enabled and disabled and had the same issue with both of the PLX adapters. At least I think I tried it with both. I never had this problem with my OBDlink MX and there is no question that the PIDs updated much faster with the MX. I also added a new screen and dropped the number of PIDs I was monitoring down to about 6 and had the same problem.

Hi!

Got the debugs, thanks!

From them I did notice that there was an instance of 012F being requested from 7E1 instead of 7E0 (a different ECU), which seems a bit odd and could be the result of an app optimisation that’s done at build time which I’ll need to investigate further. Hopefully I’ll find what is the issue and will get it fixed within the next 2 updates

Edit: ok that above issue is unrelated after looking at it a bit more (though it is still something I’m going to fix). Pretty sure I think I know what’s going on now though as it seems that the bluetooth connection is occasionally dropped and reconnected (I can see instances of LV RESET from the adapter indicating a possible bad connection or under-voltage resets).. I will see if I can improve this behaviour in an update as that does have a knock-on effect to requesting PIDs if it thinks the adapter is being flakey or the bluetooth connection isn’t stable

Edit2: Also looking at this a little further, I’ve noticed you have PIDs that are too ‘big’: ‘22117201’ (this should be ‘221172’ only – which would also cause issues. Torque appends any extras needed automatically. ‘22131001’ is also another one that’s too big and should just be ‘221310’)

Saw there was an update yesterday and that it dealt with some Kiwi 2 issues. Installed it and checked it this morning, but still have the same issue. Within 20 minutes, EOT started reading 32°F. Not sure if this update wa supposed to fix my issue or the other issues you found. Just thought I’d report my findings.

Bump.

OK, made some changes to what I think is happening. hopefully that will sort it out for you – I’m not 100% sure why it’s doing it but I guess that the adapter is glitching or not replying sometimes for the PIDs in question, though I have tried to put a workaround in

You’ll get that in the next beta update (if you’re opted-in) or the next main app update which should hopefully be happening “Real soon now”

If it doesn’t fix it, then a debug of it happening (when it’s stuck) would be invaluable

Whatever you did seems to have fixed the problem. EOT continued to update for my hour and 15 minute drive to work this morning. Previously, it would have stopped updating and went to 32°F within 10-15 minutes.

Update to my update to my update.

It still craps out. Pretty sure it’s got something to do with the iMFD stuff since on a restart, I can get EOT back but lose my iMFD inputs.

ok, can you turn debugging on, and when it ‘craps out’ can you send it to me if you have a chance – there may still be room for improvement on this as long as I can see what’s going on (when I tested it last time I did leave it running for a couple of hours and it seemed fine, though that was on a testbench and not in a vehicle)