• Content count

  • Joined

  • Last visited

Everything posted by FantomXR

  1. AINSER + CLCD display = more analog jitter

    I'm quite sure you can leave it away if using an external PSU. I've never used it in conjunction with MCP1541.  I think the resistor should "decouple" the VRef from Vdd somehow. But I don't know anything about the technical background. 
  2. Elrom Teaser :)

    What kind of switches you will use?  
  3. AINSER + CLCD display = more analog jitter

    I don't know. I can't see in the datasheet if 5V input voltage is enough... so, try it and please report back.
  4. AINSER + CLCD display = more analog jitter

    Well... at least for me it solved all problems :-) 
  5. AINSER + CLCD display = more analog jitter

    I use this method a year or so on different cores with different configurations. My last build was a faderbox with 9 100mm faders which can send 10bit resolution with USB-power. If you only need 7bit, there shouldn't be any problem. Yes, it has 4V Output. Of course 5V would be better. But as @Zam already said: You can not really clean up 5V USB and end up with 5V. You will loose something. I'm okay with it, because it works perfectly. Even on breadboard. No need for a high-precision PCB-design to get this working. Just try it. It costs just a few cents.  I have a few capacitors connected to the USB-5V-rail and an inductor in front. But even that is not necessary. My earlier designs didn't have that filter-caps and worked very well too. 
  6. AINSER + CLCD display = more analog jitter

    The solution is easy: Go and get a MCP1541. You connect USB 5V to the input and it's output you connect to the VREF input on the AINSER8 (of course you need to cut the trace between VREF and +5V on the AINSER) and to the all analog controls that are connected to the AINSER8.  This little IC solved all my problems I had with jitter. Especially when running just at 7bit, this should do the trick.
  7. Strange... Could you please upload an image from the core-module? Maybe there is a jumper missing on the discovery-board itself?  Also you don't need both USB-connectors for uploading that firmware. The micro-USB should be enough. 
  8. 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": 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
  9. OLED: Stream longer than pixels on display

    So in case I have another sysex-stream assigned to the 2nd line this would also get overwritten? This is also no solution for me :-(
  10. Hey people, I have a question: I use OLEDs with a resolution of 128 x 64. I use them in a row. I set up a sysex-stream which shows text on the displays. This stream is set to lcd(1:1:1).  If the text takes more space than 128px, the rest gets printed on the next screen(s). I know that this could be useful. But not in my application. Can I somehow disable that? I took a look into the code but I didn't find it yet.  Each OLED should get it's own stream. If I do not push the streams in the correct order (f.e. first stream 2 => OLED 2 and then stream 1 => OLED 1) it will overwrite stream 2 of the 2nd OLED. Thanks, Chris
  11. OLED: Stream longer than pixels on display

    And what happens with the text when it exceeds 128px? Wordwrap? Or discarded? 
  12. Fatar TP/40L Midification

    Great! Looks good! :-) Strange keybed... from C to B?
  13. Hey people, I have a question: I have made my own MB_NG & KB-application. Now I want to save only the files that are needed to "make" this firmware into a separate folder to keep the oversight.  Does anybody know how to do this? I'm on OSX and work with XCode.  Thanks, Chris
  14. MCAN

    Looks like an awesome feature! A perfect way to connect two or more midiboxes without adding latency! Thanks for sharing! :-) I'll give it a try also...
  15. Hey people, I try to understand how the DIN is even working in the STM32F4-Core.  PB14 is not going through the HCT541 buffer. It goes directly into the IC. If I understood it correctly the purpose of the HCT541 is to do a level-amplification. It takes the level from the STMs outputs (which is 3.3V - 0.4V for HIGH for CMOS or 2.4V or TTL) and amplifies them. As the HC165 and HC595 are powered from +5V they need 3.15V to see a HIGH-signal. As the HCT541 delivers 4.5V for HIGH the HC595 does of perfectly work. But why do the HC165 even work? As I said it doesn't get an amplification. So in theory the HC165 sees 2.9V for HIGH but that's not enough so it should stay LOW and doesn't work. But it does... Can someone explain this behavior? Thanks, Chris
  16. Why does the HC165 even work?

    Oh dear... thanks for clearing my mind! ;-) BTW: Do you watch this forum all day? ;-) 
  17. dipCoreF4 and dipBoardF4, a compact Core.

    I'll look into it ;-) You don't have any suggestions which pins I can use? :-)
  18. 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.
  19. 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?? :-) 
  20. 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...
  21. 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
  22. 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
  23. No one? Any help would be very appreciated! 
  24. 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.
  25. 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