OBD logging and real-time histogram

[kur4o]

Have no clue where is the problem in tunerpro, in patch or in both or vehicle doesn`t support AFR the way we know it. At least for sure there is some data sent on the target afr, so patch kind a works.

I think only manual troubleshooting can find the problem.

Sending some custom commands with stnterm.exe can give more clues what is not working.
If you are willing to try I will get you some commands.

[woody80z28]

That kind of thing is above my current level of understanding, but I'm willing to learn it.

[kur4o]

Here is the stnterm.

Upon starting select the comm port and baud rate of the elm device. If you are unsure of the comm port open device manager and see the number there.

Pressing the ATI button will get you the elm id.
When you are sure you have good communication with the elm device, send ATSP 2 . This will set the protocol to j1850 vpw.

Now you can send custom request to pcm. Like requesting different pids.

To request mode1 sae pids type

01xx

01=mode
xx= sae pid number 01-ff

To request mode 01 pid 1c simply send
011c and you will get the result.
If you get a 7f reply, this means that the pid is not supported or the request is in invalid format.


To request enhanced pids you will use mode 22 requests.
the format is

22xxxx01

22=mode
xxxx=pid
01=??byte count request?? not sure on this but in most cases 01 will do the job.

So 119e pid can be requested by sending

22119e01

Let me know how you are coping with this so we can get to level2.

[kur4o]

To get mode22 working you might need to change the header first.

send

ATSH6C10F0

After that mode 22 requests should work fine.

[woody80z28]

Ok, I got the COM and baud figured out COM5 and 9600. I know ELM is communicating because I connected in TunerPro and then closed out. I even unplugged and replugged after closing TP to make sure it wasn't "busy" before opening stterm.

Key on, engine running: I send "ATSP 2" and it shows in the list red with no response. Same thing with PIDs I tried: 0112, 0107, 010D. What am I doing wrong?

[kur4o]

Pressing any of the built in button does it return a reply. I am sure it is set for different baud rate stock, so try all of them until you get a communication from the tool.
You can try sending it without the space: atsp2. Before opening make sure the bluetooth is paired and the com port is not used by other software.

Ignore tunerpro settings since it can request different baud rate. 9600 is extremely slow, try upping it to 115000 in tunerpro and see if it connects.

[kur4o]

Found that some of the later version of tunerpro supports 2 bytes pid requests. I will give it a try and hopefully it will work.