serial monitor locks after exceeding threshold

I would add a serial.println within the while loops, like this:

(digitalRead(rightSwitchPin) == LOW) //keep going until limit switch reached

    {

      Serial.println("rightSwitchPin is low");

      stepper1.step(-1);  //move right

    }

    while (digitalRead(leftSwitchPin) == LOW) //keep going until limit switch reached

    {

      Serial.println("leftSwitchPin is low");

      stepper1.step(1);  //move left    

    }

I'm guessing that it's getting stuck in one of those loops.

Cheers,

-Nico

Yes! I added the "println" under the while, but it works just the same.

Thanks so much.

Keith

Yes! I added the "println" under the while, but it works just the same.

Thanks so much.

Keith

I just looked at the details of Stepper.step, and it looks like this block is not needed (taking 0 steps should do nothing)...

  else

  {

    stepper1.step (STOP);

  }

Maybe remove that block, in case that's causing the issue?

ps, from the code it looks like when sonarValue goes over 900, the stepper motor will go all the way right until the limit switch is hit, and then it will go all the way left until the limit switch is hit, and then it reads the sensor again, waits half a second, and repeats the process. Was that the intention?

Thank you.  After adding a println in each while statement, the sketch

works fine. Had some help here.

Keith

Keith

As Nico says ...

Not sure where your sketch is, but you read the sonarValue at the start of the loop, then don't read it again until you hit the limit switch.

The serial.println(sonarvalue) will always be the same until the switch limit is reached.

You can combine items in the If statement so that it becomes :-

void loop()

{

  sonarValue = analogRead (sonarPin);

  Serial.println (sonarValue);

  if (sonarValue >900 && digitalRead(rightSwitchPin) == LOW)   // below 900 and keep going until right limit

    {

        stepper1.step(-1);  //move right

        Serial.println (sonarValue);

    }

    if (sonarValue >900 && digitalRead(leftSwitchPin) == LOW)   //below 900 keep going until left limit

    {

        stepper1.step(1);  //move left

        Serial.println (sonarValue);

    {

}

This sketch (and the others) still has a problem .....

This will read the sonarPin and if less than 900 AND the limit switch isn't reached, will step -1.

Since the sonarValue is still less than 900 and the other limitswitch isn't reached, will step 1.

Basically it will go up one and back one.

Is this what you want or would you prefer it to go from one limit switch to the other while the sonarValue is below 900.?

obviously if the sonar value is greater than 900 its going to print flat out, so a delay/timer or something else is a good idea...

Mark

I think you nailed it, Mark Beckett.  The problem has nothing to do with the sensor at all.  It has to do with the fact that there is no secondary variable that REMEMBERS that the rightSwitchPin was HIGH just last go round.  The same thing goes for the leftSwitchPin.

Yes, thanks for the advise. I was playing with the switches and noticed

some positive behavior but didn't understand how to push it.

Ah ha! That is a more elegant solution.  To explain what all this is

about: I am designing a sculpture involving many actions that must occur

simultaneously when the viewer approaches. For the experienced, I assume

this can be accomplished with code but I surrendered that goal after

several months of failure, not to speak of the money wasted on a Mega and

many, many components, so I chose a more primitive solution.

  I'm using a bunch of cheap pro mini boards, all activated by a single

Maxsonar sensor that lights an LED on one end of a short length of PVC

pipe. On the other are mounted photocells to all the other boards.

Theoretically, one LED could fire a million Arduino, all electronically

independent. I'm using an 8amp power source.

  In hindsight, would a series of optocouplers have been a better choice?

Keith

Just to be sure I have this right.

You have a sensor to detect someone is present/approaching/etc.

This then is required to trigger some other Arduino's into doing something.

I'm presuming these 'others' are close (enough to use a short piece of pvc pipe).

You are using a single power supply, so you have wires running to them, and they are all connected to the same 8 amp power supply.

If the above is correct, then electrical isolation isn't really necesary.

Optocouplers will give the ability for isolation (maybe in the future), and I always prefer to use a pullup resistor, and drag the input down to ground. (You can't short out the power supply that way)

FYI

Multiple things can be done at once, its how you do them.

I use an analogy of filling a pool.

If you stand there holding the hose (aka delay(xxxx)) then you can't do anything else.

If however you come back every minute/5mins/1hr and check the level (aka BlinkWithoutDelay example), then you can do other things....

So now we have resolved the stepper issue, what is the next step.?

Mark

Also feel free to tag the 'Helpful Answers' as it helps readers to see the answer more easily.

Keith

I have always found a flow chart or a mapping of what you want to achieve is useful.

While I don't use a full flow chart, having the basic decision blocks is useful.

In this case one would be the sonarValue and two paths below and above the 900 value.

In the >900 path is a block for 'Is the RightLimitSwitch = LOW' and two possible paths.

(you might decide to set the direction to Right or Left then go back to the main path)

In this manner you may be able to identify any common things which can them become a seperate routine.

It also helps to remove the clutter of the code.

Mark

These are all very helpful solutions but I don't understand how to tag it. The photocells are clustered an inch or so, opposite the LED.  I will experiement with the "no delay" example you mention with a simple, straight forward project. The complexity of this monster was overwelming. Even though I was offered generous help, I couldn't write a sketch using the timer method. Next challenge is "bending" audio circuits from salvaged toddler toys that respond to the same sensor input as the servos, dc motors, and steppers.  LED's are the final challenge and then, the more familiar task; a skin of applique and assorted imbedded objects, nearly a year in the making.  This is my first attempt to learn Arduino as a medium of expression.