Hi!

I’ll have a look at this, though this one might be a little difficult (from my end) to fix, I will have a try and see if I can put something into the next beta if I find anything

What is the custom init you’re using at the moment? – is it one of the honda ones?

This might be the USB device being cut off by the Head Unit when the unit goes to sleep.

installed latest version tonight – unfortunately, still same trouble.
I have seen at least once that in status line it has changed from “applying custom init” (not sure about wording – it was translated) to something different and late again to “custom init” but it couldn’t connect.
Restarting torque – and connected in less than 3 seconds.
Anything that i can help with? any log file, screenshot, video?

Hi!

Vasilich:

Hm – I’ll need to look into that a bit more then as it might be the USB init code having trouble talking to the adapter – this is possibly due to the way the headunit starts up. I’ll have a look to see if I can get it ‘stuck’ over here and will then probably put any fixes into the next beta if I find anything

Lakisdj:

If you uninstall and reinstall you’ll need to tell Torque to use the USB adapter instead of the bluetooth device (if you are using USB)

Got a similar (same?) issue. If I turn on the lights from my remote, the device wakes up or something, and I have to remove the device and start pairing again with the program turned off.

Using a Obdlink MX.

If I unlock the car with the phone in range, it almost always works as it should.

Is there any way to reinitialize USB device/port in the app without restarting the app?

Tested it a bit more. Clear steps to reproduce:
1. OBD adapter has power, but ECU is off (my adapter get its power not from OBD but from external ACC wire). In that mode torque cannot connect and this is normal. Note that HU was awake already for a long time, so USB should be already initialized.
2. Switch on ignition, so ECU has power and can respond. Torque cannot connect – here we have problem.

It has nothing to do with HU wakeup from snandby or other USB initialisation things – i can reproduce it even after torque has been connected: just switch ignition off (so that OBD adapter is still powered, but cannot connect to ECU), wait some seconds until torque loses its connection to ECU (car icon in status bar starts to flash), and then switch ignition back on.

To get torque to connect again:
1. either restart app
2. or go to “edit profile”, do not change anything just press “save” and go to dashboard – torque gets connected.

Saying this i just want to point your researches in a right direction in a hope that it can be fixed soon

Ian, do you need more details from me on how to reproduce this bug? Have you been able to reproduce it at your side?

Hi!

When it’s “Not working” are the TX/RX lights on the adapter(if it has tx/rx lights) flashing at a slower rate still indicating communication or very infrequently?

Hi!

OK – last thing to test (which will tell me the best way to recover your connection when it’s in that state)

When it is “not working”, Can you switch vehicle profiles (and then switch back) which will force the connection to be reset (without restarting Torque itself). If you could let me know if it starts working if you do that then I can probably come up with a workable solution

Hi!

Ok, think I know where this is now – one more question:

What PIDs are you using, are you using any of the standard OBD2 PIDs, or are you using extended PIDs only? (what does the Adapter Status ‘supported sensors’ screen say for supported sensors?)