TK.

Alright Robin, thanks for the logfile! So it seems that the bootloader receives anything, but it never returns an acknowledge. Such a behaviour could be related to a MIDI-Ox setup or MIDI driver problem (e.g. the USB-MIDI driver from Microsoft corrupts also the messages if the buffer size is smaller than the SysEx string). Could you please try following settings (SysEx configuration menu of MIDI-Ox): Low Level Output Buffer Size: 2048 Low Level Output Buffer Num: 32 Delay after F7: 750 ms (just to ensure, you could also increase this delay, but 750 ms should work ok) Another usefull test: connect the MIDI-Out of your PC with the MIDI-In (feeback loop). Load a .syx file and start the "Send/Receive" function under "Command Window->Send/Receive SysEx". The number of received bytes should match with the number of transmitted bytes. If this value doesn't match, the driver of your MIDI interface defenitely has a bug (for which the increased buffer size could be a workaround) Best Regards, Thorsten.

You wrote that a copyright message appears, thereafter the PIC will be reset. Is this still the case? This would mean that you were able to upload MIOS itself once. It would be interesting for me, if the complete OS has been uploaded, means: I want to see all the "acknowledge" messages which are sent during the upload of the operating system. You will not be able to upload an application if MIOS is not complete, e.g. because of an error during the first upload procedure (this could also explain why the PIC will be reset) Ok, so just try the MIOS upload again. If this doesn't work anymore, you've possibly problems with the MIDI-In connection (from the Rx pin of the PIC to the MIDI-In of your PC) - in this case I can give you some more infos, how to debug the hardware... Best Regards, Thorsten.

Update: I just have integrated a new function into MIOS which allows to set the "startup speed". Just another value which can be tweaked ;-) Resulting from this possibility, the Up/Down speed can now be decreased to 0x03 (before the change it was 0x10). The Faders are starting faster now, but they are reaching the target position more smoothly. Now I will integrate a calibration menu into the LC application so that the values can be optimized in direct interaction with the host software. :) Best Regards, Thorsten.

I haven't asked for the MRST# voltage without a reason ;-) The measuring result would be interesting, because it would show if it makes sense to improve this voltage for the PIC18F. The Note and CC events can only be assigned with computer, a keyboard or another MIDI controller - sorry. :-/ Best Regards, Thorsten.

Thats a very interesting input! It makes sense to increase the PWM voltage level for the first miliseconds when the fader starts to move. I will try this on the driver side Best Regards, Thorsten.

> Will there be a chance for a driver update someday? > Especially the multiclient thing is not so good for me... This isn't in my hand, the Microsoft driver isn't multiclient capable... However, if somebody has experiences in writing an own USB driver for the OS site, he is welcome for doing this! Best Regards, Thorsten.

Stealth mode? Hm.... maybe too much coffee ;-) The results given by the monitor are showing that you've no jitter on the AIN lines, this is very good! This means also that you can decrease the AIN deadband to 1, and the MF deadband to 3 or higher (but I think that you've already tried this). But it makes sense to use these settings and to vary only the motorfader voltage AND the calibration value (motor speed) for upward and downward movements. Maybe I should integrate the calibration feature also into  the LC application so that you are able to start some experiments with the settings without reburning the PIC. Best Regards, Thorsten. P.S.: the described effect (fader stops ca. 4 mm beside of the target position) means that the faders are too fast, so that they never reach the exact position. A timeout will happen after 5 retries, thereafter the MF driver will send the "real" position. You can slow down the fader with a lower MF module voltage and with the Up/Down calibration value.

Alright, did you also try the "Windows API" setting. And which voltage level do you measure at the MRST# pin during programming? Note that you can increase/decrease this level with the I/O delay, maybe this already helps Best Regards, Thorsten.

Could you please make some snapshots of your IC-Prog configuration and post it here (or just send me the snapshots via Email) Sure, you can also use the MBPlus to control the SID. The CC table can be found here: http://www.ucapps.de/midibox_sid/sid_cc_implementation_chart.txt Best Regards, Thorsten.

-> http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1055947907

Ok, switching to the Gameport.... no, it isn't possible to change the default baudrate without reburning the PIC, it can be changed from the Application, but since the upload doesn't work.... however - now it's maybe better if you would check the Rx/Tx line of your Gameport first just to ensure that MIDI-Ox has been configured correctly. Desolder the MIDIbox connections from the Gameport plug and solder the Tx pin to the Rx pin so that you have a feedback loop. Start MIDI-Ox, send a MIDI-Event (e.g. with the virtual keyboard). You should see the outgoing as well as the incoming MIDI event on the screen. If not, please post your MIDI-Ox configuration here (the port setup) - and maybe also the SysEx configuration (hope that you've set the delay between two F7 to 750 ms?) Best Regards, Thorsten.

Hallo Jimy, Du kannst das Core Modul dazu hernehmen, das Layout findest Du unter Concepts->MBHP->Core Module, eine fertige Leiterplatte gibt es unter http://www.mikes-elektronikseite.de fuer 6.50 EUR Gruss, Thorsten.

Na immerhin sind die genialen KS0108 GLCDs noch erhaeltlich - wie lange hast Du gebraucht, um den Distributor zu finden? Kannst Du mir das .pdf mal zuschicken? Ich wuerde mir gerne das Pinout ueberpruefen bevor Du bestellst. Gruss, Thorsten.

A very clean setup! :) No, the bootstrap loader isn't the problem. I guess that the application fails since the open analog pins are not connected to ground. Did you also try another application, for example the DOUT test, just to check if anything is running ok? Which messages appear during the MIOS upload, do you see any "...0E xx F7" error message? Regarding the MB64 application: see http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1055947907 Since the SID control surface is nearly finished, it cannot get that long ;-) Best Regards, Thorsten. P.S.: are you able to increase the input voltage to the core module? Maybe the backlight consumes too much power that Vdd sinks below 5V and the PIC will be reset!

Hi Sephult, the 2*40 display is a common CLCD (character LCD) which requires no additional configuration. Just use the default type (0x00) and it should work :) Best Regards, Thorsten.

Hi Dan, > > External Meters: will work in exactly the same way like the LED rings, > > so you could change LEDRINGS_SR_CATHODES and *_ANODES_* setting to > > test the LEDs > change these to what? I just wired them up as described for the led > rings pdf...i hope that was right Shocked... yes, this was correct. The midibox_lc application allows you to specify where these shift registers are located. Just take a look into the main.asm file of midibox_lc > So the 4th register would have 4 brdiges and 4 resistors stuffed for an > additionl 4 LED inputs right? yep! > Can i use the spare inputs on the shift registers used on the LED meter > rings for the MTC display digits, or just a regualr LED assigned to a LC function? Would be cool, but I cannot support the shifting of multiplexed pins as a general solution, such a flexible routine would cost a lot of performance. However, after I've implemented this stuff, I could tell you how to modify the firmware so that the anodes/cathodes pins can be assigned to any pin (hardcoded solution). Best Regards, Thorsten.

Hi Pearl, yes, you have to solder all power pins, in most cases they are not connected together (unfortunately!). I will send the PCB to Mike next week when he is back from vacation. Note for people outside germany: the PCB can also be ordered from SmashTV from the US for about US $7 (Tim: please correct me if I'm wrong)! He made the PCB layout and only his board will have the DIY friendly laser print (the part names and outlines are printed at the top side) Best Regards, Thorsten.

Mike is currently on vacation, but I will ask him next week. Btw.: the PCB layout has been created by SmashTV - thanks a lot!!! :-) And of course, you can also order the board from him (he should be back on friday) Best Regards, Thorsten.

okok, before you've to wait endless for the complete documentation, you will find now all the stuff which is required to get this module running under Concepts->MBHP->USB Please read it carefully, this projects isn't suitable for beginners (because of the SMD chip) Best Regards, Thorsten.

Ja, richtig, der Optokoppler muss nur am ersten Eingang der MIDI-Kette bestueckt werden. Bist Du schon am basteln? :) Gruss, Thorsten.

Hi Duggle, MB64, MB16E, MBMF and MIDIbox64SEQ will be ported to MIOS as soon as I finished my running projects. In the meantime you could use the ain64_din128_dout128 test application which don't come with a menu or defined SysEx structure, but already supports 64 pots and a lot of buttons and LEDs. All the known MB64 features will be available with the ported firmware, but if you want to start with some experiments, an upgrade would already makes sense. :) Best Regards, Thorsten.

Than lower the R*C value, than shorter the delay time of the monoflop. However, it's not clear to me why 100k wasn't working, maybe you are using a bigger capacitor? Best Regards, Thorsten.

I never tried the Kawai driver by myself, another user noticed that the Yamaha and Roland driver don't work with his windows installation, but the Kawai did run... however, I'm using Windows ME (and don't plan to switch to any newer version ;-)) therefore I cannot help if the failure is caused by a driver issue. Rx pin: yes, you can disconnect this directly on J11, this should help. It's only important to know if the continuous stream is caused by a feedback loop, and this can be determined by "breaking" the loop. Best Regards, Thorsten.

Hi Pilo, Jack sent me a KS0104 based display some time ago, but I wasn't able to write a driver because of a incomplete spec. Later I realized that such kind of displays will eat so much performance, that they cannot be used with a single chip. A second PIC will be required with a tricky firmware which emulates a KS0108 protocol or something similar. Too much effort for me (yet), so: forget this display :-/ Best Regards, Thorsten.

Hi Dan, to 1: only two layers are provided. So, you could assign Mute to the first, Solo to the second layer, and use two layer buttons to select the layer. And of course also a shift button if you want. :) It isn't possible to assign a function of a second LC, because the protocol doesn't support channels or Client IDs. Only a trick could help: if you've experiences with the Map-Feature of MIDI-Ox and MIDI Yoke, you could try to route the MIDI events to virtual MIDI ports depending on a MIDI channel or whatever. I never tried this (because I've no need for this), so you have to make your own experiements ;-) to 2: the MBLink port of the USB module is nothing else than a direct connection to J11 of the core module. It replaces the LTC. MBLink "Forwarding" and "Endpoint" are features which don't help for the LC protocol, because it requires a direct Point-to-Point connection (like mentioned by you) External Meters: will work in exactly the same way like the LED rings, so you could change LEDRINGS_SR_CATHODES and *_ANODES_* setting to test the LEDs LED digits: possibly simmilar to the MTC from the MIDImon, the additional digits will also be connected to the first and third SR (so that 6 digits are on the left, and 6 digits on the right side). The 4 additional anode lines will be connected to the 4th register. You are right, due to the 128 DOUT pins limitation it's not possible to use so much LEDs like without the meters and MTC display. A Possible configuration: o 3 SR for 8 LED rings o 3 SR for 8 meters o 4 SR for the MTC display (4 spare pins) makes 6*8 + 4 = 52 free DOUTs for LED functions Best Regards, Thorsten.