CCN DATAPORT - dms.hvacpartners.comdms.hvacpartners.com/docs/1000/Public/08/808-619.pdf · 1 The...
Transcript of CCN DATAPORT - dms.hvacpartners.comdms.hvacpartners.com/docs/1000/Public/08/808-619.pdf · 1 The...
This document is the property of Carrier Corporation and is delivered on the express condition that it is not to be disclosed,reproduced in whole or in part, or used for manufacture by anyone other than Carrier Corporation without its written consent, andthat no right is granted to disclose or so use any information contained in said document.
Carrier reserves the right to change or modify the information or product described without prior notice and without incurring anyliability.
© 2002, Carrier Corporation Printed in U.S.A. 808-619 1/90
Overview and ConfigurationManual
Introduction ............................................................... 1General Information ................................................ 1About this Manual ................................................... 2
Operating Characteristics ......................................... 3CIO Module ............................................................ 3DATAPORT Functions ........................................... 5
Configuration and Maintenance Screens .............. 13Configuration Decisions ....................................... 13Maintenance Decisions ......................................... 17
Off-Network Control ............................................... 21Commands ............................................................ 21Error Codes ........................................................... 25
CCN DATAPORT
ii
1
The CCN DATAPORT made by Carrier Corporation is an interfacethrough which certain data from one or more devices connected to aCCN Communications Bus can be transmitted to a non-CCN device.It is for use in applications that require the transfer of status infor-mation from a CCN controller to a device, not manufactured byCarrier, that cannot be connected to a CCN Communications Bus.A DATAPORT is a read-only device. It does not convey data fromthe off-network, non-CCN device onto the CCN bus.
This manual describes the purpose, function, and operation of theDATAPORT. It includes descriptions of the DATAPORT’s physi-cal characteristics, the screen displays by which an operator interactswith the DATAPORT from a Building Supervisor or CCN ServiceTool, and the command and error codes by which an off-networkinteracts with the DATAPORT.
The data that can be transmitted through a DATAPORT is mainte-nance and operating information that is contained in a CCNcontroller’s Point Screen. The DATAPORT reads the data from thecontroller, converts it into ASCII characters, and transmits it to theoff-network device. The off-network device receiving the data maybe either a non-Carrier controller that employs the data as input to acontrol routine, or a personal computer.
The CCN controllers from which the DATAPORT can transmit datahave to be specified in the DATAPORT’s configuration table, whichis accessible by means of a Building Supervisor or CCN ServiceTool. The actual transmission of data is controlled by commandssent form the off-network device that is to receive the data. ABuilding Supervisor or CCN Service Tool can also display aDATAPORT maintenance screen that shows information about howthe DATAPORT is operating.
The controllers from which the DATAPORT can transmit PointScreen data include PICs and CIO Module-based devices such as theCPOC and the 32MP Gateway. The DATAPORT cannot transmitdata from a FID.
GeneralInformation
Introduction
2
This manual is intended for use by an operator who has access toboth the off-network device that is to receive data from theDATAPORT and the CCN system in which the DATAPORT isinstalled. It is divided into four sections:
• Introduction contains brief descriptions of the DATAPORT andthe Manual.
• Operating Characteristics describes the CIO Module in whichthe DATAPORT runs and the functions that the DATAPORTperforms.
• Configuration and Maintenance Screens describes the deci-sions that appear on the screens an operator can access from aCCN Building Supervisor or Service Tool to configure aDATAPORT or monitor its operation.
• Off-Network Control describes the commands that be sent fromthe off-network device to the DATAPORT to control its opera-tion and the error messages that the DATAPORT can send to theoff-network device when a command cannot be carried out.
About This Manual
3
A DATAPORT consists of a CIO Module equipped with specializedsoftware to perform the tasks required of it. Those tasks consist ofrequesting Point Screen data from the appropriate CCN controllerson the CCN Communications Bus, translating the data into ASCIIcharacters, and outputting those characters through the CIOModule’s RS-232 COMM2 connector.
The CIO Module is shown in Figure 1. When used as aDATAPORT, the CIO Module employs the 4-pin, Phoenix-typeconnector labeled COMM1 and the 25-pin, D-shell connectorlabeled COMM2.
CIO Module
32
1
12
34
12
34
32
1
PWR2PWR1
COMM 1
COMM 2
Carrier
ELEMENT #
(HEXADECIMAL)
XX
S1
S2
Figure 1CIOModule
OperatingCharacteristics
4
COMM1 is the DATAPORT’s connection to a CCN Communica-tion Bus. The bus, which uses RS-485 signaling, may operate at1200, 2400, 4800, or 9600 bits per second. It typically operates at9600. A DATAPORT may reside on any CCN CommunicationsBus, 0-239, and may be assigned any system element number, 1-239. The DATAPORT’s default address is bus 0, system elementnumber 110. The CCN Network Configuration Tool (NCT) may beused to change the DATAPORT’s bus and element numbers and theoperating rate for COMM1.
COMM2 is the DATAPORT’s connection to the off-network devicethat is to receive the ASCII characters. It accepts and transmits RS-232 signals at a rate of 1200, 2400, 4800, or 9600 bits per second.The operating rate of COMM2 is set from a Building supervisor or aService Tool by means of a configuration decision in theDATAPORT. The DATAPORT compensates for differencesbetween the operating rates of COMM1 and COMM2.
The cable between the off-network device and COMM2 of theDATAPORT can be up to 50 feet in length.
Only four pins of the COMM2 connector are used in theDATAPORT’s RS-232 communications:
• Pin 1 - protective ground• Pin 2 - transmit data• Pin 3 - receive data• Pin 7 - signal ground
The DATAPORT employs software control to regulate the transmis-sion of data through COMM2, so RS-232 control signals are notrequired on the other pins of the connector.
5
A DATAPORT can be configured with the addresses of up to 15CCN controllers. The user configures the DATAPORT by enteringeach controller’s bus number and system element number in theDATAPORT’s configuration table.
The DATAPORT maintains a database for its configured control-lers that contains the following information (static data) for eachpoint in each controller.
• Point name (up to eight alphanumeric characters)• Units ( a three-digit code that identifies the unit of measure)• Description (up to 24 alphanumeric characters)
There are three conditions that cause the DATAPORT to acquirenew static data for its database. First, two minutes after theDATAPORT is powered on, it will poll its configured devices forstatic data. Second, it will poll automatically when a changedconfiguration table is downloaded to it. Third, it will poll in re-sponse to a Read Configuration command from the off-networkdevice.
The DATAPORT database can contain entries for up to 900 points,which works out to 60 points in each of 15 controllers. If control-lers are configured that contain more than 60 points apiece, there isan effective reduction in the number of controllers that theDATAPORT can support.
For example, if controllers are configured that contain 100 pointsapiece, all 15 sets of bus and system element numbers may still beentered in the configuration table, but only the first nine controllerswill be accessible to a Send Controller Data command. If the off-network device were to command the DATAPORT to send datafrom any of the last six configured controllers, the DATAPORTwould respond with an error message of 4, which means DatabaseFull.
The CCN controllers are associated by the order in which they areconfigured with single letter ASCII command A through O (ineither upper or lower case). A is the Send Controller Data for
DATAPORTFunctions
6
Controller 1 command and O is the Send Controller Data for Con-troller 15 command. Each Send Controller Data command instructsthe DATAPORT to perform the following functions:
• read the dynamic data portion of a Point list display (value andstatus for each point) from the controller that corresponds to thecommand letter
• translate the data into ASCII characters• format the characters together with the appropriate static data
stored in the DATAPORT database• transmit the result through COMM2
When commanded to transmit a CCN controller’s point data, theDATAPORT first transmits an ASCII Form Feed character. Thenfor each point in the requested controller the DATAPORT transmitsa line of data in the following format:
Name Value Units Status Description (Carriage Return)
Single spaces are transmitted to separate Name, Value, Units,Status, and Description. A second Carriage Return is transmittedfollowing the last point in the controller. The Carriage Returncharacters transmitted by the DATAPORT do not provide line feed.
The point name consists of up to 8 alphanumeric characters. Thisname appears in the rightmost column on a Building SupervisorPoints Screen.
The point value may consist of up to ten characters. If the value isanalog, it is presented in the same format in which it would appearon a Building Supervisor screen, that is, with the same number ofdigits and decimal point placement. If an analog point value isoutside the range that can be represented by ten characters, theDATAPORT will transmit ten asterisks in place of the value. If thepoint value is discrete, it is presented as a 1 or a 0.
The units designator transmitted through the DATAPORT takes theform of a three digit number. Table 1 explains how the numberscorrespond to units of measure.
7
Status is also transmitted as a three digit number. Each statusnumber represents a unique combination of an error condition and aforce condition. Table 2 defines how to decode transmitted statusnumbers into error and force codes. Simply locate the displayedstatus number in the table. The table’s columns correspond to errorconditions and its rows correspond to force conditions. The twolists below the table describe the conditions.
The point description consists of up to 24 alphanumeric characters.Transmission of the description field can be suppressed by a com-mand from the off-network device.
8
Table 1Three DigitUnitsCodes
Customary US Units Metric Units
000 no units 256 no units001 degrees F 257 degrees C002 degrees F 258 degrees C003 percent004 inches of water 260 Pascals005 milliamps006 delta degrees F 262 delta degrees C007 degrees F 263 degrees C008 delta degrees F 264 delta degrees C010 Volts011 degrees F 267 degrees C
013 percent014 inches of water 270 Pascals015 milliamps016 delta degrees F 272 delta degrees C017 degrees F 273 degrees C018 delta degrees F 274 delta degrees C
020 pounds per square inch 276 kiloPascals
032 gallons per minute 288 liters per minute033 gallons per hour 289 liter per hour034 thousands of gallons per minute 290 cubic meters per minute035 thousands of gallons per hour 291 cubic meters per hour036 pounds per square inch, gauge 292 kiloPascals037 pounds per hour 293 kilograms per hour038 thousands of pounds per hour039 BTUs per hour 295 kilowatt hours040 thousands of BTUs 296 kilowatts
(continued)
9
Customary US Units Metric Units
041 inches of water 297 millimeters of water042 inches of mercury 298 millimeters of mercury043 kilowatt hours 299 kilowatt hours044 kilowatts 300 kilowatts045 degrees F 301 degrees C046 percent relative humidity 302 percent relative humidity047 amps 303 amps048 volts 304 volts049 cubic feet per minute 305 cubic meters per minute050 cubic feet per hour 306 cubic meters per hour051 feet per minute 307 meters per second052 thousands of cubic feet
per minute053 thousands of cubic feet
per hour054 tons 310 tons055 tons per hour 311 tons per hour056 revolutions per minute 312 revolutions per hour057 percent open 313 percent open058 hours 314 hours059 gallons 315 liters
(Continued)
Table 1(Continued)Three DigitUnitsCodes
10
Table 1(Continued)Three DigitUnitsCodes
Units Common to Customary US and Metric
064 on/off input065 off/on input066 input pulses on067 input pulses off068 seconds069 normal/alarm070 Hz
080 minutes081 hours082 revolutions per minute
124 clock
126 ASCII
128 no units
133 milliamp
137 pounds per square inch138 volts
144 kilowatts145 kilowatt hours/pulse146 pulses
192 on/off output193 off/on output194 pulsed on output195 pulsed off output
208 steps
254 ASCII
11
Force Error ConditionsConditions A B C D E F
No Force 000 001 002 003 004 005Fire 016 017 018 019 020 021
Safety 032 033 034 035 036 037Service Tool 048 049 050 051 052 053
Supervisor 064 065 066 067 068 069Monitor 080 081 082 083 084 085
Minimum-off 096 097 098 099 100 101Control 112 113 114 115 116 117
BEST 128 129 130 131 132 133Temp Override 144 145 146 147 148 149
Loadshed 160 161 162 163 164 165
Error Conditions:A = no errorB = hardware or communications errorC = software errorD = low alarm limit exceeded (analog point),
or point in alarm (discrete point)E = high alarm limit exceededF = unconfigured point (VVT Gateway only)
Force Conditions:No Force
Fire = forced by fire alarm equipmentSafety = forced by internal safety override
Service Tool = forced by CCN Service ToolSupervisor = forced by local Building Supervisor
Monitor = forced by remote Building SupervisorMinimum-off = forced by minimum off time requirement
Control = forced by System Software OptionBEST = forced by BEST program
Temp Override = forced by temperature overrideLoadshed = forced by Loadshed System Software Option
Table 2Error andForceConditionsRepresentedby theThree-DigitStatusDisplay
12
13
The user configures the DATAPORT by means of decisions on aconfiguration table screen reached through the Carrier Controlsfunction of a CCN Building Supervisor or Service Tool. The con-figuration table is identified by the name DATAPORTCONFIG.More detailed information on working with the Building Supervisoror the Service Tool can be found in their respective manuals.
The DATAPORT Configuration Screen is shown on the next pagein Figure 2. The figure is followed by explanations of the decisionsthat appear on the screen.
ConfigurationDecisions
ConfigurationandMaintenanceScreens
14
Save Upload Download Copy Edit QuitModify data; Press F2 to activate menu.
MODIFY CONTROLLER CONFIGDTP_01S - #4
POINT
010000000000000000000000000000110
STATUS
Device 1 Bus NumberDevice 1 Element NumberDevice 2 Bus NumberDevice 2 Element NumberDevice 3 Bus NumberDevice 3 Element NumberDevice 4 Bus NumberDevice 4 Element NumberDevice 5 Bus NumberDevice 5 Element NumberDevice 6 Bus NumberDevice 6 Element NumberDevice 7 Bus NumberDevice 7 Element NumberDevice 8 Bus NumberDevice 8 Element NumberDevice 9 Bus NumberDevice 9 Element NumberDevice 10 Bus NumberDevice 10 Element NumberDevice 11 Bus NumberDevice 11 Element NumberDevice 12 Bus NumberDevice 12 Element NumberDevice 13 Bus NumberDevice 13 Element NumberDevice 14 Bus NumberDevice 14 Element NumberDevice 15 Bus NumberDevice 15 Element NumberPort 2 Baud RateUpdate Period
DESCRIPTION
Carrier Controls
DEV1BUSDEV1ADDRDEV2BUSDEV2ADDRDEV3BUSDEV3ADDRDEV4BUSDEV4ADDRDEV5BUSDEV5ADDRDEV6BUSDEV6ADDRDEV7BUSDEV7ADDRDEV8BUSDEV8ADDRDEV9BUSDEV9ADDRDEV10BUSDEV10ADDRDEV11BUSDEV11ADDRDEV12BUSDEV12ADDRDEV13BUSDEV13ADDRDEV14BUSDEV14ADDRDEV15BUSDEV15ADDRP2BAUDUPDATPER
Figure 2DATAPORTConfigurationScreen
15
Each of these decisions can be used to input the bus number of acontroller that can supply data to the DATAPORT.
Allowable Entries
0 through 239 = bus numbers
Default Value
0
Each of these decisions can be used to input the system elementnumber of a controller that can supply data on the DATAPORT.
Allowable Entries
0 = no controller configured1 through 239 = system element numbers
Default Value
1 for Device #10 for Devices #2 through 15
This decision is used to configure the operating rate, in bits persecond, of the COMM2 connector through which the DATAPORTcommunicates with the off-network device.
Allowable Entries
1 = 9600 bps2 = 4800 bps3 = 2400 bps4 = 1200 bps
Default Value
1
Device 1 Bus Numberthrough Device 15Bus Number
Device 1 ElementNumber throughDevice 15 ElementNumber
Port 2 Baud Rate
16
The value entered in this decision specifies how frequently data is tobe sent to the off-network device in response to a Send Data Peri-odically command.
Allowable Entries
10 through 600 (seconds)
Default Value
10
Update Period
17
A Building Supervisor or Service Tool can display a maintenancetable screen that shows the current state of the DATAPORT’sactivities. The table is shown below in Figure 3. Explanations ofthe table’s maintenance decisions follow the figure.
Detailed information on working with the Building Supervisor orthe Service Tool can be found in their respective manuals.
MaintenanceDecisions
Figure 3MaintenanceScreen
LIST POINT COMMANDS
Carrier Controls
DTP_01S - #4
Press Escape to end Maintenance Display
POINTSTATUSDESCRIPTION
Current Device NumberDevice Update StateInclude Description
00
Enable
DEV_NUMUPDSTATEINCDESC
18
This maintenance decision displays a number in the range from 0 to15. The numbers from 1 to 15 correspond to the CCN controllersthat can be configured in the DATAPORT. The number 0 repre-sents an idle condition under certain circumstances.
If the DATAPORT is currently transmitting data in response toeither a Send Controller Data command or a Send Data Periodicallycommand, the number on display indicates the controller fromwhich data is being sent.
If the DATAPORT is not transmitting data because it is in betweenperiodic transmissions or because it has completed a one shottransmission, the number on display indicates the last controllerfrom which data was sent. If the DATAPORT is not transmittingdata because the last command sent to it was Stop Sending (EscapeKey), 0 is displayed.
Display Values
0 = transmission stopped1 through 15
This maintenance decision indicates whether or not theDATAPORT is currently transmitting data, and if it is, whether thetransmission is a one-shot transmission in response to a Send Con-troller Data command or an on-going, periodic transmission inresponse to a Send Data Periodically command.
Display Values
0 = idle1 = one shot transmission in progress2= periodic transmissions in progress
Current DeviceNumber
Device Update State
19
This maintenance dicision indicates whether or not the DATAPORThas been commanded to include point descriptions in the data ittransmits to the off-network device.
Display Values
Disable = descriptions not being transmittedEnable = descriptions being transmitted
Include Description
20
21
Off-NetworkControlCommands
There are 22 commands that can be sent from the off-networkdevice to the DATAPORT. Each command may be sent in the formof one ASCII character or its hexadecimal numeric equivalent.
The 15 Send Controller Data commands, one for each controller thatcan be configured in the DATAPORT, are each represented by asingle ASCII letter. If a keyboard is used to input commands fromthe off-network device to the DATAPORT, the letter commandsmay be sent in either upper or lower case. ASCII code representsthe upper and lower case forms of a letter with different hexadeci-mal values. If commands are programmed into the off-networkdevice as hexadecimal values, the hexadecimal equivalent of eitherupper or lower case may be used.
The other seven commands are represented by ASCII control char-acters. One of those is the character generated by pressing akeyboard’s Escape (ESC) key. The remaining six are characters thatare generated by simultaneously pressing the keyboard’s Controlkey and a letter key. The hexadecimal equivalents of the Control/letter combinations are the same for both upper and lower caseletters.
In the list that appears on the next page, each DATAPORT com-mand is identified by name, by the key or combination of keys usedto input the command at a keyboard, and by the hexadecimalequivalent of the character.
22
Controller 1 = A (41H) or a (61H)Controller 2 = B (42H) or b (62H)Controller 3 = C (43H) or c (63H)Controller 4 = D (44H) or d (64H)Controller 5 = E (45H) or e (65H)Controller 6 = F (46H) or f (66H)Controller 7 = G (47H) or g (67H)Controller 8 = H (48H) or h (68H)Controller 9 = I (49H) or i (69H)Controller 10 = J (4AH) or j (6AH)Controller 11 = K (4BH) or k (6BH)Controller 12 = L (4CH) or l (6CH)Controller 13 = M (4DH) or m (6DH)Controller 14 = N (4EH) or n (6EH)Controller 15 = O (4FH) or o (6FH)
Each Send Controller Data command is a one-shotinstruction for the DATAPORT to get point data fromthe specified controller and transmit it to the off-networkdevice. Transmission of a controller’s point data maymade to pause and resume by an XOFF command and anXON command, or stopped completely by a Stop Send-ing command. If the DATAPORT receives a SendController Data command while it is already transmittingdata, it will immediately stop the transmission inprogress and respond to the newly received command.
Control/P or Control/p (10H)
This command instructs the DATAPORT to periodicallyupdate and transmit point data from the controller thatwas specified by the most recent Send Controller Datacommand. The Update Period configuration decisiondetermines how frequently the transmissions occur.Transmissions begun by this command may be made topause and resume by the XOFF and XON commands.Transmissions may be stopped completely by a StopSending command, after which the DATAPORT willremain inactive until a new Send Controller Data or Send
Send Controller DataCommands
Send Data Periodically
23
Data Periodically command is issued. If theDATAPORT receives a Send Controller Data commandwhile periodic transmissions are underway, it will imme-diately stop the transmission in progress and respond tothe newly received command.
Escape (1BH)
This command instructs the DATAPORT to stop sendingdata to the off-network device. The DATAPORT stopsat whatever point it has reached when the command isreceived and does not complete transmitting data fromany remaining points in the controller. Once this com-mand has been issued, the DATAPORT will not transmitany further data until it receives a new Send ControllerData or Send Data Periodically command.
Control/S or Control/s (13H)
This command instructs the DATAPORT to pause insending data to the off-network device. TheDATAPORT pauses at whatever point it has reachedwhen the command is received and does not complete itstransmission until it receives an XON command. Oncean XOFF command is issued, the DATAPORT will notrecognize any command except XON.
XOFF
Stop Sending
24
Control/Q or Control/q (11H)
This command instructs the DATAPORT to resumesending data to the off-network device after an XOFFcommand has made it pause. Transmission resumesfrom the point it had reached when the XOFF wasreceived. This is the only command that a DATAPORTwill recognize after it receives an XOFF command.
Control/N or Control/n (0EH)
This command instructs the DATAPORT not to includethe 24 character point descriptions in the data it trans-mits. Once this command is issued, the descriptions willbe omitted from all future transmissions until an Include24 Character Description command is issued.
Control/D or Control/d (04H)
This command instructs the DATAPORT to include the24 character point descriptions in the data it transmits.The DATAPORT’s default condition is to transmit thedescriptions, so the only reason to issue this command isto countermand a previous Omit 24 Character Descrip-tion commnad.
Control/T or Control/t (14H)
This command instructs the DATAPORT to read thestatic data (point names, units, and descriptions) from allof the up to 15 controllers from which it may transmitdata. The DATAPORT stores the static data for eachpoint in its database to be transmitted along with thepoint’s dynamic data (value and status). The
XON
Omit 24 CharacterDescription
Include 24 CharacterDescription
Read Configuration
25
DATAPORT reads static data from the controllers twominutes after it is prowered up, when it is downloadedwith a changed configuration table, and in response tothis command. This Read Configuration commandshould be issued from the off-network device any timechanges are made to point names, unit designations, orpoint descriptions in the controller(s) from which theDATAPORT is to transmit data.
If the DATAPORT cannot successfully respond to a command fromthe off-network device, it will instead return an error code to the off-network device. There are six error codes, represented by the ASCIIdigits 1 through 6.
A complete error message from the DATAPORT consists of anASCII Formfeed control character, followed by the error code,followed by two ASCII Carriage Return control characters.
The following paragraphs describe the interpretation of the sixDATAPORT error codes.
The digit 1 returned as an error code means that the lastASCII character sent to the DATAPORT by the off-network device is not one that the DATAPORT recog-nizes as a command.
The digit 2 returned as an error code means that the off-network device has commanded the DATAPORT totransmit data from a controller that is properly config-ured in the DATAPORT, but the controller does notcontain a point display table.
Error Codes
1 Invalid Command
2 No Display Table
26
The digit 3 returned as an error code means that theDATAPORT cannot transmit data from the requestedcontroller because a communication error occurred whilethe DATAPORT was acquiring data from that controller.
The digit 4 returned as an error code means that the off-network device has commanded the DATAPORT totransmit data from a controller that is properly config-ured in the DATAPORT, but the controller is beyond the900 point limit. For example, if controllers 1 through 10each contain 90 points, a command for the DATAPORTto transmit data from controller 11, 12, 13, 14, or 15 willresult in error code 4.
The digit 5 returned as an error code means that a staticdata update is in progress, preventing the DATAPORTfrom responding successfully to a Send Controller DataCommand or a Send Data Periodically command.
The digit 6 returned as an error code means that the off-network device has commanded the DATAPORT totransmit data from a controller that is not configured inthe DATAPORT. For example, if only controllers 1through 5 are configured in the DATAPORT, a com-mand of 0 (Send Controller Data for Controller 15) willresult in error code 6.
3 CCN BusCommunicationError
4 Database Full
5 DATAPORT Busy
6 Controller NotConfigured
Reader'sComments
Fold so that the mailing address is visible, staple closed,and mail.
Your comments regarding this manual will help us improve futureeditions. Please comment on the usefulness and readability of thismanual, suggest additions and deletions, and list specific errors andomissions.
Document Name: Publication Date:
Usefulness and Readability:
Suggested Additions and Deletions:
Errors and Omissions (Please give page numbers):
Date:Name:Title or Position:Organization:Address:
Carrier CorporationCarrier World Headquarters Building
One Carrier PlaceFarmington, CT 06034-4015
Attn: CCN Documentation
SCP Printed in U.S.A. 808 - 619 1/90