pcmhacking.net

BennVenn wrote: ↑Sat Nov 23, 2024 11:48 am you would add something like this to the CONDITIONS{} area in the config file

IO1=VAR09>0BB8=00;
IO1=VAR09<0AF0=FF;

This is assuming RPM is assigned to VAR09 (in the math section)

IO1 output is set to 00 (0% duty cycle, or effectively off) when VAR09 (the RPM) is > (greater than) hex value 0BB8 (in decimal = 3000RPM)
it'll then check the next condition
IO1 output is set to FF (100% duty cycle, or ON) when VAR09 (the RPM) is < (less than) hex value 0AF0 (in decimal = 2800RPM)

so assuming you had IO1 going to a relay which is powering the ignition coil, if you go over 3000RPM it'll shut the relay off until RPM falls below 2800RPM.

You can also add more conditions after it, example

IO1=VAR02>00C8=00;

here, IO1 is turned off (0% duty) when VAR02 > 200KPA. Like a boost safety.

Every packet that is received from the ECU, all the conditions are checked once again, so it is the last valid condition that actually controls the IO.

This would always give you 2step which is probably not ideal. You could disable it with a rocker switch or push button, or I can update the code so you can assign a VAR with IO2's logic state. So you could check for a pushbutton press in the conditions, from IO2, and have that enable or disable the 2 step.

Sorry if this reads as a little complicated! Might be best to connect a test lamp / led to the IO1 output and try some code to see how it works, and if you need the IO2 as an input into a VARxx, I'll code that up