Do-more software how to build a sequence logic?

Hi All,
I am an absolute beginner in terms of programming, and I was told to create sequence logic for traffic lights assignment, and I am stuck. I started, however, once I energised the timer, it keeps timing over and over the preset value without turning on the next contacts on the ladder. Am I missing something there (please see the attachment)? Please help.

Hi, and welcome to the forum. You are doing one thing correct which is posting what you have done/tried and then asking for help. A lot of folks, especially students, will do just the opposite and want the pros here to do their homework. I am not real familiar with this platform, however just a WAG it looks like the first timer is an Off delay? I rarely use those. Also I don't see the timer structure "tag" on the first timer like on the second timer, and it would seem the second timer the .DN bit would be green, because it is not done, like an XIO instruction in A-B. Just some observations and I'm sure I have missed something. Again, welcome!!

Do the colored bars alongside rungs 3 & 4 mean anything?

Hi, thanks for that, I'll have a lot at it later on, and post the results. Thanks

I'm sure the software has some sort of compile feature, checks for errors either at the rung level or the entire program. Those bars could mean many things, perhaps an error or perhaps those rungs are in edit mode? Sorry I can't be of more help. Let us know how it goes.

The bars mean the program hasn't been saved to disk and have not been accepted by the compiler.

This is why it isn't working. The edits need to be accepted and written to the PLC.

Another thing I see that may be an issue, you are relying on Y0 being energized to start timer T0. However, as soon as T0 is finished, T0.DN will change states causing Y0 to drop out and resetting your timer.

For any given homework assignment or task at work, you must consider these instructions as the customers specifications.
1. read the specifications several times.
2. write down your understanding of what you read in a step by step fashion.
3. review what you wrote down and see if it makes since, modify if necessary.
4. step through your notes again this time, you are the one following the instructions.
In other words, you are the plc. Write down on paper the events you are doing.
For example, turn on hydraulic motor 1, write down hydraulic motor 1 on.
If a sensor is needed, write that down.
5. continue through the instructions. When you turn off the motor, mark a line thru it.
6. go through your instructions with all the sensors, motor aux. contacts, outputs
Documented. Modify if necessary.
7. repeat step 6 until no changes are made.
8. Try to group your data words into some organized fashion.
The more programs you write, the more organized you become
9. write the plc program using your notes.
10. install the program and leave in program mode if possible so you can to debug your i/o
11. Question for you, when is a machine and plc the most dangerous and why?
When it’s first powered on – when power is first applied to a machine, you don’t know
How things are wired. When you energize the plc outputs, you don’t know how things
are wired. When the plc is put into run mode the first time, it will do what you told it to do,
NOT what you wanted it to do.
12. debug the program.
13. DOCUMENT EVERYTHING!!!
you may remember things today, but in 5 years and hundreds of programs later, you won't
remember, so DOCUMENT EVERYTHING.
14. MAINTENANCE is your best friend or your worst enemy.
if you work with them and find out what they can do, write the program where they can
trouble shoot the program. they will be able to fix the problem and everyone will be happy.
BUT
if you write the program to where you are the only one who understands what is going on,
maintenance can't fix the issue, the machine is down, production is down, management hears about
it, your boss hears about it, then you hear about it - rewrite the program or else.
you get calls all hours of the day and night.

this still holds true, a machine can cost a billion dollars, but it's not worth 10 cents if
maintenance cannot trouble shoot the issue and fix the issue.

everyone has their own style of programming and you must develop your own way as well.

this is the best advice I can give anyone.
if others has more / better suggestions, feel free to post.

james