Marxon

Programmer
  • Content count

    474
  • Joined

  • Last visited

Everything posted by Marxon

  1. Servus Midiboxer! Der Titel sagt eigentlich schon alles :) Natürlich gibt es auch eine Aufwandsentschädigung in Form von Bauteilen oder Geld. Mfg Marxon
  2. PIC18F4685 configuration bits ?

    Problem solved!  I found a tool called PICPgm which supports my old Willem parallel port programmer  (the manufacturer software doesn´t support 18F4685) and burned my PIC without any problems. Have a nice day!   Best regards Marxon
  3. PIC18F4685 configuration bits ?

    Hi,   this topic is a bit older but i'm facing the same ID problem with my G540 programmer. There is also no option in software to reconfigure the programmer so that only the first 4k block will be overwritten. Since the baud rate is set COM, would it not be possible to upload the workaround somehow via a LTC module? Thanks for your help.   Best regards Marxon
  4. Hi TK I just wanted to buy you one or two beers and realized that there is no "Buy TK a beer" button anymore. Have you renounced the alcohol? ;) Best regards Marxon
  5. Where is the "Buy TK a beer" button gone?

    Yeah the signatures are back again.
  6. Where is the "Buy TK a beer" button gone?

    Aber kein Alkohol ist auch keine Lösung. In plain english: But no alcohol is no solution, too.
  7. Yes they look very nice! The same button are also used in my Quasimidi 309. But they are so expensive :( This is my low-cost variant: http://midibox.org/forums/topic/17186-yaib-yet-another-illuminated-button/ Best regards Marxon
  8. Cleaning your Boards

    I also tried Isopropyl but I could not achieve the same results.
  9. Cleaning your Boards

    Hi Midiboxers, i asked my electronic dealer of trust for something to clean my boards. He advised me this: "PCC" from Kontakt Chemie. It was quiet expensive 12€/200ml But this stuff is really amazing and very, very fertile. Unfortunately i have cleand all my boards now so i can not show you some "before/after" pictures :smile: I will post some later. Best regards Marxon
  10. BLM 16x16+X PCB and case order [CLOSED/waitlist]

    Hi all! I am very sad becaused i missed this bulk order. If someone changed his mind and does not want his 16x16 board anymore please let me know :) Nevertheless have much fun with your boards! Best regards Marxon
  11. BLM 16x16+X PCB and case order [CLOSED/waitlist]

    Damn! I visit the forum regulary but missed this bulk order. If there are any PCBs left i wouldt buy them instantly. Best regards Marxon
  12.  Hi Midiboxers,    while i was tinkering with my midiboxes i wondered if it would be possible  to use a Midibox NG to simulate a encoder. Something like an "encoder generator" simply by using a Dout board and a .NGR script.  Some quadrature encoder signal may could be generated like this: if ^section == 1 set LED:0 0 delay_ms 2 set LED:1 0 delay_ms 2 set LED:1 1 delay_ms 2 set LED:2 1 delay_ms 2 set LED:0 0 delay_ms 2 set LED:1 1 delay_ms 2 endif I guess connecting DOUT pins directly to the encoder inputs on the destination device requires some kind of adjustment but should work too? What do you think? Is something like that in genaral possible? Best regards Marxon
  13. MIDIbox NG Release + Feedback

    Hi FantomXR try if this works like you expect. The channel select buttons will run a script (to activaon press .NGC #CH2 EVENT_BUTTON id=1 hw_id=1 type=Meta meta=runsection:1 range=127:0 button_mode=OnOff EVENT_BUTTON id=2 hw_id=1 type=Meta meta=runsection:2 range=0:127 button_mode=OnOnly #CH3 EVENT_BUTTON id=3 hw_id=2 type=Meta meta=runsection:3 range=127:0 button_mode=OnOff EVENT_BUTTON id=4 hw_id=2 type=Meta meta=runsection:4 range=0:127 button_mode=OnOnly EVENT_KB id=1 hw_id=1 type=NoteOn chn=1 EVENT_KB id=2 hw_id=1 type=NoteOn chn=2 EVENT_KB id=3 hw_id=1 type=NoteOn chn=3 .NGR #CH2 if ^section == 1 LOG "CH2 deactivated" set_active (id)KB:2 0 endif if ^section == 2 LOG "CH2 activated" set_active (id)KB:2 1 endif #CH3 if ^section == 3 LOG "CH3 deactivated" set_active (id)KB:3 0 endif if ^section == 4 LOG "CH3 activated" set_active (id)KB:3 1 endif   
  14. SCS display and ssd1306

    Hi sprintf, unfortunately it is not possible to mix display types. AFAIK Hawkeye and nILS made a working SSD1322 and SSD1325 driver for theire projects. If you really want to use different displays, you can connect them to multiple cores.  
  15. *Request* button_mode=OffOnly

    Hi Novski, thanks for your suggestion! Your inverted range get me on the right path. Last night I did not come up with the idea. This is working:    ### BUTTON PRESS EVENT_BUTTON id=1 hw_id=3 type=Meta range=127:0 button_mode=OnOff meta=runsection:1 ### BUTTON RELEASE EVENT_BUTTON id=2 hw_id=3 type=Meta range=0:127 button_mode=OnOnly meta=runsection:2It allows to run two different scripts on button press and button release. Until now i used a if/then statement in my .NGR script wich was probably not very CPU friendly. ### .NGC EVENT_BUTTON id=1 hw_id=1 type=Meta range=0:127 button_mode=OnOff meta=runsection:1 ### .NGR if ^section == 1 if (id)button:1 == 0 LOG "BUTTON RELEASE" else LOG "BUTTON PRESS" endif endif  Best regards Marxon
  16. *Request* button_mode=OffOnly

    Hi TK, would you please add also a "OffOnly" mode for buttons? A way to start a ngr on button press and a other script on release would be just as helpfull. Thank you very much! Best regards Marxon
  17. NRPN - "current instrument"

    Hi Thorsten You are genius! After more than three years reminding you, you come up with it without warning on a sunday afternoon. :) I would love to test it right now unfortunately i am already on the way to work. But it looks exactly like what i've wanted. Really great! Thank you! Best regards Marxon
  18. NRPN - "current instrument"

    Hi everybody, i have some question about controlling these "current instrument" parametes via NRPN: How do i change which is the "current" one in different engines? According to the manual: "...the final destination depends on the selection on the control surface, or on the MIDI channel..." I tried different midi channels and also all edit screens, but its allways controlling instrument 1 Thanks for help Marxon
  19. NRPN - "current instrument"

    Hi TK! Is there still hope that the current instrument can be selected via NRPN? Best regards Marxon
  20. Led wiring

    Thank you Thorsten! A friend has my first FM synth so i couldt not check how i wired it there. I edited the cs_menu_io_tables.inc so that the pin order matches the "MIDIbox FM CS DOUT map" schematics. (It is just a other pin calculation, so please do not laugh)   DIO_M_COL_ENTRY MACRO sr0, pin0, sr1, pin1, sr2, pin2, sr3, pin3, sr4, pin4, sr5, pin5     db    ((7 - pin0) + 8*(sr0-1)), ((7 - pin1) + 8*(sr1-1)), ((7 - pin2) + 8*(sr2-1)), ((7 - pin3) + 8*(sr3-1)), ((7 - pin4) + 8*(sr4-1)), ((7 - pin5) + 8*(sr5-1))     ENDM DIO_M_ROW_ENTRY MACRO sr_in, pin_in, sr0, pin0, sr1, pin1, sr2, pin2, sr3, pin3     db    ((7 - pin_in) + 8*(sr_in-1)), ((7 - pin0) + 8*(sr0-1)), ((7 - pin1) + 8*(sr1-1)), ((7 - pin2) + 8*(sr2-1)), ((7 - pin3) + 8*(sr3-1))     ENDM cs_menu_io_tables.inc There is also a writing mistake about the CAN bus pins in the setup*.asm files:     Best regards Marxon
  21. Led wiring

    Hi all! I am a confused about the FM led wiring. In the DOUT schematic the intrument and operator LEDs are connected to-SR2 D6 and SR D7. It is not possible to change the pin configuration for these LEDs in „cs_menu_io_tables.inc“. But here SR2 D6 and SR D7 are assinged to matrix Col1 Col2 instead. Which configuration is correct? Best regards Marxon
  22. Led wiring

    Hi again!     It seems that the DOUT pins of the matrix get mirrored somehow. In my Midibox FM i connected LED column 1    SR 3    Pin 4 LED column 2    SR 3    Pin 5 LED column 3    SR 3    Pin 6 LED column 4    SR 3    Pin 7 LED column 5    SR 2    Pin 0 LED column 6    SR 2    Pin 1 LED row    1    SR 2    Pin 5 LED row    2    SR 2    Pin 4 LED row    3    SR 2    Pin 3 LED row    4    SR 2    Pin 2 but in cs_menu_io_tables.inc i have to define it: DIO_M_TABLE     ;; --> DIN <-- pins of the 6 column select buttons     ;;         Col1 SR/Pin, Col2 SR/Pin,  Col3 SR/Pin,  Col4 SR/Pin,  Col5 SR/Pin,  Col6 SR/Pin     DIO_M_COL_ENTRY  3, 6,        3, 5,         3, 4,         3, 0,         3, 1,         3, 2     ;; --> DOUT <-- pins of the 6 LED columns     ;;         Col1 SR/Pin, Col2 SR/Pin,  Col3 SR/Pin,  Col4 SR/Pin,  Col5 SR/Pin,  Col6 SR/Pin     DIO_M_COL_ENTRY  3, 3,        3, 2,         3, 1,         3, 0,         2, 7,         2, 6     ;; --> 1*DIN/4*DOUT <-- pins of the 4 row select buttons     ;;         DIN SR/Pin,  Row1 SR/Pin,  Row2 SR/Pin,  Row3 SR/Pin,  Row4 SR/Pin     DIO_M_ROW_ENTRY  3, 3,        2, 2,         2, 3,         2, 4,         2, 5    
  23. RGB colour matrix (8x8)

    Now you have a similar situation like before. Leave out the rgb parameter in the led event because it is already forwarded by the button event and by what you said, it seems that the forwarded value has a lower priority.
  24. RGB colour matrix (8x8)

    Maybe the dimmed parameter conflicts with the rgb parameter. Try to delete the dimmed parameter
  25. RGB colour matrix (8x8)

    Hi, you have set the first DOUT shift register in your DOUT matrix and your DIN matrix.