Simon Game programming

This is the whole coding for the simon game. I am curious about how the code flow since each function do not return anything. And I am curious about this part:

void input()
{
  for (int x=0; x <= turn;)
  {
    input1 = digitalRead(SWITCHROOT);
    input2 = digitalRead(SWITCHROOT+1);
    input3 = digitalRead(SWITCHROOT+2);
    input4 = digitalRead(SWITCHROOT+3);

    counter++;
      
    if (counter > RESPONSETIME)
    {
      Serial.println("TIMEOUT!");
      fail(randomArray[x]);
      counter = 0;
      x++;
    }

Does that means that we need to respond faster as the counter increases ?

Thanks

Game (6.99 KB)

This is the whole coding for the simon game.

No, it isn't.

The whole code in the text file as it exceed the word limits.

Thanks

you can attach as zip file

Cant be view now ?

Vincent19:
This is the whole coding for the simon game. I am curious about how the code flow since each function do not return anything.

In certain terminologies, functions which don’t return anything are called “procedures”.
Your example code is well-written, IMO.

And I am curious about this part:

void input()

{
 for (int x=0; x <= turn;)
 {
   input1 = digitalRead(SWITCHROOT);
   input2 = digitalRead(SWITCHROOT+1);
   input3 = digitalRead(SWITCHROOT+2);
   input4 = digitalRead(SWITCHROOT+3);

counter++;
     
   if (counter > RESPONSETIME)
   {
     Serial.println(“TIMEOUT!”);
     fail(randomArray);
     counter = 0;
     x++;
   }



Does that means that we need to respond faster as the counter increases ?

No, it means if too much time has elapsed, you lose. Big clues are: “TIMEOUT!” and “fail” :slight_smile:

HTH,
John

But is it true that every turn I have 3s of timeout time ? But it seems to me not on hardware ><

Well, procedures so means once it done execute the output code, then it will automatically go to input code ? Flow according to the code ?

Thanks

Vincent19:
Does that means that we need to respond faster as the counter increases ?

///////////////////////////////////////////////////////////////////////////
// Slowly cranks up the pressure
void increaseSpeed()
{
  if (turn == band)
  {
    beepdelay = 170;
    pausedelay = 80;
    return;
  }
  if (turn == band * 2)
  {
    beepdelay = 150;
    pausedelay = 60;
    return;
  }

  if (turn == band*3)
  {
    beepdelay = 120;
    pausedelay = 40;
  }
}

///////////////////////////////////////////////////////////////////////////
void loop()
{
 for (int y = 0; y < WINSTATE; y++)
 {
   output();
   input();
   increaseSpeed();  // <---------------------------------- THIS is the part that makes it go faster as the game proceeds
 }                                                               It calls the procedure "increaseSpeed" defined above
 
 win();
 
}

in the “for” loop above, until the player either wins or loses, the output code is executed, then the input code is executed, then increasespeed, and then back to output, etc.

John

Ok, the speeed of the output goes faster. However, based on the full coding, does it means that the time I need to respond also getting faster ? Cause I seems to feel it when playing it ><

Ok, so either the player win or lose, it will follow the sequence : output > input > increase speed. And the final win(); is for what ?

Thanks

Vincent19:
Ok, the speeed of the output goes faster. However, based on the full coding, does it means that the time I need to respond also getting faster ? Cause I seems to feel it when playing it ><

I don’t think so, because RESPONSETIME is a defined constant and doesn’t get changed.

Ok, so either the player win or lose, it will follow the sequence : output > input > increase speed. And the final win(); is for what ?

Up above is the definition of the win() “procedure”. Looks like it beeps a certain way and flashes all the lights.

The loop() procedure at the bottom of the code is called over and over by the Arduino framework code. Therefore, win or lose, the player gets to keep going (but I think the score is reset once you lose). http://arduino.cc/en/Reference/Loop

The loop() procedure “high-level” code being at the bottom is typical of c and c++ coding style, with the definitions of the procedures/functions/subroutines above.

Note I am answering these questions from quick, cursory examination of the code because it is well organized, factored, and very good names for the variables. (But I could have missed something :slight_smile: )

Have you programmed in any other languages? If so, what?

No..just arduino languages. So , win() will only be call once the for loop finish executing in void loop() ?

Vincent19:
No…just arduino languages. So , win() will only be call once the for loop finish executing in void loop() ?

Yes, it will be called after y<WINSTATE becomes false. WINSTATE is defined as 32 so it appears that the for-loop will loop 32 times.

I am very curious and dont understand for the part if(counter> RESPONSETIME)

How is that ? the counter will increase in every loop, so in every loop it is getting closer to exceed RESPONSETIME isnt ?

Vincent19:
I am very curious and dont understand for the part if(counter> RESPONSETIME)

How is that ? the counter will increase in every loop, so in every loop it is getting closer to exceed RESPONSETIME isnt ?

Yes. It looks like the player has something slightly over 3 seconds (RESPONSETIME=3000) to push the buttons in proper sequence, or else he fail().

slightly over 3s ? not less than 3s ?

Vincent19:
slightly over 3s ? not less than 3s ?

Yes.

Mean the player has more than 3s before they fail ? LOL I thought less than 3s before they fail !

It could be under 3s depending on the accuracy of your particular Arduino crystal or resonator. Why don't you devise a way to measure it against an atomic clock reference standard and get back to us with the results.

I will record a video later on. :smiley:

johncc:
It could be under 3s depending on the accuracy of your particular Arduino crystal or resonator. Why don't you devise a way to measure it against an atomic clock reference standard and get back to us with the results.

This is the video. You can observe that the timeout is quite fast sometimes..LOL