Jump to content

finally getting output!  very very strange output.


Guest jkerman

Recommended Posts

Guest jkerman

I am using midibox 64 with 6 faders (to test) no buttons, and no LCD.  I have 1 analog multiplexer.

All unused ports are clamped correctly, and there are no midi events until i move the POT.  I am getting lots of PC events, on 4 or 5 midi channels.  What could be causing this?  It should only be sending on channel 1 right?

also, what are the "default" settings for all the pots?

thanks a lot! I think im going to try connecting some buttons instead to see if i get more solid results.

Link to comment
Share on other sites

Guest jkerman

here is my mixi-ox output for moving fader #1. approx 1/4 of the way

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT              

0014B99C   1  --     F3    00    --   --  ---  Song Select          

0014DECB   1  --     CE    00    --   15  ---  Program Change        

0014DECB   1  --     CE    00    --   15  ---  Program Change        

0014DECC   1  --     FE    --    --   --  ---  Active Sensing        

0014DECB   1  --     C3    00    --    4  ---  Program Change        

0014DEE3   1  --     CE    00    --   15  ---  Program Change        

0014DEE3   1  --     CE    00    --   15  ---  Program Change        

0014DEE4   1  --     FE    --    --   --  ---  Active Sensing        

0014DEE3   1  --     B3    00    00    4  ---  CC: Bank MSB          

0014DEF8   1  --     CE    00    --   15  ---  Program Change        

0014DEF8   1  --     CE    00    --   15  ---  Program Change        

0014DEF9   1  --     FE    --    --   --  ---  Active Sensing        

0014DEF9   1  --     83    00    00    4  C -1 Note Off              

0014DF0F   1  --     CE    00    --   15  ---  Program Change        

0014DF10   1  --     CE    73    --   15  ---  Program Change        

0014DF11   1  --     FE    --    --   --  ---  Active Sensing        

0014DF2B   1  --     CE    00    --   15  ---  Program Change        

0014DF2B   1  --     CE    00    --   15  ---  Program Change        

0014DF2C   1  --     CE    43    --   15  ---  Program Change        

0014DF2D   1  --     FE    --    --   --  ---  Active Sensing        

0014DF49   1  --     CE    00    --   15  ---  Program Change        

0014DF49   1  --     CE    00    --   15  ---  Program Change        

0014DF4A   1  --     CE    33    --   15  ---  Program Change        

0014DF4B   1  --     FE    --    --   --  ---  Active Sensing        

0014DF6C   1  --     CE    00    --   15  ---  Program Change        

0014DF6C   1  --     CE    00    --   15  ---  Program Change        

0014DF6C   1  --     CE    03    --   15  ---  Program Change        

0014DF6D   1  --     FE    --    --   --  ---  Active Sensing        

0014DF90   1  --     CE    00    --   15  ---  Program Change        

0014DF91   1  --     CE    00    --   15  ---  Program Change        

0014DF91   1  --     CE    00    --   15  ---  Program Change        

   

Link to comment
Share on other sites

Hi,

the default settings are documented in the midibox64.ini file which can be found under http://www.ucapps.de/midibox/mk_syx.zip

Normally common CC events are assigned to the pots. A possible reason why your box sends Program Change events could be a wrong baudrate. Hopefully you are using a 20 MHz crystal? Did you disable the "to-Host" option?

Best Regards, Thorsten.

Link to comment
Share on other sites

Guest jkerman

I just built my midi-in port.  When the midi cable is plugged into the computer, the box will send about 40 lines of random stuff, and lock whenever i move the POTS, or send any sysex data.

I am using a 20mhz crystal, but ill have to double check for interference on my design...  Maybe i'm using the wrong type?  Is there an easy way to tell "parelell cut" from other types?

(thanks for the reply!)

Link to comment
Share on other sites

No, there is no easy way to check the crystal type - only the specs given by the manufacturer can help.

Ok, I think that you should test a more simple firmware in order to eliminate all possible errors....

http://www.ucapps.de/howtodebug/test_tx.hex.zip

sends a volume controller (B0 07 7F) every second, and

http://www.ucapps.de/howtodebug/test_rxtx.hex.zip

just forwards the incoming data from MIDI-In to MIDI-Out

This will help you to determine if the chip is clocked with the correct frequency.

Btw.: did you program the PIC with IC-Prog? Did you ensure that the "HS Oscillator" is selected?

Best Regards, Thorsten.

Link to comment
Share on other sites

Guest jkerman

heres some output from the test program

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT              

00007179   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

0000717A   1  --     CE    06    --   15  ---  PC: Harpsichord      

0000717A   1  --     E0    00    00    1  ---  Pitch Bend            

00007530   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

00007531   1  --     CE    08    --   15  ---  PC: Celesta          

00007531   1  --     E0    00    00    1  ---  Pitch Bend            

000078E7   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

000078E8   1  --     CE    0E    --   15  ---  PC: Tubular Bells    

000078E8   1  --     E0    00    00    1  ---  Pitch Bend            

00007C9E   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

00007C9F   1  --     CE    30    --   15  ---  PC: String Ens 1      

00007C9F   1  --     E0    00    00    1  ---  Pitch Bend            

00008055   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

00008056   1  --     CE    36    --   15  ---  PC: Synth Voice      

00008056   1  --     E0    00    00    1  ---  Pitch Bend            

0000840C   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

0000840D   1  --     CE    38    --   15  ---  PC: Trumpet          

0000840D   1  --     E0    00    00    1  ---  Pitch Bend            

000087C3   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

000087C4   1  --     CE    3E    --   15  ---  PC: SynthBrass 1      

000087C4   1  --     E0    00    00    1  ---  Pitch Bend            

00008B7A   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

00008B7B   1  --     C0    00    --    1  ---  PC: Acc. Grand Piano  

00008B7B   1  --     E0    00    00    1  ---  Pitch Bend            

00008F31   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

00008F31   1  --     C6    00    --    7  ---  PC: Acc. Grand Piano  

00008F32   1  --     E0    00    00    1  ---  Pitch Bend            

000092E8   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

000092E8   1  --     C8    00    --    9  ---  PC: Acc. Grand Piano  

000092E9   1  --     E0    00    00    1  ---  Pitch Bend            

0000969F   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

0000969F   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

000096A0   1  --     E0    00    00    1  ---  Pitch Bend            

00009A56   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

00009A57   1  --     E0    00    00    1  ---  Pitch Bend            

00009E0D   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

00009E0D   1  --     F6    --    --   --  ---  Tune Request          

00009E0E   1  --     E0    00    00    1  ---  Pitch Bend            

0000A1C4   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

0000A1C4   1  --     F8    --    --   --  ---  Timing Clock          

0000A1C5   1  --     E0    00    00    1  ---  Pitch Bend            

0000A57A   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

0000A57B   1  --     FE    --    --   --  ---  Active Sensing        

0000A57C   1  --     E0    00    00    1  ---  Pitch Bend            

0000A931   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

0000A932   1  --     CE    00    --   15  ---  PC: Acc. Grand Piano  

Link to comment
Share on other sites

Guest jkerman

The strange thing is that the results (although incorrect) seem to change over time.  the longer it runs, the more different signals I get.   The output is identical every test run i do.

VERY odd!   I think i might just order a new crystal.  Unless there is a capacitence issue?

The ic-prog options were correct, and i have tried different PIC's as well!

Link to comment
Share on other sites

Guest jkerman

replaced the crystal, and all output is as expected now!  Thanks for the tips.

Ive got my hands on an old 48 channel analog light board with fried transformers in it.  Its turning out to be a VERY cool midi mixing console!  I'm sure I'll send some picttures of it when its cleaned up a little.

thanks again!

Link to comment
Share on other sites

  • 2 months later...
Guest mickb

Having similar problems as described above.

Tried running the test rxtx.hex file, and the data send in is not returned corretly. Does this indicate a crystal problem?

I've had a look at the data sheet for the crystal i ordered, and the only information i can find about the cut is that it is "AT Fundamental"

What does this mean? is it the wrong type?

The crystal was ordered from www.farnell.co.uk order number 177408

Thanks

Michael

Link to comment
Share on other sites

Hi Michael,

the crystal type seems to be ok (I checked this on the farnell homepage), so it must be another problem. Could you create a MIDI-Ox logfile and post it here? It would be interesting, on which way the MIDI events are corrupted.

Best Regards, Thorsten.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...