Start Button Function

[mtmotorsport]

Setting up the push button start function and I've run into an issue.

Current config:
Proteus 0.7 F7, firmware snapshot 1019
Start Pin: Analog Volt 11
Mode: Default
Starter Control: Lowside 10
Crank max time: 5 seconds

With the laptop connected the engine cranks immediately upon request. With no laptop connected the engine will not crank until about 6 seconds has elapsed from ignition on. So if you hold down the start request from ignition on you must continue to hold for about 6 seconds. If you turn ignition on, then simply wait about 6 seconds before depressing the start button it cranks right away. I cannot get a datalog of this behaviour for two reasons. First, like mentioned above, with the laptop (USB) connected it cranks immediately. Second issue is the internal flash drive does not enumerate, neither the RUSEFI internal drive with the ini file, or the USB Drive (SD Card).

[mtmotorsport]

Link to MSQ

https://www.rusefi.com/online/view.php?msq=1274

[mtmotorsport]

Possibly rectified the SD car logging issue. Card was not inserted properly.

[AndreyB]

Let's isolate the issue. Can we move starter control to an unused output temporaraly and focus on start button input? Unused output is better than NONE output since it reduce change of functionality being deactivated.

In TS "View->engine_state" do you see proper state change of startStopState?

image.png (49.56 KiB) Viewed 1586 times

[AndreyB]

This reminds me of a Proteus unit with poorly soldered 5v sensor power chips. Engine was starting to cranke once I would touch accelerator pedal, the fun of electrical gremlins affecting button state unexpectedly.

[mtmotorsport]

startstopstate changes as expected. Lights up when I request a crank event, turns off when I let go of the button. The SD logs do not show this start stop state so I cannot confirm operation there. What I am seeing is the SD logs start at an Uptime counter of 5. The SD log files always start with the engine cranking over and starterState field at 1. I'm not sure if this is by design that the SD log starts sometime after the ECU boots, maybe some internal counter of 5 seconds.

Not sure if this is related but the comment of solder quality caught my attention. The car will cough/backfire on hard left turns. Like one or two good backfires through the intake. This feels like an electrical problem, losing sync, rebooting ECU, something along those lines not something like a calibration issue. It also has a stumble, misfire type operation between 1500-2200 rpm under light load. There is a harmonic in the engine at this speed that kind of vibrates things and I'm wondering if this misfire is bad solder joints.

[AndreyB]

I am working on more data points into SD card logs. Actually just added some under https://github.com/rusefi/rusefi/issues/3985

Hope to make more progress on "Start Button Function" in the next three days