TK.

Perfect, this demonstrates that the "fail save" protection is working! :) From the ChangeLog: o this version *REQUIRES* a PIC18F4620, it won't run on a PIC18F452 ! o there is now a check during the initialisation for the PIC derivative. Execution from any other PIC than PIC18F4620 is gracefully prevented. You will see a message on screen, and a MIDI event "EE <devid[2:0]> <devid2[9:3]> is sent to notify about the wrong PIC [/code] Best Regards, Thorsten.

If you are planning to create a frontpanel for your MIDIbox SID V2 ("Step A", "B" or "C" stage), please consider that the purpose of the Link/CC and Edit button has been changed. This mainly affects the labling the LINK button will get the purpose of a SHIFT button. In addition, it displays a special configuration page, which for example allows you to switch between left and right SID channel the CC button is used for "Page Up" (increments OSC/LFO/ENV/MOD/TRG/KNB) the Edit button is used for "Page Down" (decrements OSC/LFO/ENV/MOD/TRG/KNB) SHIFT+CC and SHIFT+EDIT still switch the CC/Edit function like before - this means: the two LED labels are still valid! in the OSC section, the "Arpeggiator" label should be renamed to "Phase" The Page Up/Down buttons are just a new feature which save you from scrolling to the left end of a menu page in order to select a different oscillator/LFO/ENV/... etc A MBSID with the minimal "Step A" control surface still allows full access to all parameters, but adding a Shift/Page Up/Down button is strongly recommented for faster usage Best Regards, Thorsten.

Danke! :) Ich denke, dass Du so etwas wie die MIDIO128 suchst, mit dieser eigentlich recht einfach gestrickten Applikation lassen sich bis zu 128 Taster und 128 LEDs betreiben. Hardwaremaessig benoetigst Du ein Core Modul, sowie die entspr. Anzahl an DINX4/DOUTX4 Module (maximal 4, jedes Modul bietet 32 Eingaenge, bzw. 32 Ausgaenge) Die LEDs koennen dann von der Host Applikation angesteuert werden (jede LED reagiert per default auf das gleiche MIDI Event, das auch von dem entspr. Taster gesendet wird. Auf Wunsch kann man auch verschiedene MIDI Events hernehmen) Taster: sollte funktionieren, ich wuerde jedoch empfehlen, vor der Grossbestellung erstmal drei oder vier verschiedene Exemplare zu bestellen, und dann das auszuwaehlen, welches Dir (bspw. vom "Klickgefuehl" her) am besten gefaellt. Gruss, Thorsten.

Kann es sein, dass das Display eine negative Spannung an V0 benoetigt? Im Kapitel 5.3 des Datasheets faellt V0 verdaechtig von 0V nach unten Gruss, Thorsten.

Thats ok, according to the datasheets the PIC can be supplied with up to 5.5V, and for the OPL3/YAC I think it's similar Best Regards, Thorsten.

Hi, the Rx pin has a pull-up resistor to +5V, accordingly you should read +5V so long no MIDI data is received (you can doublecheck this by temporary removing the optocoupler) So, it's very likely that there is a problem with the power tracks at the right side of the core PCB With your multimeter you can follow these tracks to locate a crack, a bad connection or something similar - once the voltage turns from 5V to 0V, you know, where it is Best Regards, Thorsten.

The upload was totally successfully, because there are 32 positive acknowledges (32k), and one additional error response, which propably comes from a recorded "dummy upload request", which will be sent by the core after a reset. You could remove this last upload request from the SysEx dump Best Regards, Thorsten.

Hi, renaming a .syx file to .hex won't work, the content is totally different (binary vs. ASCII format) You could try the upload via MIDI-Ox, see http://www.ucapps.de/howto_tools_hex2syx.html (the MIDI-Ox part, not the hex->syx conversion part) this won't work Best Regards, Thorsten.

No problem - I'm currently working on a similar "Auto Slave" mode for MBSID V2. Once I got enough experience, I will add this to MBSEQ V3 as well. Best Regards, Thorsten.

Hallo, es ist sehr unwahrscheinlich, dass der PIC nicht wiederzubeleben ist. Ich kenne den Elektor Brenner nicht, aber vielleicht hat er den Config Sektor entweder falsch, oder gar nicht programmiert? Hier wird bspw. die Clockoption eingestellt (sollte auf HSPLL stehen) Die Flags stehen eigentlich im .hex File, aber manche Programme lesen diese Information nicht ein, so dass man manuell Konfigurieren muss. Die Flags findest Du auch unter bootloader/main.asm im MIOS Source Package Gruss, Thorsten.

Siehst Du einen schwarzen Balken? Falls nicht, ist evtl. der Contrast falsch eingestellt. Zum Testen der Verbindungen zum LCD gibt es uebrigens eine spezielle Applikation auf der MIOS Download Seite: lcd_interconnection_test_v1 Gruss, Thorsten.

Ich verwende die XLR Stecker/Buchsen ebenfalls fuer diesen Zweck - vor allem fuer bipolare Spannungen gibt es nichts praktischeres! :) Gruss, Thorsten.

yes, this is the right location for sync to 4/4 measure Best Regards, Thorsten.

Great! :) Best Regards, Thorsten.

There are error messages (...0E 01 xx F7) which indicate, that less bytes than expected have been received. Some other messages (...0F xx F7) indicate a correct upload So it seems, that you are not using a SysEx tool which allows to add a delay between two SysEx blocks - the delay should be ca. 600 mS (I think this was the worst case) For MAC you can use the SysEx Librarian, see http://www.ucapps.de/howto_tools_mbsyx.html It's normal, that after a BankStick dump or upload the core will be reset, this is no error Best Regards, Thorsten.

Hi Hans, it seems that your PIC is running with the old bootloader, which was located at 0x7c00-0x7fff Just upload the pic18f452/midi/update_with_old_mios.hex file of the mios_update_v1_9d package This will install the new bootloader and a new MIOS version. Best Regards, Thorsten.

Yes, it sounds like a feedback. What happens when you disconnect the cable on the MIDI In port, do you still get so many upload requests? Best Regards, Thorsten.

No, currently it isn't possible to change a pattern or a song via MIDI. Integrating such a feature is easy, but I'm still unsure about the best solution (e.g. if CCs or Program Changes over different MIDI channels are better...) The advantage of a Program Change Event is, that PC/Mac based sequencers are (mostly) sending them before a new measure starts, so that the next note will already play the newly selected sound (or for MBSEQ: that the right pattern/song is selected on time) - this is perfect! But disadvantage: there is only one program change possible per MIDI channel. This would break up the "single MIDI channel" approach for controlling MBSEQ CCs have the advantage, that there are 128 numbers free per MIDI channel, enough for switching 4 patterns and one song parameter. But only a small number of PC/Mac based sequencers allow to apply a negative delay to the track which sends the CCs (Logic allows this, not sure about other sequencers...) However, here a quick solution for switching Songs via Program Change over any MIDI channel. It has to be inserted into seq_midi.inc (search for SEQ_MIDI_ProgramChange, and add the following) SEQ_MIDI_ProgramChange SET_BSR SEQ_BASE movf SEQ_SONG, W, BANKED andlw 0x80 iorwf MIOS_PARAMETER2, W movwf SEQ_SONG, BANKED return [/code] Best Regards, Thorsten.

MIDIbox SEQ V3.1 can now be downloaded from http://www.ucapps.de/mios_download.html Changes are documented here: http://www.ucapps.de/midibox_seq_changelog.html Special thanks to Whomper for reporting issues and testing bugfixes! Best Regards, Thorsten.

I will integrate the driver into the MBSID V2 application if really so many LCDs are affected Best Regards, Thorsten.

Yes, thats the way how the modules should be "daisychained". See also http://www.ucapps.de/midibox_sid_cs/mbsid_din_default.pdf as an example Best Regards, Thorsten.

See the updated http://www.ucapps.de/mios/mios_backup.txt Best Regards, Thorsten.

Hi, in one of your earlier posts you wrote, that the 2x16 was working. Do you remember, what you've changed until then? 2x40 LCD: take care for the pinning. The WM-C4002P datasheet contains a table with the "interface pin connections", where pins are counted from 1..8, 9..16 in two lines (horizontally) - but this doesn't match with the physical layout. The correct pin layout can be seen in the graphical representation (which also describes the dimensions). From the upper left to the lower right pin it counts: 16, 15, 14, 13, 12, 11, ... 2, 1 Best Regards, Thorsten.

The remaining "step offset" issue is related to the way, how MBSEQ calculates the step positions based on the incoming song pointer, which is sent by Logic. It cannot be 100% accurate, since the song mode of MBSEQ works with 1 measure (16 step) resolution, and the track lengths can vary from 1..32 steps. This means for example: if your song consists of 1: 1 x A1 2: 2 x A2 where A1 and A2 is a 32 step pattern, the song position will be calculated correctly for the first measure, for the second measure the sequencer will start at A2, step 17, and for the third measure the sequencer will start at A2, step 1 This might be an unexpected behaviour, but there is no proper solution for this Only workaround is to ensure, that a song always uses "even loops" (2x, 4x, 6x, ...) when it plays 32 step tracks. The initial position of tracks with != 16 steps where not calculated correctly in v3_1rc1, but I improved this in v3_1rc2 But I fear that this is all what I can do http://www.ucapps.de/tmp/midibox_seq_v3_1_rc2.zip SysEx dump (load/save) issue: the format has been changed, the bankstick is now selected with the 7th byte of the SysEx request. This is documented in the updated http://www.ucapps.de/mios/mios_backup.txt The example in CHANGELOG.txt is working, this is what I tried out yesterday Best Regards, Thorsten.

v1.74685 is available now, see news section for details Best Regards, Thorsten.