Trying to make a simple code so on a simple push a relay is activated but if button held then the second relay is held for as long as the button is held keeping first relay activated until another press of the button.
#include <SM.h>
const int Switch = 3;
const int ARelay = 9;
const int BRelay = 8;
SM btnCtrl(Waiting);
void setup(){
Serial.begin(115200);
pinMode(ARelay, OUTPUT);
pinMode(BRelay, OUTPUT);
}//setup()
void loop(){
EXEC(btnCtrl);
}//loop()
State Waiting(){
if(digitalRead(Switch)) btnCtrl.Set(Pressed);
{digitalWrite(BRelay, 0); digitalWrite(ARelay,0);}
}//Waiting()
State Pressed(){
digitalWrite(ARelay, 1);
if(btnCtrl.Timeout(200)) btnCtrl.Set(Holding);
if(!digitalRead(Switch)) btnCtrl.Set(Waiting);
}//Pressed()
State Holding(){
{digitalWrite(ARelay, 1); digitalWrite(BRelay, 1);}
if(!digitalRead(Switch)) btnCtrl.Set(Pressed);
}//Holding()
Do i need to do a case for the first button push to see if relay is being held? Just beginning and sort of understand bits but more i try to read up the more i doubt what i know.
First thing I would need to know is what is the "SM" library? I guess it is State Machine library, but where from?
It's not very clear from your description. The way I do state machines is first list the events for each state, and what actions and state transitions to perform. If there is a situation where it needs to "remember" a previous event then add a new state.
It also helps a lot to draw a diagram.
But, I think you would benefit from a new state "relay on".
Button press -> relay 1 on
Button held -> both relays on
Button release -> relay 2 off
another Button press -> relay 1 off
Does holding down the press that turns off relay 1 turn on relay 2 until the button is released?
FWIW I do not know this state machine library but this is a case where I would switch to just learning how to make a state machine using simple C code.
See
and/or google
arduino state machine
Reading a variety of approaches will be beneficial. And time better spent than aligning your thinking with what one person thought best and wrote a library to do
Since eveyone else is still trying to figure out what the OP actually wants, you might spend a few of your limited life time supply of words to say what your code does, or which if any of the suggested scenarios it might be coded to.
Or is this just another thing to consider and mine for how to do things in the way you like?
Right so not explained anything well here i want a momentary press of the button to turn relay a on (and stay on) and a hold to turn on relay b also a on while held ( b off on release only on for hold) and for a to stay on until another momentary press of the button.
Almost never. Isn't part of learning how to accomplish anything with computers figuring out how to tell other ppl what the desired functionality might be?
Something like this allowing for multiple interpretations only gets worse as the number of ambiguously described features increases.
Life is too short to take the approach of throwing stuff at the wall to see what sticks.
Look at it from the other direction and list all the different behaviors (states) first, then consider how you change between them (button events, timing?)
States:
Aoff Boff
Aon Boff
Aon Bon
Aoff Bon?
Transitions?
(I find it easiest to draw a diagram instead of spelling it out)
From what you’ve written I have a question: If you do several long presses, does A turn on and stay on continuously, while B turns on and off as the button is long-pressed?