TK.

Hallo, die Versorgungsspannung ist zu niedrig, der LM317 benoetigt ein wenig "Luft nach oben", um 12.5V zu stabiliseren. Wenn am Eingang etwa die gleiche, oder eine niedrigere Spannung anliegt, kann es evtl. schon sein, dass am Ausgang nur noch 7..8V herauskommen. Da bin ich mir jedoch nicht 100% sicher. Ein anderer Grund koennte sein, dass Du den LM317 falsch angeschlossen hast (das Pinning steht im Schaltplan) - ist mir auch schonmal passiert, das Verhalten der Ausgangsspannung war ziemlich seltsam ;-) Falls eine hoehere Spannung nicht machbar ist, koenntest Du das Netzteil + 9V Batterie auch einfach direkt an J2 anschliessen Der BC546 sollte ok sein, er ist nicht zur Stabilisierung gedacht, sondern schliesst den MCLR Pin gegen Masse, um einen Reset auszuloessen. Gruss, Thorsten.

Der Encoder-Eintrag in mios_tables.inc ist falsch, hier wurde der Encoder auf Pin D0 und D1 gelegt, Du hast ihn aber sicherlich an D6 und D7 angeschlossen? Du koenntest den Eintrag dementsprechend anpassen. Ausserdem sind in main.asm der Exec und Select Button auf andere Pins gelegt, wenn DEFAULT_ENC_DATAWHEEL >= 0 ist Auch hier muesstest Du die richtigen Pin-Nummern eintragen. Gruss, Thorsten.

Debugging with a scope is really simple: check the signal at the oscillator pins (OSC1 and OSC2), it should be 10 MHz, the amplitude is ca. 2-3 V so far I remember but it doesn't matter here - only the frequency is important, so long the clock is not available, nothing else will work. SMDs: are you sure that this is a cheaper solution? The DIP version of the 74HC595 costs 0.33 EUR at Reichelt. Best Regards, Thorsten.

Unfortunately there is no special mark, only the manufacturer can tell you if the crystal is the right one or not. On the other side: in 99% of all cases you will get a parallel cut crystal if the distributor doesn't mention that it's a special type. Only unexperienced distributors don't specify the type Best Regards, Thorsten.

No, this is a serial connection which increases the resistance. Parallel means: just connect them together Best Regards, Thorsten.

Thanks for the feedback! :) Don't hesitate to publish your code in the MIDIbox Wiki Best Regards, Thorsten.

Ok, since you made such a progress, I haven't added the stuff into the original release. ;-) It's too difficult to find a general solution, the informations which should be displayed on the additional LEDs are too individual, especially in drum mode. And there are many cases which have to be tested. Since I'm not able to do this with my hardware, I don't want to spent any effort here. Hint: maybe it's better to add the changes to SEQ_LED_UpdateIRQ, search for SEQ_LED_UpdateIRQ_GPLED_Not0, this is the place where the different LED patterns are selected. The track number is in SEQ_STEP_LEDS_CTR. Don't use the SEQ_FSR* or CS_M_HLP* functions here to determine the pointer to the track records, also don't use the TMP variables --- this is an interrupt service routine. Thats all what I can say reg. this topic. Best Regards, Thorsten. P.S.: take care, parts of seq_gp.inc have been changed, don't copy your old file over the new one

Alright, this is the root cause! The PIC18F452 requires a 10 MHz crystal Best Regards, Thorsten.

Hi Martin, your help is welcome! :) Style guide: the easiest solution would be when only the texts are translated. If you want to add more descriptions, more pictures, more examples, then this should be done in the original page as well to avoid inconsitencies on changes. I already wrote it to Moxi, but it's possible for general interest. Here some things which will be changed in the next weeks: all MBHP pages will get some hints and pictures about bypass caps the MBHP_MF page will be completely rewritten the MIOS Bootstrap page will be partly overworked due to the new upload tool (MIOS Studio) hints about MIOS Studio will also be added to the "MPASM" and "MPLAB" page, and to the troubleshooting page Best Regards, Thorsten.

An impressing pictures! :) Not sure if caps will really help, maybe it's better to reduce the value of the pull-up resistors on the DIN module. You don't need to replace them, just solder the resistors in parallel. E.g., with a second 10k in parallel, you will get a 5k resistance You could try this for 1..8 inputs first in order to check if this really helps Best Regards, Thorsten.

If the crystal would be a problem, you wouldn't be able to upload code or to receive the right MIDI events. So, it must be ok. Which display are you using exactly? Best Regards, Thorsten.

General tips for improvements: interrupts don't need to be disabled - currently it would be difficult to use the functions if interrupts are already disabled by the function which calls the subroutine (for any reason) use FSR1 instead of FSR0 like every MIOS routine - so that the program can use FSR0 for something else add a "movf MIOS_PARAMETER1, W" at the end of SRAM_Read, this saves code size on the calling routine (e.g. call SRAM_Read, movwf MY_VARIABLE) the PAGE* functions should access pages of 0x40 bytes, this makes it compatible to the MIOS_*_PAGE* functions variables like SRAM_ADDR should always be defined in app_defines.h to improve the oversight. An hint in the source code, that these registers must be defined, should be enough I would suggest to make the port for the SRAM control pins (currently LATA) and maybe also for the data/address port definable. See the aout driver (aout.inc) as an example Best Regards, Thorsten.

Hi, frequency: up to 400 kHz, pull-up resistor value: 1k doesn't hurt here, than lower, than better (ok, the current consumption with < 100 Ohm would be too high) Best Regards, Thorsten.

The new version v2_2b is now available in the MIOS download section: http://www.ucapps.de/mios_download.html Fixed bugs: firmware doesn't crash anymore when multiple tracks are selected and the GP buttons are pressed MIDI event type (Note/CC/...) printed at first line when in drum mode ALL function disabled in drum mode track shift function disabled in drum mode Solo plays only the selected tracks and layer in drum mode (it's not possible to select multiple layers) manual trigger doesn't stop the sequencer anymore manual trigger plays only one step if sequencer is not in run mode (same behaviour like before) the display artifacts issue should not happen anymore Please let me know if there are any other (or new...) problems Best Regards, Thorsten.

Adam has sent me a new beta release (_beta2) with some minor bugfixes. Use this especially if you notice problems with the code upload (the block size has been decreased to 256 bytes due to problems with the Java MIDI handler in connection with the MIDI driver for SBLive and USB-MIDI) The link can be found under: http://www.avishowtech.com/midibox/wiki/index.php/miosstudio (Rene: strange, it should be a .jar file, does your browser support .zip an on-the-fly?) Best Regards, Thorsten.

Danke Martin! Du solltest diesen Artikel im Wiki veroeffentlichen, damit er nicht verloren geht (er muss nicht unbedingt in English uebersetzt werden) Gruss, Thorsten.

Hallo, je nach Vendor und Product ID sucht Windows einen passenden Treiber, es ist jedoch auch moeglich, diesen nachtraeglich zu aendern ("Treiber aktualisieren") Ich habe uebrigens meine eigenen PIDs, sponsored by Voti: http://www.voti.nl/pids/ allerdings helfen sie bei diesem Problem auch nicht weiter ;-) Gruss, Thorsten.

Hallo Markus, Mit ID 0x01 kann man einen Dump requesten, er enthaelt jedoch saemtliche Konfigurationsdaten Oder moechtest Du genau die MIDI Events requesten, die von den Bedienelementen (Encoder/Pot/Buttons) gesendet werden? Solch einen Snapshot kann man eigentlich nur ueber einen Taster antriggern, und nicht via SysEx. Falls Du hier keine weitere Programmierarbeit reinstecken moechtest, koenntest Du auch einfach das "AUTO_SNAPSHOT" und "RECEIVE_PC_FOR_BANKCHANGE" Flag im midibox64e.ini File einschalten - so laesst sich der Snapshot ueber einen Program Change Befehl antriggern. Es gibt mittlerweile eine neue MB64E Variante, die jedoch noch nicht veroeffentlicht ist. Sie unterstuetzt (optional) einen Patch Modus, bei dem man als Snapshot lediglich die Encoder/Pot/Button Einstellungen zurueckbekommt, und nicht die MIDI Events (zusaetzlich kann man 128 dieser Patches in jeden BankStick speichern). Falls Du so etwas brauchst, dann kann ich Dir eine Vorabversion zuschicken. Gruss, Thorsten.

Before I'm consuming the time to check and especially to describe how the LED feature has to be hacked into the application, I will include this option into the next release. Best Regards, Thorsten.

Hi Robin, before this thread runs endless, I would suggest that you send me your code + the BankStick dumps, so that I can try this with my hardware. An unrelated note: did you ever think of programming the application in C instead of assembler? The SDCC wrapper is already available - the implementation should be much easier, and it is especially not required to use the MIDIO128 as a framework. I guess that your whole application could be put into a single main.c file, which gives you a much better oversight - I think it's worth a try! More infos can be found under: http://www.ucapps.de/mios_c.html Best Regards, Thorsten.

Hi, with these results it is very obvious that you are using a wrong crystal, so that the PIC is clocked with the wrong frequency. This leads to the wrong baudrate. From where did you by the crystal, whats the part number? Normaly it's not hard to get the right one, but it can happen that a shop sells you a crystal for radio devices (which are working on serial, and not on parallel resonance) Best Regards, Thorsten.

Finally finally finally... MIOS Studio has reached the beta phase! :-) MIOS Studio was started by Wilba in November 2003, and later taken over by Adam King. It is a java-based, platform-independent MIDI processing environment, which not only provides upload and debug functions for MIOS, but also advanced features like MIDI Port Routing, Filtering and a virtual Keyboard. It's written in a modular way and will be published under GPL later so that other programmers can make their contributions. More infos can be found in the Wiki: http://www.avishowtech.com/midibox/wiki/index.php/miosstudio Thanks Wilba and Adam for your work!!! MIOS Studio was my "secret weapon" in the last months, without this tool I wouldn't be able to develop and debug so efficient :) Best Regards, Thorsten.

Thanks Julian - this will also be fixed (seems that I have to hurry up with v2.3 ;-)) Best Regards, Thorsten.

The code for the step patterns is located in seq_gp.inc, function SEQ_GP_Mode0_LED (there you will also find a branch for drum mode) Best Regards, Thorsten.

FAQMARKER ;-)