Scantool

Efess · 08-29-2009, 12:45 PM

I just bought and received the Scantool CI product
The driver installation was a snap to setup, the only issue I hadd was I couldn't install the driver on my x64 machine (which I won't be using anyway) but just a heads up since x64 is becoming more and more the standard these days..

I'm using this on a 96 Nissan Altima btw

When I got everything setup and ran scantool .net, I had a problem with the signal from the tool - it would reset the interface, connect on com3 (at the default baud - 348000?) - and the device would register as working. When I went to check the sensor readings, I got an initial reading from the default sensors that were turned on, but it seems like right after the interface died and I got no signal from the device or the ECU. The software said it was probing at 4hz, and slowly dropped to 0 with N/A for all sensors. The status light remained green.

This was all with my car on the "ON" setting without the engine running, though this shouldn't matter.

The device also couldn't read any engine codes, even though my check engine light has been on..

Don't know if there's any issues with the .net software, although the other free (non trial) software refused to work at all, or maybe there's a problem with the device or my ECU. Hopefully someone can help me here though!

-Joe

Vitaliy · 08-31-2009, 12:36 AM

Quote: Originally Posted by Efess

I just bought and received the Scantool CI product
The driver installation was a snap to setup, the only issue I hadd was I couldn't install the driver on my x64 machine (which I won't be using anyway) but just a heads up since x64 is becoming more and more the standard these days..

Sorry about that. The drivers for 64-bit Vista are available from FTDI's website:

http://ftdichip.com/Drivers/VCP.htm

We're working on creating an installer for the 64-bit flavor of Vista, but for now you can just extract the file you get from FTDI, and point the default Windows installer to the directory.

Quote:

I'm using this on a 96 Nissan Altima btw

When I got everything setup and ran scantool .net, I had a problem with the signal from the tool - it would reset the interface, connect on com3 (at the default baud - 348000?) - and the device would register as working. When I went to check the sensor readings, I got an initial reading from the default sensors that were turned on, but it seems like right after the interface died and I got no signal from the device or the ECU. The software said it was probing at 4hz, and slowly dropped to 0 with N/A for all sensors. The status light remained green.

This was all with my car on the "ON" setting without the engine running, though this shouldn't matter.

Thank you for the very detailed description. It sounds like a known problem with some ISO vehicles. Basically, the problem boils down to the fact that ECUs treat unsupported requests as "no request", and time out ("go back to sleep"). Try this: turn off all sensors, then turn them on one-by-one. If a sensor displays "n/a", turn it off again -- it is not supported by your car.

Quote:

The device also couldn't read any engine codes, even though my check engine light has been on..

Are you sure that the light that is on, is really the "Check Engine" light, and not some other service light?

Quote:

Don't know if there's any issues with the .net software, although the other free (non trial) software refused to work at all, or maybe there's a problem with the device or my ECU. Hopefully someone can help me here though!

-Joe

Which other free software have you tried?

We can try some advanced troubleshooting with STNTerm, if my other suggestion doesn't solve your problem.

Vitaliy

Efess · 09-01-2009, 05:52 PM

You were right on about the No Request putting it into sleep. Making sure only the supported sensors were on, the interface worked fine at 4hz.

I still could read no engine codes- but they probably got erased since I unhooked my battery, and the light turns on by default when the ignition is "on" with the engine off. I could read engine codes from my buddies car fine, so when I get my car running again, i'll post if I still have issues.

The free software I was talking about was "EasyODBII" off of the install CD. This software
refused to initialize the interface.

Also, I haven't looked yet, but is there a programming API available to access the information from this tool?

Thanks a lot
-Joe

Vitaliy · 09-02-2009, 04:15 AM

Quote: Originally Posted by Efess

You were right on about the No Request putting it into sleep. Making sure only the supported sensors were on, the interface worked fine at 4hz.

I still could read no engine codes- but they probably got erased since I unhooked my battery, and the light turns on by default when the ignition is "on" with the engine off. I could read engine codes from my buddies car fine, so when I get my car running again, i'll post if I still have issues.

The free software I was talking about was "EasyODBII" off of the install CD. This software
refused to initialize the interface.

Also, I haven't looked yet, but is there a programming API available to access the information from this tool?

Thanks a lot
-Joe

Joe, exactly what kind of error do you get with EasyOBDII?

There's no API, but you can basically use the same commands found in the ELM327 datasheet.

Vitaliy

Efess · 09-02-2009, 05:18 PM

Not so much an error, it just has an issue initializing the interface I guess. After picking the com port, it says PC Communications OK, than sits at "Checking Interface Hardware" for a few seconds before displaying the message "Interface communication error / OBDII Timeout"

I also have to close the proccess through Task Manager, the close button doesn't work

... all the while Scantool.net still works.

Vitaliy · 09-03-2009, 11:47 PM

Quote: Originally Posted by Efess

Not so much an error, it just has an issue initializing the interface I guess. After picking the com port, it says PC Communications OK, than sits at "Checking Interface Hardware" for a few seconds before displaying the message "Interface communication error / OBDII Timeout"

I also have to close the proccess through Task Manager, the close button doesn't work

... all the while Scantool.net still works.

Thanks for the report. We'll try to replicate the issue on our end, and notify Steve (the program's author).

Vitaliy

Vitaliy · 09-04-2009, 03:29 PM

Quote: Originally Posted by Efess

Not so much an error, it just has an issue initializing the interface I guess. After picking the com port, it says PC Communications OK, than sits at "Checking Interface Hardware" for a few seconds before displaying the message "Interface communication error / OBDII Timeout"

I also have to close the proccess through Task Manager, the close button doesn't work

... all the while Scantool.net still works.

A colleague suggested something... do you have the latest firmware update? You may be able to get faster refresh rates.

http://www.scantool.net/scantool/dow...mware-updates/

Best regards,

Vitaliy

User Name		Remember Me?
Password