Hi
My car is Nissan Sunny 2013, engine 1.5 HR15DE. I purchased ELM327 bluetooth from BAFX and install Torque Pro 1.8 in my Nexus 4. The Bluetooth connecting are ok and I have successfull check for ODB2 information with other software such as DashCommand, ODBII-Elm327…

When I try to connect with torque pro, software is alway using protocol 15765-4CAN11/500 to connect and send the error “ECU reports no PIDs supported”

Could you please help to sovle this problem?

Hi

What country did you purchase the vehicle in?

Hi
Below are some screenshots I took from another software that have success connected and read ODB2 information from my car.

ODBII Scan Master detected that there are two types of ECU: E8 and E9

ODBii-ELM 327 Car Diagnostics (free and simple software) can connect and read some basic information such as engine RPM, speed…

ODB Car Doctor Free can read also

And Dash Command Pro can have very good dashboard

All above softs use ISO 15765-4 CAN (11/500) to connect to ECU.

How ever, as said, I am still want to use torque because of friendly GUI and plugins. Please help me to fix this issue

Quote from cintakc on November 25, 2014
Try a terminal (Elm Basic and other) program file manually team and see the answers from the unit ECU
https://yadi.sk/i/8sQDhDzZcvGW9
https://yadi.sk/i/2jDrX9BqcvGWM
https://yadi.sk/i/daMVQ8F6cvGWT

Which software did you use for those image cintakc? I try to search ELM327 Chat application but didn’t search out yet.
Below are result which your suggestion commands, using elmbasic. Don’t know why my ECU only return 7F 21 80. What doest it mean?

I forgot to write, after the team ATAL, give the command 10C0 is the initialization command communications, then 2181, 2183, 21FE

13:21:31.961
01 00\r
01 00\r7E8 06 41 00 00 00 00 00 \r7E9 06 41 00 98 18 80 13 \r\r>

Hi Torque developers

As showed above, my ECU returns two values for 0100 request, the first one doesn’t contain any pid. Should this be a root cause of problem that Torque can not detect any PID supported?

Hi Cintakc
I try to add the custom init string into torque but no luck. Could you please advice of what should I add to tell torque reading 7E9 ECU?

Below are several init string I have tested:
ATSP6\nATAL\nATSH7E0\nATCRA7E9 : this case torque can connect to my ECU but the status is “checking model…” for too long time (5 minutes, can’t wait more)

ATSP\nATAL\nATSH7E1\nATCRA7E9 : this case torque even cannot connect to ECU and the blue car icon keep blinking

I don’t know how exactly step that torque did to read the supported PDIs but when I tried with elm basic, it is quite simple with few at commands as below:

AT Z\r
AT Z\r\r\rELM327 v1.5\r\r

AT E1\r
AT E1\rOK\r\r

AT H1\r
AT H1\rOK\r\r

AT SP 6\r
AT SP 6\rOK\r\r

01 00\r
01 00\r7E8 06 41 00 00 00 00 00 \r7E9 06 41 00 98 18 80 13 \r\r

Please help for the correct INIT string

It ‘s typo mistake, I actually set the init string to ATSP6\nATAL\nATSH7E1\nATCRA7E9 and the blue car icon kept blinking forever.

But… great hint from you, I have found a work around to solve my probelm. I created a custom extra PID with Diagnostic stop command: ATCRA7E9. So after added a display of new PID in Realtime Information plugin, torque read ECU again and success connect to corrected address I want.

This is work-around solution only because if I don’t open the realtime information plugin, torque will not read the address 7E9. So I still need torque team give out the longterm solution

Again, thanks a lot for your hint cintakc

I have some solution for HR15DE engine for year 2013 and above, with my nissan livina (in Indonesia) please reply into this post if u need responses from me, to make sure this thread still active

Hi!

I’m going to look at this in the next couple of beta to see if I can get it sorted – the main issue is that the engine ecu address is replying with 0 pids enabled (though another ECU is replying with some enabled). It should be possible to sort out with ATCRA 7E9 in the custom init and the atsh 7e1, as pointed out above, but it seems something may be stopping it from working properly

Edit: I’ve made some changes which will be in the next beta which should now fix this (beta .182) which will be out in a day or so – you’ll need to join the beta to get this update if you haven’t already done so