In the next build (tommorow) there is an EKP fuel pump support with the separate table for pump DC
I have a couple more suggestions for you.
Can you please add a minimum RPM to the launch control so that it doesn’t enable ignition retard before a minimum RPM? Currently if I floor it, I get a random backfire and slower RPM increase due to the ignition retard being enabled. Allowing a min RPM of say 3000 will allow revs to shoot up quickly, then retard can kick in till my set RPM of 4000. I suppose I could also do this with a function like if CAN15 + RPM > 3000 then turn on launch control. But a direct option is easier.
Secondly when reviewing the Graph Log, and moving the mouse around on the log all the other active tunable maps track with that mouse movement. Love that feature. But if you could add a Click function to select the active cell in the cross hairs that would be great. It would allow me to jump straight to fuel or ignition maps and +/- the selected value instead of clicking it.
In the launch control there is parameter Target - RPM delta to activate.
“RPM below the RPM target above which launch control is activated.”
If you have any issues below this RPM it is probably not caused by Launch control.
There are two problems with that. When you double click on the graph log, there is already functionality (channel configuration). Also you lost focus to your window with the table.
I will make some experiments. Maybe when your table window is focused and you move the cursor over the log, the cursor on the table follows the log.
Or pressing middle mouse button
The current output test limit is set to 100 cycles, which is too low for comprehensive injector testing. Please update the maximum allowable number to at least 10,000 cycles.
How about a timer based rpm limiter for drag use? X axis time Y axis limit rpm. Can be activated from lc exit state.
Can we get a spectrogramm like forexample haltech has? The calculated knock frequency is almost always inaccurate or does not give the best signal to noise ratio. A spectogramm would make finding the best knock frequency like a piece of cake not needing audio equipment and goldwave anymore
hi its been over 1 year now. do you think that we can find a way to solve the issues i have with abs errors . if needed i can try to get what ever hardware tools is required to solve this as i now have 2 cars with the same issues @Jadzwin_ECUMASTER look forward to hearing from you
Can you remeber me what ABS / car ?
Not possible, there is no hardware in the ECU to do that.
It could be added to the Timers section where you can already control timing and boost.
so this particular abs system is only found from 2005 to 2010 in polo gti 9n3 and seat ibza cupra 6L with esp 8 system
Is there a problem with the stock car ? Or there are modification to the any of modules ?
OK let me reexplain .
vw polo gti 1.8t 2007 model swapped with a dq250 on a stock ecu bosch me7.5 that uses CANbus pq34 from my under standing . with a stock ecu i have no warings on the dash . now i have fitted a ecumaster emu black with a plug and play harness . the abs lamp and traction lamp and esp-button will stay on . sometimes if you put the key on and wait for a few 30seconds befor starting the abs will not be on . but traction and esp button will stay on if u take vcds and clear the codes in the abs it will come back immediately .
the abs system is called (esp 8) this system predates UDS and mqb . it dose not use long coding.
this is the errors in the abs
( Control Module Part Number: 6Q0 907 379 AT HW: 6Q0 907 379 AT
Component and/or Version: ESP 8.0 front H03 0003
Software Coding: 0002317
Work Shop Code: WSC 31414 000 00000
VCID: 0F7A48D2FB416922DE9-50D0
2 Faults Found:
18055 - Check Coding of ECUs on Powertrain Data Bus
P1647 - 000 -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 2
Fault Frequency: 1
Reset counter: 160
Mileage: 148528 km
Time Indication: 0
01314 - Engine Control Module
000 - - - Intermittent
Freeze Frame:
Fault Status: 00100000
Fault Priority: 2
Fault Frequency: 1
Reset counter: 200
Mileage: 148528 km
Time Indication: 0
this is in the abs system.
this is what i have tried .
i hope that we can sort this out
Would it be possible to add Variable Nozzle Turbo (VNT) boost control ? These turbo’s have traditionally been used on Diesel engines, but are becoming more common on Petrol engines. They have great response, when controlled correctly. I’m building a VNT turbo setup for a motorcycle, and could use some additional features in the EMU Black SW to control it.
The VNT actuator can be controlled using the H-Brige EWG controller in the V3 SW. The main difference from a EWG setup is that a too high DC (vanes closed) restricts exhaust flow severely, leading to extreme backpressure and loss of VE (torque). During spool an EWG setup generally targets 100% DC to get the fastest response.
For the VNT turbo:
At 4000rpm a DC of 100% may give 2bar backpressure before turbo is spooled
At 10000rpm a DC of 100% may give 6bar backpressure, and engine VE drops by 10-20% due to restriction. So at 10000rpm you don’t want to exceed 50% DC (2bar backpressure)
I think VNT control can be added with the addition of:
- 1D table (EWG DC max, based on airflow)
- optional: 1D table (EWG DC min, based on airflow)
- Dropdown selection “DC below margin” –> Add EWG DC max table
- Channel in datalog
Some additional info below:
Good day ECU Master Team!
It would be really cool if the following featurs were added:
- Send the main relay status to the CAN bus (currently only a physical output)
- Add a forced fan on switch
- Add a forced fan off switch, either before a critical threshold or after a certain amount of time.
Hello, I am returning to the request for activation delay time of the overrun strategy, fuel cut enter rate ( %/cylce ) would be welcome too. And would it be possible to change the cutting strategy, including changing the ALS1 and ALS2 maps? For example fuel cut for Als1 and spark cut for Als2
The question is if you disconnect DSG gearbox, and then start the engine, is there the ABS error ?
We can work on this after official V3 release in November.
I try to add this for next build