Simplex 4120 Programming Unit Programming Instructions For 4120 Network 5983620147
Simplex 4120 Programming Unit Programming Instructions For 4120 Network 5983620147
firealarmresources.com
firealarmresources.com
TABLE OF CONTENTS
APPENDIX A - HARDWARE/SOFTWARE REQUIREMENTS ... .. ... . .... .. . .... . .. .. . .. .. .. . .. .. .. ... .. . ... . .. . .. .. . .. .. ... . .. .. .. .. .. .. ..27
APPENDIX B - USING THE 4100 PROGRAMMING UNIT DOS UTILITIES . ... . ...__._.............................................. 29
firealarmresources.com
FIGURES
Figure Page
1 Fixed Directory Structure.. ......................................................................................................................... 2
2 File Utilities Menu ...................................................................................................................................... 3
3 Network Directory ...................................................................................................................................... 4
4 Unload Job Prompt.. .................................................................................................................................. 4
5 Working Directory Changed Prompt.. ........................................................................................................ 5
6 Network Filename Prompt ......................................................................................................................... 5
7 Create New Directory Screen .................................................................................................................... 6
8 Network Information Screen.. ..... .... ........................................................................................................... 6
9 Network Build Results Screen ................................................................................................................... 7
10 Network Report Output Choice Menu ........................................................................................................ 8
11 Sample Network Report ............................................................................................................................. 9
12 Job Directory Showing Network Jobs NOT Current to Network .............................................................. 10
13 Job Directory Screen ............................................................................................................................... 10
14 Load Specific Job Menu Screen .............................................................................................................. 11
24 Network Interface Data Entry Screen Showing Selected PUBLIC Points ............................................... 18
ii
firealarmresources.com
INTRODUCTION TO NETWORKING
The 4120 Network is a peer-to-peer network. This means that every network panel (or node) has an equal chance
of putting a message out on the network. Each node can maintain the status and control of its own dedicated circuit
points while monitoring and controlling activity at other locations.
The 4120 Network uses a communications scheme known as Token Ring Protocol. In Token Ring communications,
an electronic data “flag” or “token” is passed from one node to the next. The node that holds the token is the only
one permitted to talk on the network. A node that has no messages or requests for the network simply passes the
token onto the next node. Thus, every node has an equal chance of putting a message out on the network when
needed.
Network Features:
Version 6 of the 4100 system software allows existing 4100 Fire Alarm Control Panels and Universal Transponders
to be networked together by installing a 4120 Network Interface Card into each panel of the intended network, and
configuring each panel to accept the card.
Panels compatible with the 4120-0140 Network Interface Card card are:
l 4100-8001 Fire Alarm Control Panel
l 4100-8201 Voice Fire Alarm Control Panel
l 4100-8010 Miniplex Control Panel
l 4100-8210 Voice Miniplex Control Panel
l 4100-8511 Universal Transponder
l 4100-8601 Voice Universal Transponder
l 4100-8602 UT Voice Status Command Center.
NOTE: If your 4100 Fire Alarm Panel is at Software Version 4.02 or earlier, it can only be connected to the 4120
Network by upgrading the Master Controller in one of two ways:
l Installing a 4100-7050 Master Controller Upgrade Kit, or
l Reprogramming the Master Controller with a 4100-0150 After-Market Reprogram.
Defining a network node requires that you declare PUBLIC and EXTERNAL points within the node via Version 6 of
the 4100 Programming Unit. The network definition is accomplished with a 2-pass approach. Points PUBLIC to the
network in all nodes are declared first. A second pass is required to select EXTERNAL points from a tag list-based
feature that gives you access to all Network PUBLIC Points.
firealarmresources.com
The node number of a particular job may be viewed on either the General Information, 4120 Information or Job
Directory screens. Other network information is changed by editing the 4120 Network Interface Card itself. Most of
the network configuration data is entered in the NETWORK POINTS submenu from the Configuration menu.
Directory Structure
To help keep files associated with a network organized and to insure proper operation of the Programming Unit, the
following subdirectory structure must be used. Each network should have its own subdirectory off of the
<NETJOBS> directory which contains the .DBN file and subdirectories for all the nodes on the network. Each of
these subdirectories should contain all files associated with that node.
When adding nodes to a network, the Programming Unit creates subdirectories for the .DBF and .MOT files off of
the network directory containing the .DBN file in a manner shown in Figure 1.
<9229013>- ..*
t <9279020> - ...
T '9220126A.MOT
9220126A.REP t
T ag22101'
. .
Figure 1
Fixed Directory Structure
When loading a job, the programmer only “looks” in the current directory and the parent directory for the .DBN file.
When doing a Job Directory, the programmer only searches in the current directory, down one level of subdirectories
and in parallel directories. If the files can not be found in these search paths, the Programming Unit will not be able
to find the appropriate job files.
2
firealarmresources.com
THE PROGRAMMING UNIT NETWORK SCREENS
NOTE 1: For basic information on the 4100 Programming Unit, refer to Simplex Publication FA4-41-222, “4100
Programming Unit - Introduction”.
NOTE 2: Refer to Appendix A for a summary of the Programming Unit hardware and software requirements.
The 4100 Programming Unit still functions in much the same way as it did before the networking functions were
added. However, some new menu selections have been added to the various sub-menus, and the Programming
Unit functionality has been expanded to incorporate the Network Card. The following paragraphs describe the
changes and additions that have been made to Revision 6 of the 4100 Programming Unit.
Utilities Menu
When you select the Utilities menu option from the Programming Unit Main Menu, the screen appears as shown in
Figure 2.
NET~~ORKDIRECTORY
FILE DIRECTORY
GENERAL INFO
CREATE NEU JOB
LOAD SPECIFIC JOB
SAVE CURRENT JOB
EXIT TO DOS
Figure 2
File Utilities Menu
The Utilities submenu selection, NETWORK DIRECTORY, provides a list of all networks present in the
subdirectories one level below the <NETJOBS> directory. The Programming Unit determines which networks to
display based upon the presence of network (.DBN) files. If a network had previously been selected, it will be
identified with an asterisk (*) displayed next to the network filename.
If present, the ~41 OOJOBS> directory will also show up in the network directory. This is obviously not a true network,
but is shown here to allow the user to select this path as the new working (current) directory.
3
firealarmresources.com
NETWORK DIRECTORY
Figure 3
Network Directory
Find the first text line at the bottom of the Network Directory screen. This is the Network Directory menu line. You
can select a network, create a network, get information about a network, build a changed node, build all nodes of a
network, generate a network report, view the build report, or rename a network. This is accomplished by first
highlighting the desired network, and then pressing the first bracketed (< >) letter of the desired action. Each of these
menu selections is described in the following paragraphs.
The &select action changes the active directory to the directory containing the highlighted .DBN file. Pressing cS>
or <Enter> selects the highlighted network. If a job is currently loaded, you are prompted to “unload” the current job
(out of RAM) before selecting the network. (See Figure 4.)
NETWORK DIRECTORY
Figure 4
Unload Job Prompt
4
firealarmresources.com
If the current job has not been saved, you are prompted to save it using the load path as the save path. After the
network has been selected the new path is displayed for you. (See Figure 5.)
NETWORK DIRECTORY
Figure 5
Working Directory Changed Prompt
Creating a Network
The <Cz-reate network menu option prompts you for a valid network filename. When you press the <Enter> key to
enter your filename, the Program Unit automatically suggests a Network Path. To select this path, press the <Enter>
key again. This menu option also allows you to type in a network path for the database network file (.DBN file). (See
Figure 6.)
NETWORK DIRECTORY
Figure 6‘
Network Filename Prompt
After you enter the network filename and path and press the <Enter> key, the Programming Unit will ask if you want
to create a new directory if the one requested by you does not yet exist. (See Figure 7.)
firealarmresources.com
NETWORK DIRECTORY
Figure 7
Create New Directory Screen
As soon as you press cy>, the Programming Unit immediately displays the Network Information Screen so that you
can enter the appropriate information. (See Figure 8.)
NETWORK INFORMATION
Filename: 92C9013A
Branch Number: 001
Branch Location: GARDNER, MA
:
:
Figure 8
Network Information Screen
Whenever you need to view or edit network information, select the cbnfo network menu option. This brings up the
Network Information Screen.
6
firealarmresources.com
Building a Network
Two options are available to you when building network jobs. The first is cB>uild changed. When you select
cB>uild changed, the Programming Unit only forces a build for systems on the highlighted network which need to
be rebuilt. The Programming Unit maintains an internal flag in each job. This flag is set when the job needs to be
rebuilt. You can see the status of this flag in the network report.
The second build option, cA>ll build, is used to force a rebuild - or initial build - of every node in the selected
network. Due to interdependencies between nodes, it is often the case that building one node requires a rebuild of
another node. The <A>II build feature and the eB>uild changed feature sometimes builds a job twice. This
selection also produces or updates the Report of Build (.RPB) file on disk. (See Figure 9.)
NETWORK BUILD
BUILD OK: Job i192C3127B1' built successfully. Mon Dee 28 11:45:33 1992
BUILD OK: Job 1a92C3129A'a built successfully. Mon Dee 28 11:46:38 1992
Figure 9
Network Build Results Screen
This report is automatically sent to the disk as <NETFILENAME>.RPB (Report of Build), and includes the memory
chip requirements for each job that was rebuilt. From the Network Directory screen, you can select <V>iew Build
Report to see this .RPB file. You can also view this report from the File Directory screen by selecting the <V>iew
option.
The jobs that have been built successfully will have new .MOT files generated on disk. However, you must still
download the new job information. If you have a 4100+, Network Display Unit, or Universal Transponder, you can
download the new job information directly to the Master Controller’s CFIG Flash EPROM. If you have a standard
4100, you must first download the new job information to a PROM programmer, and then “burn” the CFIG PROM
chips and manually insert them into the designated sockets on the Master Controller Board.
Selecting <Raeport generates a network report describing the nodes in the network and their current status. You
can select the destination of the report to be the Printer, Disk or Screen. (See Figure 10.)
7
firealarmresources.com
NETWORK DIRECTORY
Figure 10
Network Report Output Choice Menu
This option also generates a different report about the build and edit status of those jobs that were rebuilt.
If you choose your disk as the destination, the report is sent to the disk as a file named cNETFILENAME>.REP. (See
Figure 11.)
NOTE: This is not the same file as the output of a network build.
8
firealarmresources.com
----------------------------------------------------------------------
Network: STR BUILDING 24
Network Configuration Report Mon Dee 28 ll:48:~~g?99~
---------------c------------------------------------------------------
NetworkName: STR BUILDING 24
Branch Number: 001
Branch Location: GARDNER, MA
Comments :
:
:
:
.:
E
:
:
:
Node Type Filename Name Addr Status
1 4100+ 92C3127B FLOORS 1 THRU 3 1 NoChg
$ NDU
4100+ 92C3129A
92C3128B FLOORS
BUILDING4 TNRU
24 6 23 NoChg
NoChg
Figure 11
Sample Network Report
Status Key
NoChg = Job Unchanged; Job has not been affected since it was last edited and built.
Edit = Needs Edit; EXTERNAL points referenced by system have been deleted or changed. Editing may be
necessary.
Build = Needs Build; Job needs to be rebuilt. Change is either an updated label or a changed network point link to
another node. No editing should be necessary.
The JOB DIRECTORY sub-menu selection no longer lists only the jobs in the current directory. It now lists all jobs:
in the current directory, in subdirectories one level down, and in directories parallel to the current directory. This
makes it easier to switch between nodes on the network under the new directory structure. Network jobs that are
NOT current versions with respect to the selected network are identified with a tilde (-) symbol in the left-most
column next to the job filename. A previously selected job is identified with a greater than (7) symbol in the left-most
column next to the job filename. (See Figure 12.)
9
firealarmresources.com
JOB DIRECTORY
1
loaded.
- = Job not in current network.
Figure 12
Job Directory Showing Network Jobs NOT Current to Network
When a job is selected to be loaded, the working directory is changed to the directory containing the job; then the
job is loaded into the Programming Unit. The current directory path is displayed at the bottom of the JOB
DIRECTORY screen.
A specific network should be selected from the Network Directory before entering the Job Directory menu. Once in
the Job Directory menu, you simply highlight a network job (node) and press CL> or <Enter> to load the job (and
change the working directory). (See Figure 13.)
JOB DIRECTORY
Figure 13
Job Directory Screen
10
firealarmresources.com
Deleting a Network Job
After highlighting the desired job, press CD> to delete its files from the disk. This action deletes the
cJOBFILENAME>.DBF, .MOT, .REP files and the job subdirectory of the same name. In addition, this action
removes references to this node from the .DBN file.
The Load Specific Job menu (Figure 14) prompts you for the load path when trying to load a job. This facilitates
adding a stand-alone panel onto a network. The default path for this feature is the current directory. If the
Programming Unit does not find the job there, it looks in the ~41 OOJOBS> directory. If the job is not found there, you
must specify the full path.
NOTE 1: You may now load any job directly from a floppy diskette or a hard drive without first loading the
Programming Unit from the required path.
NOTE 2: You cannot edit the path displayed in the prompt window for dual-floppy computer (i.e., NEC Multispeed)
operations.
Figure 14
Load Specific Job Menu Screen
The Save Current Job menu item (Figure 15) prompts you for a pathname in addition to the jobname. The default
pathname is the path that was used when the job was loaded (i.e., the load path). If the specified path differs from
the load path, you are given the option of changing the path of the file. You cannot edit the path displayed in the
prompt window for dual-floppy computer operations.
11
firealarmresources.com
F ILE UT I LITIES MENU
JOB DIRECTORY I
NETWORKDIRE
FILE DIRECT0
GENERAL INFO
CREATE NEW J
LOAD SPECIFIC.JOB
SAVE CURRENT JOB'
EXIT TODOS
I I
Save resident job database to disk.
.. ......A:,:,:.:.:.,:.:.:.:.:.:.:.:.:.::::::::::::::::::::::::::::~~:~:~~:~~~~
““.‘.‘.:.:.~:.:......
./......,.,.....,....
::::::+:w::.:.:.:.:.:.:.:.:.:.::::: ,,_,._..
,,,,,,,,,,,,,
;,,,(_,,(_,,, 1 iiiliiiiii:t)i:i:i:i:~:~:~~~~~~~:::~:~:~~::~:::::::::~:~:~
s........_..._
..._.....
.....:.:...:.:.,.
,,.... ,.,,.,.,_
\
‘~‘~‘~~+:_A’.
:.:.:.:
.....i.,..... ., _.
,....\.......,. ...?:(.:
...<.>:.:.:.:.>>>
,......
::..;:
,(,,, :::.,._
...,.,.,.,.,.,._...,..,_,..,,,,,
::: HELP ,,::::::::i:I:~:~:~;~:~:~:~::::::::::::::::~:~:~:~:~:~:~~~:~:~:::::~:::::::~:~:~::~:::::::::::::::::::::~::~:::
Figure 15
Save Current Job Screen
To add an old job to an existing network, go to the Utilities submenu and select the desired network from’the Network
Directory, as shown in Figure 16.
NETWORK DIRECTORY
Figure 16
Selecting the Network
The next step is to select LOAD SPECIFIC JOB from the Utilities submenu and enter the job name. (See Figure 17.)
12
firealarmresources.com
FILE UTILITIES MENU
Figure 17
Entering the Job Name
If the Programming Unit is unable to find the job in the current directory or in c41OOJOBS>, repeat this step and
enter the correct path. If the job file is not in the appropriate directory for this network, you will be prompted to move
this job to the network that you’ve chosen, as shown in Figure 18.
.. .. ..:.i:.:.:.:.:.:.:.:.:.:.):.:.:.:.:.:.:.~~:.~:.~:.:.:.:.:,:,~:.:,:.:~:~:~:~:~:~:~:~:~~~~
:‘:‘:*.‘A ‘.‘.‘.‘““‘...“.:.‘.~.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .:.:.:p$..,; :,:,:,:,:,:,:,,,,,, 1
HELP 4 iiiiiiii~~~~~~~~~~~~~~~~~~~~~
:~~li:cn:::rrr::r::~:.~.:~::::rrrr:.: ... ... . . ...~/.....~.~.~.~.~.......~. .....i....._. ................................................
.........................................._...
Figure 18
“Move This Job” Prompt
NOTE: If you answer ‘Y”, the job is deleted from its location and is moved to the current network directory. If you
answer “N”, you cannof add the job to the current network.
After the job has been loaded into memory, the next step is to add the Network Interface Card to the new node.
13
firealarmresources.com
Adding a Network Interface Card
The 4120 Network Interface Card is added in the same manner as any other card. (For information on adding and
editing system cards, see Publication FA4-41-223.)
Go to the Configuration submenu and select SYSTEM CARDS. You are placed in the Card Configuration Editor.
Press the <A> key, select the Interface card type, and highlight the 4120 Network Interface entry. Enter the number
of cards that you want to add. The default value for this entry is 1. (See Figure 19.)
NOTE: At this time, you can only add one network interface card to a node.
How many ? f
Total cards: 10
Figure 19
Adding the 4120 Network Interface Card
The Card Configuration Editor permits only minimal data entry for this card. To edit this card, highlight the Network
Interface card and press the cE*dit key. The 4120 NETWORK CARD DATA ENTRY SCREEN appears as shown
in Figure 20.
Style (7/4) : 7,
Node Address : 1
Loop Number : 1
Press LFll for Help Press IF101 to Save Press CESCI to Quit
Figure 20
Network Card Data Entry Screen
The only field that can be edited on this screen is the Style field. The default communications style is Style 7.
14
firealarmresources.com
The Node Address (number) is automatically placed in the field, based on the information entered when the job
was created; if it is incorrect, you cannot change it on this screen. The node number can only be changed after the
Configuration submenu option, NETWORK POINTS, is selected.
The Loop Number default is 1. The loop number, like the node number, can only be changed with the Configuration
submenu option, NETWORK POINTS.
NOTE: The 4120 Network only supports one loop at this time.
To configure the Network Card, highlight the Configuration submenu selection, NETWORK POINTS, and press the
<Enter> key. The 4120 NETWORK INTERFACE INFORMATION DATA ENTRY SCREEN (Figure 21) is
automatically displayed if no network name has been previously entered. (The screen may also be accessed by
pressing cl> from the 4120 NETWORK INTERFACE DATA ENTRY screen.)
Press IF13 for Help Press IF103 to Save Press tESC1 to Quit
Figure 21
Network Interface Information Data Entry Screen
This screen allows you to modify the node number, network filename, network prefix, and master timekeeper
selection, as well as control the automatic features of Annunciate Missing Node(s) and Auto List Gen Externals.
If the Network Filename field is empty, you may declare the network filename of the network to which this node
belongs. If this field is left empty, you may not declare any points as PUBLIC or EXTERNAL. If you have selected a
network through the NETWORK DIRECTORY function, the network filename is automatically inserted in this field.
You may toggle the Master Timekeeper field to YES if no other node is currently designated to perform this network-
wide function. If another node has already been given this task, an error message will be generated. There may only
be one Master Timekeeper.
The Network Prefix is a 19 character label that will be attached to a custom label in a future release.
The Annunciate Missing Node(s) feature allows you to automatically bring in the Common Trouble Points of every
other node in the network. These points are inserted in the network interface card starting at address 256 and are
added in ascending order by node number. If this feature is enabled (YES in the field), you may NOT add or delete
points in the 256 to 511 range on the card. If disabled (NO at the prompt), you may add or delete any Common
Trouble Points in this range.
15
firealarmresources.com
The Auto List Gen Externals feature allows you to take advantage of the system lists that are used by the default
SMPL program(s). If this feature is enabled, an EXTERNAL point is included in the local system lists at auto-list
generation time. This feature is based upon a point’s assigned point type and/or device type. Not every system list
is included; the affected set of lists are contained in Point List L102, LISTS TO AUTOGENERATE EXTERNALS.
You may edit this list of lists from the Pre-Programmed User Lists option in the EXPANDED OPERATIONS
Submenu.
To save the screen information that you have just entered, press the <Flop key. This causes the 4120 NETWORK
INTERFACE DATA ENTRY screen to appear.
The 4120 NETWORK INTERFACE DATA ENTRY Screen (Figure 22) is the primary network configuration screen.
The first text line at the bottom of the Network Interface Data Entry screen is the menu line. You can add PUBLIC
Points, add EXTERNAL Points, delete Network Points,, view/edit the Network Interface Information Data Entry
Screen, or go to the next available point location. This is done by pressing the first letter of the desired action.
The cl> key brings up the Network Information Screen described earlier.
You may delete a single point with the CD> key. This feature warns you that deleting a PUBLIC point may force an
edit and build of any panel that declared it EXTERNAL. Deleting an EXTERNAL point may invalidate local Custom
Control SMPL as well as any other local reference to the point, such as LED/Switch programming.
Figure 22
4120 Network Interface Data Entry Screen
You can use the tag list function of the 4120 Network Interface Data Entry Screen to select network points. (See
Figure 23.)
16
firealarmresources.com
4120 INTERFACE - PUBLIC POINT SELECTION Current Gap Size: 1024
CESC> = Exit Space = TAG A = TAG all G = TAG by type CF91 = Tag List I)nit
H)eIp Sort by P)oint T)ype L)abel U = Tags Up F)ind C)tear R)elabel M)enu
Figure 23
PUBLIC Point Selection Using Tag All Function
To declare a point “PUBLIC”, you must first move the highlight bar to the desired position for the point. The <G>oto
feature facilitates this by prompting you with the next available (unused) location. You may then press <Enter>, or
manually input a new location to “jump to” and highlight.
The next step is to press cP>. This calls up a tag list facility. You are then allowed to ta3 as many points as there
are blank consecutive positions relative to the current position highlighted. If only one point needs to be tagged, just
highlight it and press <Enter> to add it.
NOTE: If you highlight a point location that is being used, and press <P>, the Programming Unit prompts you with
the next unused location.
Leaving the tag list and saving the points fills as many positions as selected with the PUBLIC label. The point name,
device type, point type and custom label are filled in based upon how the point is defined on the card controlling that
point. None of the fields on this screen are directly editable. (See Figure 24.)
17
firealarmresources.com
4120 NETWORK INTERFACE DATA ENTRY
Figure 24
Network Interface Data Entry Screen Showing Selected PUBLIC Points
The ‘Current Gap Size” field displayed in the upper right area of the tag list (Figure 23) is a measurement of the
space available on the network card relative to the starting position and next used position, Simply put, it is the size
of the current hole in the network card that may be filled in during the current session of the tag list.
Due to the potentially large repercussions caused by moving points around, you are prevented from inadvertently
doing this. The tag list does not allow you to tag more points than would fit in the gap. When declaring points
PUBLIC, the tag list facility does not display points that are not allowed to be declared PUBLIC or have already been
declared PUBLIC.
EXTERNAL points are added to the interface card much the same way as PUBLIC points. You move the highlight
bar to the next available position to select the first of the EXTERNAL points. As described earlier, the eG>oto feature
can also be used to easily find the next available hole. Next, you press <Es to call up a list of nodes currently
associated with this network from which to choose the desired points. (See Figure 25.)
18
firealarmresources.com
I
Pt
4120
Typ Point
NETWORK INTERFACE
-- --
FLOORS 1 ,.THRU3
FLOORS 4 THRU 6
Figure 25
Node Selection Menu
The node is then highlighted and pressing <Enter> displays the available points to be tagged as EXTERNAL.
When a node is brought into the tag list, all available points are initially untagged. The points displayed are those
that were ejther declared PUBLIC on the node in a previous programming session or were declared PUBLIC by
default. The Current Gap Size field in the top right area of the screen shows you how many points may be tagged.
(See Figure 26.)
4120 INTERFACE - EXTERNAL POINT SELECTION NODE: 1 Current Gap Size: 1022
Figure 26
EXTERNAL Point Selection Screen
Many of the standard tag list features are not available for EXTERNAL point selection. The ones that are still allowed
are shown at the bottom of the screen.
19
firealarmresources.com
PUBLIC Reserved Points
Due to typical network programming considerations, the first 512 points on the interface card have special
restrictions. The first 256 points are PUBLIC Reserved Points. These are automatically declared public on every
node and always reside in the same offset on the network interface card. You may not edit these reserved network
points.
When a 4120 Network Interface Card is added to a system, the Programming Unit automatically adds certain
PUBLIC points at the beginning of the interface. These points are available to any other node in the network to
declare as EXTERNAL, if desired.
The next 256 points (256 - 511) are reserved as EXTERNAL Common Trouble Points. Every node in the network
has a Common Trouble Point. It is always Point 1 on the interface card.
If you selected YES at the “Annunciate Missing Node(s):” prompt on the 4120 NETWORK INTERFACE
INFORMATION DATA ENTRY SCREEN, all of the EXTERNAL Common Trouble Points from the other nodes will
automatically be selected at the node currently being programmed.
If you selected NO at the “Annunciate Missing Node(s):” prompt, individual Common Trouble Points can be selected
(or deselected) by highlighting any available reserved address (256-511) on the Network Interface card and pressing
cE:, to add EXTERNAL Points. You can also tag the desired points with the tag list function.
If you press cE> while in the 256-511 point range, the node menu screen is not displayed. Instead, the tag list is
immediately displayed with any EXTERNAL Common Trouble Points that are still available.
The Programming Unit software program includes a report utility that will allow you to view the relationship between
network points on a node-by-node basis. It basically shows (by node) each point that has been declared PUBLIC
and which node or nodes have brought that point in as EXTERNAL. The network interface point address is shown
for the owning node and for the sharing node(s).
The report can be displayed on the screen, sent to a printer or saved as a separate file for manipulation or viewing
via a text editor. The utility program is executed from the DOS prompt, therefore you must first exit from the
Programming Unit.
20
firealarmresources.com
To display the Network Report on the screen of the computer, type the following at the MS-DOS prompt followed by
<Enter>:
NETREP cNETFILENAME>.DBN
NOTE: By adding I MORE to the end of the above command, the screen will automatically pause when filled and
scroll again when you press any key to continue.
To send the Network Report directly to a parallel printer connected to your computer, type the following command
followed by <Enter>:
To save the Network Report as a separate file so that it can be viewed or printed via a text editor program, type the
following command followed by <Enter>:
See Figure 27 for a sample of a Network Report using this utility program.
21
firealarmresources.com
4120 Network - Report Utility Version .l.Ol
Figure 27
Sample/Partial NETREP Report
It is highly recommended that you observe the following configuration conventions to minimize the chance for
mistakes and unnecessary re-edits and rebuilds:
l Follow the 2-Pass Method (i.e., declare all needed PUBLIC points first; then declare the EXTERNAL points).
l Leave space between nodes on the interface card. This is to allow for expansion, and to make it easier to view
each node in the interface screen.
22
firealarmresources.com
l Whenever possible, do not move or delete points on the interface card. Moving and deleting points can
adversely affect other nodes in the system. It may be difficult for the Programming Unit to resolve these
conflicts.
l When adding PUBLIC points to the interface card, try to group together points that are of the same Device
Type and Point Type. This will optimize the performance of the network.
The Programming Unit handles an NDU job just like any other 41 OO-family job type with a few exceptions. The point
range in the 4120 Interface Card is increased from 1536 to 3072 points to give you access to the full capacity of the
2500 NDU. There is a new default SMPL Program 0 called “NDU.CC”. This program is automatically included at
build time just like DEFAULT.CC and UTONLINE.CC for other job types.
The NDU is intended to be a replacement for a single 2120 System and an annunciator-type of panel. Therefore,
only alpha-numeric annunciator cards are allowed to be added. These include Remote LCD Annunciators and 2120/
RS232 Interface Cards. The NDU may also have a 2120 port.
In general, you must declare all network points as EXTERNAL in the NDU so they may be annunciated. When an
NDU job is created, the Programming Unit automatically adds a 4120 Network Interface Card and a Power/Supply
charger in addition to the Master Controller.
When an EXTERNAL point is added to the interface card, it is available in Custom Control the same as any other
point. Its point name will be preceded with “X:“, where X is the noted number of the owning node. The “Data Not
Available” status of the point is also available as a new input qualifier.
Once an EXTERNAL point has been added-to the network interface card, it is available as a reference address for
LEDs, Switches and 2120 Interface slots in the same manner as any other point.
Error Checking
Basic error checking for EXTERNAL points will be done the same way as for internal, local points. It is based upon
the Device Type/Point Type pair associated with a given point. Additional error checking is done to validate
compatibility of Network points. Points are only allowed to be declared EXTERNAL if they have already been
declared PUBLIC on the owning node. If a point has been declared PUBLIC, and you delete that point from its
interface card, the Programming Unit will delete the EXTERNAL copy of the point during the Load Job function and
prompt you with the message shown in Figure 28.
23
firealarmresources.com
NETWORK BUILD
Figure 28
“EXTERNAL Point Removed” Warning Message
Any local references (including Custom Control references) to the deleted EXTERNAL point(s) will now be errors in
much the same manner as when a card is deleted. These errors are displayed either within the data entry screens
which referenced the point, or at build time (if they are not fixed prior to building).
There is a new warning message displayed at build time if you have declared a point PUBLIC, but not declared it
EXTERNAL in at least one other node. (See Figure 29 and Figure 30.)
NETWORK BUILD
WARNING: Job l~91B1058Cw built with 1 warning(s). Mon Dee 28 15:12:27 1992
Figure 29
Build Warning Message (Network Build Screen)
24
firealarmresources.com
JOB BUILDER MENU
CONFIGURATION ERRORS/WARNINGS
1 Warning Found.
Figure 30
Build Warning Message (Job Builder Menu Screen)
25
firealarmresources.com
firealarmresources.com
APPENDIX A
HARDWARE/SOFTWARE REQUIREMENTS
Version 6 of the 4100 Programming Unit requires the following hardware and software.
l MS-DOS Operating System at Version 3.3 or Version 5.0. (Version 5.0 is recommended.)
l Minimum of 1 Mb of RAM (Random Access Memory) with EMS driver. (At least 2 Mb of RAM is recommended.
More RAM will enhance performance.)
l Minimum computer disk drive configuration of one 720 Kb floppy disk drive and one 40 Mb hard drive required.
(A 3.5 inch high-density floppy drive and a 100 Mb hard drive are recommended.)
l Monitor.
l Keyboard.
NOTE: Do not install RAM-resident programs concurrently with Programming Unit software.
27
firealarmresources.com
firealarmresources.com
APPENDIX B
Introduction
The NETBACK Utility program makes a backup (or archive) copy of your files so that you can safeguard your data
against damage or other loss. Rather than making an exact copy of one file as the DOS COPY command does, the
NETBACK Utility copies every file in your current directory AND every file in every subdirectory BELOW your current
directory. These files can be reinstalled in your computer at a later time using the NETINST Utility. (See “Installing
the Network Files with the NETINST Utility”.)
While the NETBACK Utility is running, it creates a log file on your backup disk that contains the following information:
l The path name and file name of each file that is backed up
If the log file already exists, this file will not be erased. Instead, the backup information is added at the end of the
log, thereby creating a backup history.
Before you can begin the backup, you must exit the Programming Unit. Select the EXIT TO DOS option from the
Utilities submenu. You are now in the Programming Unit “Working Directory”. (The Working Directory is the
directory that you used while you were using the Programming Unit.) To backup all of the files in this directory to
disks in the A: drive, type NETBACK A: at the DOS prompt and press the <Enters key, as shown in the following
example.
C:\41 OOJOBS>netback a:
When you insert your first backup diskette in drive A: and press a key, the screen display continues:
NOTE: If you are not sure if your backup diskettes are empty, abort the utility now by pressing and holding the <Ctrl>
key while pressing the CC> key. Verify that your diskettes are blank and restart the procedure.
29
firealarmresources.com
If more than one diskette is needed, you will be prompted to insert the next diskette into the A: drive at the proper
time, as shown below.
When you insert your second backup diskette into drive A: and press a key, the screen display continues:
Label each diskette as soon as it is removed from drive A:, so that the files can be reinstalled easily at a later date.
When the backup procedure is finished, the screen shows the following message:
Backup complete.
Introduction
Before leaving the factory, all of the necessary network and individual node files were saved to a diskette (or a series
of diskettes, depending on the size of the network) using the NETBACK Utility. The NETINST Utility copies these
4120 Network files from the factory diskettes to your computer hard drive, and maintains the directory structure of
these network files.
Begin the installation by creating the NETJOBS subdirectory on the hard drive that you are going to use. (For this
example, “C” drive will be used.)
C:\md netjobs
C:\NETJOBS>netinst a:
The screen displays a prompt to install the first backup diskette, as shown below:
C:\NETJOBS>netinst a:
30
firealarmresources.com
When you insert the first backup diskette into drive A: and press a key, the screen display continues:
Diskette Number: 01
When the next diskette is needed, you will be prompted to insert the diskette into the A: drive at the proper time, as
shown below.
Restore complete.
Change your current directory to NETJOBS by entering the following command at the prompt:
cd\netjobs
Invoke the Programming Unit to start work on the newly-installed 4120 Network.
If you have a question about either of these DOS utilities, just type the name of the utility at the DOS prompt and a
Help message will appear. An example is shown below.
C:\>netback
Usage: NETBACK [destination-drive:]
This utility will back up all files in the current subdirectory, and all
subdirectories below it, to the destination drive that you specify. If
necessary, multiple diskettes will be used. These diskettes must be
formatted prior to backup.
Note: Be sure to include the colon with the destination drive letter.
C:b
31
firealarmresources.com
firealarmresources.com
firealarmresources.com
I,.
Ed 12 92 Simplex Time Recorder Co., l
Pi,Simplex
Simplex Plaza l Gardner, Massachusetts 01441-0001 U.S.A.
NET-41 -003
(574-308) I
firealarmresources.com