Lotus Elan Central

by **Oliver** » Sun 24.12.2006, 16:08

Hello everyone,

Got my ElanScan software running via the serial port on my laptop but i`m not getting any data - just errors. Does the serial port have to be configured in any particular way? Any advise appreciated.

Happy christmas !

Regards

Oliver Beames

by **GeoffSmith** » Sun 24.12.2006, 17:38

Oliver,

Sorry you're having problems.

ElanScan should take care of the port configuration. What error messages are you getting?

Geoff

by **Oliver** » Mon 25.12.2006, 11:10

Hello Geoff and all,

The errors appear to be:

IGN OFF:
BAD ECHO (sent: F4 56 1 B5 received 0 0 0 0)

ENGINE RUNNING:
BAD ECHO (sent: F4 56 1 B5 received FC)
received 0 0 0 0)
received 000 FC) etc etc

These are not always exactly as above, the text moves up the screen too quickly !
i may try another laptop, or is my ECU buggered ?!

Anyway, happy christmas to everyone

Best regards

Oliver

by **ailwyn** » Tue 26.12.2006, 00:49

Oliver,

Are you sure that Elanscan is using the correct COM port?

COM Port (through control panel > device manager) should be set as follows:

Bits Per Second: 9600
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None

This should ensure that the COM port settings are correct.

The ignition should be on (lights on dash) or the engine running before you hit "start talking".

If you have turned the ignition on, make sure you've not activated the immobiliser as that can cut power to the ECU, so for initial testing start the engine before connecting.

This error can be received when the ECU is not powered:
BAD ECHO sent: F4 56 1 B5

Second thing is are you sure you have a working ALDL cable? Can you test it on another car with another PC?

Ailwyn

by **GeoffSmith** » Tue 26.12.2006, 08:45

ailwyn wrote:The ignition should be on (lights on dash) or the engine running before you hit "start talking".

Should not matter. Without power, you get the "Bad echo (sent: F4 56 01 B5 received: )" message. When the ECU gets power but isn't responding, you will get a "not responding" or similar message. The trouble is that you appear to be getting some sort of returned bytes.... :smt017

After you've pressed F1, you can change the acquisition and update periods (the former is how frequently ElanScan asks the car for data and the latter is how often the display is updated) - change them both to e.g. 2000ms which will then churn out data every 2 seconds which gives you a chance to see what is happening. I will be more concerned if the returned bytes are inconsistent so no need to let me know exactly what is being displayed, but it would be good to get an idea as to how inconsistent they are.

ailwyn wrote:If you have turned the ignition on, make sure you've not activated the immobiliser as that can cut power to the ECU, so for initial testing start the engine before connecting.

Good point! It has caught me out a couple of times. :oops:

ailwyn wrote:Second thing is are you sure you have a working ALDL cable? Can you test it on another car with another PC?

I checked out the cable before sending to Oliver so it should be OK. If you can try it out on another car or pc, that would be good. Otherwise I'll send you my development cable to try out.

Let us know how you get on.

Geoff

by **Oliver** » Wed 27.12.2006, 20:15

Thanks for the help guys,

Changed my parity to NONE, other than that the COM port appears to be set ok.
Slowed down ElanScan`s sampling rate, still getting the same message - data sent, none received. When the ignition is switched on or the immobiliser blipped (to power up the ignition), the data received marker occasionally indicates 0 0 0 0 instead of nothing.
I can get an ancient P166 laptop by Saturday to try so i may be able to eliminate the COM port as faulty. Failing that i will drag my internet machine into the garage and give that a try.

When i switch the ignition on via immobiliser plip or the switch i can hear the fuel pump running, all the ususal lights illuminate, the ECU lamp blinks once and then extinguishes when the engine is started. When you put it into diagnostic mode it flashes `code 12` so presumably the ECU must be functioning ??

The thing is over fuelling badly, causing poor starting and cutting out when running in traffic, sometimes ok on long motorway runs. This is the problem i am trying to solve. It is driving me nuts - two years and counting. About the only items i haven`t replaced are ECU, fuel pump, pressure regulator, injectors, throttle body, TPS - i.e all the expensive bits !!

I am on standby Thursday night so won`t be able to fiddle but will catch up with you all Saturday.

Yours in hope

Best regards

Oliver Beames

by **ESM** » Thu 28.12.2006, 13:30

Changing the comm settings is futile - the program sets up the port (its a non standard baud rate of 8192).

Because both signals to and from the ECU travel down the same wire in the ALDL setup the request for data sent by the PC is also received by it - this is the 'echo'. ElanScan checks for the 'echo' and then for the reply from the ECU which should follow. If the former is not received, or doesn't match the outgoing message, you get a 'bad echo' error and if the latter a 'no reply. error. The interface should give an echo even if its connected only to the PC and not to the car. The bad echo indicates either the wrong port is set, a port failure, or an ALDL interface problem.

by **GeoffSmith** » Thu 28.12.2006, 15:45

ESM wrote:The interface should give an echo even if its connected only to the PC and not to the car.

Not with the serial interface, because it's open collector output and relies on the ECU pull up resistor to give a high level.
As I said earlier, without power, you should get the "Bad echo (sent: F4 56 01 B5 received: )" message. When the ECU gets power but isn't responding, you will get a "not responding" or similar message.

I was hoping to make a test lead to prove ALDL interfaces and to help resolve problems like this, but I haven't been able to get hold of an ALDL test socket - can any help or donate one from scrap car?

Geoff

by **ESM** » Thu 28.12.2006, 16:54

I stand corrected. Maybe the ALDL socket has a bent pin then?

by **Doug** » Thu 28.12.2006, 19:20

maybe crickey put a pin in the wrong slot

by **Oliver** » Sat 30.12.2006, 17:33

Hello,

Just tried another laptop with identical results. Pins in connectors seem ok. Any ideas ? I presume the ECU`s working because my engine runs albeit badly.

Regards

Oliver

by **GeoffSmith** » Sat 30.12.2006, 23:37

Oliver,

Although the ECU may be operational, there is a small chance that the ALDL interface circuits may not be working correctly.

If you have access to a multimeter, you could measure the voltage between 0V (ALDL pin A) and the interface line (ALDL pin G) - it should be 5V when the ignition is turned on. You should also see 12V on pin F permanently.

Although I tried out your interface to confirm functionality, there is a slight possibility that the S2 interface may be slightly different to the SE. It is possible that the long lead length is giving problems, so you could try shortening the leads. It's as simple as opening up the serial plug backshell and reducing the length of the cable. The cable is made off in a screw terminal to enable people to shorten the cable if they thought it was too long, so I labeled the connector with the colour of the three wires. Even if you manage to get it the wrong way around, it is bomb proof (I deliberately tested one with -15V to convince myself). If you have any queries, give me a shout.

I'm sorry you're having problems and I'm not in a position to send you a replacement straight away.

Geoff

by **Oliver** » Sun 31.12.2006, 15:07

Thanks for the tips, by the way i like the neat circuit board inside the connector shell, i`ll try your suggested tests, by the way my old machine is a 1990 non-turbo - don`t know if this makes any difference ?!

Oliver

by **Oliver** » Sun 31.12.2006, 17:18

Geoff,

I have measured the ALDL pins you mention and although i am getting battery voltage on pin F, pin G is only 3.30v to 4.00v, not 5v. Presumably this is why ElanScan is not working. Your little circuit board is a work of art by the way (i have shortened the cable).

Anyone got an ECU for sale ?! :cry:

I think Clemmo suggested it was later fitted to the Daewoo Espero ?!

Oliver

by **GeoffSmith** » Sun 31.12.2006, 18:26

Oliver,

That is about right with the interface plugged in. You should get 5V without the interface - sorry I should have made it clear.

I believe that the NA ECU is the same as the rest, it's just the MEMCAL which is programmed differently.

Geoff

by **GeoffSmith** » Sun 31.12.2006, 23:58

Thinking about this while painting the skirting boards, I wonder if anyone with an NA has ever run ElanScan. It could be that the dump initiation command might be different. Could Alan/Nige/Clemo/anyone confirm?

Geoff

by **GeoffSmith** » Mon 01.01.2007, 14:45

Oliver,

Alan and Nige have cannot confirm that it works with the N/A so I have e-mailed Clemo.

Watch this space before buying a new ECU!

Geoff

by **Oliver** » Mon 01.01.2007, 18:15

Geoff and other helpful Elan`ers

Thanks for your time whilst decorating etc.! My brain has become so preoccupied with getting the thing running properly i can`t sleep.

I did the voltage test on the ALDL test socket pins without the ElanScan cable attached - just stuck my probes straight into the socket.
Today i re tested the TPS which was 0.32v so i adjusted it to .40v and it appears to work in a proper linear fashion when you open the throttle.

I also carefully cleaned the ECU pins whilst referencing my EML manual. Still can`t get any response from ElanScan.

South West Lotus Centre have ECU`s for 150+vat but as you say the part no. for N/A and SE is different. Surely the only difference can be the mem-cal cartridge as you suggest but i won`t buy one unless someone can confirm it. We all know what assumption is! :!:

I also suspect the fuel pressure regulator but i haven`t got a price yet.

Anyway happy new year to you

Oliver

by **GeoffSmith** » Wed 03.01.2007, 00:56

Oliver,

I've cobbled together some bits for another interface. I'll get it built and checked out asap and will try and get it sent to you before the weekend.

Geoff

by **GeoffSmith** » Wed 03.01.2007, 13:52

geoffsmith wrote:Oliver,

Alan and Nige have cannot confirm that it works with the N/A so I have e-mailed Clemo.

Watch this space before buying a new ECU!

Geoff

Clemo has confirmed that he didn't try ElanScan out on his N/A.

Lotus Elan Central

Any advise on getting ElanScan working ?

Any advise on getting ElanScan working ?

Who is online