TK.

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.

In MBSEQ V3, I'm using 6 characters to display the chord name: ;; 1 2 3 4 <----> (6 chars!) CHORD_ENTRY 0, 4, 7, -1, "Maj.I " CHORD_ENTRY 4, 7, 12, -1, "Maj.II" CHORD_ENTRY 7, 12, 16, -1, "MajIII" CHORD_ENTRY 0, -1, -1, -1, "Root " CHORD_ENTRY 4, -1, -1, -1, "3rd " CHORD_ENTRY 7, -1, -1, -1, "5th " CHORD_ENTRY 0, 4, -1, -1, "R.+3rd" CHORD_ENTRY 0, 7, -1, -1, "R.+5th" CHORD_ENTRY 0, 4, 7, 9, "Maj.6 " CHORD_ENTRY 0, 4, 7, 11, "Maj.7 " CHORD_ENTRY 0, 4, 7, 12, "Maj.8 " CHORD_ENTRY 0, 4, 7, 14, "Maj.9 " CHORD_ENTRY 0, 7, 12, 16, "Maj.10" CHORD_ENTRY 0, 7, 12, 19, "Maj.12" CHORD_ENTRY 0, 5, 7, -1, "Sus.4 " CHORD_ENTRY 0, 4, 8, -1, "Maj.+ " [/code] Best Regards, Thorsten.

Hi Antony, I'm not sure in which source code you are searching, but normaly main.asm (or main.c if it is a C application) is a good starting point. For the case you don't know it: here is an explanation for the MIDI protocol: http://www.midibox.org/dokuwiki/doku.php?id=midi_specification And some programming examples for C are located here - they help to understand the basic concepts of MIOS: http://www.ucapps.de/mios_c.html Best Regards, Thorsten.

I just have added following text: Addendum to Event Mode 2: a second track is used as chord memory. Each step of this track stores a 3-note chord in Layer A/B/C, which can be triggered from the track which is running in event mode 2 (select S1..S32 for step 1..32 of the chord memory). The chord memory track can either be located in the same, or in a different pattern. This means, it is possible to define the chords globally for multiple tracks, and to change them independent from the other patterns. For correct visualisation, the chord memory track should be configured for event mode 4 (Note/Note/Note), and track mode should be "off" (-> Track Mode page), so that the notes are not played. Best Regards, Thorsten.

Nein, das ist nicht vorgesehen. Gruss, Thorsten.

No, this is not possible. Generating PWM with an adequate resolution is one of the most CPU intensive tasks you can think of. Therefore most microcontrollers provide special timer peripherals, which are doing this in parallel to the CPU. The PIC18F4620 has an integrated timer which can generate two independent PWM, but the timers and IO pins are already allocated for other functions. Btw.: I'm very busy with a lot of other stuff and I'm especially not searching for programming tasks. My motivation to spend my sparetime with implementing alternative solutions for people who want to save some EUR is very low... just consider this when asking questions which are starting with "do you think it is possible" and ending with "but I'm no programmer" ;) Best Regards, Thorsten.

Ich habe auf der MIDI Config Seite die Split Funktion aktiviert. Mit der linken Hand steuere ich den Transposer, mit der rechten den Arpeggiator Gruss, Thorsten.

How does it change when you remove the 4 bridges to the CLK pins of the 74HC165s? And when you connect them again step by step? Maybe this helps to narrow down the problem Best Regards, Thorsten.

The start/stop pin is implemented now. If somebody wants to test this before the next release, just drop me a mail Best Regards, Thorsten.