FantomXR

Members
  • Content count

    784
  • Joined

  • Last visited

Everything posted by FantomXR

  1. Another MIDIbox core

    Hey people, since I'd like to be independent from the availability of the STM32F4-discovery board I started designing my own board, which has an STM32F407VGT6 on board. Its an LFQP 100 package, so not easy to solder. I have a reflow oven and the first PCB I made seems to work fine. The PCB has very few components. This was just a quick test board to see if the basic circuit of the STM32F4 is working. It's basically just the STM itself and it's components like caps and crystal. Also there is a 3.3V regulator (based on 1117 but will change to TC2117) to power the uC. I added a pinheader for USB connection (on the very left), a pinheader for SWD to flash the bootloader and a reset-header.  On the right you see the HCT541, which connects to J8/9 (tested: works fine). Also I added an MCP3208 and HC595 for an AINSER64-like-analog-scanning.  On the bottom of the PCB there is a MicroSD-slot.  No changes in the firmware are needed to use this. The only thing one need to do is flashing the bootloader the first time. @latigid on made a nice "how-to": http://wiki.midibox.org/doku.php?id=wcore After that you can use the MIOS as is. So, why I'm telling you this?  This core is already very specific for my applications. But if you are interested I could upload the minimal circuit for the STM32F4 to work and you could add all headers and components that YOU need by yourself. So in theory you could recreate the original MIDIbox core but you should end up with a much smaller footprint (especially regarding height).  If you need assistance regarding soldering the STM32F4 I can offer to reflow-solder it for you.  I'll clean up my circuit and upload it the next days!   Best, Chris
  2. AINSER deadband configuration?

    @Zam: Just a quick note on this: I tested several things on my PCBs but I was not able to get rid off these value-jumping-issues when changing the colors on my WS2812B. After researching I found a little chip called MCP1541 from microchip. This generates a super stable reference voltage for the MCP3208 out of 5V. Even out of the noisy USB-5V. And this solved all problems. Such a great IC. Also very low component count. MCP1541 + 2 caps and you are done.   
  3. AINSER deadband configuration?

    Hey people, I searched the NG-firmware for the parameter, which set's the deadband of the AINSER-inputs. I found this: #define MIOS32_AIN_DEADBAND 31 But if I change that to f.e. 100 or more it doesn't change anything. My problem is, that my slide potentiometer have some jittering (even when the pinrange is set) when they are not at 0 or 127.  I also found the parameter #define MIOS32_AIN_IDLE_CTR 3000 But changing this value also doesn't make any difference. Does anybody know where to set this value? Thanks, Chris
  4. search 4 OLED LCD

    How many do you need? I just received 40pc.
  5. is the STM32F4 EOL?

    @Alasdair Moon The discovery board is now available again on mouser.
  6. Waveshare Core

    My prototype-PCB arrived yesterday. I set up my reflow oven and gave it a go. I'm very happy with the result. LQFP100 is really small. But it's working! Apart from some changes I needed to make on the 3.3V power supply, it seems that I have the minimal circuit working. :-)
  7. is the STM32F4 EOL?

    I just created a design for a core by myself and ordered it. It's downstripped (has just J8/9 + MicroSD-card reader on board) because I want to test the basic functionality of the circuit first. I'll keep you posted if it runs fine :-) If the design works, it can be easily extended to other people needs.
  8. Replace SD-CARD with FRAM?

    Hey people, just a short question: Is it possible to replace the SD-Card with another kind of memory f.e. FRAM?  Thanks, Chris
  9. is the STM32F4 EOL?

    @Alasdair Moon: Sorry! You are right... damn it!  But yeah, looks like latigid on seems to have a solution for that.
  10. is the STM32F4 EOL?

    https://www.mouser.de/ProductDetail/STMicroelectronics/STM32F407G-DISC1?qs=sGAEpiMZZMvt1VFuCspEMrjE4TO0IyBBeNQ%252bgqeMpN8%3d Take this one ;)
  11. Midibox_NG and kb_transpose

    Easy task! Just create two EVENT_KBs with different ids but same hw_ids and set them to different channels. Regarding your second question: I think TK implemented a Learn-function a while ago. Maybe this works with KBs too. Search here for "learn": http://ucapps.de/midibox_ng_manual_ngc.html
  12. SCS encoder jumps

    I use PEC16 without issues. 
  13. SCS encoder jumps

    Hi! Yes, there is a debounce_mechanism: SRIO debounce_cycles=<0..65535>   Anyway: Improving the hardware should be better than software debouncing. 
  14. Smaller alternative to discovery-board?

    I'm building a lot of keyboards with MIDIbox and space is a problem at any time. So the main reason is, to create a PCB, that has just those components on board, which are necessary for that application (including the shift registers for scanning). This would save space and cables. Like I said: The Wavecore seems to be a huge improvement already. So I'm curious if latigid is willing to share his project ;)  Maybe you are right: I could go through all schematics of those boards which are on the market. But as you said: This is really time consuming. I took a look into the waveshare-407-schematic. This looks promising! Very few parts and a good oversight. The datasheet of the disco-board is really killing...
  15. Hey people, I took a look into the drivers that come with MIOS. It seems that all STM32F4xx could be supported. Is that right?  I ask because I'm looking for a smaller alternative to the DISCOVERY-board which has a big footprint. Here f.e. you can find a much smaller board with has a STM32F405 on board: http://re.reworld.eu/de/produkte/s64dil-405/index.htm Any informations on this? Best, Chris
  16. Smaller alternative to discovery-board?

    Thanks for your suggestions! @latigid on: Your design has a big advantage: I hate those Micro-USB connectors on the DISCO-board. So this will be a huge improvement. Also it looks a bit smaller as the DISCO-board. How about the PCBs? Do you plan to upload the layout?  I designed my own breakout-board for the DISCO-board. So it has a bunch of connectors that the MIDIbox-core doesn't have. Also some regulators and another micro-sd-card slot. I'd like to take your design, make those changes and give it a try. Is there any chance to get the eagle-files from you? @Antichambre: I've read in the link you posted that you already designed an own stm32f4-PCB. Any progress on this? To be honest: I'd really like to create my own stm32f4-PCB. But I have no clue about what is needed for a minimal circuit. Your PCB looks like it has everything on board and I just need to make my modifications to it. SMD soldering is not a problem. I have a reflow oven. We could also think of a core, that is especially made for midibox-users. I could make them in my reflow oven and sell them to others if there is any interest. 
  17. Fast trigger option for organ keybeds?

    Same here! Please see here:  
  18. Hey people,   I want to use a fatar TP8/O for playing organ sounds. As every keybed, it has two switches to calculate the velocity. Is there an option, that allows to fire a "note on" already when the first switch is pressed? Real hammond organs do react very fast. You don't have to press down the key a lot to play a note.   This would be nice :) Thanks, Chris
  19. Why should it not? If you add some DINX between the two DIO-modules you just have to change the values for the shift-registers in the NGC-file. 
  20. Fast trigger option for organ keybeds?

    Hi Frank, yes. That is possible. You can achieve that by using a NGR-script, that sets break_is_make on. This script you need to trigger with the switch.
  21. Midibox_NG Event NoteOn lost

    Hm... I'm using NG in keyboards for a few years now and as far as I remember I never had the issue, that notes are not being played. I enable make_debounce on my keyboards. Without that sometimes note-off is not being send (IIRC).  As NG does not support 3-contact-keybeds at the moment it needs both contacts to be opened before sending the next note-on. Without both switches opened NG can not calculate the velocity so it's not being send.  If "break_is_make on" works for you, it's quite clear, because break_is_make doesn't wait for both switches to be released.
  22. Hey out there, because the ones on the market are very exepensive and not fitting my needs, I decided to use Eagle, to design an own PCB. I never did a PCB before, so please be kind. I'm happy if you have any suggestions, to make it better. I want to create different PCBs with one encoder, two, four and eight. But at first I need to know, if I did any mistakes in the schematic. So please take a look at the pictures. When everything is ready, I will contact a pcb manufacture to get some prices and will start a bulk order, if other guys are interested in this too. To save space I used 4x 8pin header. They will be mounted on the bottom. I used 16x 0805 SMD LEDs. The encoder is a STEC12E06, because this was the only one in the library and I don't have my encoders yet to create a device by myself. Hint: Look on ebay. I bought 45x encoders ALPS EC11 (don't have the exact modelnumber) for around 30,- EURO. Because the encoders have a thread, I don't need mounting holes but I can add them anyway. There should be enough space in the corners So, any suggestions? ;) Best regards, Chris
  23. Fatar 61 key keybed controller question:

    My tests with NG vs KB had the result that no matter what I change in the official NG-app, I'll never get those fine velocity steps, that KB gives. So I created my own NG app and kicked out all of the functions, I do not need. There is a thread about it in this forum. Just use the search engine and you'll find it quick.  Anyway: I still feel, that KB outputs more velocity values as my NG does still. So I think it depends on your needs.  Btw: please be aware, that there is no octave shift function (regarding if NG or KB) yet 
  24. Problems with OLEDs over time

    Yes @Zam you are right. I had issues with those LEDs. But since I use a separate PSU for the LEDs the problem is gone! ;-) Well, I'm still not able to run the faders in 11bit because of jitter (regardless if the LEDs are connected or not) but I really don't need that. 7bit is sufficient.... and thats another topic ;-) I also made a design-mistake: The VDD-traces on the LED-PCBs are way too thin. I used about 0,6mm which might not be enough for this current. I expect a current of above 2A when changing the color for the LEDs. Of course I never run them at full brightness! Then they would draw MUCH more.  But yes: If you think we would be able to make something "better", than start another topic. I'm happy to help! (but I'm on vacation from tomorrow on ;-) )
  25. Problems with OLEDs over time

    Hey people, I have some problems with my OLEDs. Technical background: The OLEDs are mounted on a PCB and powered through a stable 5V power supply (they can be powered with 3.3V or 5V). Each OLED has a 1k resistor between RST and VDD and a 10uF cap between RST and VSS. The OLEDs are triggered by NG. In NG I've added several receivers and senders, which translate sysex-streams into labels. That works very well... but! I uploaded a picture where you can see the problem. Sometimes after using the MIDIbox for a while I get those errors. I'm really not sure what the problem is. I need to powercycle the midibox, to "reset" the displays. As you can see the whole label gets moved down and it will NOT reset by sending new sysex-events.  So, do you have an idea? Is it something in the firmware or is it hardware? Maybe also @TK. can help ;-) Thanks!! Best, Chris