Hello Folks

I am a beginner with LOGO and I have written a few programs with much frustration and ALOT of forum help.  My question is this - How do you keep a program / block diagram somewhat organized as it gets bigger?  Although my program works fine, it lacks organization and structure.  How do we keep things organized as we go?

As always, any advice is always appreciated

ixo65

Click the "Page Layout" icon in the menu bar at the top of the editor. A pop-up menu then opens in which you can set how many pages the diagram has vertically and horizontally.

See attached screen video.

 Thanks...I am aware of the page layout function.  I have it set to 2 wide X 3 high.  My question is referring more to how does one keep the program organized in general?  The program function doesn't matter.  Is there a better way to lay it out?

From my point of view: 
1. The line cut tool is your friend.
2. Use text to draw lines if you need them.
3. Size the page size with your printer settings.

Then view a concept for format in the attachment. It is only 4 pages from the 9 page whole. Because of intellectual rights I cannot share the unedited program.

qwazee

From my point of view: 
1. The line cut tool is your friend.
2. Use text to draw lines if you need them.
3. Size the page size with your printer settings.

Then view a concept for format in the attachment. It is only 4 pages from the 9 page whole. Because of intellectual rights I cannot share the unedited program.

All right folks - In my quest to organize my program I have indeed given it structure and some sense of flow but I have created another problem.  It seems my 0BA8 BM is now out of layout memory.  My layout is 33032 when the max is 30000.  Input 1 triggers 37 other points which created alot of mess an disorganization so I used the "Separate" command to clean everything up.  I didnt change the program other than separating those points.

Is there a way to make the layout more efficient to minimize memory use?  Can more memory be added?  There is some discussion of this in the forums with the general consensus that it does not effect operations?

Resources used:
Function Blocks         169/400
REM                     1/250
Digital Inputs          9/24
Digital Outputs         12/20
Flag                    15/64
Analog Inputs           0/8
Text Box                0/50
Text contents           0/50
Analog outputs          2/8
Program memory          2492/8500
Block names             21/100
Analog flags            8/64
Cursor keys             0/4
Shift register          0/4
Shift register bits     0/32
Open connectors         7/64
LOGO! TD Function keys  0/4
Network inputs          12/64
Network analog inputs   4/32
UDF types               0/16
UDF instances           0/64
Data Log                0/1
Network outputs         5/64
Network analog outputs  0/16
Analog Filters          0/8
Layout memory           33032/30000
Maximum nesting depth: I1-B001-B002-B003 INTERVAL-B004-B005 RANDOM-B006-B007 WAKE UP-B045-B046-B008-B055-Q1

Hello TwistedTeknician,

Personally, I'm pretty economical with the line cut tool.I prefer to arrange the blocks of a partial aspect close together. Texts are also reduced to the bare essentials.

Complete program descriptions of a project are better stored in the comments area under “Properties”.

For recurring or more complex circuit parts that can also be used in later projects, I like to use UDFs. I then develop and document these separately from the actual project, so that all I have to do is use them and describe the parameters.

However, these also need to be managed. To do this, I then use my own demo program, which describes this UDF in detail.

If necessary, I also use the comment descriptions of the individual blocks. The text colors also have a special meaning for me. For example, the text color red represents particularly important information that needs to be taken into account.

Ella_68

Hello TwistedTeknician,

Personally, I'm pretty economical with the line cut tool.I prefer to arrange the blocks of a partial aspect close together. Texts are also reduced to the bare essentials.

Complete program descriptions of a project are better stored in the comments area under “Properties”.

For recurring or more complex circuit parts that can also be used in later projects, I like to use UDFs. I then develop and document these separately from the actual project, so that all I have to do is use them and describe the parameters.

However, these also need to be managed. To do this, I then use my own demo program, which describes this UDF in detail.

If necessary, I also use the comment descriptions of the individual blocks. The text colors also have a special meaning for me. For example, the text color red represents particularly important information that needs to be taken into account.

Organize and document your project so that someone else or you can find your way around it years later. But too much description can also have the opposite effect.

Greetings, Ella_68

(translated with Google)

​

 Hello Ella_68

Thank you so much for your thoughts.  Using the help of the forums I have been able to organize my program in such a way that it is very clear and much easier to understand.  This particular program does nothing in the real world, it is just a learning exercise for me and something of a hobby.

Even with a hobby you shouldn't lose track...

greeting Ella_68