TK.

Hallo Matthias, MIOS laeuft ausschliesslich auf dem PIC18F452. Es ist eigentlich schon seit einem halben Jahr fertig, wird aber hin und wieder mit zusaetzlichen Features angereichert - also nicht verunsichern lassen ;-) Gruss, Thorsten.

Hi Dan, these are warning messages. "BUILD SUCCEEDED" means that the file has been assembled successfully. Message[302] can be disabled with following line in the assembler code: ERRORLEVEL -302 The IC-Prog message "The file does not contain any configuration information!" can be ignored, just disable this check somewhere in the options menu Best Regards, Thorsten.

Dan: you've to use the scart socket (A/V input of your TV) Btw.: the next MIOS version will support a new display type #6 which redirects all print commands directly to the MIDI Out based on the new MBHP_TV protocol. By changing the device ID up to 128 "MLCDs" can be addressed in this way - not only the MBHP_TV itself, but also other "slaves" which support this protocol (example driver for a character LCD as slave will follow). I also plan to include a "soft font" feature into the MBHP_TV which allows to create special characters dynamically like known from character LCDs - hold the line ;-) Best Regards, Thorsten.

1A! :-) Did you know that Phil aka pkstone is working on a similar instrument? http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1046457465 Maybe you could collaborate together. Best Regards, Thorsten.

Man benoetigt fuer dieses Feature auf alle Faelle eine neue Firmware, die zwei Parameter-Sets gleichzeitig im RAM haelt. Zum ersten Mal ist mir diese wirklich brauchbare Funktion beim AN1x aufgefallen, auch Reaktor bietet sie mittlerweile, es wird also Zeit, dass auch die MIDIbox so etwas unterstuetzt. Wegen des doppelten RAM-Verbrauchs wird sich das aber nicht mit dem PIC16F realisieren lassen (es sei denn, man reduziert die Anzahl der Potis, aber ich moechte mir den PIC16F wirklich nicht mehr antun...)... ich werde es bei den PIC18F Versionen der MB64 und MB16E beruecksichtigen. Gruss, Thorsten.

Hallo Pearl, "app_lcd.inc" fehlt im Archiv, das wird bei der naechsten Version nachgeholt. Quickfix: dieses File befindet sich auch in der MIOS Release, kopiere es einfach in das midibox_lc* Verzeichnis Gruss, Thorsten.

Thanks! :) I started the MBHP_TV as a new challenge to learn something new (e.g. to find a solution for an isochronous system which never gets out-of-sync), it's another topic if a display with such a low resolution is usefull or not. But it awakes some vintage feeling - if MIOS would support a keyboard and a mass storage device (PRESS PLAY ON TAPE...), you would have a complete homecomputer ;-) The fascinating thing on this project is that you can see the execution time of a routine directly on screen. Every pixel "consists" of 4 PIC instructions executed within 400 nS - I could also display a pixel with one instruction only, but the PIC18F452 doesn't offer enough memory to store so much data. However, the code is now released and can be found in the MIOS download section (still PAL only), the resolution is 128x64, only one character set is supported yet (but additional fonts could be included) - character size 8x8 (16x8 display) Following SysEx commands are available: ; o Clear Screen: ; f0 00 00 7e 3f 00 00 f7 ; o Set Cursor Pos and Print Characters: ; f0 00 00 7e 3f 00 01 <pos> <char_1> <char_2> ... <char_n> f7 ; o Print Characters (don't set cursor): ; f0 00 00 7e 3f 00 02 <char_1> <char_2> ... <char_n> f7 The MBHP_TV module will be supported by the next MIDIbox LC version :) Best Regards, Thorsten.

How about a big MTC display a nice meter bridge a CC parameter screen a MIOS status display on your TV? is coming soon :-) Based on the Video HowTo from Rickard Gunee http://www.rickard.gunee.com/projects/ Schematic: http://www.ucapps.de/mbhp/mbhp_tv.pdf (you can just re-use your existing MBHP_CORE module and add the two resistors for the Video Out) Preview firmware: http://www.ucapps.de/tmp/mbhp_tv_preview.syx.zip (only prints this intro on screen) Specs: standalone application, display accessible via MIDI, resolution: 128x64, black-white only, currently PAL only, NTSC planned. Best Regards, Thorsten.

Hallo, Die Anzahl der Digits, die von der Applikation angesteuert werden koennen, ist nahezu unbegrenzt :) Siehe auch: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1061838266 Nein, MIOS hat schon immer die Ansteuerung von LED Digits unterstuetzt, lediglich das Programmierbeispiel fehlte... es ist nun unter MIOS->Downloads zu finden. Gruss, Thorsten.

You have to use a temporary register like TMP1 or (better) MIOS_PARAMETER1 ..2 or ..3 (which should be prefered for low-level function) to compare the value by using a xor instruction. Btw: a 8 bit value can also be divided / 16 by using the swapf instruction And you can write 0xff to a register by using the setf instruction And you can left out the return by using "goto" instead of "call" (since the function behind the call will execute the return instruction anyhow) Example: swapf INDF0, W andlw 0x07 movwf MIOS_PARAMETER1 xorlw 0x07 ;; result: zero if value matches skpnz setf MIOS_PARAMETER1 movf MIOS_PARAMETER1, W goto MIOS_LCD_PrintChar Have fun :) Best Regards, Thorsten.

Hi Wilba, your assumptions in a) and b) are correct. USER_SR_Service_Finish gets called directly after the DIN registers have been updated. By using the MIOS_DIN_SRGet function (WREG=0) you will get a pointer to the first register and you can iterate over all 16 registers by incrementing the pointer. Before USER_SR_Service_Finish will be called, also another usefull array will be updated: SR_DIN_CHANGED which notifies a transition for every single bit. You just only have to add 0x10 to FSR1. Btw.: if you want to prevent that USER_DIN_NotifyToggle will be triggered, since your own handler already takes care for some pins, just delete the appr. flags which are related to the appr. DIN. Example: USER_SR_Service_Finish ;; get pointer to first DIN register call MIOS_DIN_SRGet ;; add 0x10 to pointer in order to address the DIN_CHANGED register movlw 0x10 addwf FSR1L, F ;; check for transition on input #3, if not, exit IFCLR INDF1, 3, return ;; prevent that USER_DIN_NotifyToggle will be triggered bcf INDF1, 3 ;; switch back to DIN register movlw -0x10 addwf FSR1L, F ;; branch depending on pin state IFCLR INDF1, 3, rgoto XXX_0 rgoto XXX_1 On the other hand: it would be interesting why you don't plan to use the standard handler --- example for USER_DIN_NotifyToggle ;; branch depending on state of "shift" button (connected to pin #0) movlw 0x00 call MIOS_DIN_PinGet bz USER_DIN_NotifyToggle_SendCC rgoto USER_DIN_NotifyToggle_SendNote ;; ... Assignments of the pins: bit #0 corresponds to D0 of a shift register, etc. Best Regards, Thorsten.

Some short comments to the Panasonics: Steven C sent me three of his faders a week ago for testing. I will do this in one of the next days/weeks after I've finished some other stuff. I wrote to Steve: -> MIOS V1.4 will provide a special option for Panasonic faders Best Regards, Thorsten.

You could manually trigger MIDI events by using a cable, connected to ground, and tapping it to the DIN chain input. However, if the Tx firmware doesn't work, the MB16E won't work, too -> Hardware issue Best Regards, Thorsten.

Hi, you possibly have to disable the CBM8580_FILTER_FIX switch in main.asm Have fun! :) Best Regards, Thorsten.

For the records: the SID's which I own: 1 * MOS 6581 CBM / 3183 (perfect sound, warm filters) 1* MOS 6581 CBM / 2584 (perfect sound, low signal-noise ratio, warm filters) 1* MOS 6581 CBM / 4084 (distorted sound, but nice for fat leads, used in mbsid_demo8.mp3) 1* MOS 8580R5 / 3389 25 (see below) 1* CSG 8580R5 / 4388 25 (see below) 4* CSG 8580R5 / 5092 25 (perfect sound, very high signal-noise ratio, fat filters, see mbsid_v1_5_filter.mp3) Best Regards, Thorsten.

These are driver examples, the possibilities are unlimited, if you plan to use it with other configurations, you are able to change the code in order to adapt it to your hardware. If you want to connect more than 64 LED digits (512 LEDs by the way...), just time-multiplex 16 digits (makes 3 shift registers for 16 digits -> 80 digits = 640 LEDs) --- they won't be so bright like with the 8x8 configuration, but you shouldn't notice flickering. Another solution would be the use of an additional 7-segment decoder (idea by Pilo), so that one DOUT register can drive 2 patterns instead of 1. This would allow to drive 2*16 = 32 digits with 3 DOUT registers, makes 160 digits with a single core, makes 1280 LEDs As I wrote: feel free to change the driver for your needs ;-) Best Regards, Thorsten.

I will use the MAX525, a 4 channel DAC with 12 bit resolution. Latency is no issue (only limited by the transfer time, less than 5 uS (microseconds)). These DACs can be cascaded in a chain like the DOUT registers for a nearly unlimited number of channels. The driver will be embedded into the application and will be written in a way which allows to reuse the code for other DACs from other manufacturers - the adaption will be your job... Best Regards, Thorsten.

yes Best Regards, Thorsten.

Everything ok, but you should add the 4 10k pull-up resistors to RC0-RC3, otherwise the box will generate random events due to open inputs Best Regards, Thorsten.

Metering is supported by the Logic Control protocol, when you take a look into the source code you will already find the handler which converts the appr. MIDI events to bars which are displayed at the LCD The resolution (LEDs) is limited by the protocol, it's 8 channel Mono. It doesn't require an additional core. If you would like to realize a meter bridge for audio signals: this would be a seperate project, and this would require an additional core. Best Regards, Thorsten.

ok, Du verwendest also die unmodifizierte PIC18F firmware. Per default ist sie fuer den 8580 konfiguriert: ;; set this to '1' to enable the filter software workaround for the 8580 SID #define CBM8580_FILTER_FIX 1 demnach fuer 6581 -> ;; set this to '1' to enable the filter software workaround for the 8580 SID #define CBM8580_FILTER_FIX 0 also einfach das main.asm editieren, assemblieren, konvertieren und schliesslich das neue .syx file aufspielen. Gruss, Thorsten.

Hallo, der SID ist (zum groessten teil) ein analoger Chip, es ist voellig normal, dass er warm wird. Die aelteren Revisionen werden wesentlich waermer als die neueren (speziell 8580), aber das passt schon. Dass das Filter sofort sperrt ist allerdings seltsam. Welche Chip-Revision verwendest Du genau (komplette Typenbezeichnung), welche Firmware, und welche Kondensatoren sind an Pin 1/2 und 3/4 angeschlossen? Gruss, Thorsten.

daraus sind mittlerweile 16 digits pro DOUTX4 modul geworden :) nein - das LCD wird einfach direkt an J15 angeschlossen Gruss, Thorsten.

Yes, the bootstrap loader sends an upload request which is also a "sign of live" Please read the bootloader page carefully, there are a lot of things which have to be taken into account (I hope that I didn't miss anything...) Best Regards, Thorsten.

Did you read the new troubleshooting section in the MBHP_JDM page? The new mods are valid for every burner which are connected to the COM port... Best Regards, Thorsten.