Not enough bytes received

[roj]

Hi everyone.

I've constructed my own Elan Scan cable and have had partial success. I can talk to the car and I can see data showing but when it comes to 'start logging' I get in the error log 'not enough bytes received'. I've checked settings, turned the latency down to 1 but still no joy. The only potential thing I can flag us is that my cable only has 9 wires in its construction! Sods law, the missing one is the top connection, second from right (and yes, I did continuity checks on all wires). To get around this I bridged it with a staple. I assume this isn't causing me the error as I see data in the window. Hit a brick wall for now. Laptop is a good 5-6 years old and running Windows 7.

Any help or useful comments would be gratefully received. Many thanks in advance.

Cheers, Rog.

[Tuga2112]

those messages are normal when its fully operational in my experience.

can you see the TPS value changing when your logging ?

TPS is the easiest one to check , ignition on. engine off. look at number. put foot on accelarator. look at number changing.

if it changes. your cable is workign

[roj]

Thanks for the reply Tuga.

Tried out your suggestion and no joy. I'm now not getting any data at all. Sigh...

I think this could be down to my missing wire/jumper connection throwing a spanner in the works. Anyone out there got a link to ebay for a new cable (that they've purchased from and has 10 wires inside)?

This is the cable that I purchased but it only has 9 wires in it!

https://www.ebay.co.uk/itm/364016033942

Happy to try another cable to rule it out.

[chrism]

Just a thought...have you updated to the new Elanscan _beta_usb and the new EScan m100 ALDL protocol?

These were LEC upgrades due to win11 not 'playing' and giving the same symptoms. I know you're running win7 but...

[roj]

I have indeed and set up the new protocol. I've just double checked my wiring/soldering/bridging piece. Added some solder to the bridging piece to ensure good connection and resoldered the ground wire. Will try again over lunchtime to see if that has made any difference. Thanks for the suggestion.

[roj]

Just tried again. Nothing at all.

I've also tried using every USB port on the laptop to check as well as adjusting the latency and response timeouts.

[Tuga2112]

if all else fails, i can sell you one i've made. been tested in my car.

[chrism]

With respect roj I'd suggest putting your location into your profile and hope that someone close to you can get in touch to use their known working stuff on your car - or beg/borrow their (known-to-work) lead.

[roj]

Good call Chrism. I’m banished away on the Isle of Wight.There’s a few hidden Lotus dotted around the island and one or two ‘classic’ specialist garages. I thought I’d have a go myself with one or two things but there will be a point I’ll give in and have things done.

[Tuga2112]

Isn't there a daveiow in the forum from there?

[roj]

Just had a look and not sure he’s on here or still an owner. I did see a user called ‘gov’. Thanks for the heads up.

[chrism]

I'm in West Sussex. You can borrow mine if you pay the postage, promise to handle with care and only keep it long enough to see if yours works

It'd be better, tho', if someone on IOW had the whole package so's you could substitute lead, laptop, EScan version winxx version etc

(PM me your name + address if you need to use mine.)

[roj]

Thanks Chrism. Will keep your offer in mind. Blimey. This is just the first part of the puzzle just trying to get ElanScan to work. Once sorted I can then look into error code 33 and the high idle speed. I won’t go off topic here though. One thing at a time.

[Fredjohn]

Just had a look and not sure he’s on here or still an owner. I did see a user called ‘gov’. Thanks for the heads up.

Daveiow is still on here, but he sold his Elan to another IOW resident and bought an Evora. Dave runs a campsite on the island.

Think the new owner is on here too.

[dapinky]

Of course, there is always the owner of the blue NA hiding away from all his creditors on the IOW....... but he wouldn't have Elanscan for his car!!!!

There are a couple of owners from IOW on here...... maybe someone will see this and respond,

[roj]

GOOD NEWS! I have Elan Scan working. Solution.....Purchase a new laptop. Put through the business as it can be used for other projects but thought I'd give it a try. Purchased the cheapest Win11 Laptop possible. I've been able to take logs from the car. At one point I lost all comms. Strangely, turn the ignition off on the car and then back on again and all seemed to start talking once more.

Next step. What's best practice to gather data? I'm chasing down the 'usual' high idle and running rich scenario. Start up from cold, sit idling till the fans kick in? I then guess go for a test run to gather data on the move.

Thanks everyone so far for all of your help/comments/pointers. Most appreciated.

[chrism]

Yep, that makes sense since. If I remember correctly, the old EScan 'runs out' when working with the later versions of win10 and the new EScan_beta was modified by LEC 'stars' when that fact was realised. Also around that time most older win7 machines were being updated or replaced with win11 newer ones. Win7 couldn't be reloaded on modern machines easily (why would you - other than to run EScan?) because it couldn't update - whilst initially configuring - since windows withdrew support for upgrades (needed to finalise loading) while they were 'encouraging' consumers into their new product...

Gathering data? I suggest use the 'start talking' then 'start logging' buttons and run the engine for at least 10mins or, if you like, until the fans cut in. That'll give you useful info about thermostat and fan temps.

When finished stop logging and talking, and EScan will give you the option to save your file somewhere (I have an EScan map file) as a xxxx.ecu file. Your Escan can read this. If you want to show it on LEC it needs to be compressed to a ZIP file then 'upload attachment' 'Choose file' then 'Add the file' to a LEC post so's we can all unzip it and read it on our machines in our EScans.

If find it most useful to compare 'problem' ecu files with known working files one aspect at a time - eg 'O2 sensor volts' or 'air/fuel ratio' - with a warm-up stationary data .ecu file. An 'on the run map' is useful, too, but harder to drill down into since variables are changing in response to other changing variables as you're on the move...

Attached is a .zip file which will look like the one we'll see your subsequent post. You'll need to unzip it if you want to play about with it in your own EScan and perhaps even compare it to your own scan. You can even load both scans and overwrite them on top of each other (they're different colours) to help with comparisons.

I think that's it; hope this helps...yeah, I know, a bit of a learning curve...

[roj]

Thanks for the feedback. This weekend will be retrieving data for me. Bit late in the day now to tinker as it's nearly pub time.

[roj]

Thanks for sending me your data Chrism. I've dropped that into ElanScan and overlaid with my recently acquired data. Interesting results! Some similar and others very much different. Unfortunately, all of this is way past my pay grade. I've now raised a new topic within the engines section and had a good waffle in there and shared my data.

As far as this post/topic is concerned, it can be marked as resolved. Thanks all to those who took the time to help.