Does this mean, that V4 doesn’t support the 4x16 BLM?
Actually it is supported, but the design is outdated.
With the 4x16 BLM which is directly connected to the DIN/DOUTs of the core it won’t be possible to provide the features of a BLM16x16+X (which is running on a separate core and communicates via MIDI with the MBSEQ V4), therefore this expired solution isn’t “promoted” from my side anymore to avoid that somebody things that he gets something which is equivalent.
The configuration of the directly connected 4x16 BLM has to be done in the MBSEQ_HW.V4 file, search for the keyword “BLM”
While testing the underside of the DIN module which were connected to anodes of the “button-diodes” got contact with conductive material…BIG MISTAKE, I know…
Happily, everything else still works, but I guess the DIN and DOUT-modules which were connected to the BLM are broken..
Is it sending 3 volt of direct current in the LED anodes(coloumns) and setting the rows which are not wanted to light on high current(so that the other LED’s will get high current on both cathodes and anodes)?
Can I somehow “simulate” the matrix driver with my multimeter?
I have a really simple one, but if I would send 2.5V direct current in for example couloumn 1 (anodes) and setting COM/ground to a row 4, the 4 led’s in the coloumn light && I will not damage anything?
(I’m sorry I have pretty much no knowledge to electricity stuff..)
…but I get a lot of debugging messages on the terminal: “DIN_BLM_NotifyToggle(n,1)”, with n constantly changing from 0 to 31.
This function should only print this message with a changing value at the input n. What could this “random” variation mean?
There is probably a problem with the RC signal between core module and the DIN shift registers.
This signal latches the values before shifting, and if it isn’t connected you will get random values.
Beside of this: are you able to control the LEDs by sending MIDI notes to the core?
e.g. with the virtual keyboard of MIOS Studio… ensure that channel 1 is connected. The core will output debug messages whenever a matching event has been received, and the LED state should change.
There is probably a problem with the RC signal between core module and the DIN shift registers.
This signal latches the values before shifting, and if it isn’t connected you will get random values.
Ok. When I connect normal button’s (to the same DIN module) according to this schematic and the 010_din tutorial app, everything is working fine. Is this in conflict with your idea, or could there still be the problem with the RC signal?
Beside of this: are you able to control the LEDs by sending MIDI notes to the core?
e.g. with the virtual keyboard of MIOS Studio… ensure that channel 1 is connected. The core will output debug messages whenever a matching event has been received, and the LED state should change.
I’m sorry that I didn’t mention:
I can’t control any LED. The terminal is printing that the core receives midi notes/events (on channel #1), but no LED reacting neither glowing.
(But the same here : with the same DOUT module and standard LED connection, no problems….)
DIN and DOUT module is working, but you will get a lot of MIDI events once your BLM is connected.
How to check that the BLM application is scanning the keys: disconnect the BLM hardware, and short a DOUT pin with a DIN pin which is normally connected “between” a button.
It took a bit longer than expected, but finally I tested what you (Thorsten) proposed:
How to check that the BLM application is scanning the keys: disconnect the BLM hardware, and short a DOUT pin with a DIN pin which is normally connected “between” a button.
Take a cable and connect it with D0 of DEFAULT_SRM_DIN_L and D7 of DEFAULT_SRM_DOUT_CATHODES1 -> do you get a single MIDI event, or multiple events?
Try also other pin combinations.
Best Regards, Thorsten.
It didnt worked, as you described. …
By luck two friends from India came by (one hardware - && one software specialist) and we looked together at the circuit.
Their opinion was that the DOUT module couldn’t work without the serial resistors connected, which I didnt solder on the board - because of the following description from this schematics
“NOTE: the 220 Ohm Resistors on the two DEFAULT_SRM_DOUT_CATHODES* Registers should be removed.”
I dont know if I completely misunderstood these words, but when we tested with exactly the same configuration with a DOUT module with all four 220Ohm resistor networks connected everything worked fine…
So, finally “everything” is working - I will just finish and then post a little picture..
!!! THANKS EVERYBODY FOR YOUR TIME AND HELP !!!
you are great. ucapps is great. midibox is great. TK. is great!
Of course, instead of “220 Ohm resistors can be removed” actually I meant “220 Ohm resistors can be replaced by cables” - I corrected this in the schematic.