JPDiag gets stuck on connecting

[miky94]

hi,
trying to use JPDiag it gets stuck on connecting, some time ago with the same bike (IAW 59M), same cable (OBDLink SX USB Scan Tool) and same computer (Windows 10 running as XP SP3 and administrator) it worked...
port 3 is correct, I also tried with fast unit and with another computer but after I click connect it stops responding, how can I understand where the problem is?
with putty I can connect so it doesn't seem a hardware problem.
thanks

[jpl250rs]

if you uise an elm cable , you shouldn't use kkl settings
click on ?- about and change to elm . the OBDlink use 115200bds by the way

[miky94]

The JPDiag28c.ini file has last modified date 2020 and it worked, I noticed though that the driver version is 2021 and I think is the one from the manufacturer, anyway with elm I can only check the flag for 9600 or uncheck for 38400, which one should I use? And with fast or slow init? A log to see what's going on would be helpful but I didnt' find it.
Thanks

[jpl250rs]

no need to change your settings in the device manager
i patched the exe for you , replace the existing one with this one : https://jpdiag.akress.com/JPDiag28c.exe

[miky94]

Thanks, it worked, is it possible to know the available Services / PIDs and response data structure?

[jpl250rs]

you can use mecodiag for this , it'll list you some PID , ecus ...
there is several function for grabbing PIDS, but other function will not works for sure

[miky94]

I read it works with ELM interface v1.4 to v1.5 but mine is v1.3 so it won't work?

[jpl250rs]

yours is obdlink , it's one of the most advanced elm kind
so no problem at all

[miky94]

I get thie attached error, I then tried jpdiag and it works so no elm or wiring problem

[jpl250rs]

yes the 2 protocols are different .
but if elm stay connected , you can go to passive tab and grab the pid list