For all EMU classics. Juuat pelase wait severql days for offcial anouncment as we test the firmware right now.
2 Likes
Iāll have to take the case apart and see exactly where the damage was done but something shorted out. I was able to open v3 studio, select emu classic, upgrade firmware successfully, and import a v2 emu black map for a bmw m50. I got a dialog message about it can only migrate trigger settings and a few other setting.. I press okay then it did its thing. Thatās when I notice the smell of the board shorting out. I immediately powered down. The pnp adapter is damaged. The emu was then bench powered and I was still able to connect to it in v3 studio and emu classic software was able to detect v3 firmware. I havenāt tried reverting back to v2 yet. Iām aware I have a classic but the option to import an emu black project file was allowed and the process was completed.
As far as Iām aware the emu grey/silver box and the new black box classic are the same inside.
It could be connected to coils settings.
Actually the classic firmware is tested in vehicles.
We plan to start open beta next week if our tests wi perform well.
Could you please provide me you base map that you used to import ?
I was able to apply the Fireware update this time around with revision C of the software. I still notice that the new V3 Studio does not play nice with my OneDrive instance. That isnāt a game changer, and I know some other ECU Software has challenges as well such as Haltech.
I just changed my default directory in the software options and continued on.
Could you please explain what is a ln issue with the Onedrive ?
For sure. My documents folder automatically syncs with onedrive. Essentially when I hit F2, and the studio tries to save a āquicksaveā file or when the firmware upgrade happens and it tries to automatically create a āUpdate packageā file, the save fails and states āunable to save to C:\users\User\onedrive\documents\Emu_black_V3ā for example.
When using the previous non Studio versions (V2 or V3) this error was not present.
Perhaps this is due to the New Studio version trying to leverage the exisiting V3 file structure and canāt write there due to some type of permissions issue?
I also may be unique, someone else may not have this issue.
I do know a friend of mine uses Haltech NSP and they have similar issues with losing config files and templates due to the Software not being able to properly access onedrive locations (or something to that effect).
Again, isnāt really an issue for me, as I changed the default location to C:\ecumaster, for example.
But thought I would bring it up as it seems to only be an issue in V3 studio, the other 2 software packages worked fine.
Let me know if you need any more details or screenshots, Iāll see what I can come up with.
Hello dear V3 fans 
Unfortunately, I noticed that this new V3 Studio is not running stably. When I checked the logs over a longer period of time (about 15 minutes), the program crashed several times. This was tested multiple times, and it crashed repeatedly. There may still be a software issue.
When the program crashes it generates a crashdump.
Could you try to crash it and provide crashdump file ?
2 Likes
I noticed a similar problem. But only after longer usage of software. The screen froze once and second time after minimizing window and closing laptop, when i went back and turn it on could not bring up screen from taskbar, restart sw helped.
1 Like
And frozen screen with message āNo responding" as well happened few times. Was able to generate 2 error reports today.
EcumasterEMUBLACK364_error_report_260404-100442.zip (1.3 MB)
EcumasterEMUBLACK364_error_report_260404-140351.zip (1.3 MB)
2 Likes
Iām also experiencing some crashes and freezes. I thought it was because Iām running it on Linux, but it seems to be a different problem.
It would be nice if double-clicking worked in this window.
Did you work with ecu connected or offline?
I used software Offline.
offline and Ecu Connected
Offline 
20characters 
The new client is very unstable, Iām experiencing a lot of crashing that has forced me to revert back to 3.063.