Guzzi Diag Help in the SE

[Mayor_of_BBQ]

Hi all,
Made this request before. Antmanbee has offered help but he's way down in Florida so distance is an issue.

I have a Breva 1100, a beetle map, and a cat delete Y-pipe just dying to all get married!

Problem is, even after a dozen attempts on 3 different laptops with two sets of cables, I cannot operate guzzidiag.  Maybe I'm just that dumb, but a man's got to know his limits. Computers are not my thing. 

Is there anyone in the WNC/E.TN/SC/SWVA/NWGA area who can help???  I will set the valves, install the Y-pipe, and truck the bike to you. I can bring beer, smoke, cash, bitcoin, platitudes, nudie mags, rally T-shirts, or whatever else I need in trade to get this done. 

I love my bike but I can't take the pinging anymore and I really want the y-pipe on-- thats a problem because I have an open exhaust (po installed) and dont want to open up the breathing any more without getting the better map in there! Its also been throwing the SERVICE warning intermittently and need to see what that code is to address it.

Nearest Dealers are 4hr, 7hr, and 8hr round trips for me~ and no one I have been able to get a hold of at any of the three will install a non-factory map or touch GuzziDiag with a 10ft pole.

Help please anyone?

[Bert Remington]

MBBQ -- 

Computers are not my thing.

Well you either need to change that or stick to your carburetor MGs.

First, you have several computers.  Are they Windows or not?  If Windows choose the oldest (WinXP is great) laptop (don't have a laptop -- borrow one).  Then as a skills test, view the hardware configuration using Device Manager.  If you don't know how to do that, it's time to call in an expert.  That would be the neighborhood kid who keeps asking about your motorcycles.

Use the Lonelec adapter, nothing else.  I also recommend using a external battery -- NOT a battery charger, etc.

Install the GD software.  Familiarize yourself with the various menus even though the Breva isn't connected, especially the Report option.  Make sure you have chosen the correct ECU model.

I have found a specific sequence is required to achieve successful connection.  Starting from Ignition Off and GD not started, the sequence is:

1 -- connect the Lonelec 3-pin to the diagnostic 3-pin
2 -- connect the Lonelec Black and Red clips to battery power (I use a separate battery)
3 -- connect the Lonelec USB plug to the computer (you should hear the familiar jingle)
4 -- verify the Lonelec COM number in Windows Device Manager (often COM4)
5 -- start GD
6 -- verify GD shows your ECU model in the bottom left box
7 -- select/re-select the COM number in Preferences
8 -- now click Connect and wait for the Ignition prompt
9 -- turn ignition On, wait 15 seconds, and press Ok

After a few seconds, GD should fill in the bottom left box with configuration information about your ECU.

In my experience, if Step 9 still shows Disconnected in the GD status line, I have to start all over from the beginning with Ignition Off and GD not running.  Sometimes I'm successful on the first try and sometimes on the third try.  Sometimes I have to swap USB ports.  But I've always been successful.

I recommend as a first step reading and saving a report.  It's very useful to have a printout before clicking on the other stuff GD offers.

As a second step, download a copy of your ECU map and your ECU firmware (two separate items).  I was more successful invoking the appropriate programs directly rather than via the GD menu.

Again run through the various GD menus to get a better understanding of your Breva and GD.

Disconnect and power down everything.  Recharge the laptop.  Take a break.

I have never loaded a map but if you were successful with all the above you should be successful now.  Start from Step 1.  When you have a successful connection, write your Beetle map.  Then read and save another report.  Disconnect and power down everything.  Take the Breva for a ride.  Tell us how it turns out.

Best wishes with your Breva.

[Mayor_of_BBQ]

MBBQ --  Well you either need to change that or stick to your carburetor MGs.

First, you have several computers.  Are they Windows or not?  If Windows choose the oldest (WinXP is great) laptop (don't have a laptop -- borrow one).  Then as a skills test, view the hardware configuration using Device Manager.  If you don't know how to do that, it's time to call in an expert.  That would be the neighborhood kid who keeps asking about your motorcycles.

Use the Lonelec adapter, nothing else.  I also recommend using a external battery -- NOT a battery charger, etc.

Install the GD software.  Familiarize yourself with the various menus even though the Breva isn't connected, especially the Report option.  Make sure you have chosen the correct ECU model.

I have found a specific sequence is required to achieve successful connection.  Starting from Ignition Off and GD not started, the sequence is:

1 -- connect the Lonelec 3-pin to the diagnostic 3-pin
2 -- connect the Lonelec Black and Red clips to battery power (I use a separate battery)
3 -- connect the Lonelec USB plug to the computer (you should hear the familiar jingle)
4 -- verify the Lonelec COM number in Windows Device Manager (often COM4)
5 -- start GD
6 -- verify GD shows your ECU model in the bottom left box
7 -- select/re-select the COM number in Preferences
8 -- now click Connect and wait for the Ignition prompt
9 -- turn ignition On, wait 15 seconds, and press Ok

After a few seconds, GD should fill in the bottom left box with configuration information about your ECU.

In my experience, if Step 9 still shows Disconnected in the GD status line, I have to start all over from the beginning with Ignition Off and GD not running.  Sometimes I'm successful on the first try and sometimes on the third try.  Sometimes I have to swap USB ports.  But I've always been successful.

I recommend as a first step reading and saving a report.  It's very useful to have a printout before clicking on the other stuff GD offers.

As a second step, download a copy of your ECU map and your ECU firmware (two separate items).  I was more successful invoking the appropriate programs directly rather than via the GD menu.

Again run through the various GD menus to get a better understanding of your Breva and GD.

Disconnect and power down everything.  Recharge the laptop.  Take a break.

I have never loaded a map but if you were successful with all the above you should be successful now.  Start from Step 1.  When you have a successful connection, write your Beetle map.  Then read and save another report.  Disconnect and power down everything.  Take the Breva for a ride.  Tell us how it turns out.

Best wishes with your Breva.

I know you are trying to be helpful, but I have done this repeatedly with several computers and assisted by people up to 20 years younger than myself. I exchanged messages with beetle for three weeks. I posted in the guzzi diag tutorial thread for 4 days (I've since deleted those posts). I printed out the guzzi diag tutorial in hard copy and followed each step to the letter, highlighting and checking off every step of the process.
Yes I'm using the correct drivers
yes I have the correct version of GD for my ecu
Yes I bought a second set of cables- the exact ones linked to in the tutorial thread

so, none of this has worked. I am seeking someone proficient with the program who has successfully done it with known working components to assist me.

[Tom H]

You said you followed everything. Just a thought, on the GD website, they show how the cable is wired. Did you confirm the cables you tried were wired correctly?

I also have trouble getting GD to connect sometimes. It's usually the comm port selection. If two ports are showing, try each one. Even when one didn't work, when I went back to it, it would work??? Shrug!

Tom

[Bert Remington]

Okay many others have been successful with other computers and other motorcycles.  So we're looking at a common failure point.  That would be either the operator or the motorcycle.

Let's start with the operator.

You said computers are not your thing.

Do you know how to run Windows Device Manager?

If you don't then stop right now and return your Breva to stock exhaust.

But if you want to keep your current exhaust then find someone to help you that is familiar with Device Manager.

Then be specific exactly where GD "fails".

Can you read the menus?

Is your ECU correctly selected?

Is the Blue light on the Lonelec ON?

Do you get the jingle when you plug the USB cable in?

What are the configuration parameters for the COM port?

The Lonelec adapter WORKS.

GuzziDiag WORKS.

Windows WORKS.

So what exactly are these things NOT working for you?  What is the specific step where the failure occurs?

[guzzisteve]

May not be your fault why it doesn't work. I have found some ecu's don't want to communicate. These were 15RC's though, haven't had a problem with the 5AM.
I know it's frustrating and you been through it all too many times. PM reply.

[Mayor_of_BBQ]

You said you followed everything. Just a thought, on the GD website, they show how the cable is wired. Did you confirm the cables you tried were wired correctly?

I also have trouble getting GD to connect sometimes. It's usually the comm port selection. If two ports are showing, try each one. Even when one didn't work, when I went back to it, it would work??? Shrug!

Tom

if I'm doing something incorrectly, then me and 2 other people on three different occasions are not seeing it... GD doesnt even see that there is a bike connected. I have tried every available port on two different laptops running two different generations of windows. It would be impossible to express how closely I followed the instructions. I am talking about going painstakingly line by line exactly to the letter of the steps laid out in the instructions...  Doesn't work? Ok, now I will read it line by line to someone else and have them do the steps... ok that didnt work either, shut it down, disconnect, start over...  Now you read it out to me and I follow your instructions. Ok that doesnt work either... shut down disconnect, start over.. etc etc etc. I've spent hours and hours starting over and over and over on multiple occasions with different computers, helpers, and cables. I got advise in the thread, started over and followed those steps.. got advice from beetle and tried that. *I* am not capable of getting it to work, that's why I'm hoping to try it with someone who has the proven know-how. If they cant get it to work, then maybe I have a bad ecu or the plug is messed up-- thats all I know to do at this point.

I cant believe Guzzi sells products off the showroom floor that requires you to reprogram it with a free computer software made by private individuals to make it work correctly. f***ing crazy.

[antmanbee]

For a new map you only need the writer program and the reader program to save your old map.
Did you run the adapter test program?

[Bert Remington]

MBBQ -- okay we have a data point in the connection sequence: GD always shows Disconnected.  Until you see Connected, you ain't going nowhere communicating with your Breva.

Are you using the Lonelec adapter?

Is the Blue light ON?

Are you getting the Windows jingle when you plug the USB cable in?

What does Device Manager show for the COM port configuration?

GD has a quirk (at least on my WinXP) when you must specify/verify the COM port in Preferences before clicking Connect.  Failure to do this requires starting over at Step 1.

GS -- concur with your analysis.  That's what I included motorcycle as a common failure point.  Early MGs might be using a slightly different K-line protocol/message format than later MGs.

[Mayor_of_BBQ]

Did you run the adapter test program?

I can't remember, is that one of the steps outlined in the tutorial thread? I did whatever that said to do, in the order it told me to do it. I'm not sure about this program, I was trying to use the reader/writer functions.


I do know I only need to read/save the old map and then write the new map...  I never even got the old map read, it says connecting connecting connecting endlessly until it times out. The connection is never established

[Mayor_of_BBQ]

Hopefully Guzzisteve is swooping in for the assist! just need to work out the schedule! Thanks guys

[antmanbee]

“This is a very complicated case Maude. You know, a lotta ins, a lotta outs, lotta what-have-yous.”

Good luck to you and Guzzisteve

[Mayor_of_BBQ]

“This is a very complicated case Maude. You know, a lotta ins, a lotta outs, lotta what-have-yous.”

Good luck to you and Guzzisteve

Lot of threads running around the 'ol Duder's head!

[guzzisteve]

We'll get it sorted. Might bring your laptop too, who knows, it may hook up.