multiple Clcd's

ssp · January 25, 2020, 11:54pm

Looking in my .ngc file i see the dout matrix hardware section, i notice that everything is pretty much the same, do i need to edit this section to reflect the code in the led test?

DOUT_MATRIX hardware

DOUT_MATRIX n=1   rows=8 inverted_sel=0 inverted_row=0 mirrored_row=0 \
                   sr_dout_sel1= 0 sr_dout_sel2= 0 sr_dout_r1= 0 sr_dout_r2= 0 sr_dout_g1= 0 sr_dout_g2= 0 sr_dout_b1= 0 sr_dout_b2= 0
DOUT_MATRIX n=2   rows=8 inverted_sel=0 inverted_row=0 mirrored_row=0 \
                   sr_dout_sel1= 0 sr_dout_sel2= 0 sr_dout_r1= 0 sr_dout_r2= 0 sr_dout_g1= 0 sr_dout_g2= 0 sr_dout_b1= 0 sr_dout_b2= 0

I didnt put all of it in here to keep it simple.

in the led digit demo it shows this

Control 5x3 LED Digits to output 7bit values

RESET_HW

LCD “%CLED Digit Demo”

HW definitions for “Common Cathode” Digits

see also http://www.ucapps.de/midibox_ng/mbng_led_digits_5x7bit.pdf

DOUT_MATRIX n=1 rows=8 sr_dout_r1=1 inverted_row=0 mirrored_row=0 sr_dout_sel1=2 inverted_sel=0
DOUT_MATRIX n=2 rows=8 sr_dout_r1=3 inverted_row=0 mirrored_row=0 sr_dout_sel1=4 inverted_sel=0

the led digit demo has the DOUT_MATRIX n=1 defined, but my ngc file doesnt, do i need to edit the ngc in the same way?

latigid_on · January 25, 2020, 11:58pm

Just now, ssp said:

DOUT_MATRIX n=1   rows=8 inverted_sel=0 inverted_row=0 mirrored_row=0 \
                   sr_dout_sel1= 0 sr_dout_sel2= 0 sr_dout_r1= 0 sr_dout_r2= 0 sr_dout_g1= 0 sr_dout_g2= 0 sr_dout_b1= 0 sr_dout_b2= 0
DOUT_MATRIX n=2   rows=8 inverted_sel=0 inverted_row=0 mirrored_row=0 \
                   sr_dout_sel1= 0 sr_dout_sel2= 0 sr_dout_r1= 0 sr_dout_r2= 0 sr_dout_g1= 0 sr_dout_g2= 0 sr_dout_b1= 0 sr_dout_b2= 0

Define the shift registers connected to the “sel” and “dout” parts, at the moment they all = 0 and so no data are sent.

ssp · January 26, 2020, 1:02am

24 minutes ago, latigid on said:

Define the shift registers connected to the “sel” and “dout” parts, at the moment they all = 0 and so no data are sent.

Ok, but in this case with the disco connection to mios studio and just running the lcd test code from there I get some of the (cc#16 and 17 work fine with the 3 digits going from 0-127) should that even happen?

I used clean flashed disco board, then mbng installed, open mios studio and create a test. Ngc file. Then I selected edit text, pasted in the led test code, save. The 3 digit lit up and I moved mios studio cc18 slider. Some worked some didn’t.

I will have to read the relevant sections again tomorrow and try the code on one 3 digit and see what happens.

ssp · January 26, 2020, 6:07pm

spent some time on this but for some reason it eludes me, i cannot put the pieces together. I really want to figure this out but its like using a flower to puch a hole through a brick wall on times.

I know how a dout works, i understand the pins out on the first and the cathodes on the second sr, etc. but when i try to put it all together in the code it doesnt work.

how is it i can understand most of it already but this is just not sticking or making sense…

latigid_on · January 26, 2020, 8:10pm

Could be anything from incomplete NGC file, dodgy breadboard or wiring, corrupt SD card (saving often doesn’t work well, upload always worked better for me) etc. etc.

Draw a functional map of how it should work and see if you connected the dots properly. Adapt the NGC file to suit your hardware and again just playing with it might help.

ssp · January 26, 2020, 11:01pm

2 hours ago, latigid on said:

Could be anything from incomplete NGC file, dodgy breadboard or wiring, corrupt SD card (saving often doesn’t work well, upload always worked better for me) etc. etc.

Draw a functional map of how it should work and see if you connected the dots properly. Adapt the NGC file to suit your hardware and again just playing with it might help.

I have buzzed all of the cables to and from the breadboard, checked the dout pcb, (i even soldered a new one up and changed out all the sr’s on the old one) all is good connectivity wise. I am trying hard to understand this, What i have done is create a test.ngc file on my sd card and i run all my test code from that in mios studio, same as the first steps examples did. most of the things i have done since starting to learn i have done this way and have worked.

I dont hide the fact i am not a coder and where it gets more complex i struggle yet, i push on but yes i know its annoying I have to ask questions along the way but I dont expect anyone to do do the work for me.

I work off examples, that way i can try it, figure it out by messing with it and hey presto it clicks, like the padding and syntax for the lcd’s and oleds. It took a while but after playing with the examples and trying a few modifications it all clicked and I understood it all, the same with mapping potentiometers and encoders etc and their types, values etc. i have all of that down and i use it fine.

I just need to figure out the matrix syntax etc and as soon as i do.. it will click.

for example:

n=<1..8>Specifies the matrix number which should be configured; it can range from 1..8 ( this i dont understand)

rows=<4|8|16>Sets the number of rows which should be scanned: (this i dont understand)

This is think I understand

sr_dout_sel1=<0..16> Sets the first DOUT shift register which should output the row selection signals ( if this =1 then this means the 7 segments goto sr=1)

sr_dout_r1=<0..16>Sets the first DOUT shift register of the LED matrix row. (if r1=1 then the first shift register on the doutx4 pcb is number 1)

Where do i assign the common cathodes? as they would link to J4 the second shift register that has no pullup resistors in just bridges.

I also looked at this schematic and it blew my mind!! http://ucapps.de/mbhp/mbhp_blm_map.pdf

latigid_on · January 26, 2020, 11:35pm

Hi,

3 minutes ago, ssp said:

n=<1..8>Specifies the matrix number which should be configured; it can range from 1..8 ( this i dont understand)

Defines the matrix to be addressed. You could have one matrix for 7-seg digits and another as a simple LED dot matrix. Each one needs a unique address, otherwise MIOS wouldn’t know what one to turn on when assigned.

Quote

rows=<4|8|16>Sets the number of rows which should be scanned: (this i dont understand)

Simple case: 8 rows is typical. 4 rows will repeat the selection pulses. 16 rows would need two SRs for 16 selection pulses. Use rows-8 unless you need a 16x16 matrix.

Quote

This is think I understand

sr_dout_sel1=<0..16> Sets the first DOUT shift register which should output the row selection signals ( if this =1 then this means the 7 segments goto sr=1)

Determine where the common pin of your LED segments go. Then connect them to this SR in order. If it is the first SR in the chain, then sr_dout_sel1=1. If it is the nth SR in the chain, then sr_dout_sel1=n

Quote

sr_dout_r1=<0..16>Sets the first DOUT shift register of the LED matrix row. (if r1=1 then the first shift register on the doutx4 pcb is number 1)

r1 refers to red1, for the case where you’re defining an RGB matrix. Then you have g1 and b1, and also r2, g2 and g2 if you want a 16x16 matrix.

Quote

Where do i assign the common cathodes? as they would link to J4 the second shift register that has no pullup resistors in just bridges.

Not pull-up resistors, these are series resistors to limit the current and they probably should be bridges to sink more current for the common cathodes. So assign the sr_dout_sel1=n where those bridges are.

If you have common cathodes, then

inverted\_sel=0

is probably correct. At least that is the case for matrices that I have configured (not including those with sink drivers!)

Quote

I also looked at this schematic and it blew my mind!! http://ucapps.de/mbhp/mbhp_blm_map.pdf

Tell me about it!

Have fun!
Andy

ssp · January 27, 2020, 12:26am

Look at that, even the things I thought I knew were wrong!! I never cease to amaze myself

ssp · January 27, 2020, 12:09pm

My brain may have clicked today, not 100% sure yet but I sat talking the code to myself and it started making sense. Will post some up later after trying it or vice versa…

ssp · January 27, 2020, 6:29pm

I am pleased to say that I finally understand the dout matrix syntax and structure for what i want., I am going to have a play with it now but this is a single 3 digit lcd on a doutx4 on the first shift register.

RESET_HW

LCD “Single CLED 3 Digit”

DOUT_MATRIX n=1 rows=8 sr_dout_r1=1 inverted_row=0 mirrored_row=0 sr_dout_sel1=2 inverted_sel=0

EVENT_LED_MATRIX id=1 fwd_id=LED_MATRIX:2 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 16 lcd_pos=1:1:2 label=“1:%3d%B”
EVENT_LED_MATRIX id=2 fwd_id=LED_MATRIX:3 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=3 led_matrix_pattern=Digit3

My code, all is good, I changed the code so it moves to the 3rd shift register and the commons on sr=4

RESET_HW

LCD “Single CLED 3 Digit”

DOUT_MATRIX n=1 rows=8 sr_dout_r1=3 inverted_row=0 mirrored_row=0 sr_dout_sel1=4 inverted_sel=0

EVENT_LED_MATRIX id=1 fwd_id=LED_MATRIX:2 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 16 lcd_pos=1:1:2 label=“1:%3d%B”
EVENT_LED_MATRIX id=2 fwd_id=LED_MATRIX:3 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=3 led_matrix_pattern=Digit3

ALL IS GOOD!!! my brain worked today. I am just reading how to forward from an encoder to this event now. wish me luck!!

Many thanks to latigid-on for his patience and help so far.

ssp · January 27, 2020, 7:05pm

Encoder all hooked up and forwarding to the 3 digit display and the oled display!! cookie for me tonight!

RESET_HW

LCD “Single CLED 3 Digit”

DOUT_MATRIX n=1 rows=8 sr_dout_r1=3 inverted_row=0 mirrored_row=0 sr_dout_sel1=4 inverted_sel=0

EVENT_LED_MATRIX id=1 fwd_id=LED_MATRIX:2 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 16 lcd_pos=1:1:2 label=“1:%3d%B”
EVENT_LED_MATRIX id=2 fwd_id=LED_MATRIX:3 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=3 led_matrix_pattern=Digit3

ENC n= 1 sr=1 pins=0:1 type=non_detented
EVENT_ENC id=1 fwd_id=LED_MATRIX:1 type=CC chn= 1 cc= 1

latigid_on · January 27, 2020, 8:14pm

POIDH!

ssp · January 27, 2020, 8:40pm

Just now, latigid on said:

POIDH!

I just hooked up a second 3 digit and moved the encoder over as well. it worked first time, the second 3 digit is just linked to the first on the row pins and the commons to the next 3 on the sel pins.

RESET_HW

LCD “Single CLED 3 Digit”

DOUT_MATRIX n=1 rows=8 sr_dout_r1=3 inverted_row=0 mirrored_row=0 sr_dout_sel1=4 inverted_sel=0

ENC n= 1 sr=1 pins=0:1 type=non_detented
ENC n= 2 sr=1 pins=2:3 type=non_detented

EVENT_ENC id=1 fwd_id=LED_MATRIX:1 type=CC chn= 1 cc= 16
EVENT_ENC id=2 fwd_id=LED_MATRIX:4 type=CC chn= 1 cc= 17

EVENT_LED_MATRIX id=1 fwd_id=LED_MATRIX:2 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 16 lcd_pos=1:1:2 label=“1:%3d%B”
EVENT_LED_MATRIX id=2 fwd_id=LED_MATRIX:3 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=3 led_matrix_pattern=Digit3

EVENT_LED_MATRIX id=4 fwd_id=LED_MATRIX:5 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 17 lcd_pos=1:1:2 label=“2:%3d%B”
EVENT_LED_MATRIX id=5 fwd_id=LED_MATRIX:6 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=6 led_matrix_pattern=Digit3

now i see it I can’t unsee it!!

ssp · January 28, 2020, 12:30am

Dout question just wondering if this is right:

If i connect two dout pcbs then this works fine for the first one

DOUT_MATRIX n=1 rows=8 sr_dout_r1=1 inverted_row=0 mirrored_row=0 sr_dout_sel1=2 inverted_sel=0

is this correct for a second connected dout?

DOUT_MATRIX n=2 rows=8 sr_dout_r2=1 inverted_row=0 mirrored_row=0 sr_dout_sel2=2 inverted_sel=0

Dout pcb 2 pins start from 33 - 64

so should the next section for the led matrix be?

EVENT_LED_MATRIX id=33 fwd_id=LED_MATRIX:34 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 16 lcd_pos=1:1:2 label=“1:%3d%B”
EVENT_LED_MATRIX id=34 fwd_id=LED_MATRIX:35 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=35 led_matrix_pattern=Digit3

I am going to make another dout pcb tomorrow to test this anyway. I see in the manual it says this:

sr_dout_r2=<0..16> sets the (optional) second dout shift register of the led matrix row

sr_dout_sel2=<0..16> set to 0 if second is not required.

latigid_on · January 28, 2020, 6:58am

sr_dout_r1= is for 8x matrices
sr_dout_r2= is for 16x matrices

I suppose you only use 8x8 matrices, thus keep sr_dout_r1 for the second DOUT.

Here’s how you address one DOUT PCB:
sr_dout_r1=1
sr_dout_r1=2
sr_dout_r1=3
sr_dout_r1=4

and here’s how you address the next DOUT:
sr_dout_r1=5
sr_dout_r1=6
…

ssp · January 28, 2020, 7:55am

1 hour ago, latigid on said:

sr_dout_r1= is for 8x matrices
sr_dout_r2= is for 16x matrices

I suppose you only use 8x8 matrices, thus keep sr_dout_r1 for the second DOUT.

Here’s how you address one DOUT PCB:
sr_dout_r1=1
sr_dout_r1=2
sr_dout_r1=3
sr_dout_r1=4

and here’s how you address the next DOUT:
sr_dout_r1=5
sr_dout_r1=6
..

I thought it was but, the manual isn’t specific at that point so I wanted to check. I will give it a run later.

I assume the DOUT_MATRIX n= also changes?

DOUT_MATRIX n=1   rows=8   sr_dout_r1=1 inverted_row=0 mirrored_row=0 sr_dout_sel1=2 inverted_sel=0
DOUT_MATRIX n=2   rows=8   sr_dout_r1=3 inverted_row=0 mirrored_row=0 sr_dout_sel1=4 inverted_sel=0
DOUT_MATRIX n=3   rows=8   sr_dout_r1=5 inverted_row=0 mirrored_row=0 sr_dout_sel1=6 inverted_sel=0
DOUT_MATRIX n=4   rows=8   sr_dout_r1=7 inverted_row=0 mirrored_row=0 sr_dout_sel1=8 inverted_sel=0

Also!! on the old core8 i could connect 4 doutx4 can you connect 4 to the mb_ng??

ssp · January 28, 2020, 1:09pm

5 hours ago, latigid on said:

sr_dout_r1= is for 8x matrices
sr_dout_r2= is for 16x matrices

I suppose you only use 8x8 matrices, thus keep sr_dout_r1 for the second DOUT.

Here’s how you address one DOUT PCB:
sr_dout_r1=1
sr_dout_r1=2
sr_dout_r1=3
sr_dout_r1=4

and here’s how you address the next DOUT:
sr_dout_r1=5
sr_dout_r1=6
..

I thought it was but, the manual isn’t specific at that point so I wanted to check. I will give it a run later. Tx

EDIT: Ok looking through some old threads I see that it is n=1/2/3/4 etc. I’m good there.

ssp · January 28, 2020, 7:19pm

11 hours ago, latigid on said:

r_dout_r1= is for 8x matrices
sr_dout_r2= is for 16x matrices

I suppose you only use 8x8 matrices, thus keep sr_dout_r1 for the second DOUT.

Here’s how you address one DOUT PCB:
sr_dout_r1=1 sr_dout_sel1=2
sr_dout_r1=3 sr_dout_sel1=4
sr_dout_r1=5 sr_dout_sel1=6
sr_dout_r1=7

and here’s how you address the next DOUT:
sr_dout_r1=5
sr_dout_r1=6
…

ah now, looking at this again.. wouldnt it be like this? as the 2nd sr is for the common selectors.

sr_dout_r1=1 sr_dout_sel1=2
sr_dout_r1=3 sr_dout_sel1=4
sr_dout_r1=5 sr_dout_sel1=6
sr_dout_r1=7 sr_dout_sel1=8

ssp · January 28, 2020, 7:58pm

ok ran the code, it didnt work, will have to look into this a bit more.

is this correct?

Control 5x3 LED Digits to output 7bit values

RESET_HW

LCD “%CLED Digit Demo”

HW definitions for “Common Cathode” Digits

DOUT_MATRIX n=1   rows=8   sr_dout_r1=1 inverted_row=0 mirrored_row=0 sr_dout_sel1=2 inverted_sel=0
DOUT_MATRIX n=2   rows=8   sr_dout_r1=3 inverted_row=0 mirrored_row=0 sr_dout_sel1=4 inverted_sel=0
DOUT_MATRIX n=3   rows=8   sr_dout_r1=5 inverted_row=0 mirrored_row=0 sr_dout_sel1=6 inverted_sel=0
DOUT_MATRIX n=4   rows=8   sr_dout_r1=7 inverted_row=0 mirrored_row=0 sr_dout_sel1=8 inverted_sel=0

these can be changed for each 3 digits to test connectivity

ENC n= 1 sr=1 pins=0:1 type=non_detented
ENC n= 2 sr=1 pins=2:3 type=non_detented

EVENT_ENC id=1 fwd_id=LED_MATRIX:1 type=CC chn= 1 cc= 16
EVENT_ENC id=2 fwd_id=LED_MATRIX:4 type=CC chn= 1 cc= 17

First Value (3 digits) received via CC#16

EVENT_LED_MATRIX id=1 fwd_id=LED_MATRIX:2 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 16 lcd_pos=1:1:2 label=“1:%3d%B”
EVENT_LED_MATRIX id=2 fwd_id=LED_MATRIX:3 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=3 led_matrix_pattern=Digit3

Second Value (3 digits) received via CC#17

EVENT_LED_MATRIX id=4 fwd_id=LED_MATRIX:5 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 17 lcd_pos=1:1:2 label=“2:%3d%B”
EVENT_LED_MATRIX id=5 fwd_id=LED_MATRIX:6 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=6 led_matrix_pattern=Digit3

Third Value (3 digits) received via CC#18

EVENT_LED_MATRIX id=17 fwd_id=LED_MATRIX:18 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 18 lcd_pos=1:1:2 label=“3:%3d%B”
EVENT_LED_MATRIX id=18 fwd_id=LED_MATRIX:19 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=19 led_matrix_pattern=Digit3

Fourth Value (3 digits) received via CC#19

EVENT_LED_MATRIX id=20 fwd_id=LED_MATRIX:21 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 19 lcd_pos=1:1:2 label=“4:%3d%B”
EVENT_LED_MATRIX id=21 fwd_id=LED_MATRIX:22 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=22 led_matrix_pattern=Digit3

Fifth Value (3 digits) received via CC#20 (this is to test the first row on the second dout pcb)

EVENT_LED_MATRIX id=33 fwd_id=LED_MATRIX:34 led_matrix_pattern=Digit1 fwd_to_lcd=1 type=CC chn= 1 cc= 19 lcd_pos=1:1:2 label=“4:%3d%B”
EVENT_LED_MATRIX id=34 fwd_id=LED_MATRIX:35 led_matrix_pattern=Digit2
EVENT_LED_MATRIX id=35 led_matrix_pattern=Digit3

ssp · January 28, 2020, 9:50pm

the first two 3 digits on cc 16 and cc17 on the first dout work fine, the second dout is not working.. cant figure out why, all new wires and another new dout pcb as well.