the usb port doesnt matter. COM3 is a virual port created by the lonelec cable. as long as the COM port in the device manager and the port in iawdiag match ads the ignition is on (doesnt need to be running) it should connect try slow init first
Both are on Com 3 so that's good. I hit "Connect" and it tells me turn ign on and press OK - all good Then 2 seconds later it tell me to turn ign off !! As per instructions I have changed the Latency Timer to 2 - no change - still as above. I then reduced Recieved & Transmit Bytes from (as found) 4096, first to 2304 then 1408 but still no changes. I must be so close !! Many thanks for your help funkatronic !!
I’m watching this with interest. On the last 2 or 3 rides mines also developed a cut out, similar to a rev limiter at 60-70 mph. ( new crank position sensor fitted with air gap and TPS reset )
Did this "new crank position sensor fitted with air gap and TPS reset" cure your problem itsamonster ?
sorry you are struggling. this setup works pretty reliably usually. you definitly have the loneelec croc clips on the right battery terminals (i think the cable lights up an led ).
Unfortunately not. The TPS reset gave a better idle. Without hijacking your thread, i’m wondering if my new crank position sensor needs a smaller gap. I even ground my thinnest shim down a bit. The thing i’m unsure about is the new sensor has black plastic sealing the end, whereas the old one didn’t. I’m thinking the plastic thickness ( even if it’s 0.3 mm) will alter the gap needed to the metal pickup inside the sensor. I could be talking rubbish though!
Cheers funkatronic, yes croc clips all good and both systems on Com 3. I've deleted and reloaded IAWDiag but no change. I'm sure that the lead side is OK but the IAWDiag is not seeing it. I've sent a message to Lonelec to see if they have any ideas - fingers crossed. Any ideas @chrisw ?
without seeing your setup its hard to be sure . but could it be that the lonelec drivers are not installed properly and COM3 is another internal port(vitual or physical) . if you unplug the loneelec cable and open device manager. does COM3 dissapear?
v,similar symptoms i had with my 2007 fugly 1100. if it uses the same ECU it could actually be a starter motor fault. next time it happens and it starts with a bump start but not of the starter (even tho it turns over fine) have a wee think about replacing it.
No yet, still waiting for Lonelec to get back to me, they are checking that their lead is compatible with the S2R !!
it is, i used it on mine. can you try another laptop? i have the software working on some really old machines
I've got a smart phone, might try that ?? ( but it has'nt got a USB Port !) I'll try and get the old laptop working too
Cheers Turbogeek, I've got Com 3 on my device manager for the lead and on the IAW Diag Is IAW P7 PF09 correct for a S2R, there are no other options that I can see on IAWDiag ??
Chrisw - you are a star !! I changed IAW P7 PF09 to IAW 59M PF09 and we are in !! I have some fault codes, one or more of which is probably the answer to my problems !! PO 335, no signal (crankshaft position sensor A circuit) PO135, lambdasonde heizung links no signal (lambda probe heater left no signal ) P0500, to high ( speed sensor A) u1600 invalid signal ( imobilizer signal) So I guess that I need a new lambda probe and maybe a crankshaft position sensor. I found the codes on https://www.desmo-racing.com/en/code-list-dtc-ducati-pxl-26.html Many thanks to all who helped out and I'll keep you posted
the po335 is the most relevent code to your fault. personnaly i would deleet all codes then wait untill you see what comes back.