TK.

Aus diesem main.hex wird das main.syx generiert, das Du dann via MIDI aufspielst. Dieses main.hex enthaelt lediglich den Applikationscode - und nicht das Betriebssystem. Deshalb macht es keinen Sinn, die Applikation einzeln via JDM in den PIC zu Brennen, wenn der Rest fehlt. Gruss, Thorsten.

Are you really sure that you are using Bootstrap Loader V1.1b? (available since 30.3.2003) How to test this: o Send any MIDI events to the box (just use a MIDI sequencer) o reboot the box (Power off/on) If it doesn't reboot until MIDI cables are diconnected: you are using the (very) old BSL v1.1 or lower If it boots: then I need more input from your side - under which circumstances does it work, when not? Best Regards, Thorsten.

Hi, thanks for the remark at the end, because the MIDI In LED effect indicates that there is a feedback loop in your host application - did you enable some kind of "MIDI Thru" function? This would also explain why the second MIDIbox stalls for 2 seconds before it continues. Please also ensure that you are using the most recent MIOS version V1.5b! Best Regards, Thorsten.

Hi, thanks for your input. It's really strange, because the left side digits are handled by the same code like the right side digits, so why does Digit14/15 display the chars from Digit8/9 and vice versa? Of course, this could also be fixed by software, but I guess it's better when I build the hardware and check it by myself (this can take some weeks...) in order to avoid a documentation disaster. till then you can use the hardware fix Best Regards, Thorsten.

Thanks for the link, Wilba! Well, my offer is still valid - send me a display so that I can try it out. It will be a nice driver example :) Best Regardsm Thorsten.

Hi, you can be sure that a perfectly working CV function for external access to the AOUT module will be provided. Why? Because I also own a Simplesizer ;D (but it is not ready yet... some components are missing) Best Regards, Thorsten.

In fact I was the guy who decided the logo without a competition, although Ofir initially asked for fair play. I was really impressed about his work since it expresses very directly what people can expect from the website w/o much words: a worldwide operating community DIY stuff (soldering iron) faders representative for controlling sounds midibox.org (.org to point up the non-commercial spirit) So, thats also the reason why you can find this logo at my personal page http://www.ucapps.de now (press the reload button). It's a pointer to the midibox.org site. I thought you also like it, but it seems that taste is really different around the world. ;-) (for example, I don't like colourful and unmeaning banners) I've no problem with the view of the globe, am I too tolerant? What shall our fellows in Australia and New Zealand say about this? Think global! And thanks for your contribution, Ofir! :-) Best Regards, Thorsten.

Hi, Steve: there is just a minor bugfix, the MBLC specific "Layer mode" LED didn't work, but normaly is isn't stuffed anyhow. And the LED-Digits feature is only for people who want to add a SMPTE display. STephenTi: yes, you can set the number of faders to 0 and you can disable the MF driver at the top of main.asm The purpose of the digits is described here: http://www.ucapps.de/midibox_lc/midibox_lc_leddigits.pdf only 12 are used, the other four digits output random characters. Are the two status digits also ok? Best Regards, Thorsten.

The interesting thing on this LCD is, that it is working in "vertical mode", means: customized characters can be print with highest performance like known from the KS0108 Buy and send me such a display, and you will get a driver (sooner or later... ;-)) Best Regards, Thorsten.

Hi Alex, you are using v1.1 and not v1.1b? Then please take into account that this older version stalls (doesn't boot MIOS) so long as any MIDI event is received (e.g. Active Sense events from your keyboard). This isn't the problem here, but I just want to inform you before another issue pops up... Based on your other questions I assume that you haven't read all points of the MIDI Troubleshooting Guide: http://www.ucapps.de/howto_debug_midi.html It also explains how to check if your MIDI interface sends the SysEx data correctly... but my suggestion: check all points, regardless if it makes sense for you (yet) or not... just to ensure... Best Regards, Thorsten.

Did you ever try to upload code? Then this strange behaviour could be the result of a data transfer error caused by your MIDI interface or by a bad MIDI connection (check the solderings around the Rx/Tx pins). In this case there is no complete program in the PIC, but only trash which will be executed and is doing anything but a proper boot of the system. If this happens, then you're always on the secure side by uploading MIOS again with the first level bootstrap loader (within 2 seconds after power-on). This is some kind of recovery. If the MIDI Out LED still flickers permanently during the upload, and not only every 750 mS (during the upload...), then there is either a hardware problem (check the Rx/Tx connections again) or the bootstrap loader does not exist in flash. In other words: the LED should never flicker during the first 2 seconds after power-on. It flickers immediately: hardware problem (solderings...) or bootstrap loader doesn't exist It begins to flicker after 2 seconds: corrupted MIOS version due to an unproper code upload Best Regards, Thorsten.

Do you notice the same effect with another application (e.g. the CRC test), and do see any message on the LCD? Best Regards, Thorsten.

Hallo, > Ist der Shuffle Stufenlos einstellbar ? klaro, von 0 bis 15, der Wert laesst sich waehrend der Laufzeit aendern, ohne dass der Sequenzer anfaengt zu stolpern :) > Welche Module brauche ich dafür ? eine detailierte Bauteilliste wird es nach der Release geben. Aber soviel steht fest: ein MBHP_CORE, drei MBHP_DINX4, ein MBHP_DOUTX4, zwei 2x40 LCDs, mind. 38 Buttons, mind. 28 LEDs, und 17 Encoder (Endlosregler) mit Rasterung (!) > Wo bekomme ich die Potis ? Bspw. ALPS STEC16B04 (vertikale Ausfuehrung mit Rasterung - die ist essentiell fuer einen Sequenzer). Gibts ab 1.80 EUR bei Schuricht Oder die Panasonic Encoder, die man hin und wieder bei Ebay ersteigern kann (100 Stueck fuer $24) - qualitativ mindestens genauso gut wie ALPS! (siehe http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=news;action=display;num=1060000023) Gruss, Thorsten.

Do you notice the same effect when no MIDI software is running? Or does it only appear with MIDI-Ox? Best Regards, Thorsten.

Hi Dominik, your PIC has been damaged? Strange! Check the direction of the Schottky diodes (MF Module), they protect the digital circuit against negative transients from the motors. Best Regards, Thorsten.

Hi Cyril, when using the MAX232, you've also to enable the to-COM option in the MIDI merger menu, otherwise the baudrate will be wrong. This explains why the box doesn't receive SysEx anymore, and why it sends pitch bender events instead of controller events. But it's strange that your box sends more or less random data continuously. The root cause must be different. Possible reasons: feedback loop (exit Cubase and check the MIDI messages with MIDI-Ox, if the vanished, check your Cubase setup) missing Pull-Up at the last 74HC165 shift register or DIN input missing ground connections on unused analog pins Best Regards, Thorsten.

Hi SB, thank you very much for this really simple solution!!! :-) I've added a note to the README.txt Best Regards, Thorsten.

Hi Stephen, problem is, that I've added a LED digits driver to the MIDIbox LC application, but haven't found the time to build the hardware in order to test the functionality. D2k tried it, but he noticed the wrong digits - but this could also be a wiring error. So, since you've a tested module, could you please check this version: http://www.ucapps.de/mios/midibox_lc_v1_5rc1.zip You've to set "METERS_ENABLED" and "LEDDIGITS_ENABLED" to 1, otherwise the appr. drivers will be skipped. Best Regards, Thorsten.

Thanks, I've added the link to http://www.ucapps.de/wheretoorder.html Best Regards, Thorsten.

You could add some lines of code into the application which switches between the baudrates. I can tell you more details once I know which application you are planning to build exactly ;-) Best Regards, Thorsten.

Kein Problem, schicke mir die PICs zu, Adresse liegt in Deiner Mailbox. Serge's SysEx loader eignet sich leider nur fuer den Upload von MIDIbox64/MIDIbox64E/MIDIO128 Baenken (Konfigurationsdaten). Aber keine Panik - alles wird einfacher! Die verschiedenen Tools werden demnaechst durch das "MIOS Studio" abgeloest. Gruss, Thorsten.

...should be ok please read again what I've wrote before about the MBHP_USB module in your last postings. The upload of a MIDIbox bank doesn't work with MIDI-Ox, but with Serges SysEx loader, required upload rate: 100 bytes/s The upload of MIOS code doesn't work with Serges SysEx loader, but with MIDI-Ox. The required settings can be found here: http://www.ucapps.de/mios_bootstrap.html Best Regards, Thorsten. FAQMARKER (so that I don't have to repeat myself every week... ;-) )

I've changed the panel design of MIDIbox SEQ - it's still not final, but much more changes are not planned. http://www.ucapps.de/midibox_seq.html Best Regards, Thorsten.

In theory you could add some code to the applications in order to send CC values with the pots, but this solution won't never be so comfortable like the MIDIbox64 application. So - in consideration of your missing programming skills - it's easier for you to use a seperate core module. There is no need for an external Merger, just enable MIDIbox Link (see also http://www.ucapps.de/midibox_link.html). You can select the merger options in the menus (or from external) - connect the MIDIbox64 before the MIDIbox SEQ, select "MBLink Forwarding Point" in the MIDIbox64 menu, and "MBLink Endpoint" in the MBSEQ menu - voila! Best Regards, Thorsten.

Hi Dan, I never tried this out, so I cannot give you more detailed tips. Try some existing options. Hope that you publish your experiences some day at the Portal :) To the code in main.asm: yes, this has to be added to USER_Init... Best Regards, Thorsten.