 | | | | | | |
| |
|
I recently read a post from someone wanting to
generate friendy sounds similar to R2D2 using an RCX.
I thought this was a good challenge so set out to try.
I was getting to the point where I could generate a
number of similar friendly sounds and then the RCX
stopped generating sounds completely (except for beeps
from the On-Off button when pressed). This happened
within an hour!
I can only assume that the repeated intensive use of
the oscillator circuit has burnt out some component.
All other functions of the RCX seem to be intact.
Does anyone know the location of a circuit diagram for
the RCX?
The algorithm I was using (in Robolab) to generate the
sounds was as follows:
Select a start frequency.
From this calculate half and quarter of same
(harmonics 1 and 4 I think).
Select a frequency step size.
Select a note duration.
Select number of loops.
The sound is then generated by interleaving the
playing of the 3 harmonics for the selected duration,
stepping up or down as the program loops.
I was intending to create a subroutine which would be
passed parameters (frequency, duration, step and
loops) to create different sounds which could then be
strung together.
I suspect that the intensity of the switching has been
the cause of my RCX getting laryngitis.
For anyone who is game I have attached an image of one
of the programs I tried. Don't over do it if you try
it.
Cheers
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com
--
MIME ATTACHMENTS DISCARDED:
1. Content-Type: image/bmp; name="Sounds.bmp"
Content-Transfer-Encoding: base64
Content-Description: 857255036-Sounds.bmp
Content-Disposition: inline; filename="Sounds.bmp"
Content-Length: 1137668
| | | | | | | | | | | | | | | | |
| |
|
In lugnet.robotics, John Reynolds <john-reynolds@rocketmail.com> wrote:
> I recently read a post from someone wanting to
> generate friendy sounds similar to R2D2 using an RCX.
> I thought this was a good challenge so set out to try.
> I was getting to the point where I could generate a
> number of similar friendly sounds and then the RCX
> stopped generating sounds completely (except for beeps
> from the On-Off button when pressed). This happened
> within an hour!
>
> I can only assume that the repeated intensive use of
> the oscillator circuit has burnt out some component.
> All other functions of the RCX seem to be intact.
>
> Does anyone know the location of a circuit diagram for
> the RCX?
>
> The algorithm I was using (in Robolab) to generate the
> sounds was as follows:
>
> Select a start frequency.
> From this calculate half and quarter of same
> (harmonics 1 and 4 I think).
> Select a frequency step size.
> Select a note duration.
> Select number of loops.
>
> The sound is then generated by interleaving the
> playing of the 3 harmonics for the selected duration,
> stepping up or down as the program loops.
>
> I was intending to create a subroutine which would be
> passed parameters (frequency, duration, step and
> loops) to create different sounds which could then be
> strung together.
>
> I suspect that the intensity of the switching has been
> the cause of my RCX getting laryngitis.
>
> For anyone who is game I have attached an image of one
> of the programs I tried. Don't over do it if you try
> it.
>
> Cheers
>
>
Picture was missing. Though, as I understand the sound-generation, I doubt that
actually you are able to produce an RCX hardware-laryngitis through a program
that is based on the standard RCX firmware, because you just don't touch the
hardware directly. If you change frequencies and durations, the firmware will
adjust a timer-match register or simply turn the timer on and off. Internally to
the H8, the concerned 8-bit timer (TMO0) is configured to toggle a pin output
that drives the speaker (port 6 pin 4). Pin LOW inverts the speaker voltage to
-5V; whereas pin HIGH sets the speaker voltage to +5V.
The beep at On/Off proves that the system sound still works. (Tone and system
sound use the same basic sound driver, only queuing changes.) My first guess is,
that through your program you changed a configuration register that the firmware
doesn't reset at start. Having not seen your ROBOLAB code, that's only a guess.
But, before opening your RCX, try the following therapy:
1. Reboot the RCX after having taken off the batteries. Reload the firmware and
your program...
2. Take off the batteries while the RCX is ON. This will completely discharge
the capacitors and the processor will completely be reset....
I'm really curious about this. Please post the code somewhere visible.
... Laryngitis is cool !
- Claude
| | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.robotics, John Reynolds <john-reynolds@rocketmail.com> wrote:
> I was getting to the point where I could generate a
> number of similar friendly sounds and then the RCX
> stopped generating sounds completely (except for beeps
> from the On-Off button when pressed). This happened
> within an hour!
>
> I can only assume that the repeated intensive use of
> the oscillator circuit has burnt out some component.
> All other functions of the RCX seem to be intact.
>
> Does anyone know the location of a circuit diagram for
> the RCX?
Here is the sound driver section:
http://www.brickshelf.com/gallery/Philo/RCX-comp/sound_driver.gif
(Mark Bellis, if you read this you can add this schematics to your RCX circuit
collection to get everything together)
It seems impossible that you have fried anything if you still get on/off sound:
there is only one buzzer driven by a simple circuit, so the hardware can't be
wrong here (and I don't think it could ever get "tired" with the 330 ohm series
resistance...)
So I suggest you follow Claude's suggestions who posted while I wrote this ;o)
Philo
| | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.robotics, Philippe Hurbain wrote:
> In lugnet.robotics, John Reynolds <john-reynolds@rocketmail.com> wrote:
> > I was getting to the point where I could generate a
> > number of similar friendly sounds and then the RCX
> > stopped generating sounds completely (except for beeps
> > from the On-Off button when pressed). This happened
> > within an hour!
> >
> > I can only assume that the repeated intensive use of
> > the oscillator circuit has burnt out some component.
> > All other functions of the RCX seem to be intact.
> >
> > Does anyone know the location of a circuit diagram for
> > the RCX?
>
> Here is the sound driver section:
> http://www.brickshelf.com/gallery/Philo/RCX-comp/sound_driver.gif
> (Mark Bellis, if you read this you can add this schematics to your RCX circuit
> collection to get everything together)
>
> It seems impossible that you have fried anything if you still get on/off sound:
> there is only one buzzer driven by a simple circuit, so the hardware can't be
> wrong here (and I don't think it could ever get "tired" with the 330 ohm series
> resistance...)
>
> So I suggest you follow Claude's suggestions who posted while I wrote this ;o)
>
> Philo
Your circuit diagram checks out Philo, though a 47k resistor to ground should be
added to the processor connection. As soon as I get access to Visio again, I'll
write it up and post it with a credit.
I was wondering what the other NAND gate is used for. Input pin 1 traces to
somewhere under the ROM. Input pins 2 and 13 and output pin 12 disappear
elsewhere.
I suggest that a 3-input NAND gate was needed by the main computer circuit and
that the speaker driver circuit just mopped up the spare gates. The speaker
circuit is effectively an H-bridge design, using the CMOS output stages of the
two gates, which allows 10 volts differential across the speaker and series
resistor.
Mark
| | | | | | | | | | | | | | | | | | | | | | | |
| |
|
Hello Mark,
> Your circuit diagram checks out Philo, though a 47k resistor to ground should be
> added to the processor connection.
Quite possible as I obtained the schematics only with an ohmeter...
>
> I was wondering what the other NAND gate is used for. Input pin 1 traces to
> somewhere under the ROM. Input pins 2 and 13 and output pin 12 disappear
> elsewhere.
I spent some time again with my ohmeter, here is the schematics for this part:
http://www.brickshelf.com/gallery/Philo/RCX-comp/motor_cmd.gif
This is the motor driver control circuitry, data is latched when there is a
write to address x111 xxxx xxxx xxxx (binary). As I think H8 is used in mode 2,
A15 is always 1 for external access, so any write to fxxx should write to motor
driver latches. In the schematics, OUT_X_1 and OUT_X_2 are connected to Melexis
motor drivers in1 and in2.
> I suggest that a 3-input NAND gate was needed by the main computer circuit and
> that the speaker driver circuit just mopped up the spare gates.
Probably, yes ;o)
Philo
| | | | | | | | | | | | | | | | | | | | | | | |
| |
|
Hi,
I haven't really got the first clue what you are talking about here, but I would
like to - any suggestions for reading up on this stuff?
Thomas
In lugnet.robotics, Philippe Hurbain wrote:
> Hello Mark,
>
> > Your circuit diagram checks out Philo, though a 47k resistor to ground should be
> > added to the processor connection.
>
> Quite possible as I obtained the schematics only with an ohmeter...
>
> >
> > I was wondering what the other NAND gate is used for. Input pin 1 traces to
> > somewhere under the ROM. Input pins 2 and 13 and output pin 12 disappear
> > elsewhere.
>
> I spent some time again with my ohmeter, here is the schematics for this part:
> http://www.brickshelf.com/gallery/Philo/RCX-comp/motor_cmd.gif
>
> This is the motor driver control circuitry, data is latched when there is a
> write to address x111 xxxx xxxx xxxx (binary). As I think H8 is used in mode 2,
> A15 is always 1 for external access, so any write to fxxx should write to motor
> driver latches. In the schematics, OUT_X_1 and OUT_X_2 are connected to Melexis
> motor drivers in1 and in2.
>
> > I suggest that a 3-input NAND gate was needed by the main computer circuit and
> > that the speaker driver circuit just mopped up the spare gates.
> Probably, yes ;o)
>
> Philo
| | | | | | | | | | | | | | | | | | |
| |
|
The note duration must be a compile time constant. By any chance were you
trying to use a run-time variable (Robolab container) for this? This could
explain your problem.
-----Original Message-----
From: news-gateway@lugnet.com [mailto:news-gateway@lugnet.com]On Behalf
Of John Reynolds
Sent: Tuesday, June 21, 2005 5:18 PM
To: lugnet.robotics@lugnet.com
Subject: R2D2 Sounds - A Warning my RCX has laryngitis.
I recently read a post from someone wanting to
generate friendy sounds similar to R2D2 using an RCX.
I thought this was a good challenge so set out to try.
I was getting to the point where I could generate a
number of similar friendly sounds and then the RCX
stopped generating sounds completely (except for beeps
from the On-Off button when pressed). This happened
within an hour!
I can only assume that the repeated intensive use of
the oscillator circuit has burnt out some component.
All other functions of the RCX seem to be intact.
Does anyone know the location of a circuit diagram for
the RCX?
The algorithm I was using (in Robolab) to generate the
sounds was as follows:
Select a start frequency.
From this calculate half and quarter of same
(harmonics 1 and 4 I think).
Select a frequency step size.
Select a note duration.
Select number of loops.
The sound is then generated by interleaving the
playing of the 3 harmonics for the selected duration,
stepping up or down as the program loops.
I was intending to create a subroutine which would be
passed parameters (frequency, duration, step and
loops) to create different sounds which could then be
strung together.
I suspect that the intensity of the switching has been
the cause of my RCX getting laryngitis.
For anyone who is game I have attached an image of one
of the programs I tried. Don't over do it if you try
it.
Cheers
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com
--
MIME ATTACHMENTS DISCARDED:
1. Content-Type: image/bmp; name="Sounds.bmp"
Content-Transfer-Encoding: base64
Content-Description: 857255036-Sounds.bmp
Content-Disposition: inline; filename="Sounds.bmp"
Content-Length: 1137668
| | | | | | | | | | | | | | | | |
In lugnet.robotics, Dick Swan wrote:
> The note duration must be a compile time constant. By any chance were you
> trying to use a run-time variable (Robolab container) for this? This could
> explain your problem.
Hi Dick.
No the frequency and loop number are managed by containers, but the note
duration was set by using a control (or directly specified) in the version that
caused the problem.
| | | | | | |
