Thank you for pointing this out – we will correct this in the next app update so that the information is not misleading.
Currently, the hardware and system requirements are described in detail in the “Start Here” post and in the Manual.
I had a go at it yesterday with no luck, the app wouldn’t discover the device
Device model: Samsung A26
IOS / Android version: UI 8, Android 16
App version / build number: 0.0.43
ECU model: EMU Black V3.064
Connection type: EDL-1 V1.26
Ive always had issues with the Bluetooth connection on this EDL, it would only very occasionally actually connect and show data on the old app. But I was optimistic about all the work that’s been put into the V3 and the new app so gave it another go.
Other than not connecting I noticed that all the EDL data in the V3 software data logs show nothing “EDL connected: NO”
The data logs have always worked fine saving to the SD card. Green light flashes indicating logging and the blue light has a slow blink.
If there’s anything I can try let me know, this is my personal car I’m happy to spend some time on it
Thanks
The iPhone 15 with the old EDL does not connect to the new EDL without a connection problem
Samsung a11 android
Bt module ecu master
Black v3 3.061
TPS only goes up to 50% @ wot
Injector trim won’t receive data
-
Short description of the issue - No device found under eDash Bluetooth on iPhone and Samsung devices. EDL Status in V3 software is good for connected, card state and bluetooth state.
-
ECU model EMU Black V3 firmware 3.061.
-
Connection type EDL-1 firmware 1.26.
-
Device model iPhone 16 Plus.
-
iOS version 26.4.1.
-
App version 0.0.43 (75).
-
Device model Galaxy A03s.
-
Android version 13.
-
App version 0.0.43 (24).
-
EDL-INFO.TXT:
Requires Android 11+.
Hi, so I’ve been using the new software on my iPhone and works ok. But now my logging onto the SD card only sometimes works. The attached log just stops recording. I have a RED flashing light?
Also the time stamp is wrong after update.
Both EDL and Black V3 are using latest version’s.
18154209.BG3 (6.3 MB)
I just said to an emu classic owner guy with the bluetooth circular plug module, to install the latest edash from playstore, from the 5 minutes i played with it. Fuel Pressure showed 6bar instead of 3bar. EMU Classic firmware was 1.218. Connection was pretty fast and solid
Ah ok sorry. I chickened out updating the firmware because it was a first meet with the client i didnt want to brick any firmware update… We just did a briefing about the car and its problems and what he needs.
Any updates on this? Can I download grade the firmware so I can actually log data reliably?
Testing in the Middle East market.
Device model: Ruancheng Android Headunit
Android version 14
App version 0.0.43
ECU model EMU Black V3
Connection type: BT Module
There is a known issue where the android head units don’t connect to Bluetooth BLE devices or connection drop after a short time. If we can create a new product just for Edash to support non BLE devices with all the features like with an option in the BLE module to use usb or switching mode to non BLE. I am not sure if EDL1 is BLE or not but the canbus to Bluetooth is BLE. This is important as most of the cars connecting would want their Android head unit to connect to the ECU.
can we continue testing on BLACK V3 3.065 or stay on 3.064(d)
@noobtuner You can test on BLACK V3 3.065 
-
Device model (nothing phone 2, lenovo tb310xu tablet)
-
iOS / Android version (nothing phone 2 android 16, lenovo tablet android 13)
-
App version / build number app v0.0.42(22)
-
ECU model (EMU Black V3)
-
Connection type (EDL-1 old one )
-
Short description of the issue
I have problem that the edl-1 dont show the blue light, and it wont find the connection for my phone or tablet in the app but if i search for bluetooth in the phone it finds the emu logger.
This is a known limitation at the moment — older EDL-1 devices are not yet supported, but we’re actively working on adding compatibility.
The reason is that older EDL-1 units use so-called “Classic Bluetooth” (SPP protocol), while eDash currently supports only Bluetooth Low Energy (BLE).
That’s why the device is visible in your phone’s Bluetooth settings, but does not appear inside the app.
possible to get the old app to work with v3? or do i need to wait you guys to get this fixed?