Jump to content

keves

Members
  • Posts

    33
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by keves

  1. Ah, silly me. The second parameter to MIOS32_BOARD_LED_Set is not on/off, its a mask of the LEDs. Nevermind :)
  2. 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!
  3. 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 :(
  4. My mistake - I wasn't sure there would actually be a need to modify anything. Due to my cramped board layout (or lack of layout skills...) my LEDs/buttons are already in a messed up order that made routing easier... Thanks for the catch! Will add one. Okay, staying with 2. Sweet :) I'll revisit the AINSER8 and DIN/DOUT schematics, and try to adapt my pinout to the standard ones. It is my interest to make this reusable by other people. That wouldn't work in my case since I plan on having 2 of these boards connected to my core module. 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...
  5. 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!
  6. 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
  7. 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.
  8. Hello everyone. I am looking for a knob that will fit on a PTV111-4220A-B104 potentiometer (datasheet). I would've searched myself but I can't figure out how - which diameter am I looking for? 4.5mm? 6mm? Thanks! :)
×
×
  • Create New...