We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am trying to program the 8051 for a "Pelican" type pedestrian road crossing. It should control the red, amber and green lights for the traffic, the red and green pedestrian lights, and the bleeper. I have written some code but unfortunately it does not work. Bits 0 to 5 of P1 are supposed to control the lights and the bleeper and bit 0 of P2 is supposed to control the pedestrian button. Any ideas where the problem is? Code size limit is 2K. Thanks! Marko
#include <reg51.h> sbit red_traf=P1^0; sbit amber_traf=P1^1; sbit green_traf=P1^2; sbit red_ped=P1^3; sbit green_ped=P1^4; sbit bleeper=P1^5; sbit button=P2^0; unsigned char count; void delay_vshort() { unsigned int x; for (x=0;x<65536;x++); } void delay_short() { unsigned int x; for (x=0;x<131072;x++); } void delay_long() { unsigned int x; for (x=0;x<1048576;x++); } main() { P2 = 0xff; s0: green_traf=1; red_ped=1; if (button==1) goto s1; else goto s0; s1: amber_traf=1; red_ped=1; delay_short(); goto s2; s2: red_traf=1; green_ped=1; bleeper=1; delay_long(); goto s3; s3: for (count=0;count<5;count++) { amber_traf = 1; green_ped = 1; delay_vshort(); amber_traf = 0; green_ped = 0; delay_vshort(); } goto s4; s4: amber_traf=1; red_ped=1; delay_short(); goto s0; }
Quite a number of schools have small boards with traffic lights, since they represent an interesting concept and the end goal is easy to grasp.
It is easy to start with a fully timer-based solution, and then extend it with faked sensors, that the logic should respond to.
Thanks for all suggestions so far. I do ralize that the code is very poorly written, however it is written for self educational purposes only. I am not going to use it for a real pedestrian crossing - I am not insane. Again all I wish is to make the program work and learn from it. I did rewrite the code because there were some obvious mistakes in there regarding the logic behind it. Here is the code:
#include <reg664.h> //Register map for 8051. sbit red_traf=P1^0; //Red traffic light is connected to bit 0 of P1. sbit amber_traf=P1^1; //Amber traffic light is connected to bit 1 of P1. sbit green_traf=P1^2; //Green traffic light is connected to bit 2 of P1. sbit red_ped=P1^3; //Red pedestrian light is connected to bit 3 of P1. sbit green_ped=P1^4; //Green pedestrian light is connected to bit 4 of P1. sbit bleeper=P1^5; //Bleeper is connected to bit 5 of P1. sbit button=P2^0; //Pedestrian button is connected to bit 0 of P2. unsigned char count; void delay_vshort() //This defines a very short delay. { unsigned int x; for (x=0;x<65536;x++); } void delay_short() { //This defines a short delay. unsigned int x; for (x=0;x<131072;x++); } void delay_long() //This defines a long delay. { unsigned int x; for (x=0;x<1048576;x++); } main() { P1 = 0x00; //P1 defined as an output port. P2 = 0xff; //P2 defined as an input port. s0: green_traf=1; //Green traffic light is on. red_ped=1; //Red pedstrian light is on. if (button==1) goto s1; //Check if button was pressed. else goto s0; s1: green_traf=0; //Switch off green traffic light. amber_traf=1; //Switch on amber traffic light. delay_short(); //Leave amber traffic light on for a short time. s2: green_traf=0; //Switch off green traffic light. red_traf=1; //Swich on red traffic light. red_ped=0; //Switch off red pedestrian light. green_ped=1; //Switch on green pedestrian light. bleeper=1; //Switch on the bleeper. delay_long(); //Remain in the same state for a long time. s3: red_traf=0; //Switch off red traffic light. for (count=0;count<5;count++) //This will make amber traffic and green pedestrian light //flash five times. { amber_traf = 1; //Switch amber traffic light on. green_ped = 1; //Switch green pedestrian light on. delay_vshort(); //Wait for a very short time. amber_traf = 0; //Switch both previous lights off. green_ped = 0; delay_vshort(); } s4: bleeper=0; //Turn off the bleeper. green_ped=0; //Turn off green pedestrian light. amber_traf=1; //Turn on amber traffic light. red_ped=1; //Turn on red pedestrian light. delay_short(); //Wait for a short time. goto s0; //Return to the beginning. }
The whole idea is to use the pin 0 of P2 as an input(=pedestrian button). But when I run the program the traffic amber and red pedestrian light stay on indefinetly. Does anybody know if I defined P1 and P2 as input and output ports correctly? I thank you again for your precious time. Regards, Marko
I had to make your code readable to comment on it, so I include it for the benefit of otheres
include <reg664.h> //Register map for 8051. sbit red_traf=P1^0; //Red traffic light is connected to bit 0 of P1. sbit amber_traf=P1^1; //Amber traffic light is connected to bit 1 of P1. sbit green_traf=P1^2; //Green traffic light is connected to bit 2 of P1. sbit red_ped=P1^3; //Red pedestrian light is connected to bit 3 of P1. sbit green_ped=P1^4; //Green pedestrian light is connected to bit 4 of P1. sbit bleeper=P1^5; //Bleeper is connected to bit 5 of P1. sbit button=P2^0; //Pedestrian button is connected to bit 0 of P2. unsigned char count; void delay_vshort() //This defines a very short delay. { unsigned int x; for (x=0;x<65536;x++); } void delay_short() //This defines a short delay. { unsigned int x; for (x=0;x<131072;x++); } void delay_long() //This defines a long delay. { unsigned int x; for (x=0;x<1048576;x++); } main() { P1 = 0x00; //P1 defined as an output port. P2 = 0xff; //P2 defined as an input port. s0: green_traf=1; //Green traffic light is on. red_ped=1; //Red pedstrian light is on. if (button==1) goto s1; //Check if button was pressed. else goto s0; s1: green_traf=0; //Switch off green traffic light. amber_traf=1; //Switch on amber traffic light. delay_short(); //Leave amber traffic light on for a short time. s2: green_traf=0; //Switch off green traffic light. red_traf=1; //Swich on red traffic light. red_ped=0; //Switch off red pedestrian light. green_ped=1; //Switch on green pedestrian light. bleeper=1; //Switch on the bleeper. delay_long(); //Remain in the same state for a long time. s3: red_traf=0; //Switch off red traffic light. for (count=0;count<5;count++) //This will make amber traffic and green pedestrian light flash five times. { amber_traf = 1; //Switch amber traffic light on. green_ped = 1; //Switch green pedestrian light on. delay_vshort(); //Wait for a very short time. amber_traf = 0; //Switch both previous lights off. green_ped = 0; delay_vshort(); } s4: bleeper=0; //Turn off the bleeper. green_ped=0; //Turn off green pedestrian light. amber_traf=1; //Turn on amber traffic light. red_ped=1; //Turn on red pedestrian light. delay_short(); //Wait for a short time. goto s0; //Return to the beginning. }
go through your code and follow it under the assumption that the button is held only for a millisecond
fix what you see by that and then come back
Erik
Thanks for all suggestions so far.
Did you read my comments about the size of an integer in '51 C ?
All of your delay loops are still endless loops. They will never return. You program will enter an endless loop before getting to s2. Does the compiler emit any warnings ?
I am afraid I do not understand.
step through your code 'on paper' follow the process when the button is only detected pressed once.
THAT is known as debugging
1.I did fix that but the problem is that now the delays are way too small. How do I program three different delays each 0.5s, 4s and 10s long respectively? 2.The compiler did not emit any warnings apart from these: TRAFFICLIGHT.C(46): warning C280: 's2': unreferenced label TRAFFICLIGHT.C(54): warning C280: 's3': unreferenced label TRAFFICLIGHT.C(66): warning C280: 's4': unreferenced label To get rid of these warnings I was using unnecessary goto statements at the end of each state. Regards, Marko
A permanent fix for timing loops - use the hardware. You might use a timer in the chip to count x clock cycles.
The quickie: Nest several loops. Create a function that takes about 1 ms.
Call that function 500 times to get a 0.5 second loop.
Addendum: Just note that a delay created using a loop can (and most often will) greatly change in speed depending on used compiler, and used optimization mode, memory model, version of the compiler, ...
Don't rely on it for production code.
Just note that a delay written in C created using a loop can (and most often will) greatly change in speed depending on used compiler, and used optimization mode, memory model, version of the compiler
a delay loop written in assembler, however, only is affected by the execution of interrupts.
I do ralize that the code is very poorly written, however it is written for self educational purposes only.
You have that dangerously backwards. Knowingly writing poor code may sometimes be justified by pressing circumstances (e.g. momentary lack of time to do it right), but never in a setting of self-education.
If you can't do it properly with practically infinite amounts of time on your hands, how will you ever do an acceptable job under stress?
How do I program three different delays each 0.5s, 4s and 10s long respectively?
Use timers. That's what your controller has them for.
To get rid of these warnings I was using unnecessary goto statements at the end of each state.
As opposed to just throwing out those useless labels, that is? Wow, that's impressively sick.
I do not work in a programming business and most probably never will. As far as my area of expertise is concerned I do think that I do more than an acceptable job under stress.
I definetly need to learn a lot more about programming. But I do think that you cold do well with a simple etiquette course. Calling people sick just because they do not know how to write good code is a bit over the edge.
Calling people sick just because they do not know how to write good code is a bit over the edge
In many peoples eyes using 'goto' is 'sick' but they did not say so (I would, in most cases, consider a goto 'stupid' but did not say so.) All restrained themselves and said 'not advisable'
Now you compound the issue by adding a goto for no other purpose than getting rid of an 'unused label' warning and I can easily see that makes somebody not able to hold his tongue.
Do note, you added these labels after being informed that goto was 'not advisable'
So, there is no reason to get miffed becuase of a word, I could easily get miffed over some of your statements, but shall not give examples.
Thanks for your help guys. I have learned a great deal about philosophical issues in programming. Unfortunately I did not learn that much about actual coding itself. Consider the matter ad acta. Thanks again! Best regards, Marko