JPDIAG slow to respond/unresponsive

[jp129]

Hey all,

I am wondering if anyone else has experienced JPDiag software being extremely slow to respond or inconsistently becoming unresponsive?

I am trying to use JPDiag on my 2002 Monster S4 with 59M ECU, but have been experience the scenario above. Sometimes the data outputs realtime, but more frequently than not the program stops display the data real time or become unresponsive.

I've followed the step by step guides to the T. If it makes any different, I was able to use the exact same setup (cabels, software, drivers) on a friends 2006 Monster 620 with no issues. It didn't hiccup once (data was realtime, all the time).

Any ideas? I would greatly appreciate any and all feedback.

[jp129]

Any ideas? I am beginning to have a gut feeling that something may be wrong with the ECU... Any ideas to confirm my theory?

[brad black]

put a charger on the battery while you're doing it.

[jp129]

I will give this a try today. Thank you for the suggestion.

[bagodoosh]

i have a similar issue with a 2003 620 (59M) ECU. i have the FTDI KKL cable + fiat adapter.
i charge the battery while using JPDiag. i've used win7 (64b) including run as admin, and xp compatibility mode, xp mode in win7, and a real win xp (32b). it behaves the same way: connect via slow-init. takes a while to connect. semi-real time in the beginning and then (after 5-10 seconds) it goes limp: data does not update. the app itself is almost unresponsive. the only way to get around it is disconnect, turn ign off, turn ign on, [re]connect.

a peculiar thing happens in win7 in that if i kill the app in this slow/unresponsive state, windows kills the UI but the process (jpdiag28a.exe) still hangs in the background (task manager). attempting to kill the process says "access denied". the process remains in this hung state, locking the COM port, essentially requiring a reboot.

another weird thing that sometimes happens (so far noticed it only in win7) is that the main window keeps becoming active and pops up, over other open jpdiag windows, every time it "updates" - which is every few seconds.

it may be a timing issue with the (slower?) 59M ECU. i'm still fiddling around with it.

[jp129]

i have a similar issue with a 2003 620 (59M) ECU. i have the FTDI KKL cable + fiat adapter.
i charge the battery while using JPDiag. i've used win7 (64b) including run as admin, and xp compatibility mode, xp mode in win7, and a real win xp (32b). it behaves the same way: connect via slow-init. takes a while to connect. semi-real time in the beginning and then (after 5-10 seconds) it goes limp: data does not update. the app itself is almost unresponsive. the only way to get around it is disconnect, turn ign off, turn ign on, [re]connect.

a peculiar thing happens in win7 in that if i kill the app in this slow/unresponsive state, windows kills the UI but the process (jpdiag28a.exe) still hangs in the background (task manager). attempting to kill the process says "access denied". the process remains in this hung state, locking the COM port, essentially requiring a reboot.

another weird thing that sometimes happens (so far noticed it only in win7) is that the main window keeps becoming active and pops up, over other open jpdiag windows, every time it "updates" - which is every few seconds.

it may be a timing issue with the (slower?) 59M ECU. i'm still fiddling around with it.

Looks like we have the same issue. You should give GuzziDiag a try. See status report below...

Status report:

I hooked up a charger to the bike while I was using JPDiag and that did not resolve my issues.

Based on another suggestion, I tried using a USB hub between the cable and my PC and that seems to keep it from locking up completely, but is still extremely slow to respond.

On a different note, I was able to get GuzziDiag 4.2 to communicate with the ECU to get the telemetry from the bike. However, I cannot get the CO trimmer to work with the ECU.

My ECU has the trimmer set at -5 and the CO adjustment in GuzziDiag is complicated.

With the bike on, I'll navigate to the CO Trimmer screen, when I click the + or - sign to adjust the trimmer I am greeted by a prompt saying that the engine needs to be off. I shut off the bike then go back to key on position, make my adjustment, then click start, I am then prompted saying to turn the bike back on. I turn the bike on, then click the finish button. No indication whether the adjustment took or not. I then navigate back to the measurement window where it seems to have stopped real time communication. I disconnect and reconnect, and once the telemetry goes live, I see the CO trimmer field still at -5. I am still at a loss. Looks like I am still SOL...

[bagodoosh]

i had tried guzziDiag before but i did not see a bike with 59M on its list. i assumed that it does not support my bike. after seeing that you had succeeded, i just went back and connected to "Breva 850".
initially it listed the ECU as "IAW 5AM PF1C", however after connecting it shows "IAW59MHW010". this did not happen when i chose "California x?" for a bike, which has "IAW 15M PF3C" ECU.

to be honest, this has a much nicer interface. i will fiddle around with trim next.

have you tried adjusting the fuel trim with jpDiag in that initial 5-10 second window when it is kinda-responsive? after connecting, head to trim window, change value, [test], [confirm].

[bagodoosh]

i just messed around with the trim in guzzidiag and the setting sticks.
i think your error is procedural. here's the way i did it:

• run bike until temp >40C; turn IGN OFF
• bike:IGN ON; GuzziDiag:Connect, go to View>CO Trim (it'll say bike must be off, click [OK]), click [Start] (it'll say start the bike); bike:press starter button (on my bike the starter button becomes inactive about 15sec after IGN ON, so i have to be quick about this step)
• adjust value
• click finish
• at this point the value should stick; verify by going to View>Measurements to check "CO Trimm" value
  
• final verification -- GuzziDiag:Disconnect; bike:IGN OFF ... IGN ON, GuzziDiag:Connect, check "CO Trimm" value

[brad black]

generally any 5.9m and 5am interface works for either.  although the mts 620/1000/1100 tps reading is always really wacky, it's offset and is nearly at ffff (65535?) at wot.

guzzidiag has seemed very good ime.

[jp129]

i just messed around with the trim in guzzidiag and the setting sticks.
i think your error is procedural. here's the way i did it:

• run bike until temp >40C; turn IGN OFF
• bike:IGN ON; GuzziDiag:Connect, go to View>CO Trim (it'll say bike must be off, click [OK]), click [Start] (it'll say start the bike); bike:press starter button (on my bike the starter button becomes inactive about 15sec after IGN ON, so i have to be quick about this step)
• adjust value
• click finish
• at this point the value should stick; verify by going to View>Measurements to check "CO Trimm" value
  
• final verification -- GuzziDiag:Disconnect; bike:IGN OFF ... IGN ON, GuzziDiag:Connect, check "CO Trimm" value

Thank you for posting your procedure and results. I will give it another try and report back.

[bagodoosh]

jp129,
another discovery today: during the "adjust value" step, you can switch back and forth to the "measurements" screen -- to read the RPM, injector timing, etc. however, because of what i consider a bug, every time you come back to the "co trim" screen, you will encounter the "the engine must be off" pop up, which should be ignored.

brad,
while you are here, i have a few questions after reading your fuel injection article:

regarding the "trim factors - injection", it seems counter-intuitive to remove fueling from a hot engine. wouldn't running lean make the engine run even hotter? why would there be negative coolant trim for 89C+ ?

while tuning the CO%, wouldn't the CO value lower (lean out) over time, since the bike is just sitting there getting hotter? you mentioned "some have negative trim for when the coolant temp gets over 89 degrees). the 620 service manual says to make sure the engine temp is above 65C. then it should really say make sure the engine temp is between 65-89C (or wherever the particular mapping has 0% coolant temp trim). yes?

i observed that the bike goes thru a warm-up enrichment cycle even though the engine temp is warm. this was not covered in your article. what i mean is.. engine temp is at 70C, bike is turned off, and immediately restarted. the ECU seems to force a rich condition, as observed by high CO% readings. this will last for maybe 10 seconds. what is the purpose for this?

[jp129]

jp129,
another discovery today: during the "adjust value" step, you can switch back and forth to the "measurements" screen -- to read the RPM, injector timing, etc. however, because of what i consider a bug, every time you come back to the "co trim" screen, you will encounter the "the engine must be off" pop up, which should be ignored.

brad,
while you are here, i have a few questions after reading your fuel injection article:

regarding the "trim factors - injection", it seems counter-intuitive to remove fueling from a hot engine. wouldn't running lean make the engine run even hotter? why would there be negative coolant trim for 89C+ ?

while tuning the CO%, wouldn't the CO value lower (lean out) over time, since the bike is just sitting there getting hotter? you mentioned "some have negative trim for when the coolant temp gets over 89 degrees). the 620 service manual says to make sure the engine temp is above 65C. then it should really say make sure the engine temp is between 65-89C (or wherever the particular mapping has 0% coolant temp trim). yes?

i observed that the bike goes thru a warm-up enrichment cycle even though the engine temp is warm. this was not covered in your article. what i mean is.. engine temp is at 70C, bike is turned off, and immediately restarted. the ECU seems to force a rich condition, as observed by high CO% readings. this will last for maybe 10 seconds. what is the purpose for this?

Very appreciative for you to post your findings. I was busy getting O2 bungs welded on my exhaust today to use my wideband, so haven't had time to mess with GuzziDiag. I will work on this tomorrow morning.

[jp129]

Status report:

I gave JPDiag another try and I just can't make it work for me. I have given up messing with JPDiag.

GuzziDiag works as far as telemetry is concerned but the CO trimmer is more complicated than it needs to be.

My OBD2 Bluetooth device came in and I gave Scan M5X a try. It works BEAUTIFULLY!! Everything works as it should and I can do all of this using my Android phone instead of a laptop. I find it very simple to use and intuitive. If you guys haven't given I try, I highly suggest it.

Here is the bluetooth adapter I ordered: http://www.amazon.com/ELM327-Bluetooth-Diagnostic-Scanner-Scantool/dp/B0051CAE1C

You can download the App from the google play store, Scan M5X all-in-one datalogger.

[bagodoosh]

i searched for Scan M5X, and found a link for the windows version called ScanST. ultimately the URL redirected to here. it's supposed to work with the VAG KKL cable but i have not tried it yet.