Bluetooth ALDL interface for ElanScan and ALDLScan

[KenS]

I have a few built up a Bluetooth ALDL Interfaces which allow engine parameters to be viewed and logged using programs ElanScan (on PC/laptop) and ALDLScan (on Android phone/tablets). The build is using parts remaining from minimum order quantities of PCBs etc made for the original post unit. These interfaces are priced at £55 each (incl UK postage). Please PM me if you are interested in one.

complete-sml.jpg

Internally:

board-Ax.jpg

board-Cx.jpg

board-Bx.jpg

The units are of the design detailed here viewtopic.php?f=34&t=29379#p378756 comprising a ESP32-WROOM32 configured for classic bluetooth (BR) operation, hence most compatible with Windows drivers. Units have been commissioned for PCs with clean installs of Win10 and Win11 across a number of laptops using inbuilt Bluetooth and USB Bluetooth V4 and V5 dongles, all giving good performance (thanks goes to Chrism for running additional trials). The original Windows drivers for Bluetooth and Virtual Com Ports have been found to work well, however alternative 3rd party drivers have not been tested, so if you were to find incompatabilities with your particular installed drivers, then I am happy to provide full refund on return of the interface. Happy for any feedback on what does or doesn't work as a guide to all.
In addition to the ALDL/ODB1 function, an independant switch on the unit allows Service Mode to be selected (aka paperclip mode), allowing base timing to be set or simultaneously observe the effect of switching out the engine sensors via the ALDL function.
Brief instructions for setting this up on a PC:

How to setup.pdf

Info for using with Android: viewtopic.php?f=34&t=29379&start=20#p378959

[TrevorB]

Has this resolved the driver issue with windows 11 being covered by this thread? Or is it still ongoing?
viewtopic.php?f=34&t=28169

Trevor

[chrism]

Hi TrevorB.

I'm sure that KenS's new bluetooth obd1/ALDL connector serves to improve upon what I suspect is the driver provision problems that seem to manifest in the latest win updates for ElanScan.

A clean load of the earliest version of win10 seems to support EScan - though it complains bitterly of 'error logs' - but H22/23 verions and subsequent versions of win11 seem to cause reading/logging problems (on my l/top at least...) with my cabled EScan adapter c/w the older serial -> usb based drivers. (I haven't been able to load win7 to see how effective it was when compared with earlier XP-ish versions although running it virtually on win11 is something I feel I ought to do...)

I think Ken uses different processors - so his new bluetooth solution provides an alternative - while RonR might still be looking for a solution that'll utilize obd1 cabled adapters.

Hope I haven't offended by answering, sort of, 'out of turn'...

[KenS]

Hi Trevor & Chris - Using a Bluetooth interface does away with the need for the FTDI chip and its drivers, so thats one possible issue removed. The Bluetooth interface does require the PC to have 'Virtual Comm Port' drivers, and Windows normally provides those. Running trials with clean installs of Win10 and Win11, those Windows virtual Com Port drivers have so far worked well and ElanScan works well with very few or no reported faults/errors. However if alternative drivers are installed (maybe supplied via the FTDI driver set?) I cannot be sure of the effect. Hence I am a little bit cautious in saying that using a bluetooth interface will fix all the problems, especially where alternative drivers have been installed. One advantage of a bluetooth interface is that it can also be used with a phone app such as ALDLScan, which is a system completely independant of windows and its drivers, so free from that original problem, however those apps are not comprehensive as ElanScan is in visually displaying and comparing data. Trevor, if you want to see how a Bluetooth interface works on you system, I would be happy to send one over, just PM me the address, it would be good to get more coverage. ( - Chris, always appreciate your input, keeps things alive)

[RonR]

Hi Trevor,
I prepared a reply much the same as Chris and Ken's above, but I think they've answered better than I would have.
However when we tried Dave's Bluetooth interface with your laptop and car at CC we couldn't get it to work.
This one uses different hardware so it's worth a try.

Meanwhile I've tried using several alternatives to the FTDI chip to get a cabled solution working, some were complete non-starters but 2 are worth further investigation.

[TrevorB]

Thanks for the responses which although I sort of understand have mainly gone over my head.

I'm sure I will catch up with RonR next time at an NKLG event and he can update me with it all.



Trevor

[funandsea]

Hi Ken,
Do you still have these available?

If so what would be the cost with shipping to FL USA?

Thanks James

[phamm61]

Just found this page and would be intersted it buying one .
!992 Se

[phamm61]

Are theese still available as i would like to buy one
peter