The New Improved GuzziDiag Tutorial

[80CX100]

Hi,

I never recommended 0.3mm valve clearance for the V11 camshaft.

Cheers
Meinolf

Pm on the way

tks

Kelly

[SIR REAL ED]

Beetle,

I had a discussion with another Guzzi owner who can not run version 47 of GuzziDiag on his Mac with the latest OS.  He has found a work around.  Version 46 of GuzziDiag seems to run just fine.

Any ideas why?

Could you provide a link to download version 46?

Thanks in advance!

[beetle]

No, and, no.

I've made enquires. Stay tuned.

[SIR REAL ED]

the good news is version 46 opens on my Mac.

the bad news is it is not the right version for my ECU.

[beetle]

Huh? It should work fine with the 15RC. What bike have you selected?

[SIR REAL ED]

Huh? It should work fine with the 15RC. What bike have you selected?

The 5AM ECU popped up in the window (Stelvio 1200 IIRC).  I thought there would be a drop down menu to pick the ECU, but that function did not work.

[beetle]

You have to click "File" -> "Preferences"

Use the dropdown from the dialog box that opens to select the bike.

[SIR REAL ED]

You have to click "File" -> "Preferences"

Use the dropdown from the dialog box that opens to select the bike.

When I click "File" the only option I get is "Connect."

[SIR REAL ED]

GuzziDiag downloaded like a dream to a 10 year old Notebook running Windows7.

Using a new Mac to download software to use on an old bike is as problematic as using a laser to measure the straightness of your frame....

[beetle]

So..using Windows now?


As for the Mac, look in the same folder that your running GuzziDiag from. There should be a file named GuzziDiag_V0.46.ini . Edit this file, and change line 6 (Modell) to Nevada 750 S.

[SIR REAL ED]

So..using Windows now?


As for the Mac, look in the same folder that your running GuzziDiag from. There should be a file named GuzziDiag_V0.46.ini . Edit this file, and change line 6 (Modell) to Nevada 750 S.

I'm using whatever I can get to work.  Cresent wrenches, pliers, vise grips, whatever!

I can only take a machine, especially a computer....... telling me to "F**k Off!" just so many times. 

When it comes to portable devices with a screen, my preference is for an Etch-A-Sketch!

But I do appreciate your help!  Assuming of course you're human!   

[Harryc]

Hi Beetle.

Thanks for doing the work to get this going. I've just loaded the V7II Stornello map onto my V7II special with Arrow exhaust. I've had the Lonelec kit for nearly a year, but it took this long to get the Arrow Exhaust mounted.

Loading the new map was a simple process when I followed the documentation. Performance wise, I noticed an immediate improvement starting cold. I hope I get a chance soon to see how it goes on some mountain roads.

One comment on the Tutorial, Maybe a few more words on setting up for Linux. I read your post here: https://wildguzzi.com/forum/index.php?topic=84489.msg1333294#msg1333294. The comment" With the cable plugged in and powered, check that you have this device:  /dev/tts/USB0" led me down the wrong track for a while, It looks like you only need to have /dev/ttyUSB0 , which is the standard location for the USB port on my Linux Laptop (xubuntu 18.04).

The main point for Linux users would be to check you are part of the dialout group. Once I did this, everything was good.
The second point for some versions of Linux may be about setting up the symlink to /dev/ttyUSB0 if their USB appears somewhere else.

Thanks again and great effort.

[beetle]

Bernd has released V0.48 of GuzziDiag. This release fixes some issues with resets on the 7SM.

I recommend California 1400 and V85tt owners who use GuzziDiag download it immediately. I also strongly recommend you backup your eeprom with the eeprom tool ASAP.


I will update the links in the first post when I get a chance.

[SIR REAL ED]

hi Beetle,

After the long delayed connection, "hook up" in hipster lingo, GuzziDiag said I had no faults (IIRC there were two catagories, actual and recorded) in my Nevada's system.  I appreciate your help.

Are you aware of any software fixes that eliminated the random EFI light appearance?

thanks,

Ed

[beetle]

Only the map fix Guzzi released., previously mentioned by guzzisteve in one of your threads.

[SIR REAL ED]

Only the map fix Guzzi released., previously mentioned by guzzisteve in one of your threads.

I talked to Guzzisteve about that.  Since I have the older dash board, I should not load the updated Guzzi map.

He thought it might be possible to eliminate the unwanted and unwarranted EFI by disabling the O2 sensor.  I assume the O2 sensor and the Lamda sensor are the same thing.  IIRC, you created a map that eliminated the Lamda sensor.  Is that included on the drop down menu of GuzziDiag_V0.47?  If not where could I find that map?

thanks again.

[guzzisteve]

If it was me, I'd send Beetle the map from your bike, then it has the correct dash info if it makes a difference for the older dash.

[SIR REAL ED]

If it was me, I'd send Beetle the map from your bike, then it has the correct dash info if it makes a difference for the older dash.

What do you think beetle?  If I send the current map to you, can you do anything to it that might help?  thanks again.

[beetle]

I'm happy to take a look at the map, although just posting the text from the GuzziDiag ECU information box is probably all I need. I can make a lambda-off map for you if you want to try it.

[Kiwi Dave]

What year model is the Nevada?  The earlier ones (like I assume you have got) don't have a Lambda.

On the later ones that might have a Lambda, won't there be an issue with just switching the lambda off?

On the CARC bikes IIRC, the raw map(s) was stupidly rich, and it was the lambda that corrected everything up to 40% throttle.  To gain improvements over 40%, the procedure before Beetle appeared on the scene was to fit a wide band lambda controlling a power commander; autotune was an optional extra.

I think it's gonna need more than a Lambda switch off.

[SIR REAL ED]

I'm happy to take a look at the map, although just posting the text from the GuzziDiag ECU information box is probably all I need. I can make a lambda-off map for you if you want to try it.

I'll send you the information in a PM hopefully within the next couple days.  Thanks again.

[SIR REAL ED]

What year model is the Nevada?  The earlier ones (like I assume you have got) don't have a Lambda.

On the later ones that might have a Lambda, won't there be an issue with just switching the lambda off?

On the CARC bikes IIRC, the raw map(s) was stupidly rich, and it was the lambda that corrected everything up to 40% throttle.  To gain improvements over 40%, the procedure before Beetle appeared on the scene was to fit a wide band lambda controlling a power commander; autotune was an optional extra.

I think it's gonna need more than a Lambda switch off.

It is a model year 2007, and there is a sensor in the cross over exhaust pipe.  Maybe that is a F/A sensor? 

Is the Lambda sensor the same beast as an O2 sensor?

[guzzisteve]

Before the V7 arrived the Nevada had a Breva map in it. AND the dash. They made a newer dash, if you put the V7/NEVAD update map in older dash bike it BRICKs the ECU. Ask me how I know.
Went and got my notebook-- info from using TechnoResearch VDSTS

Nevada V75    part#6160139700 & calibration #3L09BN22
Breva   V75    part#6160106000 & calibration #3L09BR40
V7 Cafe         part#BC0103278A & calibration #3L10BN22

as far as I could tell Guzzi's mapping matched up to calibration info.
The V7/NEVAD map was released 9/15/09 for new dash issue.

[SIR REAL ED]

I'm happy to take a look at the map, although just posting the text from the GuzziDiag ECU information box is probably all I need. I can make a lambda-off map for you if you want to try it.

Here is the text from my ECU information box:
IAW15RCPF1C
61601.397.00
3L09BN22

Let me know what you think.  thanks again!

[beetle]

Yours doesn’t seem to be the latest release. I have 3L10BN22, which would be a later version. Do you want to read your map and send it to me. I will check it, and you might want to install the later version.

[SIR REAL ED]

Yours doesn’t seem to be the latest release. I have 3L10BN22, which would be a later version. Do you want to read your map and send it to me. I will check it, and you might want to install the later version.

Very interesting!  I have read and saved my map.  I will send you my map.  Per GuzziSteve's post above, will you know by looking at my map if installing the 3L10BN22 map instead of the existing 3L09BN22 map will brick my ECU, since I have the older instruments?

thanks.

[beetle]

Hmm. Might not be a good idea then.

 

[SIR REAL ED]

Hmm. Might not be a good idea then.

 

My thoughts exactly.

So......you are saying that by looking at the existing map that:

A.  you would not be able to tell if the updated map will brick my ECU?

or

B.  you will be able to tell that he updated map will not brick my ECU?

Enquiring minds want to know!

[beetle]

I won't be able to categorically say that the newer map will not brick your ECU, although I'm not sure why or how that could happen.

Send me the map. I will compare it to the maps I have. Worst case, I turn off lambda in your map. It may not run brilliantly, but if the EFI light doesn't come one, then you can assume your lambda probe is not functional.

[SIR REAL ED]

I won't be able to categorically say that the newer map will not brick your ECU, although I'm not sure why or how that could happen.

Send me the map. I will compare it to the maps I have. Worst case, I turn off lambda in your map. It may not run brilliantly, but if the EFI light doesn't come one, then you can assume your lambda probe is not functional.

Yeah, I can't imagine how a change in code could destroy hardware either, but I guess the guy that programs the Mission Impossible communication devices knows how to do it......

I'll send you the map.  I appreciate you taking a look.