RhinoPower Ltd

Thank you.
I have 12V between the H and A and 5V between M and A. I also have between 16 and 12V and 5V 5 between 9 and 5.
I will retest the ECU and see if there are any problems with the cables or connectors. Suddenly right on ECU testing.

About this error (floating-point-errors) I resolved, chage " , " from " . ".



Marsello wrote:

---

Yes is COM4.

Rhinoman, my car is a Sidekick, 1994, 5D 1.6, 16V and my ECU (as e-mail on the date of purchase) is ALDL.

This is in agreement?

I will be waiting for further instructions,

 

Marcelo Dante



---

I had a hard drive failure and I don't have any emails from the last few months. 

COM4 is good.

Before you try to connect you should select 7812 baud and COM4 and then press connect. Do you get any error messages when you press connect?

You need to test the ALDL socket to ensure that you have 12V between pins H and A and 5V between pins M and A. Then plug in the adapter cable and measure at the OBD2 end betwen pins 16 and 5 to ensure that you still have 12V and between 9 and 5 to ensure that you still have 5V. The ignition must be ON when the tests are done.

If the voltages check out OK then plug in the interface and use hyperterminal or similar to send some data, for this test any data will do at any speed. because its a one-wire serial link any data you send should be echoed back. The ECU will ignore any data that it doesn't recognise so it shouldn't corrupt the data.

If that all checks out OK then there is a problem with either the interface or the ECU, can you try the interface on another Suzuki?

Regards

James

The image has come out too small is the USB-serial converter on COM4? Have you tested the OBD2 socket to confirm that you have 12V between pins 16 and 5?

You need to go to the device manager and check that the driver has been correctly installed. You should see a window that looks something like this:

Unplug the interface and then see if one of the com ports is removed. If the interface doesn't appear as a ComPort then try looking under HID devices, if it appears there then you will need to right click on the device and the under 'properties' uninstall the driver and then install the FTDI driver again. You must use the FTDI VCP (Virtual Com Port) driver.

Regards

James

Could also be the floating point error. Here in Brazil we use comma instead of point.

Marsello, se precisar de ajuda me manda uma MP. (Marsello, if you need some help send me a PM.)

Did you configure the software to use the correct port & baud rate?

After starting Rhinoview, pull down the Comms menu and select Settings, then set the Comm Channel to match the cable, com1 in your case, and then choose a baud rate, click OK and then reopen the Comms menu and select Connect.

If necessary try both 7812 & 15625 baud rates.

Can you be more specific? are you getting any error messages? is the interface showing in the device manager under 'Com Ports'