Problems under Vista with ES and Interface

[jecuk]

I think this may be caused by problems with my USB/serial adapter. I connect the little box to the plug under the glovebox and a light comes on. Start up the laptop, run ES and then all I get is No reply messages. The LHS is not populated at all.

I have tried different USB/serial drivers and turned down all the FIFO buffers etc but there is no latency option.

On Geoff's website it seems like the boxes are now passe (I inherited mine from Andrew with the car) and it can all be done with a USB cable interface. Am I better to go that way?

[al]

Am I better to go that way?

better to get rid of Vista too
Sorry, that's not very helpful

Is the USB->Serial adapter a known-good model ?
If it's not based around the FTDI chip then all bets are off...

[ailwyn]

IIRC the USB cable produced by Geoff includes a usb 2 serial conversion, so you're likely to get the same issues, providing that you have the correct driver installed.

Noddy questions but they have to be asked...
Have you checked that vista recognises the serial port, and checked which COMxx it's assigned to?

Have you selected the correct port in ES?

[jecuk]

Yes, it is COM9 and this is set in ES.

[ailwyn]

No idea then, ES + one of ESMs USB interfaces (which uses the FTDI chip) works fine for me under Vista, so it would appear to be either a driver or USB 2 Serial issue.

[jecuk]

It is a Prolific chip so looks to be a problem. Anyway, nothing lost, I had it and thought it worth a try. Have ordered the full isolated kit from Geoff now.

Should go well with the V5 chips also on order.

[tweetdriver63]

I tried my new laptop a couple of days ago. It has Vista. Here's how it went:
First, the laptop was already on.
I connected the USB cable to the computer first. When I did, the computer did the usual thing it does with the "USB xxx device connected" type message, and asked about looking for a driver. I ignored that.
Next I opened elanscan (which is the new beta version, if that makes a difference).
Then I connected to the ALDL.
I got the same "no reply" message you did, so I started changing the com port. I went throught all 20 ports with no change.
Next I disconnected from the ALDL, then reconnected.
VOILA!!
I was back to com port 1, and up and running. I don't know why. Maybe the connector just wasn't well seated the first time, or maybe it needed elanscan running before connecting to the ALDL.
Whatever, it's working now.

[GeoffSmith]

Jason,

The Prolific chip has transmit and receive buffers: ES relies for correct operation on any data being sent or received making its way through with no delay and the buffers may affect this. The FTDI chipset is the same and it is important to set the latency to 1ms to avoid this problem. It might be worth checking the advanced settings.

Geoff

[jecuk]

Thanks Geoff. I tried setting the buffers as low as could go and turning them off. There is no latency option on the drivers in advanced settings. Please just send the USB unit when you can and I will start afresh.

I think the unit Andrew had is a very early development unit. On the website they seem very small now in comparison.

[John_W]

jecuk,
The ElanScan interface which Andrew Ennis had (and has presumably given to you) is the same as mine.

It is from Andy Whittaker, and is a serial-port type interface Andy used to make for the Esprit to run freescan, the Esprit equivalent of ElanScan. Although Freescan doesn't work for the Elan (ESM developed ElanScan), the interface does. It came as a made-up circuit board without a case, so Andrew put it in an aluminium case from Maplins.

Mine still works fine on my old laptop with the serial port, but I also bought one from Geoff for when my old PC goes belly up and I have to use a new one which only has USB ports.

John

[jecuk]

Thanks John, that explains the differences.