Jazzamoto

Great video Dave! The North coast is always so beautiful. Planning a ride up that way in early June. So how come the bike looks progressively cleaner the closer you get to home?

I had some connection problems with getting the right driver for the cable. A cheap Chinese OBD2 cable would only connect to a 15M using the driver from the same site I got GuzziDiag from, but it refused to connect to a 15RC. The cable I bought from www.lonelec.co.uk worked best using Lonelec's driver. Windows 10 didn’t get the cable working, but forcing Lonelec's driver made it work. Once I consistently got a reliable connection on GuzziDiag, I have never had an issue with IAW15XWRITER. Dangerous and I both have succeeded in browsing for, and loading a .BIN file using a windows 10 or XP computer, but I can't comment about a Mac. I saw GuzziDiag fail to connect to a 15RC ECU when GD was set to a V11 model which uses 15M. It just returns a message "switch off ignition" after about 10 seconds of no other response, with no error message. Your error message could be related to a driver or cable problem. Marty, I'm using the Lonelec cables as well. For Mac they recommend the same driver from the FTDI driver page as ESCTuning does (which was the first cable I tried without success and returned it). I'm using "V11 Sport" as my model since the "Cafe Sport" selection assumes I have a 15RC ECU, and I have the 15M. I'm definitely connected and can read RPM, engine temp, etc. Meinolf mentioned that my existing map has been modified, by whom and to what extent is unknown and I'm guessing that this may be preventing the CO trim function from working, hence the "Active Diagnostics" error message. My plan was to write the stock map you sent me over whatever is in the ECU now in the hopes that it will allow Guzzdiag to function normally. But, as Swooshdave said yesterday, unfortunately something in the IAW15XWRITER code isn't searching my hard drive for your .bin file so I'm stuck between a rock and...another rock. Meanwhile I'm looking around for another laptop I can beg, borrow or steal so I can try this whole thing in Windows which I'm more familiar with. The MacBook I'm using is a hand me up from my son and I haven't really used it much until now and I'm not impressed. Marty, thanks again for your input! Cheers! John (I'm no Steve Wozniak)

Since I posted this I've found that the folders in the left box are in my MacBook hard drive yet I'm still unable to open them to find the .bin file I need (which is a stock V11 map sent to me by MartyNZ). Swooshdave says, and I agree with him, that It looks like there's an issue with IAW writer not being able to search my Mac hard drive. Has anyone had this issue? Also, In Guzzidiag, has anyone gotten the error message "Active Diagnostics Could not be Started" when attempting to set their CO trim? Help! My bike is running so rich the neighbors have taken up a petition!

This is directed to Mac Book Pro users who are running Guzzidiag. I've been trying to load a new map to the 15M ECU on my 2004 V11 Cafe Sport. When I open the IAW 15 Writer app and hit the "click to choose file" button it brings up a box called "Choose a file" (shown in the screen shot below). Not a box I've seen before. All the items listed in the left box are dead links BTW. How do I get the writer to search my downloads, desktop, etc? Thanks! John (it was all so simple way back when I had my 386sx!)

Well look at it this way Dave, if you'd bought the bike in Olympia you never would have been able to visit Beautiful Exotic East Richmond Heights!

Swooshdave "swooshed" by this morning on his way home to Portlandia. Nice guy and nice bike. What a score! We hung out, talked Guzzidiag, etc. a when it finally warmed up enough sent him on his way up 101 North with his Greenie. Thanks for coming by, Dave! Cheers! John

At this point I'm thinking Meinolf has identified the problem. Someone has gotten into the ECU and made some tweaks to richen it up. I tried again to adjust the CO trim and for a brief moment I got a reading of +113! but then the box closed and I got the "Active Diagnostics Could Not Be Started" error message again. Soo..... I'm thinking I might want to reload a stock map and start from scratch. Where can I find a bin file for the stock map? Is there a bin file library or someone who is the official librarian of Guzzi bin files? I'm looking for the stock map for a 2004 V11 Cafe Sport or a map for stock plus FBF slip-ons. Meinolf, thanks again for the EEPROM suggestion.I read up on it and it looks a little dangerous for someone at my primitive skill level. Thanks again All! John

Docc, it says 50 but can't tell if it's + or - 50. Sorry docc, thought that was directed to me. John

Docc, it says 50 but can't tell if it's + or - 50.

Hello Meinoff, By "content was edited" do you mean that the stock map has been altered? Thanks! John

I did but got the same result. Not only does it show the wrong ECU but I get all zero's where it's supposed to show the map info. Thanks though, czakky!

My apologies for somewhat duplicating my post above but I really do need some help. I'm almost finished with Docc's Decent Tuneup. All that remains to be done is to adjust the CO trim. Apparently a previous owner set the CO VERY rich. I'm only getting 30 MPG and after only 1300 miles the plugs are totally black. I don't want to ride it in this condition so I've developed a serious case of "No Bike Syndrome" which is very painful and keeps me awake it night. The bike is a 2004 V11 Cafe Sport. I'm using the latest Guzzidiag V0.47 on an earlier Mac Book Pro OS 10.7.5 and hooked up with the Lonelec cable set. My problem is as follows: When I attempt to set the CO trim, after warming the engine to +60 c, I get an error message stating "Active Diagnostics Could Not Be Started" and I'm unable to continue the CO trim adjustment process. Also, and I don't know if this is related to the above, but when I select my model "V11 Cafe" in the Guzzi Diag Settings window it shows that I have a 15RC ECU when the unit in the bike is a 15M. At this point I'd really appreciate any help, suggestions, etc. Need to get back on the road. Cheers! John

Paul, I took your suggestion and ordered the Lonelec cable set and now, at last, it can read my MacBook port and I'm able to connect. However I'm still having a few problems, as follows: I have a 2004 V11 Cafe Sport. When I select "V11 Cafe" in the Guzzi Diag Settings window the ECU Information box shows an ECU that I don't have - 15 RC PF3C . My Cafe Sport ECU is 15M - C1. It also shows only zero's for the map version. Despite this I tried to adjust my CO trim after bringing the bike up to 60C temp and got an error message stating "Active Diagnostics Could Not Be Started". I decided to try the process again using "V11 Sport" as my model because that at least showed a 15M PF3C ECU but got the same results, only zero's for the map version and the same error message for CO trim. Is there another listed model that I should be using and why am I getting the "Active Diagnostic" error message? I'd sincerely appreciate any suggestions. Thanks! John

Docc FYI The OBD II to usb cable I ordered from ESCTuning didn't work for me. I suspect it doesn't have the correct FTDI 232RL chip despite being listed as such on their website. At Paul's suggestion I ordered the Lonelec kit and was able to hook up with my MacBook. Both cables use the same FTDI driver. My recommendation is to forget other sources and just order from Lonelec in the UK. A bit more shipping time but they're garanteed to work.

That's interesting docc. I tried it again and noticed that when I enter my model, V11 Cafe (for 2004 V11 Cafe Sport) Guzzidiag lists a different ECU in the ECU Information window. The bike has a IAW 15 M . C1 and the window shows IAW 15RC PF3 C. It shows this ECU for "Bellabio Cat", "V11 Cafe" and "V11 Cat". All other models show IAW 15M PF3 C ECU's. So I tried using one of the models with a 15M ECU and still no luck, no com ports shown. John

Thanks Paul. Looks like the Apple FTDI driver started with OS-X 10.9 and my older MacBook can only run as high as OS 10.7.5 so I guess there couldn't be a driver conflict with the one I downloaded from the FTDI driver page (version 2.2.18). I'm using the the VAG KKL usb adaptor from ESCTuning and the OBD - OBDII Fiat/Lancia connector and still unable to any reading on any com port (only two on my MacBook). So, before I pop for a second set of cables, are there any other Mac users who have had similar problems and can give me some guidance? I really need to get to the CO trim. I'm only getting 30 MPG and the plugs are sooty. Thanks everyone! John

Great, thanks czakky! That was my guess but didn't want to force it. Maybe drizzle a little of your favorite CLP into it first? Will do. Thanks docc.

Great, thanks czakky! That was my guess but didn't want to force it.

Regarding disconnecting the right throttle linkage - how is this done? Does the ball joint snap off or do I unscrew the white knob on the left side?

Hello docc, I tried your solution but no luck. When I opened "preferences" - "file" the "connect" box was grayed out and didn't respond. I'm wondering if this is a driver issue. I'd downloaded driver 2.2.18 from the ECStuning driver page http://www.ftdichip.com/Drivers/VCP.htmsince I'm using a Mac Book Pro running OS X 10.7.5. There's a reference to a Technical Note regarding issues with Mac drivers TN-105 but it's beyond my level of comprehension. I seem to remember some mention on this site about not using the cable manufacturers driver but instead a specific Guzzidiag driver but can't find that comment on search. At any rate, thanks for your help. I'm headed down to LA for a few days (memorial for a family member) so won't be able to do anything on the bike until next week. Not that it matters, pissing down rain with 30 mph gusts here on NorCal. Thanks again docc!

That is my understanding. Make your selection based upon your computer's operating system and processor architecture (Not the bike's computer, the computer you are using to interface with the ECU software). As I am not the expert to answer this, I welcome clarifications or corrections! Thanks Docc. That's what I had done. I made my first attempt to run Gizzi Diag yesterday and couldn't get any Com ports to list in the Guzzi Diag Settings window. My older Mac Book has two usb ports and neither would work. I thought perhaps I might have loaded the wrong drivers. Also the cable light comes on (red not blue as in the pic) when I plug in to the usb port even if it's not connected to the battery with the alligator clips. I've also downloaded the IAW15xreader and IAW15xwriter files but I have no idea what the hell they are and whether I really need them. Cheers! John (Confused in East Richmond Heights) Any luck? Where did you source the OBD -> USB cable? If this is not a solution, I will move these posts to the main ECU Diagnostics and reprogramming thread to get some expert response. Haven't been able to get to it yet docc. Hopefully tonight or tomorrow. The cable was sourced from ecstuning.

That is my understanding. Make your selection based upon your computer's operating system and processor architecture (Not the bike's computer, the computer you are using to interface with the ECU software). As I am not the expert to answer this, I welcome clarifications or corrections! Thanks Docc. That's what I had done. I made my first attempt to run Gizzi Diag yesterday and couldn't get any Com ports to list in the Guzzi Diag Settings window. My older Mac Book has two usb ports and neither would work. I thought perhaps I might have loaded the wrong drivers. Also the cable light comes on (red not blue as in the pic) when I plug in to the usb port even if it's not connected to the battery with the alligator clips. I've also downloaded the IAW15xreader and IAW15xwriter files but I have no idea what the hell they are and whether I really need them. Cheers! John (Confused in East Richmond Heights)

Quick question on the FTDI driver. Is it the VCP Virtual Com Port driver that should be downloaded? Thanks!

Just my 2 cents, I've got a 170 on my 2004 Cafe Sport (5.5" rim) and it does turn in more quickly. Too quickly, in fact. After it's worn I'll go back to a 180.

What kind of rear stand are you using? Just curious.