rusefi.com

This Ford I intend to fit with rusEFI has cruise handled by the OEM computer. Input comes from one wire, with 5 different states. On is signalled by pulling up to 12v; off is pulling down to GND; set, coast and accel are signalled by various resistance values with reference to GND.

Output is in the form of 2 PWM signals controlling solenoid valves, vent and hold. They are modulated to hold the throttle at some desired value to maintain road speed. The ECU asserts control by a momentary increase of the throttle.

Question is, what I/O configuration would support this and is the code present to do so? Outputs are low side active.

This project is NOT for emissions regulated or safety regulated applications. This project is for race cars, snow blowers, fixed engine applications, and science experiments.

In light of the above there will absolutely be no cruise control logic in rusEFI.

I'd love to have cruise control on my snowblower!
SHOf429, if you add such a feature, please, let me know

AndreyB wrote: ↑

Wed Jun 03, 2020 1:59 am

This project is NOT for emissions regulated or safety regulated applications. This project is for race cars, snow blowers, fixed engine applications, and science experiments.

In light of the above there will absolutely be no cruise control logic in rusEFI.

This doesn't mean that you would refuse a pull request, does it?
For what it's worth, not all places have emissions regulations.

I would be extra stringent with a cruise control PR for sure. Probably not an automatic close at this point.

At the very least, cruise control is a far lower priority than many "normal ECU" features.

AndreyB wrote: ↑

Wed Jun 03, 2020 1:59 am

This project is NOT for emissions regulated or safety regulated applications. This project is for race cars, snow blowers, fixed engine applications, and science experiments.

In light of the above there will absolutely be no cruise control logic in rusEFI.

For the safety aspect of my uh...snowblower, I would use brake pedal and clutch switch as 'disengage' inputs. Set minimum activation to something like 20 mph.

Purely academic purposes, of course.

I will resume this thread once I see I pull request. Until there is a pull request let's halt this academic discussion to reduce distraction.