Uploading and Downloading Databases Technical Bulletin

Technical BulletinIssue Date 09/01/01

© 2001 Johnson Controls, Inc. 1Code No. LIT-636115 www.johnsoncontrols.com

Introduction Page 2

• Theory of Operation 2

Setup Procedures 10

• Procedure Considerations 11

• Uploading and Downloading Procedures 12

• Error Messages 14

Windows 17

• Upload/Download Summary 17

• Upload and Download Dialog Boxes 18

Reference Tables 22

• Order of Object/Feature Upload 22

• Order of Object/Feature Download 32

Uploading and Downloading Databases

2 Uploading and Downloading Databases Technical Bulletin

Introduction

There are three types of databases: global, Network Control Module(NCM), and controller. NCM and global databases can be uploaded ordownloaded. Controller databases can only be downloaded. TheUploading and Downloading feature allows you to transfer data fromone device or Personal Computer (PC) file to another. This enables you tokeep controller, NCM, and global databases up-to-date and synchronized.

There are two versions of each database: the archive database and theonline database. An online database is an operational copy of a databaseused to operate the Building Automation System (BAS); an archivedatabase is the master copy of an online database. When one of thedatabases is changed, either upload or download the database to keep theother synchronized.

The global database contains network configuration, the Devices system,systems, report/access groups, and the password database.

A global upload copies the online global database to the archive globaldatabase at the workstation performing the upload. If a change is made tothe online copy (for example, a Report/Access group is modified), youshould perform a global upload to update the archive copy of the globaldatabase. Then perform a global upload at each of the workstations on thenetwork to ensure that all of the archive global databases are the same.

If a change is made to the archive global database (for example, you useDDL to add a PC to the network), you need to download the globaldatabase to keep the online database up-to-date. After the download iscomplete, the Metasys Network automatically sends the global data to allonline nodes on the network. If the network and workstation are connectedthrough phone lines and a modem (if the workstation is remote), the Dial-up feature will make the connection that allows the global download tooccur.

The NCM database contains process code and object/feature data. Forexample, this database contains Graphic Programming Language (GPL)process objects, object definition, trend, and totalization data. There aredifferent types of NCMs (e.g., Standard and Migration). Some of the datacontained in the NCM database varies depending on the type of NCM andits associated controllers.

Theory ofOperation

Global Database

NCM Database

Uploading and Downloading Databases Technical Bulletin 3

The NCM archive database can be kept at the PC you are using or theNCM’s designated archive PC. It should be updated every time you makea change to the online NCM database. For example, when you define anobject using the Operator Workstation (OWS), you are changing anNCM’s online database. You should perform an upload to update theNCM’s archive database.

An NCM upload copies the online NCM database, located at the NCM, tothe archive NCM database, located at the archive PC. During an NCMupload, all object/feature databases in the NCM are uploaded. You cannotupload an individual database (for example, BI object data). The onlyexception to this is the uploading of process objects, which is described inthe Operator Workstation User’s Manual.

An NCM download copies the archive database, located at the current orarchive PC, to the online NCM database, located at the NCM. If youchange the archive NCM database (for example, you define an objectusing DDL), perform an NCM download to update the NCMs onlinedatabase.

Maximum Number of Objects That Can Be Downloaded into an NCM

A Network Controller (NC) download fails if the database has too manyobjects. The maximum limits for objects that can be downloaded into anNCM are as follows:

• Release 5 (or earlier): Approximately 1425 objects can bedownloaded into an NCM. However, since a system takes up the spaceof approximately 2.5 objects, for each system on the same NCM, the1425 maximum is reduced by 2.5 objects.

For example, if 10 systems are on the NCM, there is a loss of25 objects from the maximum (10 x 2.5). In this case, the maximumnumber of objects would be 1400.

• Release 6 (or later): Approximately 1850 objects can be downloadedinto an NCM. This limit applies when there are up to 430 systems onthe same NCM. However, if the number of systems on the same NCMis more than 430, the 1850 maximum is reduced by approximately2.5 objects for each additional system over 430. (This is because asystem takes up the space of approximately 2.5 objects.)

For example, if 440 systems are on the NCM (10 more than 430), thereis a loss of 25 objects from the maximum (10 x 2.5). In this case, themaximum number of objects would be 1825.


Notes: One way to determine how many systems and objects reside on anNCM is to decompile the global and NC files. The global file listssystem definition for the entire network, including on which NCsthe systems reside. The NC file lists one NC’s definition andincludes an object total at the end of the file. See the DDLProgrammer’s Manual for more information.

If the workstation and the NCM are connected through phone linesand a modem (i.e., the workstation is remote), there are specialconditions that need to be considered when performing an uploador download. Refer to Uploading Through Dial-upCommunications and Downloading Through Dial-upCommunications later in this section for details.

The controller database contains object/feature data specific to variouscontrollers. When a download command is given to a controller, thecontroller is taken offline.

If the workstation and the controller’s archive NCM are connected throughphone lines and a modem (i.e., the workstation is remote), there are specialconditions that need to be considered when performing a download. Referto Uploading Through Dial-Up Communications and DownloadingThrough Dial-Up Communications later in this section for details.

The following controllers can be downloaded:

DSC8500 Distributed System Controller

Downloading to the DSC8500 copies the CAL1 program for a DSC8500controller from the PC, via the S2 Migration NCM, to the online databaseof a DSC8500. You must archive the CAL1 program before it can bedownloaded to the DSC8500 controller. For detailed information, refer tothe Operator Workstation User’s Manual.

You must have a copy of the controller’s archived CAL1 program on thePC you are using to perform the DSC8500 download.

D600 Access Controller

The D600 download copies data held at the Access NCM to the onlinedatabase of the D600 Access Controller. When you download to an AccessNCM, access data dedicated to the D600 is not automatically sent to thecontroller. Instead, it is held at the NCM until you command the downloadto the controller. This prevents the controller from going offline at aninconvenient time.

You can use any configured or unconfigured workstation to perform theD600 download.

ControllerDatabase


Note: These are default directories. You can change to another directoryby pressing Tab when the cursor is in the directory field.

To configure the Air Handling Unit (AHU), Variable Air Volume (VAV)controller, Unitary (UNT) controller, or Phoenix (PHX) controller, you usethe HVAC PRO configuration tool. The PHX must be configured withHVAC PRO Release 4.0 or later. For HVAC PRO Release 4.0 or later, thefile extension is .ASC.

If you are configuring an AHU, VAV, or UNT and you use a version ofHVAC PRO software earlier than Release 4.0, the file extensions varydepending on the type of controller. AHU object files end with the .AHOextension. VAV object files end with the .VAO extension and UNT objectfiles end with the .UCO extension.

System 91 Application Specific Controller

The System 91 download copies a configuration file for a controller fromthe Operator Workstation, via the NCM, to the specific controller(DX9100, DX9120, XTM, LCP/DC9100, or TC9100).

For the System 91 controllers, the object files should be stored in theC:\BAS\DATA\SYSTEM91 directory of the PC you use to download thecontroller. If you use the PREP-FOR tool to load your program, the filesshould be stored in the C:\PROJECT\Contract#\SYSTEM91directory. (This is the default; however, you can change to any directory.)

Depending on the configuration tool you use, the object files havedifferent extensions.

Use the GC-9100 Graphic Programming Tool (Version 3.2 or later) toconfigure the LCP/DC9100. The file extension for the LCP/DC9100 isalways .DCF.


Use the GX-9100 Graphic Programming Tool (Version 2.0 or later) toconfigure the DX9100. To configure the DX9120, use the GX-9100 GraphicProgramming Tool, Version 4.01 or later. The file extension for both theDX9100 and the DX9120 is always .DXF. If you have defined new timeschedules (.TSD file) for a specific DX9100 or DX9120 controller, you canchoose to download the archived (new) schedules, which then replace theschedules currently defined in the controller’s memory.

XTMs can be configured at the Operator Workstation (OWS) with aconfiguration tool that is accessed from the Custom Applications optionon the Accessory menu. The configuration tool automatically creates theXTM download file. The XTM has a .DBF extension.

TC9100s are configured using HVAC PRO Release 6.0 or later.HVAC PRO Release 6.0 automatically creates the TC9100 download file.The download file has a .TCO extension (HVAC PRO Release 6.02 orearlier) or a .TCD extension (HVAC PRO Release 6.03 or later).Download of .TCD files is available with Metasys PMI Release 9.0 orlater.

If the PC is remote (connected by modem), there are special conditionsyou should consider before performing the NCM upload.

• When an NCM communicates over a modem, and the NCM is forcingthe communication connection, it can only communicate with itsdefined PC. Make certain that the archive and defined PCs for theNCM are the same.

• If you are using an unconfigured (undefined) PC, and you chooseThis PC, you can upload via a dial-up connection as long as the NCyou are uploading from is not connected (dialed in) to its defined PC.

• If you choose NC Archive and the NCM being uploaded is directlyconnected by modem to the archive PC (Figure 1), the archive PC mustalso be the defined PC for the NCM. If it is not, the upload fails.

UploadingThrough Dial-upCommunications


The archive PC must be the defined PC for the NCM being uploaded.

ModemPC2Archive PC = PC2

Defined PC = PC2

Uploading NCM

If you choose NC Archive,

FIG41

Figure 1: NCM Dial-up - Direct Connect to Archive PC

• If the archive PC is connected by modem to an NCM other than theone being uploaded (Figure 2), then the archive PC for the uploadingNCM must be the defined PC for the NCM to which the modem isdirectly connected. If it is not, the upload fails.

NCM 1

Defined PC = PC2

NCM2

Archive PC = PC2

PC2

If you choose NC Archive,

FIG42

Upload from NCM2

to archive PC

Figure 2: Archive PC and NCM Indirectly Connected


When an NCM or controller download is performed, consider thefollowing conditions:

• If you (the operator) initiate the download of both data and code, theNC terminates the phone connection and redials in order to completethe transfer of data. The transfer is completed in three segments(Figure 3):

21

3

datacode

The PC dials the NCM.When the connection is made, thephone number, baud rate, and node address are downloaded to the NCM.

When the information inStep 1 has been downloaded,the NCM hangs up and redialsthe PC. When the connectionis made, the BAS code is downloaded.

When the information inStep 2 has been downloaded,the NCM hangs up and redialsthe PC. When the connection is made, the NCM data is downloaded.

Figure 3: Data Transfer

• If you (the operator) initiate the download of data only, the downloadis performed in two steps (Figure 4):

21

test

The PC dials the NCM.When the connection is made, thephone number, baud rate, and nodeaddress are downloaded to the NCM.

When the information inStep 1 has been downloaded,the NCM hangs up and redialsthe PC. When the connection ismade, the NCM data is downloaded.

Figure 4: Data Downloading

DownloadingThrough Dial-upCommunications


• When the NCM forces the communication connection (i.e., the NCMinitiates the download), it can communicate only with its defined PC.You’ll need to make certain that the archive and defined PCs for thedownloading NCM are the same.

• If you choose NC Archive, and the archive PC is connected by modemto an NCM other than the one being downloaded (Figure 2), then thearchive PC for the downloading NCM must be the defined PC for theNCM to which the modem is directly connected. If it is not, thedownload will fail.

Note: This will also be the case if the NCM being downloadedinitiates the download.


Setup Procedures

Perform an upload or download by selecting the appropriate command inthe Action menu. Figure 5 outlines the procedure for uploading ordownloading a database.

Procedure Considerations1. Decide which databases you want to

upload or download.

2. Decide the order in which the databasesneed to be uploaded or downloaded.

↓Uploading/Downloading Procedure1. Activate the network containing the

databases.

2. Select the NCM, or access the controller’sFocus window. (If you areuploading/downloading the global databaseonly, skip this step.)

3. Perform the upload/download by selectingthe appropriate command from the Actionmenu.

Figure 5: Uploading/Downloading Procedure Flowchart


Before uploading and downloading, consider the following:

• Decide which databases need to be uploaded or downloaded. Adatabase should be uploaded or downloaded if it is changed so thatother databases are kept up to date and synchronized. Table 1 providesexample situations when each type of database needs to be uploaded ordownloaded.

Table 1: When to Upload and DownloadProcedure Example

Global Upload Perform a global upload when you add or alter online global data(for example, when you define a password at the OperatorWorkstation).

GlobalDownload

Perform a global download when you add or alter archived globaldata (for example, when you use DDL to define a device).

NCM Upload Perform an NCM upload when you use the Operator Workstation toadd or alter online data or when you program an NCM on line.

NCMDownload

Perform an NCM download when you use DDL to add or alterarchived NCM data or when you install an NCM and need to load itsprogram.

DSC8500Download

Perform a DSC8500 download when you add or change CAL1programs or when you install the S2 Migration NCM.

D600Download

Perform a D600 download when you download altered access datato the Access NCM or when you install the Access NCM.

N2OpenControllerDownload*

Perform an N2Open controller download when you add or alter theASC’s HVAC PRO object file or when you add a controller.

System 91ControllerDownload*

Perform a System 91 controller download when you add or alter thecontroller’s configuration file or when you add a controller.

* First upload the files locally to retrieve any changes made to the controller’sconfiguration during commissioning.

• Decide the order in which the databases need to be uploaded ordownloaded.

If you need to upload both the global and the NCM databases, upload theglobal database first. Do not perform both at the same time.

If you need to download all three types of databases, perform the globaldownload first, then the NCM, and finally the controller. Wait untilone download is complete before beginning another.

ProcedureConsiderations

Order of Upload

Order ofDownload


You can only upload or download databases online using the OWSwindows. Also, NCMs and controllers that are offline cannot send orreceive data. There are three steps necessary to perform an upload ordownload:

1. Activate the network. Log on to the network by selecting the networkfrom the list box in the BAS Log On dialog box and entering yourpassword in the Password field. If you are already logged on, skip thisstep. Refer to the Operator Workstation User’s Manual.

2. Select (highlight) the NCM on the Network Map (under the Deviceheading) that you want to upload or download. If you aredownloading a controller, display the controller’s Focus window. Ifyou are uploading or downloading a global database, skip this step.

3. Initiate the upload or download by selecting the upload or downloadcommand from the Action menu.

If you are uploading or downloading a global database, or if you aredownloading a D600 Access Controller database, click OK to initiatethe download.

If you are uploading or downloading an NCM or if you aredownloading a DSC8500, N2Open or System 91 controller, select theappropriate options in the dialog box and click OK to initiate theupload or download. Table 2 describes the choices you make in eachcase.

Uploading andDownloadingProcedures


Table 2: Upload and Download SelectionsOperation Selection

NCM Upload This PC Select this to choose the PC you are using toreceive the upload.

or

NC Archive Select this to choose the PC that is defined asthe archive PC for the NCM sending the data.

NCM Download NC Data Select this to download NCM data only.

or

Code and NCData

Select this to download both the code and NCMdatabases or to load a software update.

This PC Select this to choose the PC you are using todownload the code and/or data.

or

NC Archive Select this to choose the PC that is defined asthe archive PC to download the code and/ordata.

DSC8500Download

This PC Select this to choose the PC you are using todownload the controller’s CAL1 programs.

or

NC Archive Select this to choose the PC that is defined asthe archive PC for the S2 Migration NCMcontrolling the DSC8500.

The PC performing the download must containthe CAL1 file.

N2OpenDownload

Select File toDownload

Select the HVAC PRO object file from the listbox. If no files exist, either the path name in theDownload File Path field is incorrect, or there areno files in the directory.

System 91 Select File toDownload

Select the XTM, LCP/DC9100, DX9100, orDX9120 object file from the list box. If no filesexist, either the path name in the Download FilePath field is incorrect, there are no files in thedirectory, or the files in the directory have thewrong file extension.

Replace timeschedules inconfigurationfile witharchived timeschedules

DX9100 and DX9120 only. Mark this checkboxto download the archived (new) time schedules(.TSD file) defined for the selected device. Thearchived time schedules are created by theDX9100 Local Time Schedules Definition dialogbox. The archived schedules will be downloadedafter the configuration file and will replace theconfiguration files currently in the controller’smemory.


When an upload or download cannot be started (and for some failureconditions), an error message appears on the screen. Click the OK buttonto acknowledge the message; this also aborts the attempt to upload ordownload. Then refer to the Error Log for the exact nature of the failure,correct the problem, and attempt the operation again. For moreinformation on the Error Log, refer to the Troubleshooting GuideTechnical Bulletin (LIT-636328).

Error messages vary, depending on the type of upload or download. Someof the most common error messages for each type of upload and downloadare listed below.

Table 3: Global Upload ErrorsError DescriptionGlobal Upload Failed Usually indicates an NC direct or dial-up connection

failed.

Global Upload NotInitiated

Usually indicates that an internal failure occurred whenthe online data was being transferred to the archiveglobal database.

Table 4: Global Download ErrorsError DescriptionGLOBAL DOWNLOADFAILED

Copy to onlinesuccessful.

Transfer to networkfailed.

The archive was successfully copied to the onlineglobal database, but the online database could not betransferred to the network. This usually indicates an NCdirect or dial-up connection failed.

Global Download NotInitiated

Copy to onlinefailed.

This error message, as well as the previous one,usually indicates that an internal failure occurred whenthe archive data was being transferred to the onlineglobal database.

Table 5: NCM Upload ErrorsError DescriptionNC needs codedownload

Indicates the NCM needs a download of BAS code anddata.

Download/Uploadalready in progress

Indicates the NCM is already involved in an upload ordownload.

Table 6: NCM Download ErrorsError DescriptionNCM needs codedownload

Indicates the NCM needs BAS code as well as thedatabase, and you selected to download the databaseonly. Start the download process again, but this time,select to download both the NC data and the BAScode.

Download/Uploadalready in progress

Indicates an upload or download is already in progress.

ErrorMessages


Table 7: DSC8500 Distributed System Controllers ErrorsError DescriptionDevice is Offline,Command Not Accepted

The DSC8500 is offline.

CommunicationDisabled, Command NotAccepted

Communication to the DSC8500 is disabled.

Device Download inProgress

Download to the requested DSC8500 is already inprogress.

NC Download Busy A download is in progress elsewhere on the NCM.

Table 8: D600 Access Controllers ErrorsError DescriptionDevice is Offline,Command Not Accepted

The D600 is offline.

CommunicationDisabled - commandnot accepted

The communication to the D600 is disabled.

Device Download inProgress

A D600 download is already in progress at this NC.

Command AlreadyExecuted

The command to download the controller has alreadybeen issued but has not yet begun.

Table 9: N2Open Application Specific Controllers ErrorsError DescriptionDevice is Offline - CommandNOT Accepted

The controller is offline.

Communication Disabled -Command NOT Accepted

The controller communication is disabled.

Bad Download Attempt The controller is already receiving a download.

NC Download Busy The NCM is busy with another download.

Firmware Version Mismatch The firmware version for the files beingdownloaded is different from the one installedon the controller, or the firmware version is notsupported by N2Open download.

Hardware Busy The controller is busy performing some otherfunction.

Invalid Path The path name for the HVAC PRO directory isinvalid.

File Does Not Exist The file name entered in the Download FilePath text box does not exist.

Device Type and File FormatDo Not Match

The selected file is not valid for the type ofcontroller you are attempting to download.


Table 10: System 91 Application Specific Controllers ErrorsError DescriptionBad Download Attempt The controller is already receiving a download.

NC Download Busy The NCM is busy with another download.

Firmware Version Mismatch The firmware version for the files beingdownloaded is different from the one installedon the controller, or the firmware version is notsupported by the System 91 Downloadfeature.

Invalid Path The specified directory, as indicated in theDownload File Path text box does not exist.

File Does Not Exist The file name entered in the Download FilePath text box does not exist.

Device Type and File FormatDo Not Match

The selected file is not valid for the type ofcontroller you are attempting to download.


Windows

Use the following windows to use and monitor Uploading andDownloading operations:

Upload/Download Summary Lists all device uploads and downloads thathave been, or are currently being uploadedor downloaded. Allows you to abort anyupload or download currently in progress.

Upload and Download Dialog Boxes Allows you to upload and downloaddatabases in order to keep network dataup-to-date and synchronized.

The Upload/Download Summary contains a record of NCM and controlleruploads and downloads that have been executed or are currently inprogress at the OWS. Use the summary to find out the status of an uploador download, or use it to stop an upload or download in progress.

If the summary is not displayed at the time of an upload or download, itautomatically appears as a flashing icon (Figure 6) when the upload ordownload begins. The icon stops flashing when the operation iscompleted; however, it remains on the screen. Double-click on the icon toview the summary.

ICON

Figure 6: Upload/Download Summary Icon

The summary (Figure 7) lists the network, system, object, status, initiator,date, and time for each upload or download.

Upload/DownloadSummary


SUMMARY

HelpItem Edit View Action Go To Accessory

System

BASEMENT

FLOOR_11

FLOOR_11

FLOOR_11

Object

DSC45

AC45

NC2

NC3

NC4

DSC15

AHU12

Status

DOWNLOAD IN PROGRESS

????????

UPLOAD FAILED

UPLOAD ABORTED

UNABLE TO START DOWNLOAD

DOWNLOAD ABORTED

DOWNLOAD COMPLETE

Network

HDQTRS

HDQTRS

HDQTRS

HDQTRS

HDQTRS

HDQTRS

HDQTRS

Upload/Download

Figure 7: Upload/Download Summary

When you command an NCM to upload or download data or when youcommand a DSC8500, N2Open, or System 91 controller to download, adialog box appears allowing you to specify what data is to be uploaded ordownloaded and the location from which it was sent or to which it wasreceived.

If you are uploading or downloading a global database or if you aredownloading a DSC8500 or D600 Access Controller, no dialog boxappears for making selections. Instead, a Global Download/Uploadmessage box appears prompting you to begin the upload or download.

Use the Network Map - Upload dialog box (Figure 8) to choose the PCthat will receive the data you are uploading.

NC_UP

Archive Destination

This PC

NC Archive

OK

CANCEL

Source: NC44

Network Map - Upload

Figure 8: Network Map - Upload Dialog Box

Upload andDownloadDialog Boxes

Global, D600,and DSC8500Uploads andDownloads

NCM Upload


Use the Network Map - Download dialog box (Figure 9) to select the PCthat will download the data and/or code.

NCMDOWN

OK

CANCEL

Archive Source

This PC

NC archive

Download

NC Data

Code and NC Data

Destination: NC44

Network Map - Download

Figure 9: Network Map - Download Dialog Box

NCM Download


Use the DSC8500 Download dialog box (Figure 10) to choose the PCcontaining the archived CAL1 program you want to send to the DSC8500.The CAL1 program must be archived on the PC you are using to performthe download.

DSC8500

Archive Source

This PC

NC Archive

OK

CANCEL

Source: NC44

DOWNLOAD - DSC8500

Figure 10: DSC8500 Download Dialog Box

Use the N2Open dialog box (Figure 11) to choose the HVAC PRO objectfile that you want to download to the AHU, VAV, UNT, or PHX. Thedefault directory for object files is the HVACPRO directory (for AHU,VAV, UNT, or PHX controllers); however, you can change directories byentering a new directory name in the Download File Path field.

N2Open

Select File to Download

AHU1.AHO

AHU2.AHOAHU12.AHOAHU43.AHOAHU50.ASCAHU51.ASC

OK

CANCEL

Download File Path {<Tab> after change}

DOWNLOAD - AHU

Note: Download does not alter AI offsets!

C:\FMS\DATA\HVACPRO

Figure 11: N2Open Download Dialog Box

DSC8500Download

N2OpenDownload


Use the Download dialog box (Figure 12) to choose the System 91 objectfile that you want to download to the LCP/DC9100, XTM, DX9100,DX9120, or TC9100. The default directory for object files is theSYSTEM91; however, you can change directories by entering a newdirectory name in the Download File Path field.

9100

Select File to Download

SYS1.DXFSYS2.DXFSYS5.DXFSYS6.DXFSYS8.DXF

CANCEL

Download File Path {<Tab> after change}

DOWNLOAD - DX9100

C:\FMS\DATA\SYSTEM91

OK

Replace time schedules in configuration with archived time schedule?

Figure 12: Download Dialog Box for a DX9100

System 91Download


Reference Tables

The objects and features supported vary depending on the type of NCM.Refer to the following tables to find out which object and feature databasesare uploaded as well as the order in which they are uploaded for eachNCM.

Table 11 lists the order in which the object/feature databases are uploadedfrom an Access NCM. The order is the same for all Access NCMs(e.g., NCM 200/300).

Table 11: Order of Access NCM Database UploadOrder Database Order Database

1 Object Directory 17 CSG

2 AC 18 MC

3 XM 19 Subordinate4 DCDR (System 91) 20 JCB

5 N2Open 21 DL/LR Groups

6 BI 22 Totalization (analog)

7 MSI 23 Totalization (event)

8 Card Reader 24 Totalization (pulse)

9 ACM 25 Totalization (runtime)

10 BO 26 Trend

11 MSO 27 Alarm Messages

12 AI 28 NC Weekly Schedule

13 AOS 29 NC Calendar Schedule

14 AD 30 Access Card

15 BD 31 Time Zone

16 MSD

Order ofObject/FeatureUpload

Access NCMUpload


The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 12 lists the order ofupload for NCM 101/102/401. Table 13 lists order of upload forNCM 200/300/350.

Table 12: Fire NCM 101/102/401 Database UploadOrder Database Order Database

1 Object Directory 15 BD

2 Fire 16 MSD

3 XM 17 CSG

4 DCDR (System 91) 18 JCB


6 Zone 20 Totalization (analog)

7 BI 21 Totalization (event)

8 MSI 22 Totalization (pulse)


10 BO 24 Trend




14 AD

Table 13: Fire NCM 200/300/350 Database UploadOrder Database Order Database

1 Object Directory 16 MSD

2 Fire 17 CSG

3 XM 18 MC

4 DCDR (System 91) 19 Subordinate5 N2Open 20 JCB

6 Zone 21 DL/LR Groups



9 ACM 24 Totalization (pulse)

10 BO 25 Totalization (runtime)

11 MSO 26 Trend

12 AI 27 Alarm Messages

13 AOS 28 NC Weekly Schedule

14 AD 29 NC Calendar Schedule

15 BD

Fire NCM Upload


Table 14 lists the order in which the object/feature databases are uploadedfrom an Intelligent Lighting Controller (ILC) NCM. The order is the samefor all ILC NCMs (e.g., NCM 101/102/401).

Table 14: ILC NCM Database UploadOrder Database Order Database

1 Object Directory 19 C260A

2 LCD 20 C260X

3 XM 21 C500X

4 PIDC 22 AD

5 DCM 23 BD

6 DSC1000 24 MSD

7 DCDR (System 91) 25 LCG

8 N2Open 26 CSG

9 BI 27 JCB

10 MSI 28 DL/LR Groups

11 ACM 29 Totalization (analog)

12 BO 30 Totalization (event)

13 MSO 31 Totalization (pulse)

14 AI 32 Totalization (runtime)

15 PIDL 33 Trend

16 AOD 34 Alarm Messages


18 C210A 36 NC Calendar Schedule

The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 15 lists the upload orderfor NCM401. Table 16 lists the order for NCM 200/300.

Table 15: JC/85 Gateway NCM401 Database UploadOrder Object/Feature Databases Uploaded

1 Object Directory

2 Alarm Messages

3 NC Weekly Schedule

4 NC Calendar Schedule

Table 16: JC/85 Gateway NCM 200/300 Database UploadOrder Object/Feature Databases Uploaded1 Object Directory 7 Totalization (runtime)

2 AD 8 Trend

3 BD 9 Alarm Messages

4 Totalization (analog) 10 NC Weekly Schedule

5 Totalization (event) 11 NC Calendar Schedule

6 Totalization (pulse)

ILC NCM Upload

JC/85 GatewayNCM Upload


Table 17 lists the order in which the object/feature databases are uploadedfrom a Network Port NCM. The order is the same for all Network PortNCMs (e.g., NCM 200/300).

Table 17: Network Port NCM Database UploadOrder Database Order Database

1 Object Directory 20 C500X

2 LCD 21 AD

3 XM 22 BD

4 DCM 23 MSD

5 DSC1000 24 LCG

6 DCDR (System 91) 25 CSG

7 N2Open 26 MC

8 BI 27 Subordinate9 MSI 28 JCB

10 ACM 29 DL/LR Groups

11 BO 30 Totalization (analog)

12 MSO 31 Totalization (event)

13 AI 32 Totalization (pulse)

14 PIDL 33 Totalization (runtime)

15 AOD 34 Trend

16 AOS 35 Alarm Messages

17 C210A 36 NC Weekly Schedule


19 C260X

Network PortNCM Upload


Table 18 lists the order in which the object/feature databases are uploadedfrom an OT NCM. The order is the same for all Operator Terminal (OT)NCMs (e.g., NCM 200/300).

Table 18: OT NCM Database UploadOrder Database Order Database

1 IO Dispatch 23 AI

2 Calendar 24 PIDL

3 Holiday 25 AOD

4 Daylight Savings 26 AOS

5 Password 27 AD

6 NM 28 BD

7 Default Device 29 MSD

8 Report Routing 30 LCG

9 N1 31 CSG

10 Sys 32 MC

11 Object Directory 33 Subordinate12 LCD 34 JCB

13 XM 35 DL/LR Groups

14 PIDC 36 Totalization (analog)

15 DCM140 37 Totalization (event)

16 DCDR (System 91) 38 Totalization (pulse)

17 N2Open 39 Totalization (runtime)

18 BI 40 Trend

19 MSI 41 Alarm Messages

20 ACM 42 NC Weekly Schedule

21 BO 43 NC Calendar Schedule

22 MSO

OT NCM Upload


The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 19 lists the order ofupload for the S2 Migration NCM401. Table 20 lists order of upload forthe S2 Migration NCM 200/300.

Table 19: S2 Migration NCM401 Database UploadOrder Database Order Database


2 DSC8500 14 JCB

3 FPU 15 DL/LR Groups





8 MSO 20 Trend




12 BD

Table 20: S2 Migration NCM 200/300 Database UploadOrder Database Order Database

1 Object Directory 14 MC

2 DSC8500 15 Subordinate3 FPU 16 JCB

4 BI 17 DL/LR Groups

5 MSI 18 Totalization (analog)

6 ACM 19 Totalization (event)

7 BO 20 Totalization (pulse)

8 MSO 21 Totalization (runtime)

9 AI 22 Trend


11 AD 24 NC Weekly Schedule

12 BD 25 NC Calendar Schedule

13 MSD

S2 MigrationNCM Upload


The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 21 lists the order inwhich the object/feature databases are uploaded from the Standard NCM101/102/401. Table 22 lists the order of database upload for the StandardNCM 200/300.

Table 21: Standard NCM 101/102/401 Database UploadOrder Database Order Database

1 Object Directory 18 C260A

2 XM 19 C260X

3 PIDC 20 C500X

4 DCM140 21 AD

5 DSC1000 22 BD

6 DCDR (System 91) 23 MSD

7 N2Open 24 CSG

8 BI 25 JCB






14 PIDL 31 Trend




Standard NCMUpload


Table 22: Standard NCM 200/300 Database UploadOrder Database Order Database


2 LCD 21 C500X

3 XM 22 AD

4 PIDC 23 BD

5 DCM140 24 MSD

6 DSC1000 25 LCG


8 N2Open 27 MC







16 AOD 35 Trend




Table 23 lists the order in which object/feature databases are uploadedfrom the System 91 NCM. The order is the same for all System 91 NCMs(e.g., NCM 101/102/401).

Table 23: System 91 NCM Database UploadOrder Database Order Database

1 Object Directory 15 AD

2 XM 16 BD

3 PIDC 17 MSD

4 DCM 18 CSG







11 AI 25 Trend

12 PIDL 26 Alarm Messages

13 AOD 27 NC Weekly Schedule


System 91 NCMUpload


Table 24 lists the order in which object/feature databases are uploadedfrom the General NT NCM. The order is the same for all General NetworkTerminal (NT) NCMs (e.g., NCM 200/300).

Table 24: General NT Database UploadOrder Database Order Database

1 Object Directory 21 AOS

2 Fire 22 AD

3 AC 23 BD

4 LCD 24 MSD

5 XM 25 LCG

6 PIDC 26 CSG

7 DCM140 27 MC

8 LON 28 Subordinate9 DCDR 29 JCB NC

10 N2 Open 30 DL/LR Groups


12 Card Reader 32 Totalization (event)

13 BI 33 Totalization (pulse)

14 MSI 34 Totalization (runtime)

15 ACM 35 Trend

16 BO 36 Alarm Message

17 MSO 37 NC Weekly Schedule

18 AI 38 NC Calendar Schedule

19 PIDL 39 Access Card

20 AOD 40 Time Zone

General NTUpload


Table 25 lists the order in which object/feature databases are uploadedfrom the General OT NCM. The order is the same for all General OTNCMs (e.g., NCM 200/300).

Table 25: General OT Database UploadOrder Database Order Database

1 I/O Dispatch 23 AI

2 Calendar 24 PIDL

3 Holiday 25 AOD

4 Daylight Savings 26 AOS

5 Password 27 AD

6 NM 28 BD

7 Default Device 29 MSD

8 Report Routing 30 LCG

9 N1 Directory 31 CSG

10 System Directory 32 MC

11 Object Directory 33 Subordinate12 LCD 34 JCB NC




16 DCDR 38 Totalization (pulse)

17 N2 Open 39 Totalization (runtime)

18 BI 40 Trend




22 MSO

Table 26 lists the order in which object/feature databases are uploadedfrom the UL Fire NCM. The order is the same for all UL Fire NCMs(e.g., NCM 200/300).

Table 26: UL Fire Database UploadOrder Database Order Database


2 Fire 6 MC

3 Zone 7 Subordinate4 BD 8 Alarm Message

General OTUpload

UL Fire Upload


The objects and features supported vary depending on the type of NCM.Refer to the following tables for object and feature databases and the orderin which they are downloaded for each NCM.

Table 27 shows the order in which the object/feature databases aredownloaded from the Access NCM. The order is the same for all AccessNCMs (e.g., NCM 200/300).

Table 27: Order of Access NCM Database DownloadOrder Database Order Database

1 NC Text 17 MSD

2 Object Directory 18 CSG

3 AC 19 MC

4 XM 20 Subordinate5 DCDR (System 91) 21 JCB


7 Card Reader 23 Totalization (analog)




11 BO 27 Trend




15 AD 31 Access Card

16 BD 32 Time Zone

Order ofObject/FeatureDownload

Access NCMDownload


The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 28 lists the order ofdatabase download from the Fire NCM 101/102/401. Table 29 lists theorder of database download from the NCM 200/300.

Table 28: Fire NCM 101/102/401 Database DownloadOrder Database Order Database

1 NC Text 15 AD


3 Fire 17 MSD

4 XM 18 CSG







11 BO 25 Trend




Table 29: Fire NCM 200/300 Database DownloadOrder Database Order Database

1 NC Text 16 BD


3 Fire 18 CSG

4 XM 19 MC

5 DCDR (System 91) 20 Subordinate6 N2Open 21 JCB

7 Zone 22 DL/LR Groups





12 MSO 27 Trend




Fire NCMDownload


Table 30 shows the order in which the object/feature databases aredownloaded from the ILC NCM. The order is the same for all ILC NCMs(e.g., NCM 101/102/401).

Table 30: ILC NCM Database DownloadOrder Database Order Database

1 NC Text 20 C260A


3 LCD 22 C500X

4 XM 23 AD

5 PIDC 24 BD

6 DCM 25 MSD

7 DSC1000 26 LCG


9 N2Open 28 JCB






15 AI 34 Trend




19 C210A

The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 31 lists the order ofdatabase download from the JC/85 Gateway NCM 101/102/401. Table 32lists the order of database download from the JC/85 GatewayNCM 200/300.

Table 31: JC/85 Gateway NCM 101/102/401 Database DownloadOrder Object/Feature Databases Downloaded1 NC Text

2 Object Directory

3 Alarm Messages



ILC NCMDownload

JC/85 GatewayNCM Download


Table 32: JC/85 Gateway NCM 200/300 Database DownloadOrder Object/Feature Databases Downloaded1 NC Text

2 Object Directory

3 AD

4 BD

5 Totalization (analog)6 Totalization (event)7 Totalization (pulse)8 Totalization (runtime)9 Trend10 Alarm Messages



Table 33 lists the order in which the object/feature databases aredownloaded from the Network Port NCM. The order is the same for allNetwork Port NCMs (e.g., NCM 200/300).

Table 33: Network Port NCM Database DownloadOrder Database Order Database

1 NC Text 20 C260X


3 LCD 22 AD

4 XM 23 BD

5 PIDC 24 MSD

6 DCM 25 LCG


8 N2Open 27 MC







16 AOD 35 Trend




Network PortNCM Download


Table 34 shows the order in which object/feature databases aredownloaded from an OT NCM. The order is the same for all OT NCMs(e.g., NCM 200/300).

Table 34: OT NCM Database DownloadOrder Database Order Database

1 I/O Dispatch 23 MSO

2 Calendar 24 AI

3 Holiday 25 PIDL

4 Daylight Savings 26 AOD

5 Password 27 AOS

6 NM 28 AD

7 Default Device 29 BD

8 Report Routing 30 MSD

9 N1 Directory 31 LCG

10 System Directory 32 CSG

11 NC Text 33 MC

12 Object Directory 34 Subordinate13 LCD 35 JCB



16 DCM 38 Totalization (event)

17 DCDR (System 91) 39 Totalization (pulse)


19 BI 41 Trend




OT NCMDownload


The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 35 lists the order ofdatabase download from the S2 Migration NCM 101/102/401. Table 36lists the order of database download from the S2 Migration NCM 200/300.

Table 35: S2 Migration NCM 101/102/401 Database DownloadOrder Database Order Database

1 NC Text 13 BD


3 DSC8500 15 JCB

4 FPU 16 DL/LR Groups





9 MSO 21 Trend




Table 36: S2 Migration NCM 200/300 Database DownloadOrder Database Order Database

1 NC Text 14 MSD


3 DSC8500 16 Subordinate4 FPU 17 JCB






10 AI 23 Trend


12 AD 25 NC Weekly Schedule

13 BD 26 NC Calendar Schedule

S2 MigrationNCM Download


The order of object/feature database upload depends on the type of NCM(e.g., NCM 101/102/401 or NCM 200/300). Table 37 lists the order ofdatabase download from the Standard NCM 101/102/401. Table 38 liststhe order of database download from the Standard NCM 200/300.

Table 37: Standard NCM 101/102/401 Database DownloadOrder Database Order Database

1 NC Text 19 C260A


3 XM 21 C500X

4 PIDC 22 AD

5 DCM 23 BD

6 DSC1000 24 MSD


8 N2Open 26 JCB






14 AI 32 Trend




18 C210A

Table 38: Standard NCM 200/300 Database DownloadOrder Database Order Database

1 NC Text 21 C260X


3 LCD 23 AD

4 XM 24 BD

5 PIDC 25 MSD

6 DCM 26 LCG

7 DSC1000 27 CSG

8 DCDR (System 91) 28 MC

9 N2Open 29 Subordinate10 BI 30 JCB






16 PIDL 36 Trend




20 C260A

Standard NCMDownload


Table 39 lists the order in which object/feature databases are downloadedfrom the System 91 NCM. The order is the same for all System 91 NCMs(e.g., NCM 101/102/401).

Table 39: System 91 NCM Database DownloadOrder Database Order Database

1 NC Text 16 AD


3 XM 18 MSD

4 PIDC 19 CSG

5 DCM 20 JCB

6 DCDR (System 91) 21 DL/LR Groups





11 MSO 26 Trend


13 PIDL 28 NC Weekly Schedule

14 AOD 29 NC Calendar Schedule

15 AOS

System 91 NCMDownload


Table 39 lists the order in which object/feature databases are downloadedfrom the General NT NCM. The order is the same for all General NTNCMs (e.g., NCM 200/300).

Table 40: General NT NCM Database DownloadOrder Database Order Database

1 NC Text 22 AOS

2 Object Directory 23 AD

3 Fire 24 BD

4 AC 25 MSD

5 LCD 26 LCG

6 XM 27 CSG

7 PIDC 28 MC

8 DCM140 29 Subordinate9 LON 30 JCB

10 DCDR 31 DL/LR Groups

11 N2 Open 32 Totalization (analog)

12 Zone 33 Totalization (event)

13 Card Reader 34 Totalization (pulse)

14 BI 35 Totalization (runtime)

15 MSI 36 Trend

16 ACM 37 Alarm Messages

17 BO 38 NC Weekly Schedule

18 MSO 39 NC Calendar Schedule

19 AI 40 Access Card

20 PIDL 41 Time Zone

21 AOD

General NTDownload


Table 39 lists the order in which object/feature databases are downloadedfrom the General OT NCM. The order is the same for all General OTNCMs (e.g., NCM 200/300).

Table 41: General OT NCM Database DownloadOrder Database Order Database

1 I/O Dispatch 23 MSO

2 Calendar 24 AI

3 Holiday 25 PIDL

4 Daylight Savings 26 AOD

5 Password 27 AOS

6 NM 28 AD

7 Default Device 29 BD

8 Report Routing 30 MSD

9 N1 Directory 31 LCG

10 System Directory 32 CSG

11 NC Text 33 MC

12 Object Directory 34 Subordinate13 LCD 35 JCB NC




17 DCDR 39 Totalization (pulse)


19 BI 41 Trend




Table 39 lists the order in which object/feature databases are downloadedfrom the UL Fire NCM. The order is the same for all UL Fire NCMs(e.g., NCM 200/300).

Table 42: UL Fire NCM Database DownloadOrder Database Order Database

1 NC Text 6 MSD


3 Fire 8 Subordinate4 Zone 9 Alarm Message

5 BD

General OTDownload

UL FireDownload

Controls Group507 E. Michigan Street www.johnsoncontrols.comP.O. Box 423 Release 12.00Milwaukee, WI 53201 Printed in U.S.A.

Uploading and Downloading Databases Technical Bulletin

Documents

Transcript of Uploading and Downloading Databases Technical Bulletin