S4 Open Appliances V7

Steven E. Jones

The S4 Group Inc.

© 2012 The S4 Group, Inc. 1

© 2014 The S4 Group, Inc.

Components, Services, And Features Common To All S4 Open Appliances

3


Solutions are built around a software framework using a Lego®-like architecture with plug-in modules

Upstream Interfaces

Ethernet RS-232 RS-485 BACnet OPC Metasys® N2 SNMP XML/oBIX …

Auto Configure Scheduler JIT Compilers Administration

Virtual Devices Core Services

Universal Points

Routing Address Management Object Management

Metasys® N2

OPC BACnet MODbus DALI Siemens P1 …

Ethernet RS-232 RS-485 Ethernet Serial Server

Downstream Interfaces

5


Automatically detects all S4 Open Appliances

Configure the system Manage all S4 Open

Appliances on the network

Review detailed information on any field device

Test read and write to any point on any device

Rename, create, and delete points or devices

6


S4 Open: BACnet-N2 Router

S4 Open: OPC-N2 Router

9

10

Upstream Interfaces

Ethernet RS-232 RS-485 BACnet IP Metasys® N2



Universal Points

Routing Add ress Management Object Management


Ethernet RS-232 RS-485

Metasys® N2

S4 Open: BACnet-N2 Router

Upstream Interfaces

Ethernet RS-232 RS-485 OPC Metasys® N2



Universal Points




Metasys® N2

S4 Open: OPC-N2 Router


N2 Read, Write, Override, and Release supported All N2 sub-protocols and hardware types are fully

supported Upstream Interface – Facing the supervisory controller ◦ The N2 Router and BACnet (or OPC) interface are transparent to

the Metasys® supervisory controller ◦ N2 address translation

Downstream Interface – Facing the field devices Automatically detect N2 hardware type and loaded

application Automatically assign point mappings via Device Type

Template

11


BACnet IP The BACnet-N2 Router has a presence on the local

BACnet Network ◦ Device ID and Network can be set and easily modified via the

management console

Each discovered N2 device is published as a BACnet device under a virtual BACnet network

Virtual BACnet devices are assigned unique BACnet device IDs ◦ based on the N2 address and user specified offset

Standard BACnet Data Objects are Supported BACnet Priority Array is supported

12


The S4 Open: Management Console transparently creates a local OPC Proxy Server ◦ establishes a secure tunnel to the S4 Open Appliance

◦ established on the local machine during the Auto Detection process, or manual linking process, for S4 Open appliances

From the standpoint of an OPC client application, it is talking to a local OPC server ◦ there are no DCOM configuration or security issues

13


Ethernet Network

M3 / M5 Workstation

N30 / NCM

Supervisory Controller

VMA Device

(N2B

Protocol)

DX-9100

(System 91

Protocol)

TEC2145-2

(N2 Open

Protocol)

MS-MIG3120

(Metasys

Integrator)

TCS Basys

(VND Device)

N2 Protocol

(RS-485)


Benefit: Leverage existing infrastructure

Replace HMI with BACnet or OPC based solution

Merge legacy busses if desired

Manage both new and existing equipment from one interface

Always the starting point

16


Benefit: Cost of upgrading can be distributed over any length of time

Replace HMI with BACnet or OPC based solution

Gradually replace Legacy equipment with new solution

Seamlessly transition to new equipment on parallel MS/TP bus

Simply unplug N2 Router when upgrade is complete

17


The legacy supervisory controller continues its global control task forever

The S4 Open Appliance can act as an on-site agent for Cloud-based services ◦ Value added applications can be added to older buildings.

The N2 Router and BACnet (or OPC) Interface are transparent to Metasys®

Can be used as a stepping stone to eventually migrate to new technology

18


The legacy supervisory controller can be removed completely

If the new head end can perform the following: ◦ Occupied / Unoccupied schedules. The N2 field devices

normally do not include a time clock so they must rely on the head end for scheduling activities.

◦ Trending and logging activities. ◦ Global Variable support. For example, an outside air

temperature sensor on one N2 device may be shared with other N2 devices on the same N2 bus or with N2 devices on other Metasys® networks.

◦ Custom logic coded into the NCM or other supervisory controllers with GPL, JC Basic, or other languages.

When the legacy supervisory controller is removed, the S4 Open appliance will act as bus master.

19


Upstream Open Interface (BACnet or OPC?)

# of N2 devices per N2 bus

# of N2 buses per Metasys® supervisory controller

Election of Upstream N2 option enabling coexistence with the Metasys® supervisory controller

# of years of Software Assurance needed

Systems are sold as complete system bundles

Licensing is independent of the # of points

20


S4 Open: Software Assurance program for S4 Open Appliances Annual Subscription includes: ◦ All minor software or firmware enhancements and bug

fixes ◦ Device Type Template updates ◦ All major software or firmware releases ◦ Telephonic and eMail support ◦ Access to the secure support area of the S4 Group web site

One year of Software Assurance is included with each system purchase.

This program extends software support through the 2nd and subsequent years of product ownership.

21


Note 1: Utilizing the Upstream N2 port allows you keep legacy Metasys® supervisory controllers in place.

Note 2: Johnson Controls reserves N2 addresses 0, 254, and 255.

22

-S indicates that this is a complete system package. If absent, this indicates a bare-

bones appliance.

The number of Downstream N2 interfaces that are licensed. D1, D2, or D3

The absence or presence of an upstream N2 interface. U0 (absent) or U1 (present)

S4O-BACnet-N2-N016-D1-U0-S

Indicates the product family: S4O-BACnet-N2 or S4O-OPC-N2

The size of the N2 Router i.e. the number of N2 devices it is licensed to support. N016,

N032, N064, N128, or N256


S4 technology and recommended procedures are geared towards minimizing and mitigating risk inherent in the integration process.

Plan carefully

Assume nothing

Utilize lessons learned shared by other Integration Partners

Detect telltale signs early and take aggressive action.

Share your own experiences

24


Validate that the customer’s N2 Bus is within specifications with ◦ a digital volt meter, or

◦ The ComBus Quick Tester, or

◦ The S Squared S2USB485 and S2USB485DiagN2

Note any known problems identified in the Metasys® OWS

Run a HVAC Pro “devices” report

Schedule and complete any maintenance work before starting integration

25


Hand Held Device

Quickly tests the entire N2 system

Checks bus voltages indicating Pass/Fail

Counts all devices on the bus and identifies each by hardware type and N2 address

Works as a Master Controller to check the entire system or segments of the network

26


USB to RS-485 Converter

OBD (On-Board Diagnostics) analyze voltage of the RS485/N2 bus

S2USB485DiagN2 utility ◦ Checks bus voltages indicating Pass/Fail

◦ Confirms no other “Master” devices are active on the network

◦ Produces a simple report

Supports all Metasys® utilities HVAC Pro, GX9100, etc.

27


Using JCI’s Metasys ® Utilities, Identify ◦ What applications are loaded on existing N2 controllers ◦ Interlocks or Single Side Loops in N2 field devices ◦ Which points are relevant to bring in to the new head-end ◦ Which controllers are obsolete and require replacement (remove

risk)

Supervisory Logic and Services ◦ Custom logic in the supervisory controller ◦ Scheduling, trends, or other standard services

Metasys ® Utilities are available through distribution ◦ M-Tools package

HVAC Pro – N2 Open and VMA devices GX9100 – DX-9100

If you do not have Metasys® expertise ◦ Find an independent consultant ◦ DO NOT GUESS!

28


Integrated Lighting Controllers did not follow the N2 Open Spec and are very maintenance intensive. ◦ Replace them day one.

Expansion I/O cards in a NCU or NEU chassis depend on logic in the NCM. ◦ Replace them with current technology.

N2 devices operating in adverse environmental conditions might be a high risk. ◦ Replace them as soon as practical.

Remember: As soon as you touch the system you own it. ◦ In the building owner’s mind anything that happens on your

watch is your responsibility.

29


30


Used by Auto Configure Wizard ◦ Application Device Type

◦ Hardware Device Type

◦ Custom Device Type

◦ Probe For Points

Can be manually assigned

Field customizable

Stored in On-board Catalog

Off-line library available

Each N2 Device Type Template starts with a header section

Next is the Point Map section

Unique Device Concerns ◦ VND

◦ MIG

◦ System-91 Devices

◦ Point Multiplexer

33


Install S4 Open Management Console ◦ Free management utility provided by S4 that works as a

Microsoft Management Console snap-in

Load Device Type Templates (if needed) ◦ Template library on Support CD ◦ Custom templates

Run Auto Configure Wizard ◦ You may need to manually assign device type templates

after Wizard completes

34


Note: N2 devices will appear off-line to the supervisory controller during the auto configuration process.

35


Ethernet Network

M3 / M5 Workstation

N30 / NCM


VMA Device

(N2B

Protocol)

DX-9100

(System 91

Protocol)

TEC2145-2

(N2 Open

Protocol)

MS-MIG3120

(Metasys

Integrator)

TCS Basys

(VND Device)

N2 Protocol

(RS-485)

S4 Open

Appliance

Install the replacement OPC or

BACnet HMI / Head End

Replacement

Workstation


Develop Graphics for new HMI If the legacy head end is being removed you may

need to: ◦ Define Schedules ◦ Define Trends ◦ Replace any Global Variables ◦ Replace any supervisory controller logic

Be aware: the legacy head end and the replacement workstation may both try to control the same points! ◦ The last one in wins

37


Ethernet Network

M3 / M5 Workstation

N30 / NCM


VMA Device

(N2B

Protocol)

DX-9100

(System 91

Protocol)

TEC2145-2

(N2 Open

Protocol)

MS-MIG3120

(Metasys

Integrator)

TCS Basys

(VND Device)

N2 Protocol

(RS-485)

S4 Open

Appliance

Replacement

Workstation

Ethernet Network

VMA Device

(N2B

Protocol)

DX-9100

(System 91

Protocol)

TEC2145-2

(N2 Open

Protocol)

MS-MIG3120

(Metasys

Integrator)

TCS Basys

(VND Device)

N2 Protocol

(RS-485)

S4 Open

Appliance

Replacement

Workstation

Remove Legacy Metasys

Supervisory Controller and

Workstation

(Optional)


N2 Device and Point Discovery

Device Type Catalog

Device Type Template Assignment

(Modified) point lists

39


Manual Updating Configuration

Backup and Restore

Device Type Template Catalog

BACnet Features

BACnet names

IP Configuration

BBMD Configuration

Remote Reboot

Firmware Updates

40


Enables the Supervisory Controller on the upstream interface to participate in the Priority Array Mechanism

Supervisory controller originated transactions can operate at any of the 16 standard BACnet priorities

If Disabled, the supervisory controller operates at a priority higher than any BACnet client or application

Supervisory controller can operate at a priority lower than any BACnet client or operation ◦ can be put into read-only mode

42


Ethernet Network

VMA Device

(N2B

Protocol)

DX-9100

(System 91

Protocol)

TEC2145-2

(N2 Open

Protocol)

MS-MIG3120

(Metasys

Integrator)

TCS Basys

(VND Device)

N2 Protocol

(RS-485)

S4 Open

Appliance

Replacement

Workstation

VMA Device

(N2B

Protocol)

DX-9100

(System 91

Protocol)

TEC2145-2

(N2 Open

Protocol)

MS-MIG3120

(Metasys

Integrator)

TCS Basys

(VND Device)

M3 / M5

Workstation

N30 / NCM

Supervisory

Controller

Optonal


No two devices can have the same address, so… ◦ The N2 Router translates N2 addresses to resolve duplicate addresses ◦ Device on the lower bus keeps original address ◦ No need to manually change N2 device switches

44


Ethernet Network

VMA Device

(N2B

Protocol)

DX-9100

(System 91

Protocol)

TEC2145-2

(N2 Open

Protocol)

MS-MIG3120

(Metasys

Integrator)

TCS Basys

(VND Device)

N2 Protocol

(RS-485)

S4 Open

Appliance

Replacement

Workstation

ADAM

Serial Server

N2

Pro

toco

l

(ET

HE

RN

ET

)

N2

Pro

toco

l

(ET

HE

RN

ET

)

BA

Cn

et o

r O

PC

(ET

HE

RN

ET

)

Downstream N2 Connection Via

Advantech ADAM Ethernet Serial

Server

BA

Cn

et o

r OP

C

(ET

HE

RN

ET

)


Replacement for Metasys® Passthrough Mode

Implemented as a virtual COM port managed by the S4 Open Management Console

Limited to COM1 and COM2 because of M-Tools

Can be installed on any Windows PC running the Management Console

Licensed as part of the Metasys® Upstream N2 Option

Scheduled for the next firmware update

46


Points defined in Device Type Templates determine what is published to BACnet (or OPC)

Independent of Supervisory Controller database

Defines points in the addressed N2 device ◦ Supports N2 Open, N2B, and System-91 N2 variants

Defines Smart Data Points

Defines Engineering Units, Enumerations, and other point attributes

Today defined as a .CSV file, moving to XML

47


Virtual Points exist only in the N2 Router

Domain is the N2 device Defined in the Device

Type Template JC Basic compatible

scripts drive the value ◦ Triggered by BACnet Read or

Write Operations ◦ Enables emulation of other

manufacturer devices

Published to BACnet

48


Input: Metasys® Resource Files ◦ .PRN for N2 Open ASCs and VMAs ◦ .DMO for DX-9100

Output: ◦ Hardware device Type Template ◦ Application Device Type Template ◦ Custom Device Type Template ◦ Import into Device Types Catalog

Results may be manually customized Download from

http://www.thes4group.com/ClickOnce/S4FileConverter/publish.htm

Automatically updates upon startup

49




Resource file converter utility creates a custom Device Type Template for each device

N2 Open Override and Release functionality is emulated for the DX-9100

Points are published with accurate object types for each point

User friendly point names are included from the .DMO resource file.

Devices on XT expansion bus are fully supported.

50


51


The N2 bus operates at 9600 baud half-duplex ◦ This can’t be changed! ◦ The S4 Open appliance protects the N2 bus from becoming overwhelmed with requests from

high speed Ethernet interfaces ◦ The S4 Open appliance has built in performance and error monitoring capabilities

Installation problems ◦ Validate the N2 bus ◦ Repair any electrical or installation problems ◦ Make sure that the installation follows RS-485 standards. Repeaters may need to be replaced or

added to boost weak signals

Polling a large number of points at high frequency ◦ EMF interference and malfunctioning N2 devices, along with other factors, contribute to time-

out, data loss, and associated errors

These issues compound exponentially as the physical downstream Bus grows in size and age

JCI Engineering Guidelines ◦ N30 – 50 N2 devices ◦ NCM – 100 N2 devices ◦ DX-9100 and VMAs count as two

53


Split a single large N2 Bus into multiple downstream networks ◦ Each segment is brought into a single N2 Router on separate

downstream ports ◦ The new configuration will continue to look and behave like a

single N2 Bus to any upstream supervisory controllers ◦ This is all achieved without the need to implement any new logic

in the supervisory controller or extensive rewiring.

Split a single large N2 Bus into multiple independent segments ◦ Each segment is served with its own S4 Open Appliance ◦ From the point of view of the supervisory equipment, there are

now 2 separate N2 buses ◦ At the field level, communications are more resilient and better

error detection and correction can be performed

54


BACnet services can be de-selected to support special needs.

BACnet performance parameters can be adjusted

55

Example: Tuning system for Niagara installations Niagara expects instantaneous response from

BACnet IP Deselecting RPM / WPM support makes BACnet

IP chatty but foces Niagara to handle each BACnet property as a separate request

Eliminates points going stale in Niagara. Utilizing COV support, or enabling Caching

would achieve the same results


BACnet statistics are currently oriented towards the internal BACnet stack performance.

Enhancements are scheduled that will add integration performance statistics.

60


The Johnson Controls web site is a great resource for documentation on N2 devices and the Metasys® technology

CAS BACnet Explorer Read Tapes feature WireShark M-Tools

61


1.The N2 Router supports any N2 device that you will find on a N2 bus including N2 Open, VMA, Vendor Devices, Metasys Integrator, and Centaurus Integrator; direct Read, Write, Override, and Release transactions for any point limited only by the programming in the N2 device.

63


2. The Upstream Interface enables the co-existence with the Metasys® head end. This is a key feature in cases where minimal (or zero!) down time is mandated.

64


3.Auto discovery and configure wizard, facilitated by our robust library of Device Type Templates which predefine point mapping for each Metasys® device and application (custom templates can also be generated from Metasys® resource files) – all minimize the man hours required to integrate your N2 devices to BACnet.

65


4.Use all of the features of HVAC Pro and GX-9100, including uploading and downloading devices. The N2 Router can provide a replacement for the Metasys® “Passthrough” option for the configuration and commissioning utilities (in development).

66


5.In buildings with older, and potentially less reliable, N2 devices, the BACnet-N2 Router automatically resets N2 devices when multiple retries of an operation fail; it also logs the number of times that this action is taken.

67


6.The N2 Router products expose all N2 device points to the new head end, even those that JCI doesn’t normally expose to their operator workstation, such as tuning parameters.

68


7.The N2 Router products work independently of any database, priority, or security settings in the Metasys® supervisory controller.

69


8.The N2 Router products establish a very cost effective gateway to BACnet IP in the short term, quickly adding value and extending the life of legacy systems. Facilitates the migration away from Metasys® N2 devices in the longer term.

70


9. The N2 Router can force the N2 data stream from legacy Metasys® supervisory controllers (NCM, for instance) to participate in the BACnet priority array mechanism, giving the integrator complete control over which head end is commanding each point. No other product has this “supervisory controller as a BACnet client” capability.

71


10.Publish each N2 device as its own BACnet device within a virtual BACnet network.

72


Integration Boot Camp

Sales Boot Camp

Scheduled quarterly

On-demand sessions possible

Covers everything in the Live Demo in much more detail

Includes hands-on exercises in the S4 test lab

73


Example Integrations Using S4 Open Appliances

74


Problem ◦ A facility owner has a small, one

story, office building with 12 units.

◦ The building has a total of 10 N2 devices

◦ The N30 supervisory controller is no longer functioning, all N2 devices are in default operation mode.

Solution ◦ Replace N30 with S4 Open:

BACnet-N2 Router 16 ◦ Install new BACnet based HMI


Problem ◦ A school district needs to keep

track of energy usage across a diverse range of buildings

◦ A sizable percentage of the buildings are Metasys® based

◦ The district already uses an OPC-based trending solution for central reporting for some of its buildings

Solution ◦ Install an appropriately sized S4

Open: OPC-N2 Router in each building

◦ Connect each S4 Open: OPC-N2 Router to the central office via existing IT infrastructure

76


Problem ◦ A building operator wants to migrate from

Metasys® to a purely BACnet-based system ◦ Budget does not allow for a complete upgrade to

take place all at once

Solution ◦ Install one appropriately sized S4 Open:

BACnet-N2 Router for each legacy supervisory controller

◦ Install a new BACnet-based HMI, all data from the legacy Metasys® installation is immediately available to the new system

◦ Leave the legacy controller in place and allow it to continue communicating via the upstream interface on the S4 Open: BACnet-N2 Router

◦ Run a parallel BACnet field bus and replace N2 controllers with BACnet controllers as budget allows or as need arises

77


79


Protocol Plug-ins can be added to any S4 Open Appliances or Obermeier Software products as options.

Service Plug-ins can be added to any S4 Open Appliances or Obermeier Software products as options.

80


Obermeier Software is S4’s Development Partner

Obermeier Software’s SNMP OPC Server and OPC SNMP Enterprise Agent (eAgent) pre-dated the S4 Open Products

The Obermeier Products are migrating to the same architecture and framework as the S4 Open Appliances

Major difference: These are software only products

Protocol plug-ins will be compatible with both product lines

81


S4 Open: BACnet-EnOcean Gateway

S4 Open: BACnet-FLN Router

S4 Open: BACnet-Novar Router

S4 Open: OPC-Novar Router

S4 Open: OPC-FLN Router

SNMP BACnet-Server

BACnet OPC Server

Modbus SNMP eAgent

S4 Open: OPC-EnOcean Gateway

82


Core Services

• Logic engine to migrate Metasys® Global Variables (Data Distribution Daemon)

• Support for more serial server brands

• BACnet Scheduling

• BACnet Alarming

• Wherever our partners and the market take us

Downstream Protocols

• BACnet MS/TP

• Barber-Colman

• CSI

• DALI

• EnOcean

• Ethernet/IP

• Metasys® N1 (Ethernet)

• MODbus/TCP

• OPC

• PROFIbus

• Siemens P1

Upstream Protocols

• SNMP v1/v2/v3

• XML / oBIX

• Web Services

• Metasys® N2 - 3rd party (non-N2) devices published as N2 Vendor (VND) devices

• BACnet /WS

83


S4 Open: BACnet-EnOcean® Gateway S4 Open: OPC-EnOcean® Gateway

84

85

Upstream Interfaces

Ethernet RS-232 RS-485 BACnet IP



Universal Points



Ethernet RS-232

EnOcean

S4 Open: BACnet-EnOcean Gateway

Wireless

Upstream Interfaces

Ethernet RS-232 RS-485 OPC



Universal Points



Ethernet RS-232

EnOcean

S4 Open: OPC-EnOcean Gateway

Wireless


Two major components ◦ S4 Open: BACnet-EnOcean Router

◦ EnOcean Access Point

Zones of EnOcean wireless automation can now participate in BACnet Enterprise Solutions

86

BACnet EnOcean Gateway

EnOcean® Connector

Gateway Engine

EnOcean® NetworkBACnet Internetwork BACnet Connector

<Administration><Name Space Resolution><Data Integrity><Caching><Service Translation or Emulation>

<Object Management>

<Scheduling>

<Discovery><Routing>


Built on the S4 Open Appliance Framework Delivered as a turnkey network appliance, hosted

on an Industrial PC. EnOcean Access Points and EnOcean devices are

dynamically discovered and published to BACnet IP. Provides systems management services for the

EnOcean Access Points. Depending on the size of the facility, you may need

one per building, or one or more per floor. Provides the user interface for system configuration

and administration

87


Connect to the building infrastructure via Ethernet.

Support Power Over Ethernet (POE) or external power sources.

Every EnOcean device and point is fully accessible, supporting read and write operations as defined by the EnOcean device.

Inserted as a probe into each EnOcean Zone of Automation (hotel room, dorm room, etc.)

88


S4 Open: BACnet-EnOcean Gateway - Application Scenario

BACnet / IP EnOcean / Ethernet

BACnet HMI

S4 Open:BACnet-EnOcean Router

S4 Open: EnOcean Access Point

EnOcean Wireless Zone

Scenario :

For facilities with multiple zones of EnOcean devices, each S4 Open: EnOcean Access Point communicates with the S4 Open: BACnet-EnOcean Router over a standard Ethernet connection. The router then translates and publishes this data for use with any BACnet BAS.





No Wires. No Batteries. (No Limits)2.


MODEL EnOcean DEVICES

UPSTREAM EnOcean PORT

DOWNSTREAM EnOcean PORTS

BACnet-EnOcean Router-32 32 N/A 1

BACnet-EnOcean Router-64 64 N/A 1

BACnet-EnOcean Router-96

96 N/A 1

OPC-EnOcean Router-32 32 N/A 1



90

In addition to the EnOcean® Router you will need an appropriate number of EnOcean® Access Points.


S4 Open: BACnet-FLN Router S4 Open: OPC-FLN Router

91

92

Upstream Interfaces

Ethernet RS-232 RS-485 OPC Siemens® P1



Universal Points




Siemens® P1

S4 Open: BACnet-FLN Router

Upstream Interfaces

Ethernet RS-232 RS-485 OPC Siemens® P1



Universal Points




Siemens® P1

S4 Open: OPC-FLN Router


Built on the S4 Open Appliance Framework Delivered as a turnkey network appliance, hosted on an

Industrial PC. Standard vendor tools used to configure FLN devices on

each FLN bus. All Apogee® FLN devices supported, including 3rd party

devices supporting the P1 protocol. BACnet device and point level discovery. Every FLN point is fully accessible, supporting read,

write, override, and release operations as defined by the FLN device.

Easily upgradeable via protocol and application plug-ins for expanded functionality.

93


Modular

Building

Controller

(MBC)

Modular

Equipment

Controller

(MEC)

FLN Downstream

P1 Protocol

(RS-485)

Ethernet Network

TEC

Controller

(P1 Protocol)

TEC

Controller

(P1 Protocol)

TEC

Controller

(P1 Protocol)

TEC

Controller

(P1 Protocol)

Other FLN

Controller

(P1 Protocol)

Replacement Workstation

and BACnet Controllers

Apogee Insight

Workstation

BACnet IP

Protocol S4 Open:

BACnet-FLN RouterField Level

Network

Controller

(FLNC)FLN Upstream

P1 Protocol

(RS-485)

Building Level Network

(All Components become

Optional)

Building Level Network

(P2 Protocol)


MODEL FLN DEVICES UPSTREAM FLN PORT DOWNSTREAM FLN PORTS

BACnet-FLN Router-32 32 Optional 1



OPC-FLN Router-32 32 Optional 1



95

Utilizing the Upstream FLN port allows you keep legacy Siemens Apogee building level controllers and Insight workstation in place.


S4 Open: BACnet-Novar Router S4 Open: OPC-Novar Router

96

97

Upstream Interfaces

Ethernet RS-232 RS-485 BACnet IP Novar Logic One



Universal Points




Novar Logic One

S4 Open: BACnet-Novar Router

Upstream Interfaces

Ethernet RS-232 RS-485 OPC Novar Logic One



Universal Points




Novar Logic One

S4 Open: OPC-Novar Router


Built on the S4 Open Appliance Framework Delivered as a turnkey network appliance, hosted on an Industrial

PC. Standard vendor tools used to configure Secondary Control Unit

devices on each NovarNet bus. All Novar SCU devices supported, including 3rd party devices

supporting the NovarNet protocol. BACnet device and point level discovery. Every SCU point is fully accessible, supporting read, write,

override, and release operations as defined by the field device. Variable speeds supported for SCUs on NovarNet bus SCU Program Download supported when Executive controller is

removed Easily upgradeable via protocol and application plug-ins for

expanded functionality.

98


iScope Workstation

Savvy Master

Controller

Novar SCU

Hawki

Novar SCU

IOM/2

Novar SCU

VAV

Novar SCU

HPC+

Novar SCU

….

NovarNet

Downstream Protocol

(RS-485)

S4 Open:

BACnet-NovarNet

Router

Typical Novar Integration

BACnet IP

(ETHERNET)

Dial Up

Network

NovarNet

Upstream Protocol

(RS-485)

BA

Cn

et IP

(ET

HE

RN

ET

)

BA

Cn

et IP

(ET

HE

RN

ET

)

Building Level

Controller

Ethernet Network

Executive Level

Network

(All Components

become Optional)

New Head End


MODEL SCU DEVICES UPSTREAM NovarNet

PORT DOWNSTREAM NovarNet PORTS

BACnet-Novar Router-16 16 Optional 1



OPC-Novar Router-16 16 Optional 1



10

0

Utilizing the Upstream NovarNet port allows you keep legacy Novar Executive controllers and iScope workstation in place.

S4 Open Appliances V7

Documents

Transcript of S4 Open Appliances V7