ECU model (EMU Classic / EMU Black / EMU Black V3 / EMU PRO)
Connection type (EDL-1 / CAN BUS - Bluetooth module / BT Module)
Short description of the issue
Steps to reproduce (if possible)
Screenshots or screen recordings (if available)
Example:
Device: iPhone 14 Pro
iOS: 17.2
ECU: EMU PRO
Connection: CAN BUS Bluetooth
Issue: Lambda value stuck at 0.12
Steps: Added Lambda gauge → value does not update
The more details you provide, the easier it is for us to reproduce and fix the issue.
_____________________________________________
Known Issues & Status
Below is the current list of reported issues and their status.
Issue Description
Source
Status
Notes
There is no possbility to change min and max for Gauge Widget
Apple Store
Fixed
In version 0.0.36
Cannot resize widget to 4x3 when other widgets are placed above
Community
Investigating
Status Legend
Investigating
In Progress
Planned
Fixed (in next build)
Cannot Reproduce
Needs More Information
_____________________________________________
We’ll keep this post updated as issues are reviewed and resolved.
Thank you again for your support — your feedback directly helps us improve eDash
Just installed the app and tried to make my own layout when I noticed the following.
Device: OnePlus 15
Android:16
ECU: Emu Black (not connected)
Connection: EDL-1 (not connected)
Issue: Can’t change the size to 4x3 depending on what’s on screen
Steps: add 2 or 3 ‘text value’ to the top of the screen and try to add another item.
Thank you for reporting this — I really appreciate it!
I suspect this may be related to how the layout system currently works.
Depending on how much free space is available for a given widget, only certain sizes are offered. The available space is calculated starting from the widget’s top-left corner.
I’m aware that the interface does not clearly explain this behavior, which makes it unintuitive and can give the impression that some size options disappear “without reason.”
Could you please try moving the problematic widget to a location where there is plenty of free grid space to its right and below? In that position, all available size options (including 4x3) should appear.
If that resolves the issue, then it’s likely the behavior described above rather than a sizing bug itself.
We already have interface improvements planned in this area for March to make this behavior clearer and more intuitive. I’ll also add this to the tracking table above.
I’ve quickly tried it by moving all the current widgets down, that does indeed solve the issue.
Perhaps something like a red tint to the widget when it doesn’t fit, and you can move it until it turns green could be a good indicator?
Your idea for solving this is very good. Unfortunately, at the moment we don’t have the technical possibility to allow one widget to overlap another (even partially) or to extend beyond the screen boundaries.
Because of this, we will approach the solution differently. In the “Widget Size” field, all available sizes for a given widget will remain visible. However, for the sizes that cannot fit in the current position, we will display a clear message such as “Not enough space.”
This way, the user will better understand why certain sizes are not available in a specific location, instead of feeling like the options disappear without explanation.
Below I’m sharing a draft/mockup of this solution for reference:
This would indeed give a heads up to the user, and hopefully make it a bit clearer. However this won’t solve the issue of widget placement.
Can the widget automatically be moved to where there is room? Otherwise we’ll have to keep shuffling around until a specific size can be placed.
I’m not in app development myself, but I guess the widgets get placed at a pre-defined location? Having this location be ‘move where it fits’ would already solve most of this issue. Otherwise that pre-defined location has to be kept empty up to the last widget is placed on screen.
For now, we will proceed with the solution I described above. It’s the minimum necessary change to make the behavior clearer and help users understand what’s happening.
At the moment, we’re also heavily focused on implementing several important features that we want to release as soon as possible — including alarms, the Check Engine indicator, and support for imperial units.
Once those core features are in place, we’ll be able to revisit and further refine the widget placement logic.
Thanks again for the thoughtful feedback — it’s very helpful.
Just to clarify — was this tested on EMU Black with the newest software (EMU Black V3)?
This will help us understand whether the issue may be related to the ECU software version. Thank you in advance for confirming.
At the moment, we don’t have this feature in our current development plan.
However, I’d really like to better understand why this would be useful for you. Could you share a bit more about your use case? For example, what would make editing dashboards on a PC easier or more important in your setup?
Your feedback helps us decide what to prioritize next, so I’d appreciate any additional details
Ease of setup, so much easier to navigate on a laptop screen than a tablet, especially if you have it permanently mounted in the dash, if not i dont see it a big deal, but if you are it will increase the overall use experieince
Thank you for your response emu is running version 2.161 and edl-1 was running an older version but has since been updated to version 1.23 however readings are still showing the same
Kind regards paul
Update since updating edl-1 to version 1.23 sd card is no longer registering and just flashes red and when put new sd card in it works however iv noticed now that e dash doesn’t seem to like it sat with vehicle stationary speed is now going from 0 - 60kph back to 0 on its own with vehicle stationary this seemed to all work ok before v1.23 update
Latest update have tried all firmware versions available for edl however when using e dash it says connected to edl and Bluetooth led on edl is on and green Bluetooth logo on edash but nothing is reading at all no no rpm,speed limit,coolant,lambda nothing
So final test found if edl is on v1.23 once installed sd will not read and led goes red however if put another card in it reads and led is green but on e-dash readings are all over the place rpm is at 148rpm with engine off then when running speed goes up and down while vehicle is stationary
If I install previous versions eg. 1.22,1.12,1.10,1.08
No issues with cards reading and logging however none of these versions now seem to work with e-dash it connects to Bluetooth on edl but won’t read any data at all even if I put it to the previous version that was working for me before which was v1.12 now doesn’t seem to work,which it was reading fine except the Lambda reading as previously mentioned. Nothing else has been changed/updated only the edl firmware
Yes, that’s perfect place And the good news is that we are planning to add this Data channel. It will work only with supported devices - as I remember you have EMU BLACK V3 and EDL-1? If yes, it will work for you.
It’s a part of a bigger feature, so it will take couple of weeks to implement.
How to Report a Bug
Known Issues & Status
Fixed
Investigating
In Progress
Planned
Cannot Reproduce
Needs More Information
And the good news is that we are planning to add this Data channel. It will work only with supported devices - as I remember you have EMU BLACK V3 and EDL-1? If yes, it will work for you.