latigid on
-
Posts
2,516 -
Joined
-
Last visited
-
Days Won
147
Content Type
Profiles
Forums
Blogs
Gallery
Posts posted by latigid on
-
-
You can leave off the USB, it's only an additional +5V power option selectable by jumper..
-
1
-
-
One way is to use the punch in footswitch mode, but that's not exactly the same. Unless Peter knows of another way, maybe it could work to have scrub+footswitch (punch in) also delete notes under the cursor when the sequencer is not running?
Also an idea is to allow an "off" footswitch setting, for example if you only have a mono footswitch.
-
For this, set up a note track on AOUT port channel 16
Note 16 DOUT drum gates/triggers
Notes to CV Channel #16 (C-1, C#1, D-1, ... upwards) will be redirected to up to 64 digital outputs of the DOUT chain. Each key number triggers an individual gate for 1 mS, accordingly this mode is predestinated for drum triggers. The used shift registers have to be defined in the MBSEQ_HW.V4 file (DOUT_GATE_SR1..8) -
MCP4922 was indeed developed for, so it could be a good start? It doesn't look like it has a serial output, so if you need more than 2 channels you need to run them in parallel with /CS lines. That is a good advantage of MAX525/MAX5500 or the TLV chip.
The midiphy euroceiver has an IDC header that may be attached to a "crimpable" DB-25 connector. So that way it can sit in the back of the case if you like.
-
Great that you got it to work!
-
Seems like the bootloader is also corrupted, so the next step is to connect through ST-LINK and try to reflash that way.
Please see here:
http://ucapps.de/mios32_bootstrap_experts.html -
MIOS upload shouldn't depend on the SD card but you can try to remove it when flashing. You could try the following steps and see what works:
0. Restart MIOS Studio
1. Configure USB ports and try to upload
2. Hold and keep the blue button pressed. Now you should be able to bypass any faulty code and jump straight to the bootloader. Try to upload the SEQ app.
3. If you can't flash properly with the boot hold button pressed, reflash the bootloader using the miniUSB connector on the other side of the Discovery board and ST LINK Utility. If necessary, first update your STLINK firmware.You can find HWCFG files here (first get the firmware flashed):
https://github.com/midibox/mios32/tree/master/apps/sequencers/midibox_seq_v4/hwcfg -
Hi Roel,
I honestly haven't looked much more into this over the past years. There is a basic hardware setup and I still even have a few PCBs left, but I am not sure about whether this is the right approach. I also don't see a huge amount of activity on MIDIbox, meaning the uptake might be quite low. I could never fully agree with TK. on the UI/usage and that probably demotivated further development.
Regarding SD card/ethernet, I have not tried to use both at once. The assigned "SPI/PHY" ports definitely conflict, so it might need more elaborate software handling.
Best,
Andy -
Hi Phill,
What hardware are you using? Please take a picture of the control PCB and the core.
For uploading, you have to restart MIOS Studio each time the MCU is reset. If you have bricked your core, you should try to reflash it. How you do this depends on the hardware you have.
Best,
Andy -
Not sure if this is the right place for Arduino...
-
Great that you learned the mysteries of compilation!
I uploaded your file to the wiki page too:
http://www.midibox.org/dokuwiki/doku.php?id=sammichsid -
Hello,
You tested all of the inputs before soldering the Matias switches right? ;-)
The encoders are not on a switch matrix like the buttons are, so my guess is that there is a short between the two boards. Try to see if any resistors or diodes poke through. You could consider desoldering the encoder and bridging the pins to see if it is related to that.
But you mentioned "press on the encoder"; do you mean the encoder push switch? That is connected in the matrix in the same column as SW23.
Diodes in that column (including on ENSW7) are connected to pin 9 of J2 and pin 5 of IC3.
The encoder itself is connected through J3 pins 6/7 then through the header to pins 4/5 of IC5. A short to the adjacent pin (serial clock) might explain things.Best,
Andy -
Congrats on a fantastic looking MIDIbox!
-
Modular grid has you covered!
-
In theory yes I think you can, but there is a post from @Phatline saying that it didn't work when he tried, so maybe it needs code changes (at least for character LCDs).
http://midibox.org/forums/topic/19377-multiple-2x40-lcds-on-lpc17-core-solved/#comment-180667
-
You have the pinouts in the wiki and it basically follows the "J15" layout. There are 4x /CS signals per IDC10 header.
I think you need to configure the MIOS bootloader for the number of displays that you require (x,y), then connect J10B to the core GPIO to generate a pseudo SRIO/SPI to derive the CS signals with MB_NG or your custom code. The "J15" SI/SO/SC signals are simply buffered and routed to the headers as shown.
-
Right, that would short circuit the +5V rail to 0V!
-
So everything else works when the I2C board is disconnected? Is the cable still plugged in here?
Do you measure a short circuit on the I2C board? Measure across a 100n capacitor, or what voltage do you read? Are your PICs in the right way around? How is the soldering around J1/J4A?
Please upload a photo of the board to check.
To check if it's the PICs, you can try to remove them and see if you get the same behaviour.
Best,
Andy -
Hi Ewen,
Could be possible, but of course you need to redefine the ports in software, also to handle the incoming events appropriately.
Does it not work simply to extend the J89 SRIO line? If it needs to be remote in theory you could also put a line driver at the end. Or, can't you just send in the DIN inputs to the boards? They could also be distant from the chain.
Best,
Andy -
14 hours ago, Phatline said:23 hours ago, latigid on said:
The delay part didn't really make sense to me.
i made a video (and cut it - in real it was twice long...)- that explains the whole thing - and why a delay - i think is needet:
The "realtime switch" makes more sense now. I thought you meant you had 8 individual switches to pick the core directly.
14 hours ago, Phatline said:QuoteI think that you also need to consider how to avoid activating >1 line at once.
delay?
If it's controlled by the counter, then I think only one line can be activated at once.
I don't think you really need the delay lines. If the run state chosen by the counter is fed to the Core, when the state changes you could run a wait timer to ignore incoming inputs, also to delay sending more data out.
14 hours ago, Phatline said:QuoteAs an alternative idea, why not program a 595 shift register to send out the required "single" signal? You could easily scan in switches (momentary buttons) to specify the active line and output one 0/LO out of 8 outputs. You could also have a cycle button.
i dont get this idea.
A 595 shift register has 8 outputs, so in theory you can write a program to choose the output instead of cycling through the counter.
6 hours ago, Phatline said:... a other thing... i get my head by switching the J15A Ports... this are already buffered signals on the core? do i have to route them - or is it enough to connect them somehow together (and pull down), and just tell the cores to shut up, and only one to speak?
i ask, because, J15A connected to 8xSSD1306 need 10 Data pins (CS1-CS8, SC, SD) a 74HC541 has only 8 Buffers (and i did not find a buffer that makes more then 8), by switching 8 cores i end up by 16x Buffer Chips... that is to much place-usage (eurorack...), and i have the feel (not the knowledge) that a output is not so crucial... since i will initialize the Screen-Driver anyway while the program is running...
I think you need to buffer/switch them, otherwise the clock lines etc. will interfere?
-
I didn't check in great detail but that seems to be the right idea. The delay part didn't really make sense to me.
I think that you also need to consider how to avoid activating >1 line at once.
As an alternative idea, why not program a 595 shift register to send out the required "single" signal? You could easily scan in switches (momentary buttons) to specify the active line and output one 0/LO out of 8 outputs. You could also have a cycle button.
Note that outputs are high impedance (i.e. disconnected/floating) when the /OE signal is high. This means that you must define the logic level of all downstream logic inputs with pull-up/-down resistors (1k-10k), whatever the default state should be.
-
Very nice! I really wonder what happened to those 595s? Could it be oxidation on the sockets?
For ports, I think we will stick to the 8x MIDI outs currently available. I know Peter controls over 30 synths by using Thru splitters and that works just fine too. But as another idea, you could always repurpose the old SEQ as a glorified router?
Best,
Andy -
Grüssi Michael,
I would suggest to first check the tactile switches as these often go bad.
I would highly doubt a software error, but I tried it on mine and couldn't replicate your error. Just the switches were bad and needed extra effort to push.
The only other thing might be a bad diode or LED, but I would think that that's really unlikely.
Best,
Andy -
Okay, all good then! Above schematic is wrong of course as the "SI" pin from the chain should be connected to the input! But you get the idea I hope.
Actually, the SI normally comes in unbuffered and only SC/SO/RC1/RC2 (outputs) are buffered. But for your case I think you also need to "switch" the SI? So you can use 5 gates or just combine RC1/RC2 as they are normally set simultaneously
Triggermatrix 5
in MIDIbox User Projects
Posted
Epic MIDIbox -- well done!