Bugs and Feature reqests
Important things that need to be improved :
-TPS settings resolution, one decimal digit
-Idle pid lockout strategy during decel
-fuel cut rpm vs coolant temp table
-table set 1/table set 2 break points independent from each other
And some more, that are important but not so basic :
-traction control with driven/nondriven wheel speeds
-charge temp blend with 2nd air temp sensor
-fuel cut/fuel cut resume timing advance gradual increase/decrease
-knock control, needs more lockout parameters, independent cylinder activation, gain per cylinder
-TPS settings resolution, one decimal digit
-Idle pid lockout strategy during decel
-fuel cut rpm vs coolant temp table
-table set 1/table set 2 break points independent from each other
And some more, that are important but not so basic :
-traction control with driven/nondriven wheel speeds
-charge temp blend with 2nd air temp sensor
-fuel cut/fuel cut resume timing advance gradual increase/decrease
-knock control, needs more lockout parameters, independent cylinder activation, gain per cylinder
Re: Bugs and Feature reqests
CAN EGT log channel value range is only 0 to 5.
Should be a bit higher.
Should be a bit higher.

www.Beth-Rennsporttechnik.de
Re: Bugs and Feature reqests
Is the idle pid activation via virtual par. output 3 working properly? I am ticking the option in idle pid, and then setting the virtual output 3, RPM->lower than 910>hysterisis 100, but i still see the pid lowring the valve dc at 1400rpm during deceleration. (910 because i have idle target at 860rpm warm and 50rpm deadband)
And, idle activation dc increase doesn't seem to work looking at the data logging, unless i am missing something. Is the activation dc added on the base dc, or is it a multiplier? Answered this myself with testing, multiplier
And, idle activation dc increase doesn't seem to work looking at the data logging, unless i am missing something. Is the activation dc added on the base dc, or is it a multiplier? Answered this myself with testing, multiplier
-
- Posts:15
- Joined:Thu Apr 13, 2017 9:01 pm
Re: Bugs and Feature reqests
Updated to 2.039, while connected to laptop every power cycle of the ECU would always state Client is different than ECU even though "make permanent" had been applied. Flashed back to 2.035 it went away.
Re: Bugs and Feature reqests
Can You add PWM of haldex pump and also PWM of solenoid valve to the emu CAN stream ?. And also what with haldex oil temperature sensor ?
Re: Bugs and Feature reqests
Regarding the version 2.041, bug fix "rpm spike (for low resolution trigger wheels and TFI) during cranking bug fixed" : i have this bug since i had the EMU, and now with the EMU Black, but it doesn't happen only during cranking, it also happens often during hard driving (full throttle and/at high revs). Already upgraded to 2.041
-
- Posts:15
- Joined:Thu Apr 13, 2017 9:01 pm
Re: Bugs and Feature reqests
Is it possible to see what differences are in the project Client Data and the EMU when the Client asks to use the Client Data or the EMU data upon laptop connection? It would be a great addition. Some changes are made offline that may need to have a second thought on the change before sending it to the EMU.
I am going through this issue now where the Client data is always different than the EMU data on every connection or key off/on (due to some user CAN settings issue per Jakub) and I can't tell what has been changed.
I am going through this issue now where the Client data is always different than the EMU data on every connection or key off/on (due to some user CAN settings issue per Jakub) and I can't tell what has been changed.
Re: Bugs and Feature reqests
In next version there will be fix for this issue (it happens when user can stream enabled).
turbofreak wrote:Is it possible to see what differences are in the project Client Data and the EMU when the Client asks to use the Client Data or the EMU data upon laptop connection? It would be a great addition. Some changes are made offline that may need to have a second thought on the change before sending it to the EMU.
I am going through this issue now where the Client data is always different than the EMU data on every connection or key off/on (due to some user CAN settings issue per Jakub) and I can't tell what has been changed.
Re: Bugs and Feature reqests
Could you provide us a log with that spike and your project data ?
nickbmw wrote:Regarding the version 2.041, bug fix "rpm spike (for low resolution trigger wheels and TFI) during cranking bug fixed" : i have this bug since i had the EMU, and now with the EMU Black, but it doesn't happen only during cranking, it also happens often during hard driving (full throttle and/at high revs). Already upgraded to 2.041
Re: Bugs and Feature reqests
It is already as PWM DC (it uses the same output and log channels)
RasPL wrote:Can You add PWM of haldex pump and also PWM of solenoid valve to the emu CAN stream ?. And also what with haldex oil temperature sensor ?
Re: Bugs and Feature reqests
This option is experimental and works only once after power up.
Activation DC increase is adder
Activation DC increase is adder
nickbmw wrote:Is the idle pid activation via virtual par. output 3 working properly? I am ticking the option in idle pid, and then setting the virtual output 3, RPM->lower than 910>hysterisis 100, but i still see the pid lowring the valve dc at 1400rpm during deceleration. (910 because i have idle target at 860rpm warm and 50rpm deadband)
And, idle activation dc increase doesn't seem to work looking at the data logging, unless i am missing something. Is the activation dc added on the base dc, or is it a multiplier? Answered this myself with testing, multiplier
Re: Bugs and Feature reqests
I don't see how it's an adder, it's clearly a multiplier based on what i see. I have to insert 8%, to get 2% dc increase with a base dc 24% (24x1.08=25.92)
I don't have any datalogs with the issue, but i do have an onboard video where it happened. Project, Honda S2000 F20C, multitooth. (12 evenly spaced crank, 4-1 cam)
I don't have any datalogs with the issue, but i do have an onboard video where it happened. Project, Honda S2000 F20C, multitooth. (12 evenly spaced crank, 4-1 cam)
Re: Bugs and Feature reqests
Has the second external lambda input been added yet?
Re: Bugs and Feature reqests
I've checked and Acivation target increase and Activation DC increase adds to the target and DC
nickbmw wrote:I don't see how it's an adder, it's clearly a multiplier based on what i see. I have to insert 8%, to get 2% dc increase with a base dc 24% (24x1.08=25.92)
I don't have any datalogs with the issue, but i do have an onboard video where it happened. Project, Honda S2000 F20C, multitooth. (12 evenly spaced crank, 4-1 cam)
Re: Bugs and Feature reqests
It is already added (for logging purpose)
Jon1465 wrote:Has the second external lambda input been added yet?
Re: Bugs and Feature reqests
Ok thanksJadzwin wrote:It is already added (for logging purpose)
Jon1465 wrote:Has the second external lambda input been added yet?
Also i will run out of inputs on the emu black the 6 I have are:
3 for DBW
Left lambda from gauge
Right lambda from gauge
Fuel pressure
To add extra inputs is it possible to have a Can module from the earlier emu with the 4 extra analogue inputs?
I plan to run a Bluetooth module so this will use up the serial connection.
Can the can bus output of the can module be connected to the can connection on the emu black and not use the serial connection at all? Just supply power to the can module.
-
- Posts:15
- Joined:Thu Apr 13, 2017 9:01 pm
Re: Bugs and Feature reqests
While developing my CAN display for MAP KPA yesterday, I noticed the MAP gauge will shoot back to 100 KPA when the the internal MAP sensor reaches over 412 KPA. Is this a boost limit shutdown point on the EMU?
Re: Bugs and Feature reqests
Rev counter went mad again today, so 2.041 didn't fix the issue, at least not besides cranking
Re: Bugs and Feature reqests
The fix was only for cranking. So you have seen the spike on your rev limiter ? Any misfire during this ?nickbmw wrote:Rev counter went mad again today, so 2.041 didn't fix the issue, at least not besides cranking
Re: Bugs and Feature reqests
It is fail safe value. This value is assigned if the MAP voltage is below or over operating range.
You can change it in Engine protection / Fails safe
You can change it in Engine protection / Fails safe
turbofreak wrote:While developing my CAN display for MAP KPA yesterday, I noticed the MAP gauge will shoot back to 100 KPA when the the internal MAP sensor reaches over 412 KPA. Is this a boost limit shutdown point on the EMU?