guzzidiag to ecu comms issue

Hi Guzzistas

My 2008 GRiSO has a problem connecting Guzzidiag to the ecu, and I'm after any pearls of wisdom, but first some salient points, to tease your brains. Don't let my seeming expertise fool you, if I had a clue, I'd have fixed it already ... right ?

Salient points:
* I'm a experienced electronics tech with backgrounds in embedded, data-comms, wireless, instrumentation and automotive electronics over the last 45 years.
* The exact same gear worked 100% on a MG Bellagio, and connected easily every time, but I don't have access to scope it for a comparison at the moment..
* gear is a Linux Mint laptop with the recommended dongle and adaptor on this forum.
* the problem is exactly the same under windowsXP on another pc
* I have scoped the K-line ISO9141-2 signal on my GRiSO, and even have color pics!
[You must be registered and logged in to see this image.]

* Minimum bit width is about 100uS which gives around 10k baud by my estimation. Both the K line data from the PC and the response from the ECU are the same bit widths and so the same frequency I think.
* The K-line signal looks good and is at battery voltage when high and near enuf to 0v when low. No ripple or crap that I can see.
* the comms sequence looks classic ISO914i-2 to me with a  25ms low following bus idle, a 25ms high wake up, the start comms message from the PC, a pause then the ecu response. The data is exactly the same every time regardless of the delay when turning on the ignition
after hitting the start menu button in Guzzi Diag.
* Pins 4 and 5 are both connected together in the dongle, there is no 0 volt or earth problem.
* It connected once after about 10 million attempts (ok, not quite 10 million, but a lot!) and I downloaded the MAP, viewed the data while the engine ran. After that it would not reconnect again.

When I started on this tonight, I was sure i'd find a broken wire, or a crappy signal (Italian electrics right?) but everything looks good, which begs the question .....

What's wrong ????

Oh, the Guzzidiag error is always "ignition switch is off", but trust me, it's not.

Cheers
Terry

Hello
Oh !
I am not specialist sorry, but ......if you want to try

Others points control
stop scanner virus
Port com
reinstall cable drivers and software

If cable is bad, see other cable.
[You must be registered and logged in to see this link.]
This cable is sure for communication ecu / FTDI chipset FT232RL
[You must be registered and logged in to see this link.]


Do you try for your communication cable AdapterTest V1.01
[You must be registered and logged in to see this link.]
Do not connect the cable to the ecu taken during test !

[You must be registered and logged in to see this image.]

It either a flaky OBD cable, or power/grounding. Check your ECU ground.



.

[quote="beetle"]It either a flaky OBD cable, or power/grounding. Check your ECU ground.




Thank you Sir Beetle, you were right again ... problem fixed, schematics in jpg and pdf below.
GRiSO obd2 adaptor cable mods
GRiSO obd2 adaptor cable mods PDF

Good job.

beetle wrote:

Good job.

Ta!
I've read many GRiSO suggestion online, i.e. start Guzzidiag first, wait x seconds then turn on ignition, and so on. I guess the wrong adapter cable (not the OBD2 to USB interface unit) is the main problem ?

Now the wiring is correct, I can turn on the ignition, connect the adaptor, and start Guzzidiag or start Guzzidiag then turn on the ignition, it doesn't care and connects flawlessly each time.

Same with the iaw5xreader, works flawlessly now.

Now I can purchase one of your maps, and get the nice new C kit fitted thanks to Pete's excellent online instructions:)

I have a 'Agostini' muffler fitted, which map would you recommend, the one without the dbkiller or the one with the dbkiller ?

Nah, doesn't matter which way you do it. It is helpful for the less nerdish of us to have a sequence to work with. Creates less angst. 99% of issues are cable problems.

Hmm. I haven't made an Agostini without dBk. Only X-Black or Megaphone.

beetle wrote:

Nah, doesn't matter which way you do it. It is helpful for the less nerdish of us to have a sequence to work with. Creates less angst. 99% of issues are cable problems.

Hmm. I haven't made an Agostini without dBk. Only X-Black or Megaphone.

Oops, my mistake, well that makes my buying decision a lot easier ;-)

Terry, there is something wrong on your GRiSO wiring, switched connection to the 3p superseal?

It should be on the GRiSO

1 nc
2 grnd, blue
3 k , yellow/black

You have that different on your drawing.

pauldaytona wrote:

Terry, there is something wrong on your GRiSO wiring, switched connection to the 3p superseal?

It should be on the GRiSO

1 nc
2 grnd, blue
3 k  , yellow/black

You have that different on your drawing.  

Hi Paul,
You're very observant

I noticed it was different to the GRiSO schematic I downloaded from the Web but I drew my schematic from the connections as they are on my (second hand) GRiSO.

This is a pic of my 3 pin ECU Diags  connector, I wonder if it was changed by a previous owner, or the guzzi schematic is wrong ?

Can any 2008 GRiSO 8v owners confirm if the wiring on my GRiSO ECU Diag plug (below) is different to the one on their bike ?

[You must be registered and logged in to see this image.]

Terry, doesn't look right - all 5AM ECUs have the same connection. Blue wire should move to the middle.

It could also be the cable, I had that issue some time back. It would work with GuzziDiag hard wired to my laptop but de damned if I could get it to work on the OBDII bluetooth dongle. Mark found the issue when we were trying to do some logging. Ended up buying a cable from Lonelec in the UK - hasn't missed a beat since.

Oz1200Guzzi wrote:

Terry, doesn't look right - all 5AM ECUs have the same connection. Blue wire should move to the middle.

It could also be the cable, I had that issue some time back. It would work with GuzziDiag hard wired to my laptop but de damned if I could get it to work on the OBDII bluetooth dongle. Mark found the issue when we were trying to do some logging. Ended up buying a cable from Lonelec in the UK - hasn't missed a beat since.

The cable would have worked fine *if* the blue (K-Line Ground) wire had been in the middle on pin 2.  Both my cable and the OBD-usb dongle came from Lonelec as they were recommended on this forum .

It's looking like a previous owner had moved the blue wire, and it's time for me to move it back and change my schematic etc.

Thanks for the input.