On Tue, May 27, 2003 at 11:09:15AM -0400, Byron A Jeff wrote:
> On Tue, May 27, 2003 at 02:29:10PM +0200, faisal moro wrote:
> > Fortunately i have other, more easy problems at the moment: i have to
> > send some bytes from a controller to a keyboard.
>
> Typical MIDI app, though I wouldn't start there. More in a minute...

I hate when I put something off until later in a post and I forget to
address the issue. Your first project should always be a MIDI THRU. Two
reasons:

1) You have to build both a MIDI IN and MIDI OUT
2) You don't have to worry about the MIDI protocol yet since you are echoing
   what's transmitted by the keyboard.

I always test MIDI THRU at both the hardware and software level. In hardware
I simply connect the MIDI OUT output to the MIDI IN input. My Yamaha Clavinova
can disable the internal keyboard/sound generator connection becoming only
a MIDI keyboard. So I test by running my MIDI THRU hardware to the keyboard.
If it works then I know that my hardware is cool. This also works fine if you
use a separate KB and sound module.

In software do exactly the same. Write an echo routine (which I think that the
aforementioned PICUART.ZIP does by default) and connect the MIDI IN to the
receive of the PIC and the transmit to the MIDI OUT hardware. If everything
is working you get the same effect as the hardware THRU.

Then, and only then, do you start trying to figure out how to do something
else. The MIDI THRU establishes a baseline where you know that all of the
hardware and software works. So if something doesn't work subsequent to that
then it simplifies isolating the problem.

Hope this helps,

BAJ

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads