Hi. that would be nice, if there was an option to control nitro solenoid with pwm/dc x time its realy cool for big shots (better control for torqe)
I think it is possible, but make sure the message with the CAN analog is sent at least every 10ms (100Hz).
Nitro support is on the way!
I still appear to get a random drop in RPM when in idle state - the idle is stable before and after the times it happens…
The only thing I see in the log is the DBW DC goes from 34 > 0, but I have no idea why… unless anyone can see something I’m missing in the attached log.
This was a cold start on 3.036 (but happened on a number of previous versions too). It’s at 2min58s and is repeatable, always around the same time. Idle is otherwise great and functions as expected.
20241006_1635_24.emublog3 (1.6 MB)
987_18092024.emub3 (64.6 KB)
For me it seems the DBW DC changes are caused by I term of PID. DC always changes in those big steps when target TPS vs actual TPS is >0,2% which is ur deadband value. But interesstingly throttle isn’t moveing after the DC change. Just slowly the I term sums up later and then randomly it snaps below the target und is controlled smoothely back to target position.
I would assume ur throttle is a bit stucky or the motor a bit weird.
In first step i would clean the throttle.
Then i think u should play with the deadband values of ur DBW.
If it doenst help i would change the throttle and play again with deadband.
But for me it seems it is related to throttle control system only.
Your DBW delta error spikes to 12.5% right before this dip and your tps 2.6—>1.9. You can try less hz like 1000 to add more torque to the dbw blade just to test.
Can i ask when will arrieve the first public V3?
I have 3 customer cars running on V3 now and i cant provide remote desktop support them due to software permission…So is there any option how to solve this? Is there any limited version of permission or i have to ask for another regular one?
Thank you!
To make close beta open beta, we need to finish help for fueling and ignition.
I hope it will take about 2-3 weeks. Then the key will not be required.
So far I can generate you additional keys. Just send me machineInfo.dat file (in separate emails please).
1 Like
Still working on getting the transient fueling sorted (either that or something else is causing a delay and hard shudder when re applying the throttle), but I just wanted to say: the software improvements are much appreciated and very noticeable. The idle ignition PID controller, for example, is excellent and a huge step up over the V2 idle control.
2 Likes
thank you. In 3.037 there is an improvement for async acc enrichment.
Also if yiy use DBW now you can slow down the throttle opening for low RPM what should improve th transient response of the engine.
1 Like
Could you reproduce this issue with the DBW PID debug enabled and the latest firmware with the DBW HW debug ?
I’ll run it again tomorrow with that enabled and get a log 
Just a small one for now (call me fussy). In the oxygen sensor parameters, the title has the second ‘sensor’ mention misspelled (snesor).
Can we please get a logged status for the PWM outputs? Just a simple flag that says whether the output is active or not.
And/or…
Logged status for the function outputs?
Also, given that the parametric outputs have gone, can we have a dedicated EWP strategy? In V2 I used two virtual outputs, a virtual parametric output, and pwm1 to drive my water pump to mimic the manufacturers (Davies Craig) recommended strategy.
I’m hoping we could have an EWP strategy that works like:
EWP CLT set point 1: ___ (below this value set point 1 values are in effect)
EWP CLT set point 1 cycle on time (s):___
EWP CLT set point 1 cycle off time (s):___
EWP PWM DC below set point 1:___
EWP CLT set point 2: ___ (below this value set point 2 values are in effect)
EWP CLT set point 2 cycle on time (s):___
EWP CLT set point 2 cycle off time (s):___
EWP PWM DC below set point 2:___
PWM 2D table (CLT vs PWM DC) that is in effect if CLT is greater than set point 2.
Then the usual assigned output, PWM frequency, etc… Maybe you’d have to assign Timer 1 or 2 to the EWP strategy and/or give up some of the Function operators (because of resources)?
Thanks!
I also suggest returning to the possibility of calibrating the Flex Fuel sensor (hz- etanol cont.% ) like it was in the emu classic. Sometimes I come across flex sensors that often do not match the table 50hz - 0% 150hz-100%
1 Like
Thanks for your feedback.
Adding EWP support is not a problem. Could you explain what is PWM DC and PWM separate table for ?
All functions state is logged already (channels Fn 1 to Fn 12)
1 Like
What kind of sensor is that ? Are you sure it was original, properly working sensors ?
Excellent, thanks!
Just to clarify, the two ‘cool’ set points should have a PWM duty cycle value to run the pump at say 30% below 55° and then 50% below 70° (or similar - at user discretion) just to circulate the coolant to prevent localised hot spots.
Then a maybe 4-6 cell 2D user defined table to cover the ramp up/desired PWM % from the upper ‘cool’ set point through the lower to upper operating point.
And I’ll have another squiz for the function logs.
Cheers.
I mainly had problems with p/n 7645642 continental ( those in a wide housing ) they underestimated the bio value by about 12-15%. Theoretically they were from official distribution, but I will write in a PM from whom 
Other sensor like Continental Sv7 ( short housing ) or from your distribution ( ecumaster) show correct values
Just noticed, if I store or save desktops, the windows (most notably the 3D tables) change size (shrink). I was wondering why my fuel and ignition tables were shrinking - Now I know why.