• Content count

  • Joined

  • Last visited

Community Reputation

123 Excellent


About Antichambre

Profile Information

  • Gender Male
  • Interests Create.

Recent Profile Visitors

1,854 profile views
  1. Why does the HC165 even work?

    lol Yeah I've got some default pages opened when my computer is switched on, all my email boxes, messenger and midibox forum! My computer is always switched on when I'm home. And I work 80% of the time at home so. ;)
  2. Why does the HC165 even work?

    ?? QH pin which is connected to the STM on SI, is an output! It sends 5V cmos level to the STM, the inputs pin of the STM are '5V tolerant' then you don't need level shifting down in this way(165 to STM).  
  3. Then you can use a chip which is made for that: Its a 64 sensor input(8*8 matrix). It has a SPI port, easy to interface with any Core. You need only one IC for less than 8€. Best regards  
  4. midiphy SEQ v4+

    Hey, If you need more just tell me ;) Best Bruno
  5. And a single CPU, an STM32F4 to take advantage from the MIOS32, AND good ADC with multiplexed input? An 8 inputs ADC with eight (8:1) multiplexers will give you 64 inputs ;)
  6. dipCoreF4 and dipBoardF4, a compact Core.

    No I can't, it depends on the functions you need on your 'mainboard' and the ones you already mapped. Best Bruno  
  7. dipCoreF4 and dipBoardF4, a compact Core.

    No no there's no problem for that, this is just a bit dirty in code for the moment, and I have to complete it, I didn't write any callback installer for the HID for example, this is toDo. I can share, I already shared it with my dipCoreF4 beta testers ;)
  8. dipCoreF4 and dipBoardF4, a compact Core.

    In this extended chart you can see the functions available for each pin, (It's from stm32f4 documentation.)
  9. dipCoreF4 and dipBoardF4, a compact Core.

    In MIOS32 the problem with the 407 is that the pin for the second USB(OTG_HS) are used for SPI2 which is your J8/9 Spi port. Then on the dipCore I moved the SPI function to other pins . AND I implement it in MIOS32 ONLY for the DipCooreF4. In MIOS32 the DipCore has is own pinout and functions.  
  10. dipCoreF4 and dipBoardF4, a compact Core.

    You want two USB with HID support. Which uC you use on your 'mainboard'? I implemented the second OTG HS for the STM32F405RG, coded in MIOS32 with/for the DipCoreF4 pinout. I just put an STMPS2141STR as protection, the same as Disco one.    
  11. dipCoreF4 and dipBoardF4, a compact Core.

    Hello Chris, Which feature do you need? Best Bruno
  12. CORE_STM32F4 Module, LCD, and fire

    to cut yourself cleanly ;) , eagle files    
  13. CORE_STM32F4 Module, LCD, and fire

    Workaround at osh park for castellation. Use micromatch as low profile connector eagle files Best regards Bruno  
  14. MCAN

    I will do ;) More than that I have to complete, error handling and field filtering for enhanced mode. Best Bruno
  15. MCAN

    @ALL .About the MCAN MCAN, MIDIbox Controlled Area Network Low cost MIDI(Native) Network using CAN, this is MCAN…   2 cores interconnected with simple 'One Wire'. But you can add more: 2 wires in fact, we need a short common ground too. Bus length is limited to a total of 45cm. Unknown maximum number of Cores, but 4 is suggested.   3 interconnected Cores with CAN Tranceivers: Cables between the MCAN modules are RJ12, I use molded high speed ADSL cables from supermarket. First RJ12 connector is IO, second is a Loop Thru. If loop is not used each MCAN module has a 120 Ohm terminator switch. First and last nodes must have terminator ON. Bus length is limited to a total of 15m. Unknown maximum number of Cores, just respect maximum bus length. For both connection methods, the Cores are dialoguing in MIDI natively, thru the 16 virtuals MCAN ports. This is something you can expand, you can create your own Sysex based MCAN layer to build one unique app which is in fact a multi-Core App. Or you can easily create your MIDIBox(es) based Network to interconnect yours Seq, Synth and/or Controllers App. with easy to find ADSL cables. Note: In basic mode, all nodes(Cores) can talk, if one is talking the others are listening, that's all. Message priority is based on the types of MIDI events, and there's no filtering or Node ID to set. Best Bruno