Brought Vag kkl 409.1 did mod to make it work with holdens vr to vy ALDL and it worked only paid $8 + shipping for cheap cable
Then thought could i make, and use the case for an ESP32 Mini, it would then have WIFI & Bluetooth for cheap as packet of chips
Got case for ALDL to connect the car, have esp32 mini, just waiting on buck converter to arrive
Then make single wire ALDL mod to esp32 RX TX + Gnd wire
I can then make firmware for esp mini to talk in WIFI or Bluetooth to ALDL network. ALL this for $8 for cable - $9 for buck converter - $10 esp mini = $27 bucks
Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
-
Rapidfire
- Posts: 66
- Joined: Sun Oct 18, 2026 9:56 am
- cars: Vp Group A Rep
Ve 6.0 Lsa 6 speed Ute
Vf Redline Wagon
L300 Van with 3.8 Buick
Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
You do not have the required permissions to view the files attached to this post.
-
vlad01
- Posts: 8600
- Joined: Mon Oct 08, 2012 8:41 am
- cars: VP I S
VP I executive
VP II executive
VP II executive #2 - Location: Kyneton, Vic
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
How do the drivers work? and how does TP see this if it's via BT or WiFi?
I might be interested if I could get it to work in TP in linux with some sort of pass through wine?
I got the regular USB ALDL cable working on my VPs perfectly, but it needed some custom rules made and registry hacks to get a sort of passthough happening, it relied on there being a consistent device that the rules auto detect the device and apply the custom parameters to get 8192.
I might be interested if I could get it to work in TP in linux with some sort of pass through wine?
I got the regular USB ALDL cable working on my VPs perfectly, but it needed some custom rules made and registry hacks to get a sort of passthough happening, it relied on there being a consistent device that the rules auto detect the device and apply the custom parameters to get 8192.
-
Rapidfire
- Posts: 66
- Joined: Sun Oct 18, 2026 9:56 am
- cars: Vp Group A Rep
Ve 6.0 Lsa 6 speed Ute
Vf Redline Wagon
L300 Van with 3.8 Buick
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
you`ve got right questions vlad01vlad01 wrote: Sat Nov 14, 2026 1:28 pm How do the drivers work? and how does TP see this if it's via BT or WiFi?
I might be interested if I could get it to work in TP in linux with some sort of pass through wine?
I got the regular USB ALDL cable working on my VPs perfectly, but it needed some custom rules made and registry hacks to get a sort of passthough happening, it relied on there being a consistent device that the rules auto detect the device and apply the custom parameters to get 8192.
I need to start at end and work my way forward to get to beginning, to show i got to wanting to make ALDL with esp32 mini
tuner pro rt needs to see virtual com port bidirectional,
I'll use my Windows app as an example I'll include Fabula tech, it creates a virtual com port in my windows app for the Wi-fi. App is written for CAN bus But also can be written for Aldl communication
when the ESP32 mini is configured for Wi-Fi, It would need to be set as a hotspot.
I'll use my t43 Commander app for this example, when your laptop connects to the hotspot it will show the ESP's 32 IP address
the commander then asks you to enter in its IP address into t43 command app, fabula tech then creates a virtual comport and creates the connection between Wi-Fi and the ESP32.
this is what tuner pro RT requires to be able to connect to the aldl esp32 mini.
I just don't know how Linux would create this connection And if there's an application out there or if Linux has already inbuilt to make the virtual comport
let me know if you follow so far
if you're using Microsoft Edge my app is unsigned it'll show as a virus I use Firefox for downloading and I've scanned it with Norton and it shows it's all clear
anyone that downloads it can reverse engineer it I have no issues with that
I'm more than happy to share the source code with this as well
You do not have the required permissions to view the files attached to this post.
-
vlad01
- Posts: 8600
- Joined: Mon Oct 08, 2012 8:41 am
- cars: VP I S
VP I executive
VP II executive
VP II executive #2 - Location: Kyneton, Vic
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
Linux doesn't know com ports, it knows serial ports or adapters. In my case the OG DelcoHacking ALDL cable is an FTDI chip via USB. So it sees it as it is, a USB device with serial attached to it (eg. dev ttyUSB0).
The com port is sorted by mapping the "windows" environment in wine to point your desired com port to the linux device, but the device settings are entirely handled outside on Linux, this is where I had to wright up some custom rules that force the FTDI into 8192 as soon as it's plugged in, the app in wine has no way of telling the FTDI what to do since com ports is strictly a windows thing and doesn't exist in Linux.
So the com port mapping isn't an issue, but how will Linux see the device when connected and whether is knows it's got serial is another question. In my experience, linux is usually much better than windows at detecting and installing devices without needing drivers to be installed or special software to use it, unlike windows. So it might be work out of the box with some luck, but I am not sure with wifi or BT sitting in between the two ends.
Personal experience, I think BT is better for these sorts of IoT devices, at least for end to end scenarios. I often do my tuning in the shed and I get wifi from the house 30m away no probs, so having internet access without swapping to the ALDL adapter hot spot would be better. At home I have used both wifi and BT IoT devices (in my case aquarium dosing pumps), BT is way better, saving so much time mucking around swapping from internet to the devices wifi and back and I have had some devices where it won't work unless I disable 5Ghz capability on my router, phone or laptop. BT just works and automatically connects when I access the app, I don't need to manually connect to the hotspot, BT seems to be a far more robust connection to IoT I found too (albeit with a shorter range), never once had a single drop out, unlike wifi.
The com port is sorted by mapping the "windows" environment in wine to point your desired com port to the linux device, but the device settings are entirely handled outside on Linux, this is where I had to wright up some custom rules that force the FTDI into 8192 as soon as it's plugged in, the app in wine has no way of telling the FTDI what to do since com ports is strictly a windows thing and doesn't exist in Linux.
So the com port mapping isn't an issue, but how will Linux see the device when connected and whether is knows it's got serial is another question. In my experience, linux is usually much better than windows at detecting and installing devices without needing drivers to be installed or special software to use it, unlike windows. So it might be work out of the box with some luck, but I am not sure with wifi or BT sitting in between the two ends.
Personal experience, I think BT is better for these sorts of IoT devices, at least for end to end scenarios. I often do my tuning in the shed and I get wifi from the house 30m away no probs, so having internet access without swapping to the ALDL adapter hot spot would be better. At home I have used both wifi and BT IoT devices (in my case aquarium dosing pumps), BT is way better, saving so much time mucking around swapping from internet to the devices wifi and back and I have had some devices where it won't work unless I disable 5Ghz capability on my router, phone or laptop. BT just works and automatically connects when I access the app, I don't need to manually connect to the hotspot, BT seems to be a far more robust connection to IoT I found too (albeit with a shorter range), never once had a single drop out, unlike wifi.
-
vlad01
- Posts: 8600
- Joined: Mon Oct 08, 2012 8:41 am
- cars: VP I S
VP I executive
VP II executive
VP II executive #2 - Location: Kyneton, Vic
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
I asked google and this was the response when I asked what 8192 baud compatible BT devices existed, and then asked the following below, sounds all easily doable, but a tad more work than the standard USB cable adapter I already got working, but sounds like the 8192 is handled by the device directly? If so, that's one less step on the script/rules side of things to do from what I gather.
Going by what is says, either serial devices it comes up with will work. You can map more than one serial device in wine in the windows regedit, if it's not the same device as the cable, then you just map it to another com port number, eg com2 which you will need to change in TP depending on which adapter you are using at the time. So no different to native windows.
"When using an ESP32 bridge, will linux automatically recognize the BT device as a serial port? or will more work needed to be done to get that kind of connectivity?
No, Linux will not automatically mount a Bluetooth Classic SPP device as a /dev/ttyUSB* or /dev/rfcomm* serial port out of the box. While Linux natively supports the Serial Port Profile (SPP) through its BlueZ stack, you must manually pair the device and bind it to an RFCOMM virtual serial device using terminal commands.
1. Bluetooth Classic vs. BLE on Linux
• Use Classic Bluetooth (SPP): Make sure you use an original ESP32 (or ESP32-WROOM/WROVER) with the BluetoothSerial library, not newer chips like the ESP32-S3 or ESP32-C3. Newer variants only support Bluetooth Low Energy (BLE), which does not natively create standard serial ports in Linux without complex third-party bridge scripts.
2. Required Terminal Steps to Create the Port
Once your ESP32 is powered on and advertising its Bluetooth Serial service, you need to run a quick sequence in Linux:
• Pair and Trust: Open bluetoothctl in your terminal to scan for your ESP32's MAC address (e.g., AA:BB:CC:DD:EE:FF). Run pair <MAC_ADDRESS> followed by trust <MAC_ADDRESS> so Linux remembers the device.
• Bind the Serial Port: Exit bluetoothctl and run sudo rfcomm bind 0 <MAC_ADDRESS> 1 (the 1 specifies RFCOMM channel 1, which ESP32 uses by default). This command creates the virtual serial port at /dev/rfcomm0.
• Set User Permissions: By default, /dev/rfcomm0 is owned by root and the dialout group. Run sudo usermod -aG dialout $USER (and log back in) so your diagnostic software or serial terminal can access the port without sudo.
3. Automating the Connection
• Systemd Service: The rfcomm bind command does not persist after a reboot. If you want /dev/rfcomm0 to be available automatically on startup, you can create a simple systemd service file that executes rfcomm bind whenever the Bluetooth service starts.
• Baud Rate Note: When opening /dev/rfcomm0 in your Linux software, the baud rate setting in the Linux app doesn't actually matter over Bluetooth—the ESP32 handles the exact 8192 baud timing on its physical UART pins regardless of what speed your Linux software thinks it is using."
Going by what is says, either serial devices it comes up with will work. You can map more than one serial device in wine in the windows regedit, if it's not the same device as the cable, then you just map it to another com port number, eg com2 which you will need to change in TP depending on which adapter you are using at the time. So no different to native windows.
"When using an ESP32 bridge, will linux automatically recognize the BT device as a serial port? or will more work needed to be done to get that kind of connectivity?
No, Linux will not automatically mount a Bluetooth Classic SPP device as a /dev/ttyUSB* or /dev/rfcomm* serial port out of the box. While Linux natively supports the Serial Port Profile (SPP) through its BlueZ stack, you must manually pair the device and bind it to an RFCOMM virtual serial device using terminal commands.
1. Bluetooth Classic vs. BLE on Linux
• Use Classic Bluetooth (SPP): Make sure you use an original ESP32 (or ESP32-WROOM/WROVER) with the BluetoothSerial library, not newer chips like the ESP32-S3 or ESP32-C3. Newer variants only support Bluetooth Low Energy (BLE), which does not natively create standard serial ports in Linux without complex third-party bridge scripts.
2. Required Terminal Steps to Create the Port
Once your ESP32 is powered on and advertising its Bluetooth Serial service, you need to run a quick sequence in Linux:
• Pair and Trust: Open bluetoothctl in your terminal to scan for your ESP32's MAC address (e.g., AA:BB:CC:DD:EE:FF). Run pair <MAC_ADDRESS> followed by trust <MAC_ADDRESS> so Linux remembers the device.
• Bind the Serial Port: Exit bluetoothctl and run sudo rfcomm bind 0 <MAC_ADDRESS> 1 (the 1 specifies RFCOMM channel 1, which ESP32 uses by default). This command creates the virtual serial port at /dev/rfcomm0.
• Set User Permissions: By default, /dev/rfcomm0 is owned by root and the dialout group. Run sudo usermod -aG dialout $USER (and log back in) so your diagnostic software or serial terminal can access the port without sudo.
3. Automating the Connection
• Systemd Service: The rfcomm bind command does not persist after a reboot. If you want /dev/rfcomm0 to be available automatically on startup, you can create a simple systemd service file that executes rfcomm bind whenever the Bluetooth service starts.
• Baud Rate Note: When opening /dev/rfcomm0 in your Linux software, the baud rate setting in the Linux app doesn't actually matter over Bluetooth—the ESP32 handles the exact 8192 baud timing on its physical UART pins regardless of what speed your Linux software thinks it is using."
-
Rapidfire
- Posts: 66
- Joined: Sun Oct 18, 2026 9:56 am
- cars: Vp Group A Rep
Ve 6.0 Lsa 6 speed Ute
Vf Redline Wagon
L300 Van with 3.8 Buick
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
Thanks for infovlad01 wrote: Sun Nov 15, 2026 2:01 am I asked google and this was the response when I asked what 8192 baud compatible BT devices existed, and then asked the following below, sounds all easily doable, but a tad more work than the standard USB cable adapter I already got working, but sounds like the 8192 is handled by the device directly? If so, that's one less step on the script/rules side of things to do from what I gather.
Going by what is says, either serial devices it comes up with will work. You can map more than one serial device in wine in the windows regedit, if it's not the same device as the cable, then you just map it to another com port number, eg com2 which you will need to change in TP depending on which adapter you are using at the time. So no different to native windows.
"When using an ESP32 bridge, will linux automatically recognize the BT device as a serial port? or will more work needed to be done to get that kind of connectivity?
No, Linux will not automatically mount a Bluetooth Classic SPP device as a /dev/ttyUSB* or /dev/rfcomm* serial port out of the box. While Linux natively supports the Serial Port Profile (SPP) through its BlueZ stack, you must manually pair the device and bind it to an RFCOMM virtual serial device using terminal commands.
1. Bluetooth Classic vs. BLE on Linux
• Use Classic Bluetooth (SPP): Make sure you use an original ESP32 (or ESP32-WROOM/WROVER) with the BluetoothSerial library, not newer chips like the ESP32-S3 or ESP32-C3. Newer variants only support Bluetooth Low Energy (BLE), which does not natively create standard serial ports in Linux without complex third-party bridge scripts.
2. Required Terminal Steps to Create the Port
Once your ESP32 is powered on and advertising its Bluetooth Serial service, you need to run a quick sequence in Linux:
• Pair and Trust: Open bluetoothctl in your terminal to scan for your ESP32's MAC address (e.g., AA:BB:CC:DD:EE:FF). Run pair <MAC_ADDRESS> followed by trust <MAC_ADDRESS> so Linux remembers the device.
• Bind the Serial Port: Exit bluetoothctl and run sudo rfcomm bind 0 <MAC_ADDRESS> 1 (the 1 specifies RFCOMM channel 1, which ESP32 uses by default). This command creates the virtual serial port at /dev/rfcomm0.
• Set User Permissions: By default, /dev/rfcomm0 is owned by root and the dialout group. Run sudo usermod -aG dialout $USER (and log back in) so your diagnostic software or serial terminal can access the port without sudo.
3. Automating the Connection
• Systemd Service: The rfcomm bind command does not persist after a reboot. If you want /dev/rfcomm0 to be available automatically on startup, you can create a simple systemd service file that executes rfcomm bind whenever the Bluetooth service starts.
• Baud Rate Note: When opening /dev/rfcomm0 in your Linux software, the baud rate setting in the Linux app doesn't actually matter over Bluetooth—the ESP32 handles the exact 8192 baud timing on its physical UART pins regardless of what speed your Linux software thinks it is using."
In rar is flash setup firmware, guide it explains what you`ve spoke about, and a parts list. fully agree bluetooth is way to go
If i am missing anything let me know, but its more about wiring it up ALDL to Esp32
You do not have the required permissions to view the files attached to this post.
-
Rapidfire
- Posts: 66
- Joined: Sun Oct 18, 2026 9:56 am
- cars: Vp Group A Rep
Ve 6.0 Lsa 6 speed Ute
Vf Redline Wagon
L300 Van with 3.8 Buick
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
Ive orded parts to make this now, ive got an old dell 630 to put linux on. but only got vy wagon - if it work with vy adx then it will work on anythingvlad01 wrote: Sun Nov 15, 2026 2:01 am I asked google and this was the response when I asked what 8192 baud compatible BT devices existed, and then asked the following below, sounds all easily doable, but a tad more work than the standard USB cable adapter I already got working, but sounds like the 8192 is handled by the device directly? If so, that's one less step on the script/rules side of things to do from what I gather.
Going by what is says, either serial devices it comes up with will work. You can map more than one serial device in wine in the windows regedit, if it's not the same device as the cable, then you just map it to another com port number, eg com2 which you will need to change in TP depending on which adapter you are using at the time. So no different to native windows.
"When using an ESP32 bridge, will linux automatically recognize the BT device as a serial port? or will more work needed to be done to get that kind of connectivity?
No, Linux will not automatically mount a Bluetooth Classic SPP device as a /dev/ttyUSB* or /dev/rfcomm* serial port out of the box. While Linux natively supports the Serial Port Profile (SPP) through its BlueZ stack, you must manually pair the device and bind it to an RFCOMM virtual serial device using terminal commands.
1. Bluetooth Classic vs. BLE on Linux
• Use Classic Bluetooth (SPP): Make sure you use an original ESP32 (or ESP32-WROOM/WROVER) with the BluetoothSerial library, not newer chips like the ESP32-S3 or ESP32-C3. Newer variants only support Bluetooth Low Energy (BLE), which does not natively create standard serial ports in Linux without complex third-party bridge scripts.
2. Required Terminal Steps to Create the Port
Once your ESP32 is powered on and advertising its Bluetooth Serial service, you need to run a quick sequence in Linux:
• Pair and Trust: Open bluetoothctl in your terminal to scan for your ESP32's MAC address (e.g., AA:BB:CC:DD:EE:FF). Run pair <MAC_ADDRESS> followed by trust <MAC_ADDRESS> so Linux remembers the device.
• Bind the Serial Port: Exit bluetoothctl and run sudo rfcomm bind 0 <MAC_ADDRESS> 1 (the 1 specifies RFCOMM channel 1, which ESP32 uses by default). This command creates the virtual serial port at /dev/rfcomm0.
• Set User Permissions: By default, /dev/rfcomm0 is owned by root and the dialout group. Run sudo usermod -aG dialout $USER (and log back in) so your diagnostic software or serial terminal can access the port without sudo.
3. Automating the Connection
• Systemd Service: The rfcomm bind command does not persist after a reboot. If you want /dev/rfcomm0 to be available automatically on startup, you can create a simple systemd service file that executes rfcomm bind whenever the Bluetooth service starts.
• Baud Rate Note: When opening /dev/rfcomm0 in your Linux software, the baud rate setting in the Linux app doesn't actually matter over Bluetooth—the ESP32 handles the exact 8192 baud timing on its physical UART pins regardless of what speed your Linux software thinks it is using."
Thanks vlad01 Ive got sum home work todo
-
vlad01
- Posts: 8600
- Joined: Mon Oct 08, 2012 8:41 am
- cars: VP I S
VP I executive
VP II executive
VP II executive #2 - Location: Kyneton, Vic
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
Awesome, keep the thread updated 
-
antus
- Site Admin
- Posts: 10111
- Joined: Sat Feb 28, 2009 10:34 am
- cars: TX Gemini 2L Twincam 8psi
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Subaru WRX 2007
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
BT classic does not support 8192, so you'll need to communicate to the ESP as 9600. Then it becomes possible to overrun the ALDL so you'll need to think about how to handle or prevent that. It'll also change timings so stock oseplugin probably won't work. You'll need the Linux version Vlad posted (even for this hardware on windows) because of its improved comms stack. You'll need to consider the speed of the link to the PC. If you receive the whole 8192 packet then send it at 9600 you'll loose nearly half the serial bandwidth. So ideally you want to stream it. Then you need 2 threads or 2 uarts and/or proper interrupt handling. All doable, but needs to be done right. Real hardware UARTs on the PC and the ALDL side will help a lot, but your main loop needs to keep data moving, and not drop any.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
-
vlad01
- Posts: 8600
- Joined: Mon Oct 08, 2012 8:41 am
- cars: VP I S
VP I executive
VP II executive
VP II executive #2 - Location: Kyneton, Vic
Re: Car ALDL to ESP32 Mini Wifi or Bluetooth VR,VS,VX,VY
Yeah I was kinda sus on the response on the 8192 baud thing, didn't quite sound right to me, but I know nothing about the BT or ESP32 side of things.