operators123

Ah perfect, I've been looking all over for examples! Will have a look at these then draw up a new digram

Ok, just going to bump this post to post a diagram of my connections to make sure I havn't made any mistakes as getting my head round this was a bit confusing: (I apologize if this is too big) I've drawed a diagram to show what is going on, essentially I have now: -one 8x8 button matrix -one 8x8 led matrix for 64 jogwheel leds (32 on left and right deck) -one 8x16 led matrix for panel illimination leds (so about 128) -encoders connected direct to core:

Ah right, thanks for the feedback :smile: I'm going to look then into wiring all the digital IO's as matrixes, it seems as if this means I can use less shift registers and save a bit of money then. EDIT: Wow it actually looks like wiring the buttons in a matrix is much better, I now only have to carry 16 signals from my frontpanel PCB to the module as opposed to 56 for each button. My only worries so far are in the programming. When I say roughly 140 LED's I mean about 40 of them being VU meters, about 56 being switched on/off and 48 being the LED rigs for the jogwheels. Hopefully even while in a matrix each LED can be adressed individually so I can give each one a specific funcion.

Hi, I've been looking into building a new DJ Controller and I've settled on using MIDIbox NG with the STM32F4 core module as this is certainly the best option out there (my last controller was made with arduino mega and the amount of features this has compared to that is crazy). These are the features I plan to have: - About 56 tactile buttons connected directly to a DIN module (basically 7 daisy chained 165's) - About 140 controlled LEDS directly connected to a DOUT module (again about 20 daisy chained 595's) some are going to be flashed on/off went sent data from Traktor, but also I plan to have two big LED rings around the jogwheels consisting of about 24 led's each side - Three encoders (two with no detents on with detents) - About 16 pots, rotary and slide connected to one AINSER_64 module. I have a couple of questions: - Can I connect encoder pins and push buttons to the same DIN module? - What forward current does the 595 run the LED's at? It has 220 ohm resistors in front of each input so this looks like 15ma . Since I have 140 LED's does that mean 2.1A of current? - Does this design seem feasable? I do have a bit of experience with circuits and coding from my last project

Ah right, I didn't actually read about that one, I just assumed the ARM boards were a bit expensive and that PIC's were a more affordable solution, but the STM32F4 board is only £10 which is great so I guess I'm going to go with that instead. Just wish there was a PCB design available I could make the midibox core module myself :shifty: Guess I'll use the schematic and design it myself

Hi, I've just discovered midibox and I think it's the best way to go about building a DJ controller. It looks very flexible and seems to offer very good performance (<1ms latency really interested me). Anyways, I want to use the PIC based core module built from scratch, I noticed it uses a PIC18F452 though. I have a brand new PIC18F45k50 sitting at home and it'd be great if I could use this. I think it's alot newer but more importantly has D-/D+ ports for USB2.0 communication which means I can directly connect it to my USB ports and use it rather than having some kind of UART to USB circuit. I want to know if it's possible to make some kind of PIC18f45k50 based core module based off the existing core module design, and if I could still program it with the bootloader once, and program all the I/O's over USB connection (I noticed there's a GUI program, you can use this to set what each button/pot/LED does right?)