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 the bx-24 to interpret data from a midi keyboard. I have constructed a midi input according to the schematic on Tom Igoe's site. This is fed to the com1 port of the bx. I can get the keyboard sending info to the bx (monitoring it through debug.print statements), but the problem is that the numbers are all off. For instance, when it should give me something like 144 60 100 for noteon, notenumber, velocity, I'll instead get something like 255 0 147, sending numbers beyond the realm of the midi spec. Which makes me wonder, is there hex inversion going on at the com1 port that is garbling my input? I tried attaching the input to com3 and turned off inversion, and it gave me slightly better numbers (i would get a 144 for a noteon occasionally) but it was not triggering for every note that I hit, and it was also garbled (perhaps having to do with the low baudrate). So any suggestions on how to get non-garbled midi input would be appreciated. Is there any way to do hex inversion on the software/prog. side, rather than having to buy a hex inverter, as my deadline for this project is tomorrow. Thanks, -Henry

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


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