keves

Members
  • Content count

    26
  • Joined

  • Last visited

Everything posted by keves

  1. midibox seq 1.jpg

    From the album Eran Rundstein

  2. midibox seq 1.jpg

    Thank you! Unfortunately it makes the engraved text very hard to read... I am going to try and paint it and hopefully that will improve it a bit :)
  3. MIDIbox SEQ V4 Release + Feedback

    Awesome. Thanks for all the hard work you are putting into this project and the community! I just completed my Midibox SEQ v4 build last night and am fascinated by how much functionality it has, and how well everything works.
  4. You're a life saver. Thanks!
  5. Hello! I ordered the following kit: http://midiboxshop.bigcartel.com/product/seq-cs-parts-kit It has three resistor values (220, 470, 1K) but I can't figure out which one goes where... Any idea?   Thanks!
  6. Super looking forward to have it fully working!  
  7. Hello! I'm currently in the process of building the awesome Midibox SEQ using Wilba's front panel PCB from SmashTV's shop. I am using an STM32F core board. I have soldered the following on the front panel PCB: - All diodes - J1 connector - All 5 pin resistor networks - All IC sockets - All pushbuttons - Capacitors   I have not soldered ANY of the following: - Resistors - Rotary encoders - LEDs - Anything else I am missing?   I have two LCD modules connected to my core board (and they work fine), and the front panel PCB (to J8/9). Pressing any of the buttons does not do anything.  Things I have checked: - All diodes are in the right orientation - All ICs are in their sockets in the right orientation (U1-U6 are the 165, U7/8 are 595) - I can see a clock signal on J1 SC pin. I can see VCC and GND.   One important mistake that I made: I initially soldered the J1 connector in the wrong orientation (or the flat cable I used is different than the one that's on the photo instructions thread). This resulted in U1 overheating and may have ruined it or anything else. After discovering this awful mistake I used wire patch cables to connect the core module and the PCB so I am fairly certain they are properly connected now (I can see a clock signal on SC, and measure ~5v between VS and VD).    Does anyone have an idea of what can be wrong? Here are some theories that I have but not sure if they make sense: - I ruined some or all the ICs - thankfully they are socketed so I will just order a bunch of new ones and try that next week. - I ruined something else - I doubt that because capacitors, switches and diodes are pretty resilient and I can't see reversed connector being an issue - This thing does not work without the LED resistors (I doubt, but maybe I'm wrong? I couldn't find a schema of the board online).   I have access to a 2 channel scope so I can look at signals if someone has an idea of what would be worth checking.   Many thanks!
  8. Thank you for the detailed reply! I am embarrassed to say it was SO/SI - can't believe I didn't double check that one! Seems to work now :D :D :D The ICs indeed seem to have survived even though the did overheat like you mentioned. Oh well, now I'll have a few more of them :) Thanks again, this made my day!!!
  9. Thanks for the reply :) I also checked the resistor networks, they are properly placed. I used the buttons SmashTV sends in his parts kit, and they cannot be misaligned. I ordered new chips so I will just try that next week when they arrive.
  10. Elektron Machinedrum Mute Controller

    Got the first version of the Acrylic panel. Learned a few things, the most important being that high density pots make no sense - they are very hard to use when they are so close to each-other :(       Higher resolution images available here: http://imgur.com/a/Pkv9d
  11. Hello fellow MIDI enthusiasts!    I recently purchased an Elektron Machinedrum drum machine, with the intent of performing live using it. Coming from the Korg ESX/EMX world, I am very keen to playing with track mutes (i.e. muting/unmuting tracks on the fly). While the Machinedrum supports this functionality, it has two major disadvantages: 1) Mutes are not 'directly' accessible - I need to navigate to a specific menu to access them, and this is pretty annoying. 2) Mutes are not stored as part of a pattern - which is another thing I find to be very convenient for live performances.   Thankfully, the mutes can be controlled via MIDI - so I was thinking, why not build a device that has 16 buttons + LED indicators for each of the Machinedrum's tracks. While at it, I figured it might be a nice idea to throw some knobs in the mix so I can control more Machinedrum parameters without navigating the menus around. This led to me wanting to create a device that has the following: 1) 16 Pushbuttons with LED indicators 2) 32 Potentiometers 3) LCD + Rotary Enc + few pushbuttons  4) Device cannot exceed 5.5" x 7" x 1.75" (so that it sits nicely next to the Machinedrum, allowing to mount both in a 19" rack) That way I get to control the mutes, 2 parameters per track and more advanced functionality (maybe switching modes/shift button/etc) using the LCD/RotEnc interface. While I am not sure I will manage to fit everything, I decided to give it a shot. The approach I'm thinking of is having 3 PCBs: 1) A PCB with 8 Pushbuttons+LEDs and 16 pots, together with two MCP3208 to read the pots, a shift register to control the button LEDs and a parallel in/serial out sift register to read the buttons. Since there is usually a minimum of 3 or so PCBs when manufacturing (not going to do this at home), I automatically get at least one other PCB, giving me the amount of IOs I want. 2) A PCB with a 20x2 or 40x2 LCD, RotEnc, Pushbuttons, etc 3) A "motherboard" PCB that has ports to connect each of the 3 PCBs (2 IO boards and the LCD control board), has the MIDI sockets, and either an STM32F chip - or preferably a STM4F Discovery board (will this fit?)   What do you think about this architecture/design? I am very open to suggestions :smile:   As first step, I went ahead and designed the IO board. I think I got it right, but I am not 100% sure - I am mostly concerned about the connections between the ADCs, the shift registers and the main board. I am also wondering about how hard would it be to modify the CORE32 code to support this connectivity. I looked at the AINSER64/DIN/DOUT drivers and it seems doable.   Some questions about the design, if anyone here feels like looking into this: 1) I separated the analog part (pots) of the circuit and the digital part (pushbuttons/LEDs) - Is this necessary? Did I get it right? 2) Did I get the ADCs connectivity right? Can I maybe switch to 1 ADC and use some sort of 'analog bus switch' to switch between the 2 rows of pots? 3) Can I expect a stable 8-bit reading using this? I am afraid of small value fluctuations sending updates to the Machinedrum, overriding its settings even when I didn't touch any pots (this would suck badly :/) 4) Does the way I connected the shift regsiters makes sense? 5) Is the board layout acceptable? 6) For people who has the Core32 with the Discovery board - any idea what the maximal height of the two of them together? 7) Is there any chance this would all fit? The board is currently 5x2.5, leaving 2" for the LCD/control board - and very little for enclosure mechanics (which I don't even know how to approach at the moment...)   I have attached pictures of the board and schematic. Eagle files are currently in my junk repository at https://github.com/eranrund/blinky-pants/tree/master/eagle/mutebox As a side note, I intend to make everything open-source and sell spare PCBs I get while making this, if this is of any interest to someone. I can see other uses to this specific controller, the most interesting one being a 16-step sequencer.   Thanks for your time!  mutebox.pdf
  12. UPDATE - This was a race in my code. EEPROM_Init seems to take some time, and that was delaying the execution of initialization code causing my AINSER task to access uninitialized data.   Have a great NYE! :) 
  13. Hey,   I'm experiencing something odd - if I call EEPROM_Init(0) in APP_Init then I cannot upload code using the bootloader unless I reset the board and hold the user (blue) button. Has anyone else experienced this? I'm guessing this has to do with EEPROM_Init touching the flash and somehow messing it for the bootloader...   Thanks :)
  14. Hello and thank you for the reply.   I just checked with MIDIbox KB and this isn't happening (I can repeatedly upload it). With my app it fails repeatedly the moment I introduce EEPROM_Init(0). Note that I am not doing anything with the EEPROM at the moment other than initializing it. In addition, the rest of my app seems to work (MIDI over USB, DIN/DOUT chain, AINSER are all working as expected).   Any idea what else could cause this? I will start commenting out parts of my code and see if I can narrow it down.   Thanks again, Eran 
  15. Elektron Machinedrum Mute Controller

    Made some good progress :smile:   So far I tested this UI module (combination of DIN/DOUT/AINSER) - it works! However the main board support two such modules, and the second one would not work because I mistakenly confused RC(RCLK) signals to be chip selects. New revision would allow to chain the shift registers on the modules by providing a header with the outputs of the DIN/OUT registers that would go back to the main board, and on to the 2nd module. A bit of an inelegant hack, but should work. Haven't tested MIDI ports or LCD yet.
  16. Hello!   Is the MIOS32 JUCE port functional in any way? Do people only develop on actual hardware, or is this port or something similar can be used to aid in development? The app I will be working on will have LCD and a few pushbuttons and pots - and I feel like developing with some kind of hackish port would speed things up - downloading to an embedded target is slow and annoying.   Thanks!
  17. Ah, silly me. The second parameter to MIOS32_BOARD_LED_Set is not on/off, its a mask of the LEDs. Nevermind :)
  18. Hello,   I got my STM32F4 board today, and for reasons beyond my understanding I cannot get any LEDs other than LED1 to light up. I am modifying the application template - so my code is as minimalistic as it gets. If I call MIOS32_BOARD_LED_Set(1,1), the green LED turns on. MIOS32_BOARD_LED_Set(2,1) or even MIOS32_BOARD_LED_Set(0xF, 1) do nothing.   Some answers to potentially obvious questions: 1) I am certain I am properly recompiling the code and uploading, as I see the green led no longer lighting up when trying MIOS32_BOARD_LED_Set(2, 1) and lighting up again when I switch to MIOS32_BOARD_LED_Set(0xF, 1). 2) I tried commenting out the code in the timer function and simply turning the LEDs on in APP_Init() 3) I am compiling using the following env variables: export PATH=$PATH:/Users/eran/Projects/mutebox/gcc-arm-none-eabi-4_7-2013q3/bin export MIOS32_PATH=/Users/eran/Projects/mutebox/mios32-svn export MIOS32_BIN_PATH=$MIOS_PATH/bin export MIOS32_GCC_PREFIX=arm-none-eabi export MIOS32_FAMILY=STM32F4xx export MIOS32_PROCESSOR=STM32F407VG export MIOS32_BOARD=MBHP_CORE_STM32F4 export MIOS32_LCD=universal   What am I missing?   Thanks!
  19. Elektron Machinedrum Mute Controller

    No worries :) I contemplated between encoders and pots, and opted for pots mostly due to the fact I like seeing where the knob is currently set at. Led rings + encoders would've been way better of course, but that would make the whole thing way too complicated for my skillset :(
  20. Elektron Machinedrum Mute Controller

      Thanks for the detailed reply! I'll post back once I make the connector adjustments, and if everything seems correct I'll get on with the main board design. I still have to figure out if this is all going to fit given the physical size limits...
  21. Elektron Machinedrum Mute Controller

    Hello Novski,   Thank you for taking the time to look at this. U$29/47 are MCP3208 - same ADC as used in the AINSER64 module. Datasheet is available here: http://ww1.microchip.com/downloads/en/DeviceDoc/21298c.pdf   Re conenctors for DIN/DOUT through J8/J9 - I realize that is possible, however I want to connect both on a single connector. I am also thinking about merging the two connectors I already have on the board (JP1/JP4) into one, but not sure I'll manage to route all the traces if I do that.   Thanks again!
  22. Hey guys,   Here's something that might be of interest to you - http://www.sandsquid.com/ You upload a BOM and it searches the major suppliers (digikey/mouser/newark/etc) for stock and allows you to combine BOMs and easily create order lists per supplier.
  23. Knob for PTV111-4220A-B104

    Thank you, I will look.