Back to main page...
MIDIbox SID V2
Known Issues and Troubleshooting Tips
This is a "living document", which will be extended from time to time whenever a "strange behaviour" has been reported by a user which could be interesting for other people, not at least for troubleshooting an apparently non-functional MIDIbox SID.
-  PIC not starting, no MIDI output/input, code upload not possible, etc...
Please follow this Troubleshooting Guide
-  Blank screen
LCD won't be initialized so long MIOS hasn't been uploaded via MIOS Bootstrap Loader
-  Core reboots after MIDIbox SID application has been uploaded, or it behaves randomly
- [3a] Use the latest MIOS Studio version.
- [3b] Ensure that following pull-up resistors have been mounted on the core mode (Schematic): R2, R6, R9, R10, R12 --- in general it makes sense to stuff the whole core module if you are unsure.
- [3c] Ensure that in addition the 1k pull-up and 1N4148 diode for the CAN interface has been added as shown in this schematic.
Resistor and diode are even required if no slave module is used!
- [3d] Ensure that the D0-D3 data lines of your LCD are not connected to the core module (LCD is accessed in 4bit mode to keep the ECAN Rx/Tx pins free)
-  LCD freezes immediately or after some seconds, synth still functional
A rare number of LCDs don't support 4-bit access mode properly. This has been noticed on two PLED displays and one VFD display so far, "normal" HD44780 or KS0066 LCDs are working stable. Sometimes nibbles are swapped, so that the communication with the CLCD driver of MIOS is disturbed. 4-bit mode is required, as pin RB2 and RB3 are used for the CAN interface. If you notice such an issue, you could activate the alternative "custom" LCD driver, which is already part of the MIDIbox SID V2 firmware. It uses 8-bit mode by using two pins on port E to replace the two pins being used by the CAN. LCD pins D0 and D1 should be connected to PIC pins RB0 and RB1, and LCD pins D2 and D3 connect to PIC pins RE1 and RE2. The driver can be permanently activated via PIC ID Header (LCD type 7, see also Bootloader page), or by activating the DEFAULT_USE_CUSTOM_LCD_DRIVER switch in the setup_*.asm file
-  Slave Cores not found by Master
Ensure that each slave has its own MIOS Device ID (01, 02, 03). The ID of the master core has to be 00. The ID has to be programmed into the PIC ID Header. If this hasn't been done while burning the Bootloader, you can do this also with the change_id application, which is available at the MIOS Download page.
-  Buttons/Encoders not working
Please follow this Troubleshooting Guide
-  No sound from SID
Try the mbsid_interconnection_test and sid_testtone application, which can be found at the MIOS Download page. The testing procedure is explained in the main.asm file.
Just to highlight it again: the application won't run before you've uploaded MIOS (the operating system).
The audio output of the MBHP_SID module has to be connected to a mixer or audio amplifier, a direct connection to a loudspeaker or headphones won't work.
-  Still no sound from SID
Check the MIDI channel. If you are unsure (e.g. no LCD connected to Core Module), try all 16 MIDI channels with your keyboard/sequencer
-  Background noise
Ensure that the Audio In of the MBHP_SID module is connected to ground when not used.
A certain digital background noise is common on a 6581 due to a design weakness. It's much less (-90 dB) on a 6582/8580.
Another known SID bug is the leackage issue in the VCA part (especially 6581) - the oscillators are not completely silent once a note has been played. If you are using a compressor a noise gate in the Fx chain, search for a setting which eliminates this noise
-  50 Hz or 60 Hz buzz
Consider to build an optimized PSU (Power Supply Unit) like explained in the Hardware Options chapter.
-  Some buttons or LEDs are not working
Depending on the selected sound engine, some buttons and LEDs have no function. E.g., in Multi mode, OSC and ENV is always 1, and LFO toggles between 1 and 2. The modulation matrix buttons have no function at all, and the matrix LEDs display the number of the selected instrument.
For a complete CS test, select a patch which uses the Lead engine.
-  Modulation matrix doesn't show matrix connections, but flickers strangly
It's not a bug, but a feature! ;-)
Maybe you've selected the meter mode, which displays the MOD output values (e.g. LFO and ENV output) - press two column buttons of the modulation matrix to switch back to normal display mode.
When the bassline/drum or multi engine is running, the LED matrix displays level meters instead, which allow you to monitor the voice allocation.
-  Meter display mode doesn't display MOD/level meter output of slaves.
This is not possible due to conceptional reasons - it only displays the MOD outputs of the master SID
-  Some mixed oscillator waveforms don't output a sound
Thats normal on a 6581, it works on a 6582/8580 - see also the demo samples in the Lead Engine chapter
-  Some patches of the preset banks are incomplete
Ensure that you've uploaded the .syx files with a delay of 750 mS between each SysEx string. See also the README.txt of the patches/ directory for configuration details
-  Knob values of master or slaves are changing randomly
Propably you've selected the "analog input option" (DEFAULT_J5_FUNCTION set to 1) in order to connect pots/faders/joysticks to the master, and forgot to clamp all unusued analog inputs to ground (see also auaimbctg.pdf).
Due to the cloning mechanism, which transfers the firmware of the master to the slaves, this requirement has to be considered for all core modules!
Clamping unused J5 inputs to ground is not required if DEFAULT_J5_FUNCTION is set to 0 (J5 disabled --- default!) or 2 (J5 used as digital output)
-  I haven't found a way to play a 8xSID MBSID V2 as a single polyphonic synth
A special "Super-Poly" mode is planned for a post v2.0 release - see also this article.
Update (2007-09-30): An experimental solution for 4 stereo lead voices has been implemented, see Ensemble Page.
-  I haven't found a way to synchronize the internal clock of all 4 cores
This is related to , a possibility will be provided later after some evaluations. Currently wavetable and bassline/drum sequencers can only be synched with an external MIDI clock - this works quite well, and is the preferred solution anyhow if you are planning to sync MIDIbox SID with an external sequencer.
-  Multi/Drum engine: one or more voices are not used when Multi/Drum instruments are played - why?
This is related to the enhanced voice allocation algorithm - check the VAs settings in the CFG/DRM menu page. If one or more instruments are explicit assigned to O1..O6, the appr. voice cannot be allocated by the remaining instruments anymore (there is only one exception: if all voices are assigned to specific oscillators in drum mode, the "exclusive reservation" will be ignored).
This approach is important for a static filter or sync/ringmodulation routing, and therefore no bug.
The VAs (Voice Assignment) setting can be found in the CFG (multi engine) or DRM (Drum Engine) menu. It can be easily overlooked when doing modifications on patches from other users.
Tip: if you own a MIDIbox SID with LED matrix, enable the level metering mode to monitor the voice allocation (works for Multi and Drum engine, when the patch is played on the master core SID1)
-  An envelope doesn't sweep through the whole value range: yes, this is true if only the ENV depth is set to maximum level (+127). With the default configuration of the modulation matrix, this will result into a quarter of the available value range.
E.g. if the filter cutoff is set to 0, ENV depth set to 127, the filter will only sweep between 0%..25%. Same for volume.
In order to sweep through the whole range, the modulation path parameters have to be changed:
As the result, you will get an envelope which sweeps through the whole value range from 0% to 100%
- enter the MOD page
- select MOD 1 (if not already done) for EG1
- you will notice, that EG1 is only assigned to Sr1 - assign it also to Sr2, and ensure that the "1+2" operator is selected
-> this will double the ENV level
- in addition, set the Depth parameter of the modulation path to 127
-> this will double the MP level
-  The AOUT channel is always at maximum level when the V2A option is used: because the volume parameter in the CFG page sets the offset for this AOUT routing option. Change the volume to 0, so that the AOUT channel offset starts at 0V (similar to CutOff).
Note that with V2A enabled, the SID volume will be automatically set to maximum and can't be influenced with the Vol parameter anymore.
Last update: 2017-05-26
Copyright © 1998-2017, Thorsten Klose. All rights reserved.