TK.

The reason is simple: since I don't own Cubase or Nuendo (I'm a Logic user...) I used a demo version to test the protocol handling. Last check was in June 2003! I don't really know if it is still working with current versions, especially because Steinberg added some SW workarounds into Cubase in order to overcome imperfections of the original hardware. Best Regards, Thorsten.

You forgot to copy&paste the three lines before this code block: ;; duplicate (just because the remaining pins are not used for any other purpose) swapf WREG, W iorwf MIOS_PARAMETER1, F [/code] it's a hidden feature (but please don't tell it anybody else before they blame me that it cannot be found in the schematics ;-)) - each common select signal is available on two pins. In other words: the D0 signal is also available at D4 Best Regards, Thorsten.

No, it should be sufficient to swap the pins at one side for this check (so in your case: MBHP_IIC module). There is a iic_midi_sw_loopback test available at the MIOS Download page, did you already try this? It's very useful for debugging the hardware. Best Regards, Thorsten.

Hi Doug, I will get a MB-808 kit as well, and I'm planning to create a branch of the MBSEQ V3 firmware which will be optimized for drum sequencing. On the other hand especially this version will *not* support a LCD, since most people want to left it out, and accordingly the whole user interface shouldn't rely on it. In addition it would create an imense extra effort at my side, if I would have to maintain a version which has a totally different workflow - therefore I prefer a clear seperation between MBSEQ V3 and the MB-808 variant. So, what I want to say: it's great that you want to work on an alternative firmware, and you could benefit from my variant, but I'm sure that it won't be available before I got the kit and built the hardware by myself. Best Regards, Thorsten.

Hi Matteo, unfortunately there is no forwards-quantisation available. I tried to implement this, but the result was extremely unuseful, so that I gave up. :-( So, there is only a backward-quantisation, which means: the last note which has been played at the time the step was active, will be stored. The current pattern can be easily deleted by pressing F1+Clr Item. Thereafter press the button below the Rec item to go back to the record page. There is also a Move function in the utility page which allows you to shift single steps after recording. The user manual describes how it works. And the Scroll function allows you to shift the whole, or parts of the recorded track. Best Regards, Thorsten.

Hi, no you don't need to connect Vss or Vdd to any LED digit pins - in distance: if you would do this, you would fry the LEDs (-> dead) and maybe also the shift registers (-> dead) You wrote that you've removed the resistors. Thats good - but did you also solder the bridges? In other words: did you replace the resistors by bridges, so that the common pins are directly connected to the 74HC595 outputs? Another possibilty would be a failing .hex build, so that the old (unchanged) firmware has been uploaded - doublecheck that MPASMWIN doesn't print an error message. If you are unsure, you could also check this by opening main.inc, and replacing following message: #define MBSEQ_VERSION_STR "MBSEQ V3.2a " by: #define MBSEQ_VERSION_STR "Echopraxia " With this change, you should see your name after the MIOS bootscreen. Best Regards, Thorsten.

Hi, yes, BankStick support was only temporary disabled, and yes it is possible to read out the BankStick, see http://www.ucapps.de/mios/mios_backup.txt (no special support from MIOS Studio). However, I think that the issue is related to the MIOS Device ID of your core. Because the "CS not enabled!" message (thanks for listing this important detail!) indicates, that the firmware is running on a slave (-> device ID != 0x00) Is this correct? Only the master reacts on program changes, and thereafter sends the patch to the slaves which are assigned to the appr. MIDI channel. In other words: connecting a BankStick to a slave doesn't make much sense... Best Regards, Thorsten.

Since MIOS has been pre-installed, the bootloader will only send a single upload request message during power-on before MIOS is started. This one is hard to notify. No, the Tx signal doesn't go through the optocoupler - with the Core MIDI Out -> PC MIDI In connection it will be connected to the optocoupler of your PC MIDI Interface. If the Tx line outputs 5V, it's very likely that the PIC is running, otherwise Tx would be around 0V So, it looks like an issue with the MIDI In Port, with the MIDI connections to your PC, or with the driver of your MIDI interface. Yes, it is sufficient to connect only the LCD for this check, buttons and encoders can be connected later. Note that for MBSID V2 a SHIFT/UP/DOWN button should be added as well (see MBSID V2 Manual, Hardware chapter). Best Regards, Thorsten.

I don't know the modifications which have been made, but they should be more or less the same. Best Regards, Thorsten.

It's better to trace SID register changes with a tool like SIDdump. It not only gives you the oscillator settings, but also an hint about modulations and wavetable sequences. Some infos can be found here: http://www.ucapps.de/howto_sid_wavetables_1.html Best Regards, Thorsten.

Yes, should work ok, but it could make sense to use a low-drop regulator instead of the 7805, so that the unusued power won't be transfered into heat. Unfortunately I cannot give you recommendations for "known good parts"... Best Regards, Thorsten.

The MIDI output looks as expected, what is the actual problem? Best Regards, Thorsten.

So far I remember, for the rewind and forward button no LED function is available. Best Regards, Thorsten.

Hot tip: MIDI events are sent with "MIDI_EVNT_Send", this is a useful keyword when searching in cs_m_record.inc Best Regards, Thorsten.

For my own interest: could you please measure the DC voltage at following outputs: IC3, O4 IC3, O3 IC5, O4 IC5, O3 Best Regards, Thorsten.

Clever! :) Best Regards, Thorsten.

Hi Bacjonjuice, welcome on board! :) It seems that the pull-up resistor for the CAN Rx input is missing. More infos here: http://www.ucapps.de/midibox_sid_manual_ki.html Bst Regards, Thorsten.

Without loosing to many words: so long the green LED doesn't lit, the PIC16F88 firmware is not running. Possible reasons: +5V/GND (Vs/Vd) not available at PIC (check voltage between pin #5 and #14, should be 5V), crystal or 15 pF caps not soldered properly, firmware not burned correctly (probability low)... Or is the green LED not connected correctly? (check 220 Ohm resistor and polarity of LED) Best Regards, Thorsten.

Fine! :) No, encoder functions are not accessible via remote. But if you would add just one DIN shiftregister, you could control the current selected value with the "datawheel" (main encoder... the big knob in the middle) Best Regards, Thorsten.

According to the IIC spec, it is allowed to omit the STOP so long the same device is accessed again, but I felt saver to show you an example with stop/start, as I know that e.g. the IIC slave of PIC16F88 cannot handle the "restart" condition properly Best Regards, Thorsten.

Yes, it should start playing so long the BPM generator is in auto mode, so that it automatically switches to MIDI clock slave. I'm not 100% sure if this is the default setting in EEPROM, but it should... Best Regards, Thorsten.

fixed in RC12 Next bug, please! :) Best Regards, Thorsten.

The code looks correct. But the datasheet says, that there is an address pointer which will be incremented on each read operation. It isn't explicitely mentioned, but I would expect that you need to reset the pointer by hand when you want to read from zero. So, the code should look somehow like this (quick hack, errors can be expected) MIOS_IIC_Start(); MIOS_IIC_ByteSend(0xd0); // slave address, write operation MIOS_IIC_ByteSend(0x00); // set address pointer to 0 MIOS_IIC_Stop(); MIOS_IIC_Start(); MIOS_IIC_ByteSend(0xd1); // slave address, read operation b0 = MIOS_IIC_ByteReceive(); MIOS_IIC_AckSend(); b1 = MIOS_IIC_ByteReceive(); MIOS_IIC_NakSend(); MIOS_IIC_Stop(); [/code] once this sequence is working, you can add all the robustness stuff, like check for BS_AVAILABLE, etc Best Regards, Thorsten.

Yes, the red marked key combination remote+menu key has a special function, because it allows you to jump to the red marked menu pages. With key combinatin I mean, that for the menu page selection you have to press&hold the remote, and thereafter the menu key in addition. Thereafter press GP#1..GP#16 to enter the corresponding menu page. The order in which you release the keys doesn't matter (I just have doublechecked this, it is still working like expected). For the black marked key function you only have to press&hold the remote key You can always exit a menu page by pressing remote+"step view" keys In general the mechanism is working like the MIDI remote function of sequencers like Logic Audio or Cubase Just only keep in mind, that the remote key has to be pressed+held first! Best Regards, Thorsten.

RC11 contains just another fix for sustain pedal (wrong note was sometimes forwarded to oscillators) Best Regards, Thorsten.