Subversion Repositories svn.mios

Rev

Rev 1022 | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
380 tk 1
HEADER 3 MBHP USB GM5 Module
2
 
3
<H1>MIDIbox Hardware Platform, USB GM5 Module</H1>
4
 
448 tk 5
<P><CENTER><IMG SRC="mbhp/mbhp_usb_gm5_v1_1.jpg" width=500 height=380></CENTER></P>
380 tk 6
 
7
<DL>
8
   <DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Background Infos </H2></DT>
9
   <DD>
10
<UL CLASS=CL>
11
  <LI><A HREF="http://www.midibox.org/forum/index.php/topic,11387.msg90225.html#msg90225" TARGET="_blank">Forum Article</A></LI>
482 tk 12
  <LI><A HREF="http://www.midibox.org/dokuwiki/tk_gm5_bulkorder" TARGET="_blank">Wiki Page for GM5 and "Small PCB" order</A></LI>
495 tk 13
  <LI><A HREF="http://www.midibox.org/dokuwiki/gm5x5x5" TARGET="_blank">Wiki Page for order of fully featured GM5 Expansion Board</A></LI>
380 tk 14
</UL>
15
  </DD>
16
</DL>
17
 
18
<DL>
19
   <DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Download </H2></DT>
20
   <DD>
21
   <DD><TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
22
    <TR>
932 tk 23
      <TD COLSPAN=4 CLASS=TABCOLOR1>PCB data, can be viewed, modified and converted with <A HREF="http://www.cadsoft.de/download.htm" TARGET="_blank">Eagle Light</A>. The .pdf based schematic has been created with <A HREF="http://opencircuitdesign.com/xcircuit" TARGET="_blank">xcircuit</A>. There are no special eagle schematics available, since components have been netlisted in the .brd file directly!</TD>
380 tk 24
    </TR>
25
    <TR>
26
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Module</STRONG></FONT></td>
27
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Schematic</STRONG></FONT></td>
28
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Layout Data</STRONG></FONT></td>
29
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Quick-view</STRONG></FONT></TD>
30
    </TR>
31
    <TR>
381 tk 32
      <TD CLASS=TABCOLOR2><I>MBHP_USB_GM5_V1_1</I></TD>
380 tk 33
      <TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_usb_gm5.pdf">mbhp_usb_gm5.pdf</A></TD>
482 tk 34
      <TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_usb_gm5_v1_2.brd">mbhp_usb_gm5_v1_2.brd</A></TD>
35
      <TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_usb_gm5_v1_2.gif">mbhp_usb_gm5_v1_2.gif</A></TD>
380 tk 36
    </TR>
37
  </TABLE></DD>
38
 
39
  <DD><TABLE WIDTH="100%" BORDER=0 CELLSPACING=5 CELLPADDING=0>
40
    <TR>
41
      <TD COLSPAN=4 CLASS=TABCOLOR1><FONT SIZE=3>Additional informations</FONT></TD>
42
    </TR>
43
    <TR>
44
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>File</STRONG></FONT></td>
45
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Size</STRONG></FONT></td>
46
      <TD NOWRAP CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Description</STRONG></FONT></TD>
47
    </TR>
48
    <TR>
49
      <TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_usb_gm5_orderlist.txt">mbhp_usb_gm5_orderlist.txt</A></TD>
50
      <TD CLASS=TABCOLOR2>1k</TD>
51
      <TD CLASS=TABCOLOR2><A HREF="http://www.reichelt.de/" TARGET="_blank">Reichelt</A> orderlist</TD>
52
    </TR>
53
    <TR>
54
      <TD CLASS=TABCOLOR2><A HREF="mbhp/mbhp_usb_gm5_4io_board.pdf">mbhp_usb_gm5_4io_board.pdf</A></TD>
55
      <TD CLASS=TABCOLOR2>13k</TD>
56
      <TD CLASS=TABCOLOR2>Breakout board for 4 additional MIDI INs and 4 additional MIDI OUTs</TD>
57
    </TR>
58
  </TABLE></DD>
59
  </DD>
60
</DL>
61
 
62
<DL>
63
   <DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Available Ports </H2></DT>
64
   <DD>
65
<P CLASS=DESC>Following interfaces are provided by the USB GM5 module:</P>
66
  <DD><TABLE CLASS=BOX WIDTH="100%" BORDER=1 CELLSPACING=5 CELLPADDING=0>
67
 
68
    <TR>
69
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Name</STRONG></FONT></td>
70
      <TD CLASS=TABCOLOR1><FONT SIZE=2><STRONG>No. of pins</STRONG></FONT></td>
71
      <TD NOWRAP CLASS=TABCOLOR1><FONT SIZE=2><STRONG>Description</STRONG></FONT></TD>
72
    </TR>
73
    <TR>
74
      <TD CLASS=TABCOLOR2>J1, J2, J3</TD>
75
      <TD CLASS=TABCOLOR2>2</TD>
76
      <TD CLASS=TABCOLOR2>Configuration jumpers. See table in schematic</TD>
77
    </TR>
78
    <TR>
79
      <TD CLASS=TABCOLOR2>J4</TD>
80
      <TD CLASS=TABCOLOR2>3</TD>
81
      <TD CLASS=TABCOLOR2>MIDI In1 Jack (opto isolated)</TD>
82
    </TR>
83
    <TR>
84
      <TD CLASS=TABCOLOR2>J5</TD>
85
      <TD CLASS=TABCOLOR2>3</TD>
86
      <TD CLASS=TABCOLOR2>MIDI Out1 Jack</TD>
87
    </TR>
88
    <TR>
89
      <TD CLASS=TABCOLOR2>J6</TD>
90
      <TD CLASS=TABCOLOR2>10</TD>
91
      <TD CLASS=TABCOLOR2>Digital MIDI IO pins. Can be used for direct digital connections to J11 (MIDI Link port) of the <A HREF="mbhp_core.html">MBHP_CORE</A> module. Connect a J6:Ox pin to J11:MI, and J6.Ix to J11:MO. Up to 5 cores can be bidirectionally linked this way. Ground (J11:Vs, don't forget it!) is available at J7.<BR>
931 tk 92
For audio applications like MIDIbox SID, MIDIbox FM or MIDIbox CV it is recommended to use an optocoupler at MIDI In to avoid a ground loop between USB and audio (-> 50 Hz hum!)<BR>
380 tk 93
For a full featured 2x5 MIDI Interface, line I2-I5 and O2-O5 can be connected to a breakout board with 4 additional opto isolated MIDI INs and 4 additional MIDI Out Jacks.</TD>
94
    </TR>
95
    <TR>
96
      <TD CLASS=TABCOLOR2>J7</TD>
97
      <TD CLASS=TABCOLOR2>2</TD>
931 tk 98
      <TD CLASS=TABCOLOR2>External power supply port. The "Vs" (GND) pin provides the ground for digital MIDI IO connections to J11 (MIDI Link port) of the <A HREF="mbhp_core.html">MBHP_CORE</A> module. Cores could be USB powered via J7, but this isn't recommended for audio applications like MIDIbox SID, MIDIbox FM or MIDIbox CV since this will lead to a ground loop between USB and audio (-> 50 Hz hum!). Note also, that a USB host limits the max. current drain to 500 mA.<BR>
380 tk 99
This port can also be used to power a breakout board for 4 additional MIDI IOs + optocoupler.</TD>
100
    </TR>
101
  </TABLE></DD>
102
  </DD>
103
</DL>
104
 
523 tk 105
<DL>
106
  <DT><H2> <IMG SRC="images/bullet.gif" ALT=""> Windows Driver </H2></DT>
107
  <DD>
108
<P CLASS=DESC>All major platforms (Windows/Linux/MacOS) natively support the USB MIDI protocol, so that the 5 MIDI IO ports of GM5 will be available without additional driver installation. However, the Microsoft driver has some flaws (e.g. no multi client capability, corrupted SysEx transfers when large blocks are transfered, 1 mS latency between each event when they are sent over multiple ports) which can only be solved with a dedicated driver.</P>
109
 
110
<P CLASS=DESC><A HREF="http://www.ploytec.de" TARGET="_blank">Ploytec</A> (the makers of the GM5 chip) provide a Windows driver, which overcomes all these limitations. The performance is great, and the best: for GM5 buyers it's free!<BR>
789 tk 111
<B>Download:</B>
112
  <UL CLASS=CL>
867 tk 113
    <LI><A HREF="gm5/midibox.org_gm5_WIN32_1.0.10.zip">midibox.org_gm5_WIN32_1.0.10.zip from 2009-11-27</A> (32bit version)
114
    <LI><A HREF="gm5/midibox.org_gm5_X64_1.0.10.zip">midibox.org_gm5_X64_1.0.10.zip from 2009-11-27</A> (64bit version)
789 tk 115
  </UL>
116
</P>
523 tk 117
 
867 tk 118
<P CLASS=DESC><B>Hint:</B> it's possible to give each MIDI port it's own name by editing the [Strings] section in the midibox.org_gm5.inf file.<BR>
523 tk 119
Example:
120
<TT><PRE>
121
WDM.MIDI_1.szPname="MIDIbox SID (1)"
122
WDM.MIDI_2.szPname="MIDIbox FM (2)"
123
WDM.MIDI_3.szPname="MIDIbox SEQ (3)"
124
WDM.MIDI_4.szPname="MIDIbox Stribe (4)"
125
WDM.MIDI_5.szPname="Keyboard (5)"
126
</PRE></TT></P>
127
 
128
<P CLASS=INFO>This helps you to organize your MIDI ports, so that they are easier to find:
129
<CENTER><IMG SRC="gm5/gm5_multi_port.gif" width=658 height=168></CENTER></P>
130
  </DD>
131
</DL>
132
 
133
 
134
<DL>
135
  <DT><H2> <IMG SRC="images/bullet.gif" ALT=""> FAQ </H2></DT>
136
  <DD>
137
    <UL CLASS=CL>
138
       <LI><B>Q:</B> the EEPROM is marked as optional in the schematic, what does this mean?<BR>
139
           <B>A:</B> it means, that you don't need to mount an EEPROM to get the module working. It's only a minor feature which helps to separate the modules in the device list if more than 2 devices are connected to a PC, so that they don't appear under the same name. Instead of midibox.org or ploytec.com you could give it the name of your wife/girlfriend or whoever.<BR>
140
              The EEPROM can only be programmed with a special <A HREF="http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fmbhp%2Fmbhp_usb_gm5_eeprom%2F">application</A> running on a <A HREF="mbhp_core.html">MBHP_CORE</A> module.<BR>
141
              My proposal if you are unsure about this option: don't buy an EEPROM, you don't really need it, even when multiple GM5 modules are connected to your PC!</LI>
142
       <LI><B>Q:</B> I want to use two GM5 modules for getting 10 MIDI IO ports, how can I give them individual names?<BR>
143
           <B>A:</B> Break the bridge at J8 of the PCB with a small screwdriver, so that IC2:IO4 is not connected to ground anymore. This selects the ploytec.com VID, so that your operating system can differ between two devices (midibox.org and ploytec.com) and installs an individual .inf file.<BR>
144
           If more ports with individual names are required, you could use different IO number configurations (J1..J3), since this results into different PIDs. Alternativeley you can use an EEPROM to define your own IO port configuration and PID - so long VID is assigned to Ploytec range, the Windows driver will find it.<BR>
145
           Note that without individual names, your OS will numerate the ports so that you are still able to differ between them.</LI>
146
       <LI><B>Q:</B> Is a dedicated driver planned for MacOS or Linux?<BR>
147
           <B>A:</B> This isn't required, as the legacy drivers are already working great!</LI>
148
    </UL>
149
  </DD>
150
</DL>
151
 
380 tk 152
FOOTER