Share your DIY controller project based on MIDI for 3rd Party Devices | AXE3 | FM3 | FM9 | VP4 |

[Axelman8]

I use Behringer FB1010, so probably won't be able to use this, correct? It just sends PC/CC messages AFAIK
I know very little about MIDI, sadly

Hey there,
In my program the code is sysex and its handled by the AxeController library. Standard midi wont work to start/stop the metronome as far as I know.
Setting tempo also works with the sysex AxeController library and is very convenient to use with the metronome. Set with numbers like 1 9 3+Tempo and you have Metallica Battery tempo and metronome.

Im guessing the FC6 or FC12 have got these options available? But not sure

 

[fab-gm]

Hey there
Not bad for a 1st tryout pcb. It works for 75% as intended, but it does work great!
../..

View attachment 144146

Was thinking: I have PCB foot switches at home I never used yet: the idea would be speed up the process of wiring the switches too and so create a big mainboard to start a new floorboard project very fast

 

[Axelman8]

Was thinking: I have PCB foot switches at home I never used yet: the idea would be speed up the process of wiring the switches too and so create a big mainboard to start a new floorboard project very fast

If that is possible yeah that would be awesome. A big mainboard is very expensive to produce though and if there is damage, its ruined. So Im thinking connecting modular PCB's using connecters like molex, dupont or rj45 even.

 

[unix-guy]

I use Behringer FB1010, so probably won't be able to use this, correct? It just sends PC/CC messages AFAIK
I know very little about MIDI, sadly

Are you using the stock FCB or do you have one with the UnO or Eureka replacement PROMs?

I am pretty sure the UnO allows sending sysex, in addition to being a massive upgrade in functionality...

 

[Chromatizm]

stock FCB

This I'll probably buy UnO if I have a chance - the delivery now will cost more than the chip itself. My PC is always on anyway. Thanks for the suggestion!

 

[unix-guy]

This I'll probably buy UnO if I have a chance - the delivery now will cost more than the chip itself. My PC is always on anyway. Thanks for the suggestion!

Check out the Control Center software for programming it. It's very useful!

 

[Chromatizm]

Control Center software

Wow, this one looks too good to be true. Do I understand it correctly it works with stock FCB? Thanks a lot!!

 

[Axelman8]

@unix-guy reads all the manuals
If not:
Thats because he wrote them

 

[unix-guy]

Wow, this one looks too good to be true. Do I understand it correctly it works with stock FCB? Thanks a lot!!

Not that I know of - it's for the UnO as far as I'm aware.

 

[Axelman8]

Okay so next: getting rid of the 2x16 and replace it with a 2.8 inch ST7789 SPI tft.
It would fit perfectly and would give tons of options to display info.

One of my really grand wish is to show a picture of the AMP used. Saw it in @Piing his thread for the $50 controller project. Looked very cool and gives a more real world feeling seeing the actual amp.
JPEG of the amps are allready presented in the notorious AMP guide from YEK. These will do just fine

Problem: There is no way to get the AMP info from the fractal like the preset+scene export from Axe-edit. Even FracPad or Fractool dont provide this option.

Anyone got any ideas how to extract the AMP a very easy way so I can store a list on the SD-card of the Teensy? Really appreciate your input.

 

[Piing]

Okay so next: getting rid of the 2x16 and replace it with a 2.8 inch ST7789 SPI tft.
It would fit perfectly and would give tons of options to display info.

One of my really grand wish is to show a picture of the AMP used. Saw it in @Piing his thread for the $50 controller project. Looked very cool and gives a more real world feeling seeing the actual amp.
JPEG of the amps are allready presented in the notorious AMP guide from YEK. These will do just fine

Problem: There is no way to get the AMP info from the fractal like the preset+scene export from Axe-edit. Even FracPad or Fractool dont provide this option.

Anyone got any ideas how to extract the AMP a very easy way so I can store a list on the SD-card of the Teensy? Really appreciate your input.

View attachment 144297

Get more space for a Nextion TFT 4,3" touch display

 

[Axelman8]

Get more space for a Nextion TFT 4,3" touch display
View attachment 144299

Yes thats the one . But Only got space for the 2.8
Got to do it with this one man, but your Nextion sure looks fantastic.

 

[Axelman8]

See the actual amp that is active in your preset/scene/channel

Still far way from happening because there is no list of amps used in the preset/channel, but who knows... We are ready for it

This looks very cool imho

 

[mavriq]

While testing I discovered that I made a design error. To daisy chain SPI data, you really need it to be serial, not parallel. My design is parallel and I hoped it would work when connecting all together to 1 source , wellIt doesn't! Took me forever to find the issue.
Second issue is that the CS line for each screen should be a thicker line than the standard used in the PCB because it uses somuch energy to update the screens.

Can you elaborate more on the parallel issue? The DC, RST, SDA, etc are supposed to be in parallel are they not?

I'm planning to do something similar and don't want to run into the same issue.

 

[mavriq]

Also did you use kicad for the PCB? If so what connector did you use for the screens?

 

[Axelman8]

Can you elaborate more on the parallel issue? The DC, RST, SDA, etc are supposed to be in parallel are they not?

I'm planning to do something similar and don't want to run into the same issue.

You can run your screens in groups, but make sure your SPI clock runs in serial, so you wont get interference. On higher frequencies this will become a problem when adding more screens.

 

[Axelman8]

Also did you use kicad for the PCB? If so what connector did you use for the screens?

Yes KiCad, worked very easily never used it before. The pcb worked the first time out of the box. Not really like I intended, but it works great.

I used the standaard dupont 1*8 connector

 

[mavriq]

Ya, First time for KiCad here as well. Used others though. Even bought Circuit Master way back in early 2000s before there were any open source IDEs!

My unit isn't going to be for fractal, but I figured it would be useful to others. I've learned a lot here thanks to many, so hopefully it helps. I figured out who to mux screens with an 74HC595(s) as well, so I'm going to make that an optional part of my design, so the PCB may be useful to many.

 

[Axelman8]

Ya, First time for KiCad here as well. Used others though. Even bought Circuit Master way back in early 2000s before there were any open source IDEs!

My unit isn't going to be for fractal, but I figured it would be useful to others. I've learned a lot here thanks to many, so hopefully it helps. I figured out who to mux screens with an 74HC595(s) as well, so I'm going to make that an optional part of my design, so the PCB may be useful to many.

Mux screens saves some pins, but limits you to 10MHz max refreshrate frequency of the screens (read it in a faq for the MUX somewhere). Would advise to mux your switches and cable your screens.

 

[mavriq]

I'll have to mock this up then. I googled but didn't find anything specific. But as far as I know you're only limited by the speed of the muxer as far as chip selects are concerned. Which would mean that after about 10 million screens it would impact. But it certainly doesn't hurt to mock it up and double-check.

I'll report back with my findings. Just got to find a good way to attach all the screens, they all have the standard breadboard pin standoffs right now.