SpaceLogic HMIs - Operator Display Reference Guide
SpaceLogic HMIs - Operator Display Reference Guide
Operator Display
Reference Guide
04-33049-04-en
April 2023
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and furnished
for informational use only. No part of this guide may be reproduced or transmitted in any
form or by any means (electronic, mechanical, photocopying, recording, or otherwise),
for any purpose, without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide or
its content, except for a non-exclusive and personal license to consult it on an "as is"
basis. Schneider Electric products and equipment should be installed, operated,
serviced, and maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information
contained in this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.
Purpose of This Guide
This guide provides information about the administration and configuration of
SpaceLogic™ Operator Display, and how it is used to provide an easy-to-use interface
through which building managers, technicians, janitors, and security guards can locally
access the EcoStruxure Building Management systems from a Human Machine Interface
(HMI) terminal. This information is intended to help you understand Operator Display so
you can perform common and administrative tasks using the Operator Display user
interface.
Safety Information
Important Information
Read these instructions carefully and look at the equipment to become familiar with
the device before trying to install, operate, service or maintain it. The following
special messages may appear throughout this bulletin or on the equipment to warn
of potential hazards or to call attention to information that clarifies or simplifies a
procedure.
The addition of this symbol to a “Danger” or “Warning” safety label indicates that an
electrical hazard exists which will result in personal injury if the instructions are not
followed.
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible injury
or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death or
serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death
or serious injury.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury.
Please Note
Electrical equipment should be installed, operated, serviced, and maintained only by
qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction,
installation, and operation of electrical equipment and has received safety training to
recognize and avoid the hazards involved.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
• Change passwords regularly to help prevent unauthorized access to device settings,
controls, and information.
• Do not share accounts. Each user must have their own account.
• When creating user and display names, it is important to avoid using personal
information, and to consider regional privacy policies. Display names will appear in
event logs to identify who performed operations on the device.
• It is recommended that log files be encrypted before transmission to help with security
and privacy.
• Disable unused services and default accounts to help minimize pathways for malicious
attackers. Factory reset devices when they are decommissioned to help ensure all site,
user, and log information is removed.
• Place networked devices behind multiple layers of cyber defenses (such as firewalls,
network segmentation, and network intrusion detection and protection).
• Use the recommended cybersecurity safety measures (for example, least privilege,
separation of duties) to help prevent unauthorized exposure, loss, modification of data
and logs, or interruption of services.
Failure to follow these instructions can result in loss of data or unauthorized system
access.
Operator Display
Table of Contents
1 SpaceLogic Operator Display .................................................................................. 9
1.1 Operator Display Overview ............................................................................. 10
1.2 Logging on to Operator Display ....................................................................... 12
1.3 User Account Handling .................................................................................... 13
1.4 User Account Administration ........................................................................... 14
1.5 Creating a User ............................................................................................... 16
1.6 Changing Password ........................................................................................ 17
1.7 Deleting a User ................................................................................................ 18
1.8 Configuring User Settings ............................................................................... 18
1.9 Configuration ................................................................................................... 19
1.10 Hardening Specifics ........................................................................................ 19
1.11 BACnet Objects .............................................................................................. 21
1.12 Configuration Menus ....................................................................................... 23
1.13 Identifying the Target Device for a Configuration Menu Object ....................... 24
1.14 Configuration Menu Visibility Operators List .................................................... 24
1.15 Configuring the IP Network Communication .................................................... 26
1.16 Configuring the BACnet/IP Network Communication ...................................... 26
1.17 Discovering a Device ....................................................................................... 27
1.18 Date and Time Handling .................................................................................. 27
1.19 Configuring Date and Time .............................................................................. 28
1.20 Configuring Operator Display to be Time Master ............................................ 29
1.21 Upgrading the Firmware .................................................................................. 29
1.22 Recovering Operator Display (Factory Reset) ................................................. 30
1.23 Erasing All Data ............................................................................................... 31
1.24 Configuring the Language ............................................................................... 32
1.25 Configuring the Units ....................................................................................... 32
1.26 Adjusting the Backlight .................................................................................... 32
1.27 Alarm Handling ................................................................................................ 33
1.28 Acknowledging an Alarm ................................................................................. 35
1.29 Value Editing ................................................................................................... 35
1.30 BACnet Command Priorities ........................................................................... 36
1.31 Configuring the BACnet Command Priority Level for Forced Values .............. 39
1.32 Editing an Analog Input, Output, or Value ....................................................... 40
1.33 Editing a Binary Input, Output, or Value .......................................................... 40
1.34 Editing a Multi-State Input, Output, or Value ................................................... 41
1.35 Forcing an Analog Input, Output, or Value ...................................................... 41
1.36 Forcing a Binary Input, Output, or Value ......................................................... 42
1.37 Forcing a Multi-State Input, Output, or Value .................................................. 43
1.38 Schedule Handling .......................................................................................... 43
1.39 Schedule Types .............................................................................................. 44
1.40 Analog Schedules ........................................................................................... 45
1.41 Digital Schedules ............................................................................................. 45
1.42 Multi-State/Enumerated Schedules ................................................................. 46
1.43 Schedule Events ............................................................................................. 47
1.44 Weekly Events ................................................................................................. 48
1.45 Viewing a Schedule Default Value .................................................................. 49
1.46 Adding a Weekly Event ................................................................................... 49
1.47 Editing a Weekly Event .................................................................................... 50
1.48 Exception Events ............................................................................................. 50
1.49 Adding a Single Date Exception Event ........................................................... 52
1.50 Adding a Date Range Exception Event .......................................................... 53
1.51 Adding a Calculated Date Exception Event ..................................................... 54
1.52 Adding a Calendar Exception Event ............................................................... 55
1.53 Editing a Single Date Exception Event ............................................................ 57
1.54 Editing a Date Range Exception Event ............................................................ 58
1.55 Editing a Calculated Date Exception Event ..................................................... 59
The simplified user interface and the intuitive touch-screen navigation make it easy to
operate and maintain the system. Operator Display communicates quickly over
BACnet/IP open protocol with a direct connection to SpaceLogic MP or RP controllers,
IP-IO modules, AS-B or AS-P servers. Only one Operator Display is required per
cabinet in the equipment room, so there is no need for more displays when a controller
is added (up to seven controllers). The operator can view and acknowledge alarms, edit
schedules, and adjust setpoint temperatures. Authorized operators can also view and
override inputs, outputs, and other virtual points.
For more information, see section 1.3 “User Account Handling” on page 13.
For more information, see section 1.27 “Alarm Handling” on page 33.
For more information, see section 1.29 “Value Editing” on page 35.
For more information, see section 1.38 “Schedule Handling” on page 43.
For more information, see section 1.18 “Date and Time Handling” on page 27.
For more information, see section 1.62 “Trends Handling” on page 67.
1.1.7 Configuration
As an administrator you need to configure Operator Display and make it part of the IP
network and the BACnet/IP network so you can discover and add the devices.
For more information, see section 1.3 “User Account Handling” on page 13.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
• Wipe screen after use to avoid fingerprints from password entry remaining on the
screen.
• Do not share accounts between multiple users.
Failure to follow these instructions can result in loss of data or equipment damage.
4. Tap Login.
The system administrator creates a user account with your needed permissions so you
can access Operator Display and perform your assigned tasks. For more information,
see section 1.2 “Logging on to Operator Display” on page 12.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
• Wipe screen after use to avoid fingerprints from password entry remaining on the
screen.
• Do not share accounts between multiple users.
Failure to follow these instructions can result in loss of data or equipment damage.
Administrator
A building manager who has complete access to the configuration of the Operator
Display, including user administration.
Technician
A maintenance person or janitor who uses the Operator Display to interact with devices
without being able to modify the configuration.
Viewer
A security guard who can view Operator Display features like alarms, but is not
authorized to perform actions.
1.3.1 Passwords
The minimum number of characters and how many lowercase, numeric, and special
characters that are required when you create a password depends on how the Operator
Display user settings are configured.
When you change your password, the password requirements for the Operator Display
are displayed on the Change password screen. For more information, see section 1.6
“Changing Password” on page 17.
!*#$%'()*+-/:;<=>?@[\]^_'{|}~
For more information, see section 1.4 “User Account Administration” on page 14.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
• Always select the least privileged role necessary for the user to perform their duties.
• Consider regional privacy requirements when creating user and display names, as
user names will appear in event logs.
• Ensure user names are clearly unique to help ensure clear traceability. For
example, avoid creating both “User1” and “User 1”.
Failure to follow these instructions can result in unauthorized system access or
disclosure of private information.
User name
The minimum number of characters for the user name is 3 and no spaces are allowed.
Display name
The minimum number of characters for the display name is 3 and no leading, trailing or
consecutive spaces are allowed.
Role
Operator Display supports the management of users under three roles; Administrator,
Technician, and Viewer.
Password
The minimum number of characters and how many lowercase, numeric, and special
characters that are required when you create a password depends on how the Operator
Display user settings are configured.
For more information, see section 1.5 “Creating a User” on page 16.
Inactivity timeout
The default setting is that the user is logged out after 15 minutes of inactivity. You can
configure the timeout to be between 1 and 60 minutes.
!*#$%'()*+-/:;<=>?@[\]^_'{|}~
NOTE: Operator Display alerts you if the total number of lowercase, uppercase,
numeric, and special characters exceeds 128.
For more information, see section 1.8 “Configuring User Settings” on page 18.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
• Always select the least privileged role necessary for the user to perform their duties.
• Consider regional privacy requirements when creating user and display names, as
user names will appear in event logs.
• Ensure user names are clearly unique to help ensure clear traceability. For
example, avoid creating both “User1” and “User 1”.
Failure to follow these instructions can result in unauthorized system access or
disclosure of private information.
For more information, see section 1.4 “User Account Administration” on page 14.
To create a user
5. On the Create User screen, in the User name box, type a unique user name.
NOTE:
• Minimum number of characters: 3
• No spaces allowed
6. In the Display name box, type the name that will be displayed on the screen when
the user is logged on to Operator Display.
NOTE:
• Minimum number of characters: 3
• No leading, trailing or consecutive spaces allowed
7. In the Role box, select the user role to give the user the required permissions. For
more information, see section 1.4 “User Account Administration” on page 14.
8. Tap Next.
9. On the Create password for screen, in the Password box, type a unique
password.
10. In the Confirm password box, type the password a second time.
For more information, see section 1.3 “User Account Handling” on page 13.
To change a password
4. On the Change password screen, in the Current password box, type your
current password.
Continued on next page
6. In the Confirm password box, type your new password a second time.
7. Tap Save.
For more information, see section 1.4 “User Account Administration” on page 14.
To delete a user
5. On the user detail screen, tap the button to delete the user .
For more information, see section 1.4 “User Account Administration” on page 14.
4. On the User Configuration screen, tap + or - to edit the value of each user
setting.
5. Tap OK.
1.9 Configuration
As an administrator you need to configure Operator Display and make it part of the IP
network and the BACnet/IP network so you can discover and add the devices.
For more information, see section 1.10 “Hardening Specifics” on page 19.
For more information, see section 1.12 “Configuration Menus” on page 23.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Do not connect the device to a public network.
Failure to follow these instructions can result in unauthorized access to the
BACnet network.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Use the Erase all data command accessible from the About screen or perform the
Factory Reset procedure when decommissioning Operator Display.
Failure to follow these instructions can result in loss of data or equipment damage.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
• Regularly delete or downgrade the role of account users who no longer need
access to the device.
• Ensure users understand they should never share accounts or passwords.
If all administrator passwords are lost, the device must be factory reset to remove all
data and create new users.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Ensure the administrator password is stored securely.
Failure to follow these instructions can result in unauthorized access to the device,
or require recommissioning of the device.
Log files may contain sensitive information like usernames and IP addresses.
NOTICE
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Encrypt log files before transmission.
Failure to follow these instructions can result in disclosure of information that may
be sensitive or private.
NOTE: Alarm and schedule menus will still be displayed when Configuration
Menus are present.
Overview
You use configuration menus to customize values shown on Operator Display.
You create the configuration menu in Configuration Menu Editor to contain any source
values presented by Operator Display. The menu is deployed to the RP-C or MP-C
Controller and can then be accessed with Configuration Menu Viewer in Workstation, a
Commission mobile application or Operator Display.
There are no limitations on the size of menus, but it is recommended to not build
extensive menus to simplify its use for the devices.
For more information, see section 1.1 “ Operator Display Overview” on page 10.
IMPORTANT: For the first time, you can create more than one CAM object and
specify the target for that object as long as you are running the 3.3 EcoStruxure
BMS software. Existing CAM objects in 3.2 or earlier MP or RP controller firmware
are still recognized by the EcoStruxure BMS. However, if you are running
EcoStruxure Building Operation 3.3, do not attempt to set the Target device
property when using 3.2 or earlier MP or RP controller firmware. That firmware
does not recognize the Target device property.
EcoStruxure Building Operation provides you with an easy way to create a
backwards compatible CAM. To do so, select the Use backwards compatible
instance ID checkbox provided on the Create Object, Configuration Menu
wizard, BACnet basic settings page. EcoStruxure Building Operation - Technical
Reference Guide
For more information, see section 1.12 “Configuration Menus” on page 23.
2. Select Application.
3. In the File menu, point to New and then click Configuration Menu.
By doing so, you specify whether you wish to use the MBL, the OPD or both as the
client device (MBL-OPD) that the CAM object reads and uses.
7. Click OK.
Operator
TRUE Select the boolean value TRUE to have your
object (separator, submenu, or value) always
displayed in the Configuration Menu Viewer.
1.14.2 Example
For example, you want your menu value to represent the activation state of a fan (with
the bind name "fan_activ"). In the Value type box, select Digital to display the digital
sygnal for on/off. If you want your menu value to represent the speed of a fan
("fan_speed"), in the Value type box choose Analogue to display an analog signal for
speed. You can decide to display the menu value for the speed of the fan in the
Configuration Menu Viewer or in the Commission mobile application, only when the fan
is on. In this case you configure, in the Select Condition dialog box, the visibility
constraint for "fan_speed" to "fan_activ = TRUE".
4. On the Network Setup screen, tap Static IP to use a static IP address or DHCP to
use a DHCP server.
NOTE: When you select to use a DHCP server, the rest of the fields are
automatically completed by the DHCP server and not editable.
5. In the IP address box, type the static IP address for this Operator Display.
6. In the Subnet mask box, type the subnet mask for this Operator Display.
7. In the Gateway box, type the IP address of the gateway for this Operator Display.
8. Tap OK.
4. On the BACnet Setup screen, in the Instance number box, type the intance
number for this Operator Display.
5. In the Port box, type the communication port number for this Operator Display.
6. Tap Time master to configure Operator Display to send date and time to its
connected devices.
7. Tap OK.
To discover a device
1. In Operator Display, on the Device List screen, tap the discover button .
3. On the Search for device screen, in the search box, type the name of the device
you want to add to the list.
6. On the Filter screen, tap to select the box next to the models and vendors you
want to include in the filter.
7. Tap Apply.
Alarm time stamps are displayed in Operator Display with the local date and time in the
device reporting the alarm.
NOTE: If the device reporting an alarm is in a different time zone, Operator Display
does not make time zone adjustments.
All time stamps in logs and alarms are displayed with the date and time configured in
Operator Display. For more information, see section 1.19 “Configuring Date and Time”
on page 28.
NOTE: Operator Display does not make Daylight Saving Time (DST) adjustments
automatically.
On the BACnet Setup screen, an Operator Display time master is indicated by the Time
Operator Display receives date and time from the BACnet network via the Local Time
Synchronization service. The Local Time Synchronization service is configured in the
EcoStruxure Building Operation software.
For more information, see section 1.19 “Configuring Date and Time” on page 28.
For more information, see section 1.18 “Date and Time Handling” on page 27.
4. On the Date / Time screen, tap - or + to select the year, month, date, hour, and
minutes.
6. On the Select a region screen, tap the radio button next to your region.
7. Tap Next.
8. On the Select time zone screen, tap the radio button next to your time zone.
9. Tap OK.
10. On the Date / Time screen, the Universal Time Coordinated corresponding to your
selection is displayed.
NOTE: Operator Display does not make Daylight Saving Time (DST)
adjustments automatically.
For more information, see section 1.18 “Date and Time Handling” on page 27.
4. On the BACnet Setup screen, tap Time master to configure Operator Display to
send date and time to its connected devices.
5. Tap OK.
NOTICE
LOSS OF DATA
Ensure that the Operator Display power supply is not interrupted during the firmware
upgrade process.
Failure to follow these instructions can result in loss of data.
IMPORTANT: You need to configure the Operator Display date and time before
you update the firmware. The upgrade firmware feature cannot handle the date and
time factory setting. For more information, see section 1.19 “Configuring Date and
Time” on page 28.
4. Insert a USB key containing the firmware files into the Operator Display USB port.
7. Tap Update.
NOTICE
LOSS OF DATA
Recover Operator Display only if it is not accessible or when decommissioning
Operator Display.
Failure to follow these instructions can result in loss of data
2. On back of the Operator Display, in port USB-2, connect a USB On The Go cable
(OTG, USB-Micro-B to USB-A).
3. In port USB-1, connect a USB key containing the latest version of the Device
Recovery firmware file, unzipped.
NOTE: The USB OTG cable and key are not included in the purchased
Operator Display bundle.
Loading nand.img...
Writing KERNEL...
Writing ROOTFS...
NOTICE
LOSS OF DATA
• Export the logs you want to keep.
5. Tap Update.
5. Tap OK.
4. On the Display screen, drag the Active backlight slider to select the preferred
light level when you are using Operator Display.
Continued on next page
5. Drag the Inactive backlight slider to select the preferred light level when you are
not using Operator Display.
TIP: Drag the slider all the way to the left to make the backlight turn off when
your not using Operator Display.
6. Tap OK.
On the Alarms screen, active alarms and reset alarms that have not been
acknowledged are displayed. On the Alarm screen you also get information such as the
alarm state, the name of the input, output or value generating the alarm, and the alarm
message. For more information, see section 2.7 “Alarms Screen” on page 84.
1.27.1 Acknowledgement
When you acknowledge an active alarm, you let other users know that you have seen
and taken responsibility for the issue causing the alarm. Acknowledging an alarm does
not necessarily mean that you are personally solving the cause of the alarm. When you
acknowledge an an active alarm the color and icon of the alarm in the Alarms pane
changes. You also acknowledge reset alarms to remove them from the Alarms screen.
For more information, see section 1.28 “Acknowledging an Alarm” on page 35.
Icon Description
Alarm State
Indicates an active alarm in the state Alarm
that is not acknowledged.
Alarm
Fault
Acknowledged
Reset
The alarm messages can have been customized in the EcoStruxure Building Operation
software to display more detailed information on the alarm. If the alarm message is not
customized, the event state is displayed.
The table below describes the event states, event state texts, transition types, and
alarm messages that are displayed depending on in which alarm state the alarm is.
Fault
Acknowledged
Reset
(no alarm) (no alarm) (no alarm) (no alarm) (no alarm)
Normal
1.27.3 Indications
A red circle on the alarms icon in the toolbar indicates when there is at least one
active alarm that is not acknowledged.
Red, flashing (while running) There is at least one active alarm that is not
acknowledged.
Red, constant (while running) There is at least one active alarm but all
alarms are acknowledged.
For more information, see section 1.27 “Alarm Handling” on page 33.
To acknowledge an alarm
2. On the Alarms screen, tap the arrow button to select the active or reset alarm
that you want to acknowledge.
Many inputs, outputs and values receive their value from the system. For example, from
a program sequence or a time schedule in the device or server application, or from a
connected field device, such as a sensor.
When you edit the value it returns to the value received from the system. For example, if
you edit the value of a calculated setpoint it will return back to the calculated setpoint
value.
You normally do not have to force values. The system is configured so that values
intended to be edited, such as non-calculated setpoints, control mode selectors, and
digital override switches, are editable without having to be forced.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
As an administrator, you can change the BACnet command priority level for forced
values. Be careful when selecting the priority level. If higher priorities are used, it may
interfere with higher-priority equipment, such as manual life safety, automatic life safety,
or critical equipment control.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not configure the BACnet command priority level for forced values without knowing
how the priority level may interfere with higher-priority equipment.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
For more information, see section 1.31 “Configuring the BACnet Command Priority
Level for Forced Values” on page 39.
1.29.3 Indications
On the inputs, output and value detail screens, a forced value is indicated by the Force
toggle being dark gray . On the input, output and value screens, a forced value
is indicated by an yellow circle and the text Forced .
To resolve this problem, a BACnet command priority handles any potential conflicts by
prioritizing the write requests in a descending order from 1 (highest) to 16 (lowest). In
this way, the system resolves whether a BACnet write request takes effect immediately
or is stored in the command priority. Essentially, a command priority manages the
actions of multiple operators or applications that use the Value property.
Priority 3
Priority 10
= Off = On = Off
In a 16-level BACnet priority array, there are different types of levels: available,
suggested, and reserved. You can configure these levels according to your specific site
requirements.
Continued
Priority Level Description
5 Critical equipment control. This is a suggested priority level based on
the BACnet Standard.
Relinquish default
Relinquish default is the value that the system uses for the value if all commandable
priority values in the priority array are NULL. For example, you can consider this value
as the lowest priority in the system. Relinquishing a priority is the same as writing NULL
at that priority.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not configure the BACnet command priority level for forced values without knowing
how the priority level may interfere with higher-priority equipment.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
For more information, see section 1.30 “BACnet Command Priorities” on page 36.
4. On the BACnet Setup screen, in the Force Priority Level box, tap + or - to
configure the priority level at which the force command will be applied.
5. Tap OK.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
For more information, see section 1.29 “Value Editing” on page 35.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the with the analog input, output, or value you want to edit.
2. On the Device screen, tap the Inputs, Outputs, or Values arrow button .
3. On the Inputs, Outputs, or Values screen, tap the Analog arrow button .
5. On the inputs, outputs, or values detail screen, tap + or - to edit the value of the
analog input, output, or value.
6. Tap OK.
For more information, see section 1.29 “Value Editing” on page 35.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the with the binary input, output, or value you want to edit.
2. On the Device screen, tap the Inputs, Outputs, or Values arrow button .
3. On the Inputs, Outputs, or Values screen, tap the Binary arrow button .
Continued on next page
5. On the inputs, outputs, or values detail screen, tap + or - to edit the value of the
binary input, output, or value.
6. Tap OK.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
For more information, see section 1.29 “Value Editing” on page 35.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the with the multi-state input, output, or value you want to edit.
2. On the Device screen, tap the Inputs, Outputs, or Values arrow button .
3. On the Inputs, Outputs, or Values screen, tap the Multi-State arrow button .
6. Tap OK.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
For more information, see section 1.29 “Value Editing” on page 35.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the with the analog input, output, or value you want to edit.
2. On the Device screen, tap the Inputs, Outputs, or Values arrow button .
3. On the Inputs, Outputs, or Values screen, tap the Analog arrow button .
5. On the inputs, outputs, or values detail screen, tap + or - to edit the value of the
analog input, output, or value.
7. Tap OK.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
For more information, see section 1.29 “Value Editing” on page 35.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the with the binary input, output, or value you want to edit.
2. On the Device screen, tap the Inputs, Outputs, or Values arrow button .
Continued on next page
3. On the Inputs, Outputs, or Values screen, tap the Binary arrow button .
5. On the inputs, outputs, or values detail screen, tap + or - to edit the value of the
binary input, output, or value.
7. Tap OK.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
For more information, see section 1.29 “Value Editing” on page 35.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the with the multi-state input, output, or value you want to edit.
2. On the Device screen, tap the Inputs, Outputs, or Values arrow button .
3. On the Inputs, Outputs, or Values screen, tap the Multi-State arrow button .
5. On the inputs, outputs, or values detail screen, tap Force to override the value
received from the system.
7. Tap OK.
For example, the lighting in an office building needs to be automated to conserve energy
during non-business hours. To regulate the lights from Monday through Friday, you use a
weekly event in a schedule that turns the lights on at 07:00 and switches them off at 20:00.
If there are any non-routine events, such as holidays, you can use exception events to
override the weekly event and turn the lights off.
1.38.1 Schedule Types
You can have three types of different schedules in the building management system:
Analog, Digital, Multi-State or Enumerated. An analog schedule is used if the schedule
controls a device that gauges the output in real numbers. A digital schedule is used if
the schedule needs to control a device with two output states, such as On or Off. A
multi-state/enumerated schedule is used if the schedule needs to control a device that
has output states based on multiple states, such as low, medium, or high.
For more information, see section 1.39 “Schedule Types ” on page 44.
For more information, see section 1.43 “Schedule Events” on page 47.
For more information, see section 1.30 “BACnet Command Priorities” on page 36.
For more information, see section 1.40 “Analog Schedules” on page 45.
For more information, see section 1.41 “Digital Schedules” on page 45.
For example, a digital weekly schedule is bound to a digital output, such as a light
switch. It turns on the lights Monday through Friday from 08:00 to 17:00, when the
schedule is active and off when the schedule is inactive.
= Off = On = Off
For example, a multi-state weekly schedule is bound to a multi-state value that controls
an air handling unit in an office building. It regulates the air circulation Monday through
Friday from 08:00 to 17:00, to 2 (occupied) when the schedule is active and 1
(unoccupied) when the schedule is inactive.
Each schedule has a default value. The default value goes into effect after the
exception events and weekly events are complete or relinquish control. For more
information, see section 1.45 “Viewing a Schedule Default Value” on page 49.
For example, the weekly event for a fan ends at 17:00. The fan ran at a value of 3 (high)
throughout the event. There are no scheduled events after the weekly event. Because
you have assigned 0 as the default value, the fan adjusts to the default value and turns
to 0 (off). The value remains at 0 until the next scheduled event.
For example, the weekly event for a fan is set to On from '08:00 - 20:00'. An exception
event is set to Off from '17:00 - 20:00' for a specifc date. The exception event overrides
the weekly event so that the fan only runs from 08:00 to 17:00 on the specified date.
For more information, see section 1.44 “Weekly Events” on page 48.
For more information, see section 1.48 “Exception Events” on page 50.
For more information, see section 1.59 “Schedule Colors” on page 62.
NOTE: While weekly events cannot overlap, exception events can. For more
information, see section 1.48 “Exception Events” on page 50.
If there are any non-routine events, such as holidays, you can use exception events to
override the weekly events in the schedule. For more information, see section 1.48
“Exception Events” on page 50.
For more information, see section 1.30 “BACnet Command Priorities” on page 36.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule for which you want to view the default value.
3. On the Schedules screen, tap the schedule for which you want to view the default
value.
4. On the schedule view screen, tap the information button to open the
schedule detail screen of the schedule for which you want to view the default
value.
5. On the schedule detail screen, in the Default value box, view the schedule default
value.
For more information, see section 1.44 “Weekly Events” on page 48.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule to which you want to add a weekly event.
3. On the Schedules screen, tap the schedule to which you want to add a weekly
event.
8. In the Days of week box, tap the day(s) of the week this event is active.
9. Tap OK.
For more information, see section 1.44 “Weekly Events” on page 48.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule for which you want to edit a weekly event.
3. On the Schedules screen, tap the schedule for which you want to edit a weekly
event.
4. On the schedule view screen, tap the weekly event (green) that you want to edit.
7. In the Days of week box, tap the day of the week this event is active.
8. Tap OK.
For example, you create an exception event in March for an intense aerobics class in
the gym to open an air vent to 100 % from 06:30 to 17:00 every Wednesday in March.
This exception event takes precedence over the regularly scheduled weekly
Wednesday events.
When scheduling exception events, you can use three exception types to provide
flexibility and control in your schedule.
For example, to schedule a single date event to take place every year on October 31,
you select the following single date options:
• Year: Any year
• Month: October
• Day of month: 31
• Day of week: Any day
For more information, see section 1.49 “Adding a Single Date Exception Event ” on
page 52.
For example, to schedule an exception event to occur from the first day of July to the
last day of August where the priority is 16, but each day from 08:00 to 17:00 the value is
15.50, select:
• Priority: 16
• Start date: 2021-07-01
• End date: 2021-08-31
• Start time: 08:00
• End time: 17:00
• Value: 15.50
For more information, see section 1.50 “Adding a Date Range Exception Event ” on
page 53.
For example, to schedule the Monday of the first week of every month for an exception
event, select the following options:
• Month: Any month
• Week of month: First week
• Day of week: Monday
For more information, see section 1.51 “Adding a Calculated Date Exception Event” on
page 54.
For more information, see section 1.52 “Adding a Calendar Exception Event ” on page
55.
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule to which you want to add a single date exception
event.
3. On the Schedules screen, tap the schedule to which you want to add a single date
exception event.
6. On the Add single date exception screen, in the Priority box, tap + or - to edit
the priority of the event.
7. In the Year box, tap + or - to select a specific year between 2020 and 2100, or Any
year.
8. In the Month box, tap + or - to select a specific month between January and
December, Odd months, Even months, or Any month.
9. In the Day of month box, tap + or - to select a specific day between 1 and 31,
Last day, Odd days, Even days, or Any day.
10. In the Day of week box, tap + or - to select a specific day between Mon and Sun,
or Any day.
11. On the start/end time and value list header, tap the add time span and value button
.
12. On the Edit exception event screen, select the event value:
• For analog, multi-state and enumerated schedules: In the Value box, tap + or
- to specify the value of the event.
• For digital schedules: Tap Inactive or Active (Off or On).
TIP: You can add multiple time spans and values to an exception event.
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule to which you want to add a date range exception
event.
3. On the Schedules screen, tap the schedule to which you want to add a date range
exception event.
Continued on next page
6. On the Add date range exception screen, in the Priority box, tap + or - to edit
the priority of the event.
7. In the Start date box, tap the calendar button to select a specific start date
or Now to select the current date.
8. In the End date box, tap the calendar button to select a specific end date or
Never to indicate the exception does not have an end date.
9. On the start/end time and value list header, tap the add time span and value button
.
10. On the Edit exception event screen, select the event value:
• For analog, multi-state and enumerated schedules: In the Value box, tap + or
- to specify the value of the event.
• For digital schedules: Tap Inactive or Active (Off or On).
TIP: You can add multiple time spans and values to an exception event.
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule to which you want to add a calculated date exception
event.
Continued on next page
3. On the Schedules screen, tap the schedule to which you want to add a calculated
date exception event.
6. On the Add calculated date exception screen, in the Priority box, tap + or - to
edit the priority of the event.
7. In the Year box, tap + or - to select a specific year between 2020 and 2100, or Any
year.
8. In the Month box, tap + or - to select a specific month between January and
December, Odd months, Even months, or Any month.
9. In the Week of month box, tap + or - to select a specific week between First and
Fifth, Last, or Any.
10. In the Day of week box, tap + or - to select a specific day between Mon and Sun,
or Any day.
11. On the start/end time and value list header, tap the add time span and value button
.
12. On the Edit exception event screen, select the event value:
• For analog, multi-state and enumerated schedules: In the Value box, tap + or
- to specify the value of the event.
• For digital schedules: Tap Inactive or Active (Off or On).
TIP: You can add multiple time spans and values to an exception event.
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule to which you want to add a date range exception
event.
3. On the Schedules screen, tap the schedule to which you want to add a date range
exception event.
NOTE: If the Calendar exception button is gray instead of blue, and you see
No calendars found next to it, this option is unavaible for the moment on this
device because at least 1 configured calendar is required.
6. On the Add calendar exception screen, in the Priority box, tap + or - to edit the
priority of the event.
8. On the Select calendar screen, tap the radio button next the calendar you want to
edit.
9. Tap OK.
10. On the start/end time and value list header, tap the add time span and value button
.
11. On the Edit exception event screen, select the event value:
• For analog, multi-state and enumerated schedules: In the Value box, tap + or
- to specify the value of the event.
• For digital schedules: Tap Inactive or Active (Off or On).
TIP: You can add multiple time spans and values to an exception event.
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule for which you want to edit a single date exception
event.
3. On the Schedules screen, tap the schedule for which you want to edit a single
date exception event.
4. On the schedule view screen, tap the exception event (blue) that you want to edit.
5. On the Edit single date exception screen, in the Priority box, tap + or - to edit
the priority of the event.
6. In the Year box, tap + or - to select a specific year between 2020 and 2100, or Any
year.
7. In the Month box, tap + or - to select a specific month between January and
December, Odd months, Even months, or Any month.
8. In the Day of month box, tap + or - to select a specific day between 1 and 31,
Last day, Odd days, Even days, or Any day.
9. In the Day of week box, tap + or - to select a specific day between Mon and Sun,
or Any day.
10. Select to add another start/end time and value or edit existing ones:
• In the start/end time and value list, tap the edit exception button on the
row with the start/end time or value that you want to edit.
• On the start/end time and value list header, tap the add time span and value
button .
11. On the Edit exception event screen, select the event value:
• For analog, multi-state and enumerated schedules: In the Value box, tap + or
- to specify the value of the event.
• For digital schedules: Tap Inactive or Active (Off or On).
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule for which you want to edit a date range exception
event.
3. On the Schedules screen, tap the schedule for which you want to edit a date
range exception event.
4. On the schedule view screen, tap the exception event (blue) that you want to edit.
5. On the Edit date range exception screen, in the Priority box, tap + or - to edit the
priority of the event.
6. In the Start date box, tap the calendar to select a specific start date or Now to
select the current date.
7. In the End date box, tap the calendar to select a specific end date or Never to
indicate the exception does not have an end date.
8. Select to add another start/end time and value or edit existing ones:
• In the start/end time and value list, tap the edit exception button on the
row with the start/end time or value that you want to edit.
• On the start/end time and value list header, tap the add time span and value
button .
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule for which you want to edit a calculated date exception
event.
3. On the Schedules screen, tap the schedule for which you want to edit a calculated
date exception event.
4. On the schedule view screen, tap the exception event (blue) that you want to edit.
5. On the Edit calculated date exception screen, in the Priority box, tap + or - to
edit the priority of the event.
6. In the Year box, tap + or - to select a specific year between 2020 and 2100, or Any
year.
7. In the Month box, tap + or - to select a specific month between January and
December, Odd months, Even months, or Any month.
8. In the Week of month box, tap + or - to select a specific week between First and
Fifth, Last, or Any.
9. In the Day of week box, tap + or - to select a specific day between Mon and Sun,
or Any day.
10. Select to add another start/end time and value or edit existing ones:
• In the start/end time and value list, tap the edit exception button on the
row with the start/end time or value that you want to edit.
• On the start/end time and value list header, tap the add time span and value
button .
11. On the Edit exception event screen, select the event value:
• For analog, multi-state and enumerated schedules: In the Value box, tap + or
- to specify the value of the event.
• For digital schedules: Tap Inactive or Active (Off or On).
For more information, see section 1.48 “Exception Events” on page 50.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule for which you want to edit a date range exception
event.
3. On the Schedules screen, tap the schedule for which you want to edit a date
range exception event.
4. On the schedule view screen, tap the exception event (blue) that you want to edit.
5. On the Edit calendar exception screen, in the Priority box, tap + or - to edit the
priority of the event.
7. On the Select calendar screen, tap the radio button next the calendar you want to
edit.
8. Tap OK.
9. Select to add another start/end time and value or edit existing ones:
• In the start/end time and value list, tap the edit exception button on the
row with the start/end time or value that you want to edit.
• On the start/end time and value list header, tap the add time span and value
button .
10. On the Edit exception event screen, select the event value:
• For analog, multi-state and enumerated schedules: In the Value box, tap + or
- to specify the value of the event.
• For digital schedules: Tap Inactive or Active (Off or On).
An exception event occurs instead of the scheduled weekly events for a single date,
date range, calculated date, or calendar.
Exception events always take precedence over weekly events. When two exception
events overlap, priorities can determine which event takes precedence over the other.
Generally, priorities resolve the following conflicts:
• Two events with different priorities occur on the same day and time. In this case,
the higher priority takes control of the schedule.
For example, a schedule that is set at priority 14 controls a fan in an office area at
low speed during normal business hours. A Special Meeting event scheduled at
11:00 is set at priority 12 for medium speed. Therefore, the schedule adjusts the
fan from low to medium for the meeting and ignores the priority 14 event until the
priority 12 event ends.
• Two events with the same priority level occur on the same day and time. In this
case, the position in the Event tree determines which priority takes control of the
schedule. The position depends on when exception event was created.
For example, two exception events are set at priority 12. Winter Break was created
first followed by Scout Meeting. Therefore, Winter Break takes precedence over
Scout meeting because that event was created first.
By default, all exception events are set at priority 16, but you can change priority level.
For more information, see section 1.58 “Editing an Event Priority” on page 62.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the with the schedule event priority you want to edit.
4. On the schedule view screen, tap the event you want to edit.
5. On the event screen, tap + or - to edit the priority of the event. 1 is the highest
priority and 16 is the lowest.
6. Tap OK.
For more information, see section 1.43 “Schedule Events” on page 47.
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the schedule for which you want to delete an event.
4. On the schedule view screen, tap a weekly (green) or exception (blue) event.
5. On the Edit weekly event or Edit exception event screen, tap the delete button
6. Tap OK .
3. Insert your USB key in the USB port of the Operator Display.
Variable
Calculation Calculation
Σ Δ E[x] Σ Δ E[x]
12:04:00 10 12:04:00 10
12:03:00 5 12:03:00 5
12:02:00 4 12:02:00 4
12:01:00 2 12:01:00 2
NOTE: During the logging process, activity in the server may be temporarily
increased. This is because a second polling rate is applied to each variable 30
seconds before the logging time. With multiple logs, the increase in activity can be
significant. After 30 seconds, when a value is logged, the polling rate is set to the
maximum integer.
All trend log types can be configured to log meter consumption and handle meter
replacement. Extended trend logs can be used to structure the log data and to store it
where there is greater storage capacity.
Meter Function
The meter function adds meter properties to any trend log type to seamlessly handle
consumption calculations independent of meter rollover or meter exchange.
Variable
Trend Log
ºF
Timestamp Value
ºC
Figure – In this setup the variable has the temperature unit Kelvin, recorded trend log
values are stored in Fahrenheit, and are displayed in Celsius.
The trend log list can only display one trend log at a time and must be manually
refreshed to display recently recorded values.
Trend
2
4
10
Calculation
Σ Δ E[x]
Time- Valu
12:04:00 10
12:03:00 5
12:02:00 4
12:01:00 2
1. In Operator Display, on the Device List screen, tap the arrow button to select
the device with the trend log you want to view.
3. On the Trend Logs screen, tap the log for which you want to view the activity.
4. On the trend logs view screen, tap the refresh button to make sure the
information on the screen is up to date.
5. Tap the date selector button to pick start and dates and refine the
information displayed on the screen.
6. Tap the information button to open the trend logs information screen and
view its properties.
2 User Interface
What's in This Chapter?
2.1 Home Screen ....................................................................................................... 76
2.2 Login Screen ........................................................................................................ 77
2.3 Toolbar ................................................................................................................. 78
2.4 Menu .................................................................................................................... 80
2.5 User Profile Screen .............................................................................................. 82
2.6 Change Password Screen .................................................................................... 83
2.7 Alarms Screen ...................................................................................................... 84
2.8 Alarm Detail Screen ............................................................................................. 86
2.9 Device Discovery Screen ..................................................................................... 88
2.10 Device Discovery Detail Screen ......................................................................... 89
2.11 Device List Screen ............................................................................................. 90
2.12 Device Detail Screen (without Configuration Menus) ......................................... 91
2.13 Device Detail Screen (with Configuration Menus) .............................................. 93
2.14 Device Alarms Screen ........................................................................................ 95
2.15 Inputs Screen ..................................................................................................... 97
2.16 Inputs/Analog Screen ......................................................................................... 98
2.17 Inputs/Analog Detail Screen ............................................................................... 99
2.18 Inputs/Binary Screen ........................................................................................ 100
2.19 Inputs/Binary Detail Screen .............................................................................. 101
2.20 Inputs/Multi-State Screen ................................................................................. 102
2.21 Inputs/Multi-State Detail Screen ....................................................................... 103
2.22 Outputs Screen ................................................................................................ 104
2.23 Outputs/Analog Screen .................................................................................... 105
2.24 Outputs/Analog Detail Screen .......................................................................... 106
2.25 Outputs/Binary Screen ..................................................................................... 107
2.26 Outputs/Binary Detail Screen ........................................................................... 108
2.27 Outputs/Multi-State Screen .............................................................................. 109
2.28 Outputs/Multi-State Detail Screen .................................................................... 110
2.29 Values Screen .................................................................................................. 111
2.30 Values/Analog Screen ...................................................................................... 112
2.31 Values/Analog Detail Screen ............................................................................ 113
2.32 Values/Binary Screen ....................................................................................... 114
2.33 Values/Binary Detail Screen ............................................................................. 115
2.34 Values/Multi-State Screen ................................................................................ 116
2.35 Values/Multi-State Detail Screen ...................................................................... 117
2.36 Schedules Screen ............................................................................................ 118
2.3 Toolbar
Use the toolbar to access the features available for the screen that is currently being
displayed.
Table – Toolbar
Button Description
Tap to open the menu, where you access the
different features of Operator Display. For
more information, see section 2.4 “Menu” on
page 80.
Continued
Button Description
Tap to filter the list of discovered devices on
the network and add them to the device list.
For more information, see section 2.9 “Device
Discovery Screen” on page 88.
This task requires administrator permissions.
2.4 Menu
Use the menu to access the different features of Operator Display.
Figure – Menu
Table – Menu
Component Description
(user name) Tap to open the user profile screen, where
you view user settings and change your
password. For more information, see section
2.5 “ User Profile Screen” on page 82.
Continued
Component Description
Log out Tap to log out of Operator Display.
Last successful login Displays the date and time of the last user
login.
Change Password Tap to change the password for this user. For
more information, see section 2.6 “Change
Password Screen” on page 83.
Continued
Component Description
Indicates an active alarm that is
acknowledged. For more information, see
section 1.27 “Alarm Handling” on page 33.
Continued
Component Description
Indicates an active alarm in the state Alarm
that is not acknowledged. For more
information, see section 1.27 “Alarm
Handling” on page 33.
NOTE: The device detail screen is also available with configuration menus. For
more information, see section 2.13 “Device Detail Screen (with Configuration
Menus)” on page 93.
Continued
Component Description
Values Tap to open the Values screen, where you
view and edit the analog, binary, and multi-
state values. This option is only visible if
values are configured on this device. For
more information, see section 2.29 “Values
Screen” on page 111.
NOTE: The device detail screen is also available without configuration menus. For
more information, see section 2.12 “Device Detail Screen (without Configuration
Menus)” on page 91.
Continued
Component Description
Trend Logs Tap to open the Trend Logs screen, where
you view event logs specific to this device.
This option is only visible if trend logs are
configured on this device. For more
information, see section 2.53 “Trend Logs
Screen” on page 144.
Continued
Component Description
Indicates a reset alarm that is not
acknowledged. For more information, see
section 1.27 “Alarm Handling” on page 33.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
WARNING
UNEXPECTED EQUIPMENT OPERATION
Do not force values without knowing the effect.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
Continued
Component Description
(Blue single date event) Tap to open the Edit single date exception
screen, where you edit the exception event.
For more information, see section 2.48 “Edit
Single Date Exception Screen” on page 136.
(Blue date range event) Tap to open the Edit date range exception
screen, where you edit the exception event.
For more information, see section 2.49 “Edit
Date Range Exception Screen” on page 138.
(Blue calculated date event) Tap to open the Edit calculated exception
screen, where you edit the exception event.
For more information, see section 2.50 “Edit
Calculated Date Exception Screen” on page
140.
Continued
Component Description
(Green event) Tap to open the Edit weekly event screen,
where you edit the weekly event. For more
information, see section 2.43 “Edit Weekly
Event Screen” on page 128.
(Blue single date event) Tap to open the Edit single date exception
screen, where you edit the exception event.
For more information, see section 2.52 “Edit
Exception Event Screen” on page 143.
(Blue date range event) Tap to open the Edit date range exception
screen, where you edit the exception event.
For more information, see section 2.49 “Edit
Date Range Exception Screen” on page 138.
(Blue calculated date event) Tap to open the Edit calculated date
exception screen, where you edit the
exception event. For more information, see
section 2.50 “Edit Calculated Date Exception
Screen” on page 140.
Single date exception Tap to open the Add single date exception
event screen, where you add a new event on
a specific day. For more information, see
section 2.44 “Add Single Date Exception
Screen” on page 129.
Date range exception Tap to open the Add date range exception
event screen, where you add a new event on
a specific series of dates. For more
information, see section 2.45 “Add Date
Range Exception Screen” on page 131.
Continued
Component Description
Calendar exception Tap to open the Add calendar exception event
screen, where you add a new monthly event.
For more information, see section 2.47 “Add
Calendar Exception Screen” on page 135.
If the Calendar exception button is gray
instead of blue, and you see No calendars
found next to it, this option is unavaible for the
moment on this device because at least 1
configured calendar is required.
All day Tap All day to make the event span 24 hours
instead of selecting specific hours using From
and To.
Days of week Tap to select the day(s) of the week this event
is active.
All day Tap All day to make the event span 24 hours
instead of selecting specific hours using From
and To.
Days of week Tap to select the day(s) of the week this event
is active.
Continued
Component Description
Tap to open the Edit exception event screen,
where you add a time span and a value. For
more information, see section 2.52 “Edit
Exception Event Screen” on page 143.
Continued
Component Description
Tap to open the Edit exception event screen,
where you edit the time span and the value.
For more information, see section 2.52 “Edit
Exception Event Screen” on page 143.
Continued
Component Description
Tap to open the Edit exception event screen,
where you add a time span and a value. For
more information, see section 2.52 “Edit
Exception Event Screen” on page 143.
Continued
Component Description
Tap to open the Edit exception event screen,
where you add a time span and a value. For
more information, see section 2.52 “Edit
Exception Event Screen” on page 143.
Continued
Component Description
Tap to open the Edit exception event screen,
where you edit the time span and the value.
For more information, see section 2.52 “Edit
Exception Event Screen” on page 143.
Continued
Component Description
Tap to open the Edit exception event screen,
where you add a time span and a value. For
more information, see section 2.52 “Edit
Exception Event Screen” on page 143.
All day Tap All day to make the event span 24 hours
instead of selecting specific hours using From
and To.
Continued
Component Description
Record Count Displays the number of records currently
residing in the log buffer.
Log Device Object Units Displays the measuring unit of the property to
be trend logged.
Continued
Component Description
BACnet Tap to open the BACnet Setup screen where
you configure the BACnet/IP network
communication. For more information, see
section 2.65 “BACnet Setup Screen” on page
158.
Time zone Tap the pencil button to select the time zone.
For more information, see section 1.18 “Date
and Time Handling” on page 27.
This task requires administrator permissions.
Continued
Component Description
Time master Tap to determine if Operator Display sets the
time for all its connected devices.
This task requires administrator permissions.
Re-scan for files Tap to start scanning the USB key for valid
firmware files.
Last Login Displays the date and time of the last user
login.
ETH1 MAC address Displays the MAC address for the Ethernet
interface.
Erase all data Tap to erase the device list, logs, and users
from the Operator Display. The only data
remaining will be the firmware version and
time setting.
This task requires administrator permissions.
3 Troubleshooting
What's in This Chapter?
3.1 Need Help with your Password .......................................................................... 167
3.2 All the Administrator Passwords Have Been Lost .............................................. 167
3.3 Network Unavailable .......................................................................................... 167
3.4 The Operator Display Is Not Starting .................................................................. 168
3.5 Firmware Upgrade Failure .................................................................................. 168
3.1.1 Solutions
Contact your Systems Administrator. They will be able to reset your password and give
you access to Operator Display.
3.2.1 Solutions
Recover Operator Display to remove all data and create new users. This operation
clears the device list, logs, and users. For more information, see section 1.22
“Recovering Operator Display (Factory Reset)” on page 30.
NOTICE
LOSS OF DATA
Export the logs you want to keep.
Failure to follow these instructions can result in loss of data.
3.3.1 Solution
Ensure that the Ethernet cable is properly connected to the ETH1 port of Operator
Display.
If Operator Display is on network but still having trouble interacting with devices:
• Check the Network configuration:
○ If Static make sure the IP, netmask and gateway are correctly configured.
○ The IP are not hidden by other device netmasks.
○ Netmasks are used to help ensure a device only sees network traffic from
specific IP ranges.
○ If going through a gateway. make sure it is the right one.
• Check the BACnet configuration:
○ It is using the correct port.
○ Is has a unique ID within the BACnet network.
3.4.1 Solution
Ensure that the proper firmware is installed on the Operator Display by reinstalling the
latest firmware version by performing a device recover. For more information, see
section 1.22 “Recovering Operator Display (Factory Reset)” on page 30.
NOTICE
LOSS OF DATA
Recover Operator Display only if it is not accessible or when decommissioning
Operator Display.
Failure to follow these instructions can result in loss of data
NOTICE
LOSS OF DATA
Ensure that the Operator Display power supply is not interrupted during the firmware
upgrade process.
Failure to follow these instructions can result in loss of data.
3.5.1 Solutions
The solutions are listed in order: the solution most likely to fix the problem is listed first.
Work through each solution until the problem is resolved.
• Ensure that the USB key is properly formatted.
• Copy the latest version of the firmware file to the USB key.
• Upgrade the firmware once more. For more information, see section 1.21
“Upgrading the Firmware” on page 29.
04-33049-04-en
April 2023