i suppose this will work with simple serial transmission:

Code: (sender)

void setup()
{
  Serial.begin(1200);
}

void loop()
{
  Serial.print('A');
}

Code: (receiver)

void setup()
{
  Serial.begin(1200);
}

void loop()
{
  while(Serial.available()<1);
  Serial.println(Serial.read());
}

i think this should work with the serial monitor of the IDE, if not, then you should use softwareserial (because it can be that the two serial data transmission get mixed, but i don't think they will)

i start with 1200 because a lot of devices use 1200 too, i don't think you should go lower, unless you really don't see a thing of course

the output in the serial monitor should be 65 (ascii representation of A)

i think you misunderstood my comment
what i meant with replacing with for loop is that this:

Code:

void uspeech::sample(){
  arr[0] = analogRead(pin)-calib;
  arr[1] = analogRead(pin)-calib;
  arr[2] = analogRead(pin)-calib;
  arr[3] = analogRead(pin)-calib;
  arr[4] = analogRead(pin)-calib;
  arr[5] = analogRead(pin)-calib;
  arr[6] = analogRead(pin)-calib;
  arr[7] = analogRead(pin)-calib;
  arr[8] = analogRead(pin)-calib;
  arr[9] = analogRead(pin)-calib;
  arr[10] = analogRead(pin)-calib;
  arr[11] = analogRead(pin)-calib;
  arr[12] = analogRead(pin)-calib;
  arr[13] = analogRead(pin)-calib;
  arr[14] = analogRead(pin)-calib;
  arr[15] = analogRead(pin)-calib;
  arr[16] = analogRead(pin)-calib;
  arr[17] = analogRead(pin)-calib;
  arr[18] = analogRead(pin)-calib;
  arr[19] = analogRead(pin)-calib;
  arr[20] = analogRead(pin)-calib;
  arr[21] = analogRead(pin)-calib;
  arr[22] = analogRead(pin)-calib;
  arr[23] = analogRead(pin)-calib;
  arr[24] = analogRead(pin)-calib;
  arr[25] = analogRead(pin)-calib;
  arr[26] = analogRead(pin)-calib;
  arr[27] = analogRead(pin)-calib;
  arr[28] = analogRead(pin)-calib;
  arr[29] = analogRead(pin)-calib;
  arr[30] = analogRead(pin)-calib;
  arr[31] = analogRead(pin)-calib;
  arr[32] = analogRead(pin)-calib;
}

can be easily replaced with this:

Code:

void uspeech::sample()
{
  for(uint8_t i=0; i<33; i++)
  {
    arr[i] = analogRead(pin)-calib;
  }
}

that'll save a lot of bytes, and does not use anything more ram. well, it uses one byte more to store 'i', but that gets free'd afterwards, so it results in the same

nice job

i took a look at the files, and it seems you did not think about using for loops, did you xp

wince a lot of bytes can be saved by doing for-loops instead of 20 times the same.
(just a comment)

but it is fantastich you did this, i love to see things like these comming up, and i can believe you are happy to get it working

how did you reach the calculation of 5 shift registers?

the uno will do, but sound is not the strongest point of the arduino's (of none of them). it depends on what you mean by sound, you won't be able to play e.g. mp3's on it

that lcd will do perfectly, and it even has rgb leds :o that'll be a beauty xp

what do you mean by animations? from the led cube?
oh, and that led cube, you said 6x6, but do you mean 6x6x6 or just 6x6 ? because it's a huge difference in pins

some more info might come in handy

code ? how do you sense with the ir leds? where are they placed etc

Hi, and welcome

for the cube, you should multiplex your leds and use shift registers and transistors. that way you don't need to get all the pins from the arduino.
a good instructable about shift registers can be found here

for the alarm clock, you'll need an RTC (real time clock)

'lcd screen' is extremely vague. do you want a 16x2 lcd screen, or a 20x2, or a 16x4, or a full color lcd, or a nokia rip-of-lcd or.. the possibilities are endless.

an  on/off button can be a switch between the power source and the arduino, that is the most simple way to turn it off.

the other products are standard and info can be found on a million pages in the internet

Well, i'm currently deveoping a GUI for the MI0283QT2 from watterott.com

this GUI uses buttons, switches, tabs, radiobuttons, checkboxes, textboxes, sliders and a statusbar to make GUI-handling suuuper easy

it won't be long until i release a first version of it(when i get the tab delete and radiobutton delete functions working).

If you would select another displyay it probably won't be hard to edit the lib to your needs, and to make it fit with the lib of your screen.

i can clearly see why your arduino 'stops', or better, seems to stop.

it on this line:

Code:

if (IRcompare(numberpulses, Play,sizeof(Play)/4)) {
    On = 1;
    if (On == 1) {
      do{
        for (int thisPin = 4; thisPin < 8; thisPin++) {
          // turn the pin on:
          digitalWrite(thisPin, HIGH); 
          delay(DelayP);                 
          // turn the pin off:
          digitalWrite(thisPin, LOW);   
        }
      }
      while(On ==1);         //<<<<<<<<<<<<<<HERE is the mistake

    }
  }

as you tell it to do nothing while on==1. on will never change in that loop, so once it gets an IR code on is 1 and it will be stuck in the while loop. just remove this one and it will be fine

i don't thinks this runs fine on an arduino UNO though, it will react exactly the same way on the while, so i can see no differences

something like this ? http://energydefender.blogspot.be/2010/02/arduino-controlled-electric-blinds.html

You should skip the relay and jump straight to a mosfet.

http://bildr.org/2012/03/rfp30n06le-arduino/

thanks for that link, i could definitely use it, since i was trying to obtain something like that with transistors, but this seems a lot more simple :o

@OP: i'm making a complete GUI for touch screens using an arduino as control, and one of the widgets is a switch.
i'm currently adding some more things to the lib, but if you want i can send it to you so you can use it for you touch screen.
it'll make it extremely easy to switch your relays/mosfets
it looks like this: and

start with changing all the 'double' into 'unsigned long'

it is perfectly normal that the arduino resets when you open the serial monitor, if that's what you mean.
it also happens when you change the configurations from the dropsownlists in the monitor

i took a look at that pongsat thing, and i'm interested
just some off-topic questions:
is it possible for european students too?
where do they get sent of to space?

and now on topic:
how will you get the power? because a pingpong ball is very small, and batteries can be big
if you use a pressure sensor you can measure the pressure and calculate the altitude, that way you have two things at once
i think you'll have to push to get all this inside, i don't think many more sensors will be possible

maybe you could give us a little more info on the capabilities right now?

is it some kind of firmata interface? or you own?

could you give us some more info please? with this question we'll not be able to help you

 - code?
 - pins?
 - connections?