I need clarification on assigning values to Variables.

I'm thinking I must have a fundemental misunderstanding of variables, how to assign them and how to use serial.print to check them. My reading of the terms glossary and google searches for assigning variables is not clarifying this.

Here is a simple program in which I assign a constant value of 15000 to the variable named "restPeriod".
Then, I assign the variable "seqTimer" to = "restPeriod"

In my thinking, Serial.print (seqTimer) should get me a value of 15000 but it returns "0".
"restPeriod" on the other hand, DOES serial.print "15000"

Does "int seqTimer = restPeriod;" not assign restPeriod's value to seqTimer?
What am I missing?

      unsigned long seqTimer; //time between fan blasts
      const word slow = 0;
      const word fast = 1;
      int timer;

      const unsigned long fastRun = 5000;  //High speed run time in milliseconds
      const unsigned long restPeriod = (10000 + fastRun);  //Rest time in milliseconds

void setup() {

      int fan = slow;      // starts fan at low speed
      int fanStart = 0;  //start high speed fan timer at 0

      int seqTimer = restPeriod; 


void loop() {
    timeNow = millis(); //remember current time

      Serial.println("s time now ");

      Serial.println("sequence Timer ");

      Serial.println("rest period ");

      Serial.println("sequence Timer ");

You have a scope problem. The seqTimer variable that you declare in setup goes out of scope when setup() is finished. So the code in loop only sees the global seqTimer and it is 0 because no value was ever assigned to it. If you leave off the int before the assignment in setup() the value of restPeriod will be assigned to the global seqTimer and it will be valid in loop().

Declare a variable and assign a value to it:

int seqTimer = restPeriod;

Only assign a value to an existing variable:

seqTimer = restPeriiod;

Thanks so much!

I wonder if I am the only one who suffers from skills erosion?
I spent 4 months last year (about this time) teaching myself coding.
Then I got a 3D printer and stopped coding while I spent the next 4 months figuring out how to get the printer to work, how to use the design and slicing software to design things to print and then figured out why my printer had stopped working and get things going again.
Then I started working on hardware for Arduino projects again for the first time in a year … and had to relearn THAT.
Now I remember just enough coding to get myself tied in a knot.

I am proof that there is a reason coding is a profession…
and electronics is it’s own profession …
and 3D printing is a profession.