7 segment display Pin outs?

[Kaellis991]

@SimPassion

Thanks for all that. I think I have a good handle on it. But more questions will no doubt arise later.

What I wanted to do, to make things less confusing, was to change the ID name for "hw_chr_display_add" to something other than com2_actv.
When I saw line 19 I was wondering why does it say com2_actv and then nav2_val.

Then it dawned on me that the ID name com2_actv is for the complete radio...both com and nav sides of the same radio.
And that ID is used for both the com2 coding and the nav2 coding.
That name can be anything and I think changing it to something that is more descriptive of the overall radio would show that it is a variable used in both the com and nav coding..

[jph]

@SimPassion

Thanks for all that. I think I have a good handle on it. But more questions will no doubt arise later.

What I wanted to do, to make things less confusing, was to change the ID name for "hw_chr_display_add" to something other than com2_actv.
When I saw line 19 I was wondering why does it say com2_actv and then nav2_val.

Then it dawned on me that the ID name com2_actv is for the complete radio...both com and nav sides of the same radio.
And that ID is used for both the com2 coding and the nav2 coding.
That name can be anything and I think changing it to something that is more descriptive of the overall radio would show that it is a variable used in both the com and nav coding..


image.png

I like your thinking Kirk, you seem to be getting a good grasp now. Yes, the naming is something useful to you and can be changed as required.
Nice one
Joe

[Kaellis991]

As first glance the ID name confused me....but I am easily baffled.

[Keith Baxter]

As first glance the ID name confused me....but I am easily baffled.

It was my bad. I should have changed it. I simply built on from the very first basic com1 code. But you got the idea.

Keith

[Kaellis991]

Absolutely no big deal....just need to keep things organized in my head.

[Kaellis991]

I thought I would post an update.
Both displays are working as they should be.

Thanks to all who helped with this radio build.

[SimPassion]

Just to post a screenshot for reference with standard pinout in similar LEDs display modules (3641AS in the case below), as of Kirk's ones
3641AS - 4 digits 7 segment LEDs display module with 12 default pins which may be plugged on MAX7219 boards
Just unplugged one from my MAX7219 boards :

[SimPassion]

Here's a clear and concise description of the use of 3641AS and similar with less or more digits, with direct connection to Arduino boards, which requires additional transistors and resistors, as already suggested by Joe

http://www.learningaboutelectronics.com ... rduino.php



 

[Kaellis991]

I have a question.
To take this radio build a step closer to a more professional implementation and to avoid having to use connectors, wires and stacked perfboards, could I use this diagram to create my own PCB (using EasyEDA and JLCPCB for fabrication) and utilizing one of the max7219 ICs that I have?
The wiring cross connections for the two (3) digit displays could be done on the PCB...correct?
I am guessing that I could then place the two displays close together using a customized board.

[SimPassion]

I have a question.
To take this radio build a step closer to a more professional implementation and to avoid having to use connectors, wires and stacked perfboards, could I use this diagram to create my own PCB (using EasyEDA and JLCPCB for fabrication) and utilizing one of the max7219 ICs that I have?
The wiring cross connections for the two (3) digit displays could be done on the PCB...correct?
I am guessing that I could then place the two displays close together using a customized board.

Well Kirk, I found an issue in the diagram, for me there's no reason for which the ISET line should intersect with the G segment and the R1 10K resistor up to VCC
So I would wait a little until others provide confirmation on this here ... !???