March 29, 2013

4-digit-7-segment display

Introducion


In this tutorial I'm going to show you the basics of the working of a 7 segment display, and how to use, when you have 4 in a row. So lets take look:

So that"s it. I ordered it from dx.com half years ago, because it was only $2, and I was interested in it. But in the beginning it was too hard for me, I just can't make it work. It has 6+6 so 12 pins in the back, and has no sign about them, as here:
So I took it away, and didn't even touch it till this month. We learned about 7 segment displays, and I was wondering, what if I could make my work. So I looked up on the internet, and find, that this display has its own library, here: https://github.com/sparkfun/SevSeg First I just downloaded and tried it, and it worked. So I looked into the code, and started to understand the inner working. So basically this display has 4*8 leds ( because each the number has 7, and there are 4 dots also). How is it possible then to control them only with 12 pins? Don't we need 4*8=32 pins for that? Yes, theoretically we would need 32 pins. But then, how does it works? The trick is, that we don't need to light up all lightning led constantly. If they blink very fast, we will see as if they're lighting. So there is 4 pin for specifying the number, and then whit the rest 8 pins we can control the 8 leds of the number. And if we change between the numbers very fast, nobody will be able to see the blinking. And changing it very fast is not a problem, when we are using arduino.

Inner working

Okay, you can say, but how is it possible? I mean, how does it work? It's quiet simple, using the special attribution of the led, that it's a diod, so the current can flow only in one direction. So here is  how to show a 5 in the 3. place:
(Red lines are HIGH, blues are LOW, because my display is common anode type. If yours is common cathode, just change every HIGH to LOW and )So as you can see 8 of the 12 pins is connected to each led, but in every number. The other 4 pins are connected to the other side of the leds but one by every number. The led will show up, if it get a red line (HIGH) from the top and a blue line (LOW) from the button. Otherwise it stays dark. Try to understand this part, because many-many things works in this principle like led cubes, and matrix displays

Using it

The pins are numbered this way:
And connect these pins of the display to those pins of the arduino:

   //Declare what pins are connected to the digits
   int digit1 = 2; //Pin 12 on my 4 digit display
   int digit2 = 3; //Pin 9 on my 4 digit display
   int digit3 = 4; //Pin 8 on my 4 digit display
   int digit4 = 5; //Pin 6 on my 4 digit display
   
   //Declare what pins are connected to the segments
   int segA = 6; //Pin 11 on my 4 digit display
   int segB = 7; //Pin 7 on my 4 digit display
   int segC = 8; //Pin 4 on my 4 digit display
   int segD = 9; //Pin 2 on my 4 digit display
   int segE = 10; //Pin 1 on my 4 digit display
   int segF = 11; //Pin 10 on my 4 digit display
   int segG = 12; //Pin 5 on my 4 digit display
   int segH= 13; //Pin 3 on my 4 digit display

After that we can control the display from the arduino. For this here is my code:
(NOTE: I've used Arduino MEGA for this tutorial and connected the display to pins 22-33, so if you use an UNO, change it as shown under)

boolean show[4][8];

void setup()
{
  //actually we don't need this part, but it's always good to know the wiring 
   //Declare what pins are connected to the digits
   int digit1 = 22; //Pin 12 on my 4 digit display
   int digit2 = 23; //Pin 9 on my 4 digit display
   int digit3 = 24; //Pin 8 on my 4 digit display
   int digit4 = 25; //Pin 6 on my 4 digit display
   
   //Declare what pins are connected to the segments
   int segA = 26; //Pin 11 on my 4 digit display
   int segB = 27; //Pin 7 on my 4 digit display
   int segC = 28; //Pin 4 on my 4 digit display
   int segD = 29; //Pin 2 on my 4 digit display
   int segE = 30; //Pin 1 on my 4 digit display
   int segF = 31; //Pin 10 on my 4 digit display
   int segG = 32; //Pin 5 on my 4 digit display
   int segDP= 33; //Pin 3 on my 4 digit display


   for(int i=22; i < 34; i++) pinMode(i, OUTPUT);
   
   //adding the text or numbers
   for(int i=0; i < 4; i++){for(int j=0; j < 8; j++) show[i][j]=true;} //if true: the led is dark, if false the led shows up
   //A
   show[0][0]=false;
   show[0][1]=false;
   show[0][2]=false;
   show[0][4]=false;
   show[0][5]=false;
   show[0][6]=false;
   //n
   show[1][2]=false;
   show[1][4]=false;
   show[1][6]=false;
   //n
   show[2][2]=false;
   show[2][4]=false;
   show[2][6]=false;
   //a
   show[3][2]=false;
   show[3][3]=false;
   show[3][4]=false;
   show[3][6]=false;
   show[3][7]=false;

}



void loop()
{
for(int i=0; i < 4; i++) //run on the digits
{
 for(int j=0; j < 8; j++) digitalWrite(j+26, true); //turn off every segment
digitalWrite(22+i, true); //turn the actual number on
digitalWrite(22+(i+1)%4, false); //and 
digitalWrite(22+(i+2)%4, false); //fade
digitalWrite(22+(i+3)%4, false); //the rest

for(int j=0; j < 8; j++)
{
digitalWrite(j+26, show[i][j]); //turn the specified segments on as defined in the array show
}
delay(1);
}

}

And the same code for arduino UNO:

boolean show[4][8];

void setup()
{
   //I've deleted the unnecessary part from here
   for(int i=2; i < 14; i++) pinMode(i, OUTPUT);
   
   //adding the text or numbers
   for(int i=0; i < 4; i++){for(int j=0; j < 8; j++) show[i][j]=true;} //if true: the led is dark, if false the led shows up
   //A
   show[0][0]=false;
   show[0][1]=false;
   show[0][2]=false;
   show[0][4]=false;
   show[0][5]=false;
   show[0][6]=false;
   //n
   show[1][2]=false;
   show[1][4]=false;
   show[1][6]=false;
   //n
   show[2][2]=false;
   show[2][4]=false;
   show[2][6]=false;
   //a
   show[3][2]=false;
   show[3][3]=false;
   show[3][4]=false;
   show[3][6]=false;
   show[3][7]=false;

}



void loop()
{
for(int i=0; i < 4; i++) //run on the digits
{
 for(int j=0; j < 8; j++) digitalWrite(j+26, true); //turn off every segment
digitalWrite(2+i, true); //turn the actual number on
digitalWrite(2+(i+1)%4, false); //and 
digitalWrite(2+(i+2)%4, false); //fade
digitalWrite(2+(i+3)%4, false); //the rest

for(int j=0; j < 8; j++)
{
digitalWrite(j+6, show[i][j]); //turn the specified segments on as defined in the array show
}
delay(1);
}

}

If it runs perfectly you should see "Anna" on the screen, like shown here:

You can control the text with changing the array show. For example for the first character "A" we need 6 segment from the first display: a,b,c,e,f,g. So because it's the first number, we change show[0][*] and because a=0, b=1, c=2, e=4, f=5, g=6, so

   //A
   show[0][0]=false;
   show[0][1]=false;
   show[0][2]=false;
   show[0][4]=false;
   show[0][5]=false;
   show[0][6]=false;
I think it's not so complicated :)

Deeply into the case

As you see, it use 12 pins, which actually all of the digital pin of a normal arduino UNO. So what can we do? If you think about it, there is a redundant information in the system, because every time only one of the 4 digit-pin is HIGH, so it can be controlled with a demultiplexer (aka demux). It works so:
So I0 is connected to Vcc, and F0-F3 to the 4 digit pin of the display. So now if you want a HIGH on F0, you only have to give LOW and LOW on S1 and S0, for F1 LOW and HIGH, for F2 HIGH and LOW and for F3 HIGH and HIGH. So in the end you save 2 pins, which are not the word, but sometimes can be very helpful.

I hope this tutorial was helpful, if you have any question, please feel free to write or comment

Best regards:

Mark

March 14, 2013

Homemade Shooting Gallery 1.0 (LabVIEW Image Processing)

Introduction:

Several years ago I've seen a shooting gallery in the Palace of Miracles. They've solved it with a laser gun (laser with invisible frequency) and a photosensitive target. I wanted to do the same, but much cheaper, without a photosensitive target. So I thought about visible laser dots and image processing with a webcam watching the target. That sounded much cheaper and easier and I also wanted to learn the basics of image processing for other projects, so I've started.

Purpose of the project:

So my project has basically 3 parts: a gun, that emit a red laser dot for a 0.1-0.2 seconds, a target made of paper and a software part with a webcam, that monitors the target, recognizes the laser-dot and calculates your score.

What you need:

for the gun:

  • a laser-diode, like this or these
  • a battery
  • button
  • some kind of timing IC with capacitors and resistor, more about it later
  • bunch of wires
  • some kind of base. Mine was made out of wood.
for the target:
  • just design and print something like this in A3 paper (or bigger) (mine's here)
for the software part:
  • webcam
  • for the image processing LabVIEW with NI-IMAQ and NI Vision Acquisition. I've used LabVIEW 2009, but I suppose other versions work too.

First step: the gun

It's not so hard to build a gun with a button and a laser diode and if you press the button, the diode will show up. But I needed something more. I wanted the laser dot only showed up for 0.1-0.2 second, because you know, that would be more realistic and otherwise people can just move the dot to the middle of the target. Of course it wouldn't be so hard with arduino, but I wanted to do it simpler with only IC(s), resistor and capacitors.
First I looked around on the internet, and found, that almost every timing problem has a solution, called IC 555. I've made very nicely blinking leds and I can even make a led, that shows up when you press the button and after a controllable time it turns off. The only problem was that this time had to be longer than the button-pressing-time. So I asked about it on a mailing list, and got several answers. They recommended a site where is a description about this, but it just didn't want to work. So I asked my digital-electronics-teacher, and he recommended the 74122 IC (actually he recommended 74121, but I could buy only 74122, but it's almost the same). With this I have solved, that if you pressed and release the button, then it shows up for a changeable time. So here is the wiring:

For debugging I connected an other button, which is a simple press-light wiring. After testing on breadboard, I built it and soldered together:



It looks good, but the laser dot was just too dim, and from 5 m I can't even see it, so I've used the debugging-button for the test and I'm still trying to find a good solution.
That is also a problem, that I forgot to unplug it for the night, and till morning the battery discharged, and I had to buy a new one. So I'll integrate a new switch between the battery and the others.

Second step: the LabVIEW programming

As I mentioned one of my previous post I've found a youtube tutorial for image processing. I've edit it a little bit to pattern the middle of the target and the laser dot:
When the program starts to process the image of the webcam, first it makes the picture black-and-white, after that starts looking for the patterns. If it finds these, it gives back the coordinates of the en-frame rectangle. After that it count the coordinate of the middle-point of the target and the dot (for this we only need the top-left and down-right corner of the rectangle. It also shows these coordinates as an array). Sometimes the processing algorithm loses the match for a second and give back 0, so I've made a subVI for filter it and give back the previous value:
So it knows the coordinates of the 2 middle-points. Then it counts the distance between these points, subtracts it from 100 and this is your score. I store it as unsigned int, so if it is less than 0, it's going to be 0.

But I got a strange error. If I cover the camera, => there isn't any pattern, all of the coordinates will be the same, the previous version of the first coordinate. After 10 minute of google, I found all my subVIs are using the same memory, so I have to clone them to solve the problem. Open the subVI, File > VI Properties and change it so:
After that, it worked fine, here is the result:

Summary

As you can see on the video, sometimes it doesn't recognize the dot. It can be because the target's lines are too thick and the dot gets lost between them. I've showed it to my teacher, and he recommended to mark the edge of the target and only looking for the dot inside of the target. He said, that will make the program run faster and smoother. I also have to rethink the gun, so version 2.0 coming soon.

Best regards:
Mark