Code:

    if(incomming = true){
      if(index < 19) // One less than the size of the array
      {
        inChar = Serial1.read(); // Read a character

This code reads from Serial1 without checking Serial1.available() to see if any characters have arrived yet.  When you do that, Serial1.read() returns -1, which is why you see those y-umlaut characters.

Also, if it wouldn't be too much trouble, would you mind spelling "incoming" with the usual number of 'm's?

-br

The TV-B-Gone is a good high-power infrared transmitter reference design with multiple emitters.  Adafruit sells a kit and you can see the driver circuits in the documentation there.  Basically if you drive the IR emitter through a transistor you can max the transmitted power.

Lenses, tubes, and alignment will be critical to make best distance.  One hundred feet is ambitious in daylight. 

-br

A lot depends on the receiver.  What do you intend to receive these pulses with?

-br

This may not be your bug, but I wonder if matters that if the first condition is true there is no "D" response sent to the PC.

Code:

    if((getDist() > 0) && (getDist() < 10))
    {
      stopRobot();
    }
    else
    {…
        Serial.print('D');
    }

-br

Does the Arduino function correctly for a longer time if you send characters to it manually from Serial Monitor or a terminal program instead of the C++ code?

-br

Love a little Saturday night code golf.  Here's an old-school approach:

Code:

int parseNum(char *buf, int pos) {
char *parseptr = buf + pos;
while (*parseptr && !isdigit(*parseptr)) ++parseptr;

int result = 0;
while (isdigit(*parseptr)) result = (result * 10) + *parseptr++ - '0';
return result;
}

-br

Trimpots, maybe?

-br

Next background interrupt thing I would eliminate is the Serial.print background output buffer handling.  Perhaps a delay(1000); at the start and end of loop to give the serial port time to quiesce before another cycle of readings starts.

-br

I agree that free ram is a concern.  Search the forums for "free memory function" for the magic code that will report how much is free at startup.  Keep it above 200 or thy stack will invade thy heap.

I would also be wondering whether background interrupts like the millis() increment might be affecting the time interval between some samples.  An interrupt will displace all subsequent readings by a certain phase.  Perhaps it could create artifacts like we see in the chart of values.

You could test this second hypothesis by turning off interupts around the sampling loop, like this:

Code:

 cli();
  for (int i = 0; i < numReadings; i++) {
    inputReading [i]= analogRead(0);
  }
  sei();

Note that nothing is free; if you keep interrupts off long enough you will lose millis().  Doesn't seem critical in the program we see so far.

-br

Glad it worked for you.

Good luck with your project.

-br

It would be helpful to have some specific examples of commands that are failing.

See if it helps to use -d 2000 before you send anything to the arduino.  For the first two seconds after a reboot (which happens when you open the serial port) the arduino isn't listening because it's in the bootloader.

-br

From the .pdf:

// Connect your Arduino Uno to your Computer
Use the USB cable provided in the SIK kit to connect the Arduino to one of your computer’s USB inputs.

But you said:

Arduino Ethernet out to USB in

Which I will confess is confusing me.  Could you confirm you have a proper USB cable plugged into the Arduino and a USB port on your PC?  Do any lights turn on when you plug it in?

-br

Here's what works for me:

Code:

$ git clone git://github.com/arduino/Arduino.git
$ cd Arduino/build
$ ant clean; ant build; ant run

-br

May I suggest you try printing out val in serialEvent() to confirm whether it's ever being called?

-br

Well… you can use a while, but it will act a little strange (the state will increment extremely fast, so the effect will be to choose a random state.)

Couple issues with the code as presented, though:

1. As written that code won't compile because HIGH has to be uppercase.

2. If you don't digitalRead the button pin inside the loop, how is the value of buttonState ever going to change?


-br