Bugs and Feature reqests

[Urosch89]

Hi, have you news about MAF strategies, for example Bosch HFM?

Best regards and good job!

[Jadzwin]

Just enter the value one step less, faster tuning

In car it is very complicated to use the mouse. It is better to use only keybord.

So if you want to enter value to cells just select the cells (SHIFT + arrows like in excel) and just type the numers or press enter.
If you want to make any math operation just write it. Eg 2* will multiply all cells values by 2. You can scale it by percent (eg. 90%) and so on.
It is more comfortable way to work with tables than press mouse button, select enter value, enter value, press enter.
With EMU table idea it is much much faster.
And od not forget about undo option. You can undo all operation you made by just pressing CTRL+Z

i aggree, but for setting up the table its nice to select some cell's and then click enter value like in DET3.
but maybe its just because i am use to it. will see.

[Jadzwin]

Actually not

Hi, have you news about MAF strategies, for example Bosch HFM?

Best regards and good job!

[RHD]

I think there is a software problem or bug with Inverse analog IP#1 ??

I have a customer who uses it to receive the A/C request. It will work assigning the Analog I/P #1 selection but we need it to work on the INVERSE I/P #1 setting, but when we select the inverse setting it does not activate at all no matter what we do, again works fine on the normal I/P assignment but of course its backwards.

I can reverse the compressor O/P but then we dont get any idle up control etc.

[nickbmw]

The table axxis wizards are insufficient. If someone wants to add a break point or relocate one, it's a whole procedure.

[WHPZach]

There's a problem with the analog input scales. If you try to modify the voltage break points for the analog inputs, the changes you make in one table (i.e. oil temp) also make changes in the other tables (i.e. oil pressure). This poses a problem if you have one sensor with a 0-5 volt scale, but another sensor with a .5-4.5 volt scale

[nickbmw]

There's a problem with the analog input scales. If you try to modify the voltage break points for the analog inputs, the changes you make in one table (i.e. oil temp) also make changes in the other tables (i.e. oil pressure). This poses a problem if you have one sensor with a 0-5 volt scale, but another sensor with a .5-4.5 volt scale

The same is with the main fuel and ignition maps. All tables share the same axxis values. If you change the x or y axxis in the VE map 1, it goes to all the other maps, VE map 2, Lambda target maps, Ignition 1 & 2 maps. If you decide you need to change a breakpoint or two, you literraly have to redo all maps.
One would think that 20 rpm break points are enough for all engines, but they are barely enough for a 9200rpm engine with vtec. On table set 1 i need more resolution at low rpm, on table set 2 i need more resolution at high rpm, but i have to find a compromise for both because i can't have different rpm axxis between the tables 1 and 2. This is a huge downside, and from what i know it continues like this on the EMU Black.

[Jadzwin]

That is a limitation of EMU and EMU black that some tabled share the same axis.
Good news is that you modify axis in VE table #1, all tables that using this axis will be racalculated, so there should be no need to touch it (it will work as befora axis change).

In our next ecu the size of the tables and axis are fully independent and it depends on tuners choice how big are tables (and of course memory budget ).

[nickbmw]

That is a limitation of EMU and EMU black that some tabled share the same axis.
Good news is that you modify axis in VE table #1, all tables that using this axis will be racalculated, so there should be no need to touch it (it will work as befora axis change).

In our next ecu the size of the tables and axis are fully independent and it depends on tuners choice how big are tables (and of course memory budget ).

How long before the new ecu release?

[Jadzwin]

We delayed project, because we are working on DI and want PRO to be able to support DI.

However we are about to launch power management unit:

http://www.ecumaster.com/products/pmu/

It is based on PRO hardware platform.

[nickbmw]

Looking forward for the pro then.

In fueling -> rpm vs map correction table, i scaled the x axxis 10-100kpa, when i checked my file it was 5-44kpa. I am trying to change it and it doesn't accept anything more than 44kpa

[Jadzwin]

I've just tried and cannot reproduce it.
Could you send me your base map ?

[nickbmw]

I've just tried and cannot reproduce it.
Could you send me your base map ?

I didn't save that map and now i can't reproduce it too, just checked. I will give it another try tomorrow

[oneten]

Hi Guys,

Just wondering if my request as per the below will be considered or not? I'm currently hoIding out hope I can do bottle heater control with the EMU but if not I will need to get another solution asap.

Even if we can just include a "Misc Pressure Sensor Input" which I can scale myself to then use.

Thanks,
Hayden

Is there any chance we can add a sensor input for Nitrous Bottle Pressure & Brake Pressure? I want to use the EMU to monitor Nitrous Pressure and also to control the bottle heater on/off.

I wanted to use A/C Pressure for the Nitrous Bottle Pressure but upon looking it only goes up to 5000KPa (About 750 PSI). Nitrous sensor would need to scale up to about 1300-1500PSI (8000 - 10000KPa).

An input for Brake pressure would similarly need to read up to about 2200 - 2500PSI.

I have 0 - 5v rationmetric sensors that read up to 2500PSI to use for both of these applications but the only way I think I can make this work for now is to use a parametric output based on raw MV values.

Thanks guys!

[nickbmw]

Is there any chance you could add 2 more rpm points (22 total) onto the main fuel/ignition maps?

[ihiryu]

I have a customer who had an EMU with a FW version of 1.160 (I think). I updated the FW to the latest 1.178, and now the ECU is having issues with saving.

It continually reverts back to an older file, even though we are clearly hitting F2. I haven't had a chance to go back and try to downgrade to 1.177 to see if this fixes the problem.

Has anyone else had this issue?

[WHPZach]

Is there any chance you could add 2 more rpm points (22 total) onto the main fuel/ignition maps?

That's not likely.

Also, when scaling your axes, add resolution where you need it. You'll need resolution down low for idle/drivability, but beyond that the VE won't change drastically, just add resolution where you need it and reduce it where you don't. I can't think of many engines that would benefit from more resolution than 20 breakpoints on the rpm axis.

[samvel]

I have a customer who had an EMU with a FW version of 1.160 (I think). I updated the FW to the latest 1.178, and now the ECU is having issues with saving.

It continually reverts back to an older file, even though we are clearly hitting F2. I haven't had a chance to go back and try to downgrade to 1.177 to see if this fixes the problem.

Has anyone else had this issue?

I have had some weird behavior with 1 emu after fw update. "Restore to defaults" (in File menu) have solved problem in my case.

[nickbmw]

Is there any chance you could add 2 more rpm points (22 total) onto the main fuel/ignition maps?

That's not likely.

Also, when scaling your axes, add resolution where you need it. You'll need resolution down low for idle/drivability, but beyond that the VE won't change drastically, just add resolution where you need it and reduce it where you don't. I can't think of many engines that would benefit from more resolution than 20 breakpoints on the rpm axis.

N/a engines with high rev limit/large engine speed range, do have wiward ve curves, then add on this another set of cams (vtec). Yes, 20rpm points do the job for a 9500rpm engine, but the shared rpm axxis between the table sets is making it even more tricky as i have a lot of cells taking space at low rpm for driveability that i need at the second table set for the vtec, which engages ar 3600rpm. Just for reference, Haltech has 32x32, Link has 20x22 and AEM has 17x21 on their ems4/series 2.

[WHPZach]

Is there any chance you could add 2 more rpm points (22 total) onto the main fuel/ignition maps?

That's not likely.

Also, when scaling your axes, add resolution where you need it. You'll need resolution down low for idle/drivability, but beyond that the VE won't change drastically, just add resolution where you need it and reduce it where you don't. I can't think of many engines that would benefit from more resolution than 20 breakpoints on the rpm axis.

N/a engines with high rev limit/large engine speed range, do have wiward ve curves, then add on this another set of cams (vtec). Yes, 20rpm points do the job for a 9500rpm engine, but the shared rpm axxis between the table sets is making it even more tricky as i have a lot of cells taking space at low rpm for driveability that i need at the second table set for the vtec, which engages ar 3600rpm. Just for reference, Haltech has 32x32, Link has 20x22 and AEM has 17x21 on their ems4/series 2.

You seem to have a new request every 3 days. I appreciate your enthusiasm, but why not focus on getting the car tuned with what's available to you? I can assure you that 2 additional RPM break points won't make or break the performance of your car. I've tuned 13krpm engines satisfactorily with a 16x16 map, you just have to do a little planning/experimenting rather than throwing a ton of breakpoints at it. We would all love to have an infinite number of tables and breakpoints, but the EMU is very much a value-driven product aimed at ease of use.