TK.

If every slave is assigned to a different MIOS device ID, all what you have to do is to push the Link button and to send the dump to the slave via the master. Best Regards, Thorsten.

Best solution would be the MIDIbox.org portal - thats the idea behind this website - just send the stuff to Poeloq (note that he is currently very busy) Best Regards, Thorsten.

Yes, Mike shipped the boards at 16th december, so if you have luck you will get it before christmas :) Best Regards, Thorsten.

arumblack: sure, the PIC16F877A will also work, you only have to take care for the correct device setting in IC-Prog. My tip: before asking such questions, use the powerfull search function of this forum, because this question has been answered several times before. Ladybug: yes, your JDM is ok, it must be a configuration problem. You didn't answer to my question if the same address cannot be written regardless of the IO delay (and the PC) you are using. It's very very very important for me to know what happens then, otherwise I cannot sort out the root cause. The message "the file does not contain a device ID value" can be ignored, the assembler doesn't include a device ID into the .hex file. You can disable this message somewhere in the preferences... Best Regards, Thorsten. P.S.: the .hex file is correct, it has been released one year ago, and many users tried in during this time P.P.S.: other PIC16F firmwares can be found here: http://www.ucapps.de/pic16f_firmwares.html

icescraper

You mean that IC prog stops burning at address 420h regardless of which IO delay and regardless of which computer you are using? Or do you notice any differences? Is it a PIC16F877 or a PIC16F877A? Best Regards, Thorsten.

Yes, your assumptions are correct... To the PCBs: don't ask me, ask the community! :-) Best Regards, Thorsten.

I've contacted Mike Best Regards, Thorsten.

No idea, but it makes always sense to use the most current version of MIOS. It just takes 5 seconds to update the OS, so why not trying? ;-) I'm not sure, but so far as I know MBSID V1.5b uses some hooks which were not available in MIOS V1.3 Best Regards, Thorsten.

Hi, you can always add your modifications, the top-layer of the display output routines can mostly be found in cs_m_display.inc Check the current MB64 application where Duggle has added a new display mode for 20x4 displays - thats the way how you can do it also for your stuff Best Regards, Thorsten.

Ja, in allen drei Beispielen wurde ein Delay eingesetzt, und im dritten noch ein wenig Chorus hinzugefuegt. Bei einem analogen Delay sehe ich keinen wirklichen Vorteil, die Edel-Delays arbeiten ausschliesslich auf digitaler Basis. Die anderen Schaltungen sind da schon etwas interessanter (danke fuer den Link!). Gruss, Thorsten.

First you should check if this is a software configuration or a hardware problem. Just upload the MIDIO128 application, or MB64E (there is a special preconfigured binary for MBSID hardware called "setup_midibox_sid.syx"). Do they send any random MIDI events? Best Regards, Thorsten.

sure - just don't forget the 10k pull-up R9 if no DIN module is connected to the core. By default, the first 64 LEDs are assigned to Note 0x30-0x6f, the remaining 64 LEDs to CC 0x10-0x4f of the first MIDI channel, but you can change the MIDI events via SysEx by using the mk_midio128_syx script (or by changing the midio_presets.inc file) as often like you want. Best Regards, Thorsten.

thanks - I've changed the orderlist. Best Regards, Thorsten.

No, especially changing the volume register will produce a "plop" sound (it changes the DC offset). This effect has been used for playing samples in the C64 days... ;-) Best Regards, Thorsten.

Hi Jouni, by playing some simple SID files (like Ultima III ;-)) I finally found out the correct order - see sidplay.inc of the new SIDplayer application http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios_toy;action=display;num=1071925936 Thanks for your help! :) Best Regards, Thorsten.

SIDplayer V1 is now available in the MIOS download section: http://www.ucapps.de/mios_download.html ; This MIOS applications interprets the SIDstation "ASID" protocol and ; forwards the requested register changes to a MBHP_SID module ; ; compatible with the ASID player and SIDPLAY/Windows ; -> http://www.d.kth.se/~d93-alo/c64/spw/sidplayw.html ; -> http://www.sidstation.com/sidsupport.php ; ; based on http://sammal.ton.tut.fi/~paulus/asid_protocol.txt ; by Jouni Paulus (jobe(a)iki.fi) ; ; The biggest collection of SID files can be found here: ; http://www.hvsc.c64.org/ [/code] have fun! :) Best Regards, Thorsten.

There is no way to avoid this sound Best Regards, Thorsten.

yes/yes you can change the SID device ID via MIDI as much times as you want. It will be saved in EEPROM and therefore won't be deleted after power-off. Best Regards, Thorsten.

buy & sell

For those who like flash animations (wait at least for 1 minute ;-)) http://www.millan.net/funp/100/deerz2.swf

Sure, you can do this, just 5 lines of code - but the already available implementation which shows an arrow on the screen is much more useful in my eyes - with the arrow you know in which direction the pot has to be turned to reach the initial value. Best Regards, Thorsten.

Hi Domas, sure, it will work. You could connect it to the upcoming companion chip for best performance (search for the posting somewhere under Construction->Concepts), otherwise only uncritical applications like MB64 or MB64E can be used with it. Note that a MIDIbox LC requires a 240x64 display so that all characters can be displayed. There are also some really cheap T6963C GLCDs with this resolution available. Best Regards, Thorsten.

Some bad news: the counter values are jittering (independent from the frequency ), jitter stops with 4-bit resolution, so that w/o a sophisticated interpolation algorithm the d-beam implementation is useless for a musical application. The programming of such an algorithm isn't trivial and consumes a lot of time & effort. I also tried another IR-sensor and the output signal is completely different (it sends pulses with a constant frequency of 1kHz - very strange). This means that unfortunately not all types of IR sensors with integrated amplifier can be re-used, different ones have to be tried. This will be very difficult for peoeple who don't own a scope. So in fact this approach won't really help, I cannot give you any spec for the IR sensor (I only know that it's from a TV which I've canibalized ca. 20 years ago ;-)) and I've currently no motivation to search for a perfect algorithm for my own sensor (the advantage of a D-Beam isn't really so big, it would be a nice feature but nothing else...) So - thats all from my side ;-) Best Regards, Thorsten.

In theory you could patch this in the .hex file, but it's more safety when you just follow the instructions given here http://www.ucapps.de/midibox_sid_csB.html Means: just change the IDs via MIDI Best Regards, Thorsten.