…and talking about the benefit of hindsight…
In Apr ’22 I was lamenting my poor fuel cons and worried about impending MoT emissions so I decided to '1499/O2sensor' my ’90 SE relying on Wiki, RonR and KenS’s copious hand-holding (…thanks fellas)
ElanScan, despite its erroneous claims, showed all was ‘closed loop’ - and well - until it expired due to the win11/FDTI drivers legacy (there’s a long thread on this…) and it effectively ‘stopped’ for me. Jan’23’s MoT emissions were pleasingly lean and green tho’...
Later superhuman effort by these fellows got it limping back in win11, but with the same annoying ‘logging’ anomalies, so having trialled Ron’s 9930/1499 dual initiative followed swiftly by his 1499/Everest I was really keen to try KenS’s BTScan ‘magic’ ALDL adapter. It provides all the usual EScan ‘treats' but in a brand new bluetooth format.
(Ken also spotted the ALDLScan bluetooth link with his new adapter and he provides a bespoke LEC-specific m100 pathway that adds the ability to use our (andoid) mobiles to inspect static ecu data as well - which sealed its usefulness in my book.)
Unfortunately for me, BTScan was so useful that it exposed the fact that (despite suspecting higher fuel cons and noticing really poor Jan’24 MoT emissions) a data log showed that I must have been running open loop for most of 2023.
(The A4 connector on the RHFHC connector behind the splash-guard in my driver’s wheel well had de-pinned meaning that my O2 sensor wasn’t getting the necessary heater supply during this time - happily now fixed with long-nosed pliers)
Sooo…RonR’s 1499 upgrade + ‘Son of Mountain Chip’ and KenS’s ‘Daughter of ElanScan’ + ALDLScan have certainly enhanced my m100 life - and imo both deserve a place together on this ‘Update’ thread. My copy of Ken's bluetooth adapter is picced above
- I thought it was only me...
) , slide circuit board back in, replace three screws.