Phoenix Contact 2701027 NLC-050-024D-06I-04QTP-00A nanoLine Base Unit 24ßV/DC / PNP 2701027 Data Sheet
Product codes
2701027
nanoNavigator
2-12
PHOENIX CONTACT
2373_en_B
data item. For instance, some input names in a greenhouse project might be: “Greenhouse
3 Temperature”, “GH3 Water Flow Rate”, “GH3 Windows Opened”, “GH3 Windows
Closed”; output names might be: “GH3 Valve”, “Open GH3 Windows”, “Close GH3
Windows”, “GH3 Sun Lamps”.
nanoNavigator supports the nine data item types available on the nanoLC. They are:
–
Input – The number available depends on the configuration of the nanoLC. Inputs are
on or off.
–
Analog Input – An unsigned integer that represents gradually changing
voltages/values input to the nanoLC. The number available depends on the
configuration of the nanoLC. See “Handling Analog Values” on page 5-12.
–
Output – The number available depends on the configuration of the nanoLC. Outputs
are on or off.
–
Analog Output – An unsigned integer that represents gradually changing
voltages/values output from the nanoLC. The number available depends on the
configuration of the nanoLC. See “Handling Analog Values” on page 5-12. Analog
inputs provide gradually changing voltages/values.
–
Timer/Counter – Maximum of 64 total timers and counters.
–
High-Speed Counter – Maximum of 2. May be enabled or disabled by project.
–
Register – Maximum of 64. Configurable as Unconfigured, Integer, Date, Time of Day,
Duration (HH:MM:SS or msec). Registers can have an initial value and may be
–
Flag – Maximum of 128 binary flags. Flags can have an initial value (set=1) and may be
–
Keypad Key – Maximum of 16 keys available if the optional Operator Panel is present
on the nanoLC. The keys include the digits 0-9, four arrow keys, and “OK”. In addition,
there is a “Message Input Ready” Keypad Key data item.
2.5
Designing a Control Project
Control projects generally need to accomplish the following four tasks:
–
Control a process by monitoring inputs and manipulate outputs in the desired order
–
Display status information (normal conditions)
–
Display diagnostic information (abnormal conditions)
–
Recover from an error
When considering a design, it is important to create modular flow charts that work on small
sections of the total project. Using modular design techniques makes it easier to develop,
verify, and maintain a project.
Because there are common needs in almost every project, certain flow chart structures
have become common as well. Each is recognized by its characteristic shape in the same
way that building tools (tape measure, hammer, circular saw, etc.) are recognized by their
shapes, so it’s important to note that flow charts:
–
Commonly consist of repeating block patterns. These patterns become easy to
recognize what they do by how they’re laid out.
–
Don’t stop at the end, but return to a desired point (determined by the application) in the
flow chart to do the work all over again.
The examples on the following pages relate the basics of what needs to be done. They in
no way account for the specific events and requirements of each project.