latigid on

Not knowing much on the programming side, I would take the SEQ and MB6582 as examples. It looks like encoders are assigned to blocks of DIN, I'd guess the matrix scanning is more efficient this way. My approach to MBCV is to have a separate SR board because; a) it's an assembly of multiple PCBs, b) there's no room on the CS, c) it makes troubleshooting easier, and d) the data lines are confined to a smaller area and should maintain better signal integrity. That said, SRIO in MIOS-land seems quite robust and easily spreadable across multiple modules, so if there's a single PCB solution it's probably the thing to do. Best of luck!

Keep 'em coming! 20 would be a good number if possible, because I'm sure some will drop out as circumstances change. Depending on how much time I have I can consider stocking some of the components/hardware, no promises though. For now it's definitely on for the BLM PCB, miniCore PCB and machined case.

Well, it's still not too clear what you were proposing about the ground plane, but I changed it anyway .

Did you mean the 2981 chips? They will provide level-shifted gates as part of a MBCV v2 control surface (here). There could be other uses though, like a more generic NG build.

The wiki does tend to get neglected though. And new users generally don't have write access... While the BLM is a much smaller project, I think the concept of a "build thread" is nice as it's a chronological sequence :) of information. The OP, as long as they're planning to stay for a while, can update the first post to separate the good info from general chatter. It also seems more inclusive as there's a real discussion of ideas and problem solving. That said, it's a really good idea to backup the data to another location. A good example was the Great Muffwiggler Outage of 2015, where after a hacking incident the owner was so very close to giving up on months (years?) worth of invaluable posts until a brave knight came along and worked on a restore process. Lesson: backup your backups!

Could you be a bit more specific about what you don't like about it? It should be possible to mirror the 5V trace to allow a a solid connection back to the supply, but it's always a toss-up between as few vias/layer changes as possible.

Here we go: This was my best solution to routing up the DINs. Looks like it will be possible to make a "mini-DINX4" at around 50*50mm in the future.

Très beau!

Okay, here's the three boards routed up: 4*4 matrix using WS2812s and Sparkfun button pads CS board with 29 buttons, 4 OLEDs, space for a CLCD (more likely a 2*20 OLED) and 4 encoders -- with push switches or WS2812 depending on the configuration. -- it's even symmetrical = lefty friendly! 4*4 encoder bank, also illuminated It should be possible to use common DIN/DOUT boards, but to make things simpler I've made another board with 6 DIN, 4 DOUT and 2*5 headers which line up with the ribbon connectors. It mounts on the back of the CS PCB and saves two ribbons to the CS. Also included are level shifters for the DOUT gates and clocks using 2981 source drivers. Thanks @tashikoma for the tests re: current limiting using 1k resistors! If 5V gates are okay it will be possible to omit these chips and instead span a resistor over the relevant pads. It is a strange mix of DIP and SOIC, but all attempts to use regular 6-pin resistor networks for DIN pull ups were very tight and had inflexible PCB routing. I chose to keep the 595s through hole as these will interface with modulars and could be blown up! I hope this is okay, but if you're adverse to SMT it will still be possible to use smashTV boards. Another thing to note: assuming the concept works well enough these could be suitable for standalone NG builds or even MBProgramma . There's a thought of another PCB to mount the 45 degree displays on top of the encoders. China is closed for their New Year, so I will mull over the design for a few weeks before fabrication. If there's any suggestions, please let me know.

Great to hear it's solved! I was just wondering if the transistors switch off faster (which they should using Schottkys) if the current draw and thus +5V rail drop is less. I would check to see if the slight ghosting annoys you before undertaking this. I remember that the legs of my Schottkys were a bit too short to bend; perhaps a clipped resistor leg could help (carefully trimmed shorter after soldering)? But in my build I just loaded on the solder until a suitable blob formed.

I personally won't rule out offering some sort of breakout PCB in the future. But at the moment the SIP 7-pin SPI-ready displays can be had for around $7 each (or less). Their width means that you go over the magical 100mm dimension if you want to stack more than 4 side by side. In a minute I'll upload my concept for MBCV v2 which puts the display pins on the control surface PCB. So maybe it's a good idea to just integrate into dedicated projects?

One trick might be to disconnect the SEQ's LCDs to do the test, perhaps that way you can determine if the PSU is strong enough or if the problem is present on the BLM side with the low voltage. Can you mention if you have Schottkys installed? The way I have connected my PSU (old F1 Core) is to remove the 5V linear Vreg and insert SPSU 0V on pin 2 and +5V on pin 3.

No problem on my unit replicating your test conditions. I have a 2A PSU for the SEQ, adafruit Verter regulator inline inside the case, Schottky diodes piggybacked and 8 mapped AIN, with unused AINs jumpered.

Can you measure the main power rail voltage in this state? E.g. using the J3 jumper? Just on the weekend I was happily switching between layers (you should get a kind of VU meter display).

Reminder for tomorrow!

Thanks, seems to be working now after removing device/disabling and other fiddling. The ploytec wouldn't progress past the "connect your device now" without a proper GM5 I guess.

Sorry, not sure exactly what you mean? I will order a batch of miniCore boards to go with the BLMs, or if you prefer you can use a regular Core8 as the circuit is identical (linked above). It's just less convenient. The 125 chip simply buffers SO, SC and RC and there's even extra buffers on the main PCB. Probably neither of these are necessary now we know more about the brown out reset behaviour.

Exactly, you should instead disable the unused DINs and build a new .hex file otherwise the PIC is looking for registers which aren't there!

Did you compile a new setup_midibox64.asm file? Can you post it?

Relevant in setup.asm Is this correctly done?

I don't know much about MB64, but if the number of shift registers configured in software is greater than what you have installed I can imagine their addressing could get messed up. Feel free to post a pic, that always helps.

Salut Pierre, Here are the schematics; http://www.ucapps.de/mbhp/mbhp_blm_scalar.pdf -- SCALAR module which is just a mixed DIN/DOUTX3 board. There are a few modifications such as enabling a power on delay and B-E resistors for the current sink transistors. Five of these are integrated into the BLM PCB. http://www.ucapps.de/mbhp/mbhp_blm_map.pdf -- this is the matrix routing for the buttons and LEDs. http://www.ucapps.de/mbhp/mbhp_core_v3.pdf -- this is the 8 bit Core of which unneeded headers and the LCD driver circuit have been removed for the miniCore. There's an extra line driver implemented for the digital signals, and the MIDI I/O and power come in on the same 2x5 DIL header. Best,

Just to correct you there hawk, the resistors are pull ups to +5V. The other point to check is if resistor networks are oriented with the dot aligned with the PCB silkscreen. If this is a DIN kit from SmashTV then you have the correct components. Something else to consider is that DIN (or DOUT) modules will not cascade unless all chips are installed because the specific SI or SO data signal is routed through each subsequent shift register.