Confused by MidiSense

Posts about MIDIsense. open source MIDI sensor platform

Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.
Locked
Sixerdoodle
 
Posts: 5
Joined: Sat Jun 09, 2007 12:00 pm

Confused by MidiSense

Post by Sixerdoodle »

Trying to get Midisense working reliably on one of my systems. First system has an Edirol UA-25 interface. I've got it to work, but it takes a little dance. :-)

From prior work I did with the UA-25 trying to build my own midi interface it appears this device uses Midi Active Sense (ie it constantly throws out 0xFE's). Check http://www.borg.com/~jglatt/tech/midispec.htm and scroll down to the Active Sense section.

What happens - Plugging in and turning on MidiSense and then firing up the MidiSense software ends up with a "Failed to find any MIDISense boards".

However, unplug the cable connected to the MidiSense MidiIN port, cycle the Midisense power, wait a couple of seconds, then plug in the MidiIN and now the software successfully finds the MidiSense board. There's the dance!

What I think is going on - Appears the 0xFE's being periodically thrown out by the UA-25 is confusing the initial 1 sec test for "is firmware being loaded" and the board goes into firmware load mode rather than sense mode. (confirmed by the fact the midi activity light stays off) By disconnecting and reconnecting the MidiIn, you can fake out the board to not go into "firmware being loaded" mode (and you sucessfully get the midi activity light)

I think that stream of 0xFE's is also causing some problems with the firmware load and/or at least the firmware verify as it appears I successfully loaded v1.2 but it won't verify. Also may be that the 0xFE's perhaps are confusing the software because when it does connect, doesn't seem to be able to read in the current sensor configuration (though in action the sensors perform correctly). Or perhaps it really is that the v1.2 firmware didn't load completely because of the 0xFE's?

Dang 0xFE's! :-)

adafruit
 
Posts: 12151
Joined: Thu Apr 06, 2006 4:21 pm

Post by adafruit »

yes! this is defintely something i will be fixing in the next firmware version. however, theres no way for you to fix it :( i have to change the bootloader. ill add this to the faq, thanks for reminding me

i may be able to fix the software/firmware so that they ignore the 0xFE signals. man is there some way you can get the driver to quit doing it? i dont have one, but it sounds like a real pain!

Sixerdoodle
 
Posts: 5
Joined: Sat Jun 09, 2007 12:00 pm

Still odd problems....

Post by Sixerdoodle »

Ok, so I moved to my other system, the one without the 0xfe problem :-) Still seeing weird stuff like lockups when I try to calibrate a sensor. So, thought I'd try reloading the firmware. Says it completes, but the odd part is that it doesn't go thru the clearing eprom step or anything, just says firmware update complete.

[976] 21:32:01: uploading C:\Tom's Stuff\MIDIsense_v1.1\firmware\midisense-res12.hex
[976] 21:32:01: stop
[976] 21:32:01: Closing MIDI ports
[976] 21:32:01: opening connections!
[976] 21:32:01: opened midi
[976] 21:32:09: Sending Packet: 0xf0 0x7d 0x44 0x53 0x0 0xf7
[976] 21:32:09: sent
[976] 21:32:09: Recv'd Sysex: 0xf0 0x7d 0x33 0x36 0x1 0x34 0x1 0x32 0x0 0x34 0x1 0x39 0x1 0x37 0x0 0x39 0x1 0xf7
[976] 21:32:09: looking for board: 7 bytes
[976] 21:32:09: Found board 'midisns'
[976] 21:32:09: Sending Packet: 0xf0 0x7d 0x44 0x78 0x0 0xf7
[976] 21:32:09: sent
[976] 21:32:09: Recv'd Sysex: 0xf0 0x6a 0x5f 0x70 0x40 0x62 0x30 0x71 0x5 0x90
[976] 21:32:09: Recv'd Sysex: 0xf0 0x7d 0x33 0x6 0x1 0xf7
[976] 21:32:09: Sending Packet: 0xf0 0x7d 0x44 0x4e 0x0 0xf7
[976] 21:32:10: sent
[976] 21:32:10: Recv'd Sysex: 0xf0 0x7d 0x33 0x36 0x1 0x34 0x1 0x32 0x0 0x34 0x1 0x39 0x1 0x37 0x0 0x39 0x1 0xf7
[976] 21:32:10: Sending Packet: 0xf0 0x7d 0x44 0x79 0x0 0xf7
[976] 21:32:10: sent
[976] 21:32:10: Recv'd Sysex: 0xf0 0x6a 0x5f 0x70 0x40 0x62 0x30 0x71 0x5 0x90
[976] 21:32:10: Recv'd Sysex: 0xf0 0x7d 0x33 0x6 0x1 0xf7
[976] 21:32:10: Bootloader is at 0x1800
[976] 21:32:10: Sending Packet: 0xf0 0x7d 0x44 0x78 0x0 0xf7
[976] 21:32:10: sent
[976] 21:32:10: Recv'd Sysex: 0xf0 0x7d 0x33 0x36 0x1 0x34 0x1 0x32 0x0 0x34 0x1 0x39 0x1 0x37 0x0 0x39 0x1 0xf7
[976] 21:32:10: Sending Packet: 0xf0 0x7d 0x44 0x61 0x0 0xf7
[976] 21:32:11: sent
[976] 21:32:11: Recv'd Sysex: 0xf0 0x6a 0x5f 0x70 0x40 0x62 0x30 0x71 0x5 0x90
[976] 21:32:11: Recv'd Sysex: 0xf0 0x7d 0x33 0x6 0x1 0xf7
[976] 21:32:11: Sending Packet: 0xf0 0x7d 0x44 0x79 0x0 0xf7
[976] 21:32:11: sent
[976] 21:32:11: Recv'd Sysex: 0xf0 0x7d 0x33 0x36 0x1 0x34 0x1 0x32 0x0 0x34 0x1 0x39 0x1 0x37 0x0 0x39 0x1 0xf7
[976] 21:32:11: Firmware Upload Complete.

adafruit
 
Posts: 12151
Joined: Thu Apr 06, 2006 4:21 pm

Post by adafruit »

to clear the memory click the "reset" button in the midisense program

Sixerdoodle
 
Posts: 5
Joined: Sat Jun 09, 2007 12:00 pm

hangs during config

Post by Sixerdoodle »

Well.... tried getting to the reset button, problems with the config operation completing, so can't ge to reset button. locks up after sensor #2. Debugview showing PortMidi bufferoverflows.

Answer is: appears to be a bug in the Windows 2000 Midi device implementation or at least how Midisense interacts with it. moved over to a WXP machine. Much better now. Config completes, reset works, board much more stable.

word to the wise, watch out for W2K...

Locked
Please be positive and constructive with your questions and comments.

Return to “MIDIsense”