Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
INTRODUCTION.......................................................................................... 3
PREREQUISITES ......................................................................................... 4
Introduction
The Apogee Carrier Dataport Driver is a read only driver to devices on the Carrier
CCN network via the Carrier Dataport Interface.
The Apogee Carrier Dataport Driver gathers data from the Carrier Dataport
interface and makes it available for use within the Apogee system. This is achieved
by defining the data gathered from the Carrier Dataport Interface as standard
systems point information.
Supported
Configuration
The Apogee Carrier Dataport Driver enables the Siemens Apogee System 600 to
communicate with Carrier CCN nodes via the Carrier Dataport Interface. Read only
functionality is supported. Commanding of parameters on the CCN network is not
supported by this driver.
Supported
Points
The current version (ver. 1.1) of the Apogee Carrier Dataport Driver supports the
following functions:
Monitoring • Monitoring of all points from up to 15 nodes on the Carrier CCN network.
The Carrier Dataport supports a total maximum of 900 points. Therefore,
the Carrier Dataport driver also supports up to this number of points.
Control • The Carrier Dataport Interface only supports monitoring of devices on the
CCN network. Commanding is not supported.
Year 2000
Version 1.1 of the Apogee Carrier Dataport Driver is year 2000 compliant, year
2000 compliant issues regarding the Carrier Dataport products should be checked
with a Carrier representative.
Prerequisites
8. <RETURN>.
9. Command successful
NOTE: The Apogee Carrier Dataport Driver only uses the FLN 1 port. FLN 2
and 3 ports are redundant.
M-Bus Configuration:
The Apogee Carrier Dataport Driver does not control any of the Point Termination
Modules (PTMs).
CAUTION:
Only one Controller Module/Driver per cabinet can have the M-Bus
enabled. If the Apogee Carrier Dataport Driver Module is the only
controller present within the MBC enclosure, then the M-Bus may be
enabled.
7. Command successful
8. <RETURN>.
The Carrier Dataport Driver will coldstart, completing the node address
configuration.
Overview:
The communication standard for the Carrier Dataport Interface is ASCII characters
transmitted via RS-232 at 9600 bps with 8 data bits, 1 stop bit and no parity. The
communication standard for the FLN1 port of the Carrier Dataport Driver is ASCII
characters via RS-485.
The physical connector of the communication port of the TI-2 is via a 25DB male
connector. The physical connector of the Carrier Dataport Interface is via a 25DB
male connector to the RS-232 port. Refer to figure 2 for wiring termination details.
TI-II
Apogee panel with
the Carrier Dataport COMM 2 (RS-232)
Driver DB 25
SCU panel
Apogee Insight
Tx (3) Tx (3)
Rx (2) Rx (2)
Database Properties
Required Control
Points.
Control points must be created for the Carrier Dataport Driver to map data from
CCN nodes into S600/Apogee memory addresses. The property names are
optional, noting that the point type should be LAO and created at Point address 00
of each drop. The Initial value should contain the CCN node address (1-15), using a
Slope of 1.0 and an intercept of 0.0. CCN node addresses supported by the Carrier
Dataport are 1-15. The COV should be equal to the Slope. This will map data from
the CCN node address whose number equals the initial value of the control point
into the drop corresponding to the control point. If the CCN node contains more than
99 points, the next drop will be used to map the rest of these points.
• FLN number = 1
• DROP number = 01
• POINT number = 00
This will map data from CCN node address 1 into FLN1, Drop01, Points 01-99 of
the Carrier Dataport Driver. If there are more than 99 parameters for this particular
CCN node, FLN1, Drop02, Points 00-99 will be used to map the rest of these
parameters.
2. >Log, Display, Command, Edit, Operation, Monitor, Alarm, Trend, Quit? (E)
7. >Descriptor : Node.Addr----
Standard Database
Points
The following is an outline of how to create data points within the Carrier Dataport
Driver. Because the Carrier CCN Dataport is user configurable, consult the Carrier
representative for the point map for each CCN node being used.
Adding a point to monitor a unit status received from the Carrier Dataport Carrier
Dataport Interface. Example:
2. >Log, Display, Command, Edit, Operation, Monitor, Alarm, Trend, Quit? (E)
7. >Descriptor : Status-----
Adding a point to monitor a temperature setpoint received from the Carrier Dataport
Interface. Example:
2. >Log, Display, Command, Edit, Operation, Monitor, Alarm, Trend, Quit? (E)
The Carrier Dataport Driver supports both LAI and LDI point types for the reading of
data points. Any other point types created, other than those created for diagnostic or
control purposes will be created with an error type status of (E253).
The Carrier Dataport Driver utilises 94 drops allocated for point mapping purposes.
• LAI, LDI – Monitor points. All LAI points to have a Slope of 1, Intercept
of 0 and COV of 1.
• LAO – Control points for CCN node addresses. (Point 00 of each drop
only)
If a point is created beyond the mapping region specified, the point will be created with
an error type status of (E253), rendering the point unusable in a priority failed (*F*)
state.
Database
Download
1. Verify that the Carrier Dataport Carrier Dataport Interface is operating correctly,
by contacting a Carrier representative to ensure that the Carrier Dataport
System has been installed and certified, and that it is operating according to
their procedures.
2. Cold Start the Carrier Dataport Driver and download the database
3. If for any period of time communication is lost, database points will enter a
Failed *F* state, on communications being re-established the Carrier Dataport
Driver will automatically unfail all database points and continue with normal
communications.
Then communications will not be established until the Carrier Dataport Driver is
Made Ready.
Communications
Verifying
communications:
1. Verify that the STATUS LED on the front of the Carrier Dataport Driver is
blinking approximately once a second. If not, the Carrier Dataport Driver is
malfunctioning.
2. The FLN 1 TX and RX LEDs on the Carrier Dataport Driver flash together while
the Carrier Dataport Driver transmits data. Then the RX LED on the Carrier
Dataport Driver flashes while the Carrier Dataport Driver receives data from the
Carrier Dataport Interface. This sequence repeats in quick succession.
3. Verify that the Carrier Dataport Driver is communicating with the Carrier
Dataport Interface as with step 2.
Display a Point Log and verify that the Carrier Dataport Driver points are entered
and that they read the correct information from the Carrier Dataport Interface.
Make sure the points are normal (-N-). If the points do not contain the expected
information:
3. If these checks do not uncover the problem, refer to the Diagnostic and
troubleshooting document.
On verifying communication.
1. Verify that all lines of PPCL execute as intended. If there are problems, refer to
the Diagnostic and Troubleshooting document.
Commission
the System
Consult as needed with the building engineer to make sure Carrier Dataport Driver
is providing accurate information and performing the intended functions. In
particular, verify that:
If the above tests do not check out, refer to the Diagnostic and troubleshooting
document.
Point Maps
Carrier Chiller 19XR Generic Point Map
Application Notes:
• Chiller 1 or ‘A’: Create LAO point at FLN1, Drop1, Point 00. Map data points
into FLN1, Drop1, Points 01-99 and FLN1, Drop2, Points 00-26.
• Chiller 2 or ‘B’: Create LAO point at FLN1, Drop3, Point 00. Map data points
into FLN1, Drop3, Points 01-99 and FLN1, Drop4, Points 00-26.
• Chiller 3 or ‘C’: Create LAO point at FLN1, Drop5, Point 00. Map data points
into FLN1, Drop5, Points 01-99 and FLN1, Drop6, Points 00-26.
• Chiller 4 or ‘D’: Create LAO point at FLN1, Drop7, Point 00. Map data points
into FLN1, Drop7, Points 01-99 and FLN1, Drop8, Points 00-26.
Release notice
______________________________________ ___________________
Wayne Moules
Manager, Service Marketing Date
(PRODUCT MANAGER )
______________________________________ ___________________
Paul Kendall
Technical Writer Date
(AUTHOR)
______________________________________ ___________________
Wayne Moules
Engineering Manager Date
(TECHNICAL REVIEWER)