TK.

I added this to the other requests in the wish list - it will be some effort to integrate such a mode into the existing architecture and GUI, therefore a quick implementation is very unlikely. Best Regards, Thorsten.

At a first glance I don't see a configuration error. However, I think that this combination can lead to unstable SRIO transfers because of the high number of SRIOs and different chain lengths of the DIN/DOUT SRs. This would also explain, why the BLM acts strange. A prober solution to overcome this problem is MBHP_LINE_DRIVER: http://www.ucapps.de/mbhp_line_driver.html I don't know how exactly your hardware looks like, but if the TPD is close to the wilba frontpanel, then it's sufficient to connect the transmitter/receiver between TPD and BLM4x16 Best Regards, Thorsten.

This page describes how to format a SD Card from MBSEQ (sdcard_format command), and how to upload the right MBSEQ_HW.V4 file: -> http://www.ucapps.de/midibox_seq_manual_in.html Best Regards, Thorsten.

Currently there s no auto-save function, but by storing the patch the learnt messages will be persistent. This can be done from the DISK menu page (via SCS) or from MIOS Terminal Best Regards, Thorsten.

looks fine, the leftmost pins (smaller pads) are not used anyhow, therefore it's ok if they are missing. Best Regards, Thorsten.

Similar spacing like on the MBSID panel, this should work Best Regards, Thorsten.

Does the voltage change at the TLV5630 outputs (pin 12, 13, 14, 15, 6, 7, 8, 9)? See the schematic to find the outputs: http://www.midibox.org/dokuwiki/lib/exe/fetch.php?media=seppoman:mbhp_aout_ng_r1_schematic.pdf The REF output might be interesting as well, it should output 2V once the TLB5630 has been correctly configured. You can re-configure the device in the MBSEQ CV Configuration page during runtime (w/o power-cycling the core) by selecting a different interface, and then AOUT_NG again. Last but not least: I just noticed that there is an integrated AOUT troubleshooting app in the MBSEQ firmware, which might help as well! Enter "testaoutpin" in MIOS Terminal to get the appr. help page Best Regards, Thorsten.

Hi Nico, on the SC line you should see a burst of 128 clock cycles each mS The RC line will send a short pulse before and after the SCLK pulse The SO line will output the patterns during the SC burst. The SI line should send a pattern during the SC burst. It's all-1 if no button is pressed. Testing with a scope is rel. simple: just ensure that the SC and RC signal is visible on all 74HC595/165 CLK/LD inputs. And check that the serial inputs and outputs transfer the pattern. If one of the chips doesn't output the pattern, it's either because it doesn't get a pattern at the input, or because a short/power problem at this IC (in worst case the IC is defective, but this would be unusual). Schmitt Trigger: immediately forwards the input data. If you don't see any toggles at the outputs, it's related to a short/power issue. Best Regards, Thorsten.

Ok, this version also supports LPC17: http://www.ucapps.de/mios32/midibox_ng_v1_033_pre20.zip Best Regards, Thorsten.

Alternative solution: http://midibox.org/forums/topic/19761-sd-card-reader-3m-alternative/#comment-172182

No alternative solution has been found yet. Best Regards, Thorsten.

It isn't supported yet, but I could add this option without much effort. Basically the same driver like for the MAX525 could be used, only the word format is slightly different. Best Regards, Thorsten.

Ok, under these conditions MBFM is indeed a nice solution, since it has been created at a time where industrial quality PCBs where not common in the DIY world :) Best Regards, Thorsten.

This isn't required for the receiver board, since it provides a dedicated connector for the AOUT module called JAOUT: Best Regards, Thorsten.

yes, the operators of an instrument can only be controlled from a single MIDI channel. There is no possibility to satisfy special requests - this is a really old project written in assembly language for an expired microcontroller. It also has a very inflexible patch structure (where I intended to allow the control of all parameters via CC). It isn't fun to enhance this, therefore it's officially only in maintenance mode anymore. However, it makes some cool sounds! Don't miss the powerful randomizer! ;-) Best Regards, Thorsten.

At page #4 you can see, that BYPASS SELECT and PRESET SELECT are digital inputs with pull-up connected to 5V If you configure one of the J10 ports as output in open drain mode, it could be directly connected to pin 3 and 4, and Vs (ground) to pin 1 of HDR2 The MIDIbox NG firmware doesn't allow to switch between push-pull mode and open-drain yet, but I planned to provide this option anyhow. :) Page #6 shows, how the RESET# is generated, actually it's via open drain (resp. open collector) as well. This RESET# goes to U20 where also the buttons are connected. But I fear that it will not only reset the button logic, but also the DSP. Don't know what this means. You could try this out by (shortly) connecting pin 10 of U20 to ground - does this reset the entire device? Any noticeable effect in the audio path? Best Regards, Thorsten.

Hi Tom, fortunately I also implemented the inverted option for EVENT_LED (I had the same use case in mind :) For bulk-assignments, I've actually another idea: the possibility to set "attributes" from a .NGR script, and to provide some kind of iterator, such as "set_attribute BUTTON:{1-256} inverted 1" But it will take some time until this will be available, because it requires some parser extensions. Best Regards, Thorsten.

Using laser cut (e.g. from formulor) was my first idea. There might be some other parts (e.g. LCD/OLED frames) which could be part of the panel as well. Good idea to use multiple PCBs for the frontpanel. Best Regards, Thorsten.

Most simple entry point would be the MBHP_CORE_STM32F4 module running with the MIDIbox NG firmware. No DIN or DOUT module required, you could connect reed relays and buttons directly to J10A/B, configured as digital in- and outputs. If the vocoder has some kind of "reset" for the program button, it would be easy to setup a .NGR script which issues the reset, and then sends pulses depending on the desired program number. But the documentation doesn't give enough info how a reset could be triggered. Best Regards, Thorsten.

No, it isn't like modern kits. The project has been created 10 years ago and was intended to be built into a 19" case with a large display and many menu selection buttons + soft function encoders. Smaller variants (such as sammichFM) are more difficult to use, actually it's better to edit sounds with the CTRL editor for these devices. Best Regards, Thorsten.

I can send you a pre-programmed chip if it isn't so urgent (in 2..3 weeks) Actually I planned to re-establish this "PIC programming service" again anyhow, since there aren't so many PIC users anymore, which means that this doesn't result into too much effort at my side. Best Regards, Thorsten.

This is a typo, the AOUT interface should be in MBSEQ_GC.V4 (and not MBSEQ_CV.V4) file. However, you don't edit this file directly, instead this file just stores the values that you changed in the CV configuration page. Gates are configured in MBSEQ_HW.V4 You've to ensure that the 3rd SR isn't assigned to any other function which could overlay the gate. Typical errors if the CV interface isn't working: no proper connection via J19, e.g. swapped signal linestoo long cable between core and AOUT(_NG) module (max. 20 cm)soldering errorswrong track configuration (-> see http://www.ucapps.de/midibox_seq_manual_m.html search for AOUT port)wrong CV configuration Most simple way to check the communication between core and AOUT_NG: Enter the CV configuration page, select the right module (AOUT_NG), set Calibr.(ation) value to 1V, 2V, 4V, 8V You should notice that the selected CV output should change it's voltage. If this works, you know that the MIDI track configuration doesn't select the right AOUT port and channel. Most simple way to check if gates are working: Set "J5_ENABLED 1" in the MBSEQ_HW.V4 file, and connect a LED via 220 Ohm resistor between Vs (GND) and J5A.A0 to check if the gate is working with this pin. If yes, do the same with the SR that you selected with CV_GATE_SR1 Note that the first gate is located at D7 (not D0) output pin! If this test isn't working, then your MIDI track configuration doesn't select the right AOUT port and channel. Best Regards, Thorsten.

For the records: Christian and I worked out a calibration mode which is now available in the repository. More details about the calibration procedure at the MBKB webpage soon. Best Regards, Thorsten.

Currently I can't check each reported issue immediately - too many requests at once which have to be prioritized - but I will come back to this topic soon. Added to the wishlist to check this (so that it doesn't get lost) Best Regards, Thorsten.

Try: set_min AIN:1 KB:1This will transfer the current value of KB:1 (the key number) to the min value of AIN:1 or use an encoder for this purpose - very similar: set_min AIN:1 ENC:1Best Regards, Thorsten.