Shuriken

I just tested it today, but it does not seem to be working. [6707.368] [network_device_init] link speed determined [6707.468] [network_device_init] link available [6708.168] [network_device_init] lost link This is what i get in the MIOS Terminal. After that i tried another a 10/100 Switch instead of the 10/100/1000 Switch and then it doesn't do anything. Maybe the tolerances are different, i don't know. Guess i will have to look for MagJack instead.

Thats a bit hard. All the Ploytec IC are still seperated from my red gm5x5x5 pcb :wink:

The .inf file says VID 16C0 PID 03FE :wink: I am using Windows 7 64 bit. Maybe try to totally remove the driver first and then reinstall?

Well then use the Recom R-78Bxx-1.5 ...

The procedure i described is only if you use an eprom. I will check on my end with changing the names. I haven't tried it yet. Just checked. I connected a GM5x5x5 with JP8 open. Then a GM5 board with JP8 closed open as well. It seems to be working. I see all 10 ports in MIOS Studio.

As an alternative maybe the Recom R-78-1.0 series?

Antonio, The contents of the eprom is defined in eeprom_content.c The default id value is: 0x16c0 & 0xff, // Vendor ID 16C0 --- sponsored by voti.nl! see http://www.voti.nl/pids 0x16c0 >> 8, // Vendor ID (MSB) 1022 & 0xff, // Product ID (LSB) 1022 >> 8, // Product ID (MSB) So VID = 16C0 and the PID = 1022 You could just burn this to an eprom as it does not match the current PID and VID that are defined in the midibox.org_gm5.inf file, the [DRIVER_DEVICELIST] or [DRIVER_DEVICELIST.NTAMD64] section) That section currently looks like: %DevName%=MIDIDEVICE,USB\VID_16C0&PID_03FE ;midibox.org GM5 %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E501 ;out only %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E510 ;input only %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E511 ;1 port %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E522 ;2 ports %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E533 ;3 ports %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E544 ;4 ports %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E555 ;5 ports %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E521 ;eeprom demo %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E5E5 %DevName%=MIDIDEVICE,USB\VID_0A4A&PID_E5CB You should then add a line to it: %DevName%=MIDIDEVICE,USB\VID_16C0&PID_1022 For the next device you could just increase the PID to 1023.

On the frontpage: Q: I want to use two GM5 modules for getting 10 MIDI IO ports, how can I give them individual names? A: 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. 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. Note that without individual names, your OS will numerate the ports so that you are still able to differ between them. I think this should answer your question.

Great news Martijn, i was looking into this myself. I also generated a box. But was still struggling to convert it to a usuable format. Let me know how the box works out. Would be great to finally have a decent housing for it.

These are indeed the switches and caps Wilba used for SEQ and Sammich. I don't think you can source them from any other company. What latigid on said, try to find more stuff you need, then the shipping is free. Or try to find someoneelse who needs something.

Looking at the datasheet i did not see any mentioning of a negative voltage.

Looks very promising. If you manage to iron out the final quirks you have a great tool there :thumbsup:

Looking at the driver, datasheet and hookup schematic the 4 wire SPI mode is needed. So i would say your assumption is correct.

Very nice Orange. :thumbsup:

NP :wink: Unfortunately the Heidenreich online tool, does not automatically adjust if you make H1 too tall. So i think someone needs to actually make a quote request to see if the calculations are ok.

I recently got this display one from mouser. Which can be driven via SPI (48Mhz). At about same price. Hopefully a lot faster. Haven't fired it up though.

I will probably try the same approach this weekend. Will let you know what the outcome is.

What is wrong with the TLV274?

I am well aware off the fact that he is using STM32 Core. Not only because of the fact that he got the Core32 board frome me :wink:. If you look at the pictures, i never ever see more then a blank back panel. You can also notice that he is using low hex distance bolts as his board sits lower then the panel profile. So that would make the picture a good example for an LPC17 solution. But i agree on the fact that we need the exact dimensions based on the measurements that heindreich requires. I couldn't figure it out from the pdf i found either. So my assumptions were based merely on the pictures orange_hand posted.

Don't you need bidirectional signals to make good use of the controller for this display? Because this display look pretty similar to the display i have based on the ILI9320 controller.

The problem is that the LPC board is 10cm deep. So if you mount it to the back, the LCD connectors are touching the CS pcb. With lower hexbolts and not mounting it to the backpanel could work. Not sure how orange_hand exactly did it. His pictures don't tell :wink: It might also be fixable by just making the panel at the front a little bit taller. By the look of things, there is room for the whole construction to change angle without changing the other panels.

Maybe this topic helps

Thnx for updating it :thumbsup: