RhinoPower Ltd

Good afternoon,

I am writing to request your kind support, as I am trying to diagnose my vehicle using RhinoView DashBoard v1.3, but the program remains stuck on the "No Interface" and "Not Connected" status.

Vehicle data and equipment:

1. Vehicle: Chevrolet Wagon R (Year 2001, Suzuki 1.2L engine)

2. Engine: Suzuki K12

3. Software: RhinoView DashBoard v1.3

4. Operating System: Windows 11 Home (22H2 / 23H2)

5. Connection cable: KKL OBD2 diagnostic cable with pin selector and FTDI FT232RL chip (https://www.amazon.com/-/es/gp/product/B0DMTJ9TGZ?ref=ppx_pt2_dt_b_prod_image)

Procedures and checks performed:

1. Drivers: Installed the official FTDI driver on Windows, assigned to port COM3.

2. Power supply: Ignition switch in the ON position; verified that the cable's power LED turns on when opening the switch.

3. Port settings: Optimized the port's Latency Timer to 1 ms in Device Manager.

4. Configuration in RhinoView:

   • In the Comms option, set the baud rate to 38400.

   • The cable selector is set to position 7 (K-Line / Engine).

   • After confirming the changes in Comms, the bottom status bar fails to recognize the interface and remains on "No Interface" / "Not Connected".

Reason for inquiry: I would greatly appreciate your guidance to know if RhinoView v1.3 requires any specific configuration in a config file or COM port to recognize generic USB FTDI interfaces, or if the K12 engine ECU uses a different baud rate / initialization parameter. I need to read the ECU to check fault codes (DTCs) and live parameters, as the vehicle is experiencing excessive fuel consumption.

I look forward to your feedback.

Thank you very much for your help.