Phoenix Contact 2701027 NLC-050-024D-06I-04QTP-00A nanoLine Base Unit 24ßV/DC / PNP 2701027 Data Sheet
Product codes
2701027
Getting Started and Tutorial
2373_en_B
PHOENIX CONTACT
2-13
–
Have label blocks to identify what each block is doing at every step of the process – a
very important feature.
–
Vary from the examples in this guide depending on what is required, while staying
within their intended purpose and behavior.
2.5.1
Auto-mode Flow Chart
Because auto-mode flow charts are written to control process actions automatically, an
auto-mode flow chart is the equivalent of a company’s project manager with one or two main
priorities:
–
Initialize the project at the beginning of a flow chart to determine if desired inputs are at
the correct state and/or value, set all desired outputs to the correct state and/or value,
and then (usually) wait for input from a user and/or machine to begin controlling a
process automatically.
–
Control the project, which entails reading inputs, controlling actions, for example,
starting timers and reading when they’re done, updating counters, turning outputs
on/off.
Depending on the control process(es), the project could require:
–
One flow chart to control the entire project.
–
A separate flow chart for each major process to be controlled.
Because auto-mode flow charts control widely different processes, their layout and look
vary a great deal, but no matter what it controls, this type of flow chart does three things (see
–
Turn something on in an action block, like an output to open a greenhouse window, or
an output to turn on a sprinkler system, and start a timer to begin timing how long the
output should be on.
–
Monitor, in a branching block, if the thing turned on is done, for instance, did the
opening window hit a switch (an input device used to monitor if something is at a
desired position), or is the timer done – signaling that it’s time to turn off the sprinkler
system?
–
Turn off the same output in an action block that was turned on earlier.