RhinoPower Ltd

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Cannot get RhinoView V1.0 to connect to SDL interface


Guru

Status: Offline
Posts: 1274
Date:
RE: Cannot get RhinoView V1.0 to connect to SDL interface
Permalink  
 


Rhinoview V1.0 uses a USB driver that automatically recognises the interface, it does not use the Virtual Com Port and cannot support third party interfaces. I would suggest that you use TunerPro RT v5 with the 1453 definition file, it has been well proven on Metros and Swifts.

__________________

1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine
2000 Suzuki Vitara 1.6 8V, many mods
2004 Suzuki Ignis 1.5VVT 4Grip
2006 Suzuki Jimny 1.3VVT JLX+
and many more.



Newbie

Status: Offline
Posts: 1
Date:
Permalink  
 

Can someone please help me?

 

I have a 1994 Geo Metro XFi (Standard Emissions) (California Emissions)

ECU: B7  3-ER-CAL   33920-60E54

OBD Diagnostics, Inc. ALDL (GM OBD1) Cable with 12 pin SDL Connector  to USB

I get about 5 volts across M to A pins and about 12 volts across H to A pins

MIL functions properly (flashes DTC 12 only)

USB Serial Port COM3 driver provider is listed as FTDI

On status line of RhinoPower Engine Management "No Interface", "Not Connected" never go away.

When I click on Comms>Connect I always get a dialog box "No SDL Interface Connected". "Settings" never appears. Can't select COM.

I'm running Windows 7 Home Premium on my laptop.

 

I called the cable guy. He wasn't familiar with RhinoView and all he said was that when you connect to the ALDL you must request the data. How do I get RhinoView to do that?

 

I'm going insane with frustration. Everything seems to be set up properly yet I'm not getting RhinoView to work at all.

 

Gary

Oxnard, CA

 

 



__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard