i had same problems, for me problem was that i was uploading old map from older fw.
after map uploaded to ecu then emu soft will crash, only way to get it work was downgrade fw to v2 then go to v3 again.
As i remember i opened older file without connected ecu, then save as new file, after that you can upload it to ecu without errors and crashing.
I will test it as it should work without any issues.
Thanks for reporting.
I’ve reproduced it. It is just a message nothing serious. However I know it is annoying. Just upgrade firmware in device to 3.038, and it will never appear again.
1 Like
Hello,
I would like to report 2 issues, I reported in past.
Its about “Project comparator”
- Function (Fn x) name is not reported in “View variables” section if it is changed.
( Iam using the function name as Project name, becouse there is no other way how to make some note about config which is uploaded to the car, which was possible in FW v2.xxx.
I really miss the functionality .
This window saved me so much time in previous firmvare:
)
- Last time I reported that in every project comparation you can see 0 changes in Custom corr. 1.
Now we have other two items with 0 changes.
The function compare is in the bug tracker already, but it require quite a lot of work to add it. I try to add it to version 3.040.
According to the project comment, I will add a separate field with 64 characters for the project comment.
2 Likes
when using external map sensor, for example 026123001U, if calibration map set 50kpa - 0.51v and 317.3kpa - 4.51v then in log it will read min 50kpa, but analog voltage will go lower 0.31v
so it will not go lower or past min max pressure in calibration map.
Yes, that is the way 2d tables work. They do not extrapolate data.
In most situations, the datasheet shows the data values that keep in declared tolerance range.
If you want to use values under the values from the datasheet you need to extrapolate it by hand and enter proper values into the table.
1 Like
okey understood! thanx
Hello, its me again 
It is possible its only my incorrect understanding of the system.
I found crazy Switch #1 behavior.
The switch is not aligned to any function, it just fyzicaly connected and I use it as a marking button in my measurements.
Connection:
MUX - not calibrated / not used
Switch #1 - Only marking button
Switch #2 - calibrated to activate idle controller
TPS - connected to TPS
When I push TPS over 4V the Switch #1 is activated.
Then I found some connestion also to MUX switch which is the thing Iam not using.
I checked if the behavior was also in FW v2 - Its only since v3.
Is there any measurement I should deliver?
Thank you.
It is quite complex. 
If you have an EMU BLACK hardware revision lower than “O,” the switches are implemented as a mux switch (resistor ladder connected to the analog input). They should be connected to the sensor ground; otherwise, if there is a ground potential difference, they may behave unpredictably (as they function as a voltage divider connected to an analog input).
In revision “O” and newer, there is an additional interface that isolates the multiplexer switch voltage divider from the inputs, so the switches don’t interfere with each other.
I’ve just checked the code, and both V2 and V3 use the same code for reading and filtering switches.
The communication problem is resolved in 3.039 version (already published)