TK.

Sehr gut :) Hier noch ein weiterer Punkt fuer das FAQ (der Dich aber nicht betrifft): wenn das MBHP_USB modul verwendet wird, sollte die MIDI-Verbindung nicht ueber den MIDIbox-Link Port erfolgen, sondern ueber die normalen MIDI-Ports via Optokoppler. Auf keinen Fall die USB-Masse mit der Audio-Masse verbinden, ansonsten entsteht eine Masseschleife. Gruss, Thorsten.

Super! :) Immer her mit den Bildern, schicke sie einfach an tk@midibox.org Gruss, Thorsten.

So long as the programmer reads only '1's, the PIC won't work --- hm, no idea... Best Regards, Thorsten.

Alright - I've written all the required informations into a text file (which goes faster than writing it here in the forum): http://www.ucapps.de/tmp/mios_enc_integration.txt Hope that it works (I haven't tested the code, this is your job... ;-)) Best Regards, Thorsten.

Im GPC Modus kannst Du bis zu 128 Events auf verschiedenen Kanaelen versenden und empfangen - und er laeuft parallel zur MC, das heisst: er kann jederzeit empfangen, und zum senden kann er auf Knopfdruck (per Shift, Toggle oder Switch Funktion, ganz wie Du willst) ein- und wieder geschaltet werden. Den 128 Events kannst Du Namen zuordnen, mit dem Jogwheel kannst Du die Events anwaehlen (ein Fenster: 8 aus 128 ), mit den 8 V-Pots senden. Die motorfader werden im GPC Modus (noch) nicht unterstuetzt, und fuer die Buttons gibt es einen alternativen Layer. Gruss, Thorsten.

Hallo, auch Dir kann geholfen werden. Ich vermute mal, dass die vier freien analogen Eingaenge am PIC nicht auf Masse gelegt sind, deshalb sendet der Core zufaellige MIDI-Events. Zum Button Problem: entferne mal das Kabel zum DIN Modul und verbinde den Anschluss CORE:J9:SI (bzw. den Pin RD1 des PICs) kurzzeitig mit Masse. Das sollte 64 MIDI-Events ausloesen. Kabel wieder wegnehmen - es sollten abermals 64 Events gesendet werden. Wenn dieser Test funktioniert, weisst Du schonmal, dass es nicht am Core Modul liegt. Gruss, Thorsten.

Sure ;-) Have you already programmed an AIN handler which sends any MIDI event when the joystick is moved? This would be a good starting point Best Regards, Thorsten.

Hi Nacho, if verify fails with both programmers, possibly the10k pull-down resistor is not connected to pin RB3? Best Regards, Thorsten.

I've the soundblaster reference book (since more than 10 years now ;-)) which contains all the details, but thanks anyhow :) Best Regards, Thorsten. P.S.: no, I haven't started with the hard/software yet...

I've the soundblaster reference book (since more than 10 years now ;-)) which contains all the details, but thanks anyhow :) Best Regards, Thorsten. P.S.: no, I haven't started with the hard/software yet...

Hi Flecko, it doesn't really matter if you are asking on a MIDIbox related topic or not, most of us are interested in any DIY project and in exchanging experiences. Based on your descriptions I guess that the R4 SID is really dead, but the R3 behaves correctly. The DC offset changes with the volume - this "feature" makes it possible to playback audio samples with 4-bit resolution. Did you also try the other voices? Maybe it's just a configuration problem... it especially makes sense to write defined values into every register (just write a zero into unused registers) for a proper setup For testing the SID: maybe you should give us your location so that somebody from the same country could help you (-> minimal shipping costs) Best Regards, Thorsten.

Hi Dan, here the same: if you promise that you will write a report about the integration for the MIDIbox portal and send it to Poeloq until the 1st November, I will give you some step by step instructions ;-) Best Regards, Thorsten.

Hi Ian, if you promise that you will write a report about the integration for the MIDIbox portal and send it to Poeloq until the 1st November, I will give you some step by step instructions ;-) Best Regards, Thorsten.

Yes, so there is a high possibility that your SID is still working. Did you fix the WR# (or CS#) clue logic in the meantime so that register transfers are working like specified? fine! :) Best Regards, Thorsten.

Hallo Bernd, jep - in dieser Applikation senden und empfangen die Fader CC#0 bis CC#7 auf MIDI-Kanal 1 per default Falls Du eine hoehere Aufloesung probieren moechtest, koenntest Du auch einfach die MIDIbox LC Applikation einladen, hier senden und empfangen die Fader PitchBender Events. Solange Du den 10k Pull-Up an Pin RD1 und den 1k Pull-Up an Pin RA4 nicht vergessen hast, kann nichts ungewolltes passieren. Gruss, Thorsten.

Addendum: falls das Brummen vom MIDI-Kabel her kommt, einfach das Kabel zur Masse an CORE:J12 abknippsen Gruss, Thorsten.

No, the caps cannot be the reason for this behaviour. You hear the oscillator running in background - thats the known 6581 SID bug. But you don't hear the main sound, and this is strange. It really seems that the internal circuit is affected (maybe between oscillators and the amplifier stage). Best Regards, Thorsten.

SmashTV: I noticed the same, some PIC18F are working fine with an unmodified JDM, some others require an additional external power supply for programming, even if they are from the same batch. But the 10k resistor is required anyhow. After production the so called low voltage programming mode is enabled by default, it has to be disabled with the 10k pull-down. If pin RB5 is floating, you've a 50:50 chance that the programming procedure will pass (depends on supply voltage, ambience temperature, etc...). Once you've programmed the PIC, the LVP is disabled and therefore the programming will also work w/o the 10k pull-down. Dan: could you please try the most recent version again - I don't believe that the small changes made in the update are the reason. If you hear this sound again, create a backup of your system like described here: http://www.ucapps.de/mios/mios_backup.txt and send me the files so that I'm able to "clone" your setup Best Regards, Thorsten.

Some SIDs are getting very hot due to leackage issues, this differs with every chip revision and therefore isn't really an indicator if your SID is still ok or not. Do you hear strange noise when the reset is active (=0V)? This would be a simple way to check if "anything" is working. You could try it also without the transistor (but don't forget the 1K pull-down behind the Audio Out) --- with care! I would also add a 100 Ohm resistor in series to ensure that an unintentional short doesn't damage the output stage. Best Regards, Thorsten.

Hi Wancho, a nice design :) 1) yes, you need 4 buttons for the menu navigation. Maybe I will rename the buttons sooner or later to make the function more clear, in the common MIDIbox applications they are used as "Left", "Right", "Exit" (formerly called Exec) and "Exec" (formerly called Snapshot) Button. 3) beside of the menu navigation buttons, I would add at least 8 additional buttons without LEDs. Most programs are providing a bunch of useful MIDI remote functions which make live easier, for example the possibility to switch to different screen views, to open a tool, to save a song, etc... also the MIDIbox offers so called "special functions" which can be assigned to those buttons, e.g. to change directly to a special submenu, to increment/decrement the bank.... If you want to try the MB64seq application, at least 4 additional buttons are required anyhow. 2) This can simply be done by merging the led_digits_mtc application with the MB64 application (copy leddigits.inc and mtc.inc into the mb64 directory, include them from the main.asm and follow the instructions which are given in the file headers). The led_digits_mtc application comes also with a schematic, the shift registers used for the digits are freely assignable. 3 DOUT registers are allocated by the MTC digits handler, and this is exactly the number of registers which are currently not used in your setup. So - you don't need to buy an additional module :) Best Regards, Thorsten.

Hi Dan, I don't agree, every page is listed on the navigation bar, so you only have to refer to the titles like "Concepts->MIOS->Introduction". By doing so, a new viewer will regognize that there are even more pages related to MIOS which maybe provide exactly for what he was looking for. The root cause for the bad overview is, that the pages grown up with the years and need some overwork. I've planned this for the time after the PIC16F phase out. Ok, but it wasn't really my intention to prevent direct links, this is more an imperfection caused by the way how I realized the navigation bar. I don't know how to make it better without producing much more net-traffic (e.g. by including the HTML code for the navigation bar directly into every page). Best Regards, Thorsten.

Yes, thats the error - you've connected two clock domains together and this requires a proper asynchronous bus interface, at least the chip select line should never be activated when the data is not stable. Best Regards, Thorsten.

Hallo, ja, Du kannst den BankStick auch direkt anloeten - kein Problem. Bei dem Taster handelt es sich um einen Momentary Switch, er sollte also funktionieren. Gruss, Thorsten.

FSR2 is not restored when an interrupt has been invoked, only FSR0, FSR1, TBLPTR[LH], TABLAT and MIOS_PARAMETER[123] --- the reason for this is, that you normaly never need a third pointer, only on very special cases, so I decided to left it out to ensure best performance. Yes, by temporary disable interrupts with IRQ_DISABLE it's possible to use all three pointers in your main program. After the use of FSR2 you can enable interrupts again with IRQ_ENABLE. FSR2 don't has to be saved/restored. Such a routine should never run longer than ca. 300 uS to ensure the realtime capability (especially: receiving MIDI events). Yes, you can use FSR1 in between MIOS calles in your main program and in interrupt service routines w/o problems. The reason why I suggest FSR0 is not to confuse newbies too much... There is no MIOS task which uses FSR0, so it can be used without any danger. Best Regards, Thorsten.

I'm not sure why it does only work with MIOS V1.3 at your board, either you are not using the original MIOS and SID releases (download them again, ensure that MIOS V1.4 is correctly uploaded by using the CRC test), or MIOS V1.4 is more sensible to a hardware error. There is only one reason for an endless reformat: if the 1k pull-up at RA4 is not connected, regardless if a BankStick is available or not this is a *must*. You could measure the voltage at this resistor just to ensure that the +5V are there. You could also try another application which uses a BankStick like the bs_xfer example to ensure that MIOS can access your bankstick. Best Regards, thorsten.