Jump to content


Frequent Writer
  • Content Count

  • Joined

  • Last visited

  • Days Won


pilo last won the day on January 19 2015

pilo had the most liked content!

Community Reputation

4 Neutral

About pilo

  • Rank
    MIDIbox Guru
  • Birthday 04/16/1981

Profile Information

  • Gender
  • Location
    St Etienne, FRANCE

Recent Profile Visitors

1,514 profile views
  1. Salut! Tu peux poster des photos du circuit (des 2 cotés), comme te le suggérait ssp sur l'autre topic? (d'ailleurs ca serait peut etre plus pratique de centraliser les réponses dans un seul sujet, je pense celui en anglais, tu auras plus de retour ;) ) Tu as bien 5v entre les pattes 12/11, et 31/32 du pic? Et aussi entre 5 et 8 du 6N138? Essais de ne mettre que les circuit intégré essentiel, à savoir le pic et le 6N138 (en laissant les régulateur LM7805 et LM317), et rien d'autre que le midi in & out connecté (sans faders), et vois tu as plus de succès comme ca. Le cir
  2. Oh I didn't see there was multiple threads for this problem :) As I said in the thread inthe french forum, the module needs to be powered in order to work (only the midi connection is not enought).
  3. Alors si il faut alimenter le circuit via le connecteur J1, une alimentation entre 8 et 12v fera l’affaire (et peut importe la polarité, ça peut même être un simple transformateur car il y a un pont de diodes). Voilà, une fois alimenté ça devrait mieux fonctionner ;) la led s’allume ... je ne sais plus, je crois quand il y a des messages midi échangés, mais je n’en suis plus très sûre ! Et pour vérifier les soudures, il y a le schéma du module. La première étape serait de vérifier qu’il y a bien 5v où il faut (en sortie du régulateur 7805, et sur le PIC et l’optocoupleur).
  4. Salut Zennro! Alors oui il faut programmer d'abord le PIC avec le bootloader (bootloader_v1_2b_pic18f452.hex) et un programmateur , ce que vous avez fait avec succès à priori? Ensuite il faut uploadé MIOS (mios8_v1_9h_pic18f452.hex ) via MIOS Studio. Mais effectivement pour ca il faut que MIOS Studio "voit" le pic : vérifiez que MIDI IN et MIDI OUT pointe bien vers les bonnes entrées/sorties et interface sur laquelle le MF_NG est branché, et que ce dernier est bien alimenté. Il est aussi possible qu'il y est un soucis sur le circuit, un problème d'assemblage... Ah aussi, si vous
  5. It looks very nice! Can't wait to the see the inside :)
  6. pilo

    EA LPC1769 Revision

    Yes ;) Actually I noticed it didn't fit after I soldered the pin headers... So I removed the plastic, and bend the pins.
  7. pilo

    EA LPC1769 Revision

    Hi! It's possible to bend the pin to make them match the MBHP PCB, that's what I did. But I think it's better if you can get a rev B! You can find some pictures of my bending here : http://midibox.org/forums/topic/18552-lpc1769-rev-c-different-layout-than-rev-ab/?page=2#comment-167161
  8. pilo

    OLRE16, in colors.

    It looks really great! I removed led rings from my design because I though it was almost impossible for me to fit them in 1.1in channel strip and looks good. But it seems you managed to do it?
  9. Hi @tago Yes, you can print text using different font faces and sizes. It's not part of MIOS, but works by using bitmap drawing MIOS functions. It's still a bitmap font system, TTF have to be exported to bitmap, so it takes a little bit of memory for each font faces and size. Also it's not a full featured font system, for example it doesn't support kerning (could be added, but will take even more memory). If you want I could set up a better example (the one I posted was just a quick test).
  10. pilo

    LC clone

    Work in progress
  11. Hi everyone! I thought it might be a good idea to be able to print variable width font on GLCD. I wrote a simple example using this (see pictures and code in vfw.tar.gz). I don't think it was done before with MIOS? (I made a quick search). The font bitmap are exported from TTF file using a very quick (and ugly) C program based on Freetype (it might be Linux only... Freetype was an easy option for me, and a good font rasterizer). It takes as input the TTF file and a size, which is then exported as a .c file, which can then be included inside MIOS app (one file per font and size). font.c
  12. Hi! I'm not sure if I understand your problem correctly, but it seems like a general code design problem? If I understand well, you have things that should happen when there's a Midi notify or a button press? A simple way to handle this is simply putting the code that does something outside the MIOS call back : void doSomething(u32 value) { // put your code here } void APP_MIDI_NotifyPackage(mios32void APP_MIDI_NotifyPackage(mios32_midi_port_t port, mios32_midi_package_t midi_package){ if(/*condition*/) { doSomething(1); // or doSomething(0) } } #define doSomethingButton 4
  13. Thank you ;) When i said it might be a hardware issue, I was thinking about something like wiring issue. I fried my testing psu (for the analog +5/-5v) yesterday while working on this, I might have made a modification to the code that prevent it from working after (I wrote the value to dB code after my PSU made some smoke). Also it would be a shame both your PGA chips are broken. I think before ordering new ones there are other things to check ;) First, I use lpc17 core, I don't think it should make a big difference, but maybe it is. Then how did you wire your power supply? I use t
  • Create New...