TK.

Logic - weil ich Cubase unlogisch finde Gruss, Thorsten.

fixed Best Regards, Thorsten.

Under normal circumstances you don't need to create a special .h or .c file for the SFR definitions, the addresses are compatible. Just only the EEADRH register might be important if EEPROM locations >= 0x100 should be accessed, but so long you are not doing this, the pic18f452* files will work fine Yes, 0x600-0xf7f are available as additional RAM locations. And 0x3000-0xffff is the application code space Best Regards, Thorsten.

I will give you the final answer next thursday (Currently I don't find much time to answer all postings and emails...) Best Regards, Thorsten.

You can select the PIC18F452 without danger, you only need to adapt the project.lkr file (enhanced RAM/code memory) Best Regards, Thorsten.

See this answer http://www.midibox.org/forum/index.php?topic=7006.msg45321#msg45321 For somebody with programming experiences, it should be very easy to setup a compatible custom driver for 4 2x20 LCDs within 1 hour... but it can only be programmed by somebody who has build the appr. hardware... Best Regards, Thorsten.

For the 2x40 LCD option, you will read "only 8 steps are visible on screen (visible beats selected by last changed value)." This means: you will either see step 1-8, or 9-16. The application will switch to the right page when you turn an encoder or press one of the 16 general purpose buttons. Please note, that the 1 * 2x40 LCD option won't work with MBSEQ V3, only 2 * 2x40 will be supported! Best Regards, Thorsten.

I've to disagree my own answer: since MIOS SysEx responses are not tunnled (this is not possible), the endpoint will filter them out. But: you can easily change the merger mode of the last core to "forwarding point" from the debug window of MIOS Studio - just call the MIOS_MIDI_MergerSet function to the ID of the last core with WREG=0x03 Best Regards, Thorsten.

US $100 is a high price when you consider, that the core and SID kit are available in SmashTV's shop for ca. US $40, thats less than the half, and I think that even a MBHP_IIC_MIDI module, a PIC18F4620 and a wall wart won't raise the costs to more than US $50..$60. Therefore I'm currently not sure if I can recomment your venture with a good feeling, because people could assume that this is the best price for a "low-cost MIDIbox SID", which is just not correct... :-/ I've to sleep some nights of this... Best Regards, Thorsten.

this is because another thread has propably overwritten the MIOS_PARAMETER* locations in the meantime... which MIDI message is returned by the core? Btw.: in mios_lcd.inc you can find some usage example for the MIOS_HLP_Dec2BCD() function. As mentioned before: if there is a problem, I expect it in the wrapper code (still don't have time to debug this...) Best Regards, Thorsten.

It works so long the MIDI merger is enabled, regardless if it is a "normal merger", a forwarding or endpoint. Since the SysEx response is not tunnled, it is even forwarded by the endpoint. Thomas: what exactly doesn't work? Best Regards, Thorsten.

Hi, 2x24 LCDs are not enough, because the message transmitted by the host are 2x56 But: if you only need a display, then the graphical LCD solution might be interesting for you. Even a T6963C based display, which is normaly too slow for the whole application (if e.g. motorfaders have to be moved in parallel), is fast enough for your purposes. And in addition, you will get a nice MTC/Beat display, and graphical animated knobs and meters :) I suggest a T6963C based display only for your use case (display only) - they are cheap ($10...) and therefore less expensive than two CLCDs Power: yes, you can propably use the +5V from your BCF, it's worth a try Best Regards, Thorsten.

(I've currently not so much time to test this...) MIOS uses this function internally within MIOS_LCD_BCD4 and MIOS_LCD_BCD5, therefore I'm sure that it delivers the right results. But there could be a problem in the C wrapper (maybe the integer value is passed in the wrong way - this can happen depending on the SDCC version you are using) Best Regards, Thorsten.

Watchdog timer: it's configured in a way which doesn't allow to enable/disable it via software. It's always enabled, and it is serviced by MIOS within the mainloop (after USER_Tick has been called) If USER_Tick stalls longer than 2 seconds, the PIC will be reset. If your routine needs longer (this is critical, >20 mS will cause a MIDI In buffer overrun if a bulk of data is received at the same time), than you have to issue a "clrwdt" instruction in order to service the watchdog, and to avoid a reset. Best Regards, Thorsten.

Hi Jaicen, as mentioned in the last paragraph of the wishlist (http://www.ucapps.de/midibox_sid_v2_wishlist.html), I won't start to continue with planning the extension before V2 is finished. Mainly because, from my experience, I will implement much more features than written down in the list (this is for example the case for MBSEQ V3, on which I'm currently working - you will notice a lot of surprises at the end :)) Best Regards, Thorsten.

Just to say it short: keep on testing! :) Best Regards, Thorsten.

Momentan togglest Du die Variable, wenn der Taster sowohl gedrueckt, als auch losgelassen wurde. Du moechtest aber wahrscheinlich nur dann toggeln, wenn der Taster gedrueckt wurde... dies geht am einfachsten mit einem if( pin_value != 0 ) return; // exit if button has not been pressed [/code] am Anfang der Funktion Gruss, Thorsten.

Compare it with: http://www.ucapps.de/mbhp/mbhp_sid_c64_psu.pdf, a connection is not required, but it doesn't hurt However, I'm missing the 5V/ground connections, without them the logic chips won't be supplied... Best Regards, Thorsten.

I must say that I don't have a clear oversight over all the different versions and revisions. You could compare the layout with the schematic in order to find this out. You can also run the interconnection test to check the pinning if you are unsure. Best Regards, Thorsten.

Hi, the link to the .jpg file doesn't work. However, from the specs this seems to be a simple and good working configuration. Not sure about the VU meters, but from my experience transmitting them via MIDI is not accurate enough, better to build a analog circuit here Best Regards, Thorsten.

[@uote]When I upload any SID app, I start to get a high pitched tone from the audio output than never stops untill I reload MIOS again. Does this mean the PIC is ok, bad wiring or dead sid? you don't need to reload MIOS again, MIOS is not windows... ;-) If you get a high pitched sound, it could be, that the interconnections are not correct, or that there is a short. The mbsid_interconnection test helps to debug this, but you need to upload the .hex file, not the .syx file! Thereafter read the debug instructions in main.asm (or README.txt, don't remember). Best Regards, Thorsten.

it tells you, that the bootloader is up-to-date MIOS Studio doesn't support the required "delay after F7" function, therefore you cannot send .syx file properly with this tool. I know this is not obvious for a newbie, and have Adam informed about this Could it be, that your core is already running properly? Best Regards, Thorsten.

Hi, you only need to follow the instructions on these pages: http://www.ucapps.de/mbhp_core_old.html http://www.ucapps.de/mbhp_sid_old.html Best Regards, Thorsten.

Hi, the PSU requirements which are mentioned at the MBHP_CORE page mainly consider the usage of a single 7805 for multiple core modules. But in your case this is not recommented. Just stuff all components, and power the core modules via Port J1. You can use a single voltage source for this, if it is strong enough (this depends on how many LCDs and LEDs should be driven) You don't need to modify the firmware in order to chain two MIDIbox64, this configuration can be done within the MIDI menu. The first MIDIbox in the chain has to be configured as "MIDIbox Link Forwarding Point", and the second as "MIDIbox Link Endpoint" Best Regards, Thorsten.

Which file of the update package is uploaded here? Did you read the comments in README.txt? Best Regards, Thorsten.