TK.

You are right, the PSU voltage should be higher than the operating range, otherwise the amplified voltage will be clipped around the min/max voltage. I would also recommend to use a rail-to-rail OPA (such as LM324) instead of the TL074 in this case. A PSU which outputs +/- 6V should be sufficient (if I'm not wrong now, maybe somebody can confirm) Best Regards, Thorsten.

I would propose to try any prebuilt .hex file of the MB64 release package. Best Regards, Thorsten.

Thanks for the feedback, I already felt guilty that I broke something in the most recent MIOS Studio release - although it was intended to make uploads more secure than ever before ;) Best Regards, Thorsten.

Hi Jef, it's well hidden in the MIDI router configuration, rightmost selection item: Best Regards, Thorsten.

I agree, this is a good measure to simplify the PSU R_x/R_y: I've to search in my records for the best matching resistor values with bipolar option, this can take some time (because I'm currently not at home...) Best Regards, Thorsten.

For me it sounds like a problem with the PC MIDI OUT -> Core Module MIDI IN connection. What are the results of the tests described in the Troubleshooting Guide? Best Regards, Thorsten.

Hi, you could ask sonicwarrior for the eagle file. Best Regards, Thorsten.

Hi, how is your core module connected to your computer? Are you using a MIOS32 based core module as a USB-MIDI interface, and does it have the same device ID like the PIC? In this case, MIOS Studio would respond with this message on a query. If this isn't the case: needs further analysis, but here a trick which should always help: - power-off the core - start .hex upload, you will be asked to power-on the core - power-on the core Best Regards, Thorsten.

Shipped today: Fos romsom pm23 shimoda DrKorg Will be shipped once I got the money: Sampas Jojoce There are 14 GM5 chips and 14 Mini-PCBs left Best Regards, Thorsten.

The port configuration is stored in the session directory, MBSEQ_C.V4 file: MIDI_IN_RecPort It's 0 by default which means all ports enabled. Other valid settings: USB1: MIDI_IN_RecPort 16 USB2: MIDI_IN_RecPort 17 USB3: MIDI_IN_RecPort 18 USB4: MIDI_IN_RecPort 19 IN1: MIDI_IN_RecPort 32 IN2: MIDI_IN_RecPort 33 IN3: MIDI_IN_RecPort 34 IN4: MIDI_IN_RecPort 35 Best Regards, Thorsten.

Only a short mail, because I'm currently very busy with other things: - MBCV is an old MIDIbox project. We had a dedicated PCB for it some years ago + a bulk order, but it was only intended as a one-off (PCB layout is available at http://www.sdiy.de/de/projects/midiboxcv.html) - MBCV V2 is under development: It could still take some months until it's ready for broader usage, but you would try to create a PCB + setup a bulk order for an expired project. - a redesigned AOUT module is under discussion: So: currently it isn't a good idea to create a complete PCB based on a design which will change in future. Best Regards, Thorsten. /edit: synthdiy.de -> sdiy.de

Thanks for the input! This pushes the priority on my TODO list! :) But I won't have to possibility to check this before next week. Best Regards, Thorsten.

PINMODE_OD1 isn't a function, but a configuration register of the LPC17 port peripheral. MIOS32_SPI0_PP_INIT applies an AND mask over this register, which means that bits will be cleared (-> OD function for given pins disabled) MIOS32_SPI0_OD_INIT applies an OR mask over this register, which means that bits will be set (-> OD function for given pins enabled) Best Regards, Thorsten.

The LPCXPRESSO module has an external EEPROM (something like a on-board bankstick), which can be accessed through include $(MIOS32_PATH)/modules/eeprom/eeprom.mk An application example can be found under: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_osc_midi_proxy%2F Relevant files: Makefile: includes the EEPROM driver mios32_config.h: configures the EEPROM function presets.c: reads/writes into EEPROM Best Regards, Thorsten.

The next lucky guys: digga nebula loderbast fcd72 shimoda rumpelfilter stiwi gwaidan Will be shipped once I got the money: Fos romsom Sampas Jojoce There are 18 GM5 and 17 Mini-PCBs left Best Regards, Thorsten.

Your include/mios32/mios32_osc.h file isn't up-to-date -> please update the complete repository. If you want to find out the exact changes, just use the compare function of the svn webviewer: http://svnmios.midibox.org/comp.php?repname=svn.mios32&compare%5B%5D=%2F%401524&compare%5B%5D=%2F%401523 It usually helps to understand the required modifications (ignore the change in MBKB...) Best Regards, Thorsten.

I guess that you mean "distribute" or "route" instead of divide. The clockbox can only act as a MIDI clock master, and it doesn't route incoming events to the MIDI outs -> no go. And the GM5 has no integrated MIDI router, which means that MIDI events have to be routed by your PC based application, which will add (a small amount of) latency. Let's say ca. 5 mS The routing could be done from Live (I guess... I'm a Logic user) To give you an alternative solution: personally I would prefer to use a MBHP_CORE_LPC17 module with one of the major MIOS32 based firmwares, such as MIDIO128. You are not interested on the controller functions... but you will like the integrated MIDI router with up to 16 nodes. With each node you can define a forwarding path from a MIDI input to a MIDI output. You can even filter and modify MIDI channels. 4 USB IOs and 4 MIDI IOs are available... and OSC for the case that you want to do some ethernet experiments ;-) The LCD based control surface isn't required, since the device can also be configured from the MIOS terminal. In other words: the MBHP_CORE_LPC17 module would be sufficient for your purposes. + the MIDI port extension for two additional MIDI IOs: http://www.ucapps.de/mbhp/mbhp_core_lpc17_midi3_midi4_extension.pdf (no PCB available, you have to build it on veroboard) Advantage of this solution: it even works standalone without a computer, and the USB-MIDI performance is comparable to a GM5. Disadvantage: a bit more complex to build Best Regards, Thorsten.

Typical trouble with the splitted RAM... :-( However, we had luck: in osc_server.c I found an array which was located in RAM, but actually is constant (the search tree) It's now located in flash, and 1k AHB RAM is free for other purposes :) Best Regards, Thorsten.

Hi, you would have to search for a project which supports USB host functionality. The GM5, and also my own USB based projects, can't do this. Best Regards, Thorsten.

Yes, this should be possible. It isn't the optimum solution, but due to the limitations of the OT (no MIDI clock slave mode if used as looper), it has to be accepted. Definitely yes! Since we are hobbyists and doing this during our sparetime, we don't assemble complete kits. Procedure: - Send me a PM to order the GM5 chip, please take the specified form which can be found at the bottom of this page: http://www.midibox.org/dokuwiki/doku.php?id=tk_gm5_bulkorder - Send Nils a PM to order the GM5x5x5 PCB - order the remaining components at your favorite electronic shop, here the BOM: http://www.midibox.org/dokuwiki/doku.php?id=gm5x5x5 Best Regards, Thorsten.

Unfortunately I won't have the time to port the firmware for other PICs; and I wouldn't be able to try out changes by myself... Best Regards, Thorsten.

This is not a "TwinSID", but a MIDIbox SID V2, right? You will find a lot of documentation here: http://www.ucapps.de/midibox_sid_manual.html sorry, but I don't understand the question. Could you please write it in other words? You could upload the presets/v2_vintage_bank.syx file with the SysEx Librarian which is part of MIOS Studio: Best Regards, Thorsten.

You would have to add #ifdef... switches, and set the switch in your mios32_config.h file Best Regards, Thorsten.

Here's an interconnection example, which is very similar for the LPC17 core (J19 is used as well, this port is just located at a different location) http://www.ucapps.de/midibox_seq/mbseq_v4_interconnections.pdf For a redesigned AOUT module it makes sense to use a 2x5 pin IDC header for a 1:1 connection to the core. Best Regards, Thorsten.

Hi, here are the fuse settings: They are also part of the .hex file. This means that some programmers automatically will get the correct settings if they extract the information from the .hex file Best Regards, Thorsten.