TK.

Shipped today: Nestle Pivado Veermaster Moduku peefunk76 Hawkeye jona ErMangaver SMIDIRIN MisterM MPN midifix ionas Erics sylwester sparx gpmacklin Marcel60 meToo SDRman gtxdude Doug Wellington Bugfight jojjelito technobreath findbuddha Rosch gomiboy99 grizz dnode Wilba Scuzzle KeyboardSteve Monokinetic funkyboard toadstool norbim1 taximan kokiPsiho lanu64x Altitude Raphael SebastianKulik zwischennetz Nils Waiting for money: Nasrudin sunnygobo Mozart Delayed on request: cinhcet In Stock: 18 PCBs, 21 MagJacks Best Regards, Thorsten. P.S.: something totally unexpected happened! The german mail service has lowered the postage to foreign countries! :) Shipping costs is now 4 EUR outside germany

The remaining chips are already reserved for people who ordered GM5x5x5 PCBs Best Regards, Thorsten.

Please try http://www.ucapps.de/mios/midibox_808_v1_2pre2.zip Shuffle issue has been fixed, and rotate function has been added (press SHIFT + move instrument encoder) Nebula: I added an immediate display update when the encoder is moved Best Regards, Thorsten.

Alright, there are two places which have to be merged with the original MBSEQ V3 code, I only merged one function and haven't tested it properly (but this is your job anyhow as agreed ;)) The interesting point: it seems that I never committed this update to the SVN server, and the files got lost after I moved to a new computer... Therefore all the confusion. Best Regards, Thorsten.

I quickly tried this by myself, and can confirm that this isn't the intended behaviour. E.g. enable all steps of a track, increase shuffle and select any track length: the "groove" should never change, right? Best Regards, Thorsten.

How could I forget this - will be added! :) Of course, because it's in sync with the measure and to all instruments which are playing the same number of steps as selected for the measure. Example: try 7 steps per measure and the 7-step track should always be in sync. This approach is especially important when MB808 is synched to external sequencers which are playing a shuffled groove as well. Best Regards, Thorsten.

Sneakthief/Nuke: please check the preliminary v1.2: http://www.ucapps.de/mios/midibox_808_v1_2pre1.zip From the ChangeLog: MIDIbox 808 V1.2 ~~~~~~~~~~~~~~~~ o Groove function now takes the global step has reference instead of the local step. This results into better results on a non-linear step progression. o Synch-to-Measure working as intended again o Options Page: added Synched Section Change option (GP button #3) o Options Page: added Synched Pattern Change option (GP button #4) o Pattern page: GP LEDs of currently played pattern are flashing to the beat [/code] I've doubts about this change: - it wouldn't be a track copy function anymore, but more like a "layer copy" function (selected instrument from one to another section) - no possibility anymore to make a temporary backup by pressing copy, changing the pattern, restore via paste if it was trash - difficult usage; a typical feature which you would use some days, and then forget and never use it again - by re-entering a simple 16 step pattern instead of copying it, you will get some random variations for free ;) Best Regards, Thorsten.

Debug-Meldungen vereinfachen das Debuggen von Routinen, man baut sie nachtraeglich an den interessanten Stellen ein, und zwar idealerweise so, dass man sie jederzeit auch wieder ausschalten kann, ohne sie komplett zu entfernen (bspw. via #if statements) Die Kunst ist, Stellen zu finden, die nicht zu oft angesprungen werden (ansonsten wird man unnoetigen Meldungen zugemuellt), die einem jedoch trotzdem erlauben, das Fehlverhalten der Routine zu verstehen. Deshalb kann ich Dir auch nur einen Anfang geben, den Rest musst Du interaktiv "erforschen", ansonsten wird dieser Thread noch wochenlang weiterlaufen... Sag mal... wie alt bist Du eigentlich, und hattest Du schonmal Informatikunterricht? (Ich frage das nicht, um Dich blosszustellen, sondern um Dir gezieltere Antworten geben zu koennen) Habe nun folgende Meldung in app.c eingebaut: // a useful debug message to print out temporary variables // disable it by changing "#if 1" by "#if 0" #if 1 MIOS32_MIDI_SendDebugMessage("Mod:%d Row:%d sr_pin: %d value:%d\n", mod, row, sr_pin, value); #endif [/code] Ausserdem habe ich mir die Funktion nochmal genau angeschaut, und dabei wohl den Fehler gefunden: die "changed" Variable war nur 8 bit (u8), Du benoetigst jedoch 16 bit (u16) Uebernimm bitte die komplette TASK_MATRIX_Scan() Funktion. Und schau' Dir die Meldungen im MIOS Terminal an - Du wirst ueberrascht sein, wie verstaendlich der Algorithmus auf einmal wird ;) Gruss, Thorsten.

Just checked the code visually - the change which has been done in MBSEQ V3 hasn't been merged into MB808 New release next week - please promise me that you will check it immediately and don't give me feedback months later when I'm working on totally different topics ;) Best Regards, Thorsten.

I will check this once I'm back home. Somehow I remember this issue, I thought it has been fixed... maybe it happened in MBSEQ V3 and forgot to take over the changes into the MB808 firmware Hasn't this been changed on request? From MBSEQ V3.4f changelog (code has been merged into MB808 firmware as well) o Groove function now takes the global step has reference instead of the local step. This results into better results on a non-linear step progression. Or do you mean, that the groove function doesn't work this way anymore? (Currently I can't test this...) Sneakthief: adding delays will result into a lot of effort at my side, especially since I haven't programmed PIC assembly for months. This can quickly result into many iterations even on simple changes, like demonstrated here: And it could result into new bugs, reported by users months later (as demonstrated by Nuke's response) Best Regards, Thorsten.

Nur nochmal als Bestaetigung - welche Events werden gesendet, wenn Du mit Deinen letzten Hardware-Fixes folgende Konfiguration verwendest: #define DIN_16x16_L0 12 #define DIN_16x16_R0 11 // DINs of second 16x16 matrix (counted from 1) #define DIN_16x16_L1 14 #define DIN_16x16_R1 13 // DOUTs of both matrices #define DOUT_16x16_L 1 #define DOUT_16x16_R 2 // (not swapped!) [/code] Dass immer noch die gleichen Events fuer die gleiche Spalte gesendet werden, verstehe ich nicht In meinem urspruenglichen "Quick&Dirty" Code war ja ein Fehler drin (pin_sr wurde nicht zur Note addiert), den hast Du selbst gefunden, danach funktionierte es angeblich... und nun nicht mehr? Ich habe den Fehler mittlerweile auch in meiner Vorlage korrigiert: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fquickies%2Fcsc%2Fapp.c Ob der Code fehlerfrei ist, kann ich natuerlich nicht sagen - habe die Hardware ja nicht vor mir liegen und kann es nicht selbst ausprobieren. Aber vielleicht hast Du auch mit Deinen eigenen Aenderungen einen Fehler eingebaut, der zu diesem Effekt fuehrt? Am besten setzt Du nochmal komplett auf meine Vorlage auf... Falls das nicht weiterhelfen: MIOS_MIDI_SendDebugMessage is your friend! -> http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F003_debug_messages%2FREADME.txt AIN an J16: die 4 Pull-Ups (R30a/b/c/d) duerfen nicht verloetet (bzw. in den Sockel gesteckt) werden. Gruss, Thorsten.

They are available, but only in quantities of 250 pieces. While the first 1250 GM5 chips were sold within one year, the last 250 pieces took another year. Since I'm not interested to stock GM5 for so long time anymore, it's very unlikely that another bulk order will happen. Best Regards, Thorsten.

Hallo Kevin, ja, das ist moeglich. Genauer gesagt: das ist sogar die Standardeinstellung - lediglich in setup_mb6582 werden auch die restlichen Buttons/LEDs als Matrix verschaltet, in allen anderen setups hat mit Ausnahme der LED Matrix jeder Taster einen eigenen DIN Pin, und jede LED einen eigenen DOUT Pin Die Pin-Nummern werden in eine Tabelle eingetragen (siehe bspw. setup_8580.asm) - wenn Du die Taster/LEDs genau so verdrahtest wie dort aufgefuehrt, muesstest Du kein eigenes .hex File bauen... Fuer das Standard-Pinning gibt es uebrigens auch Schaltplaene: http://www.ucapps.de/midibox_sid_cs/mbsid_v2_din_default.pdf http://www.ucapps.de/midibox_sid_cs/mbsid_v2_dout_default.pdf Gruss, Thorsten.

Hi Robin, great to know that this method is working at your side! :) I consider to standardize it, e.g. in MIDIO128 V3 Best Regards, Thorsten.

Hallo, die Bezeichnung von Pin #1 ist irrefuehrend, das wurde beim MBHP_CORE_LPC17 Modul zum Glueck rechtzeitig erkannt und verbessert. Wenn Du Dich an die Fotos haelst, wird das Display funktionieren :) Ohne SD Card ist die Konfiguration unter hwcfg/standard_v4/MBSEQ_HW.V4 eingestellt Gruss, Thorsten.

Yes, it's exactly the same MagJack! Since some people have ordered the PCB without an ethernet socket, I will have some spares. Update: almost all people already confirmed the order, money requests will be sent today - thanks for the easy handling of this bulk order! :) To ensure that the MagJack won't be damaged during transport, I'm planning to solder it on the PCBs. This will take the same time like packaging it properly. Best Regards, Thorsten.

Yes! :) You even don't have to take care if the LPCXPRESSO is powered through the MBHP_CORE_LPC17 module (means for example: LPC-Link and MBHP_CORE_LPC17 USB plugs connected to a computer) since there are protection diodes. Best Regards, Thorsten.

Now I've stuffed a module with (female) sockets as well - after I've shortened the Reichelt sockets with a file they fit. :) Note how I've soldered the male headers to the LPC-Link board. For users who don't own a common JTAG interface, it's recommended to solder them upwards so that the LPC Link can be connected this way: Here another picture which shows that the ethernet LEDs have to be connected via two wires to J26, since the LPCXPRESSO module doesn't provide dedicated pins for the two Ethernet Socket LEDs. (Ilmenator: J26 doesn't exist on the first prototype board) Best Regards, Thorsten.

I got the PCBs today - everything is working perfectly!!! :thumbsup: PMs with the ordering details will be sent later today. Final prices: MBHP_CORE_LPC17 PCB: 6.50 EUR MagJack: 3.50 EUR There are enough spares, if you are interested just follow these instructions: http://www.midibox.org/dokuwiki/doku.php?id=tk_mbhp_core_lpc17_bulk_order Best Regards, Thorsten.

jep Gruss, Thorsten.

Added the hint: http://www.ucapps.de/mbhp_core_lpc17.html (press refresh button to see the changes) Another note: personally I would prefer to use female sockets on the MBHP_CORE_LPC17 module, since this is compatible to the Base Board provided by Embedded Artists, and since it's more likely that I would replace the LPCXPRESSO module by a pin compatible module in future, than circulating it between different base boards. Best Regards, Thorsten.

An die DIN shift register gehoeren keine Bruecken, dadurch wuerdest Du die Eingaenge kurzschliessen. Es wird ganz normal mit Pull-Up Widerstaenden nach 5V verdrahtet. Gruss, Thorsten.

Thanks for this useful report! I will add a link from the MBHP_CORE_LPC17 page to this posting under the topic "strongly recommended, but not required if you are sure what you are doing". In long term - if kits will ever be provided for this module or for derivatives - matching sockets (which don't need the file work to shorten the sockets) could be sourced and added to the kit. Best Regards, Thorsten.

Thank you, this is very useful input! I never tried to supply the REF voltage from external, it's good to know that it works. Usually I don't take care so much about the temperature, but it shouldn't be higher than 350°C Much more important is, that you only tip some solder on the pins for a very short moment - not longer than one second! If the pin isn't properly soldered thereafter, tip again for another second. This is save enough. The REF voltage has to be *very* stable, and it shouldn't be affected by noise. Usually an external shunt or a small VR is used - the TLV5630 has an internal reference source to save these costs. So, this is only a workaround for the case that the internal voltage source has been fried somehow, but it will result into additional hardware. Best Regards, Thorsten.

Maybe Artesia can help with this. Best Regards, Thorsten.