To avoid the ECU timing out whilst things connect the method I use is to set correct Com Port, select correct initiation speed (slowinit or fastinit), press connect and then switch ignition on. I also recommend that the black fly lead is never connected to the negative battery terminal. Instead connect it to a good earth on the engine or frame. By doing this you will avoid polarity inversion which can damage the ECU.
Thanks ChrisW Did you see my comment- "Could it make any difference if I connected the cable to a separate battery, not the bike one? I noticed that if I plug the cable in to the bike then connect the battery Crocs, the indicator LED on the OBD connectors illuminates when just the +ve Croc is connected before the -ve Croc is connected." Interested in your comments on that. Thanks so much.
There are two types of Fiat adaptor (1 x red fly lead or 1 x red/1x black fly lead). Both will work and the OBD cable will power up. As JPDiag developed it was found the two fly lead type provided more stable connection to the ECU. Bike battery or separate battery, both work but separate exposes the ECU to polarity inversion.
Thanks Petsmith and ChrisW I need to get this annoying work thing out of the way today so I can have another try at connecting later on.
Nasher, In addition to the informed help on here, the following link might provide some supplementary background reading. http://vinniesducatis.com/JPDiag-Gouge.htm . Hope it helps without confusing the issue! Good luck. Tom.
I’m sure that for no other reason than to stop me moaning about it, you’ll all be glad to hear I’ve now managed to connect to the bike. All those who took the P155 about this being a technical thread, strangely located in the technical section which they were reading, can stop reading now. But for the benefit of anyone else struggling who finds this thread in a search I’ll detail how I got there. I gave up on my old Windows XP Laptop. It’s at least 12yrs old, it’s a bit cranky, and despite recognising and giving me a COM port for the cable, JPDiag just reverted to Connect a few seconds after pressing the button. I know I’ve used it to connect to my M1000 and 1000SS in the past, and it must be seeing the ECU as I wouldn’t be getting as far as a Green Bar. So I grabbed Lady Nashers Laptop again, much to her disgust as she really doesn’t want me using it in the garage. I uninstalled and downloaded JPDiag again, plugged the cable and adaptor in, checked the COM port, reinstalled the cable drivers from the Lonelec website and checked everything was good to go: Knowing I’d connected to my 1000SS with this Laptop and cable before I tried it first, but couldn’t connect, I left it connecting for at least 3 minutes a couple of times. Note that being an IAW59M ECU Slow init needs to be selected and no ECU License is required. Thinking about what could be different from last time I connected to the 1000SS I removed the license file for the 999 ECU from the folder where the JPDiag exe file is stored, tried to connect to the 1000SS again, and connected within 10 seconds. Hooray! Flushed with that success I put the license file back in the folder, changed the setting to fast init for the 999s IAW5AM ECU, and tried to connect to the 999. Again, straight in within 10 seconds. Note on both bikes I pressed the ‘Connect’ button and then turned the bike ignition on. Hooray again. I then had a look at the error codes using the DTC function I’m not at all worried about the above list at this stage and just cleared them. The bike has not had the codes cleared in many years and has been run with lots of equipment disconnected more recently, so I’ve no idea what is and isn’t still relevant from that list. The Engine management light is now out with the ignition on, but as it was gone 23.30hrs by this point for my neighbour’s sakes I didn’t start the engine to see what pops back up. That is hopefully going to happen tomorrow now when I can get it running and fully warm it up for the first time.
Thanks for posting Simon, and good that you persevered and got your reward for that. I'm sure the above notes will be useful to others if they manage to find it at the relevant time.
Good you sorted it. This is one of the "near tech" items that I am cancelling as it is so unstable. The reasons for this are well known and understandable. Considering its free it is comfortably top half of the table. On its own, this could be sorted and accepted but next to all the other near tech in my life it has to go. I most certainly would not be flashing any CPU’s with this combo
Yes Johnny, we should all remember JPDiag is free of charge. As a comparison the 3rd party equipment and software to admittedly do a lot more to my 65 plate discovery runs into @£400. And is a similar cost for my Mercury Outboard. I also have a good quality generic OBD reader for other vehicles that was @£100. Cheaper ones can do almost as much though. To use JPDiag I think the cables were @£10. I suppose I should ask, what are the alternatives to JPDiag for those of us who want to be able to do stuff at home? Read and clear codes. Reset TPS Interrogate live data Clear service indicator Upload maps Etc And I've seen there is a later version of JPDiag, called Melcodiag, that is aimed at later bikes. How does that compare?
Hi Nasher So, if I understand this correctly, to connect to the 59M ecu you just removed the licence file from the JPDiag directory? If so this would explain the problems I encountered.
Yes, for the 1000SS, not the 999. ChrisW had sorted me out a license for the 5AM ECU in the 999 and I'd put it in the folder where the JPDiag exe file was located. It needs to be there to be able to access all the features of JPDiag when connected to a 5AM. The license is ECU serial number specific. The 59M ECU doesn't require a License, but in my case the 5AM Licence was in my JPDiag folder when I tried unsuccessfully a couple of times to connect to the 59M ECU in the 1000SS. It could be complete coincidence, or something specific to my Laptop/Cables/ECU, but as soon as I removed the 5AM Licence from the folder I was able to connect easily to the 59M ECU. I then moved the License back to the folder to connect to the 5AM in the 999. I'm not saying it would work for everyone, but it made all the difference for me. Did you have a 5AM License in your folder when trying to connect to your 59M?
Thanks ChrisW. It certainly did appear to stop me connecting to the 59M in my 1000SS. But as mentioned it could just be my setup. Worth a go for very little effort if struggling though.
HI Nash, I would gladly pay 400 for something that worked to any recognizable level of reliability. I recently binned my BMW Connected drive as it works for a while until you start to rely on it then.. They want 50 quid a year for partial connectability
Hi Chris Agreed. But I struggled to connect to the 59M and it when it did was very slow and flaky. No such issues when connecting to the 5AM on my Monster. Next time I use it I will try removing the licence file as Nasher did.
Chris, I'm really sorry, you know how much I appreciate your help and guidance with this, but I've just been and had another play and the License for the 999 5AM ECU would appear to be stopping me connecting to the 1000SS 59M ECU. I connected to the 999 with no issues at all. So disconnected and went straight over to the 1000SS and plugged in. The only change I made was to tick Slow init instead of Fast init. I tried 3 times to connect unsuccessfully, but then when I dragged the 999 5AM Licence out of the folder on to the desktop I got in on my first attempt. I disconnected and got back in again. But when I then put the 999 5AM Licence back in the folder I could not connect to the 1000SS 59M ECU. Taking the licence back out enabled me to connect. I'm assuming that the process of moving it is actually having an effect, rather than the actual non-presence of the file.
Yes indeed , and there are many good posts in this thread ( which I have just bookmarked ) . Sharing the knowledge ..... that's what I like What can I tell you ? " If you can't keep up with the big dogs ..... stay on the porch "
