TK.

Yes, the only way is to add a second core module Best Regards, Thorsten.

Only one setup is stored within the internal EEPROM. BankSticks are not supported, only SysEx dump exchange. But it could be easily added, as storage accesses are already isolated in cv_bank.inc I think that all the imperfections in the handling make clear, that MBCV was only a quick hack I made for a friend. I don't use the MIDIbox CV by myself - the user interface would look really different if this would be the case. For example, I would replace the "select" button by two buttons for CV up/down. Cycling through the CV is very time consuming, I don't really like this handling (it was made to stay compatible to the MB64/MB64E menu navigation - but there is no real reason for doing it always the same way) Also the possibility to store multiple setups is an important point. Another missing but useful feature is the possibility to activate an interpolation for incoming 7bit CCs (it's like an envelope follower) to avoid steppiness and to get use of the full 12bit resolution. Best Regards, Thorsten.

Which faders are you using? The same issue exists for Mackie Control, but the reason is not the software, but the quality of the P&G motorfaders. The root cause is propably, that the resistance is not 100% linear over the travel. Addendum: ok, seems that you mean another issue - that the host software sets the motorfader to different positions for 0dB. I'm not aware of such an issue, but I'm a logic user ;) Best Regards, Thorsten.

Thank you very much, it's very nice to read, and a good basis for writing down new findings if required. On my homepage, I've replaced the PSU links by a link to the Wiki. I've also fixed some minor typos (the short name of capacitors is "cap") - thats the big advantage of the Wiki btw., errors can be easily corrected, extensions can be easily added by anybody. :) Best Regards, Thorsten.

Hi vattern, it looks like the wrong MIDI baudrate is selected. Maybe the ID header hasn't been programmed, or some bytes are swapped (see also http://www.midibox.org/dokuwiki/doku.php?id=jdm_with_winpic800) An "all-zero" ID is a save value Best Regards, Thorsten.

-> see http://www.ucapps.de/midibox_seq_changelog.html Have fun! :) Best Regards, Thorsten. P.S.: this release is intended as last release before I focus on MBSID V2. The TODO list is empty, and it can take a couple of months before I can consider new feature requests again.

(I'm currently extremely busy and therefore haven't answered to your PM yet) Some months ago I got a special request to specify +/- 12V instead of +/- 15V in the schematic, since transformers with +/-15V voltage range normaly output +/-18V effective voltage and higher when they are not loaded. And since (or even?) the OP amps don't load the circuit that much, the 7812/7912 got very hot. However, I see your point, and I think that a clear documentation is required here. Would you like to start a new Wiki page? Also a description (and schematic) of the one way rectifier circuit would be nice. (I never found the time to write down the details for all the variants, and I still think it makes sense that Users maintain such topics) Best Regards, Thorsten.

I like the PCD8544 because of the performance (see http://www.midibox.org/forum/index.php?topic=2169.0) and the possibility to service multiple displays from the LCD port of the core module (thanks to the serial lines) Best Regards, Thorsten.

Nice chip, and it's even available at Reichelt! For applications which need to update the digits very often, there isn't really a benefit for the CPU load - quite the contrary: two MIOS_DOUT_SRSet take much less cycles than doing external IIC transfers. Yes, they have to be done periodically, so it has to be estimated depending on the update period if it improves or worsens the performance. In general I would say: the impact can be ignored. But it is a flexible solution which can be added even when the core already services 16 DOUT registers. And the wiring is less complex. Thanks for the hint! Best Regards, Thorsten. P.S.: I've already added the DOUT based BPM digit driver into MBSEQ V3.2, so if somebody reads about this in the MBSEQ hardware page, don't mix it with this solution.

MIOS V1.9e is available for download: http://www.ucapps.de/mios/mios_update_v1_9e.zip This is a "service pack" release, an update is recommented for MIDIO128, MIDIbox SID V2 and MIDIbox SEQ V3 users (see also http://www.midibox.org/forum/index.php?topic=9271.0) ChangeLog: o priority of MIDI Rx Handler changed (now it has the highest priority) o MIOS_HLP_GetIndex_2bytes now takes the 64k boundary into account (only relevant for PIC18F4685 and PIC18F4682) o debouncing was skipped (or DIN toggles were ignored) if BSR was modified within the USER_SR_Service_Finish hook o download request for 64k BankSticks (24LC512) working now [/code] Best Regards, Thorsten.

There are two possible reasons for such a failure a) what kind of SysEx are you sending? Maybe it's a command which requires a certain recovery time, before the DB50XG can receive notes again? You can test this with MIDI-Ox: open the SysEx window, enter "90 30 7F" (for Note On), add the SysEx string (160 bytes), and add "90 30 00" (Note Off) If the note is still played, then you know that this is a DB50XG issue (try also multiple notes, e.g. "90 31 7F 32 7F 33 7F" for three Note On, and "90 31 00 32 00 33 00" for three Note Off) b) you are sending so many MIDI events through the core, that a MIDI In buffer overrun does happen within MIOS. The input buffer has a size of 64 bytes. Since more bytes are sent in a stream (160 bytes) than data can be forwarded, incoming data can get lost (bottleneck problem) Best Regards, Thorsten.

No, the assign layers have predefined functions which you don't want to miss. See the V2 user manual But if you mean internal SID parameters with "predefined NRPNs": then read the "KNoBs" section of the v2 user manual Alternative functions are not planned. Best Regards, Thorsten.

Yes, you have to assign different MIDI channels to the MIDI outputs. This can be done with the mk_midio128_syx script Monitoring would only be possible if you would use DINs which are directly connected to the DOUTs. In addition, a special software would be required which is able to request the DIN values, and to compare them with the DOUT values. I don't know which software is ideal for your plans, but I guess that any MIDI sequencer could be used. Best Regards, Thorsten.

Hi, I just found a very ugly bug in the overworked debounce handler, which exists since MIOS V1.9c - after a "call USER_SR_Service_Finish" I forgot to change the register bank before checking a variable which is realted to debouncing. It can happen - depending on the code within USER_SR_Service_Finish", that changes on digital inputs will be ignored. I think it could be useful to inform you before you are starting endless troubleshooting. A new MIOS version will be released soon. I did some quick checks in following applications: MIDIbox SEQ V3 (where I found it): DINs disabled if more than 8 keys are played on a MIDI keyboard (note stack overrides debounce counter) MIDIbox SEQ V2: not affected (no BSR change) MIDIbox SID V1: not affected (no BSR change) MIDIbox SID V2: not affected (no BSR change) MIDIbox FM: not affected (no BSR change) MIDIbox64/64E: not affected (no BSR change) MIDIO128: bug disables debouncing, no other effect MIDIbox LC: not affected (no BSR change) MIDIbox CV: not affected (no BSR change) your own applications: please check if USER_SR_Service_Finish is used. Workaround: add "SET_BSR 0x500" before return Best Regards, Thorsten.

The engine reference is stored within the patch. By selecting a drum patch, you will automatically select the drum engine, by selecting a lead patch, you will automatically select the lead engine, etc... Best Regards, Thorsten.

No, the number of available MIOS IDs is 128 (00..7F) Best Regards, Thorsten.

I'm using these 22nF caps: http://www.midibox.org/forum/index.php?topic=9132.msg64907#msg64907 Best Regards, Thorsten.

Fotos -> tk@midibox.org Austauschen des SIDs: Du muesstest lediglich den Stabi austauschen (7812 gegen 7809). Den 8580 NIEMALS mit Spannungen >9.5V betreiben! Die Kondensatoren koennen erstmal so bleiben. Vielleicht funktioniert der/die/das Filter dann nicht richtig, aber Du solltest zumindest die Oszillatoren hoeren. Gruss, Thorsten.

Yes, you need an additional DIN (so: DINX2 instead of DINX1, but I guess that you will use a DINX4 anyhow?) DOUT is not required for a "Step A" CS Best Regards, Thorsten.

Hi, according to the MIDI spec, the maximum cable length is 50 feet (see http://www.midi.org/about-midi/electrical.shtml) If this is not long enough, it makes sense to get use of the RS422 approach (bipolar Rx/Tx line). There are converter chips available, e.g. from Maxim: MAX489E, which should work, but I never tried this chip by myself... Best Regards, Thorsten.

Hallo, ich weiss ja nicht, ob es wirklich so gesund fuer die Kiste ist, wenn man die Signalleitungen kurzschliesst... erinnert mich irgendwie an meinen guten alten C128. Vor Urzeiten (als unbedarfter Teenager) habe ich mal unabsichtlich die +5V Leitung mit A12 vertauscht, das hat saemtliche Chips am Datenbus in Mitleidenschaft gezogen. Ich wuerde versuchen, das digital zu loesen. Doch fuer eine flexible Loesung (AND/OR/XOR Verbindungen in einer 40x40 Matrix) muesste es schon ein FPGA sein... Also zurueck zur Kamikaze-Loesung: www.spezial.de ist der deutsche Distributor fuer Maxim ICs Gruss, Thorsten.

Yes, this is possible, and I've changed the description (replaced "channel" by "CV output" as the term "channel" seems to be misleading in this context) Best Regards, Thorsten.

It's time to welcome a new MIDIbox64 based controller! :) This big one has been made by Phil aka. Quercus. He wrote:

Hast Du beachtet, dass sich vor einiger Zeit das Pinning zwischen dem SID und dem Core Modul geaendert hat? Am besten vergleichst Du das nochmal mit den aktuellen Schaltplaenen. Gruss, Thorsten.

Since you are searching for any hints: I think it's better to do such modifications in the C based version, it's easier to understand: http://www.ucapps.de/mios/midibox_lc_v2_0_alpha1.zip the display output routines are located in lc_lcd.c Best Regards, Thorsten.