TK.

As mentioned earlier, the MIOS32_BOARD_J15_PortInit() function will already set RW to 0 It's a typo that RW will be set to 0 again after E has been pulsed, but it doesn't make a difference because RW was already 0 However, I moved the function call before the E pulse now (especially for documentation purposes) and recompiled the bootloader: http://www.ucapps.de/mios32/mios32_bootloader_v1_005_2.zip I don't think that this will solve the problem, but just created this binary to prove at your side (since you haven't installed the toolchain yet...) Best Regards, Thorsten.

Hi, could you please provide a link to the datasheet? RW is set to 0 by MIOS32_BOARD_J15_PortInit() The HD44780U datasheet clearly states that the E input should be deactivated before a change (*) on the RW line. (*) change means, that it doesn't matter if there is a rising or falling edge on the RW line. see attachment: I understand this the following way: the RW state is captured with the rising edge of the enable input, and RW should stay stable for at least t_AH It can't be excluded that the vendor of your LCD hasn't implemented the HD44780 spec correctly, but it's more likely a connection error. Did you stuff the J15_S jumper for 5V operation? Best Regards, Thorsten.

Alternative solution: order at least 4 GM5 chips to make the 6th bulk order happen - it's even cheaper than buying a LPCXPRESSO module! ;) -> http://www.midibox.org/dokuwiki/doku.php?id=tk_gm5_bulkorder Best Regards, Thorsten.

-> http://www.midibox.org/dokuwiki/doku.php?id=tk_gm5_bulkorder Best Regards, Thorsten.

A CME Z-KEY 49 seems to be nice for this purpose: This isn't a cheap solution (ca. 230 EUR @Thomann), but it has an aluminum case and plenty of space at the right side as if the designers considered the needs of the DIY folks ;) Best Regards, Thorsten.

Meanwhile I got the prototype PCBs... it works!!! Thanks SmashTV for the great layout! :) I've 13 spare PCBs which I'm selling for 8 EUR per piece. If you are interested, just write me a PM with your postal address and PayPal account Best Regards, Thorsten.

There is a simple way: if everybody would buy 4 GM5 chips for 18 EUR instead of only 1 for 4.50 EUR, the bulk order could happen once we found 62 people Best Regards, Thorsten.

MIOS32 automatically interleaves the MIDI events, and IN/OUT ports are FIFO buffered, so that there is no performance drawback. Means: the MIDI ports could still be handled at full speed over a single USB cable. :) Just connect multiple LPCXPRESSOS to a cheap USB Hub with integrated PSU (so that no separate PSU is required for the LPCXPRESSO modules) Best Regards, Thorsten.

Thats possible and there is no bandwidth issue with this solution as USB MIDI transfers the data much faster than a HW MIDI interface. I just had a look into the LPC1769 datasheet: the 4th UART is available at J4B of the MBHP_CORE_STM32 module, which is intended as a second IIC port, but I think that using it for an additional UART makes more sense. This reminds me that I should add this option to the MBSEQ V4 firmware as well. The 3rd UART is available at J5B And for your interest: if you need a PCB for the MIDI sockets + optocoupler circuits: I've still some spare GM5x5x5 boards which could be re-used for such a solution ;) Best Regards, Thorsten.

In theory this is possible, but in practice I want to make this MBSEQV4L variant as simple as possible with a straightforward workflow and without too many options. If you need more options, create an own firmware variant (requires programming skills) or build a MBSEQV4 yes, this is possible. And vice versa: you can playback all 16 tracks which have been prepared on a MBSEQV4 with the MBSEQV4L yes, why not cannibalizing a cheap MIDI keyboard and building MBSEQV4L into the case? :) Best Regards, Thorsten.

I will have more sparetime this weekend, and the weather forecast is bad as well ;) Best Regards, Thorsten.

Wow, great work! :) Best Regards, Thorsten.

Of course, the MBHP_CORE_LPC17 module can be used as a pure MIDI interface, MIOS32 is already prepared for this and there are also example applications, like this one: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_midi_2x2%2F or this advanced one: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_osc_midi_proxy%2F which supports OSC via ethernet as well. 3 UARTs are natively supported by MIOS32, the 4th UART could be added as well if really required. Of course, you could add IIC_MIDI interfaces in addition, or a hacker could implement some software based UARTs (like Ploytec did for the GM5), because the LPC17 has more than enough processing power. BUT: such an interface would only work properly under MacOS and Linux, since the USB MIDI drivers are well supported and working flawlessly (and without latency issues) Under Windows there are several issues with different OS versions. E.g. Win7 in 64bit mode: USB MIDI works only properly if the USB interface is configured for a single port. Once the USB MIDI interface is configured for multiple ports, MIDI transfers can sporadically get stucked. Thats the reason why the Ploytec driver is still superiour. And no, it won't work with the MBHP_CORE_LPC17 module as it's bundled with the GM5 hardware. My own interest to develop an alternative solution is zero, since I don't work under Windows (and own some GM5 interfaces anyhow :)) But somebody with Windows USB driver skills should be able to develop a proper solution. Best Regards, Thorsten.

Which part of the LTC module do you mean? MIDI Thru, the Second MIDI Out, MIDI IN/OUT LED don't need any activation. The RS232 option isn't supported by MBSID Best Regards, Thorsten.

Clever! Best Regards, Thorsten.

This is not a bug, but just an indication that this issue can't be solved via software. Please remove the changes and fix your hardware as well - it's simple! Best Regards, Thorsten.

Shipped today: Nestle mirmidi florian gaud nuke ssp jojjelito Waiting for money: Harley Godzisz kok6 Sidmonster Waiting List: Altitude Raphael discotsoutsouni In Stock: 0 GM5 chips (+2 reserved) 34 PCBs (+7 reserved) Best Regards, Thorsten.

In this case there is no software solution, you have to fix the encoder connections hardware-wise! (this shouldn't be so difficult, even if a PCB is used) Best Regards, Thorsten.

So, these are encoder number #1, 2, 3, 8, 9, 10, 11, 12 in the MIOS_ENC_PIN_TABLE (-> setup_* file) Workaround (simplified form, there are also ways to optimize this check but it would lead to more complicated code): ;; -------------------------------------------------------------------------- ;; This function is called by MIOS when an encoder has been moved ;; Input: ;; o Encoder number in WREG and MIOS_PARAMETER1 ;; o signed incrementer value in MIOS_PARAMETER2: ;; - is positive when encoder has been turned clockwise ;; - is negative when encoder has been turned counter clockwise ;; -------------------------------------------------------------------------- USER_ENC_NotifyChange movf MIOS_PARAMETER1, W xorlw 1 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer movf MIOS_PARAMETER1, W xorlw 2 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer movf MIOS_PARAMETER1, W xorlw 3 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer movf MIOS_PARAMETER1, W xorlw 8 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer movf MIOS_PARAMETER1, W xorlw 9 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer movf MIOS_PARAMETER1, W xorlw 10 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer movf MIOS_PARAMETER1, W xorlw 11 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer movf MIOS_PARAMETER1, W xorlw 12 skpnz comf MIOS_PARAMETER2, F ; inverse incrementer ... [/code] Best Regards, Thorsten.

Instead of copy&pasting the pattern, you could also go to the SAVE page (press MENU+GP#14), and store the current pattern to a new location. In this page, use GP#1 encoder to select the group (resp. one of 4 patterns that are currently running), and GP#7 encoder to select the pattern slot (A1..H8). (*) Press SAVE (GP#8 button) -> give the pattern a name -> done Pattern selection: go to the pattern menu. Now you can change the pattern of the 4 groups directly with GP#4, GP#8, GP#12, GP#16 encoders. You can also use the GP buttons to change the pattern of the selected group, use GP#1..GP#8 to select A..H (this won't lead to a change, but preselect the pattern set), and then GP#9..16 to select 1..8 Once you've entered the pattern number, the pattern will either change immediately, or synched to the measure depending on the selection that you made in the options page. The copy function either copies the steps only, or all steps + parameters. This can be configured in the options page. But for a 1:1 copy, just use the SAVE function. Best Regards, Thorsten. (*) The pattern bank can be changed with GP#6, but it's recommended to let it assigned to the group. Means: G1 should use Bank1, G2 should use Bank2, etc...

Thats fine for me. Note that this is a MIDIbox SID V2 kit (if PIC18F4685 are included) Best Regards, Thorsten.

Hi Cimo! :) Software-wise it wouldn't be so much effort to program a small application which allows to control 16 8x8 LED matrices (=1024 LEDs) which can be controlled via MIDI, USB-MIDI, OSC (I can program a quicky app if you want) But for 1W LEDs you will need source, but also sink drivers, otherwise the 74HC595 will be overloaded. And you will need a strong PSU! ;) Best Regards, Thorsten.

Which encoders should be reversed exactly? Best Regards, Thorsten.

Yes, a schematic is available: http://www.ucapps.de/midibox_seq/mbseq_lite_blm.pdf Best Regards, Thorsten.