Hi,Now I am working on Logical project, Let me explain what I want to do,I have 4 inputs INPUT 1, INPUT 2, INPUT 3, INPUT 4 (I Don't know where to give input/Which pin of arduino can use as input)Now I want output at PIN ** (I don't know where to receive Output/which pin of arduino can use as output)I need output at output pin after some time like I want to add "Wait (1000)" like at every pin,Eg: if I am give input at pin **, receive output at pin** after some particular time.Now I want to create logic, like if PIN** & PIN** high than PIN** should HIGHPlease guide me how to create this logic.

INPUT 1, INPUT 2, INPUT 3, INPUT 4 (I Don't know where to give input/Which pin of arduino can use as input)Now I want output at PIN ** (I don't know where to receive Output/which pin of arduino can use as output)

You can use any of the I/O pins as input or output, but stay away from pins 0 and 1 as they are used for serial comms.

Quote

I need output at output pin after some time like I want to add "Wait (1000)" like at every pin,

"wait is called delay and you should never use it! - See the blink without delay example and FSM's (Finite State Machines) in the playground.

Quote

Now I want to create logic, like if PIN** & PIN** high than PIN** should HIGH

Specifically look at the digitalRead() and digitalWrite() functions. If you're familiar with other microcontrollers this should get you on the way. As Mark mentioned above delay() might not be ideal for your project as it is a blocking function - your code will mostly not respond to external inputs while it is running. I wouldn't go so far as to say never use it, but it's rare that it's the best choice for anything more than the most simple cases.

If you are completely unfamiliar with Arduino there are some excellent tutorials available not just here, but also on youtube. This series by Jeremy Blum is a good place to start imo.

All the best,Geoff

"There is no problem so bad you can't make it worse" - retired astronaut Chris Hadfield

The sort of behaviour you're describing is certainly feasible and not difficult to code once you have got the hang of it. However, although your description is reasonably detailed it still has some ambiguity. For example, in the situation where P1 is on and L2 is also on, it's not clear which should take precedence with respect to the behaviour described above. Similarly for the other parts of the code where different input states affect the same outputs.

I only provide help via the forum - please do not contact me for private consultancy.

const int P1 = 2; // the number of the pushbutton pinconst int P2 = 3; // the number of the pushbutton pinconst int L1 = 4; // the number of the pushbutton pinconst int L2 = 5; // the number of the pushbutton pin

int S1 = 8; // the number of the LED pin int S2 = 9; // the number of the LED pin int S3 = 10; // the number of the LED pin int S4 = 11; // the number of the LED pin