CM9740-CC1System 9740

Controller

Installation/Operation Manual

C1508M-A (02/01)

Pelco 3500 Pelco Way Clovis, CA 93612-5699 USA www.pelco.comIn North America and Canada: Tel (800) 289-9100 FAX (800) 289-9150International Customers: Tel +1(559) 292-1981 FAX +1(559) 348-1120

2 | C1508M-A (02/01)

CONTENTS

Section Page

1.0 IMPORTANT SAFEGUARDS AND WARNINGS ......................................................51.2 REGULATORY NOTICES .............................................................................. 5

2.0 OVERVIEW .............................................................................................................. 62.1 INTRODUCTORY REMARKS ........................................................................62.2 MANUAL LAYOUT ......................................................................................... 6

3.0 BEFORE YOU BEGIN .............................................................................................. 73.1 A BRIEF NOTE .............................................................................................. 73.2 FOR THE BEGINNER OR NEW USER, A FEW WORDS OF ADVICE AND

SOME EXERCISES ....................................................................................... 7

4.0 INTRODUCTION TO THE CC1 ................................................................................ 84.1 DESCRIPTION .............................................................................................. 84.2 MODEL .......................................................................................................... 84.3 SERCOM BOARD CARDS ........................................................................... 104.4 MOUNTING THE CONTROLLER ................................................................. 104.5 CONNECTING TO THE CONTROLLER....................................................... 11

5.0 PHYSICAL INSTALLATION AND INITIALIZATION ................................................. 125.1 CC1 INSTALLATIONCATEGORY I ............................................................. 12

5.1.1 Category INew Installation .............................................................. 125.1.2 Category IUpgrade Replacement (Hardware Only) ........................ 135.1.3 Category IUpgrade Replacement (Hardware And Software).......... 145.1.4 Category IUpgrade Replacement (Software Only) ......................... 15

6.0 CC1 INITIALIZATION .............................................................................................. 166.1 SINGLE-NODE INITIALIZATION .................................................................. 16

6.1.1 Diagnostic Screen ............................................................................. 166.1.2 Keyboard ........................................................................................... 166.1.3 MGR Program System Window ........................................................ 176.1.4 Configuration File .............................................................................. 176.1.5 Online Node Dialog Box .................................................................... 186.1.6 Single-Node Hot Switch Configurations ............................................ 19

7.0 CC1 CONTROLLER OPERATION.......................................................................... 207.1 MONITORING CC1 FUNCTIONS ................................................................. 20

7.1.2 The Diagnostic Screen ..................................................................... 207.1.2.1 Monitor Box Examples ........................................................ 237.1.2.2 Monitor Box Allocation ........................................................ 247.1.2.3 Screen OperationKeystrokes ............................................ 25

7.2 SYSTEM TIME .............................................................................................. 267.2.1 Setting and Adjusting System TimeFor Single-Node ...................... 267.2.2 General Remarks Regarding System Time Adjustment ................... 28

7.3 CC1 SYSTEM INTEGRITY ........................................................................... 297.3.1 Dynamically Updating a Configuration File ....................................... 29

8.0 TROUBLESHOOTING/COMMON PROBLEMS ..................................................... 32APPENDIX I INSTALLING THE MGR PROGRAM ........................................... 33APPENDIX II DOS ENVIRONMENT AND COMMAND REFERENCE .............. 34APPDENDIX III MGR WRITE UTILITY .................................................................. 41APPENDIX IV MGR READ UTILITY ................................................................... 42APPENDIX V REMOVING AN EXISTING MGR PROGRAM ............................. 43APPENDIX VI EDITING THE AUTOEXEC.BAT FILE.......................................... 44APPENDIX VII EXERCISES ................................................................................ 45

9.0 SPECIFICATIONS................................................................................................... 52

10.0 WARRANTY AND RETURN INFORMATION ......................................................... 54

CM9740-CC1 | 3

LIST OF ILLUSTRATIONS

Figure Page

1 CM9740-CC1 Front View ................................................................................... 82 Rear View, General Identification ....................................................................... 93 CM9740-CC1 Rear Connector Pinouts ............................................................. 114 Multiple Receiver Hook-up ................................................................................ 115 Category IBare Bones ..................................................................................... 126 Category IFleshed Out .................................................................................... 127 Single-Node Initialization .................................................................................. 168 InitializationSystem Window ............................................................................ 179 Initialization Configuration File ........................................................................ 1710 InitializationOnline Nodes ............................................................................... 1811 MGR WindowsA Precaution ............................................................................ 1812 Single-Node Hot Switch Configurations ............................................................ 1913 Display Screen Geometry ................................................................................. 2114 Diagnostic Screen and Monitor Box Geometry ................................................. 2215 Monitor Box Camera Switching ......................................................................... 2316 Monitor Box Preset Call .................................................................................... 2317 Monitor Box Allocation ...................................................................................... 2418 Monitor BoxF1 Allocation ................................................................................ 2419 Monitor BoxAllocate 3 to 1 .............................................................................. 2420 Monitor Box Switch ........................................................................................... 2421 Keys CommandExamples ............................................................................... 2622 Time Synchronization ....................................................................................... 2723 Configuration File Dialog Box ............................................................................ 2924 Hard Drive Update ............................................................................................ 3025 Dynamic Update Block Diagram ....................................................................... 3126 Sample AUTOEXEC.BAT File ........................................................................... 3527 CC1 ConnectionsExercise I ............................................................................ 4528 CC1 SetupFinal ............................................................................................... 4529 CC1 Directory Structure .................................................................................... 4730 Root Directory ................................................................................................... 4731 9740 Directory ................................................................................................... 4732 The DOS Directory ............................................................................................ 4833 TESTPORT Directory ....................................................................................... 5034 MGR Program Location .................................................................................... 51

4 | C1508M-A (02/01)

LIST OF TABLES

Table Page

A Command Key Functions .................................................................................. 25B CC1 Hardware Errors ........................................................................................ 32C CC1 System Errors ........................................................................................... 32D DOS Command Reference Directory ................................................................ 38

LIST OF APPENDIXES

Number Page

APPENDIX I INSTALLING THE MGR PROGRAM ...................................................... 33APPENDIX II DOS ENVIRONMENT AND COMMAND REFERENCE ......................... 34APPDENDIX III MGR WRITE UTILITY ............................................................................. 41APPENDIX IV MGR READ UTILITY .............................................................................. 42APPENDIX V REMOVING AN EXISTING MGR PROGRAM ........................................ 43APPENDIX VI EDITING THE AUTOEXEC.BAT FILE ..................................................... 44APPENDIX VII EXERCISES ........................................................................................... 45

CM9740-CC1 | 5

1.0 IMPORTANT SAFEGUARDS AND WARNINGS

Prior to installation and use of this product, the following WARNINGS should be observed.

1. Installation and servicing should only be done by qualified service personnel and con-form to all local codes.

2. Unless the unit is specifically marked as a NEMA Type 3, 3R, 3S, 4, 4X ,6 or 6P enclo-sure, it is designed for indoor use only and it must not be installed where exposed torain and moisture.

3. Only use replacement parts recommended by Pelco.

4. After replacement/repair of this units electrical components, conduct a resistancemeasurement between line and exposed parts to verify the exposed parts have notbeen connected to line circuitry.

The product and/or manual may bear the following marks:

Please thoroughly familiarize yourself with the information in this manual prior to installationand operation.

This symbol indicates that dangerous volt-age constituting a risk of electric shock ispresent within this unit.

This symbol indicates that there are impor-tant operating and maintenance instructionsin the literature accompanying this unit.

C A U T I O N :

RISK OF ELECTRIC SHOCK.DO NOT OPEN.

1.1 REGULATORY NOTICES

This equipment has been tested and found to comply with the limits of a Class B digital de-vice, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonableprotection against harmful interference in a residential installation. This equipment gener-ates, uses, and can radiate radio frequency energy and, if not installed and used in accor-dance with the instructions, may cause harmful interference to radio communications. How-ever there is no guarantee that the interference will not occur in a particular installation. Ifthis equipment does cause harmful interference to radio or television reception, which canbe determined by turning the equipment off and on, the user is encouraged to try and cor-rect the interference by one or more of the following measures:

Reorient or relocate the receiving antenna.

Increase the separation between the equipment and the receiver.

Connect the equipment into an outlet on a circuit different from that to which the re-ceiver is connected.

Consult the dealer or an experienced radio/TV technician for help.

6 | C1508M-A (02/01)

2.0 OVERVIEW

2.1 INTRODUCTORY REMARKS

The CM9740-CC1 is the controller for the System 9740 Matrix switching system. Althoughthe CM9740-CC1 has a smaller hardware footprint than the CM9760-CC1, it can, with its9740 specific executable software, interface the same peripheral mix that the CM9760-CC1 does, but on a reduced scale. In fact, the CM9740-CC1 can be installed as a node in amulti-node 9760 system, if desired.

In this manual, we attempt to meet the diverse needs of the user for information by discuss-ing the most common type of configuration in which the CM9740-CC1 can be found. Thisconfiguration type, referred to here as Category I, is discussed further in the next section.

2.2 MANUAL LAYOUT

The topics touched on in Section 3.0 are important for the user to be familiar with in order togain the most benefit from the discussions that take place later in Sections 5.0 and 6.0. Thephysical aspects of the CM9740-CC1 are discussed in Section 4.0. Section 5.0 discussesinstallation configuration scenarios, and Section 6.0 is concerned with controller initialization.

The basic installation type, which we refer to as Category I, is discussed from the stand-point of the CC1 as being (1) part of a New System Installation and (2) as an indi-vidual CC1 Replacement Installation within an existing system installation. We dontexclude upgrade scenarios in our discussions, by which we mean that an existing systemsoftware and/or hardware mix (of which the CC1 is a par t) is upgraded to a newer version.

The Category I case is emphasized throughout and in more explicit detail with respect tothe subtopics mentioned above, because, in most cases, one can extrapolate CC1 behaviorthere to more involved configurations.

Section 6.0 discusses initialization and what happens or shouldhappen when the CC1 is powered on for the first time. We discussvar ious elements of system configuration, how they interact and thepart the CC1 plays in it. What should happen, what can happen, andwhat to look for during initialization are also explored. Next, diag-nostic screen functions, diagnostic key commands and those as-pects of the MGR program that affect CC1 integrity are explored.

Finally, we briefly list some of the more common problems encoun-tered dur ing initialization and suggest possible corrective action.

At any point in the manual where information appearing in an ap-pendix has a bearing on the discussion at hand, that appendix isreferenced. Based on ones current knowledge and experience,one may or may not feel the need to consult it.

CATEGORY I

CM9740-CC1 | 7

3.0 BEFORE YOU BEGIN

3.1 A BRIEF NOTE

The CM9740-CC1 is a nonexpandable CPU, optimized for systems ranging froma 16 x 4 configuration (16 inputs and 4 outputs) to a 256 x 32 configuration (256 in-puts and 32 outputs).

Beginner or New to 9740If you are totally new to Pelco, or are familiar with Pelco but new to the 9740 ma-trix system, read on.

3.2 FOR THE BEGINNER OR NEW USER,A FEW WORDS OF ADVICE AND SOME EXERCISES

From a hardware standpoint, the CM9740-CC1 is ubiquitous to 9740 System op-eration. Section 4.0 addresses that aspect of the CC1.

In addition to its physical prominence, the CC1 is central to the software tasks re-quired within the 9740 System. These tasks include configuration, initialization,and system control in operational mode.

Normally, CM9740-CC1 installations are problem free and follow an installationscenario that proceeds as follows:

1. Everything is assembled together for the system configuration according tothe provided roadmap, which exists in the form of port assignment sheetsthat tell you how everything physically relates to everything elsewhat deviceis attached to what port, and so on.

2. After all equipment and cables are installed and everything is finally hookedup, the power is turned on.

3. The system initializes.

Setup is complete and operation can begin. At some later point in time, however, ifthe existing system configuration needs to be changed, upgraded, or downgraded,then no matter how simple or complex your system is, there are two areas relatedto system software with which one should become thoroughly familiar:

The directory structure of the CC1.

The administrative extension of the system executable (the MGR* program)and the configuration files (flat files)** that comprise your specific system.

If you are not familiar with these two points, we encourage you to take the timeNOW, rather than be forced by necessity later, to become familiar with these twoitems.

Its easy. Very little equipment must be connected. Your entire system does nothave to be connected, nor does it have to be up and running to perform the twoexercises that discuss these topics. If the previous statement applies in yourcase, or if you are responsible for implementing system configuration changes,then consult Appendix VII, which guides you through the entire process.

* MGR: The MGR program is an admin-istrative extension of the 9740 executable.The executable resides on the hard driveof the CC1; the MGR program, when inuse, resides on an external PC connectedto the CC1.

** FLAT FILES: Flat files are informationfiles based upon your particular systemconfiguration that the system executableuses to know what its connected to andhow to talk to it. These flat files are createdat the factory for your particular systemconfiguration. For multi-node systems, a setof configuration files is created for eachnode (each node has its own CC1). TheCM9740-CC1 cannot be used to constructmulti-node systems. It can, however, ap-pear as a node within a multi-node sys-tem. These flat files can be found in twodifferent locations: (1) on the CC1 harddrive in the C:\9740 directory and (2) onthe floppy disk labelled Utilities.

8 | C1508M-A (02/01)

4.0 INTRODUCTION TO THE CC1

4.1 DESCRIPTION

The CM9740-CC1 Controller is the main component and central operating hub of the Sys-tem 9740. All components of the system connect to and communicate with the Controllervia the ports located on the rear of the unit.

The CM9740-CC1 Controller mounts in a standard 19-inch (48.26 cm) rack space.

NOTE: The internal cards are manu-factured or supplied by Pelco and con-tain no user-serviceable parts. Otherthan jumper settings or card replace-ment, any attempt to repair or modifythe internal components of theCM9740-CC1 will void any applicablewarranties.

Default Hardware Configuration

a. 3.5-inch Floppy Driveb. Solid-state, non-volatile, flash memoryc. CPUd. Mounting hardwaree. Keyboardf. Mouseg. 2 SerCom cards

Figure 1CM9740-CC1 Front View

4.2 MODEL

CM9740-CC1 CPU controller and processor, operates on 120-240 VAC, 50/60 Hz.(CE, UL, cUL)

Front ViewThe front area of the controller consists of the items identified in the illustration in Figure 1:

The CM9740-CC1 Controller is equipped with an internal power supply that provides all theoperating voltages for the unit. * Cooling for the processor is provided by a CPU-mountedfan.

* The power socket outlet shall be installed near the equipment and shall be easily accessable.

CM9740-CC1 | 9

Rear ViewThe rear of the controller appears as illustrated in Figure 2.

This is the business end of the CM9740-CC1.

Figure 2Rear View, General Identification

(RS-232 Wiring Connection between the CC1 and an External PC)

RXRXTX

TX

Refer to Figure 3 for COM port pinout identification

10 | C1508M-A (02/01)

4.3 SERCOM BOARD CARDS

Sercom Card installation at the factory configures the Sercom cards for the slot position lo-cations they occupy in the unit.

Once you have an operational system, you can cycle through your IRQ/Slot position set-tings by toggling the ALT + A key combination on the keyboard associated with the diagnos-tic screen.

4.4 MOUNTING THE CONTROLLER

The CM9740-CC1 Controller mounts in a standard 19-inch rack using standard mountinghardware (supplied with the unit). The unit occupies 3 RU (5.25 inches [13.34 cm]) of verti-cal rack space.

Before installing the unit, decide on the equipment orientation desired within the EIA rackand install the moveable ears on the unit accordingly. Secure as required.

WARNING: Un-plug the CC1 beforeattempting to install

or remove any of the indi-vidual components. Failure todo so could result in seriousdamage to the equipment.

CM9740-CC1 | 11

4.5 CONNECTING TO THE CONTROLLER

All system devices connect to the rear of the CM9740-CC1 controller. In general, any con-nectable device that can be used with the CM9760-CC1 can also be used with theCM9740-CC1.

D-type, 9-pin connectors are used for COM 1 and COM 2, while the VGA card connector isa 15-pin D-type connector. The PS/2 keyboard connection utilizes a standard 5-pin mini-Dinconnector.

The printer connector (used mainly for system logging and printouts) is a 25-pin D-typeconnector. A completely operational System 9740 will more than likely require the additionof more equipment to the controller; namely, such items as a VGA monitor, or a PS/2 keyboardand printer. To connect this equipment, simply plug the desired piece of equipment into theappropriately labeled port. For connector information, refer to Figures 3 and 4.

Figure 3CM9740-CC1 Rear Connector Pinouts

NOTE: When a Sercomport is used to interfacemultiple receivers, thedistance D between thepick-off points and anyreceiver should be 3 feet(.91 m) or less

D (see note)

Figure 4Multiple Receiver Hook-up

12 | C1508M-A (02/01)

5.0 PHYSICAL INSTALLATION AND INITIALIZATION

5.1 CC1 INSTALLATIONCATEGORY I

PreliminaryFor new installations, you normally receive a configuration setup or dia-gram and a por t assignment sheet for your specific installation. Pay closeattention to these when setting up your system.

Items specific to CC1 production for units leaving the factory include the following:

1. Configuration files (flat files) that correspond to your specific systemconfiguration are created and exist, as a set, in two locations. One setis located within the C:\9740 directory on the drive of the CM9740-CC1.The other backup set is located on a floppy disk labeled Utility Disk.

2. The directory structure of your drive has been set up and includesthose items alluded to in Section 3.2 and discussed in detail in Ap-pendix VII of this manual.

3. The MGR program, which is a software extension of the 9740.EXE,exists on a five-unit floppy disk installation set that accompanied yourunit. This program should be installed on the external PC that will beconnected to COM 1 on the rear of the CC1. The MGR programshould be loaded on the external PC and the PC should be connectedto the CC1 before any power to the CC1 is turned on in preparationfor the initialization process. The inclusion of MGR operability is not anecessary component of the initialization process; however, its exclu-sion would mean the loss of a valuable tool for viewing, verifying, andprobing various aspects of that process.

5.1.1 Category INew Installation1. CC1s are normally installed in close physical proximity to matrix bays,

as these are the first items to be connected to the rear of the CC1, start-ing at Port 5 on the rear of the CC1.

Keyboards are installed after matrix bays; then, after that, everythingelse is installed on a next available port basis according to the portassignment sheets.

2. If the MGR program is to be used, it is installed on an external PCconnected to COM1 on the rear of the CC1. The cable between theexternal PC and CC1 is not supplied by Pelco. Use the convenientpinout information given in Figures 2 and 4 for wiring up the cable. If youfollowed the exercise for the beginner referenced in the first part of themanual, you have already installed the MGR on an external PC. If thatis not the case or if you wish to use a different PC, then the MGR pro-gram must be installed on the PC at any point before power is appliedto the system. Use the quick-star t installation guide in Appendix I toinstall the program on the external PC.

3. Connect the external VGA PC monitor to the VGA por t provided on therear of the CC1. This will display your diagnostic screen.

4. Once you are satisfied with the physical hook-up of all peripheral de-vices and have double-checked all communication parameters andswitch settings, you are ready to do the following:

a. Turn on power to all peripheral equipment connected to the CC1.**

b. Apply power to the CC1.

5. Proceed to the Section 6.1, which discusses system initialization forsingle-nodes.

The next example is that rare case where the act of having saved a cur-rent copy of your configuration files (flat files) can save you a lot of work.

Figure 5Category IBare Bones

Figure 6Category IFleshed Out

NOTE: Remember that each peripheral deviceis unique and has its own requirements. If ques-tions arise with respect to any of the parametersfor an individual piece of equipment, it is impera-tive that you consult the manuals for the devicein question.

**Note that video paths are independent of the9740.EXE being in operational mode. The factthat pictures appear on monitors when periph-eral equipment is turned on does not meanthat the system is operational. It is a neces-sary item for proper system operation, but hasnothing to do with system initialization.

CM9740-CC1 | 13

5.1.2 Category IUpgrade Replacement (Hardware Only)Object: Physical Replacement of the CC1

Assumptions: The CC1 to be replaced is part of an existing operational system configu-

ration that has failed.

The software environment that existed on the failed CC1 is to be used onthe replacement CC1.

To physically replace the CC1:1. Shut down any parts of the system that are running and turn off power

(where applicable). We assume here that the failed CC1s power is al-ready off.

2. Disconnect all peripheral equipment from the failed CC1, noting what isconnected to what.

3. Connect a PS/2 keyboard to the replacement CC1 and power it up inde-pendent of the system to which it will be connected.

4. Take your most current copy of configuration files (flat files) for the systemin question and copy them to the C:\9740 directory on the hard drive of thereplacement CC1. If you dont have a set, you are going to have createone from scratch.

5. The 9740.EXE that exists on the replacement CC1 will be configured withthe latest revision of system software.

6. When power is applied to the replacement CC1 in step 3, it should boot tothe diagnostic screen after loading system files. This is a reflection of thestandard factory configuration of the autoexec.bat file and nothing else.

NOTE: You can choose to edit and effect changes in the autoexec.bat fileafter the system is hooked up and power is turned on. If you do, just keepin mind that the following instructions assume that you have alreadymade the changes referenced.

7. Once you have loaded a copy of your current configuration files, the oldexecutable and the adjusted autoexec.bat (if applicable) on the new CC1,turn off power to the CC1.

8. Replace the old unit with the new CC1 and reinstall, connector for con-nector, all peripheral equipment disconnected in step 2.

9. Turn on power to all the peripheral equipment and to the new CC1. Checksystem initialization and look for system errors. Correct any found, andthen, again, save to disk any copies of your configuration files and anyother files that you dont want to have to create or scrounge around forshould similar circumstances occur in the future.

NOTE: Normally, one thinks of hardwareand software as separate entities and thatupgrading or replacing one would not sig-nificantly affect the upgrade or replacementof the other. For new system configurations,this is not a problem. Areas of concern doarise, however, when upgrading or replac-ing existing units within systems that areout in the field. If the replacement equip-ment contains preloaded software (for ex-ample, the CC1) or contains programmedROMs (for example, the CM9760-KBD),care must be taken. You must make a rea-sonable effort to ensure that the newhardware and the software it contains arecompatible with the system within whichit is to be placed.

NOTE: You should always save your oldexecutables and flat files, along with yourautoexec.bat file, in case the upgrade in-stallation doesnt pan out.

NOTE: You should always have a list ofthe current version levels of all the soft-ware that you are running on your systemor at least know where to find the informa-tion. In general, its best to make a list assoon as possible after receiving new soft-ware or equipment containing software andkeep the list current.

The list would include version informationon the following:1. The CM9740.exe2. The 9760MGR software3. The CM9760-KBDs

14 | C1508M-A (02/01)

5.1.3 Category IUpgrade Replacement(Hardware and Software)

Object: Physcial replacement of the CC1, in conjunction with software upgrade or re-placement.

Assumptions: The CC1 to be replaced is part of an existing, operational, system configuration.

The operational software within the existing CC1 needs to be replaced and/or up-graded, depending on circumstances covered in the steps below.

1. Repeat steps 1, 2, and 8 of the previous section, ignoring remarks about CC1 status.Do not, however, reconnect the external PC (containing the MGR program) to thenew CC1 just yet.

The status of the new CC1 and its associated software files are as follows:**

The latest 9740 executable will reside in the C:\9740 directory on the drive of theCC1. Backups of the executable are on the Operations and Utility disks that ac-companied the shipment of the replacement CC1.

A five-disk set of the latest MGR program also accompanied the shipment.

2. If the software version of your current MGR program is less than that of the MGR pro-gram in the upgrade package, then the latest MGR software must be installed on yourexternal PC.

To accomplish that, do the following:

a. Remove your old MGR software according to Appendix V.

b. Install the new MGR software using the five-disk set of the System Manager. Usethe quick-start guide located in Appendix I of this manual for instructions.

3. Connect any new equipment that is part of your hardware upgrade to the appropriateport(s) on the rear of the CC1, according to the installation instructions found in themanual(s) accompanying the new equipment.

4. If the equipment connected in step 3 requires updates to your existing configurationfiles (which it will if the hardware portion of the upgrade necessitated the use of anyadditional Sercom ports), then do the following; otherwise, proceed to step 6:

a. Power-up the external PC containing the MGR program and use the READ utilityto read in your existing configuration set (flat files) into the MGR program (refer toAppendix IV, if needed).

b. Make the necessary changes in your current configuration files to accommodateany new equipment. As part of those changes, dont forget to enter a PIN for thenew equipment in the COMMS file and to assign operator access. Consult theapplicable device manual and the MGR documentation as needed until all the pa-rameters that need to be changed are taken into account.

c. Save your updated flat files to the database and then use the WRITE utility of theMGR program to write out the changed configuration set to floppy disk.

d. Copy the new configuration set into the C:\9740 directory of the new CC1 (referto Appendix II, if necessary).

5. Reconnect the external PC containing the upgraded MGR software to the new CC1and load the upgraded configuration set into the C:\9740 directory of the new CC1.Proceed to step 7.

6. Reconnect the external PC containing the upgraded MGR software to the new CC1and load your existing flat files into the C:\9740 directory of the new CC1.

7. Repeat step 9 of Section 5.1.2.

**IMPORTANT NOTEIf you are doing an across-the-board upgrade of the systemsoftware associated with theCC1 (namely, the MGR programand the system executable),then any CM9760-KBD usedwith the upgraded system mustalso contain software that iscompatible with the upgrade.

CM9740-CC1 | 15

5.1.4 Category IUpgrade Replacement (Software Only)Object: To upgrade current system software to the latest available.

Assumptions: Youre currently running a fully operational CC1 to which is attached an external PC

containing the MGR program.

You have ordered the current software upgrade package for the CC1.

You have also ordered (if applicable) compatible keyboard software for use with thesystem software upgrade (CM9760-KBD-XXX).

To upgrade your system software:

1. Halt system operation (if applicable) with the familiar Ctrl + Q key combination.

2. Replace the old MGR program on the external PC with the upgrade MGR program bydoing the following:

a. Remove the old MGR program, following the instructions in Appendix V.

b. Install the new MGR program using the quick-start guide in Appendix I.

3. Use the READ utility of the justinstalled MGR program to read in a copy of your cur-rent configuration files.

4. Effect any changes desired, save the files to the database and use the WRITE utility towrite a copy of your configuration files to floppy disk. Make sure you continue to usethe same global prefix name for your configuration set that you used before or you willhave to change your autoexec.bat file later.

5. Copy the new configuration set to the C:\9740 directory on the hard drive of the CC1and overwrite any files existing there.

6. Copy the latest system executable (CM9740.EXE) [located on the Utility Disk] andoverwrite the old executable located in the C:\9740 directory of the CC1.

7. Upgrade the keyboard software (if applicable) using the appropriate KBD upgrade kit.

8. Attach all equipment not yet connected to the CC1.

9. Power-up all peripheral equipment; turn on the CC1.

10. Initialize the system and check for errors.

16 | C1508M-A (02/01)

6.0 CC1 INITIALIZATION

The initialization process occurs during the time that the CM9740.EXE program is bootingup. During this time configuration files and diagnostic programs are loaded enabling systemparameters for CCTV matrix operation. As the initialization process proceeds, the execut-able calls for its associated diagnostic and corresponding information screen. The primaryvisual verification of successful initialization is signaled by the information displayed there.That, and other indicators of successful initialization (for example, the 9760 KBD LCDscreen and the Manager system window, which are both discussed in the next section) givea range of items to check to verify successful initialization.

In the absence of perfect system initialization, what you hope to see is verification that thesystem is a least up and running. Small problems might be indicated by system messagesother than the one you wanted to see, but you are essentially in business.

6.1 SINGLE-NODE INITIALIZATION

As just discussed, normal initialization is the result of a successful boot process, which,more often than not, ends with a display of its associated diagnostic screen indicating suc-cess. It will do this either because (1) it was configured that way at the factory or (2) be-cause the autoexec.bat file was edited by the user to call the appropriate executable duringthe boot process.

6.1.1 Diagnostic ScreenInitialization begins when the CC1 is turned on (we assume all peripheral equipment ispowered on). The boot process executes as a standard DOS boot. When the executable inthe autoexec.bat file is called, a bare outline of the diagnostic screen appears on the attachedmonitor. A syncopated series of messages appears in the System box until the processends and, if successful, a Setup Complete diagnostic screen like that shown in Figure 7appears.

Figure 7Single-Node Initialization

6.1.2 KeyboardWithin your system configuration, you may also haveother devices connected that give online system indica-tions, some more helpful than others.

For example, consider the CM9760-KBD. If you haveone attached to your system, the LCD screen displaywill look as follows before the system boots:

When the system boots, and initialization is com-plete, the keyboard LCD display will change fromthe above LCD screen to the following one:

The keyboard will go through this display process re-gardless of the type of configuration to which it is con-nected.

SYSTEM 9740 v7.8

CM9740-CC1 | 17

6.1.3 MGR ProgramSystem Window

That leaves the MGR system window, which ispart of the MGR program proper. If you have anexternal PC connected to the CC1 that containsthe MGR program, there are multiple indications ofonline status associated with this program that canbe checked.

Just before the boot process, have the MGR pro-gram up and running with the system window show-ing. Click on the SysWindow icon as indicated inFigure 8; the window should be blank. If it isnt,close the system window and answer No to thedialog inquiry about retaining current system win-dow messages. Then, reopen the window and itwill be blank. At the end of the initialization processwhen the Setup Complete message appears onthe diagnostic screen, a corresponding display in-dicating system status will appear in the systemwindow of the MGR program, like that shown inFigure 8, indicating that the system is up andonline.

6.1.4 Configuration FileIn addition to the SysWindow message regardingonline status, you can click on the 9760 Setupicon on the MGR program toolbar, which will bringup the Configuration Files dialog box (refer toFigure 9). On the far right side of the line indicat-ing the Node # and the group configuration filename associated with that node is another indica-tion that the system is online. The word Onlineappears, as shown in Figure 9. A dash , nor-mally occupies that spot when the system is notonline.

Figure 8InitializationSystem Window

Figure 9Initialization Configuration File

18 | C1508M-A (02/01)

Figure 10InitializationOnline Nodes

Figure 11MGR WindowsA Precaution

6.1.5 Online Node Dialog BoxIf you close the Configuration File menu and click onthe Nodes icon on the MGR program toolbar, youwill see what appears in Figure 10.

This indicates the node number and the associatedgroup flat file name associated with the node cur-rently online.

The Configuration File window still indicates the system asbeing online. You must close the Configuration Filewindow and cycle the Filter Sys icon on theMGR toolbar to update systeminformation.

A CAUTIONARY NOTEBe aware when looking at secondarywindow dialog boxes. The Online

Nodes box and the Configuration Files box,for example, are windows that are not dynami-cally updated by the MGR program whenever ad-ditional changesother than the one currentlypostedhappen in the online environment. TheSysWindow of the MGR program, however, isdynamically updated.

To show this, look at the diagnostic screen of Fig-ure 7. If you exit the program with a Ctrl + Q keycombination, the diagnostic program ends andyou immediately revert to the system prompt.

At the same time, on the external PC containingthe MGR program, the SysWindow mirrors theoff-line status as shown in Figure 11. It is dynami-cally updated. On the other hand, the Configu-ration Files subwindow still indicates that thesystem is Online. It is not dynamically updated.The same is also true of the Nodes Dialog box,if you were to look at it.

To update the Configuration File box or theNodes Dialog box to reflect the current stateof online status, you must close their respectivewindows and perform the following step:

Click on the Filter SYS icon on the MGR tool-bar. Clicking on this icon opens up the MessageMapping window. Opening and closing this win-dow causes an update of system information be-ing reported to the MGR program.

It is best to think of the information contained inthese subwindows as snapshots of the state ofthe system at the time they are opened.

CM9740-CC1 | 19

6.1.6 Single-Node Hot Switch ConfigurationsRefer back to Figure 7 and note the information in the lower right-hand corner of thediagnostic screen. Specifically, note the A OFF phrase. This means AsynchronousOFF, which means the CC1 is not part of a hot switch configuration.

If, however, the CC1 is part of a hot switch configuration, that portion of the diagnosticscreen represents the state of the CC1 being visually sampled at the time. This, inturn, depends on the switch settings on the processor board located in the hot switchinterface. You might see any one of the four different diagnostic screens displayed inFigure 12 at the conclusion of CC1 initialization. However, this would be the only areaof difference in the diagnostic display to indicate that the boot up initialization processhad been successful. MGR program displays for hot switch configurations are thesame as those already discussed.

Figure 12Single-Node Hot Switch Configurations

NOTE: The diagnostic monitor andthe external PC containing the MGRprogram are attached to the hot switchinterface CM9760-CCS-PNL.

NOTE: In the diagrams below, thehot switch terminology referencesmean the following:

A = AsynchronousS = Synchronous

SLV = SlaveMST = Master

20 | C1508M-A (02/01)

7.0 CC1 CONTROLLER OPERATION

The center of 9740 system operation is the CC1 controller.

Monitoring operations and performing housekeeping chores are important par ts of main-taining the CC1 and system integrity. First, we will discuss the tools used to monitor CC1operation in general; then, we will discuss specific examples. Later, we will talk about systemtime and its relationship to maintaining system integrity.

7.1 MONITORING CC1 FUNCTIONS

The diagnostic screen on the VGA monitor and the SysWindow of the MGR program lo-cated on the external PC are adjuncts of the controller that are used for monitoring systemfunctions and errors. In most single-node applications, the VGA monitor and associatedkeyboard are connected, respectively, directly to the VGA port and keyboard connector onthe CC1.

Similarly, the MGR program and its associated SysWindow, as well as other useful dialogwindows, are located on an external PC and connected to the CC1s Comm port.

For multi-node configurations (the CM9740-CC1 can be configured as a node in a multi-node system), the VGA monitor (for the diagnostic) and the external PC containing theMGR program are attached to the CC1 containing the NIU.

To avoid confusion over equipment configurations and the type of display screen you canexpect to see on monitors attached to specific points within a configuration, refer to Figure 18.

7.1.2 The Diagnostic ScreenOnce initialization takes place, the multi-node diagnostic screen is rather passive; it sitsthere unless system status changes. Nothing will change on the display screen. The single-node diagnostic screen, however, is a bit more engaging.

DescriptionYou have already seen how the diagnostic screen is used to observe system functions dur-ing CC1 initialization.

Moreover, at the end of the initialization process, the VGA monitor diagnostic displays aSetup Complete message on the System box (or the System Error line as it sometimescalled) of the screen. Information pertaining to system errors appear here, as well as infor-mation pertaining to system operation. In addition, the results of PC keyboard commandsappear here, which well discuss later.

Initialization will occur any time that the CC1 goes through the boot process. That happenswhen any of the following circumstances occur:

1. When power is cycled on the CC1.2. When the reset button is pressed.3. When an Alt + Ctrl + Delete key combination is invoked.

CM9740-CC1 | 21

Figure 13Display Screen Geometry

22 | C1508M-A (02/01)

In addition to the area of the screen where the System box appears, there are two other ar-eas of significance on the diagnostic screen. Refer to the sample diagnostic screen in Fig-ure 14.

First, there is the GPI and Ax (short for Aux) box located in the lower left-hand portion of thescreen.

GPI displays the GPI currently selected (if applicable). The GPI number will be updatedwhen an auxiliary command is executed.

Ax displays the auxiliar y currently selected and whether it is ON or OFF.

Second, there are eight identical Monitor boxes.

Each Monitor box represents a monitor and the camera currently being displayed on thatmonitor. The information displayed within each monitor box is detailed by the numbered ref-erences in Figure 14.

We might point out some other miscellaneous information areas associated with the diag-nostic screen. Below the ver tically placed PELCO CM9740 logo, on the right side of thescreen, there is a boxed area within which information is given about the CC1 and its rela-tionship to hot switch configurations. The term A OFF means your CC1 is not part of a hotswitch configuration. The A stands for asynchronous. If the CC1 is part of a hot switch con-figuration operating in asynchronous mode, then it may read A SLV or A MST. The normalstate for hot switch operation is, however, the synchronous mode, in which case you wouldsee S MST or S SLV depending on hot switch parameters. Directly below this, the currentversion level of the system executable is listed using the format Ver xxx xxx.

That concludes the general description ofthe layout of the diagnostic screen. Next,well look at a few examples of what youmight see on the monitor boxes andshow you how to change monitor box al-location. Then, we shall list some key-board commands that are used to gatherspecifics on system operation.

Figure 14Diagnostic Screen and Monitor Box Geometry

CM9740-CC1 | 23

7.1.2.1 Monitor Box ExamplesFigure 15 shows a normal online diagnostic screen. If a CM9760-KBD connected to thesystem is using monitor 4 for camera display, the FWD and BWD buttons on the keyboardcan be used to cycle through the available cameras. On the diagnostic screen, the corre-sponding cameras numbers cycled on the keyboard are mirrored in the numbered displayfor the camera in the diagnostic screen. As each camera is cycled, the ident associatedwith that camera also appear and the monitor box color changes. This is indicated in the il-lustration.

If a camera capable of presets, such as aSpectra II were connected, then the moni-tor box would look like that shown in Figure16, which shows that a preset call was madefrom the keyboard.

Unfor tunately, more advanced functions likepattern or zone activity are not reflected inthe diagnostic display. Your normal PTZ func-tions, presets, and so forth will have theirfunctions identified by some activity in the di-agnostic screen monitor boxes.

For example, if you issued a preset call forthe camera depicted in Figure 16 to go topreset 41, the diagnostic screen would lookthe same except the number 41 would re-place the number 21. This would occur even ifyou had never programmed the camera forthat preset. So be aware of this when inter-preting the meaning of what you see on thediagnostic screen.

Figure 16Monitor Box Preset Call

Figure 15Monitor Box Camera Switching

A CAUTIONARY NOTEThe diagnostic screen only indicatesthat a message or action was sent by

the CC1 to an affected device in response to,for example, a keyboard command to send acamera to a preset. It does not confirm, in fact,that the action actually occurred.

24 | C1508M-A (02/01)

7.1.2.2 Monitor BoxAllocation

Monitor boxes can be re-allocated. To do so,perform the following steps:

Press one of the Fx keys (F1 through F8,as illustrated in Figure 17, show the relation-ship of the Fx key and Monitor box alloca-tion) that corresponds to the number of thebox that you wish to move a monitor too.Take the F1 monitor position, for example.When F1 is pressed, the System box willread (refer to Figure 18):

Allocate Box 1 to ?

Type in the number of the box containing themonitor that you wish to move there.

Allocate Box 1 to? 3

Press the Enter key(Refer to Figure 19)

Box 3 will become blank and Mon 3 will nowappear in the box for the Mon 1 position. TheSystem Box will now display the following:

Box 1 allocated to Physical Monitor 3(Refer to Figure 19)

You can now allocate vacated Box 3 for Mon 1(which is now not represented on the diag-nostic monitor)in effect exchanging the posi-tions of Mon 1 and Mon 3 displays on the di-agnostic monitor; or, you may press the F3key and reallocate Box 3 to a different moni-tor position altogether. To perform the first op-tion, press F3 key and the System box willread:

Allocate Box 3 to ?

If you enter 1, then the diagnostic screen isagain complete, with eight monitors repre-sented and with the MON1 and MON3 dis-play positions switched (refer to Figure 20).

Figure 18Monitor BoxF1 Allocation

Figure 19Monitor BoxAllocate 3 to 1

Figure 20Monitor Box Switch

Figure 17Monitor Box Allocation

CM9740-CC1 | 25

7.1.2.3 Screen OperationKeystrokesThere are a number of helpful screen functions associated with certain keystroke combinations that result in a process being en-abled or result in information being obtained. You have just seen how the Fx keys are used to reallocate monitor boxes. Those, aswell as other key combinations, are listed in Table A.

Table ACommand Key Functions

NOTE: Be careful when using the ALT key in combination with other keys. Keyboard lockup can occur if you press an oddkey combination.

26 | C1508M-A (02/01)

A number of these key combinations are quite helpful. Below we illustrate the diagnosticscreens of some when the referenced key combination is invoked.

ALT+V ALT+A ALT+N ALT+J

There may be times when an error message appears on the System box (System Errorline) that might be due to system noise or other temporary communication problems. Toseparate genuine from occasional hits, press the spacebar. Pressing the spacebar clearsthe System box. If the error message is transient, it will not reappear again. If it does, theninvestigate the possible source of the error.

Figure 21Keys CommandExamples

7.2 SYSTEM TIME

7.2.1 Setting and Adjusting System TimeFor Single-NodeOne special key combination is ALT + L, which is used in the process of making adjustmentsto system time. System time is one of the onscreen attributes that appears on all displayswithin a system. How the time is displayed is set up in the System configuration file; howtime is set or changed is discussed here.

Single-node setup or adjustment of system time is functionally the same as that followed formulti-node setup of system time. For single-node operation, the single-node diagnosticscreen is used.

Determine your current global configuration file name (if you dont already know it) by in-voking an ALT + N key combination command. You will need that piece of information later.

CM9740-CC1 | 27

To adjust the time:

We first synchronize the system clock (this is the clock kept by the DOS operating system)to an RTC (a Reference Time Clock). We then let the system run for 24 hours (or a multipleof 24 hours, if necessary). We then compare the system clock again with the RTC and noteany difference. We then synchro-nize the system clock with theRTC again and then enter a timecorrection to the system clockbased on our earlier observation.To accomplish this, do the following:

1. Exit the diagnostic programwith the Ctrl + Q key combi-nation. This should take youto the C:\9740> prompt.

2. At the DOS prompt, enterthe TIME command. The dis-play should be similar to thatshown in Figure 22.

3. Enter a time using the timeformat displayed on the DOSscreen xx:xx:xx:xx (a or p forAM or PM, respectively).

4. Use an RTC time acceptableto you as a reference (thismay be an accurate digital watch, or, more than likely, a call on your phone to a local timereference). When the top of the hour is reached by the RTC, press the ENTER key onyour keyboard.

5. Proceed to the C:\9740 directory, if not already there. DO NOT REBOOT IN ORDERTO GET BACK TO THE DIAGNOSTIC SCREEN. This would interfere with the timesetting you just made to the system clock.

6. While in the C:\9740 directory, invoke the system executable using the configurationfile name obtained earlier with the Alt + L key combination. Assuming a file name ofTEST, the command line would look as follows:

C:\9740>CM9740 TEST

This starts the system executable and takes you to the diagnostic screen. The time youentered in step 4 will be displayed on all monitors in the system after initialization iscomplete.

7. Twenty-four hours later, check the system time against the RTC time by comparing thetime displayed on any monitor screen in the system against that of the RTC. Make a noteof this difference in time.

8. Repeat steps 1 through 6, ending up at the diagnostic screen (repeating steps 1through 6 synchronizes system time with RTC time again). This time, however, enteran ALT + L keyboard command in preparation for making an adjustment to system timebased on your observation in step 7. The System box (System Error line) will read asfollows:

System : -Last Adj 0 : 0 . 0 Total 0 : 0 . 0Enter a time using the following format:MM : SS . HH [Minutes : Seconds . Hundredths of a Sec.] based on the time differ-ence between RTC and system time that was noted in step 7.

NOTE: Since system time is dis-played on Monitor screens in for-mat variations based on the (HH/MM/SS) for mat, you will neverhave occasion to enter adjust-ments in the hundredths of a sec-ond field in response to the ALT +L diagnostic command line screen.

Figure 22Time Synchronization

NOTE: The best way to pre-pare for the synchronizationprocess is to star t the proce-dure just before the top of thehour, set your new time valueto equal it and then wait for yourreference time to approach thattime and, when it does, pressthe ENTER key, synchronizingsystem time with RTC time. Seethe sample DOS screen repre-sentation in Figure 22.

28 | C1508M-A (02/01)

For example, if system time in step 7 had read 2:02.30 (2 minutes and 30 seconds after2 PM) at the time RTC time read 2 PM, then we know that system time, over the next 24hours, must be slowed by 2 minutes and 30 seconds to synchronize system and RTCtime. To accomplish that, enter a negative (-) sign in front of the time differential that youenter. In this case, that would be:

-02 : 30 . 00

This subtracts 2 minutes, 30 seconds from system time over the next 24 hour time periodso that when you compare system time with RTC time again, they should theoretically beequal. Be sure to use the above format.

If you wish to refine the adjustments to your original effort, you can quit to the DOS screen,set RTC and system time to be equal to each other, invoke the executable for the diagnosticscreen from the C:\9740 directory, and then use your original time adjustment (in our example-02 : 30 . 00) as a basis for entering a new time adjustment that differs incrementally fromthe original. That might work based on something like the following reasoning: Say that fivedays (five 24 hour periods of time) have passed and you again check system time againstRTC time. This time you discover that over the five-day period, you are running 10 secondsslow, or, on average, 2 seconds slower for each 24 hours of elapsed time. This time youmust change the original time adjustment by ADDING 2 seconds to the original, NEGA-TIVE time adjustment.

In order to factor in the new adjustment, you should perform the following steps again, pref-erably, just before the top of the hour:

1. Quit the diagnostic and revert to the DOS screen using Ctrl + Q.

2. Invoke the DOS line commandTIMEto bring up current system time.

3. Pre-enter your system time to read top of the hour time. For our example, continue to use2 PM as RTC time, so at the NEW TIME prompt on the DOS screen, you would enter:

2:00:00.0p

When RTC time reaches 2 PM, press the ENTER key, proceed to the C:\9740 direc-tory and invoke the system executable, which includes your global configuration file-name as an argument, (CM9740 TEST, for example) and boot to the diagnostic screen.

4. At the diagnostic screen, issue the ALT + L key combination.

5. On the command line, the following should appear:

Last Adj -2 : 30 . 0 Total -2: 30 . 06. Now enter in your refined time adjustment as a change to the last adjustment shown

on the screen. In this example, you would enter the following:

-2 : 28 .0

that is, [(-2 : 30 . 0 ) + (00 : 02 . 0)] = -2 : 28 .0

7. After pressing the ENTER key, the System box will read

Last Time Adj -2:28.0 Total -4:58.0Subsequent adjustments, if necessary, can be made using the previous discussion asa guide.

7.2.2 General Remarks Regarding System Time AdjustmentWe have just discussed setting and adjusting system time for single-node operation. How isthis accomplished for other configurations?

For a hot-switch configured node, the CC1s are synchronized through the intermediation ofthe hot switch. Setting or adjusting time on one CC1 will, when it is brought back online andput in synchronous mode, cause the time adjustment to be synchronized for both CC1s.

CM9740-CC1 | 29

For multi-node situations, time adjustments are carried out utilizing the CC1 containing theNIU. The NIU, in turn, provides to the rest of the network the parameters for displaying sys-tem time. The time for the system is updated each minute by the NIU, which, of course, isinitially adjusted to RTC by the user. If the NIU goes offline, each node rever ts to its own in-ternal system time.

7.3 CC1 SYSTEM INTEGRITY

Right now, we want to cover one of the more important aspects of maintaining CC1 systemintegrity. Specifically, this deals with keeping the configuration sets that reside in the data-base of the MGR program and the configuration sets that exist in the C:\9740 directory onthe drive of each CC1, synchronized. The configuration sets that exist in either locationshould be duplicates of each other.

No system is static, changes will occur as equipment is added or moved, which means thatthe configuration files for the node on which this occurs may change. In many cases,changes to existing equipment may require an adjustment to the applicable configuration filethat, in many cases, can be taken care of directly by using the dynamic update processavailable from within the MGR program itself. Of the eleven possible configuration files thatcan exist per node, seven can be dynamically updated. Those that can, are identified by the[Save & Send] bar tab, generally located in the lower left portion of each opened configu-ration file (the textual exception is the System configuration file which reads Save SendSystem Options). The Comms, V.Amp, Macro, and NIU files cannot be dynamically up-dated.

Dynamic updates cause two potential problems that are easily remedied. The first, and moreimportant problem, is the fact that a dynamic updates affect system integrity if you dont fol-low through with a procedure called Updating the Hard Dr ive. The second problem iscaused by the solution to the first. Every time a hard drive update is invoked, you run the riskof losing your original file parameters because the number of updates you can perform arelimited. We will discuss this process in the next few paragraphs.

7.3.1 Dynamically Updating a Configuration FileRefer to the Dynamic Update Block diagram (Figure 23), which shows the process that youshould follow and what occurs every time you do an update to the system. It is very impor-tant to make sure that you maintain the synchronization between the configuration files thatexist in the MGR database and the correspondingfiles that exist on the CC1 hard drive.

Single-node and multi-node dynamic updatesare processed exactly the same way. You firstopen the Configuration File dialog box andselect the node (by highlighting) that containsthe configuration file you wish to update.In single-node situations only one node willbe represented unless you run different con-figuration sets at different times on the sameequipment configuration. Refer to Figure 23.

Click on the Setup Files bar tab which opensthe tabbed set of configuration files for thenode in question.

As an example, we will do a sample update tothe ident field in the monitor file. Click on theMonitor File Tab and perform the followingsteps:

1. Make the desired change to the identfield of the Monitor file.

2. Press the Save & Send tab bar lo-cated in the lower left portion of themonitor configuration file.

Figure 23Configuration File Dialog Box

30 | C1508M-A (02/01)

3. When the Save & Send bar tab is pressed, a splash screen appears and in the Sys-tem Window of the MGR program, the following message appears:

DYNREQ Monitor code OK from Node 1

4. If there are no more changes, close the Configuration dialog window. When you do,the following dialog box appears (refer to Figure 24).

Figure 24Hard Drive Update

5. Click on the Send Update Request bar tab.

6. The System Window of the MGR program will report the following message:

UPDT HardDrv Monitor File OK from Node 1.

At this point you are finished with the dynamic update of your Monitor configuration file. Youhave saved the changes to the configuration file to the MGR database and you have alsoupdated the corresponding configuration file on the node in question; therefore, system in-tegrity is preserved.

CM9740-CC1 | 31

Figure 25Dynamic Update Block Diagram

One more aspect of dynamic updates must be considered. Whenever you click on a SendUpdate Request, the following happens (lets stay with the same example):

a. First of all, the original TEST.MON file, which existed in the C:\9740 directory onthe hard drive of the CC1 whose configuration set we are changing, is not lost,but is saved under the new file name of TEST.MO0. Refer to the Dynamic UpdateBlock Diagram. The change to the TEST.MON file we made when we sent the Up-date Request now occupies the file by that same name.

b. Subsequent update requests to the Monitor file will result in the same scenariobeing played out. TEST.MO0 will move to TEST.MO1, TEST.MON will move toTEST.MO0 and our latest update will now occupy TEST.MON. Each time wepress the Update Request bar tab, the information for the new file will occupy theTEST.MON file and the old file information will be saved to a file of a differentname. This process, however, does not continue forever.

Any TEST.MON updates after TEST.MO2 is filled will cause the original TEST.MONfile we started with to be lost forever. Therefore, if any of the previously displacedconfiguration information is important to you and you wish to save it, then youshould rename the applicable file from TEST.MO0, .MO1 or .MO2 to some othername and save it to another directory or archive it on disk.

/

/

/

32 | C1508M (02/01)

Mismatched baud rate (actually, afterinitialization and Setup Complete thediagnostic line would first report Port xERR Coms Parity followed by theFraming error message.

Failure of Comms line after power upand initialization.

Mismatched parity entry in the Commsfile.

If the communications line is faulty (mis-wired or not seated, for example), then,on initial power-up, the diagnosticscreen will indicate this error message.If the communication line goes bad afterpower-up and initialization, then a Port xERR Coms Fatal error will occurfollowed by a Port x ERR Max Retrymessage.

Temporary communications fault.

Noise on the data line.

Port x ERR Coms Framing

Port x ERR Coms Fatal

Port x ERR Coms Parity

Port x ERR Coms Max Retry

Symptom Possible Cause Corrective Action

Correct the Comms file baud ratesettings to match those of the equipmentit is attached to.

Check and correct hardware fault.

Correct the Comms/configuration file forcorrect settings.

Check and correct the hardware fault.

Fault will automatically be correctedwhen communications resume.

Check data cables.

Table CCC1 System Errors

8.0 TROUBLESHOOTING/COMMON PROBLEMS

In the tables below, some of the more common problems associated with CC1 power up,initialization, and operation are shown. For many of these, we also list possible causesand solutions.

Problems with the CC1 may occur in the following areas: The CC1 itself. Setup files (also known as configuration files or flat files). Peripheral Devices connected to the CC1. The DOS operating system.

It is important that a log be kept of all changes made to the system whether they be hard-ware or software related. The commentary should document the change made, why it wasmade, the date it was made, and the person responsible for the change. That way it will beeasier to backtrack if errors occur. It also makes it easier to separate errors caused by thelast recorded change from other types of errors, whenever one occurs.

Table B lists some common CC1 equipment errors.

Table C lists some common CC1 initialization problems.

Table BCC1 Hardware Errors

There is no AC power to the unit.

Fuse has blown.

Video cable is not seated.Power cord not plugged in.VGA card is bad.

Green Power LED not lit

No VGA display

Symptom Possible Cause Corrective Action

Check power cord connection.

Replace fuse.

Reseat cable.Plug in cord.Replace card.

CM9740-CC1 | 33

APPENDIX I INSTALLING THE MGR PROGRAM

The reason the installation of the MGR program is reiterated here is that the 9740 DOS executable on the CC1 and the Windows 95based MGR program interact. If an external PC containing the MGR program is connected to a COM port on the CC1, the CC1 willreport operational activity to the MGR program where it can be viewed by the operator in the MGR system window. Conversely, theoperator of the system can, through the MGR program, change many of the configuration files of the 9740 online operational pro-gram via dynamic on the fly updates.

34 | C1508M (02/01)

APPENDIX II DOS ENVIRONMENT AND COMMANDREFERENCE

DOS is an acronym for Disk Operating System. Every time you turn onthe CM9740-CC1 or every time you reboot (Alt + Ctrl + Delete), thecomputer loads DOS from disk (the CC1s drive) into memory (RAM).Once loaded, DOS lets you run other programs, in particular, theCM9740.EXE program, which is located in the C:\9740 directory of theCC1. On factory-produced systems, the boot process doesnt end at abasic system prompt (C:\ > ), as would be the case for a normal PC.Instead, the process ends either at the C:\9740> prompt, or else theboot process loads and executes the CM9740.EXE program. The rea-son for this, in both instances, is the result of autoexec.bat file configu-ration. Well examine the details of autoexec.bat configuration, but first,lets look briefly at the highlights of the boot process and how theautoexec.bat file is invoked in the first place.

The Boot ProcessThe following process occurs when the CC1 is turned on or isrebooted:

1. If turned OFF and then turned ON, the CC1 goes through a power-on self-test (POST). Here the computer essentially examines itselectronic components.

2. The computer looks at drive A for a DOS system disk. If one is notthere, the CC1 will load DOS from its hard drive.

3. This process looks for two hidden system files: IO.SYS andMSDOS.SYS. If these files are not present, DOS displays the fol-lowing error message:

Non-System disk or disk error*

(The CC1 will also display this error during the boot process ifyouve left a floppy disk in your A drive that has no system files).

4. If the hidden files are present, IO.SYS loads first and executes.An initialization program called SYSINIT contained within IO.SYSreads in the MSDOS.SYS file; SYSINIT next locates theCONFIG.SYS file and executes its files in order for it to configureitself in memory. Then SYSINIT locates and invokesCOMMAND.COM. If SYSINIT cannot find COMMAND.COM, DOSwill display the following error message:

Bad or missing Command Interpreter**

5. If SYSINIT finds and loads COMMAND.COM, it, in turn, searchesyour root directory for the AUTOEXEC.BAT file. If it exists,COMMAND.COM will cause the AUTOEXEC.BAT file to execute.If AUTOEXEC.BAT doesnt exist, the DATE and TIME commandswill be invoked by COMMAND.COM. After entering date and timeinformation, the basic system prompt (C:>) appears. This com-pletes the startup or boot process.

You cannot separate the boot process from CC1 initialization. The DOSboot process must succeed before the CM9740.EXE program can run.The result of the DOS initialization process is that you are either sittingat a system prompt on a DOS screen or, as part of the boot process,the CM9740.EXE program has been invoked. In the latter case, theSystem Window of the diagnostic screen will read Setup Completeif everything initialized OK; otherwise, an applicable error messageshould appear.

IMPORTANT NOTEGenerally speaking, the CM9740-CC1 that you or-der is configured in one of two ways and dependson whether the CC1 exists as part of a system or-der or whether it has been purchased as a stand-alone unit.

If the CC1 is configured as part of a system, flatfiles are created for the system configuration ac-cording to customer ordered criteria and placed inthe 9740 directory on the CC1 hard drive. TheAUTOEXEC.BAT file is configured to call theCM9740 executable program at the end of the DOSboot process instead of reverting to an onscreensystem prompt. The result is that, at the end of theboot process, the 9740 diagnostic screen shouldappear on your monitor. Assuming you have cor-rectly connected and configured all of the equipmentattached to the CC1, a Setup Complete messageappears in the System Window of the diagnosticscreen.

CC1s purchased as stand-alone units differ in thatthere usually is not enough information with respectto where or how the unit is to be used; therefore,the factory cannot create flat files for the unit. With-out flat files, no reason exists for altering theautoexec.bat file to invoke the 9740 executable;the flat files the executable needs dont exist. Theresult of the DOS boot process, in this case, is sim-ply an on-screen system prompt. It then becomesthe users responsibility to create flat files, load theminto the 9740 directory and appropriately alter theautoexec.bat file for the boot process to call theexecutable. All the information you need to accom-plish this is contained in this and the rest of the sys-tem manuals.

* The error listed in step 3 should not occur withrespect to the hidden system files as these wereput on the hard drive when it was configured atthe factory. If you see this error during the bootprocess, you probably have a disk in the A: drive.

** Since COMMAND.COM is not a hidden file, itspossible that it could accidentally be moved,corrupted, or erased. If this occurs, you mayneed to start DOS from a floppy disk and COPYCOMMAND.COM into the CC1s root directory.

CM9740-CC1 | 35

A Closer Look at AUTOEXEC.BAT andthe BOOT Process

The AUTOEXEC.BAT file is the last file called dur ing the boot process as described in theprevious section. For CC1s configured as part of a system node at the factory, the end re-sult of this process is the appearance of the CM9740 diagnostic screen on the attachedmonitor instead of what one would normally expect to seethe system prompt.

when creating flat file names using the Win95-based 9760-MGR program as it does not al-low you to use more than eight alphanumeric characters when creating a global name foryour flat files or configuration set.

DOS CommandsDOS commands are divided into two groups. Because of their large number, only thoseused most often are loaded into memory (RAM). The rest reside in the DOS directory.The former commands are called internal and the latter are called external commands.Whenever DOS comes across a command to act upon, it looks first in RAM, then it looks inthe DOS directory, and then it looks in the directory from which the command was issued.Nothing is wrong with this unless you try to invoke an executable type file that isnt in anyone of those places. Instead, you are forced to navigate to the directory in which the execut-able file is located. Putting a PATH command statement into the AUTOEXEC.BAT file avoidshaving to do this.

The factory-configured boot process occurs because of theinstructions added to the AUTOEXEC.BAT file. TheAUTOEXEC.BAT file is a batch file, which contains a seriesof instructions that are executed serially when the file iscalled. Figure 26 is a sample autoexec.bat file.

Invoking the CM9740 ExecutableFocus on the last two instructions or commands in Figure 26.Here is what they do. The command CD 9740 directs DOSto the 9740 directory where the 9740 executable resides.The last command starts the executable and directs the pro-gram to load into memory all flat files having the collectiveprefix name of test (also located in the same directory). Theprogram continues to configure the system environment andgoes online. If everything is OK, the Setup Complete mes-sage appears on the CM9740 diagnostic System Window onthe attached monitor.

If you change the name (the prefix) of your current flat filesor copy a new set of flat files (with a different name) to the9740 directory, then your AUTOEXEC.BAT file must bechanged to correspond. Otherwise, the CM9740.EXE will notexecute properly. To effect the change, you need to edit theautoexec.bat file and change the old flat file name (in Figure26, the old flat file name would be test) to the new name;save the file and reboot. On the other hand, if you were todelete or REM out the last two entries (if you type in the let-ters REM at the beginning of a line, the line is ignored whenthe program executes) in the AUTOEXEC.BAT listed in Fig-ure 26, save the file and reboot, you would arr ive at a basicsystem prompt and not call the executable at all. Then, in or-der to star t the CM9740 executable, you would have tomanually navigate to the 9740 directory and type inCM9740 test to activate the diagnostic program.

File Names and DOSKeep in mind the eight-character limit imposed by DOS onfile names. If you issue a command to change the name ofthe flat files in the 9740 directory to one exceeding eightcharacters, the name will be truncated. No problem arises

NOTE: The prompt command line in the figure above con-tains what are called metacharacters which tell thePROMPT command what to display when these charac-ters are encountered. If the last two lines of the file abovedidnt exist, the end of the boot process would be the sys-tem prompt. The system prompt displayed would dependon the metacharacters used with the PROMPT command.In the example above, the characters have the followingmeanings:

$t means display current time$d means display current date$p means display current directory$g means display the greater than character, >.

As a result, the system prompt would look some-thing like the following:

12:29:22.23 Fri 02-19-1999 C:\ >

Figure 26Sample AUTOEXEC.BAT File

36 | C1508M (02/01)

The PATH StatementThe PATH statement causes DOS to look in each of the directory paths listed there for anyexecutable [.EXE, .COM or .BAT file] its instructed to carry out. The syntax of the PATHstatement is as follows:

PATH = { [drive:]path; [drive:]path; [drive:]path..] }

Example: PATH=c:\;c:\dos;c:\windows(We included spacing in the syntax statement to make it easier to seethe elements that make up the path statement. In actual use, spacesare not allowed, as the example demonstrates.)

Semicolons separate drive-path statements. There are no spaces. The complete drive pathmust be given for each directory you wish to include in the search. The search is for fileswith .EXE and .COM extensions only. An additional note: if the executable you call, in turn,issues a call for a non-executable file (that is, one without an .exe or .com extension), thenthe PATH statement doesnt apply. Instructions for using the executable must tell you eitherwhere to place needed non-executable files or the executable itself must provide the meanswhereby the file can be found. DOS will not look for these files.

You might think that inser ting the directory path for the CM9740 executable file into thePATH statement would be a good thing to do, but it will not work. The CM9740 executable,at one point, needs to use a non-executable file that always resides in the C:\9740 direc-tory. If you invoked the CM9740 executable from any directory location other than theC:\9740 directory, the executable wouldnt finish successfully because CM9740.EXE ex-pects to find the file residing in the same directory that its in. If you manually invoke thecommand (CM9740 test) while in the C:\9740 directory, the executable works OK. Some-times, you actually need to do this. However, in most cases, you reboot to let changes toflat files take effect and the result is that, by default, DOS boots to the root directory. That iswhy the CD command to switch to the 9740 directory is included in the AUTOEXEC.BATfile. If you used the PATH command statement alone, the CM9740.EXE would be found,but the other non-executable file needed to finish the process would not be found and sys-tem initialization would fail.

Navigating the DOS Directory TreeWhenever you exit to DOS on the CC1, you will normally be at the following screen prompt:

C:\9740>

While in the directory, you may manipulate any file there or you may navigate to anysubdirectory contained in that directory.

To navigate to a subdirectory of the 9740 directory, use the following syntax:

C:\9740> CD [subdirectory name] [ENTER]For example, if a 9740 subdirectory had the name BKUPTST, your entry would read as fol-lows:

C:\9740> CD BKUPTST [ENTER]which puts you at the screen prompt in the BKUPTST directory:

C:\9740\BKUPTST>

Once there, files within the directory can be manipulated. The key entries used to backtrackon the directory tree depend on where you want to go. From the BKUPTST directory, youeither can go back to the root directory with one single key entry or you can go in steps,one directory at a time. To proceed directly to the root directory, enter the following:

C:\9740\BKUPTST> CD\ [ENTER]

NOTE: In DOS, the \ symbolwhen used alone refers to theroot directory. The .. symbol re-fers to the parent directory. Theaction performed in the examplewhere we issued the CD (changedirectory) command in conjunc-tion with the .. symbol movedus from the current directory tothe directory immediately abovethe one we were in; that is, theparent directory.

CM9740-CC1 | 37

The \ symbol, when used alone represents the root directory; otherwise it indicates sepa-ration of various levels of the directory tree, collectively known as the directory path.The result of the above entry takes you directly to the root directory and the followingscreen prompt:

C:\>

To backtrack one directory at a time, enter the following at the system prompt:

C:\9740\BKUPTST> CD.. [ENTER]The result of that key entry is as follows:

C:\9740>

If you enter the same command again (CD..) at the C:\9740> prompt and press the ENTERkey, you would finally end up again at the root directory as was previously done.To proceed directly from the directory you are in to another directory, no matter where in thedirectory tree you are, enter the total directory path of the location you wish to go to at thesystem prompt. For example, if you are in the root directory and wish to proceed to theC:\9740\BKUPTST directory, then use the following syntax:

C:\> CD [directory path] [ENTER]Enter the desired directory as follows:

C:\> CD C:9740\BKUPTST [ENTER]The result would be a change to

C:\9740\BKUPTST>

Manipulating Files in the DOS EnvironmentThe safest way to manipulate files is to do so from within the directory in which those filesare located. There are two reasons for this:

(1) If you enter a DIR command at the directory prompt, the names of the file(s)you wish to manipulate are on the screen. This reduces the r isk of makingsimple mistakes, such as entering an incorrect file name as par t of an erasecommand, for example.

(2) When using commands directed at file manipulation, the format of the com-mand requires that the command name be listed first, followed by the filename to be acted upon. If you issue a command for a file that is in anotherdirectory, then you must enter the complete directory path where that file isfound in addition to the name of the file at which the command is directed.

The command formats (COPY, MOVE, RENAME, DELETE, and so on) for the most com-monly used commands are covered through associated examples in Table D on the next page.

Using the Wild Card CharacterThe most commonly used wild card character recognized by DOS is the asterisk [ * ].The asterisk can be used effectively as a placeholder to collectively coral large groups offiles which are going to be acted upon by the same DOS command. The asterisk helps youspecify character positions that are of the dont care type in file names. When DOS en-counters the asterisk, DOS ignores the characters in the position containing the wildcard aswell as all the characters that follow it.

38 | C1508M (02/01)

The flat files used by the CM9740-CC1 are a pr ime example of how the wildcard can beused.

Example 1 To copy flat files from the A floppy drive to the 9740 directory on the CC1hard disk:

Change to the A: directory and use the following syntax at the A prompt:

A:> copy [flat file name].* [destination] [ENTER]For example, if the filename prefix for the flat files is TEST, the command line would look asfollows:

A:> copy TEST.* C:\9740 [ENTER]Example 2 To move flat files from the 9740 directory to another directory (previously cre-

ated) for, say, archiving purposes:

From the 9740 directory, use the following command syntax to move the files:

C:\9740>copy [source] [destination]Since you are already in the 9740 directory, the source portion of the command consists ofjust the file name(s) to be moved. The destination contains the path to the directory wherethe files are to be moved to (assume a destination directory named archive and the sameflat file prefix name of TEST). The command line would read as follows:

C:\9740>copy TEST.* C:\archive

DOS Reference DirectoryThe following is a Command Reference Directory of the most common DOS commands that you are most likely to use when operat-ing the CC1. This list, along with the HELP command reference that resides on the CC1 hard disk itself, should provide you withmore than enough working information on DOS.

Table DDOS Command Reference Directory

COMMAND EXAMPLE(s) SWITCHES COMMENTS

Displays the name of the current directory orchanges the current directory if specified (and ifthe directory specified exists).

Changes to the 9740 directory.

If you want to clear a full screen display, the ClearScreen command will do it. It clears the screen tojust the command prompt and the cursor.

Copies one or more files to the location youspecify. Source specifies the location and nameof a file or set of files. Source can consist of adrive letter and colon, a directory name, afilename, or a combination of files you want tocopy. Destination specifies the name andlocation of a file or set of files to which you want tocopy. Destination can consist of a drive letterand colon, a directory name, a filename, or acombination of both.

When more than one file is copied, MS-DOSdisplays each filename as the file is copied.

CD C:\>CD

C:\>CD 9740

CLS C:\>CLS

COPY C:\>COPY [source] [destination]

C:\>COPY A:\TEST.* C:\9740C:\>COPY A:\*.* C:\9740C:\>COPY A:\TEST.MON C:\9740

(Continued on next page)

CM9740-CC1 | 39

Table DDOS Command Reference Directory (Continued)COMMAND EXAMPLE(s) SWITCHES COMMENTS

Deletes the file or files you specify. You mustinclude the location (if other than your currentlocation) and name of the file or set of files youwant to delete.

Prompts you for confir mation before deletingeach file.

Displays a list of files and subdirectories that arein the directory you specify. When you use the DIRcommand without switches, it displays the disksvolume label and serial number, one directory orfilename per line, including the filename extension,size, date and time the file was last modified; thetotal number of files listed, their cumulative sizeand free space left on the disk.

Displays the listing in wide format, with as manyas five filenames or directory names on each line.

Displays one screen of the listing (in whateverformat) at a time. Its useful to use these switcheswhen looking at the contents of the DOSdirectory.

This switch will look for all instances of thefilename in all directories.

In the example the location of all file nameshaving the .mon extension will be found anddisplayed.

Starts the MS-DOS editor, a test editor you canuse to create and edit ASCII text files. Theexample shown would load the autoexec.bat filefor editing.

Lists and briefly describes every commandprovided with MS-DOS. This list is much lessdetailed than the list you get using the HELPcommand.

Specifies the name of the command that youwant FASTHELP to give information about. In thisexample: DIR.

Formats a disk for use with MS-DOS.

Transfers system files to the formatted disk. Youcan boot from the floppy of a disk formatted usingthis switch.

Starts the MS-DOS command reference locatedon the CC1s hard disk.

Specifies the command whose help topic youwant to display. In this example: DIR.

Creates a directory. The example creates a 9740directory.

DEL C:\>DEL C:\9740\TEST.MONC:\>DEL A:TEST.MONC:\9740>DEL TEST.*

C:\9740>DEL TEST.* /P /P

DIR C:\>DIR

C:\>DIR/W /W

C:\>DIR/P /PC:\>DIR/W/P

C:\ >DIR {filename} /S [syntax] /Sexample: C:\ >DIR *.mon /S

EDIT C:\>EDIT AUTOEXEC.BAT

FASTHELP C:\>FASTHELP

C:\>FASTHELP DIR

FORMAT C:\>FORMAT A:

C:\>FORMAT A:/S /S

HELP C:\>HELP

C:\>HELP DIR

MD C:\>MD 9740

(Continued on next page)

40 | C1508M (02/01)

MORE C:\>DIR C:\DOS MORE

PATH PATH=C:\;C:\dos;C:\windows

RENAME or C:\>RENAME C:\9740\TEST.*REN TESTALL.*

C:\>REN C:\9740\TEST.* TESTALL.*

TYPE C:\>TYPE C:\9740\TEST.MON

C:\>TYPE C:\9740\TEST.ALM MOREMORE

UNDELETE C: