Nissan primastar 1.9 dci 2006 says e.c.u unsupported its a uk model ………….told a friend to buy this for his car and try lite thats what happened any ideas ………………………
Another good idea would be if you could screenshot a screen of your car at tickover normal running will all sensors and place on homescreen for refrence ….can this be done?

Cheers he has the full paid version he will have a go many thanks and well done on a top program. Works great on peugeot 107 which has no rev counter selling point for your program as it displays one and a corsa c many thanks.

Hi!

Go into the adapter information screen when you’re connected, and scroll down – there will be a list of sensors supported by the ECU – if there are no sensors listed there then it’s likely the manufacturer has disabled your vehicles OBD2’s Mode 01 PIDs (and it likely supports OBD2 fault codes only for engine/powertrain codes)

The latest update did address an issue for some nissan ECUs replying with the wrong engine address (the original poster never sent the debug but I was able to deduce what the issue was for some nissans)

If you’re not getting a response, then check that the adapter is working on the protocol your vehicle uses (and that it follows the OBD2 wiring properly) 1996 was right on the implementation date for OBD2 so you’ll need to check when the manufacture date of the vehicle not the registration date for if it supports it or not (in the absence of any documentation). If it definitely supports OBD2 then it should definitely work, in which case you would need to look at the adapter

Sorry to bother you again with this message but I can’t figure out what is the weak link here, though I suspect it is the adapter.

The car definitely supports OBD11. Everything connects but almost nothing reports (except acceleration??) in Torque. Whatever acceleration is reporting doesn’t seem to bear much relationship between the squiggly line on the screen and whatever acceleration is being engaged.

It it relevant that the connection sometimes doesn’t connect and often disconnects and starts searching through protocols? Once I saw it report “you appear to be using protocol 3” but more often without finding one that works?

Does it mean anything that I was down at my garage yesterday trying to identify fault codes the ecu is throwing up and we couldn’t link an expensive SNAP-ON OBD11 device into the ECU at all, – but then we grabbed some inexpensive ‘toy’ he had lying around and it connected up without a problem and reported all the error codes

Doesn’t this mean that whatever Bentley has done or what protocol is being used, I should be able to use OBD11 with my ECU?

But even where I can get a stable connection to Torque, when I try to diagnose / look at error codes, the app just returns me to the previous screen?

Sorry, I cant figure out how to get into adapter status through the icon, – I did follow how to get to the adapter, and saw it in the list but when I tap on it, a browser opens and i just get taken to some ebay page!

Unless I am looking in the wrong place, no error messages appear. It is as if the device is connecting, getting into the ECU and then not actually doing anything. Or, the input electronics is working but the output electronics has failed?

No, it doesn’t swipe (either way) it only goes to a browser and opens eBay when I tap the picture of my adapter in SETTINGS (cog wheel on screen) OBD ADAPTER INFORMATION.

Yes, it does say TAP AN IMAGE FOR MORE INFORMATION at the top of that page!

Is there possibily any incompatibility between Torque and the Samsung Galaxy S7 Edge, such that it won’t install properly? I seem to remember that Torque did return some information on my prior phone, – an S3.

No, sorry, I am using Torque Lite!

Does it have completely different functionality?

What, – that it reports results to the screens and can be diagnosed to see if anything is wrong with the protocols when it isnt working?

I think that may be the whole problem. Bentley seems to like to keep protocol information secret!

The software connects automatically. Then sometimes it disconnects. When it does, it searches around protocols and usually doesnt find one. Occasionally it reports that the car seems to use protocol 3, whatever that is. But even then, Torque reports nothing whatsoever!

But the vehicle is OBD11 compliant. Which being the case, I wonder whether Torque Lite should report anything? Surely it should?

Can software report anything if everything connects, and Torque reports that it has succesfully connected to the ECU even though there are no protocols? Torque themselves are reluctant to answer this question, –even where the indications are thatt the software is not at fault but rather that the el-cheapo adapter might well have failed.

The only way I can check any of this is to get another adapter (they all seem to cost the same) and see what happens. I wonder if the 3-4 main types available are all the same inside, or if one is more reliable or compatible than the others?

Torque has said “it likely supports OBD2 fault codes only for engine/powertrain codes)” But they wont say why the program just returns me to the previous screen when I try to see what codes are being reported! So I am left wondering if this program is just ultra-flakey?