HidRo wrote:Well, I was thikning that I was being a numb dirk but it seems that I'm missing the Idle Advance, like it is described in page 7 of the PDF that comes with the firmware.
WHat am I doing wrong?
Enabled the PWM Closed loop, and this doesn't show up.
HidRo wrote:AhAH! I now saw it, and it's under the Extended menu, not the Advanced.
I'll give it a go, but I'm not sure the difference will be major, and hopefully, nothing bad will happen. I have 17º of advance at idle, and once I added 10º and the idle was the same. Not even a glich. So, if I understand correctly, if the idle is supposed to be at 1000, and it drops to 650 (in my case) it might add something like 30º?
muythaibxr wrote:gslender wrote:Greg G wrote:Just flashed it in today. Initial impression- very nice!
Something is still nagging me about the dashpot action with AC. It still seems not to apply dashpot when the AC is on. The dashpot decay seems to only apply with dashpot values of >7. But it looks really promising, have to get some more data on it. Love the logging of engine status and dashpot decay
There is a bug in the ms3 code that I've fixed... so should have something soon to correct that.
muythaibxr wrote:So I just tested this and it reacts the way I want. I changed it so that if the valve even starts closing, we engage the dashpot.
This avoids the issue that you were seeing with the quick blip (as long as the quick blip goes over the RPM at all the valve should be marked closed), and the issue I was trying to avoid as well (the valve closing then taking too long to reopen causing odd RPM fluctuations or stalls worst case).
It was a 2-line change. Diff will be in your inbox shortly.
pigga wrote:Hi G.
Thumbs up for your research and nice to see how your ideas come together with the developers' thoughts. I like it.
With the old CL idle code the Daspot-Adder was some kind of "safety buffer" to make sure CL Idle is entered from above idle Target, right? Just something like "New_Idle_PW= old_idle_PW+adder".
The new dynamic daspot will be added to the Inital-Value duty first and be decayed depending on actual RPMdot, i.e. the more stable RPM is, the faster it will be decayed, right?
But what will happen if the PID delay timer has expired and PID takes over CL idle? I am thinking about the situatuion that the adder has not been decayed to zero and PID takes over CL Idle (which may happen). Will Daspot be decayed additional to PID control, or willl CL idle just take over the actual idle PW at that point of time (and ramp down to target etc.)?
As you described, AC equipped cars can benefit from your code.
I equipped a Car with a MS that has an automatic gearbox. It is always hard for the old style CL idle to catch up RPM drop when it is shifted from "N" to "D" and vice versa. Do you think this can be improved with your code as well? As far as I understand it, the major advantage is that MS controls the load so it can react BEFORE the load is applied to the engine. With a automatic gearbox the RPM will drop in the same moment as MS gets the switch signal from the gearbox. Will it be an improvement anyhow? (I hope so )
gslender wrote:If you turned on and off the ecu many times before starting it might look like flooding due to the repeated priming.
Users browsing this forum: Exabot [Bot] and 2 guests