TK.

Hi Julian, which application controls the AOUT module? If you are using MIDIbox SEQ, then take care for the special MIDI channel->AOUT routing which is described at the bottom of this page: http://www.ucapps.de/midibox_seq_options.html So long the gates and the first channel are working, the interconnections between core and AOUT are ok. I would continue with the MAX525 outputs, they can be measured from the jumper sockets (voltage range: 0..2.048V) Results? Best Regards, Thorsten.

Hi Jorge, there is no other way to enable the link without control surface, you already made it correctly by sending the sysex string. Power supply issues: maybe 9V is too much (did you measure the effective voltage at the 7805 input? It could be more than 9V) - a larger head sink can help, another solution is the use of a second converter stage - means: use a 7809 to reduce the voltage to 9V (I still assume that your transformer delivers a higher voltage), then the 7805 to reduce it again to 5V. Thats no professional, but a simple solution. Best Regards, Thorsten.

Hi Jitterbug, a joystick just consists of two pots, I don't see problems so long the resistance of each pot is ca. 10k Best Regards, Thorsten.

The 1.2k pull-up doesn't hurt (it isn't required so long you don't plan to disconnect the MIDI Out driver during runtime) Best Regards, Thorsten.

Hi Sjakie, I guess that you want to select the interface depending on PORTD, 4 (and not PORTC, 4) Yes, this should work. But don't forget to bring this pin into TriState mode (bset TRISD, 4), otherwise you will get a short circuit Best Regards, Thorsten.

Hi Yair, I've absolutely no experiences with such a material, but the idea sounds exciting. Yes, you can use the same ground. The noise can be filtered by using a "schmitt trigger" before the DIN input - a description can be found here: http://www.play-hookey.com/digital/experiments/rtl_schmitt.html I would suggest the use of an integrated circuit - eg. the 7414, which provides 6 schmitt triggers in a single chip: http://www.nullohm.de/datenblaetter/index.htm Best Regards, Thorsten.

Hi Robin, I never really used the simulator, it's mostly more effort then debugging in-system - a valuable debugging help is the use of the MIDI interface in conjunction with a MIDI-Monitor (MIDI-Ox). You can send out common MIDI events (or SysEx streams) to protocol what happens with your code. Example: in order to notify that a certain parts of the code have been executed, you could send out program changes with a continuous number (I call this the "checkpoint method"). Example: ;; some code.. ;; ... ;; checkpoint #1 reached movlw 0xc0 call MIOS_MIDI_TxBufferPut movlw 0x00 call MIOS_MIDI_TxBufferPut ;; some code.. ;; ... ;; checkpoint #2 reached movlw 0xc0 call MIOS_MIDI_TxBufferPut movlw 0x01 call MIOS_MIDI_TxBufferPut [/code] the content of variables can also be sent via MIDI. Here I'm normaly using SysEx streams --- but take care, the bytes within a SysEx stream must be limited to 7-bit! [code] ;; send MIOS_PARAMETER[12] movlw 0xf0 ; begin SysEx call MIOS_MIDI_TxBufferPut movf MIOS_PARAMETER1, W andlw 0x7f ; MIOS_PARAMETER1 & 0x7f call MIOS_MIDI_TxBufferPut movf MIOS_PARAMETER2, W andlw 0x7f ; MIOS_PARAMETER2 & 0x7f call MIOS_MIDI_TxBufferPut movf MIOS_PARAMETER3, W andlw 0x7f ; MIOS_PARAMETER3 & 0x7f call MIOS_MIDI_TxBufferPut movlw 0xf7 ; end SysEx call MIOS_MIDI_TxBufferPut if the full resolution (8-bit) is required, then you have to send the high- and low nibble seperately: ;; send MIOS_PARAMETER[12] movlw 0xf0 ; begin SysEx call MIOS_MIDI_TxBufferPut swapf MIOS_PARAMETER1, W andlw 0x0f ; send upper nipple of MIOS_PARAMETER1 call MIOS_MIDI_TxBufferPut movf MIOS_PARAMETER1, W andlw 0x0f ; send lower nipple of MIOS_PARAMETER1 call MIOS_MIDI_TxBufferPut movlw 0xf7 ; end SysEx call MIOS_MIDI_TxBufferPut [/code] [b]Important:[/b]: MIOS_MIDI_* modifies the BSR, this means: if you are doing BANKED transfer, then BSR has to be restored after the MIDI events have been sent Best Regards, Thorsten.

Hi William, don't know, it will be your job to find a solution ;-) As I already wrote in another thread: the Mackie protocol was designed for stupid slaves, such extensions normaly have to be integrated into the host application Best Regards, Thorsten.

done Best Regards, Thorsten.

Hallo Lemonhorse, die Verbindungen sind ok, allerdings muss im .asm File (bspw. main.asm) noch das ENABLE_AOUT flag gesetzt werden. Letztes Wochenende hat uebrigens ein Bekannter einen analogen Synth (RFE kobol expander) vorbeigebracht, er war voellig perplex, welche Klaenge sich herausholen lassen, wenn man die CV Eingaenge mit der MIDIbox SID ansteuert --- probiere mal die Random Patches (Tip: am besten sind die PW und Filter AOUTs geeignet, da sich der Offset ueber den Pulsewidth/CutOff Regler anpassen laesst) Gruss, Thorsten.

The server was down for ca. 1 hour, reason unknown. Currently a lot of update processes are running, maybe they are doing something against the fails? Best Regards, Thorsten.

Hi Robin, from that what I can see I can only presume that you need to change your workflow. I can see a lot of syntax errors which will (normaly) be reported by the assembler (take a look into the main.err file), they need to be fixed first, the assembler will tell you faster what is wrong (in principle) then I ;-) Second problem I see: since you are trying to implement the whole thing without validating changes step by step, there is a high chance that you will have a lot of trouble to debug the application if nothing works (e.g. if the application crashes). Try to begin with simple extensions and check if your changes are working like expected. Thereafter start to enhance the code in little steps, always check the effects. This will prevent a lot of frustration Best Regards, Thorsten.

Great! (also success stories are welcome :)) Best Regards, Thorsten.

Hi James, thanks for the kind words! :) Regulator: so long it doesn't fail, it's ok. You could mount the regulator directly on the metal case of your sequencer in order to improve cooling. The regulator of my own MBSEQ doesn't get hot, since the core module is powered by a (unregulated) 6V AC source encoders: swap the two cables which are going to the DINX4 module to change the direction Datawheel: I'm not sure, but possibly you have to change the encoder type in the setup_mbseq_v2.asm file from MIOS_ENC_MODE_DETENTED to MIOS_ENC_MODE_DETENTED2 Thereafter rebuild the application like described here: http://www.ucapps.de/howto_tools_mpasm.html Best Regards, Thorsten.

fine! :) Best Regards, Thorsten.

Hi, I think it's the same like for the C64, you can test this by measuring the voltage between pin 14 and 28 when the C128 is powered Best Regards, Thorsten.

Hi Redhead, for motorfaders you have to include the loop into the LC_MF_FaderEvent function (-> lc_mf.inc) Best Regards, Thorsten.

Hi Sebastian, if there is no other volunteer, you can send the stuff to me (not only the PIC, but also the core and SID module) - just write me a mail to get the Packstation address However, before please doublecheck if the loopback in MIDI-Ox is disabled (-> http://www.ucapps.de/mios/bootstrap_sysex0.gif), theafter open "View->Port Routings" and check if the MIDI In data is still forwarded to MIDI Out And please also try to download MIOS with Serge's SysEx Loader Best Regards, Thorsten.

No, you have to use at least one 74HC165 Best Regards, Thorsten.

Maybe the cheapest solution to bring a SID into the box made by David: And Ludos very compact and nice looking MIDIbox SID: More pictures can be found at his webpage: http://www.tatapoum.net/photos/sid/

Wouter just wrote me that he has received a new batch of encoders "Das lange Warten hat ein Ende" :) Best Regards, Thorsten.

You have to change the settings in main.asm of the midibox64 application to 8 (pots) and 0 (no multiplexer), rebuild the application (like described here: http://www.ucapps.de/howto_tools_mpasm.html), and then you can connect your pots directly to the pins of J5. It shouldn't be so difficult - just try it out and you will understand what I mean ;-) Best Regards, Thorsten.

Hallo Dominik, ich habe meine Empfehlung fuer das Pollin Netzteil (weiter oben) korrigiert - schade, dass die Ausgangsspannung absinkt (passiert eigentlich nur bei Ueberlastung, doch da es eigentlich bis zu 1.4A liefert, tippe ich eher auf einen Designfehler) Reichelt PSA 31U-150: extrem teuer, ich weiss nicht, ob sich das lohnt - und vor allem - ob es problemfrei funktioniert. Dann schon lieber ein eigenes Netzteil zusammenbauen (fuer das MF Modul benoetigst Du lediglich ein Netzkabel, eine Feinsicherung+Halterung und einen Transformator, z.B "EL 54/18,8 112" fuer 6 EUR, die Stabilisierung uebernimmt das MF modul). Dabei solltest Du Dir jedoch darueber bewusst sein, dass das Arbeiten an 220V nicht ungefaehrlich ist. Der Transformator sollte nicht frei herumstehen, sondern am besten in das Gehaeuse montiert, und dann erst angeschlossen werden. Nach dem Verloeten des Netzkabels die 220V Anschluesse mit einem festen Klebeband isolieren, um die Gefahr zu vermeiden, dass Du (oder jemand anderes!) irgendwann einmal versehentlich mit der Hochspannung in Kontakt kommst. Fuer das Core Modul benoetigst Du dann noch einen zweiten Transformator, hier bietet sich fuer eine "normale" MIDIbox "EI 42/14,8 106" an, fuer eine MBLC (wegen der vielen LEDs) "El 48/16,8 106" Preisliche unterschiede zwischen den verschiedenen Netzteilen: haengt vom Hersteller, von der Qualitaet und natuerlich vom Innenleben ab. Stecker-Netzgeraete bestehen meistens aus einem Transformator (ptional mit mehreren Ausgaengen fuer verschiedene Spannungen) + Gleich-riecht-er + Elko. Ein Schaltnetzteil enthaelt keinen Trafo, ist aber nicht fuer jedes Geraet geeignet (wie Du bereits gemerkt hast), ein Festspannungsnetzgeraet ist fuer eine bestimmt Spannung optimiert, und ein stabilisiertes Netzgeraet kannst Du zwar an das MF/Core Modul anschliessen, ist jedoch nicht unbedingt notwendig Gruss, Thorsten.

Hi Steve, in MIOS applications the PIC runs at 40 MHz - the external 10 MHz will be quadrupled by the internal PLL. I guess that the name of the MP3 player (nice work) either doesn't know about this feature and uses a 1:1 clock, or that he has some good reasons for a lower frequency Best Regards, Thorsten.

Hi Wise, in the meantime it should be ok to use the "latest and greatest" version Once I've finished the documentation of MIDIbox FM, I will continue with the C stuff. I'm planning a C testsuite (some kind of reliability test) which ensures that the most important C constructs are working, and that all MIOS functions can be accessed Best Regards, Thorsten.