TK.

Hi Dan, yes, time to start with the most pleasant part :-) Do you still know the reason why the slaves didn't work correctly, or was it just the result after a lot of different changes? Best Regards, Thorsten.

I guess that the crystal is ok ("for use with microprocessors" sounds good and the capacity is also within the range). Just to ensure: a LED has a polarity - does it light up when you connect it between ground and any +5V pin of the PIC? It's also important that the MIDI-Out is not connected with the MIDI-In of your PC during the test. If this is the case --- if the LED doesn't light up when connected to the Tx pin, the PIC isn't running. Which PCB are you using? The one with the crystal at the bottom side or the improved PCB by SmashTV where the crystal is beside of the PIC? You've to ensure that the metal case of the crystal doesn't get in contact with the tracks... Best Regards, Thorsten.

MIOS doesn't reboot so long as MIDI events are received - every time a MIDI device sends some notes/controllers/sysex strings to the core, the handler will wait at least 2-3 seconds before rebooting. Only realtime events (like MIDI clock or Active Sense) will be ignored. Could you please check if this was the reason? Best Regards, Thorsten.

Farnell is one of the most expensive distributors, maybe it's better to order the parts from a scandinavian shop - see also this article: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=scandinavian;action=display;num=1048720464 Some words to the resolution: it depends on the application which encoders are the best for you. In the meantime I prefer a reduced resolution for MIDIbox SID so that I'm able to change the values more precisely. The progressive mode (Speed Setting) still allows to sweep over the full range with a single turn. Pay_c: you possibly have to change the CS_MENU_ENC_SPEED_VALUE in main.asm for a higher acceleration on fast turns. Best Regards, Thorsten.

Hi LO, 15V at SID::J1 are recommented for the 6581 12V at SID::J1 for the 8580 in a mixed setup use 15V for both Best Regards, Thorsten.

V1.5b has been released PIC16F877 version: http://www.ucapps.de/midibox_sid/midibox_sid_v1_5b.zip Correct saturation when more than 2 modulation sources are assigned to Pitch/PWM PIC18F452 version: http://www.ucapps.de/mios/midibox_sid_v1_5b_18f_stepC.zip Same bugfix like above plus minor bugfixes for the control surface (e.g. WT editor displayed relative values in the wrong format). Minor Improvements: by default the OSC button now switches between the 3 oscillators and doesn't switch between combined modes anymore (e.g. OSC 123) for a faster handling. If parameter changes should take place for more than one oscillator, just select the appr. combination in the menu. This button behaviour can be alternated to the old solution in main.asm (set CS_MENU_OSC_BUTTON_BEHAVIOUR to 0) Rotary Encoders: CS_MENU_ENC_SPEED_VALUE allows to define the speed setting for encoder #2-#15. Although I'm using non-detented encoders, I prefer following setup: encoders in MIOS_ENC_MODE_DETENTED2 mode (reduces the resolution), CS_MENU_ENC_SPEED_VALUE set to 3 (by moving the encoder faster, you can sweep over the whole value range) The best setup depends on the used encoder, just try different settings. I've tested the firmware by creating a new demo song - maybe the best I ever made with the MIDIbox SID :D The result will be downloadable in the next days so soon as the storage server problem has been fixed. Best Regards, Thorsten.

They appear as "Audiodevice 1", "Audiodevice 2", "Audiodevice[2] 1", "Audiodevice[2] 2", ... etc. Best Regards, Thorsten.

Falsch - MIOS bietet wesentlich mehr Features als die MIDIbox64/MIDIbox16E/MIDIO128 Firmwares, es gibt bereits Demo-Applikationen mit denen man einiges anfangen kann, es gibt sogar Applikationen die ueber die Funktionalitaeten der PIC16F Firmwares hinaus gehen (MIDIbox LC, MIDIbox HN, MIDIbox SID...). Was fehlt sind Applikationen die mit dem Editor kompatibel sind, aber fuer mich ist das ein low-priority Task. Gruss, Thorsten.

The instructions are for the bootstrap loader, all precompiled .hex files for the PIC16F are not working with a PIC18F. So, for the PIC18F the strategy is to get the bootstraploader running first. Once it works, you don't need the JDM anymore. Thereafter upload the operating system (MIOS V1.3) via MIDI - also this has only to be done once. Thereafter try some MIOS applications. Best Regards, Thorsten.

I've 3 MBHP_USB modules running on a USB hub and no idea how to measure the additional latency. I guess that it is ignorable compared to the delay caused by the USB midi protocol itself (1 ms). Best Regards, Thorsten.

Please try the following: use the PIC18F452 (you wrote that IC-Prog verify passed...) use a 10 MHz crystal ensure that C1 and C2 is 33pF (pico-farad) plug the 5 jumpers into the J3 socket connect a LED+220 Ohm resistor between the Tx pin of the PIC and ground. Cathode (the short leg) connected to ground the LED should lit at power on. if MIOS has not been uploaded yet, it should flicker every 2 seconds disconnect the LED and try to upload the operating system. If this doesn't work, check the MIDI In port like descriped here: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1055726526 disconnect the LED after the test and try the upload again Most important: so long as MIOS has not been uploaded correctly, the LCD will not be initialized! Best Regards, Thorsten.

Hallo, der PIC18F ist leider nicht binaer-kompatibel zum PIC16F, die alten .hex files werden also nicht laufen, und die Firmware laesst sich leider nicht auf Knopfdruck fuer den PIC18F kompilieren (ein paar Assemblerbefehle haben sich geaendert). However, eine Portierung auf MIOS ist geplant, ich kann allerdings nicht sagen, wie lange es noch dauern wird (bei dem derzeitigen Wetter macht es einfach keinen Spass, am Rechner zu sitzen...) Gruss, Thorsten.

Hi Steve, this would be really helpfull! :) Some infos to LEDrings and encoder settings: buttons are "shadowed" by the encoder pins. Means: once you've assigned two pins to an encoder in mios_tables.inc, these pins will not trigger a button function anymore, therefore the appr. button entries in lc_io_tables.inc will never be processed. digital output pins are "shadowed" by LEDring assignments. Means: the shift registers for anodes/cathodes which are assigned to the LEDring handler cannot be used for common LED functions defined in lc_io_tables.inc, since the handler overwrite the values every milisecond Best Regards, Thorsten. FAQMARKER

One user noticed a similar problem after he checked the solderings of the MIDI In circuit, the reason was that he forgot to disconnect the LED, which is only used for debugging purposes and consumes so much power that the PIC doesn't receive any MIDI data. Best Regards, Thorsten.

Hi Steve, Pin 19 drives a high frequency signal, it's not possible to measure a meaningfull value there, only a scope would help to make the waveform visible. However, the easiest method to search for the error should be to disconnect the modules and connect every DINX4 and DOUTX4 again successively. Best Regards, Thorsten.

Hi Ilmenator, ..so, this means that you found the reason for your problems? No, MIOS doesn't provide a feedback detection. It's only a minor feature which allocates some RAM and causes more problems when it solves (especially in combination with a MIDIbox Link to another core module). Best Regards, thorsten.

Hi, I've updated the SID page with some more basic informations about the possible hardware configurations. Hope that it isn't so confusing anymore. Best Regards, Thorsten.

Hi Justin, both is correct. The mute function is intented to temporary mute some steps during a live session. And they control all tracks at the same time. Notes (e.g. for drums) can be disabled by setting the velocity or note number to zero. Thats the way I like it ;-) However, the MIOS based version could provide some more configurable options especially for different workflows. Best Regards, Thorsten.

Hi, LO: you see the new settings since I've updated the v1.5 archive with the new source Btw.: in the next days I will release v1.5b which comes with an important bugfix in the sound engine (saturation doesn't work properly when more than 2 LFOs/envelopes are assigned to a target), and some minor bugfixes and improvements for the control unit. In the meantime I also changed the encoder configuration of my own MIDIbox. Now the encoders are running in "DETENTED2" mode (one increment every 4 edges) and not with the quadrubled resolution anymore although I'm using non-detented encoders. The speed mode is configured to "FAST", factor 3 In this way I'm able to modify the values very precisely when the encoder is moved slowly. And due to the high acceleration settings, I'm still able to sweep from 0 to the max value with a single, fast turn. Best Regards, Thorsten.

Yes, you can place the meter LEDs anywhere - damned! thats the problem when the application allows too much options - how to answer a simple question with one sentence when so much variations are possible? :-( You see: under these circumstances the LC documentation will never be finished... ;-) Best Regards, thorsten.

...and is there also a #include "app_lcd.inc" in the main.asm file? Best Regards, Thorsten.

it looks like a problem with the shift clock (the SC line which goes to all 74HC165 CLK inputs) - if this signal isn't available, the first register will switch all 128 input functions at the same time. Best Regards, Thorsten.

Hi Ilmenator, FD45 is the correct checksum of the current MIOS version, so the OS is complete. You could change following lines: ;; use 64 pots movlw 64 call MIOS_AIN_NumberSet ;; use the AIN 4051 multiplexers call MIOS_AIN_Muxed to ;; use no pots movlw 0 call MIOS_AIN_NumberSet in order to disable the analog inputs. it's very strange that the PIC is not rebooted after the upload. Are you receiving acknowledge messages during the transfer? Best Regards, Thorsten.

Alright, so this issue has been clarified ;-) Best Regards, Thorsten.

Hi Ian, the data structure of the SIDstation has been published in the manual, so in theory it should work with a simple conversion script. However, due to the different sound engines the results will not be the same. But it would be a nice possibility to increase the number of patches - I will try this sooner or later ;-) Best Regards, Thorsten.