A few Questions re 07 1100

I have the tank off my 1100 at the moment checking on stuff, namely the Idle Stepper.
The bike has been powered down for several weeks with the battery out;


When I put the battery back and turn on the key I get the triangle at top right and the word SERVICE in red across the bottom
Does this sound normal?
Could it be because the tank is unplugged.

I have never used the program Guzziduag, My previous FI bike had one of Cliffs MyECU kit sets in it so I never had a use for this software.
When I boot up Guzzidiag it comes up
V0.40    2014 by Beard

It seems to be configured for
IAW 5AM PF3C  I have no idea if that's applicable to the GRiSO

I don't see any indication that the PC is communicating with the bike (no numbers filled in)
I am plugged into the 3 pin connector at the rear of the seat next to the minor fuses, I have +/- 12 on the adapter (light is on)
The adapter is plugged into one of the PCs USB sockets.
I'm pretty sure I'm doing something stupid, please bear with an old fart.

Thanks in advance
Roy

Service warning with fuel pump disconnected is normal. GuzziDiag v0.40 is old. Get the latest version:

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

IAW 5AM is applicable to the GRiSO, but as GuzziDiag defaults to Bellagio, you might want to click on "preferences" and set it to GRiSO 1100. You also need to set the COM port in the preferences. The drop-down may have several ports listed. You may have to try them one at a time.
Assuming you have installed the correct drivers?

You may wish to go through the GuzziDiag tutorial I wrote.

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

Wow that was fast.
Thank-you very much

Assuming you have installed the correct drivers?
Drivers eh! why did I think they were just for reading and writing maps LOL

I will go thru the tutorial today.

Roy

I think I have the software I need
Guzzidiag_V0.47   377KB
IAW5x Reader 136KB
IAWSx Writer 174 KB

When I tried to download the drivers for the hardware by clicking on your link  it comes up with the following,
Can you suggest anything?
"The document name you requested (/Drivers/CDM/CDM 2.08.30 WHQL Certified.zip) could not be found on this server. However, we found documents with names similar to the one you requested.
Available documents:
•/Drivers/CDM/CDM 2.08.24 WHQL Certified.zip (common basename)

I purchased the hardware you recommended perhaps I don't need to download any firmware
One small point, to select the port under Windows NT is that in control panel?
I have an old MacBook as an option

Thanks
Roy

Try this link:

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

I need to fix the link in the tutorial. You select the port from the programs. For GuzziDiag, it's in the preferences. For Reader and Writer, the main dialog Window.

Brilliant,
Thanks Mark, I should have come to your site first it explains everything.

I find if I write stuff out it helps to understand what's going on

I sort of half got the software working on a DELL PC laptop but the USB ports seem a bit flakey, it only worked on Com25 and the read software doesn't give me that option.
I'm supposed to be able to change the port address into the range of 1-4 but its an old clunker, the instructions don't seem to apply. I had our IT guy look at it, ne explained that the early USBs were far from stellar

So now I want to use a Mac Laptop I have, this has never done anything out of the ordinary   
MAC OS X Version 10.5.8 checked for the latest revisions
I fire up Guzzidiag but it doesn't give me the option of selecting a COM port, just a blank space greyed out

I'm sure we have some Mac experts out there
I tried installing the Mac cable driver from Mark's site in order to download the driver into the USB port,
I let it install into the default location, seems to be going well but at the last second says "Install Failed" that's really useful.
Show error, "The installer could not install some files in "/"     Is that the clue?
Is there somewhere else I should install it?
Please give me instructions a neandathal could follow

I assume this software is writing to the chip inside the cable, through but not to the laptops virtual port

Update:
The plot thickens, I asked a Mac guru at work about the message the driver was giving me, he figured out the hardware was too old for this driver and found another FTDIUSB Serial Driver which loaded normally

Kiwi_Roy wrote:

Update:
          The plot thickens, I asked a Mac guru at work about the message the driver was giving me, he figured out the hardware was too old for this driver and found another FTDIUSB Serial Driver which loaded normally

That's good news. That should get you going.