Facility Explorer ® - Basics Virtual Training

14720
Agenda

Day 1

Facility Explorer Overview Schedule Manager

JCI Appliance Workflow Link Manager

Workbench Overview Custom Control

Station Creation Defining Users

Defining JCI Controllers and Points Graphics

Point Extensions & Point Extension Using Standard Graphics for Non-Standard
Manager Applications

Duplicating Controllers and Points Commissioning the FX Supervisory

Controller
 Day 1
Facility Explorer®

C
op
yrig
ht
20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
C
op
y
Facility Explorer® Overview

rig
ht
20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 Facility Explorer® Overview

Objectives

Welcome to the Facility Explorer® Overview lesson.

c
In
At the end of this lesson, you will be able to:

,
ls
ro
Describe FX series supervisory controllers

t
on
Explain capabilities of supervisory controllers

C
n
so
Describe FX Server and FX Workbench

hn
Describe License options necessary

Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX Series Supervisory Products

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

Facility Explorer® Supervisory Overview

There are several supervisory controllers in the Facility Explorer ® product

c
In
family:

,
ls
ro
Current Model: FX80

t
on
Previously Release Models upgradeable to FX Release 14: FX60, FX60E, FX70

C
n
Previous Release Models recommended to remain at FX Release 6.x or previous

so
release FX30, FX30E

hn
Jo
Previously released models to remain at FX Release 6.x or previous release: FX20,

by
FX40 19
These supervisory controllers have:
20
ht

Similar set of supervisory control capabilities

rig

Different hardware configurations/capacities

y
op
C
Day 1 Facility Explorer® Overview

Facility Explorer® Supervisory Overview (Cont’d.)

FX Server:

c
In
Integrates multiple supervisors and other Ethernet-based devices

,
ls
ro
Centralizes user interface, scheduling, and storage of alarms

t
on
Resides in 3rd party PC platform of your choice

C
n
FX Workbench Pro:

so
hn
Configuration tools suite

Jo
by
19
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities

The supervisory controllers provide integrated control, supervision, and network

c
In
management services to one or more local networks of field controllers.

,
ls
ro
Multiple field controller networking protocols are supported by:

t
on
BACnet® (MS/TP and IP)

C
n
N2

so
hn
LonWorks®

Jo
ModBus® (RTU, TCP, etc.)
by
19
FlexSerial®
20

Carrier® CCN (open)

ht
rig

McQuay® OPM®
y
op

Etc. (Refer to product bulletin for complete listing)

C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Data sourced from these devices and protocol types are transformed into

c
In
a common point model (Niagara points.)

,
ls
ro
Following are various data types:

t
on
Numeric: Represents analog data

C
n
Boolean: Represents 2-state data

so
hn
Enumerated: Represents multi-state data

Jo
String: Represents textual data
by
19
20
ht
rig

Key Benefit
y
op
C

The ability to apply the same set of features to these points consistently regardless
of their source.
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

It Supervisory Controller provides system-wide automation and coordination via:

c
In
,
ls
ro
Scheduling Linking

t
on
C
n
so
hn
Jo
Alarming Control logic

by
19
20
ht

Histories Totalization
rig
y
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Scheduling

c
In
Schedules can be used to control any data point

,
ls
ro
that could be modified such as:

t
on
Occupancy

C
n
Start/stop time for

so
mechanical equipment

hn
Jo
Setpoint
Access
by
19
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Types of scheduling:

c
In
Weekly

,
ls
ro
Calendar (exception/holiday)

t
on
Trigger

C
n
It is an intuitive, graphical

so
hn
scheduling interface

Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Alarming

c
In
Alarm extensions can be added to any data point

,
ls
ro
Alarms are generated based on user-defined

t
on
criteria

C
n
Following are the available options:

so
hn
Alarm Console:

Jo
by
Acknowledge 19
Hyperlink
20

Annotate
ht
rig

Silence
y

Filter
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Email

c
In
FX Server

,
ls
ro
Printers

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Histories

c
In
It displays time-stamped records of data points over a period of time

,
ls
ro
History extensions can be added to any data point based on:

t
on
C
Periodic interval

n
so
Change of value/state

hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Following are the viewing options:

c
In
Table

,
ls
ro
Chart

t
on
Multiple histories can be charted simultaneously

C
n
You can use pan or zoom in/out features to view these charts

so
hn
Export to .csv, .txt, and/or

Jo
.pdf format

by
19
20
ht
y rig
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Linking

c
In
It implies sharing data across devices and networks

,
ls
ro
Priority array: 16 levels

t
on
Control logic:

C
n
so
Boolean logic (AND, OR, NOT, etc.)

hn
Comparative (<, ≤, >, ≥, =, ≠, etc.)

Jo
by
Mathematical (+, -, x, ÷) 19
Sequencers
20

PID control
ht
rig

On/off control
y
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Totalization

c
In
Totalization extensions can be added to any data point such as:

,
ls
ro
Runtime

t
on
Change of State (COS) counts

C
n
so
Summary of dynamic analog data (for utilities, consumption, etc.)

hn
Viewing options:

Jo
by
Table 19
Export to .csv, .txt, and/or .pdf
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

System User Interface

c
In
It is served up by Supervisory Controller to the web browser

,
ls
ro
Following are the presentation options based on user profile:

t
on
C
Px

n
so
Java applet is downloaded during login

hn
Full-featured graphics and animations can be presented

Jo
by
19
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

Hx

c
In
Java applet is not required

,
ls
ro
It has limited features

t
on
HTML, JavaScript, and CSS

C
It is applicable for handheld PDAs or PCs where java applet is not an option

n
so
Access and command privileges are restricted based on user profiles

hn
Jo
by
19
20
ht
y rig
op
C
Day 1 Facility Explorer® Overview

Hx Example Interface

Java applet is not required

c
In
It has limited features

,
ls
ro
HTML, JavaScript, and CSS

t
on
It is applicable for handheld PDAs or PCs where

C
java applet is not an option

n
so
hn
Jo
by
19
20
ht
y rig
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Models

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX80 Supervisory Controller

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX Supervisory Hardware Information

Licensing based on Field Devices/Points (50 points/device)

c
In
Ordering needs to include:

,
ls
ro
FX Base (includes micro SD with licensing purchased separately

t
on
Core Device License (5, 10, 25, 100, 200 devices)

C
n
so
Software Maintenance (1, 3, 5 years)

hn
Additional devices can be ordered as needed (capacity added to base)

Jo
by
Initial Purchase (10, 25, 50 devices)
19
After Initial Purchase (10, 25, 50 devices)
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

Supervisory Controller Capabilities (Cont’d.)

FX 80 is available also with:

c
In
WLAN disabled

,
ls
ro
No micro SD and licensing (Replacement for service)

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C

For Hardware information please see the FX80 Supervisory Controller catalog page.
Day 1 Facility Explorer® Overview

FX30E and FX60E Supervisory Controller (Legacy)

c
,In
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX70 Supervisory Controller (Legacy)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX20 and FX60 Supervisory Controller (Legacy)

c
In,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX22/62 Supervisory Controller (Legacy)

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX40 Supervisory Controller (Legacy)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX Server

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

FX Server Overview

The FX Server is a software package that can be loaded onto a variety of third

c
In
party PC or server hardware platforms.

,
ls
ro
It provides network management, integration services, and coordinated control for

t
on
one or more FX Supervisory Controllers.

C
n
Niagara Analytics for analytic algorithms and diagnostic for real time and

so
historical. Every FX80 and FX Server is licensed for 25 analytic objects

hn
Jo
It optionally supports management of other IP/Ethernet-based devices.
such as:
by
19
Microsoft® SQL Server
20

BACnet® IP
ht

ModBus® TCP DB2

rig
y

OPC® Oracle®
op
C

oBix
Day 1 Facility Explorer® Overview

FX Server Overview (Cont’d.)

c
Refer to the FX Server Product Bulletin for available drivers.

In
,
ls
ro
There are various licensing options of the software based on:

t
on
C
Number of IP Devices to manage (10, 25, 50, 100, 200, 500,1000)

n
so
Database Support (MYSQL, Oracle, SQL, CSV, OPC)

hn
Jo
Number of Niagara Network Connections (0,1, 2, 3,10, 100, Unlimited)

by
Analytics (250, 1000, 2500, 10k, 50k, 100k, unlimited)
19
20
ht

Software Maintenance Plans are also available based on:

yrig

Number of years (1, 3, 5)

op
C

Number of Niagara Network Connections (0, 1, 2, 3, 10, 100, unlimited)

FX Workbench is fully integrated into the FX Server software.
Day 1 Facility Explorer® Overview

FX Server Overview (Cont’d.)

Capacity upgrade licenses are also available.

c
In
The software provides enterprise-wide automation and coordination that includes:

,
ls
ro
Master scheduling

t
on
Centralized, long-term, high capacity storage for alarm and history records

C
n
so
Single seat and single entry-point user interface for entire enterprise

hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

FX Server Overview (Cont’d.)

The FX Server is applicable to:

c
In
Projects requiring more than one FX Supervisory Controllers with true single-seat

,
ls
operation. Examples:

t ro
on
Large building with large number of field controllers and more than one FX Supervisory Controller

C
Campuses with multiple local buildings

n
so
National chains with multiple remote buildings

hn
Jo
Projects requiring large capacity and/or long-term storage of alarms and/or histories

by
19
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

FX Workbench

FX Workbench is an engineering tool for FX Supervisory Controllers and FX

c
In
Server stations. The tool:

,
ls
ro
Configures networks and adds devices/points

t
on
Adds and configures alarms, schedules, histories, totalizations, etc.

C
n
Performs program control routines such as:

so
hn
Data linking (global data sharing)

Jo
Interlocking
Control loops
by
19
20

Energy management
ht

Designs system user interface

y rig

Binds real time data to graphical symbols, labels, etc.

op

Creates reports
C

Defines users and access rights

Day 1 Facility Explorer® Overview

FX Workbench (Cont’d.)

Access:

c
In
It is served up by FX supervisory controllers or FX Server via a web browser

,
ls
ro
It may operate as a standalone software application on a PC

t
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Facility Explorer® Overview

FX Workbench (Cont’d.)

Labor saving features:

c
In
Online discovery of field devices and points for several protocols

,
ls
ro
JCI based controllers allow quick point mapping, online or offline

t
on
.CAF, .APD, .PRN, .DMO, or .VCT files

C
n
Points list and features are organized in a table, which eases enabling/disabling of point

so
extensions, including:

hn
Jo
Alarms

by
Trends 19
Totalization
20

Graphic pages can be automatically generated for standard systems

ht
rig

Customization is allowed
y

Schedule, Link, and Point Group Managers

op
C

Report Manager for summary point information on demand

Day 1 Facility Explorer® Overview

Facility Explorer® System with Programmable Controllers

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

Single FX80, N2 Communication Bus

c
Internet

, In
ls
ro
Web FX

t
Ethernet, TCP/IP, XML, HTTP Workbench

on
Browser

C
n
so
hn
FX80

Jo
by
19
Web
Browser
20

N2 Communication Bus
ht
y rig
op
C

FX06 FX-PCG FX16 DX-9100 VMA UNT TEC

Day 1 Facility Explorer® Overview

Single FX80 and BACnet® MSTP Communication Bus

c
Internet
INTERNET

In
,
ls
ro
Web FX

t
on
Browser Ethernet, TCP/IP, XML, HTTP Workbench

C
n
so
hn
FX80

Jo
by
19
Web
Browser
20

BACnet® MS/TP Communication Bus

ht
rig
y
op
C

3rd Party
BACnet®
FX-PCV FX-PCG FX-PCX FX-PCA Controllers
Day 1 Facility Explorer® Overview

Single FX80 and LON Communication Bus

c
Internet

In
,
ls
ro
Web FX

t
on
Browser Ethernet, TCP/IP, XML, HTTP Workbench

C
n
so
hn
Jo
FX80

by
19
Web
20

Browser
LON Communication Bus
ht
y rig
op
C

3rd Party
LonMark®
FX06 LX-PRG FX15 LX-VAV TEC Controllers
Day 1 Facility Explorer® Overview

Single FX80 and Multiple Communication Buses

c
,In
Internet

ls
ro
t
on
Web FX

C
Browser Ethernet, TCP/IP, XML, HTTP Workbench

n
so
hn
Jo
FX80

by
19
20

Web
MS/TP
Browser
ht
rig

N2
y
op

MODBUS®
C

LONWorks®
Day 1 Facility Explorer® Overview

Multiple FX Supervisory Controllers with FX Server

c
, In
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Facility Explorer® Overview

Summary

There are many FX supervisory controllers in the Facility Explorer ® product

c
In
series

,
ls
ro
These controllers provide integrated control, supervision, and network

t
on
management services to one or more local networks of field controllers

C
n
The FX Server provides integration services and coordinates control for one or

so
more FX Supervisory Controllers

hn
Jo
FX Workbench includes many labor saving configuration features
by
19
20
ht
yrig
op
C
C
JCI Appliance Workflow

op
yrig
ht
20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 JCI Appliance Workflow

Objectives

Welcome to the JCI Appliance Workflow lesson.

c
In
At the end of this lesson, you will be able to:

,
ls
ro
Identify the process steps to create a station

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 JCI Appliance Workflow

Flowchart for Creating a Station

Create a New Remove any Add Control Logic for

Add Users
Unnecessary Devices Added

c
JCI Station to the Station

In
Controller Objects Online

,
ls
ro
Copy Station from User
Add Appropriate Set up Email Create Graphics for
Home to Secure

t
on
Extensions Devices Added Online
Platform Daemon Home

C
n
Commissioning the

so
Define JCI Controllers Duplicate Typical Backup the Station
FX Supervisory
and Points

hn
Controllers
Controller

Jo
by
Add Equipment and Create Schedules
19 Backup the Station Enterprise Setup
Spaces
20
ht

Add Tags and Global Links Using Add Non-JCI Devices

rig

Hierarchies Link Manager and Points Online

y
op
C

Add Any Other Define and Test

Add Appropriate
Objects to the Control Logic
Extensions
Controller Routines
 Workbench Overview

C
op
yrig
ht
20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 Workbench Overview

Objectives

Welcome to the Workbench Overview lesson.

c
In
At the end of this lesson, you will be able to:

,
ls
ro
Identify the purpose of FX Workbench

t
on
C
Navigate through the application

n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Workbench Overview

Overview of FX Workbench Pro

FX Workbench Pro is a software application to:

c
In
Create stations offline for FX Supervisory Controllers

,
ls
ro
Upload and download FX Supervisory Controllers

t
on
Remotely connect to FX Supervisory Controllers

C
n
It Utilizes HTML5 – HTML5 based Software Framework but still allows for JAVA

so
hn
support for Browsers as well

Jo
Hardware Platform Independent
by
(runs on embedded FX Supervisory Controllers FX80)
19
20

FX Workbench Pro software must be licensed

ht
yrig
op
C
Day 1 Workbench Overview

Overview of FX Workbench

Following are some basic hardware/software requirements:

c
,In
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
y rig
op
C

Refer to the FX Supervisory Controller Family Software Products Installation Instructions for
current and detailed information. Also, check online for any update information.
Day 1 Workbench Overview

Licensing FX Workbench Software

Licensing is done through Johnson Controls Customer Service

c
In
License received from them will need to be copied to the following

,
ls
ro
folder on your PC:

t
on
C:\JCI\FXWorkbench-xx.x\security\licenses

C
n
The license is not transferable to another PC

so
hn
A new PC may be licensed by providing Johnson Controls with the host ID of the PC

Jo
being replaced

by
19
20
ht
yrig
op
C

“xx.x” is the version of FX Workbench purchased. (i.e. FXWorkbench-14.7)

Day 1 Workbench Overview

FX Workbench Main Screen

View Selector

c
In
Edit Path

,
ls
Menu Bar

ro
Tool Bar

t
on
C
Locator Bar

n
so
hn
Side Bars

Jo
by
View Pane 19
20
ht
yrig
op
C
Day 1 Workbench Overview

File Menu Options

Open Platform: Use this feature to open a

c
In
platform on the local host or network

,
ls
ro
Open Station: Use this feature to open a

t
on
station on a local host or a remote platform

C
n
Find Stations: Use this feature to find all

so
hn
stations on the Niagara Network

Jo
Save: This feature saves whatever is
currently in view by
19
20

Save All: This feature saves all BOG file

ht
rig

changes
y
op

Save BOG: This feature would save the

C

BOG in the current view

Day 1 Workbench Overview

File Menu Options (Cont’d.)

Back: This feature opens the previous view

c
In
Forward: This feature opens the next view

,
ls
ro
t
Home: This feature takes you to the home page

on
C
Refresh: This feature allows you to update the

n
so
current view

hn
Jo
Close: Use this feature to close the station
by
19
Exit: Use this feature to exit FX Workbench Pro
20
ht
yrig
op
C
Day 1 Workbench Overview

Edit Menu Options

Cut: Use this feature to cut data to Clipboard

c
In
Copy: Use this feature to copy data to Clipboard

,
ls
ro
Paste: Use this feature to paste data from Clipboard

t
on
Paste Special: Use this feature to paste data with options to keep all links

C
and/or all relations

n
so
hn
Duplicate: Use this feature to make a copy

Jo
of whatever is highlighted

by
Delete: Use this feature to remove an item from the
19
database
20

Rename: Use this feature to rename an item

ht
rig

Undo: Use this feature to reverse the last change

y
op

Redo: Use this feature to repeat the last change

C
Day 1 Workbench Overview

Bookmark Options

This feature allows users to create shortcuts to frequently used folders:

c
In
Graphics

,
ls
ro
Configuration files

t
on
Bookmark menu selections:

C
n
so
Add to Bookmarks: Select this feature to add whatever is highlighted in the navigation

hn
tree as a bookmark

Jo
Manage Bookmarks: Select this feature to
create, delete, and copy bookmarks
by
19
20

Go Into: Select this feature to add bookmark to a folder

ht

File: Select this feature to view existing bookmarks

yrig
op
C
Day 1 Workbench Overview

Tools Menu Options

Options: This feature is used to customize certain

c
In
parameters such as Auto log out, time format, etc.

,
ls
ro
Certificate Management: This feature manages secure

t
on
communications

C
n
Lexicon Tool: This feature is used to support other

so
hn
languages

Jo
Lon Xml Tool: This feature is used to make Lon Xml
by
(.lnml) file for a device, using the source .xif file and
19
20

(if necessary) other resource files, as available from the

ht

device's manufacturer
rig
y
op
C
Day 1 Workbench Overview

Tools Menu Options (Cont’d.)

System Library Editor: This feature allows you to edit

c
In
the way the appliance manages the objects in the

,
ls
controller configuration files

ro
t
on
Restore Folder Contents From Bog File: This feature

C
is used to add contents from a Bog file to the station

n
so
hn
Save Folder Contents To Bog File: This feature is

Jo
used to save specific data to a Bog file for later use
by
19
20
ht
rig
y
op
C
Day 1 Workbench Overview

Tools Menu Options (Cont’d.)

Generate LON Diagnostic File: This feature is used to

c
In
compare the APD to the LNML file when using

,
ls
FX Builder applications

t ro
on
Launch Project File: This feature is used to easily

C
import a major portion of a station database into

n
so
FX Workbench

hn
Jo
New JCI Station: This feature is used to create
a new database
by
19
20
ht
rig
y
op
C
Day 1 Workbench Overview

Tools Menu Options (Cont’d.)

Migrate Station: This feature migrates an FX 6.1

c
In
system or station to current release

,
ls
ro
Update Home Page Graphic: This feature is used to

t
on
automatically scan the remote station driver directory

C
and add hyperlinks to the main page for each added

n
so
controller

hn
Jo
Auto Tag Station Devices: This feature is used to
by
automatically add tags to an existing station. Tags will be
19
added based upon the System Library used for import to
20

all the devices and their points

ht
yrig
op
C
Day 1 Workbench Overview

Windows  Side Bars Menu Options

Show Side Bar: Use this feature to hide or view/display the side bar(s)

c
In
Jci Web Appliance Side Bar: Use this feature to navigate through options

,
ls
ro
(same as navigation)

t
on
Nav: This feature displays a tree view or hierarchical order of the whole

C
n
system including the content of your computer

so
hn
(only visible when logged in with an Admin level password)

Jo
Navigation: This feature provides a tree
by
view or a simplified hierarchical view
19
of a station
20
ht

Palette: This feature works as an additional

rig

tool to create graphics, custom control logic, etc.

y
op
C
Day 1 Workbench Overview

Various Palettes

The Palette feature allows users to add various components to a system:

c
In
Control routines

,
ls
ro
Graphics

t
on
C
Email

n
so
Additional networks/protocols

hn
Jo
Integrations

by
Filter allows for filtering of available
19
modules within the palette.
20
ht
yrig
op
C
Day 1 Workbench Overview

Niagara Objects

These 8 Niagara objects are integral to the driver architecture that is the

c
In
foundation on which all device integration rests.

,
ls
ro
COMMON OBJECT MODEL

t
on
C
Boolean Point

n
so
Boolean Writable

hn
Numeric Point

Jo
Numeric Writable

by
Enum Point
Enum Writable
19
String Point
20

String Writable
ht
yrig
op
C
Day 1 Workbench Overview

Standard Views

Wire Sheet: used for Linking components

c
In
Property Sheet: used for configuring components

,
ls
ro
Slot Sheet: used to configure all of the slots of a component

t
on
C
Action

n
so
Property

hn
Jo
Relation Sheet: displays all links and relations for a component
by
19
Category Sheet: displays the categories for a component
20
ht
yrig
op
C
 Day 1

Wire Sheet

C
op
yrig
ht
Workbench Overview

20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 Workbench Overview

Wire Sheet (Cont’d.)

Link from Source to Target

c
In
Can never link to In1 or In8 input slots

,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Workbench Overview

Property Sheet – Out Property

Value: Current Value output from

c
In
data item; conforms to one of the four

,
ls
data categories

t ro
on
Status: Indication of health and

C
validity; described by combination of

n
so
status flags: ok, disabled, fault, down,

hn
alarm, stale, overridden

Jo
Facets: Modify the display of the
by
19
values: precision, unit of measure,
20

text description
ht
rig

Priority: Current active priority level;

y
op

sixteen levels of priority with 1 being

C

the highest and 16 being the lowest

Day 1 Workbench Overview

Property Sheet – Facets

Boolean: Sets the displayed text depending upon the value of a point being

c
In
true or false

,
ls
ro
Numeric: Sets the display units, min/max and decimal precision

t
on
C
Enumerated: Sets the enumeration range

n
so
hn
Jo
by
19
20
ht
yrig
op
C
 Day 1

Slot Sheet

C
op
yrig
ht
Workbench Overview

20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 Workbench Overview

Slot Sheet (Cont’d.)

Niagara components are a collection of slots that define

c
In
Characteristics: Property

,
ls
Behavior: Action

ro
t
on
C
Definition of slots

n
so
Frozen: Cannot be edited

hn
Jo
Dynamic: May be added, deleted, renamed, reordered during runtime

by
19
Config Flags: Modifies how an object is presented or behaves
20

Read-only
ht
rig

Operator allowed
y
op

Hidden
C

Summary
Day 1 Workbench Overview

Slot Sheet (Cont’d.)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
 Station Creation

C
op
yrig
ht
20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 Station Creation

Objectives

Welcome to the Station Creation lesson.

Create a New

c
In
At the end of this lesson, you will be able to: Station

,
ls
ro
Use the New Station Wizard to create your database

t
on
Copy the Station to the Workbench

C
n
so
Check the Platform Application Director for a running station

hn
Jo
Remove any Add Users Add Control Logic for
Create a New
Unnecessary to the Station Devices Added
JCI Station

by
Controller Objects Online

Copy Station from User Create Graphics for

Add Appropriate
19
Home to Secure Platform Set up Email Devices Added
Extensions
Daemon Home Online
20

Define JCI Commissioning the

Controllers and Duplicate Typical FX Supervisory Backup the Station
Controllers Controller
ht

Points
rig

Add Equipment and

Create Schedules Backup the Station Enterprise Setup
Spaces
y
op

Add Tags and Global Links Using Add Non-JCI Devices

C

Hierarchies Link Manager and Points Online

Add Any Other Define and Test

Objects to the Control Logic Add Appropriate
Controller Routines Extensions
Day 1 Station Creation

Create a New Station Using the Wizard

FX Workbench Pro includes a New JCI Station wizard with same capabilities as

c
In
the Niagara New Station wizard but adds the following functionalities:

,
ls
ro
Add popular network drivers

t
on
N2

C
n
LonWorks®

so
hn
BACnet®

Jo
Ndio
by
19
Nrio
20

SNMP
ht
rig

Wireless TEC
y
op

Modbus
C
Day 1 Station Creation

Create a New Station Using the Wizard (Cont’d.)

FX Workbench Pro includes a New JCI Station wizard with same capabilities as

c
In
the Niagara New Station wizard but adds the following functionalities:

,
ls
ro
Add popular services

t
on
Tunnel (allows connection to remote supervisor)

C
n
Weather (displays the National Weather Service Information)

so
hn
SMS (allows alarms to be sent as .txt message to mobile device)

Jo
by
19
20
ht
yrig
op
C
Day 1 Station Creation

Create a New Station Using the Wizard (Cont’d.)

FX Workbench Pro includes a New JCI Station wizard with same capabilities as

c
In
the Niagara New Station wizard but adds the following functionalities:

,
ls
ro
Add predefined FX user role templates to the station

t
on
Operator

C
n
Maintenance

so
hn
Tenant

Jo
by
19
20
ht
rig
y
op
C
Day 1 Station Creation

Create a New Station Using the Wizard (Cont’d.)

FX Workbench Pro includes a New JCI Station wizard with same capabilities as

c
In
the Niagara New Station wizard but adds the following functionalities:

,
ls
ro
When finished the wizard offers the following options

t
on
Open the station in User Home

C
n
Use Station Copier to copy the station to the localhost secured platform and

so
optionally start the station

hn
Jo
Close the wizard

by
19
20
ht
rig
y
op
C
Day 1 Station Creation

Create a New Station Using the Wizard (Cont’d.)

During the New JCI Station wizard:

c
In
Station is named

,
ls
ro
Admin password is created

t
on
C
One upper case letter minimum

n
so
One lower case letter minimum

hn
One number minimum

Jo
by
10 characters minimum 19
20
ht
rig
y
op
C
Day 1 Station Creation

Using the Application Director

Application Director of the Secure Platform may be opened at any time.

c
In
Most common commands are:

,
ls
ro
t
on
C
n
so
hn
Jo
by
Start – Begins the station operation in the secured platform
19
20

Stop – Provides orderly shutdown of the station including a station save

ht
rig

Restart – Restarts the station in the secured platform

y
op

Kill – Immediately shuts down the station without any saves

C

The status of the station may be verified as well as diagnostic log of the running
station.
Day 1 Station Creation

Opening the copied Station

The running station may be opened by either:

c
In
Right-click My Host/Open Station

,
ls
ro
Select File/Open/Open Station, then

t
on
entering the IP Address of the remote

C
n
platform

so
hn
Right-click on an existing station

Jo
connection in the Nav sidebar and
selecting Open Station
by
19
20
ht
rig
y
op
C
Day 1 Station Creation

Niagara 4 Home Locations and Station Encryptions

c
, In
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Defining JCI Controllers and Points

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Objectives

Welcome to the Defining JCI Controllers and Points lesson. Define JCI

c
In
At the end of this lesson, you will be able to: Controllers &

,
ls
Points

ro
Add JCI controllers to a Supervisory Controller

t
on
Add points to a Supervisory Controller

C
n
Alter facets of points

so
hn
Remove points

Jo
Remove any Add Users Add Control Logic
Create a New for Devices Added
Unnecessary to the Station

by
JCI Station Online
Controller Objects

Copy Station from Create Graphics for

19
Add Appropriate Set up Email
User Home to Devices Added
Extensions
Secure Platform Online
20

Daemon Home
Commissioning the
Duplicate Typical Backup the Station
FX Supervisory
ht

Define JCI Controllers

Controllers and Controller
rig

Points

Create Schedules Backup the Station Enterprise Setup

y

Add Equipment
op

and Spaces
Add Non-JCI
C

Global Links Using

Add Tags and Link Manager Devices and Points
Hierarchies Online

Add Any Other Define and Test

Add Appropriate
Objects to the Control Logic
Extensions
Controller Routines
Day 1 Defining JCI Controllers and Points

Overview of Adding JCI Controllers

N2 Controllers are added to the N2 Network.

c
,In
ls
ro
BACnet®/MSTP Controllers are added to the BACnet® Network.

t
on
C
n
so
LON® Controllers are added to the LON® Network.

hn
(BcpLonNetwork if using LX Controllers)

Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Overview of Adding JCI Controllers (Cont’d.)

Points are added based on the resource file:

c
In
.CAF file: MSTP Controllers

,
ls
ro
t
.APD file: FX Field Controllers

on
C
.PRN file: ASC Controllers

n
so
hn
.DMO file: DX-9100 Controllers

Jo
.VCT file: MIG Controllers
by
19
20
ht

Based on the resource file, a graphic can be added for standard applications
yrig

Standard graphics can also be added for custom programs.

op
C
Day 1 Defining JCI Controllers and Points

Adding N2 Controllers

N2 controllers are added by type:

c
In
AHU, FX, MIG, PCV, PHX, TEC, UNT, VAV, VND

,
ls
t ro
VMA

on
C
DX

n
so
hn
TC

Jo
XTM
by
19
Define only typical types.
20

Modify the typical types then

ht
rig

duplicate later to save work.

y
op
C
Day 1 Defining JCI Controllers and Points

Adding N2 Controllers (Cont’d.)

Name will be display name

c
In
Address is the hardware DIP switch setting on the controller

,
ls
ro
t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Adding BACnet®/MSTP JCI Controllers

Number to Add will be the number of typical devices to be added

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Adding BACnet®/MSTP JCI Controllers (Cont’d.)

Populate the desired fields

c
In
The Device ID field displays the Instance Number of the controller

,
ls
ro
(set up when creating controllers in other software)

t
on
The Netwk field displays the network number of the communication bus (set

C
n
up in Workbench, should be unique number for entire site)

so
hn
The MAC Addr field displays

Jo
the DIP switch setting of the
controller
by
19
20

Set Use Cov to False

ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Newly Added Controller(s)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Adding Points and Graphics to JCI Controllers

Editing in the Jci BACnet Import Manager or Jci N2 Import Manager allows for

c
In
proper setup

,
ls
ro
System Library populates data from XML if you are using MSTP or FX field

t
on
controller. It will select the Workbench Std Graphic File and the

C
Hx Std Graphic File fields

n
so
hn
Import Graphic Type field designates previous generation Px images or the

Jo
newer Niagara 3.7 Px images
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Adding Points and Graphics to JCI Controllers (Cont’d.)

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Adding Points and Graphics to JCI Controllers (Cont’d.)

Resource File is the .CAF, .PRN, .DMO, .APD, etc., file

c
In
Import Graphic Type –

,
ls
tro
KitPxHVAC matches graphics built before Workbench 5.x

on
C
KitPxGraphics newer graphics

n
so
hn
Use Existing Graphic File and Use Existing Hx Graphic File fields allow

Jo
aliasing of a graphic to an existing graphic
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Adding Points and Graphics to JCI Controllers (Cont’d.)

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Adding Points and Graphics to JCI Controllers (Cont’d.)

Create New Graphic File field allows you to command the appliance to actually

c
In
make the graphic

,
ls
ro
Create New Hx Graphic File field allows you to command the appliance to

t
on
actually make the graphic

C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Adding Points and Graphics to JCI Controllers (Cont’d.)

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Adding Points and Graphics to JCI Controllers (Cont’d.)

Clean Graphic field allows you to remove unused symbols from a graphic and

c
In
resolve the proper links for the graphic templates

,
ls
ro
Update Action Menus field allows you to rebuild the command index after

t
on
changing facets of an object

C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Default Graphic Added Example (Legacy - Kit Px HVAC )

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Default Graphic Added Example (Wb 5.0 or later – Kit Px Graphics)

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Default Hx Graphic Added Example

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Location of the Points in the Controller

The points will be added to:

c
In
Station  Config  Drivers  Controller  Points

,
ls
t ro
on
C
Double-click Points to view all the points and their

n
so
respective data.

hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

The Points in a Controller

From the Point Extension Manager view:

c
In
Double-clicking the point links to the AX Property Sheet of the object

,
ls
ro
t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

The Points in a Controller (Cont’d.)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

The Points in a Controller (Cont’d.)

AX Property Sheet of a Point:

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

The Points in a Controller (Cont’d.)

From the Bacnet Point Manager (or N2 Point Manager) view:

c
In
Double-clicking the point links to the point configuration

,
ls
ro
Right-clicking the point displays the full right-click context menu

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

The Points in a Controller (Cont’d.)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

The Points in a Controller (Cont’d.)

From the BACnet Point Manager view:

c
In
Right-clicking the point and selecting View  AX Property Sheet

,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

The Points in a Controller (Cont’d.)

From the AX Bacnet Point Manager view:

c
In
Right-clicking the point displays the full right-click context menu

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Cleaning Up the Added Controller

Once the controller is added, review the added points and delete what is not

c
In
desired.

,
ls
ro
If the Supervisory Controller commands the value of any point, it must be defined

t
on
as:

C
n
Boolean Writable

so
hn
Numeric Writable

Jo
by
Enum Writable 19
It may be necessary to delete inputs that were added and redefine them as
20

writable points.
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Deleting Points

From the AX BACnet Point Manager view:

c
In
Highlight the desired points (standard “ctrl” and “shift -ctrl” options work)

,
ls
ro
Right-click any of the

t
on
highlighted items

C
n
so
Select the Delete option

hn
from the drop-down menu

Jo
by
19
20
ht
y rig
op
C
Day 1 Defining JCI Controllers and Points

Manually Adding Points

Points can be added to a controller without the use of a resource file.

c
In
Points are added after the controller has been added to the station

,
ls
ro
Any point that needs to be redefined:

t
on
C
Writable (Boolean Writeable, Numeric Writeable, Enum Writeable)

n
so
Non-Writable (Boolean, Numeric, Enum)

hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Manually Adding Points (Cont’d.)

1. Identify and select the appropriate point type from the Type to Add drop-down

c
In
list

,
ls
ro
2. Identify and enter the number of points to be added

t
on
3. Click the OK button

C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Manually Adding Points (Cont’d.)

4. Fill in the appropriate fields:

c
In
Facets are units of measurement as well as min/max values and decimal precision

,
ls
ro
Fill in the appropriate fields depending on the type of controller

t
on
C
n
so
There is no error checking for duplicated point addresses.

hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Manually Adding Points (Cont’d.)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Facet Example

c
In,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Facets for Enums

1. Click the >> icon to access Config Facets

c
In
,
ls
tro
on
C
n
so
hn
Jo
2. Click the … icon to access Facets

by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Facets for Enums (Cont’d.)

3. Click the >> icon to access Facets

c
In
4. Use your own or use a Frozen set:

,
ls
ro
The Frozen set has predefined states

t
on
and names

C
n
5. Deselect the Use Frozen Enum in

so
hn
Range (module:name) check-box to

Jo
enter your own data

by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Frozen Enum Example

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
y rig
op
C
Day 1 Defining JCI Controllers and Points

Using Your Own Enum Example

1. Ensure that the Frozen Enum in Range

c
In
(module:name) check-box is not selected

,
ls
ro
2. Type in the state and the associated

t
on
phrase you desire to use

C
n
so
3. Click the Add button to add the entered

hn
the data

Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Editing a Point

1. Be sure BACnet Point Manager is the active view for the controller you are

c
In
editing

,
ls
ro
2. Double-click a point and edit the desired field(s)

t
on
C
3. Click the OK button to save changes

n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Editing a Point (Cont’d.)

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Concerns for Boolean Outputs

1. Double-click a point from the Points Extension Manager list

c
In
2. “Fallback” is the value the point will go to on startup

,
ls
t ro
If the null option is selected, this feature will not be used

on
C
If the null option is deselected, the FX Supervisory Controller is in control of the point

n
so
24/7

hn
Jo
3. Set Min Active Time:

by
When commanded to state 1, for how long should it be on?
19
20

When commanded to state 0, for how long should it be off?

ht
rig

4. Set Min Inactive Time:

y
op

It keeps item in state 0

C

on power up
Day 1 Defining JCI Controllers and Points

Tuning Policies

JCI N2 Tuning Policies are rules assigned to proxy points for:

c
In
Evaluating Write Requests

,
ls
ro
Min Write Time – Minimum amount of time allowed between writes

t
on
Max Write Time – Maximum wait time before rewriting the value

C
n
Write on Start – If true, a write will occur when the station starts

so
hn
Write on Up - if true, a write occurs when parent device transitions from down to up

Jo
Write on Enabled - if true, a write occurs when writeable point transitions from disabled

by
Establishing acceptable freshness of read requests from polling
19
20

Stale Time
ht

If non-zero, point becomes stale (status stale) if time lapses without successful read.
y rig

If zero, point becomes stale immediately

op
C
Day 1 Defining JCI Controllers and Points

Tuning Policies (Cont’d.)

JCI FX N2 Predefined Tuning Policies

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20

Additional Tuning Policies may be defined as needed in the AX Property Sheet

ht

View of the jciN2Network

rig
y
op
C
Day 1 Defining JCI Controllers and Points

Tuning Policies (Cont’d.)

Use the following table as reference in configuration of N2 Tuning Policies

c
In
,
ls
ro
t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Tuning Policies (Cont’d.)

Poll Frequency Groups for N2 Points

c
In
Fast Rate – 1 sec

,
ls
ro
Normal Rate – 5 sec

t
on
C
Slow Rate – 30 sec

n
so
hn
Jo
by
Tuning Policies and Poll Frequency Group Assignments are modified using the
19
Point Extension Manager and will be discussed in a later lesson.
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Tuning Policies (Cont’d.)

BACnetTuning Policies are rules assigned to proxy points for:

c
In
Evaluating Write Requests

,
ls
ro
Min Write Time – Minimum amount of time allowed between writes

t
on
Max Write Time – Maximum wait time before rewriting the value

C
n
Write on Start – If true, a write will occur when the station starts

so
hn
Write on Up - if true, a write occurs when parent device transitions from down to up

Jo
Write on Enabled - if true, a write occurs when writeable point transitions from disabled

by
19
20
ht
yrig
op
C
Day 1 Defining JCI Controllers and Points

Tuning Policies (Cont’d.)

BACnetTuning Policies are rules assigned to proxy points for: (Cont’d)

c
In
Establishing acceptable freshness of read requests from polling

,
ls
ro
Stale Time

t
on
If non-zero, point becomes stale (status stale) if time lapses without successful read.

C
n
If zero, point becomes stale immediately

so
hn
Poll Frequency – Provide choice of 3 polling rates: Slow, Normal, Fast

Jo
Use COV – if true and BACnet device supports subscription COV service, it will be used

by
Use Confirmed COV – If Use COV is true and BACnet device supports Subscription COV, then
19
updates are attempted using BACnet Subscription Services
20

COV Subscription Lifetime – Lifetime in minutes for which Niagara subscribes for COV
ht
rig

notifications, then periodically re-subscribes occur. Value of zero means lifetime subscription,
y

however, there is no guarantee the subscription will persist through resets of the server device.
op
C
Day 1 Defining JCI Controllers and Points

Tuning Policies (Cont’d.)

JCI FX BACnet Predefined Tuning Policies

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C

Additional Tuning Policies may be defined as needed in the AX Property Sheet

View of the BACnet Network
Day 1 Defining JCI Controllers and Points

Tuning Policies (Cont’d.)

Use the following table as reference in configuration of FX-PC Tuning Policies

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht

Tuning Policies are modified using the Point Extension Manager and will be
yrig

discussed in a later lesson.

op
C
Day 1 Defining JCI Controllers and Points

Updating Action Commands

Changing facets of Boolean/Enum points will not automatically update the Action

c
In
facets.

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Defining JCI Controllers and Points

Updating Action Commands (Cont’d.)

In the Controller Property AX view

c
In
under JCI Device Extensions:

,
ls
ro
Update Action Menus is set to False

t
on
and saved

C
Update Action Menus is set to True

n
so
and saved

hn
Jo
This will update all of the facets in the

by
Action menu for this controller 19
20
ht
yrig
op
C
Point Extensions & Point Extension Manager

c
, In
ls
rot
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Objectives

Welcome to the Point Extension and Point Extension Manager lesson.

c
In
At the end of this lesson, you will be able to:

,
ls
Add Appropriate

ro
Understand Point Extensions Extensions

t
on
Define Custom Default Extensions for Points

C
n
Utilize Point Extension Manager

so
hn
Define Custom Extensions for Points

Jo
by
Remove any Add Users Add Control Logic
Create a New
Unnecessary to the Station for Devices Added
JCI Station
Controller Objects Online
19
Copy Station from User Create Graphics for
20

Add Appropriate
Home to Secure Platform Set up Email Devices Added
Daemon Home
Extensions
Online
ht

Define JCI Commissioning the

Controllers and Duplicate Typical FX Supervisory Backup the Station
rig

Points Controllers Controller

y

Add Equipment and

op

Create Schedules Backup the Station Enterprise Setup

Spaces
C

Add Tags and Global Links Using Add Non-JCI

Hierarchies Link Manager Devices and Points
Online

Add Any Other Define and Test

Objects to the Add Appropriate
Control Logic
Controller Extensions
Routines
Day 1 Point Extensions & Point Extension Manager

Overview of Extensions

Points Extensions are used to add functionalities such as:

c
In
Alarm notification

,
ls
ro
Trending

t
on
Totalization

C
n
There are sub-categories of each extension type

so
hn
It is possible to make user-defined types templates of extensions

Jo
by
Extensions may be added manually via Palettes
19
Point Extension Point Manager is a JCI tool exclusive to make easier and will be
20

discussed in the next lesson

ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Naming Extensions

Extension name must be unique on the station. Using the Niagara 4 palettes will

c
In
cause the Names to be duplicated

,
ls
ro
%parent.name% would cause a name of the parent component like OA-T to be

t
on
assigned. If any other OA-T histories existed anywhere on the station it would

C
cause a fault and not be functional

n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Naming Extensions (Cont’d.)

The JCI standard used in the library imports is to use the controller/point name

c
In
%parent.parent.parent.displayName%/%parent.displayName% would cause a

,
ls
ro
name [controller]/[point name] like in our example:

t
on
Longfellow/AHU1/OA-T The station name begins the name in either case.

C
n
so
hn
%parent.parent.parent%

Jo
by
%parent.parent% 19
%parent%
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions

Alarm extension are added to a point to monitor out of normal conditions.

c
In
Alarm Extensions (Analog):

,
ls
ro
Out Of Range

t
on
Status

C
n
so
Alarm Extensions (Boolean):

hn
COV

Jo
by
Command Failure 19
Status
20

Alarm Extensions (Enum):

ht
rig

Change of State
y
op

Command Failure
C

Status
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions (Cont’d.)

Alarm Palette contains the different extension that may be added manually

c
In
,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions (Cont’d.)

Dragging the appropriate extension to the blank space in the property sheet or to

c
In
the Name area will add it to the point

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions Out of Range

Alarm Inhibit - Prevents all alarm

c
In
generation when set to False

,
ls
ro
Inhibit Time - Amount of time the Alarm

t
on
Inhibit remains in effect after transition

C
to True

n
so
Time Delay - Minimum continuous time

hn
Jo
for alarm condition to be true before

by
transitioning to alarm status19
Alarm Enable - Selects which
20

Algorithms are turned on

ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions Out of Range (Cont’d.)

Fault Algorithm – Setup of the Fault alarm conditions and options

c
In
Offnormal Algorithm – Setup of Offnormal alarm conditions and options

,
ls
ro
Alarm Class – Specifies Alarm Routing for the component

t
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions Out of Range (Cont’d.)

High Limit – Value when exceeded will

c
In
initiate High Alarm condition

,
ls
ro
Low Limit – Value when below will initiate

t
on
Low Alarm condition

C
n
Deadband – Specifies change in value

so
necessary to leave either high or low

hn
Jo
alarm condition

by
Limit Enable – Specifies which limits are
19
turned on
20
ht
rig
y
op
C

Setup of Offnormal and Fault Algorithms are the same

Day 1 Point Extensions & Point Extension Manager

Alarm Extensions Boolean Change of State

Most of the attributes are the same as for the Out of Range alarm extension

c
In
except for

,
ls
ro
Alarm Value – Value when alarm condition exists

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions Enum Change of State

Most of the attributes are the same as for the Out of Range alarm extension

c
In
except for

,
ls
ro
Alarm Value – Value(s) when alarm condition exists

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Alarm Extensions Boolean (or Enum) Command Failure

Most of the attributes are the same as for the Out of Range alarm extension

c
In
except for

,
ls
ro
Feedback Value– Value of status of commanded component

t
on
C
n
so
hn
Jo
by
A later lesson will show how to composite an attribute and then link it to a status
19
component for actual application
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

History Extensions

Dragging the appropriate extension to the blank space in the property sheet or to

c
In
the Name area will add it to the point

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

History Extensions - Numeric COV

Enabled - Activates and Deactivates

c
In
History data collection function

,
ls
ro
Capacity - Specifies number of records

t
on
kept in the local station. Should be less

C
than 500 for Supervisory Controller

n
so
stations but could be larger for FX

hn
Servers. These records may be exported

Jo
to an FX Server for long term storage.
by
19
Change Tolerance Minimum change
20

necessary to record another record

ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

History Extensions - Numeric Interval

Enabled - Activates and Deactivates

c
In
History data collection function

,
ls
ro
Capacity - Specifies number of records

t
on
kept in the local station. Should be less

C
than 500 for Supervisory Controller

n
so
stations but could be larger for FX

hn
Servers. These records may be exported

Jo
to an FX Server for long term storage.
by
19
Interval Time between History Samples
20

taken by the extension

ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

History Extensions - Boolean (or Enum) COV

Enabled - Activates and Deactivates

c
In
History data collection function

,
ls
ro
Capacity - Specifies number of records

t
on
kept in the local station. Should be less

C
than 500 for Supervisory Controller

n
so
stations but could be larger for FX

hn
Servers. These records may be exported

Jo
to an FX Server for long term storage.
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Totalization Extensions

Dragging the appropriate extension to the blank space in the property sheet or to

c
In
the Name area or to the point name in the Nav View Panel will add it to the point

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Totalization Extensions – Discrete Totalization

Change of State Count Transition – Selects which transitions to count

c
In
Change of State Count - Specifies present number of transitions counted

,
ls
ro
Elapsed Active Time - Specifies present time in Active State

t
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Totalization Extensions – Numeric Totalization

Numeric Totalization Extension is used to integrate a numeric value over time

c
In
either Minutely or Hourly. Used for consumable items such as fuel, water, steam,

,
ls
air, etc

tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Overview of Extensions

Points Extensions Manager is used to add functionalities such as:

c
In
Alarm notification

,
ls
ro
Trending

t
on
C
Totalization

n
so
There are sub-categories of each extension type

hn
Jo
It is possible to make user-defined types of extensions

by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Point Extension Manager

Point Extension Manager is unique to Johnson Controls and provides an easy

c
In
way of:

,
ls
ro
Adding alarm, history and totalization extension to points in the station

t
on
Enable/Disable points

C
n
Add status flags

so
hn
Add point facets

Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Point Extension Manager (Cont’d.)

Point Extension Manager table view allows you to add history, alarm, or

c
In
totalization by just clicking in the cell and picking from a list of predefined default

,
ls
extensions.

tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Point Extension Manager (Cont’d.)

Once all the extensions are added, click the Save button to save your changes

c
In
Then you can double-click the point to set up the necessary parameters for that

,
ls
point

tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Point Extensions & Point Extension Manager

Point Extension Manager (Cont’d.)

Tuning policy assignments may be modified only from the

c
In
Point Extension Manager.

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Point Extension Manager (Cont’d.)

The Tuning Policy column needs to be added to the Point Extension Manager.

c
In
Click on the in the upper right corner and select Tuning Policy .

,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Point Extension Manager (Cont’d.)

Click on the cell for the tuning policy that needs to be changed and select the

c
In
appropriate new tuning policy. Then save

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Point Extensions & Point Extension Manager

Adding Default Extensions

Common Extensions may be added to the

c
In
Point Extension Defaults to save time in

,
ls
Station creation

rot
on
Point Extension Defaults are located within the

C
Facility Explorer folder

n
so
hn
Additional Point Extension Defaults may be

Jo
added to save time and normalize the station:
Zone Temp Alarms by
19
20

2 Deg change of value history

ht
rig

5 minute history interval

y
op
C

These new defaults now will appear on the

selection menu in the Point Extension Manager
Day 1 Point Extensions & Point Extension Manager

Global Point Extension Manager

It allows review of all the points in a station and a

c
In
place to add the desired extensions

,
ls
ro
It is accessed by double-clicking

t
on
Global Pt Ext Folder from the Nav Side Bar

C
under Config  Facility Explorer

n
so
hn
Caution: Attempting to add extensions using the

Jo
global extension manager will present every point
by
in the system at once. This may be cumbersome
19
to manage depending on the size of the
20

installation.
ht
yrig
op
C
Duplicating Controllers and Points

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Duplicating Controllers and Points

Objectives

Welcome to the Duplicating Controllers and Points lesson. Duplicate Typical

c
In
At the end of this lesson, you will be able to: Controllers

,
ls
ro
Identify the purpose of copying controllers

t
on
Copy controllers

C
n
so
hn
Jo
Remove any Add Users Add Control Logic for
Create a New
Unnecessary to the Station Devices Added
JCI Station

by
Controller Objects Online

Copy Station from User Create Graphics for

Add Appropriate
19
Home to Secure Platform Set up Email Devices Added
Extensions
Daemon Home Online
20

Define JCI Commissioning the

Controllers and Duplicate Typical FX Supervisory Backup the Station
Controllers Controller
ht

Points
rig

Add Equipment and

Create Schedules Backup the Station Enterprise Setup
Spaces
y
op

Add Tags and Global Links Using Add Non-JCI Devices

C

Hierarchies Link Manager and Points Online

Add Any Other Define and Test

Objects to the Control Logic Add Appropriate
Controller Routines Extensions
Day 1 Duplicating Controllers and Points

Overview - Copying Controllers

After each unique controller type is added, the copying process can be utilized for

c
In
efficiency in building the network

,
ls
ro
The typical controller should have:

t
on
Points added or removed

C
n
Extensions added

so
hn
Graphics verified to be exactly as required by the customer

Jo
by
History Extensions are copied but disabled by default
19
They are used for controllers such as:
20
ht

VAV boxes
rig

RTUs
y
op

FCUs
C

UVs
Day 1 Duplicating Controllers and Points

Copying Controllers

A typical controller may be copied in two different manners

c
In
Copy/Paste or Duplicate method:

,
ls
ro
Entire device and all underlying children are exactly copied

t
on
Graphics are relativized (aliased) and will not be individual files

C
n
so
History Extensions are copied but disabled by default and must be enabled manually

hn
Copy/Paste Special method:

Jo
by
Same as Copy/Paste and…. 19
Option to include copying either all relations or all links or both as well
20
ht
yrig
op
C
 Schedule Manager

C
op
yrig
ht
20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 Schedule Manager

Objectives

Welcome to the Schedule Manager lesson.

c
In
Create Schedules
At the end of this lesson, you will be able to:

,
ls
ro
Identify the objects and features that can be scheduled

t
on
Create a schedule for equipment to turn on and off at specified times and dates

C
n
Create a schedule to suspend alarming at specified times and dates

so
hn
Create a schedule for users to limit access at specified times and dates

Jo
by
Remove any Add Users Add Control Logic for
Create a New
Unnecessary to the Station Devices Added
JCI Station
Controller Objects Online
19
Copy Station from User Create Graphics for
Add Appropriate
20

Home to Secure Platform Set up Email Devices Added

Extensions
Daemon Home Online
ht

Define JCI Commissioning the

Controllers and Duplicate Typical FX Supervisory Backup the Station
rig

Points Controllers Controller

y

Add Equipment and

op

Create Schedules Backup the Station Enterprise Setup

Spaces
C

Add Tags and Global Links Using Add Non-JCI Devices

Hierarchies Link Manager and Points Online

Add Any Other Define and Test

Objects to the Control Logic Add Appropriate
Controller Routines Extensions
Day 1 Schedule Manager

Overview of Schedules

Schedules are used for:

c
In
Turning equipment on and off

,
ls
ro
Changing setpoints

t
on
C
Suspending alarm during specific hours of a day

n
so
Limiting access to the system during specific hours of a day

hn
Jo
by
19
20
ht
y rig
op
C
Day 1 Schedule Manager

Relationship between Calendars, Schedules, and Points

c
In
AH1-OCC

,
ls
ro
Snow Days AHU SCHEDULE AH2-OCC

t
on
WEEKLY

C
AH3-OCC

n
SPECIAL EVENTS

so
hn
Jo
HOLIDAY
by ZN1 LIGHTS
19
CALENDAR
20

LIGHT SCHEDULE ZN2 LIGHTS

ht
rig

WEEKLY
y

ZN3 LIGHTS
op

SPECIAL EVENTS
C
Day 1 Schedule Manager

Schedule

Schedules are used to command a component based upon a time of day/day of

c
In
week event

,
ls
ro
Boolean Schedule will command a Boolean writeable point type True/False

t
on
(Facets adjustable)

C
n
Enumeration Schedule will command an Enum writeable point type with either

so
manual entered Facets or Frozen Enum set to match a particular field Enum

hn
Jo
set

by
Numeric Schedule will command a Numeric Writeable point type
19
20

Calendar Schedule may be referenced by one or more schedules to trigger a

ht

special event schedule. Calendar contains no time of day. Only a list of dates.
rig

The calendar will trigger the special event calendars on the schedules that
y
op

reference it if today is a day on its list.

C
Day 1 Schedule Manager

Calendar Examples

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Schedule Manager

Calendar Examples

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Schedule Manager

Changing the Properties of a Schedule

1. Click on the Properties tab and review the Default Output options and adjust

c
In
as needed

,
ls
ro
2. Save changes when done

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Schedule Manager

Schedule Commands

Start and stop events are schedule base on the day of week

c
In
Events can be easily copied or edited

,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Schedule Manager

Special Event Schedules

Special Events are events that are in place of, or in addition to the weekly

c
In
schedule

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Schedule Manager

Special Event Schedules (Cont’d.)

Types of special events:

c
In
Date

,
ls
ro
Date range

t
on
C
Week and day

n
so
Custom

hn
Jo
Reference:

by
References are calendars
19
They need to be created before they are referenced by the schedule
20
ht
y rig
op
C
Day 1 Schedule Manager

Special Event Schedules Details

The order of Special Events is

c
In
important. If there is a conflict

,
ls
between the entries, the entry

t ro
nearer the top has precedence.

on
C
Orders can be rearranged.

n
so
When adding References, sure to

hn
Jo
highlight the calendar, even if only

by
one is listed. 19
20
ht
yrig
op
C
Day 1 Schedule Manager

Actions on Special Events

Define what you want to do by blocking the appropriate

c
In
times and selecting the appropriate output.

,
ls
ro
Adjust the following as needed:

t
on
Event Start time

C
n
Event Finish time

so
hn
Event Output

Jo
by
Special Events merge with the Weekly Schedule.
19
If there is a conflict, the Special Events have
20

precedence.
ht
rig
y
op
C
Day 1 Schedule Manager

Validating Special Events

Selecting a given Special Event entry will identify dates the meet the defined

c
In
criteria.

,
ls
ro
You will need to through the months of the calendar to identify them.

t
on
C
Useful to validate entries.

n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Schedule Manager

Effective Periods for Schedules

The Properties tab shows when the schedule is in effect.

c
In
The schedule may be active in any part of the year.

,
ls
ro
t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Schedule Manager

Summary for Schedules

The Summaries tab shows what will happen on a particular date.

c
In
Beneficial to validate events will execute as desired.

,
ls
tro
Any day in green has an event associated with it.

on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Schedule Manager

Creating Links for a Schedule

Schedules need to be linked to the components to be commanded.

c
In
,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Schedule Manager

Creating Links for a Schedule (Cont’d.)

Linking through schedule manager is

c
In
typically done from a list of points.

,
ls
t ro
on
Points may be sorted to facilitate multiple

C
n
linkings to similar points like

so
Occ-Schedule.

hn
Jo
Schedule may be linked to any by
19
20

compatible target of that component.

ht

In16 is most common.

yrig
op
C
Day 1 Schedule Manager

Alarm Inhibit Schedules

Alarm Inhibit schedules suspend alarming during specified hours of the day.

c
In
You need to have alarms set up for the feature to work.

,
ls
tro
A Boolean schedule is used to trigger the alarm suspension.

on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Schedule Manager

Alarm Inhibit Schedules (Cont’d.)

1. Select the Link to Alarm Inhibit

c
In
check-box in the Link Type

,
ls
section.

t ro
on
2. Select the appropriate points to

C
suspend alarming.

n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Schedule Manager

User Schedules

User Schedules restrict users to the system during certain hours of the day.

c
In
,
ls
ro
t
1. For the users, change

on
C
Allow Scheduled Access to True

n
so
hn
A Boolean schedule is used to

Jo
trigger the access feature.

by
19
20
ht
yrig
op
C
Day 1 Schedule Manager

User Schedules (Cont’d.)

2. Select the Link to Users check-box in the Link Type section

c
In
3. Select the appropriate users to limit their access to the system

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Data Sharing using Link Manager
Day 1 Data Sharing using Link Manager

Objectives

Welcome to the Link Manager lesson. Global Links Using

At the end of this lesson, you will be able to: Link Manager

Identify the purpose of sharing data between controllers

Configure Link Manager to share data between controllers
Use Link Mark
Remove any Add Users Add Control Logic for
Create a New
Unnecessary to the Station Devices Added
JCI Station
Controller Objects Online

Copy Station from User Create Graphics for

Add Appropriate
Home to Secure Platform Set up Email Devices Added
Extensions
Daemon Home Online

Define JCI Commissioning the

Controllers and Duplicate Typical FX Supervisory Backup the Station
Points Controllers Controller

Add Equipment and

Create Schedules Backup the Station Enterprise Setup
Spaces

Add Tags and Global Links Using Add Non-JCI Devices

Hierarchies Link Manager and Points Online

Add Any Other Define and Test

Objects to the Control Logic Add Appropriate
Controller Routines Extensions
Day 1 Data Sharing using Link Manager

Overview of Sharing Data

It is always advantageous to send the value from one controller to

other controllers:
All have the same value for mode of operation
It reduces installation costs
When the value of the source point is changed, controllers receiving the value also
get updated.
Values are updated on a polling of the source point.
Process of sharing data is known as Linking:
Define the Source
Define the Target (Destination)
Day 1 Data Sharing using Link Manager

Overview of Sharing Data (Cont’d.)

The target must be defined as an output or have an attribute that can

be written
Two Methods for making Links:
Link Manager
Link Mark Manually Linking Source/Target (Destination)
(standard Niagara feature)
Day 1 Data Sharing using Link Manager

Using the Link Manager

To Access the Link Manager, Double-click Link Folder in the Nav sidebar
Link Manager contains a list of links the user creates between points in the
station
Day 1 Data Sharing using Link Manager

Methods of Linking

Link Manager provides a single screen to view and/or link station components
together in a centralized location.

Link Mark/Link to is a Niagara standard way of manually making the links by

searching out the two components to link and making the connection.

Link Manager optionally will show all links within the station made both with
Link Manager and with Link Mark/Link to.
Custom Control
Day 1 Custom Control

Objectives

Welcome to the Custom Control lesson. Define and Test

At the end of this lesson, you will be able to: Control Logic
Routines
Identify the purpose of the control routines
Create the control routines

Remove any Add Users Add Control Logic

Create a New for Devices Added
Unnecessary to the Station
JCI Station Online
Controller Objects

Copy Station from Create Graphics for

Add Appropriate Set up Email
User Home to Devices Added
Extensions
Secure Platform Online
Daemon Home
Commissioning the
Duplicate Typical Backup the Station
Define JCI FX Supervisory
Controllers
Controllers and Controller
Points

Create Schedules Backup the Station Enterprise Setup

Add Equipment
and Spaces

Global Links Using Add Non-JCI

Add Tags and Link Manager Devices and Points
Hierarchies Online

Add Any Other Define and Test

Add Appropriate
Objects to the Control Logic
Extensions
Controller Routines
Day 1 Custom Control

Overview of Control Routines

Control routines are used for a variety of purposes:

Sequencing equipment
Resetting setpoints
Switching modes based on certain conditions
Forcing equipment On or Off based on various conditions
These routines use Wire Sheets and custom control blocks.
They perform the majority of the control not in the field controller.
Day 1 Custom Control

Palettes for Control Routines

Palettes contain a wide variety of control blocks.

To open a palette, click the Window  Side Bars menu and select the Palette
option from the drop-down menu.
You can open multiple palettes.
Day 1 Custom Control

Palette Contents

Palette Displayed Maximizes/Restores Palette

Preview

Close Palette

Open Palette
Day 1 Custom Control

Common Palettes for Control

Day 1 Custom Control

Location of Custom Controls

By default, there is a folder called Custom Control.

This is where custom control routines should be
stored.
Create folders in the Custom Control folder to
organize the control routines.
Day 1 Custom Control

Creating a Folder

1. Double-click the Custom

Control folder
2. Next, right-click the wire sheet
and select the New  Folder
option from the drop-down
menu to create a folder

If you are using a browser to write control routines directly in the Supervisory
Controller, you will need to use the baja palette. Right-clicking does not work.
Day 1 Custom Control

Creating a Folder (Cont’d.)

3. Assign a name to the Folder

4. Depending on how complex the job is, you
can create folders within folders:
Logic for a building
Type of logic
Type of mechanical system, etc.
5. Click the OK button when you are finished
6. Click on the folder and stretch it horizontally
until you can read the name fully,
if necessary
7. Double-click the folder after it is
created to add logic
Day 1 Custom Control

Adding Needed Blocks for Control (Cont’d.)

8. From the Palette, drag over the desired

function and give it a name
Day 1 Custom Control

Adding Needed Blocks for Control (Cont’d.)

9. The default name is the name of the block dragged over

10. Click the OK button when you are finished
Day 1 Custom Control

Adding Needed Blocks for Control (Cont’d.)

11. Right-click an existing object on the wire sheet to duplicate it

12. Rename the object
13. Click OK
Day 1 Custom Control

Adding Needed Blocks for Control (Cont’d.)

14. Constants are in the kitControl library

15. Add writable points by right-clicking in an open area of the wire sheet
Day 1 Custom Control

Example of Blocks Added to Wire Sheet

Day 1 Custom Control

Making the Necessary Connections

1. After the blocks are added, connections are done by marking the source and
connecting it to the target
2. Right-click the source and select the Link Mark option from the drop-down
menu
Day 1 Custom Control

Making the Necessary Connections (Cont’d.)

3. Right-click the target and select the Link From “xxx” option from
the drop-down menu
Day 1 Custom Control

Making the Necessary Connections (Cont’d.)

4. In the Source pane, select

Out
5. In the Target pane, select
appropriate attribute
6. Click the OK button
7. Link Manager is another
option for making
connections
Day 1 Custom Control

Example of Completed Wire Sheet Connections

You may need to rearrange the blocks to make it easier to understand

Blocks can be resized, if desired
The field points do not appear on the wire sheet
A Writable point is added to
represent the field point.
This is optional but
recommended
Connections to the field
point are made by
marking the appropriate
block and making the
connection
Day 1 Custom Control

Making External Connection from a Source

1. Right-click the desired source and select the Link Mark option from the
drop-down menu
Day 1 Custom Control

Making the Connection to the Wire Sheet

1. Open the control logic back up and right-click

the desired target
2. Select the Link From “xxx” option from the
drop-down menu
Day 1 Custom Control

Making the Connection to the Wire Sheet (Cont’d.)

3. In the Source pane, select Out

4. In the Target pane, select
appropriate attribute
5. Click the OK button
Day 1 Custom Control

Setting Constant Values

The constants have no values by default

Right-click the constants and select the Actions  Set option from the drop-down
menu
Define the desired value
Verify the value in the Constant
Day 1 Custom Control

Completed Logic Example

The little “nub” shows that attribute is coming from an external source
When online, live data will be displayed
Day 1 Custom Control

Reviewing the Source Connection

In the Point Manager:

1. Right-click the point
2. Select the View  Relation Sheet option
Day 1 Custom Control

Reviewing the Source Connection (Cont’d.)

3. Double-clicking in a row allows you to edit that field

Day 1 Custom Control

Reviewing the Target Connection

4. In the control logic wire sheet:

a. Right-click the point
b. Select the View  Relation Sheet option
Day 1 Custom Control

Target Command List

Review the AX Property Sheet for the target point

The Out is the current command, hence, the top priority (when online)
The various In“x” are the priority inputs, where “x” implies numbers suggesting
priority
Day 1 Custom Control

Clarifying What the Routine Does

Text Block can be added to describe what the routine does

It is useful for service or the end-user to understand what is going on
Right-click to select the
New  TextBlock option

If you are using a browser to write control routines directly in the Supervisory
Controller, you will need to use the baja palette. Right-clicking does not work.
Day 1 Custom Control

Defining the Text Block

Give the TextBlock a name

After clicking OK, a hashed area is displayed
Double-click the hashed area to add the text
Day 1 Custom Control

Defining the Text Block (Cont’d.)

Add the necessary text

If the text doesn’t wrap up, press
enter at the desired locations to
put text in multiple lines
You may need to resize the box
appropriately
Day 1 Custom Control

Example of Added Text

Defining Users and Roles
Day 1 Defining Users and Roles

Objectives

Welcome to the Defining Users lesson.

Add Users
At the end of this lesson, you will be able to: to the Station
Identify a user
Identify the various types of roles
Explain the capabilities of various roles
Define users and assign them a role
Assign Hierarchy to Role
Remove any Add Users Add Control Logic for
Create a New
Unnecessary to the Station Devices Added
JCI Station
Controller Objects Online

Copy Station from User Create Graphics for

Add Appropriate
Home to Secure Platform Set up Email Devices Added
Extensions
Daemon Home Online

Define JCI Commissioning the

Controllers and Duplicate Typical FX Supervisory Backup the Station
Points Controllers Controller

Add Equipment and

Create Schedules Backup the Station Enterprise Setup
Spaces

Add Tags and Global Links Using Add Non-JCI Devices

Hierarchies Link Manager and Points Online

Add Any Other Define and Test

Objects to the Control Logic Add Appropriate
Controller Routines Extensions
Day 1 Defining Users and Roles

Overview of Users and Roles

Users are people who will use the building automation system.
Each user corresponds to at least one role.
The role will determine what a user can or cannot do with the building automation
system.
Five roles are standard in FX.
Custom Roles can be defined with Role Service.
Permissions to view Hierarchies are given to Roles.
Day 1 Defining Users and Roles

Types of Roles
Day 1 Defining Users and Roles

Types of Roles (Cont’d.)

Day 1 Defining Users and Roles

Creating User Type Defaults

User Types are used as default user setups for similar users most commonly:
Nav File
Roles
Web Profile
Mobile Web Profile
User Types are duplicated into User Services as new users.
It is possible to make other default user types
(other than admin, tenant, operator, and maintenance.)
Graphics
Day 1 Graphics

Objectives

Welcome to the Graphics lesson.

After completing this lesson, you will be able to:
Identify the purpose of graphics
Alter an existing graphic
Copy a graphic
Associate a graphic to a controller
Use Relative References for typical graphics
Add a field controller to an FX Supervisory Controller utilizing a
Standard Graphic
Rename Points to reflect the standard naming conventions
in a graphic
Change the Home Page Graphics
Edit the data on the Home Page
Day 1 Graphics

Objectives

Create a New
Remove any
Unnecessary Controller
Add Users Add Control Logic for Create Graphics
JCI Station to the Station Devices Added Online
Objects
for Devices
Copy Station from User
Added Online
Add Appropriate Create Graphics for
Home to Secure Platform
Extensions Set up Email Devices Added Online
Daemon Home

Define JCI Controllers

Duplicate Typical Commissioning the FX
and Points Backup the Station
Controllers Supervisory Controller

Add Equipment and

Create Schedules Backup the Station Enterprise Setup
Spaces

Add Tags and Global Links Using Add Non-JCI Devices

Hierarchies Link Manager and Points Online

Add Any Other Objects Define and Test Control

to the Controller Logic Routines Add Appropriate
Extensions
Day 1 Graphics

Overview of Graphics

Graphics are used to give the user a visual representation of a

mechanical system.
Standard applications have standard graphics.
They can be modified to add/delete items
By default, a graphic is created for every controller added to the station.
It is possible to create a common graphic for “typical” controllers
By default, when a controller is opened, the associated graphic opens up
Day 1 Graphics

Location of the Graphics

The graphics are stored in the

Graphics folder.
When controllers are added,
options exist to make a graphic.
When the controller is opened, the
graphic is populated with the data
from that controller.
Day 1 Graphics

Default Main Graphic Example Workbench 4.1 and Earlier

Day 1 Graphics

Default Main Graphic Example Workbench 5.0 and Later

Kit PX Graphics is the new library of symbols. There is an option to use the Kit
PX HVAC images from release 4.1 and earlier.
Day 1 Graphics

Graphic Px Example

If you open the Px file, it shows no data.

It is simply a static background.
Click Px Editor to view which data will appear and where will it appear.
Day 1 Graphics

Px Editor
Day 1 Graphics

Common Components in Px Editor

Bound Ords:
It identifies the objects that need to be in the graphic
Widget Tree:
It identifies the components that need to be in the graphic
Properties:
It identifies colors, fonts, borders, etc., for the components in the graphic
Day 1 Graphics

Bound Ord Details

Bound Ords will either be relative or absolute:

If station:|slot:/xxx appears, it is absolute
If slot:points/xxx appears, it is relative
It is useful for typical units
Clicking the Relative Ords icon will make the appropriate points relative to the
controller.
Day 1 Graphics

Example of Relationship Between Graphic Components

All these items relate to the Cooling Valve Output.

Day 1 Graphics

Adding items to a graphic

To add items to a graphic, use Palettes.

Following are some of the common
palettes for graphics:
bajaui
kitControl
kitPx
kitPxGraphics
kitPxHvac
kitPXHvacSmall
KitPxN4svg
Day 1 Graphics

bajaui Palette Contents

Widgets:
Labels contain static data
HyperlinkLabel provides a mechanism to link to some other
item in the station
Another graphic
Schedules
Alarm Console
Shapes
Panes
Day 1 Graphics

kitPx Palette Commonly Used Items

BoundLabel:
This feature is used to display dynamic data from
an object in the station
SetPointSlider:
This feature is used for graphical representation of
a slider for setpoint changes
Day 1 Graphics

kitPxHvac Palette Contents

It contains several HVAC related graphical components:

Duct sections
Coils
Piping
Valves
Day 1 Graphics

kitPxHvacSmall Palette Contents

It has same components as kitPxHvac, but is designed to create graphics for

smart phones:
Duct sections
Coils
Piping
Valves
Day 1 Graphics

Adding Bound Data to a Graphic

1. Double-click the desired controller or graphic

2. From the menu bar, select PX Viewer  Toggle View/Edit Mode
Two methods:
Expand the Nav tree and drag items into the graphics (preferred)
From the kitPx palette, drag a Bound label onto the graphic:
1) Add it to the grid area, only
2) Double-click the newly added symbol in the graphic
3) Edit the properties of the bound symbol
Day 1 Graphics

Adding Data to a Graphic by Dragging and Dropping

1. Make sure you are in the Edit mode for the

graphic
2. Navigate to the point following the path below
in the Nav explorer view:
My Host  Station  Config  Drivers 
xxNetwork  yyController  Points
3. Drag the desired point onto the graphic
Day 1 Graphics

Adding Data to a Graphic by Dragging and Dropping (Cont’d.)

4. Select the Bound Label check

box to simply view the data and
edit the properties as desired

Change the Format Text to %out.value% to display just the value of the point.
Day 1 Graphics

Fields in a Make Widget

Bound Label: It shows the value of the point

From Palette: It adds a graphic symbol to the bound point. Depending on the
graphic symbol added, it may be animated
Workbench View: It provides options to show the property sheet, wire sheet, slot
sheet, etc., for a point
Properties: It allows you to view certain properties of a point in the graphic
Actions: It provides buttons to give commands to the point
Time Plot: It adds a trend for the point to the graphic
Chart: It embeds a History log into the graphic
Day 1 Graphics

Common Attributes Modified in a Bound Label

Format Text: It adds some text to the label in addition to the value
Status: If the item under consideration is not normal, it can change color or blink
and change color
Hyperlink: It provides a hyperlink to the points property sheet
Mouse Over: When mouse moves over point, it highlights or outlines the text
(it suggests for “commandable” points)
Border: It puts a box around a label
Make Display Name Label: It adds point name to label
Other fields can be altered
Day 1 Graphics

Other Attributes Modifiable in a Bound Label

When using the Make Widget feature, other fields

shown on the right side can also be edited:
Fonts
Colors
Day 1 Graphics

Adding Bound Data to a Graphic via the Palette

1. From kitPx Palette, drag a BoundLabel

onto the graphic
Add it to the grid area only
2. Double-click the newly added symbol in
the graphic
3. Edit the properties of the bound symbol
Day 1 Graphics

Making Ords Relative

1. Click the Relative Ords icon

2. In the displayed Relative Ords box,
click the OK button
3. The items that are already relativized
have a 
4. The items that are yet to be relativized,
have a  next to them
Day 1 Graphics

Making a Graphic from Scratch

If possible, duplicate something that already

exists and modify
1. To begin totally from scratch right-click
the component
2. Select the Views  New View option
from the short-cut menu
3. Give the graphic a name
4. Edit the new graphic
Day 1 Graphics

Making a Graphic from Scratch (Cont’d.)

5. Some of the symbols will appear as a hatched area with no symbol

appearing in
6. This occurs until the symbol is bound to an actual point in the station
7. Sometimes you need a symbol to appear on the graphic, but not linked to an
actual item
You can make a fictitious Boolean writable point and bind to it
Day 1 Graphics

Adding a Floor Plan

1. With the Graphics directory open, right-click to select the New  PxFile.px
option from the short-cut menu and give the file a proper name
2. Copy the floor-plan image into the graphics directory
3. Right-click the image and select the Views  Image Viewer option from the
short-cut menu
4. Note the dimensions of the image
Day 1 Graphics

Adding a Floor Plan (Cont’d.)

5. Open the floor-plan graphic and edit it

6. In the Widget Tree explorer view, expand the ScrollPane and double-click the
CanvasPane
7. Change the viewSize data to match the dimension of the image
8. Next, click the OK button to save the updated data
Day 1 Graphics

Adding a Floor Plan (Cont’d.)

9. From the Nav explorer view, drag the image onto the graphic page and place it
in the upper-left corner of the screen
10. From the Nav explorer view, drag the appropriate points onto the floorplan and
modify, as needed
11. Save your changes
Using Standard Graphics for Non Standard Applications
Day 1 Using Standard Graphics for Non Standard Applications

Overview

Mechanical systems are very similar regardless of the type of field controller used to
control that system.
JCI has standard graphics created for applications developed in HVAC Pro,
Builder Express (N2), and PCT.
However, these graphics can be applied to other controllers used from
similar applications:
LON®
MSTP
DX-9100
Day 1 Using Standard Graphics for Non Standard Applications

Precautions

The names of the points and point types in the FX Supervisory Controller need to
be the same as the name the Standard Graphic expects them to be.
It is suggested to print the Standard Graphic naming convention and use it as a
guide.
Day 1 Using Standard Graphics for Non Standard Applications

Standard Graphic Naming Examples

FX Fan Coil Unit Fan Coil

Short Name Description Short Name Description
ACLG-SP Active Cooling Setpoint ACTCLGSP Active Cooling Setpoint
AHTG-SP Active Heating Setpoint ACTHTGSP Active Heating Setpoint
CLG-C Cooling Command CLG1-C Stage 1 Cooling Command
CLG-O Cooling Output CLG-FB-C Cooling Face and Bypass Command
HC-O Heating/Cooling Output CLG-FB-O Cooling Face and Bypass Output
HTG-C Heating Command CLG-O Cooling Output
COM-COIL-O Common Coil Output
Day 1 Using Standard Graphics for Non Standard Applications

Using a Standard Graphic for a Custom Application

1. Add the controller following the usual process

2. Attach the appropriate resource file, if applicable
3. Click the  icon associated with the Workbench Std Graphic File field to
change it to one that matches the application. File must be in Shared directory
of the localhost secured platform
4. Select the True option in the Create New Graphic File field, or select the
Use Existing Graphic File option to locate a graphic of your choice
Day 1 Using Standard Graphics for Non Standard Applications

Example of a Standard Graphic Used with a DX-9100

Day 1 Using Standard Graphics for Non Standard Applications

Example of a Standard Graphic Used with a LON® Controller

Commissioning the FX Supervisory Controller

c
In,
ls
t ro
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Commissioning the FX Supervisory Controller

Objectives

Welcome to the Commissioning the FX Supervisory Controller lesson.

c
In
At the end of this lesson, you will be able to: Commissioning the

,
ls
FX Supervisory

ro
Identify the purpose of downloading a station Controller

t
on
Perform a station copy using the Commissioning Wizard

C
Identify the purpose of backing up a station

n
so
Perform backing up of a station

hn
Work with the DIST file format

Jo
by
Remove any Add Users Add Control Logic for
Create a New
Unnecessary to the Station Devices Added
JCI Station
Controller Objects Online
19
Copy Station from User Create Graphics for
Add Appropriate
20

Home to Secure Platform Set up Email Devices Added

Extensions
Daemon Home Online
ht

Define JCI Commissioning the

Controllers and Duplicate Typical FX Supervisory Backup the Station
rig

Points Controllers Controller

y

Add Equipment and

op

Create Schedules Backup the Station Enterprise Setup

Spaces
C

Global Links Using Add Non-JCI Devices

Add Tags Link Manager and Points Online

Add Any Other Define and Test

Objects to the Control Logic Add Appropriate
Controller Routines Extensions
Day 1 Commissioning the FX Supervisory Controller

Overview of Commissioning an FX Supervisory Controller

Commissioning an FX Supervisory Controller(remote host) provides method to

c
In
perform essential tasks. Normally done just once at initial startup

,
ls
Install Software Licenses

tro
Enable Runtime Profiles

on
C
Install a station (via Station Copy)

n
Install lexicons for additional language support

so
hn
Install/upgrade modules

Jo
Install/upgrade core software
by
Configure TCP/IP network settings
19
Remove platform default user account (performed at initial logging into the
20

platform)
ht
rig

Configure additional platform user accounts

y
op

The major software revision of the remote host controller must match that of the
C

FX Workbench. A Niagara 4 remote host can only be commissioned from a

14.x FX Workbench
Day 1 Commissioning the FX Supervisory Controller

Overview of Commissioning an FX Supervisory Controller (Cont’d.)

Setting Runtime Profiles

c
In
Runtime - Always preselected and read only and are required

,
ls
UX – Selected to support Web client browser access

ro
t
WB – Selected to enable browser FX Workbench

on
C
(selected automatically with UX)

n
SE – Not available for QNX based controller

so
hn
DOC – Downloads Documentation into remote controller. Not recommended

Jo
Most times Runtime/UX/WB are selected
by
19
Install a station from Workbench using Station Copy
20

START AFTER INSTALL – Since this is a remote host, this option should be
ht

checked
rig

AUTO START – Since this is a remote host, this option should be checked
y
op

Copy file in the station directory – Most common selected of files to copy
C

during Commissioning an FX Supervisory Controller

Day 1 Commissioning the FX Supervisory Controller

Overview of Commissioning an FX Supervisory Controller (Cont’d.)

Install Lexicon – Not recommended in Niagara 4. Use modules of customized

c
In
lexicons during Install/upgrade modules

,
ls
ro
Install/upgrade modules

t
on
Preselects all modules needed by the Controller in comparison with

C
Workbench

n
so
A list of minimum files needed by FX Workbench are listed in FX80 Software

hn
Installation and Quick Start Technical Bulletin

Jo
Module can be sorted alphabetical by clicking the header
by
19
Configure TCP/IP network settings
20

Interface 1 is the Ethernet connection defaulted for the Niagara Network

ht

Supports DHCP
rig

Default IP Address is 192.168.1.149

y
op

Interface 2 is for service port

C

Does not support DHCP

Day 1 Commissioning the FX Supervisory Controller

Overview of Commissioning an FX Supervisory Controller (Cont’d.)

Configure additional platform users

c
In
Default platform user is removed and new one added at initial login before

,
ls
ro
commissioning wizard can be invoked

t
on
Default Platform User Name: jci

C
n
Default Platform Password: explorer

so
hn
Default Platform Passphrase: explorer

Jo
This step allows you to configure additional platform users
by
19
20
ht
rig
y
op
C
Day 1 Commissioning the FX Supervisory Controller

Using Serial Shell for an FX Supervisory Controller

Serial Shell is low level access to a few of the basic platform settings:

c
In
Updating System Time

,
ls
Updating Network Settings

tro
on
Change Current Platform User’s Password

C
Change System (Platform) Passphrase

n
so
Enable/Disable Front Panel USB

hn
Jo
Configure WiFi

by
All of these functions are available using the Platform connection through FX
19
Workbench.
20

Serial Shell connection to PC:

ht
rig

Micro USB jack on Front Panel of the FX80

y
op

Using terminal emulation software such as PuTTY

C

115,200 baud rate

8 Data bits/1 Stop bits/ No Parity/Xon-Xoff flow control
Day 1 Commissioning the FX Supervisory Controller

Using Serial Shell for an FX Supervisory Controller (Cont’d.)

Serial shell is also helpful also to watch activity inside the FX80.

c
In
Especially helpful to use Serial Shell during commissioning. Commissioning will be

,
ls
ro
complete when the login prompt returns.

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C
Day 1 Commissioning the FX Supervisory Controller

Backing Up a Station

Backup file contains complete configuration save as a dist file:

c
In
Compressed file

,
ls
ro
Entire Station Folder

t
on
C
Specific NRE config by platform including licenses and certificate

n
so
Pointers to the appropriate NRE core, JAVA VM, modules, OS

hn
Jo
May be installed into similar Platform using Distribution File Installer

by
Default backup file name will be backup_stationName_YYMMDD_HHMM.dist
19
20

Example backup_Longfellow_190304_0839.dist would be a backup distribution

ht

file created for a station named Longfellow at 8:39 am on March 4, 2019.

rig

The station directory may be extracted from backup by changing the

y
op

dist extension to zip and using compression software to extract.

C
Day 1 Commissioning the FX Supervisory Controller

Working with a Backup

After the backup process is complete, the DIST file can be:

c
In
Used to restore the entire image back to a similar platform,

,
ls
ro
e.g., FX80 to 80, FX70 to 70, etc.

t
on
Renamed as a .ZIP file and managed with Windows compressed file utilities

C
n
Extract the station from a different platform (i.e. using a DIST backup

so
hn
from an FX60E to put on an FX80 after the customer purchased an upgrade)

Jo
by
19
20
ht
yrig
op
C
C
op
yrig
ht
Adding BACnet® Devices Online

20
19
by
Jo
hn
so
n
C
on
tro
ls
, In
c
Day 1 Adding BACnet® Devices Online

Objectives

Welcome to the Adding BACnet® Devices Online lesson. Add Non-JCI

c
In
Devices and
After completing this lesson, you will be able to:

,
Points Online

ls
ro
Identify the steps to prepare an FX Supervisory Controller

t
on
to communicate via BACnet®

C
Add BACnet ® devices

n
so
Add BACnet ® points

hn
Add BACnet ® schedules

Jo
Remove any Add Control Logic for

by
Create a New Add Users
Unnecessary to the Station Devices Added
JCI Station
Controller Objects 19 Online

Copy Station from User Create Graphics for

Add Appropriate
Home to Secure Platform Set up Email Devices Added
20

Extensions
Daemon Home Online

Define JCI Commissioning the

ht

Controllers and Duplicate Typical FX Supervisory Backup the Station

Points Controllers Controller
y rig

Add Equipment and

Create Schedules Backup the Station Enterprise Setup
op

Spaces
C

Add Tags and Global Links Using Add Non-JCI Devices

Hierarchies Link Manager and Points Online

Add Any Other Define and Test

Objects to the Control Logic Add Appropriate
Controller Routines Extensions
Day 1 Adding BACnet® Devices Online

Overview of Adding BACnet® Devices

The Supervisory Controller must have some parameters altered in order to

c
In
communicate with BACnet® devices

,
ls
Assigning a network number to the type of BACnet ® communications

ro
t
(IP or MSTP)

on
C
Assigning a unique Object ID number to the Supervisory Controller

n
so
Enabling the appropriate port(s) (IP or MSTP)

hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Adding BACnet® Devices Online

Overview of Adding BACnet® Devices (Cont’d)

It is recommended to add BACnet® devices when online, and not via

c
In
FX Workbench

,
ls
Discovery will find BACnet® supported items, including:

t ro
on
BACnet® devices

C
Points

n
so
Schedules

hn
Jo
by
19
20
ht
yrig
op
C

Each BACnet® device needs a unique Object ID to the entire BAS system(s). If a BACnet® device
has a similar Object ID as another device, it will lead to problems even if the BACnet® device is
not mapped in.
Day 1 Adding BACnet® Devices Online

Preparing the Supervisory Controller for BACnet®

If using MSTP, additional settings must be made

c
In
Each MSTP Bus must have a unique Network Number

,
ls
rot
Identify the Port on the Station used for MSTP

on
C
Define the Baud Rate of the Port

n
so
(all devices on this bus must communicate at the same baud rate)

hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Adding BACnet® Devices Online

Completed Discover

After the discovery is complete, the list of BACnet® items will be displayed in the

c
In
Discovered window

,
ls
tro
on
C
n
so
hn
Jo
by
19
20
ht
yrig
op
C
Day 1 Adding BACnet® Devices Online

Summary of Adding BACnet® Devices

Johnson Controls MSTP devices may be discovered online then utilize the

c
In
FX Workbench Import Managers

,
ls
ro
Third party discovered devices can also auto discover points and schedules

t
on
C
n
so
hn
Jo
by
19
20
ht
rig
y
op
C