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.
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.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.
Are you sure that the light that is on, is really the "Check Engine" light, and not some other service light?The device also couldn't read any engine codes, even though my check engine light has been on..
Which other free software have you tried?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!
We can try some advanced troubleshooting with STNTerm, if my other suggestion doesn't solve your problem.