Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

I have been trying to use PlaySound in a robot control program and I found the following (after several hours of frustration!). 1) The PlaySound function resets the entire Port (all 8 bits reset to 0) and also resets the DDR for the pin used for the PlaySound. 2) The playsound function does not seem to be affected by the resetting of the DDR. 3) If you are using any other pin of the port (port C in my case) it will be set to 0 and will not be reset until the next time you call the pin-driving function. This turned off LEDs and fouled up serial communication in my case. Has anyone else run into this and/or know of a workaround? Thanks, Stan

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Stan I just verified the bug on my test system. I had not yet put the speech function onto any of the rolling robots, I had only tested it on the bench system by itself. I'm glad you caught this now. I'm sure NetMedia will provide a work around or a patch once they can duplicate the problem. Thank you Ron A. Nucci -----Original Message----- From: Stan Cossette <> To: <> Date: Monday, October 16, 2000 6:47 AM Subject: [BasicX] PlaySound Bug? >I have been trying to use PlaySound in a robot control program and I >found the following (after several hours of frustration!). > >1) The PlaySound function resets the entire Port (all 8 bits reset to >0) and also resets the DDR for the pin used for the PlaySound. > >2) The playsound function does not seem to be affected by the >resetting of the DDR. > >3) If you are using any other pin of the port (port C in my case) it >will be set to 0 and will not be reset until the next time you call >the pin-driving function. This turned off LEDs and fouled up serial >communication in my case. > >Has anyone else run into this and/or know of a workaround? > >Thanks, > >Stan

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )