TK.

You will find following option in the OSC menu which has to be enabled for all three oscillators: GSA (Gate Stays Active): once activated, the VCA envelope won't be released anymore, resulting into a permanent sound. This allows you to control the sound volume completely with the internal, or an external filter, or with an external VCA. It's an option which allows you to overcome the infamous ADSR bug of the SID. Best Regards, Thorsten.

Hi, I've no idea why there should be a problem with the SD card under these circumstances. It isn't required to turn off the core when you insert or exchange the SD Card. What happens if you insert/remove it multiple times while the application is running. Do you get additional error messages in the MIOS Terminal? And what is the output of the "sdcard" command when you enter it into the terminal? Best Regards, Thorsten.

yes, but this shouldn't make a difference for the gate LEDs - please focus to debug this first (yes, maybe there is a problem with J19 of the core module) Best Regards, Thorsten.

Probably the missing pull-up resistor was the reason, because it can stall the CAN handler due to random events, so that only the watchdog will bring back the PIC into a controlled state by triggering a reset. That's also documented in the FAQ, see: http://www.ucapps.de/midibox_sid_manual_ki.html Best Regards, Thorsten.

I would propose to assign the buttons to Bookmarks, this gives you full flexibility (see also http://www.ucapps.de/midibox_seq_manual_m.html) Just disable the current F1..F4 assignments in your MBSEQ_HW.V4 file (can be edited with the Filebrowser in MIOS Studio). E.g. if you are using Wilba's Frontpanel with button matrix change: # Following button functions are usually assigned to Fx # buttons, or to dedicated (labeled) buttons # In Wilba's frontpanel layout: # F1 is located at SR M3 Pin 3 # F2 is located at SR M2 Pin 2 # F3 is located at SR M2 Pin 3 # F4 is located at SR M1 Pin 2 # and there are dedicated buttons for Copy/Paste/Clear/Utility/StepView # DISABLE DEFAULT ASSIGNMENTS: # SR Pin BUTTON_BOOKMARK 0 0 BUTTON_PAR_LAYER_SEL 0 0 BUTTON_TRG_LAYER_SEL 0 0 BUTTON_TRACK_SEL 0 0 And assign the SR/pin numbers to the bookmark function instead: # alternative (individual) bookmark buttons # no LEDs available! # SR Pin BUTTON_DIRECT_BOOKMARK1 M3 3 BUTTON_DIRECT_BOOKMARK2 M2 2 BUTTON_DIRECT_BOOKMARK3 M2 3 BUTTON_DIRECT_BOOKMARK4 M1 2 Use sessions! Best Regards, Thorsten.

:thumbsup:

Is it a 74HC595 or 74HCT595? A 74HCT595 wouldn't work properly. Best Regards, Thorsten.

This could be a watchdog reset caused by corrupted app upload. Do you still get error messages when you are trying to upload the application? (the upload window will notify about the number of errors) Best Regards, Thorsten.

I guess that you are mainly searching for some „blink“. Well, I consider to display animated output waveforms of the controlled parameters in future! :smile: E.g. LEDrings should be animated based on the LFO and ENV depth parameter assigned to the corresponding encoder. This was a bug (now fixed in the repository) Actually the LOAD page should search for .CV2 files, and not .MIO files Best Regards, Thorsten.

No, this would require too many changes. I don't want to overcomplicate this project. Best Regards, Thorsten.

It is implemented: J10B is used instead of J28 Pinning: J10B.D8: serial data (was J28.SDA on a MBHP_CORE_LPC17 module) J10B.D9: serial clock (was J28.SC on a MBHP_CORE_LPC17 module) J10B.D10: SR strobe (was J28.WS on a MBHP_CORE_LPC17 module) Note that these assignments are not pin-compatible to a DOUT module anymore! Best Regards, Thorsten.

The vertical row is driven by two lines which go to J15A via two transistors - a broken transistor is unlikely, check the 16 pin cable again. Best Regards, Thorsten.

Yes, the #defines are listed here: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fdoc%2Fmios32%2FMIOS32_CONFIG.txt Best Regards, Thorsten.

It's better to add #define MIOS32_DONT_USE_AIN 1 to the mios32_config.h file, this should disable the MIOS32_AIN code and calls to MIOS32_AIN driver (e.g. in main.c) completely. Best Regards, Thorsten.

The gate LEDs are a good indicator, if the Core->MAX525 communication is working or not, because an unconnected bipolar PSU or shunt won't affect this. Apparently the communication is not working, otherwise the gates would be enabled whenever a note event is played. Just to doublecheck: I guess that you are trying this example: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fcvnotes.ngc Did you change: AOUT type=AOUT_NG cs=0 num_channels=8 to: AOUT type=AOUT cs=0 num_channels=8 to select the right protocol? If yes: doublecheck the connections between AOUT module and MBHP_CORE_LPC17::J19. Best Regards, Thorsten.

Jo, dann solltest Du mal eine aktuellere MIDIbox NG Version installieren... :rolleyes: Gruss, Thorsten.

Did you consider, that for the PIC18F4685 D2 and D3 of the OPL3 board are available at Pin RE1 and RE2 of the PIC? Because RB2 and RB3 are reserved for the CAN interface. This doesn't explain why you don't see an effect at D0 and D1. But it could explain, why you noticed a difference with the PIC18F4620 Best Regards, Thorsten.

Du musst noch die MIDIbox NG Applikation aufladen. Gruss, Thorsten.

Are you able to control J15:D0..D3 on the MBHP_CORE module with the mbfm_interconnection_test when the MBHP_OPL3 module is *not* connected? Could you please do this check with PIC18F4685 and PIC18F4620? Best Regards, Thorsten.

Klar, wenn Du die MIDIbox NG Applikation verwendest, definierst Du die Pin-Belegung ja nicht in der Firmware, sondern in Deinem .NGC File. Hier muessen lediglich die beiden Pin-Zuweisungen vertauscht werden. Beispiel: aus ENC n= 1 sr= 1 pins=0:1 type=non_detented wird: ENC n= 1 sr= 1 pins=1:0 type=non_detented Gruss, Thorsten.

Hallo Mark, hast Du schon ueberprueft, ob evtl. an der Bruchstelle Leiterbahnen "zusammengequetscht" wurden, so dass ein Kurzschluss entsteht? Gruss, Thorsten.

Ok, I see! In the hysteresis function I haven't considered that somebody could use the new switch mode with a reduced range. This should be fixed now: http://www.ucapps.de/mios32/midibox_ng_v1_030_pre3.zip But you have to change your hardware as well. (don't worry, no risk for damage!) One side of the button should be connected to ground, the other to the analog input. And the Pull-Up resistor is mandatory, otherwise the input will float when the button is not closed, and this will result into random MIDI events. The other unused inputs can be connected to ground directly, no need for 220 Ohm resistors. Best Regards, Thorsten.

Awesome! :hyper: Your tune greatly demonstrates the spirit of SID tunes in combination with MBSID specific features. Therefore I couldn't resist to publish it in the MIDIbox Blog and the MIDIbox SID entry page! :smile: Best Regards, Thorsten.

Hopefully you will find somebody who helps you to doublecheck all connections... yes, unused inputs of this chip should be connected to ground. Best Regards, Thorsten.