• Content count

  • Joined

  • Last visited

Community Reputation

27 Excellent

1 Follower

About FantomXR

  • Rank
    MIDIbox Guru
  1. dipCoreF4 and dipBoardF4, a compact Core.

    I'll look into it ;-) You don't have any suggestions which pins I can use? :-)
  2. dipCoreF4 and dipBoardF4, a compact Core.

    Got you... but changing the pins for SPI2 in MIOS32 firmware shouldn't be that hard. So I could move those functions to other pins. But I don't have a clue how to implement that second USB port in the firmware... and I assume you don't want to share this informations which I can totally understand.
  3. dipCoreF4 and dipBoardF4, a compact Core.

    My mainboard uses the 407. Hm... there is still something I do not get. The discovery-boards use the micro-USB-connector for USB-Host-Mode. That means, when connecting a device (mouse or MIDI controller) to the discovery-board via this board it's not possible to connect to the core itself through USB (because the USB-port (PA12 & PA13) is blocked through the device). But in your video I see that you still have your core connected through USB to the computer. How did you do that?? :-) 
  4. dipCoreF4 and dipBoardF4, a compact Core.

    Hey Bruno, I'd like to connect another USB device (mouse or midi controller) to my core. :-) Like in your video...
  5. dipCoreF4 and dipBoardF4, a compact Core.

    @Antichambre I'd like to integrate such feature onto my mainboard. Are you willing to share the schematics and if necessary the code?  Any feedback is very appreciated. Thanks! Chris
  6. No one? Any help would be very appreciated! 
  7. Hey people, here is the problem: FATAR has changed the diode-matrix of their keybeds recently. So the DIO-matrix is not usable for those keybeds anymore. I want to get it running and of course I'm happy to design a new DIO-matrix and of course post it here so everybody can use it. So... I'm not 100% sure about the diode-matrix yet. In the old diode-matrix both keyboard sides (left and right) had separate rows. So the left side had 8 rows, the right side had 8 rows: Look at this pictures. With "rows" I mean T0-T7.  In the new diode-matrix it looks like both sides use the same rows. Because if I plug in a new keybed (via an adapter) into a DIO-matrix (which I did many times before with old keybeds though old diode-matrix) it outputs correct values from a-1 (lowest key) till middle-C. With the next key C#3 the left side starts. But C#3 outputs a-1. Further tests confirmed my assumption, that both sides share the same set of T0-T7.  So that means: I need a shiftregister more than is available on the DIO-matrix. At the moment I have T0-T7 connected to the 8 inputs of the HC165, MK&BK are connected to the 16 outputs of the two HC595s. So in total I can connect 64 keys to the DIO-matrix. I now want to add another 595 to connect the last keys. Of course connecting the 595 itself is easy and done quickly. But I need to adapt the code and what I've tried so far was not working. I need to add a dout_sr3 to the code... Any help?? Maybe @TK. could point me in the right direction! Thanks people! Best, Chris
  8. Online Gerber Viewer

    Dear Bruno, no I didn't try them. Actually they are located in the Netherlands as far as I know. I order all my stuff at elecrow in China. Fast, reliable and very cheap.
  9. Online Gerber Viewer

    Hey people, for those of you who are looking for a nice online gerber view, I can recommend AISLER: You can either upload the gerber files, but they do accept also right away eagle-brd.-files which makes it very easy to visualize it. Prices seem a bit expensive. But anyway: for visualizing the PCB this is the best tool I've ever seen. Best, Chris
  10. midi socket 5pol Din 180°

    A while ago I ordered those midi connectors and I’m happy with it. anyway: I think it’s hard to tell if those connectors are good or not. They look good and they feel nice. The midi plug has a tight fit. But apart from that? How should they differ from Kycon? If you want I could send you a few samples of those. I ordered 50pc a few weeks ago. 
  11. Blink LED with NG (Code-Sharing)

    Hm... I know how to create a meta-command. But I don't know how to refer to a timer within a meta-command. Maybe you could explain how to set up a simple timer and I'll see if I can implement that? Thanks, Chris
  12. delay function

    Do you send single note off events? This is not necessary. I assume that Thorsten took care of the classical MIDI implementation.  If you send CC #123 from NG to KB, KB should interpret this as "All notes off". This should speed up the process significantly. 
  13. delay function

    Not without programming a timer in RTOS.   
  14. Blink LED with NG (Code-Sharing)

    Hm, good point! I tried to implement such thing via RTOS... but this seems to be above my skills.
  15. Blink LED with NG (Code-Sharing)

    You could also do a "fade": if ^section == 2 if BUTTON:1 == 127 set LED:2000 127 endif if BUTTON:1 == 0 set LED:2000 0 endif if LED:2000 == 127 set LED:1 20 set LED:1 20 delay_ms 20 set LED:1 25 delay_ms 20 set LED:1 30 delay_ms 20 set LED:1 35 delay_ms 20 set LED:1 40 delay_ms 20 set LED:1 45 delay_ms 20 set LED:1 50 delay_ms 20 set LED:1 55 delay_ms 20 set LED:1 60 delay_ms 20 set LED:1 64 delay_ms 20 set LED:1 60 delay_ms 20 set LED:1 55 delay_ms 20 set LED:1 50 delay_ms 20 set LED:1 45 delay_ms 20 set LED:1 40 delay_ms 20 set LED:1 35 delay_ms 20 set LED:1 30 delay_ms 20 set LED:1 25 delay_ms 20 set LED:1 20 delay_ms 20 exec_meta RunSection:2 endif if LED:2000 == 0 set LED:1 20 endif endif