Code: Select all
int dt = maxI(10, engineConfiguration->auxPidDT[0]);
https://github.com/rusefi/rusefi/issues/393 code is ready need to test
Code: Select all
int dt = maxI(10, engineConfiguration->auxPidDT[0]);
A custom version of firmware would be needed since default firmware would reset itself if an error is detected.puff wrote:Is there a way to extract the leftover data from the flash after it has been accidentally erased?
russian wrote:10ms is used in case of 0 period settingCode: Select all
int dt = maxI(10, engineConfiguration->auxPidDT[0]);
Unfortunately not. But on the bright side, we're getting pretty good at reproducing it. So testing of fixes may be easierrussian wrote: Looks like https://github.com/rusefi/rusefi/issues/341 fix was not a success?
I'll drive home on the old code, since I would like to get there. But I should be able to test the new code after dinner.russian wrote: https://github.com/rusefi/rusefi/issues/393 code is ready need to test
Maybe fixed now.stefanst wrote: I downloaded the latest and greatest. To jump right to the ending: It didn't work.
[The extension msq has been deactivated and can no longer be displayed.]
I would say 10mS is a bit too fast. I am not an expert on control engineering at all, but at 1000 RPM the cam only swings around 8.3 times a second. If I am not mistaken the cam has 3 tooth, so at 1000 rpm you only get an update of the cam position every 40 milliseconds. I think updating the PID loop has no real sense when no new input is available.kb1gtt wrote:Perhaps something to consider, perhaps dithering the control signal might help. With cold oil you might be faced with some hysteresis. Hysteresis could cause mean that when you command it to go to say 0% to 50%, it only gets to 40%. Or if you go from say 100% to 50% it only gets to 60%. This can cause a bunch of problems for you PID. However if you command 50%, then your output is 40% for like 5mS, and 60% for 5mS, the average is 50%. However this dithering commonly removes the hysteresis.
Is there a way to verify that your valve is reaching where you are commanding it to go? I suspect part of your tuning is that at low temp, when you command it to go to a position, that position is different when it is warm.
Also how fast does this need to react? Is 10mS perhaps to fast? Perhaps change that to 100mS, or 500mS.
4 our of how many shutting down engine with autotune? What is the ratio?stefanst wrote:Strike 4 for losing the firmware. Again, autotuning and shutting down the engine.
http://rusefi.com/temp/no_auto_reset.ziprussian wrote:I will build a custom version of firmware which does not reset to default automatically - this should help isolate the issue.
No.stefanst wrote:@: does your '03 have the same "feature"?
I think you hit it on the nose! I'm pretty sure I have them wired to the main relay (white/red wire). So this could be the way the power comes back to the board. Once the main relay is engaged it powers the board through some backdoor and that keeps the main relay engaged.russian wrote:I know your diodes are on the connector and I believe you had this issue even before adding the diodes. Does your IAC go to the right power source? Does your VVT go to the right power source?stefanst wrote:@: does your '03 have the same "feature"?
[The extension msq has been deactivated and can no longer be displayed.]