Help Needed - Rover Gauge

[Plan B]

Hi all
(Posted this on the Griffith page yesterday but still needing help)
Today tried using Rover Gauge for the first time. I'm using a USB connection emulating a serial interface out of a Windows laptop (Win 7). The RG software is seeing and configures the COM port and all appears well. When clicking the "connect" button (not connected to the car at this stage) RG seems happy and accepting the "connect" showing null values as expected as it isn't hard connected to the car. The red LED in the USB plug/logic lights up but remains red rather than changing to green. When I do plug into the car, no values register on the RG dashboard. I've tried disconnecting/reconnecting and closing down and re-starting the app but still nothing is reading across. I'm suspecting a duff USB/Serial cable but any advice/suggestions would be appreciated.

[blitzracing]

Check the installation guide that comes with the cable (assuming its one of my cables) there is a bit on the last two pages on how to do a loop back and the expected resistance readings on the TTL plug. This will check the cables function and the continuity to the ECU.

[s p a c e m a n]

You do have the ignition turned on don't you?

Check in the roverguage settings what com port is selected, my version always picks the wrong one when I first install it.

[PhilH42]

s p a c e m a n said:

You do have the ignition turned on don't you?

Check in the roverguage settings what com port is selected, my version always picks the wrong one when I first install it.

All joking aside its a good point! Even if you do have the ignition on check the immobiliser hadn't kicked in as it will stay as red until reset.

[Plan B]

Had another attempt(s) earlier today.
1) The USB plug illuminates red when clicking "connect" in RG
2) Turned on ignition disabled immobiliser RG still not seeing the ECU. (neither the red or green communication buttons are lit on the RG panel)
3) cycled through disconnect/reconnect with no result
4) Changed USB port in case laptop had USB failure - no result
5) Performed loopback test on cable - still no red or green buttons lit on RG panel.
6) Looked at COM settings on PC. The cable/driver seems only to use COM3. RG seems happy with this. When configuring COM1 or COM 2 into RG it (rightly) says these don't exist.

All I can conclude is:
1) I've got bad wiring between the car's white diagnostic plug and the ECU
2) Windows is conspiring against me
3) I've got a bad USB/Serial port cable

Can I ask a big favour: I'm intending to go to Burghley on Sunday with my other half. Is there a kind soul who could bring along a working laptop/RG/cable combination to test out on my car? I realise I'm addressing a Chim forum here (I get better info on this side!!) and hope my Griff doesn't offend too much

[s p a c e m a n]

Go into the bit on rovergauge where you select the com number and type in com5

(Options-edit settings-serial device name: COM5 and press OK)

Edited by s p a c e m a n on Thursday 6th April 16:06

[Plan B]

RG doesn't see COM5 - If I force this in the config setting RG gives me an error message when clicking on connect.
In Windows I've reassigned the COM3 that the driver was selecting as default to COM1 but haven't tried it out yet on the car. Don't ask me why I'm trying this - it's Windows and sometimes a random act can fix things I'm not very hopeful though as the loopback test failed on this as well.

[PhilH42]

Plan B said:

RG doesn't see COM5 - If I force this in the config setting RG gives me an error message when clicking on connect.
In Windows I've reassigned the COM3 that the driver was selecting as default to COM1 but haven't tried it out yet on the car. Don't ask me why I'm trying this - it's Windows and sometimes a random act can fix things I'm not very hopeful though as the loopback test failed on this as well.

Did you install the cable driver before doing anything else? The literature I had said if you don't do it this way sometimes it won't recognise the cable.

[s p a c e m a n]

Weird. Just checked both of my laptops, one vista and one windows 10 and they both have COM5 as the serial device name. I remember them being 3 when I first downloaded it and getting an error message, I had to manually enter 5 before they'd connect. Took me a few hours of messing around the second time because I forgot to do it

[Plan B]

Hi guys
I've just spoken to Mark where I got the cable from and will get another cable as this appears to be the likely source of the problem. Fingers crossed.......