Elanscan not working

[geoffelan]

Hi all, just tried Elanscan and got No reply
No frame start byte received
Any ideas as to what is wrong?
Thanks Geoff

[chrism]

More details needed really, geoffelan...eg:-

Has it ever worked?

Is your version of EScan (see the 'ElanScan' thread) and Protocol up to date? (It was updated in 2024 for later win10 and all win11 versions.)

Are you using the COM port that your l/top defaults to?

Can you post your EScan results for us to see? (This is yet another part of the learning curve that involves zipping the .ecu file and attaching it to a post...)

Do you know that your cable works? etc etc

[geoffelan]

Ok I made a cable and downloaded elanscan from the forum after watching how to on you tube
did everything according to the video, running windows 10 on a MacBook Air 2015
comm port is correct. First try at using elanscan
cheers Geoff

[chrism]

geoffelan, ElanScan was born ages ago on android parallel/serial port architecture and has seen com ports and USB changes in more modern times like win7 and win8.

All was fine and dandy until we found that early versions of win10 'played ball' but the later versions (and win11) wouldn't, I think, due to the USB2->USB3 upgrades which were taking place surreptitiously and taking EScan-ers by surprise.

LEC stars such as Matt, Ken and Ron put their shoulders to the wheel and moved legacy EScan into our modern times by producing the 2024 upgrade called 'new ElanScan_beta_USB' and the consequent 'new EScan M100 Protocol'. It's a 'sticky' in the ElanScan thread.

I dunno if MACs running win10 have the same evolution, so my first thought would be to find a pal with working android EScan to test your cable and get you started on the learning curve then if you can get it working on a MAC please let us know?

(If someone on LEC has already got there with his MAC then he/she's the person to give best advice to you.)

[RonR]

IIRC I spotted recently that someone got it working on a Mac, the gist of it was to install the USB-Serial drivers on both MACOS AND in the Windows VM:

https://forum.lotuselancentral.com/viewtopic.php?f=34&t=30570&p=385133&hilit=elanscan+mac%2A#p385133

[chrism]

Hur...that's our pal NoahR whose EScans + battery probs we've just been looking at

[NoahR]

Ok I made a cable and downloaded elanscan from the forum after watching how to on you tube
did everything according to the video, running windows 10 on a MacBook Air 2015
comm port is correct. First try at using elanscan
cheers Geoff

Hi geoffelan,

I also run ES on my MacBook. I've got a couple of questions;

1) By what method are you running Windows on your Mac? E.g. Bootcamp, VMware, etc.
2) Do you have another Windows machine you could run Elanscan on just to test the cable/other bits?
3) Is your device manager picking up the device as an FTDI device? Specifically not an unknown device.
4) Can you try and load another ElanScan file into the software, and see the data from that file? - If you need help doing that, let me know. You should be able to find another file by going through a couple of threads in this section of the forum.

Finally, if I remember correctly, I used this https://web.archive.org/web/20180327082 ... _ALDL.html, specifically, ElanScan_Beta (0.10.12.71), version; I'm not sure if this is different to the one on the Sticky, but it could be worth checking if it is and, if it is, trying the above version.

Update: I did just test the newer version of ES from the sticky, and that seems to work fine as well. Could still be worth trying the old version as well though, if that is different.

Let us know how it goes or if you have any questions!

[geoffelan]

Hi NoahR,
running windows via bootcamp, no other machine, FTDI is working correctly,
my first attempt was with a version of ElanScan downloaded from the manuals section on here,
that did not work, following advice from the forum I got rid of that version and downloaded the
newer version from the sticky on here and I have tried it with the ignition on engine not running
(in the garage) and it shows all the parameters like prom I.D. voltage, coolant temp, air pressure,
throttle pos voltage(this goes up when I press the throttle) etc, have yet to try with engine running
(bad weather). I will try it on a run soon and let you know what happens.

Cheers Geoff.

[chrism]

Hi geoffelan, looks like you're almost there... So the next stage might be evaluating your data, or possibly comparing your values by 'zipping' up your data and posting it for us all to see .

In my humble opinion a run out will be the second set of data to look at: An easier first set of data might be a 10min warm-up (or till the fans cut in) because you'll be able to see where the sensors start from and (fairly straightforwardly) how they interact with each other. (Accelerating and braking causes a domino effect which can be hard to differentiate...just a thought...)

I know I'd be happy - as would others - to post our warm-up in this thread so that you can 'see what you're in for'?

ps great news that Mac-ers can finally come in from the cold.

pps another thought - will we be able to compare EScan data from these different formats?

[NoahR]

Geoff, good to hear that it's working! - If its showing data without the engine on, I imagine it will be fine on a run down the road.

pps another thought - will we be able to compare EScan data from these different formats?

Chrism, what do you mean? If you mean Mac vs Windows, ES is running on Windows still, just on Mac hardware. ES still saves so to a .ecu file, so data sharing should be fine. I might have misunderstood you, though!

Definitely good to get more Mac owners using ES.

[chrism]

...dur...yes I remember briefly runnning other windows versions in 'VMware Workstation' on my windows PC a while ago trying out the new version of EScan and I've just clicked onto the fact that that's precisely what you're doing - running windows (virtually) within MAC hardware so the outcome is still 'EScan-in-windows'...dur...

High five for opening more doors to LEC...

[NoahR]

Yep exactly!

I thought it might be problematic, especially with Apple silicone non-Intel chips, but all seems fine so far