Hi!

I have had only moments spare recently to post and check various things were working, apologies for this as I have been trying to get time to sort some other parts of the app out as well (and things got a little busy for me recently)

I have done some preliminary work with ConsultBT, though the person I was last working with (via email) is no longer responding, so never got as far as testing the code that was put into the app

In the ‘protocol’ part of the vehicle profile (if you’ve chosen the nissan protocol, beta, etc, etc) then you’ll be talking to the consult adapter properly

In that case, it means the code I put in works! Though I may need to tweak it for some more sensors on your vehicle (though I don’t know what’s available)

Can you send me a debug of it working (tag it as ‘consultBT’ in the box that pops up so I can locate it and I’ll have a look to see whats supported of if there can be improvements made

You can send a debug by enabling debugging in the settings, then restarting the app. Connect, poll a few sensors, then go to the realtime information screen, press menu, send debugging information, and type ‘consultbt’ in the box that pops up.

That’ll send me a debug so I can then see the comms session between the ECU and vehicle (and a load of app debug) and I’ll hopefully be able to get more working for you if your vehicle allows those sensors to be read

I have tried what you suggested except for the polling of sensors. It is not connecting to the ECU at all and I assume it needs to be connected to the ECU to do a sensor poll. Do I need to use the nissan init string in the wiki or just the consultbt protocol? I have sent a debug through anyway and am hoping there is some information in there for you to work with.

Is the testing something I can help with?
I also have an OBD11 adaptor and the OBD11 to Nissan 14 pin plug if that is any help in the testing.

Hi!

I’ve sorted the various bits out that needed adjusting, and hopefully the update will be out tonight or tomorrow night at the latest (You’ll see it appear on Google Play when it’s released). I have some more testing to do first before I can send it out to make sure some of the other changes are working properly

When will the update be ready for download?

Hi nothing seems to have changed. I have sent through two dubugs for you to look at. Would the nissan init string do anything or is that just for obd2 compliant vehicles.

I’ve tested the latest version of Torque with the Consult BT adaptor – it connects a little quicker than before but ultimately drops the ECU connection as soon as the first amount of data begins to be streamed.
Using an R32 Skyline GTR RB26 ecu

-D

Hi Ian, I just ran Torque for a little run and I did get a couple of sensors responding, they just weren’t logging the information fast enough and kept dropping out. I had throttle position and speed dropping in and out and a constant coolant temperature reading with very minimal dropouts. The mass airflow rate is showing green as if active but isn’t changing its reading at all. There are a few other parameters that have worked, the trip distance, trip time etc.
I have sent through a debug with Consult BT E50 Elgrand as its title and will do another run shortly to send another debug through.
Sorry for the late reply.
Thanks,
Rob.

Hi Ian,
I am just wondering when the next update will be ready. I am eagerly waiting to get Torque running properly.

Morning!

Looking at the debugs this morning, thanks for sending them as it gives me a good insight into what’s going on

It still seems like it is stopping responding after a sensor request, the adapter doesn’t reply, so I’ll concentrate on that for the next update (1.8.99 as 1.8.98 is in beta) and I’ll see if I can sort this out. Hopefully it’s something small (it usually is) though it may take a bit of two/fro before I can understand the issue fully (as I don’t have a consult vehicle here to test with)