User and Technical Guide. Nexus LX

Transcription

1 Nexus LX Version 2.1, 24 November 2010

2

3 Contents 1. Introduction to Nexus Disclaimer About the Nexus System Nexus Through-Life Support Nexus System Design Sequence Check the Data Cabling Standard Check the Data Cable Plan the SPU Locations Plan the Channel Routes Plan the Router and Repeater Locations and the Trunk Route Plan the Terminator Locations Number the Channels and Apply Channel Sequences Plan the Nexus Server Location Mark up Drawings with Details Check your Work Create the Materials List Create the Project Specifications Nexus User Guide The Nexus Program SPU Type and Status Using Groups Emergency Lighting Tests Reports Integrity Monitor Maintenance Nexus Network Management Nexus Database Network Utility User Guide Network Utility Program Commissioning the NUN Discovering Nodes Getting Info from Nodes in the Table Sorting, Saving and Retrieving Node Tables Setting Routers and Repeaters Online/Offline Packet Counting Nodes Identifying Nodes Discovering Hidden Nodes Shutting Down the NUP Installation Guide Data Cable Connection Data Communications Testing Data Communications Preparation for Commissioning...46 Nexus LX i

4 5.5 Installation List Commissioning Guide Before you Begin Purpose of Commissioning Nexus Device Credits Commissioning the Nexus System Nexus Error Messages SPU LED Colour Meanings Sample Consultant Specifications Emergency Light Fittings Data Network Computer Hardware Computer Software Communications System Programming and Commissioning Glossary of Terms 63 ii Nexus LX

5 C H A P T E R 1 1. Introduction to Nexus Nexus is a real-time Emergency Lighting monitoring and control system. It enables its users to manage an entire installation installing and removing components, testing and monitoring the system and managing maintenance activities. In This Chapter Disclaimer... 1 About the Nexus System... 1 Nexus Through-Life Support Disclaimer All information and recommendations are, to the best of our knowledge, accurate at the time of writing. All trademarks and trade names, registered or not, are the property of their respective owners. All specifications are subject to change without notice. More information is available on our website: About the Nexus System A basic Nexus network consists of a trunk with one or more branches with level 4 shielded twisted pair data cable as the transmission medium. The branches are generally referred to as channels. Each channel is connected to the trunk by a router. The only nodes that can be connected to the trunk are the Nexus Server, the Network Utility Node and the routers that connect the channels. SPUs cannot be connected to the trunk. Nexus LX 1

6 Both the trunk and the other channels may be extended by using repeaters. Where a channel has been extended using a repeater, the channel is thereby broken up into channel segments. Each channel segment consists of a length of data cable with nodes connected along the length of it and with the two ends terminated with data cable terminators (commonly referred to as end-of-line resistors ). This connection configuration is known as a doubly terminated multi-drop bus. Figure 1: Basic Nexus Network A Nexus Network consists of the following hardware components: 1 Nexus Single Point Units (SPUs: NXS Quickfit, NXS Spitfire, NXS Powerpack, NXS Flood etc) 2 Routers 3 Repeaters 4 Nexus Server 5 Network Utility Node (NUN) 6 Data Cable Terminators 7 Data Cable 2 Nexus LX

7 1.3 Nexus Through-Life Support If you require further assistance, telephone the Stanilite National Support Centre in Australia as listed below T F Trademarks All TRADEMARKS mentioned in this manual are the property of their respective owners. Nexus, Quickfit, Spitfire and Stanilite are Trademarks of Thomas & Betts Australasia Pty Ltd. ECHELON, LONWorks, LONTalk and Neuron are Trademarks of ECHELON Corporation. CYPRESS and TOSHIBA are the Trademarks of their respective companies. MICROSOFT, MS-DOS, and WINDOWS, are Trademarks of MICROSOFT Corporation. Nexus LX MANUAL Ver2 issued 20/03/2010. COPYRIGHT THOMAS & BETTS AUSTRALASIA ACN: Nexus LX 3

8

9 C H A P T E R 2 2. Nexus System Design Sequence Plan the Nexus system before you attempt to install any components. This chapter guides you through the planning process. In This Chapter Check the Data Cabling Standard... 5 Check the Data Cable... 5 Plan the SPU Locations... 5 Plan the Channel Routes... 6 Plan the Router and Repeater Locations and the Trunk Route... 6 Plan the Terminator Locations... 7 Number the Channels and Apply Channel Sequences... 7 Plan the Nexus Server Location... 8 Mark up Drawings with Details... 8 Check your Work... 9 Create the Materials List... 9 Create the Project Specifications Check the Data Cabling Standard In situations where the Nexus server will be connected to the Public Switched Telephone Network (PSTN) via a modem or some other device, it will be necessary to install the Nexus data cable in accordance with the AS/ACIF S009 cabling standard and this must be done by a registered cabling provider. The intent of the AS/ACIF S009 standard is to enforce a minimum separation between mains and data circuits for data networks that are, or are intended to be, connected to the PSTN. This requirement should be clearly listed in the project specification. Further information on this can be obtained by contacting either ACIF (Australian Industry Communications Forum) or the ACA (Australian Communications Authority) 2.2 Check the Data Cable The data cable used to install Nexus networks should be the standard Stanilite yellow Nexus cable. This is a level 4 shielded 22AWG stranded single twisted pair cable part number NXS-1PS. If it is necessary to use an alternative cable, contact Stanilite for detailed advice. 2.3 Plan the SPU Locations This Guide does not cover information contained in AS/NZS Nexus LX 5

10 Locate the fittings so that they comply with AS/NZS 2293 and are easily installed and maintained. Mark up the plans to indicate the location of every node. 2.4 Plan the Channel Routes There are two types of limitations when it comes to determining how to connect Nexus SPUs to form a network. The cabling limit is imposed by the electrical loading of a node on a length of data cabling. The addressing limit is imposed by the digital addressing mechanism of the communications protocol. Nexus Cabling Limits Within a single channel segment there must be 50 nodes or less over a cable length of 1000m. If a channel must be longer than this or have more nodes than this, the channel can be sub-divided into segments using repeaters. Each channel segment is subject to the cabling limit. Nexus Addressing Limits Within a single channel (or trunk) there must be no more than 127 nodes. This number includes any routers or repeaters on that channel. The SPUs marked on the plans must be connected to a channel within the constraints of the cabling and addressing limits. Figure 2 (following) is an example of how it is possible to connect the maximum number of nodes to a channel by using repeaters. Figure 2: Example of the Maximum Number of Nodes connected to a Channel 2.5 Plan the Router and Repeater Locations and the Trunk Route Somewhere along each Channel, there must be a Router connecting it to the Trunk (not necessarily at the end of the Channel). Repeaters are usually located at the end of channel segments. Note that it is possible to connect a repeater to the middle of a channel segment, but the Nexus Software channel map display will not display this accurately so it is best to avoid this topology if possible. Routers and repeaters must be readily accessible for installation, commissioning and maintenance and 6 Nexus LX

11 are generally located in communications rooms or cabinets. Ensure that there is a GPO within reach of each. Note that up to 5 routers/repeaters can be run from the one plug pack power supply if they are mounted adjacent to each other. The data cable route for both trunk and channels should be marked on the plans, showing the sequence of connection to routers, repeaters and SPUs. This information is vital for maintenance of the system. The as-built version of the plans must be updated to reflect the actual location of the data cable together with the connection sequence. Do not put data cabling on top of removable ceiling tiles where the movement of the tile could damage it. Do not run the trunk through tenancy areas, where renovations could damage it. Run it through the common areas of the building, and install it to minimise the risk of damage. Dedicated communication cable trays or risers are best. 2.6 Plan the Terminator Locations A terminator is a passive device which, when connected to the end of a high speed data cable, prevents unwanted distortion of the electrical signal that would otherwise be introduced by the change in characteristic impedance at the end of the cable. Both ends of every channel segment, including the trunk, must be terminated. Mark the location of both ends of every channel segment on the plans. If an SPU is located at the end of a channel segment, then the terminator is usually connected to the data cable within this fitting. Routers and repeaters are frequently located at the end of a channel segment. They both contain two built-in switch-selectable terminators that can be used in place of a discrete terminator when required. The NUN also contains a switch-selectable terminator. If these nodes are not at the ends of their respective channel segments then the terminators must be switched off. 2.7 Number the Channels and Apply Channel Sequences This section explains how to number the channels and apply channel sequence numbers to all nodes. Numbering the Channels Number the Channels in sequential order from one end of the Trunk to the other. The Trunk is always Channel 1, so the first channel is Channel 2. Each router is numbered according to the channel it connects to i.e. R2 for channel 2, R3 for channel 3 and so on. Each repeater is numbered according to its channel e.g. two repeaters on the trunk would be numbered 1a and 1b while three repeaters on channel 2 would be numbered 2a, 2b and 2c. If a new Channel is added in the future the numbering may become out of sequence. You can prevent this happening if you are aware of possible future expansion by reserving one or more Channel numbers. However, if the numbering does become out of sequence it will not prevent Nexus from operating correctly. The software does not require that Channel numbering correspond with the network s physical layout. Numbering the SPUs Nexus uses two numbers to represent each SPU: the Channel Sequence Number and the SPU_ID. The Channel Sequence Number consists of two parts, the first identifying the Channel, the second identifying the node s position on the channel (i.e. the connection order along the data cable). Nexus LX 7

12 Mark a Channel Sequence Number on the plan adjacent to the symbol for each node. Start at one of the terminators and number in sequence along each channel. Reserve numbers if you know where nodes will be added later. Each number must be unique. Refer to Figure 2 for an example of how to apply channel sequence numbers to the SPUs in a channel. When the time comes for the SPUs to be registered using the Nexus software, it will be necessary to register the SPUs in their channel sequence. In the event that extra nodes have to be inserted at the time of registration, Nexus has a facility for inserting new numbers in a sequence. The Channel Sequence Number is designed to make maintenance of the communications network easier. In the event of a cable break the Nexus software will only be able to display the location of the break if the channel sequence numbers have been correctly applied. The Consultant Specification should include a requirement that the installing contractor physically labels all emergency fittings with their Channel Sequence Number and all Routers and Repeaters labelled with their number. 2.8 Plan the Nexus Server Location The Nexus Server can connect to the network anywhere along the trunk. It is usually placed in a secure and protected location such as a maintenance or security office. If the Server must be located in an area that is exposed or is not secure, then it would be advisable to specify an appropriate housing or computer case configuration. Contact Stanilite for more advice. The NUN is usually located near the server although it can also connect to the network anywhere along the trunk. Mark the location of these nodes on the plans. 2.9 Mark up Drawings with Details Trunk Cable Route Draw the cable route on the plans as a line running from router to router. Indicate the location on the trunk of the Nexus Server and the NUN. Channel Cable Routes Draw the cable route on plans as a line running from node to node. The exact cable route can be left up to the installer who should update the as-installed plans accordingly. Routers Draw a box containing R and the channel number eg: Repeaters Draw a box containing Rpt and the repeater number eg: Channel Terminators Draw a box containing T eg: 8 Nexus LX

13 Nexus Server Draw a box containing PC eg: NUN Draw a box containing NUN eg: 2.10 Check your Work Check that the drawings show: No more than 50 nodes and 1000 metres of data cable per channel segment No more than 127 nodes per Channel (including Routers and Repeaters) Channel Sequence Numbers Trunk and Channel Data Cable routes 2 Terminators per Channel Segment 1 Router per Channel 2.11 Create the Materials List Create a materials list to enable potential installers to quote during tendering for the supply of equipment. 8 Calculate the required quantity of: SPUs NXS Quickfits, NXS Spitfires, NXS Powerpacks, NXS Floods etc Terminators (note that 2 external terminators are supplied with each router and repeater there should be no need to order extra terminators) Routers (1 per Channel) Repeaters (where required) 9 Include one Nexus Server package per Nexus network this will include the Server PC, network interface card, Nexus software and a Network Utility Node. (Other combinations are available contact Stanilite for details.) 2.12 Create the Project Specifications You should have completed plan drawings showing the: Location of the SPUs Individual Channel Sequence Number of every SPU Channel routes Router, Repeater and Terminator locations Trunk route Nexus Server location. GPOs for the Nexus Server and equipment, Routers and Repeaters. A sample Nexus Emergency Lighting System Consultants specification is included Sample Consultant Nexus LX 9

14 Specifications (shown on page 59). The following figure shows the trunk with the NUN, Nexus server PC and routers. The routers are shown with terminators turned on or off as appropriate. Channel 6 is shown with 2 repeaters. The SPUs are shown with their Channel Sequence number. Figure 3: Sample Typical Shopping Centre Layout If you require further assistance, telephone the Stanilite National Support Centre (see "Nexus Through-Life Support" shown on page 3). 10 Nexus LX

15 C H A P T E R 3 3. Nexus User Guide This chapter provides information that is needed to operate a Nexus installation safely and efficiently. In This Chapter The Nexus Program SPU Status Using Groups Emergency Lighting Tests Reports Integrity Monitor Maintenance Nexus Network Management Nexus Database The Nexus Program This section provides information about starting the Nexus program, using it, and understanding information that it provides. Nexus LX 11

16 Starting Nexus To start Nexus, double-click the NEXUS LX icon on the desktop or select Start Programs NEXUS LX When Nexus is started, it displays Lonworks Network Interface Selection form. Select the correct network interface for normal operation or Offline Mode for no communication, local database only operation. Figure 4: Nexus Lon Interface Selection Nexus LX System Information When Nexus is started, a System Information window pops up. This window provides a summary of the system status. It can be shut down or minimised at any time by using the icons in the top right hand corner. It can be restarted from the main Nexus window by selecting System Information. Changing the Installation Name To change the name of the installation, select System Set Name then enter the installation name. The name will thereafter appear in the title bar of the Nexus window and in the heading of all reports. Press OK to save the new name. Closing Nexus Nexus is a real time monitoring and control system the Nexus program and Nexus Server are designed to be run 24 hours, seven days per week. If the program is shutdown then the status of the SPUs cannot be observed and any scheduled emergency lighting tests will not be carried out. However, shutting down Nexus has no effect on the functioning of the SPUs themselves. When Nexus is started again, the status of the nodes can be polled and the system will be current again. 12 Nexus LX

17 Nexus must be running for the scheduled discharge tests to be carried out To close Nexus, select File Close or the button. Channel Display After Nexus started, it displays its main window. There are two display alternatives: Channel Display and Group Display. The Channel Display is a diagrammatic representation of one channel. When the program is started, the default channel is the trunk. The intention of the Channel Display is to show each of the nodes in correct sequence as they are connected along the channel. The channel display is only correct when the nodes are commissioned in their correct sequence. The trunk is displayed as if the Nexus Server and NUN are connected at one end of the channel this may not be the case in fact. Nexus LX 13

18 To display a particular channel click the folder symbol for that channel in the Explorer panel on the left. Figure 5: Channel Display for the System Trunk 14 Nexus LX

19 Figure 6: Channel Display Nexus Node Icons Nexus uses an icon to represent each different type of node. Any change in the status of a node is indicated by changing the appearance of its icon, as described in the table below. Component Sample Icons Icon Colour Meaning No Change Status OK Red background Unit faulty SPU Red dot Greyed out Unit under test Unit not communicating Lamp greyed out Generic decommission symbol Mains powered lamp out SPU decommissioned Or reserved Router / Repeater No change Status OK Nexus LX 15

20 Group Generic decommission symbol No change Red TEST Router decommissioned Status OK Group, or unit in group, under test Node Box If you double click a node icon, or right click and select Properties from the pop up menu, the node box for that node will appear. The node box lists all the properties and real time data relating to that node and provides access to all the tools that can be used on that node. The page tabs of node box vary depends on what type of the node is. For example, a MQF, an EFN or GPN all have some of the page tabs different because of their different functionalities. Figure 7 shows a node box for a MQF fitting. Figure 7: Node Box - Status tab 3.2 SPU Type and Status SPU Type ID and SPU Status number are two important data in the operation of the SPU node. SPU Type ID is a number which defines the description of the SPU node. For example, Type ID = 16467, its SPU description is S/F NXS ROUND SURFACE MOUNT 10W N/M 2HR. For every SPU node in NEXUS LX system they must have a Type ID. The correct Type ID value can be entered 16 Nexus LX

21 by fittings manufacture, technicians during the SPU commissioning process or user at any later stage after the SPU is commissioned. You can change the SPU s Type ID (fitting s description) at any time. Figure 8 is used for Type ID change: Node box Tool Tab Change Unit Description & Firmware. By default the user does not have the authority to change SPU s firmware. Figure 8: Change SPU Description Form SPU Status is a number to reflect the health of SPU operation. Status number is either polled or returned from the node. This number is interpreted in a way that depends on the Type ID (SPU description) of that node so it is important that the node has the correct description. Node box Status tab displays the current status for that node. If the status number is not normal, then the state is decoded and interpreted by the software and Possible Faulty Components will be listed on the page. On the Channel display, a faulty status will cause the SPU icon has a red background. Update Status Nexus operates in real-time and maintains an internal record of the current status of all the nodes on the network. If the Server has been off or disconnected and therefore unable to receive status updates from the nodes, then it is possible to perform a Status update to refresh the information in the database. If this is not done manually then the Server will after some time update all the information automatically (see "Integrity Monitor" shown on page 23). To perform a status update on: Every fitting in the network Double-click the Nexus Server icon, then on the Nexus Server tab, select Poll Status Nexus LX 17

22 All the nodes on a channel All the nodes in a group An individual fitting Double-click the channel (router) icon, then on the Status tab, select Update Status Double-click the group icon, then on the Tools tab, select Update Status Double-click the fitting s icon, then on the Tools tab, select Update Status 3.3 Using Groups Grouping is a feature of Nexus that allows some SPUs belong to different channels to be grouped together as one group. For example, Group 101 may contain SPUs like 3-10, 7-34, 12-3 etc. When a SPU is commissioned its default group number is its channel number. For example, the SPUs on Channel 2 will be put into Group 2, and so on. Any SPU can be placed into any Group at any time. However, a SPU can only belong to one Group at a time. The only exception to this is when faulty units are placed in the Maintenance Group. The scheduled discharge test can only be carried out by a group or groups, not by channels. Figure 9: Group Display Creating a Group Apart from those default groups created during the channel commissioning process, any additional groups can be created at any time. 18 Nexus LX

23 To create a Group, select the Group Display tab and select Tools Add/Edit Group. The Add/Edit Groups dialog box will pop up. Enter the Group Number and Group Name and press Add. This creates an empty Group. Changing the Name of a Group To change the name of a Group, select the Group Display tab, select the Group the select Tools Add/Edit Group. The Add/Edit Groups dialog box will pop up. Select the Edit tab, click on the name of the Group then type in the new name. Moving Nodes Between Groups To move a node from one Group to another: 1 Select the Group Display tab 2 Select the Group containing the node to be moved. 3 Right-click on the node and select Cut from the pop-up menu 4 In the Explorer, right-click on the Group the node is going into. 5 Select Paste from the pop-up menu. To move multiple nodes from one Group to another use the drag and drop method: 1 Select the Group Display tab 2 Select the Group containing the node to be moved. 3 Select the nodes - click on the first node then ctrl-click on the remaining nodes 4 Click on one of the selected nodes and drag the selection into the Explorer panel on the left and drop them on the folder for the destination group 5 A confirmation box will pop up select Yes. Maintenance Group The function of this Group is to flag SPUs that need attention. There are 3 sources of fault to make a SPU enter Maintenance Group: 1. A real time status fault; 2. Failed 1 minute diagnostic test; 3. Failed scheduled discharge test. To get a SPU out of maintenance group, it needs to clear all the faults which made it in. For example, a SPU is in maintenance group because of failure of last schedule discharge test. If this is the only reason in maintenance group, then it needs to pass another scheduled discharge test to move out of the maintenance group. Maintenance Group is a special group which the group members can not be moved in and out like normal groups. Any SPU becomes faulty will enter this group. The only way to get out of maintenance group is to clear all the faults made it in. Maintenance Group can not be scheduled for discharge test either. It is really a visual collection of faulty SPUs. It is not like a normal group which has LNS network group addressing functionality. Re-Test Group The function of this Group is to make sure the SPUs in this group must have another scheduled discharge test passed. Any SPU from any normal group can be moved into Re-Test group but the only way out is to pass a scheduled Re-Test Group discharge test. If a SPU passes the Re-Test Group Nexus LX 19

24 discharge test, it moves out of Re-Test Group and back to its own group automatically. If it fails, it stays in Re-Test group until one day it can pass another Re-Test group discharge test. Re-Test Group is more like a normal group which SPUs can be moved in from other groups and can be scheduled for discharge test. The only difference is the SPUs in Re-Test Group can not be moved out like the normal group. 3.4 Emergency Lighting Tests Every Nexus SPU is able to disconnect its own emergency circuit from the mains for a set length of time in order to simulate mains failure. This is done on command from the Nexus Server. The mains is automatically re-connected by the node when any of the following events occurs: The pre-set time period expires The battery voltage drops below the pre-set limit (battery cutout) The lamp fails A stop test command is sent by the server (the test is aborted in this case) The time elapsed from test start to test finish is measured by the SPU and recorded along with the date and time of test, end-of-test status and the required discharge time. The Emergency Lighting testing process consists of 5 stages: 1 Perform a Diagnostic Test (which can be performed on the whole system, or by group, channel or individual fitting). 2 Perform a Full Discharge Test (which can be performed on groups only). 3 Repair any failed fittings. 4 Retest any failed fittings. 5 Update the maintenance logbook. Diagnostic Test In a Diagnostic Test, the required discharge time is one minute. The purpose of this test is to briefly test the function of the SPU without fully discharging the battery. To perform a diagnostic test on: Every fitting in the network All the nodes in a channel All the nodes in a group An individual fitting Right-click the Nexus Server icon, then select Properties, then Diagnostic Test Double-click the Router icon, then on the Status tab, select Diagnostic Test Double-click the Group icon, then on the Test tab, select Diagnostic Test Double-click the fitting s icon, then on the Test tab, select Perform Diagnostic Test 1 A confirmation box will pop up. Press OK. The Diagnostic Test will start immediately. 2 After about a minute, the system will retrieve the test results from each of the fittings. These can be viewed in the Test Results report (see "Reports" shown on page 23). Alternatively you can look at the results for individual nodes from within the node box for that node. In the Test tab, last Diagnostic Test result is displayed. 20 Nexus LX

25 3 All previous Diagnostic Tests and Scheduled Discharge Tests results are listed in All Previous Result combo-box on the Test tab of node box. Once a test result is selected its details of the test result are displayed. 4 Each SPU should pass the Diagnostic Test before it is subjected to a Discharge Test. After fixing and retesting any faulty fittings, you can proceed to the discharge test. Discharge Test The purpose of the discharge test is to allow a test to continue to the point of battery cut-off. The discharge time achieved in this way is a comprehensive figure of merit for the health of the SPU. The pass time for a fitting is 120 minutes for the first time the test is run and 90 minutes for each subsequent time (ie at least every 6 months). The set time for a discharge test is 240 minutes. This is enough time for all fittings to fully discharge. This test is only performed on Groups. Note that by placing fittings into groups scheduled to test at different times, you can avoid having all the emergency lighting recharging at the same time. If Nexus is shut down prior to the test, any scheduled tests that fall due will not be performed. The next time Nexus is opened you will be asked if you want to carry out the tests. If you select to carry out the test, the test will start immediately. If you select to cancel the test, then the pending test record is deleted, no test will start. You may need to re-schedule another test. REMEMBER: Battery Packs must be allowed to charge for at least 16 hours before a full discharge test. 1 To perform a Full Discharge Test: 2 Select the Group in the Group Display that you want to test. 3 Press on the toolbar. The Program a Discharge Test dialog box will pop up (see Figure 10) 4 Set a time and date for the test. 5 Select Timeout Duration: 125 min or 240 min (normal case) 6 Press Confirm Test. 7 Select OK. Nexus LX 21

26 Figure 10: Schedule a Discharge Test The Discharge Test will be performed at the time chosen. There is a report available which shows the test schedule (Scheduled Group Discharge Tests report). The system will automatically poll and record the test results 125 or 240 min after the start of the test. These can be viewed in the SPU Discharge Test Results report. The results for an individual SPU can be viewed in the node box in the same way as for Diagnostic Tests at any time after the termination of the test on that node. 22 Nexus LX

27 3.5 Reports Figure 11: NEXUS LX Reports NEXUS LX provides a variety of reports (see Figure 11). To make a report: 1 Click Reports menu item on the main form to open Report Selection Options form (Figure 11). 2 Select the required report from the Available Reports list. 3 Set Report Selection Criterias for the report. 4 Click Make Report button to generate the report. 5 To print the report, select the print button in the top left hand corner of the report. To export the report, select the button. 6 Click the icon in the upper right of the dialog box when you are finished. 3.6 Integrity Monitor Nexus monitors the network periodically as background operation to check the integrity of the routers, repeaters, SPUs and data cable. When Nexus starts, Integrity Monitor is enabled and it polls the nodes at roughly 5 seconds interval. The current polling node is displayed on the bottom status bar. Integrity Monitor operation can be turned off. To turn off Integrity Monitor, on the main form top menu System Disable Integrity Check, Poll OFF will be displayed on the bottom status bar. Nexus LX 23

28 3.7 Maintenance Emergency Lighting testing and maintenance is a statutory requirement. The system must be tested every 6 months and the results must be recorded. Thereafter any faults must be rectified with the maintenance actions recorded in a log. The Work Instruction Report will provide a list of all fittings that require attention. Note that the suggested corrective actions in the report are a general guide as to the likely nature of the problems. Maintenance Procedure: 1 Generate a Work Instruction Report 2 Identify the fittings requiring maintenance using the location data in the report - use the SPU s node box Tool tab Yellow Blink function as an aid to locating the fittings. 3 Repair or replace the fittings as required. 4 Enter Maintenance Details. This is the logbook it should always be kept up-to-date to ensure full compliance with AS/NZS See Figure Retest repaired/replaced fittings. Figure 12: Node box Maintenance History When you enter the details of maintenance performed you should then move the repaired fittings into the Retest Group, using Cut and Paste or Drag and Drop. Note that the icons for those fittings will also remain in the maintenance group until they have passed the appropriate tests. Schedule the Retest Group for testing. 24 Nexus LX

29 Yellow Blink This function causes the LED in any SPU to blink yellow as an aid to location. Double click SPU icon to open its node box. On the Tools tab select Yellow Blink ON. To stop blinking, select Yellow Blink OFF. Or Double click the Maintenance Group icon. On the Tools tab, select Blink maint. Group. To stop the blinking select Stop Blinking. Entering Maintenance Details 1 Open the SPU node box, on the Maint tab and press Enter Details. The Maintenance Details dialog box opens - in the Replaced section, check the boxes corresponding to any of the maintenance actions performed. Enter a Comment if required, and the name of the repairer in Carried Out By. 2 Press Save to save the details to the database then select OK. View Maintenance Log Book View the maintenance log book from the reports menu by selecting Maintenance History report. Retest Repaired Fittings To retest repaired fittings, select the Retest Group. Press on the toolbar. In the Program a Discharge Test dialog box set a time and date for the test. Press Confirm Test then select OK. The Discharge Test will be performed at the time specified. Any units that pass the test will be removed from the Retest Group and the Maintenance Group and will appear in their normal group. 3.8 Nexus Network Management The sequence for commissioning a Nexus Network is set in Installation Guide and Commissioning Guide. Commissioning the NUN The NUN should be the first node commissioned ie before any of the routers are commissioned. If the NUN has not yet been commissioned, select Tools Commissioning NUN, click Commission then press the service request button on the NUN. Note that the NUN may also be commissioned from within the Network Utility Program (shown on page 31). Commissioning Routers 1 Select the Channel Display tab. 2 Select Tools Commissioning Router/Channel. The Add Router dialog box displays. 1 Select the Channel number from the dropdown list (up to 127). Nexus LX 25

30 2 Select the Near Side and Far Side Router types the default is 78kbps for standard data cable channels. 3 Press Commission. The dialog box displays "Press the Router Service Pin". 4 Go to the Router and press the Service Request button, located on the front of the Router. The dialog box will display a progress bar then "Successfully installed Router xx" when finished. Both SERVICE REQUEST LEDs on the Router will remain OFF when the Router is properly commissioned. 5 Repeat these steps until all Routers are registered into the Nexus database. 6 Press the icon in the upper right of the dialog box when finished. Correcting Router Registration Mistakes If you register a Router with the wrong Channel number, you can only correct this if either no nodes have yet been commissioned onto that channel, or you de-commission any nodes that have already been commissioned onto that channel. For this reason it is very important that the Routers are commissioned and verified correct before any nodes are commissioned. To change the Channel number of a Router you must decommission it and then re-commission it with the correct channel number. To decommission a Router, double-click the router s icon, select the Tools tab, then De-commission Router. A dialog box is displayed, asking you to confirm - select Yes. To re-commission a Router, double-click the router s icon, select the Tools tab, then Re-commission Router. The Re-Commission Decommissioned Router dialog box displays select Commission and then press the Router Service Pin. Commissioning Repeaters 1 Select the Channel Display tab. 2 Select the Channel, which contains the Repeater by clicking on it in the Explorer. 3 If the repeater is in the trunk, double-click the Nexus Server icon and then select Install Repeater. If the repeater is in a channel, double-click the channel s router icon, then select the Tools tab, then select Install Repeater. The Install Repeater dialog box opens: 4 Select the Near Side and Far Side Repeater types - the default is 78kbps for standard data cable channels. 5 Select Commission. A message is displayed: "Press the Repeater Service Pin". 6 Go to the Repeater and press the Service Request button. 7 The dialog box displays a progress bar and "Successfully installed Repeater xx" when the process is complete. 8 Press the icon in the upper right of the dialog box when finished. Changing Repeater Sequence After a repeater has been commissioned, its icon will be inserted in the channel display after the router 26 Nexus LX

31 and after any repeaters previously commissioned. The channel display is not an exact representation of the physical channel, but it can be close. The Repeater icons can be moved (using drag and drop) to a position on the channel display that represents their real location. For instance, if on Channel 2, there is a repeater installed between nodes 2-35 and 2-36, then: click on the repeater icon, drag it and drop it on the icon for node The Repeater icon will then be inserted between the two SPU icons. Repeaters on the trunk can be moved in the same way. There is an alternative method for changing sequence. Double-click on the repeater icon and select Change Repeater Position. Choose the correct location from the pull down box. Commissioning SPUs SPUs must be commissioned in the correct channel sequence otherwise they will be assigned an incorrect Channel Sequence number. Start at one end of the channel and work towards the other end. Note that you can tell by looking at a SPU whether it has been commissioned. The LED of an uncommissioned SPU will flash green. The LED of a commissioned SPU will be a static red. For more information about the LED colours that a SPU may display, see Nexus Error Messages (shown on page 52). To commission SPUs: 1 Select the Channel Display tab. 2 Select the Channel that SPUs are going to be added to by clicking on the folder in the Channel Display list. 3 Select the button in the toolbar or select Tools Commissioning Emergency Light. The Add Device dialog box pops up - Next Unit to install displays the next available Channel Sequence Number. 4 Set Device Category for the type of device you want to install. The default is Emergency Light 5 Press Commission - the dialog box displays a prompt instructing you to press the button on the SPU. Go to the selected SPU. The LED of an uncommissioned SPU will be a flashing Green colour. Push the test button, then release it. At the end of the commissioning process after about 10 seconds - the LED should change to static red. The dialog box displays a progress bar and, when the SPU is registered, "Successfully installed SPU x-x". 6 It is critical to keep SPU Channel Sequence Numbers in order. If there are SPUs that have not yet been installed, or if you know that there will be SPUs installed in the future, you can reserve Channel Sequence Numbers for them. In this case select Reserve. The place of the SPU icon. icon will be put in 7 Next Unit to install will increment. Repeat the process until all SPUs have been installed for that Channel. 8 Click the icon in the upper right of the dialog box. You can return and add further SPUs to a Channel at any time. Note: Error Messages. Most errors encountered during node registration are caused by poor communications due to faulty data cabling. Communications faults must be located and fixed before the node(s) can be commissioned. Nexus LX 27

32 Decommissioning and Recommissioning SPUs When you decommission a node, the decommissioned symbol is displayed in the Channel Display. Decommissioned nodes can be recommissioned later. To decommission an SPU, double-click its icon, select the Tools tab, then De-commission SPU. A dialog box is displayed, asking you to confirm - select Yes. To recommission a node, double-click on the icon. The Re-Commission SPU dialog box will pop up. Select Commission, then press the test button on the SPU. Inserting Extra SPUs Even if nodes have already been allocated Channel Sequence Numbers, you can add extra nodes between them. To add extra nodes (for example between nodes 4-5 and 4-6) right-click on SPU 4-5 and select Insert Device. The Device to Commission box pops up. Select the type of device to insert in this case it is an Emergency Light. The Add Device dialog box pops up. The first node is numbered and you can add nodes up to Commission the node in the usual way. You can decommission, recommission and reserve an inserted node as you would any other node. Edit Location Details for Routers, Repeaters and SPUs To edit the location details for an SPU, double-click the SPU icon to open node box. Select the Details tab, and then Edit Location Details button. A table lists all location details of this channel SPUs is displayed. Enter the appropriate information. It is possible to move directly to the next SPU in sequence from this window and to copy data from the previous SPU. For Routers, double-click the Router icon and select the Tools tab. Select Enter/Edit Location Details, A table lists all location details of all routers and repeaters is displayed. Enter the appropriate information. For Repeaters, double-click the Repeater icon and select Edit Location. A table lists all location details of all routers and repeaters is displayed. Enter the appropriate information. Packet Counting Packet Counting is a process that is used to test data communications quality. To perform a packet count for all the Routers on the Trunk, double-click on the Nexus Server icon, select the Communications tab, then select Start. The result (Pass or Fail) will be displayed in the box. You can also individually packet count routers from the Router dialog box. Double-click on the Router icon, select the Comms Test tab and then under Perform Router Packet Count select Start. The result (PC %) will be displayed in that box. To packet count all SPUs in a channel, double-click on the Router icon for that channel, select the Comms Test tab and then under Perform Channel Packet Count select Start. The result (Pass or Fail) will be displayed in the box. To packet count individual SPU, double-click on the SPU icon, select Tools tab and then under Perform Immediate Packet Count select Start. The result (Pass or Fail) will be displayed in the 28 Nexus LX

33 box. It is possible to display the packet count % result for each device underneath that device in the Channel Display. This is an alternative to displaying the Channel Sequence number or Router number. For the trunk press the button or the button to toggle between displaying the Router Number and the Packet Count. For a channel press the button or the button to toggle between displaying the Channel Sequence Number and the Packet Count. 3.9 Nexus Database The Nexus database is a set of database files that stores the details of all the SPUs, routers and repeaters on the network. When the Nexus program is started for the first time on a PC, a blank database is created. As routers, repeaters and SPUs are commissioned, they are added to this database. The database can be backed up, deleted and restored from backup as required. Backing Up the Database It is necessary to back up the database information to prevent loss of data. Stanilite recommends that you backup the database regularly onto external (removable) backup media. Backups should be performed at least: After each major maintenance (i.e. after testing and repairs have been completed every 6 months). Whenever new fittings are added or old ones removed. Whenever fitting descriptions are changed. To create a backup 1 Select Tools Database Save. A confirmation box will pop up select Yes. Nexus 2000 will shut down automatically and the Save Database Utility window will open 2 Select either Save database or Zip Save database. The Zip Save database option will backup the database in a compressed format. 3 Select Choose Location. The Browse For Folder dialog box will open 4 Select an existing folder or create a new folder then select OK. 5 Select Save Database. A confirmation box will pop up select Yes. 6 A dialogue box opens that says 'The saving of the database was successful. Do you wish to start Nexus LX?' 7 If you want to start Nexus, select Yes. 8 Copy the saved database to external media and keep in a secure location away from the computer. Retrieving databases Loading a backed-up database back into Nexus is a specialist task. It should only be necessary when the Nexus Server has been lost or destroyed. In this circumstance contact Stanilite for advice. Nexus LX 29

34 30 Nexus LX

35 C H A P T E R 4 4. Network Utility User Guide In This Chapter Network Utility Program Commissioning the NUN Discovering Nodes Getting Info from Nodes in the Table Sorting, Saving and Retrieving Node Tables Setting Routers and Repeaters Online/Offline Packet Counting Nodes Identifying Nodes Discovering Hidden Nodes Shutting Down the NUP Network Utility Program The Network Utility Program (NUP) is used in conjunction with the Network Utility Node (NUN) to test the data communications of a Nexus network 4.2 Commissioning the NUN The NUP shares the Nexus database. It can be run at the same time as Nexus LX. Whichever program is run first on a new server will create a blank Nexus database. In the NUP: The NUN should be the first node commissioned ie before any of the routers are commissioned. Select Start Programs NEXUS LX Network Utility Choose the network interface usually LON1. The NUP will start and if the NUN has not been commissioned yet, will prompt to press the service request button on the NUN. In this case press this button to commission the NUN. Nexus LX 31

36 (Note that the NUN may also be commissioned from within Nexus (see "Step 3: Commission the NUN" shown on page 45). Figure 8: Network Utility Program Window 4.3 Discovering Nodes The NUN is able to discover nodes connected to the network. It does this by sending out multiple requests for all nodes to transmit back in response. Select Action Discover devices or click the button. The NUP will then discover all devices that it can communicate with. Routers will generally be discovered before SPUs because they are programmed to respond with a higher priority. The discovery process can take a long time to finish because it attempts to communicate with nodes that may be communicating very poorly. It is not necessary to let this process run until it stops itself. Use the button to terminate the process when enough nodes have been discovered. Once a node has been discovered, the NUP displays its Neuron_ID, Program_ID and Type on one row in the main display table. 4.4 Getting Info from Nodes in the Table If nodes have been commissioned previously, there may be additional useful information stored in them. To display this information, first select the desired nodes by clicking on each row then click the click the button. To select all nodes in the list, click the button again. button. To de-select a row, click on it again or 4.5 Sorting, Saving and Retrieving Node Tables Delete Rows To delete a row, highlight it by clicking on that row then either use the Delete button on the keyboard or the button. To delete multiple rows highlight using the ctrl or shift buttons on the keyboard together with the mouse, then the button. Sort Rows Rows may be sorted according to the contents of a particular column. To do this, click the column 32 Nexus LX

37 label (eg Type, PC% etc). Click the label again to sort the table in reverse order. This can be useful for displaying nodes in order of increasing or decreasing packet count or for displaying nodes in order of channel sequence although this last one can only be done after a site has been commissioned. Copy and Paste Table The list of Neuron IDs for each channel can be very useful for diagnosing communications problems. The contents of the currently displayed table can be saved to a file and pasted back in from a file. It can also be pasted into a program such as Microsoft Excel if required. To copy a table into the Windows clipboard, first delete any unwanted rows and then click the button. Open a document in another application (such as Excel, Notepad etc) and paste using that program's menu. To copy a table directly to a text file in tab-delimited format, select Save Tab Delimited from the menu. A new form will be displayed prompting for a file name and location. Choose a filename and location and Save. To paste the contents of a file back into the table, open the text file (using say Windows Notepad) and copy the contents to the Windows clipboard (ie select data then Edit Copy). Go back to the NUP and either select Edit Paste or click table.. This will append the data to whatever rows are displayed in the Using this method, it would be possible to store the Packet Count results for each channel on the site either in one file or in individual files. 4.6 Setting Routers and Repeaters Online/Offline Routers and repeaters can be online or offline. When they are online, they transfer packets as required. When they are offline they will not transfer packets. This property is useful when you are only interested in nodes on one particular channel. If you set all the routers on the trunk offline except for the one on the channel you are interested in then the discovery process will only discover nodes on that channel. To set a router offline, it must be in the list of discovered nodes. Select the router from the list by clicking in the checkbox on the left in the Neuron ID column then click the button. If the discovery process is run again, that router will prevent nodes on that channel responding. You must turn all the routers and repeaters back online before you attempt to use Nexus again otherwise those channels will not communicate. To do this, select them and click the button. 4.7 Packet Counting Nodes The NUN uses a packet counting process (see "Data Test Mechanism Packet Counting" shown on page 41) to test the quality of the communications with a node. Once a node has been discovered and is in the main list, it can be packet counted. To do this, select the desired nodes individually or select them all by using the button. Click the button to start the packet count process. This process may take some time depending on how many nodes were selected and how good the communications are on that channel. As each node is tested, a Packet Count result will be displayed. There are 3 parameters that can be set for packet counting. They are displayed on the right hand end of the toolbar. Nexus LX 33

38 The first is the transaction timer. The default value is 48 milliseconds. This value is OK for most circumstances, although when nodes are situated behind a number of repeaters in series it may be necessary to increase this value. The second is the number of packets. The default is 100 packets. This value may be reduced to give a faster though less accurate result. The third is the wink interval. The default is 500 milliseconds this will result in an LED blink rate of 1 per second. 4.8 Identifying Nodes It will often be necessary to physically identify nodes listed in the NUP table. In particular you may want to identify which nodes are communicating on a channel so that you can determine which are not. There are two methods available: Winking Nodes The Wink by Neuron ID function blinks the red LED on a single highlighted SPU at a rate of approx once per second. To do this, highlight the desired node and select Action WinkbyNeuronID or click. The Wink all function sends out a broadcast wink command which causes every node to wink. Note that any nodes on channels behind routers or repeaters that have been put offline will not wink. To do this select Action Wink all or click. To stop the wink select Action Stop or click. Comments Column The comments column is used to record any comments about nodes. To add a comment, double click over the comments cell for a particular row. Receiving Service Pin Messages When the SPM checkbox in the main toolbar is ticked, the NUP will respond when the test button of a node that is listed in the table is pushed. A box will pop up displaying the Neuron_ID of the node. When you acknowledge this box by clicking the OK button, the row for that node will be highlighted. This is the main method whereby nodes in the table can be physically identified. It is most useful when nodes have not yet been commissioned and there is not yet any information available to distinguish one node on a channel from another. 4.9 Discovering Hidden Nodes Once a node has been commissioned, it has an address stored within it. That address is made up of a number of parts, one of which is its channel. If you disconnect a commissioned node from one channel and connect it to another, and then attempt to discover all the nodes on that second channel, this node will not be discovered. The reason for this is that the router on that second channel will not transfer the responses from that node back to the trunk because it thinks they are coming from the wrong channel. In order to discover nodes that may have inadvertently been swapped around, it is necessary to temporarily change the router so that it acts as a repeater. In this case a repeater will transfer the response from the node because a repeater is not selective in what it transfers. 34 Nexus LX

39 This function is one of a set of functions for advanced users of the system. To turn a router into a repeater, right click the mouse on the desired row and select Make repeater. After you have finished discovering that channel, restore the router to its normal mode by selecting Make router in the same fashion Shutting Down the NUN Shut down the program either by using Action Exit or by clicking the icon in the upper right of the dialog box. This will pop up a reminder to turn any temporary repeaters back into routers and to turn them back online. You will have to respond yes to this in order to shut down. This will not carry out those actions for you it is simply a reminder to do so. Nexus LX 35

40

41 C H A P T E R 5 5. Installation Guide There is a product specific installation sheet packed with every Nexus product. That document sets out in detail the procedure for mounting the product and connecting it to the data network and the mains supply. In This Chapter Data Cable Connection Data Communications Testing Data Communications Preparation for Commissioning Installation List Data Cable Connection Stanilite (or its agents) will not commission incorrectly wired installations. Data Cabling Rules It is the installer s responsibility to ensure compliance with relevant standards for installation of cabling. Data cable must be installed by a registered Cabling Provider in accordance with the requirements of AS/ACIF S009 if the Nexus Server will be connected to the PSTN. Additional information is available in this guide (see "Nexus System Design Sequence" shown on page 5). Data cable connection The standard Stanilite Nexus data cable is a single twisted data pair plus shield. The two data wires are blue and white respectively. Nodes are connected in parallel across the data pair refer to the figure in SPU Data connection (shown on page 37). The data pair is unpolarised. The shield consists of a foil wrap with a copper drain wire. The shield is connected so as to maintain continuity across all the joins along the entire length of a channel segment. The shield must remain electrically isolated from the data pair and any other metalwork or potential earthing point throughout the length of the channel segment, except for the one point where it must be connected to earth. Earthing points are provided for this purpose at Routers and Repeaters. SPU Data Connection SPU nodes have either a 2 terminal or 3 terminal connection for the data cable. When there are 2 terminals, they are for the data pair. When there are 3 terminals, the two outer terminals are for the data pair and the central terminal is for the shield. This central terminal is floating specifically it is not connected to earth. It is provided for the convenience of joining the drain wires. In a 2 terminal SPU connection, the shields are twisted together and folded back along the data cable and insulated. In Nexus LX 37

42 a 3 terminal SPU connection, the shields are joined in the centre terminal. Figure 9: Data cable connection for 2 and 3 terminal SPU connection Figure 10: Data cable connection for 2 and 3 terminal SPU connection cable end Router and Repeater Data Connection A router is a device that selectively transfers data packets between the trunk and a channel. It consists of 2 nodes, A and B, internally connected back to back. By convention node A is connected to the channel and node B is connected to the trunk. A repeater is a device that transfers all data packets between one channel segment and another channel segment. Routers and repeaters are physically identical but have a different software configuration. The following figure shows the router connections required for the most common network configuration. Note that the terminators for each node in the router are only switched on when that router node (A or B) is at the end of a channel segment. 38 Nexus LX

43 Routers and repeaters always have a 3 terminal data connection. The centre pin in the data cable terminal block for routers and repeaters is earthed. As with any other channel segment, the Trunk cable shield must only be connected to earth at one point. Refer to the following figure, which shows an example of how shield earthing should be done on the trunk. The shield earthing arrangement must be recorded on the as-built plans. Figure 11: Typical router data cable connection Data Cable Preparation for 2 terminal connection This is the procedure for preparing the data cable for a 2 terminal data connection in the middle of a channel segment or a 3 terminal router or repeater connection when the shield is connected to earth at another location: Strip back and remove the outer yellow sheath of both cables for approximately 30mm from the end being careful not to damage the conductor insulation under the shield. Peel back the shield to the level of the outer sheath and unravel to allow it to hang away from the cable to expose the inner insulated conductors. Remove the foil shield leaving the shield drain wire. Strip the data wires as shown. Nexus LX 39

44 Holding the cables side by side, twist the drain wires of the two cables together. This will provide for continuity of the shields. Twist the data wires into like coloured pairs and fold the drain wires back as shown. Bind with tape, ensuring that the shield is fully insulated, then insert the prepared cable into the terminal block and secure with a cable tie. Note that some products have a fixed terminal block for data cable connection. Data Cable Preparation for 3 terminal connection This is the procedure for preparing the data cable for a 3 terminal data connection or a 3 terminal router or repeater connection when the shield is connected to earth: Prepare the cable ends as shown. Holding the cables side by side, twist the drain wires of the two cables together and twist the data wires into like coloured pairs. Insert the prepared cable into the terminal block and secure with a cable tie. Note that some products have a fixed terminal block for data cable connection. 5.2 Data Communications This section describes the format of Nexus data, it's transmission, testing and diagnosis of faults. Data Packets The Nexus system communicates using a packet switching network. Data is contained within a discrete structure known as a packet. The data packet is a series of voltage transitions on the data cable within a channel segment. A transaction between nodes generally consists of a number of packets sent back and forth the between the nodes. If one or more of the packets is damaged, the transaction will fail and the Nexus system will report an error. By far the most common cause of damage to data packets is faulty data cable installation. Transmission Line When a data cable is long and the data rate is high, the data cable acts as a transmission line. 40 Nexus LX

45 Connections made to a transmission line must meet certain criteria if the data transactions are to succeed. If the cabling limits and structure defined by the channel segment are satisfied then the criteria for a transmission line will also be satisfied. Consequences of Faulty Data Cable Installation A correctly installed channel segment is effectively a single length of data cable with a terminator at each end and with nodes connected in parallel along its length. The cabling limits for a channel segment using standard Nexus data cable are 50 nodes over 1000 metres of cable. The shield is continuous along its length and is earthed at one point. If the cable is too long, a signal sent from one end of the cable will be attenuated (ie reduced in amplitude) by the cable resistance as it travels along the cable to the point where the signal amplitude will be too low for reception by a node at the far end of the cable. If too many nodes are connected along the length of the cable, the loading imposed by each of the nodes will attenuate a signal sent from one end of the cable. The result will be the same as if the cable were too long. If one or both of the terminators are left off then communications on that channel will be disrupted. This is because without the terminators, the unterminated ends of the data cable reflect signals generated by nodes on the segment. These reflected signals interact with the signals themselves, resulting in distortion or even cancellation of the original signal. This may prevent the intended recipient nodes from correctly receiving the signal. If the data cable is broken at one point, the remaining section of data cable will be unterminated and communications will be disrupted in the same way. If just one conductor of the data pair is broken, signal current may still flow via the stray coupling capacitance to the shield so that units beyond this break may still communicate to some extent - although communication will be severely disrupted. If additional terminators are connected to a channel segment, the impedance of the cable circuit will be lowered in the vicinity of the extra terminators. This will result in excessive attenuation of the signal. If a T junction is used within a channel segment, that segment will effectively have 3 ends rather than 2. In this case signals generated by a node on this segment will reflect off the transmission line discontinuity caused by the T junction resulting in the same kind of distortion caused by lack of terminators. If two dissimilar types of data cable are used within a channel segment, the junction between the cables is a transmission line discontinuity. This will cause reflections and consequently, signal distortion. If the shield is not connected to earth and is left to float, then the capacitive coupling of external noise sources to the data pair is increased, and the potential for signal distortion is increased. When the shield is earthed, the capacitive coupling is reduced and the cable is effectively shielded from external electric field disturbance. Data Test Mechanism Packet Counting The basic data test mechanism in Nexus is packet counting. This is one of the principal functions of the NUN. Packet counting involves sending out a string of data packets to a specific node requesting a response. If 100 requests are sent out and 100 responses are received back, the packet count for that node is 100%. If there is a fault in the data cable installation for that channel segment, the packet count may be less than 100% depending on the type of fault and where that particular node is located on the segment. If every node on a segment returns a packet cont of 100%, then that segment has no faults. For the NUN to be able to packet count a node, it must know its identity. Each node is identified by Nexus LX 41

46 two numbers (see "Number the Channels and Apply Channel Sequences" shown on page 7) the Channel Sequence Number and the SPU_ID. These numbers are only associated with the node after it has been registered onto the system. Prior to that, the node can be referred to by its Neuron_ID. This is a unique 48 bit number built into each Neuron microcontroller at the time of manufacture. The NUN uses a process of discovery to determine the identity of nodes so that they can then be packet counted. Diagnosis of communication faults Communication problems are nearly always caused by incorrect wiring of the data cable. Symptoms Some nodes not discovered, some communicate perfectly but others communicate poorly Most or all nodes discovered, some communicate perfectly but others communicate poorly Possible causes: One or both terminators not connected Broken or cut data cable either one or both conductors Wrong wiring topology (e.g. a "T" or star connection made at a node) Intermittent connections due to broken conductors or loose or over-tightened terminal screws More than two terminators connected to a channel segment Too many nodes on a channel segment Channel segment too long Incorrect connection of cable shields Wrong Data Cable type The nearness of the data cable to electromagnetic noise sources Remedial Actions: Check each end of the channel segment to see if the terminators are connected. Identify which nodes have been discovered and which are suspect. Check the Service Pin Message (SPM) box (near the top of the window). Press the test buttons on all the units on the channel, working from the router out along the channel. If a service pin message is received from a fitting with a Neuron_ID that is not in the list it will be added and highlighted. Query and packet count any fittings found in this way. Check the data cable connection at the last good node then at each suspect node In most cases the cause of the problem will be found where one or more of the nodes connects to the channel. It is less common to find a problem in the data cable between nodes although it is possible the cable is cut as a result of construction or refurbishment processes. Symptoms No nodes discovered 42 Nexus LX

47 Some nodes not discovered, but the remainder communicate perfectly Likely causes: The mains circuit may not be switched on The circuit breaker may have tripped out The data cable may not be connected The router or repeater may be switched off or not connected The router or repeater may be in an unconfigured or offline state (perhaps left in that state by the operator using the NUN) The router or repeater may have been physically connected to a different channel without being recommissioned onto that new channel There may be no data cable to that particular fitting The fitting has previously been commissioned on another channel then connected to the new channel without further change The fitting may be defective Remedial Actions Check the power supply to routers, repeaters and fittings Check the data connections at routers and repeaters Identify which nodes have been discovered and which are suspect Check the Service Pin Message (SPM) box (near the top of the window). Press the test buttons on all the units on the channel, working from the router out along the channel. If a service pin message is received from a fitting with a Neuron_ID that is not in the list it will be added and highlighted. Query and packet count any fittings found in this way. If a fault is found, repair the fault and run the test again. Repeat this process until the channel is perfect. A channel must not be commissioned until all the fittings are communicating perfectly. A perfect packet count is anything in the range of 98% to 100%. 5.3 Testing Data Communications The data network installation is not complete until it has been fully tested and shown to operate without fault. In order to test the network it is necessary to use a Nexus Server together with a Network Utility Node. Step 1: Ensure Site is Ready for Data Network Test Nexus LX 43

48 Continuously switching the mains supply to SPUs on and off will cause the SPUs to discharge and recharge their batteries many times over a short period. This will shorten the life of both batteries and lamps. The SPUs are designed to be discharge tested once every 6 months (as per AS/NZS ). Discharge testing in excess of this is an abuse of the fittings. Any warranty on the life of the batteries may not be honoured if they are subjected to such operating conditions. 1 In preparation for this stage, ensure that the mains supply to the emergency lighting network is on and stable. The mains supply to the server, NUN, routers, repeaters and emergency fittings must not be interrupted during the testing phase. 2 Prepare your channel lists (lists of routers, repeaters and SPU fittings on each channel) using the provided format found in the back of this manual (see "Installation List" shown on page 47). 3 Have with you your lists that contain the channel details so that during the discovery process you can determine if all fittings have been found. 4 Have with you the as-built site drawings with the fittings and cable routing indicated on them so as to assist you to diagnose any problems if there are fittings that are not discovered. 5 Make sure that all required end of line terminators are in place or turned on. 6 Have all routers and fittings installed with the mains supply connected and turned on prior to the commencement of the commissioning process. 7 If you intend to perform your commissioning (2 hour) discharge testing directly after commissioning the fittings you must have uninterrupted mains supply to the fittings for a minimum of 16 hours prior to the discharge test or adverse results will be achieved. Step 2: Setup the Nexus Server When setting up the Nexus Server, insert the Nexus CD before installing any interface hardware or software. Generally speaking the Nexus Server is setup in the factory and should arrive on site ready for use with sufficient device credits. If for whatever reason the server needs to be set up then follow the procedure below: 1 Insert the Nexus CD in the Nexus Server's CD-ROM drive 2 Install the LNS Server 3 Install any LNS Service Packs if it s available Do not reboot the PC after installation 4 Identify the interface card you will use PCLTA-20 (preferred) Internal PC PCI BUS. PCLTA-10, Internal PC ISA BUS. PCC-10, Type II PC card (for use with Notebook PCs) SLTA-10 External Interface (for use with Notebook PCs) 5 Install the interface device driver software Do not reboot the PC after installation. 6 Install NEXUS LX 7 Shut down and power off the Nexus Server 44 Nexus LX

49 8 Install the interface device 9 Restart the Nexus Server The installation of the driver software must be completed before inserting the interface card into the PC slot Step 3: Commission the NUN Open the Network Utility Program by selecting Start Programs NEXUS 2000 Network Utility. The program will prompt you to press the service pin of the NUN. Step 4: Discover all the Routers Once the Nexus server is setup correctly, the next stage involves testing and commissioning the routers on the trunk. The trunk must be confirmed operational before the channels are tested. Discover devices by selecting the As soon as any SPUs begin responding, stop the NUN (use the (select the rows then use the icon. All the devices connected to the trunk will be discovered. icon), delete the SPUs from the list icon), and then set the discovered routers offline (select the rows then use the icon). When a router is set offline, it will block any messages from its far side so that nodes on that side will not be discovered. Repeat this process until only routers get discovered. If the expected number of routers is not discovered then action must be taken to rectify the communications problem (see "Data Test Mechanism Packet Counting" shown on page 41). Step 5: Packet Count the Routers Select each router. Begin the packet count by selecting the icon. The approximate time remaining is displayed on the right hand side of the status bar at the bottom of the window. The packet count percentage (PC%) is displayed for each router. If any of the routers has a packet count below 98% then there is a communication problem that must be resolved (see "Data Test Mechanism Packet Counting" shown on page 41). Step 6: Commission the Routers Any communications faults on the trunk must be rectified before proceeding to the next step. You must not commission a router if its packet count is below 98%. The next task is to commission all the routers. For information about doing this, see Commissioning Routers (shown on page 25). Note that in order to commission the routers you will have to run Nexus. Once the routers are commissioned return to Step 7. Step 7: Obtain Router Information Select each router. Click on the icon. A channel number is displayed in the channel column. It can be useful to save the information from the NUP. Save the list of routers by selecting Save on the menu bar; select Tab Delimited then choose a location to save the file. Nexus LX 45

50 Step 8: Discover and Packet Count the SPUs on each Channel At this stage, all the routers connected to the trunk must be communicating perfectly. 1 Return to the Network Utility Software. For each channel: 2 Set all the routers on other channels offline (select the rows then use the icon), leaving the router of interest online. 3 Discover SPUs by selecting the icon. 4 Allow the discovery process to finish without interruption. The number of fittings discovered on the channel should match the floor plan drawings. 5 Once all the SPUs have been discovered, select each SPU. 6 Click on the icon. The state of the node will be displayed in the State column. Some possible states are: AppUncnfg CnfgOnln NoAppUncfg CnfgHoffln CnfgSoffln CnfgBypassOffln Unknown Has application but is unconfigured Configured, with application and online Applicationless and unconfigured Configured, with application but hard offline Configured, with application but soft offline Configured, with application but bypass offline Not known by any defined means 7 Perform a packet count on all the fittings (select each fitting or use the button to select all of them). If the expected number of fittings were discovered and the packet counts are all satisfactory then the channel is ready to commission. If some fittings were not discovered or the packet counts were not all satisfactory then you must find the source of the faults and rectify them. 5.4 Preparation for Commissioning Before asking Stanilite (or its authorised agent) to commission the project, you must ensure that the following steps have been taken and all the required information is ready for entry into the Nexus database. You should have: Completed and checked the plan drawings, showing the as-installed location of every SPU, Router, Repeater, Channel cable route, Trunk cable route and Nexus Server. Fully completed and printed the database installation information list (see "Installation List" shown on page 47). Successfully installed, connected, tested and repaired all nodes and data cable. 46 Nexus LX

51 5.5 Installation List PROJECT: DATE: CHANNEL: ROUTER LOCATION ON TRUNK: REPEATER LOCATION ON CHANNEL: CH SEQ# LOCATION DESCRIPTION DRAWING SPU type DB (eg 2-1) Bldg Level Zone Plan# Grid# CB Nexus LX 47

52

53 C H A P T E R 6 6. Commissioning Guide In This Chapter Before you Begin Purpose of Commissioning Nexus Device Credits Commissioning the Nexus System Nexus Error Messages SPU LED Colour Meanings Before you Begin Before you commission a Nexus System, you must ensure that: You have the completed as-installed plans and project database list of the installation. The SPUs, Routers, Repeaters, Channels and Trunk are properly installed. The Channels and Trunk have been tested using the Network Utility Node. Any wiring errors have been found and fixed. The SPUs have been powered-up continuously for at least 24 hours. Do not begin the commissioning process until these conditions are met. It would also be advisable to revise the Nexus User Guide (shown on page 11). 6.2 Purpose of Commissioning The purpose of the commissioning process is to: 1 Register the network address of each SPU. 2 Record the physical location and other installation information for each SPU in the database. 3 Enable the system to carry out a discharge test of all the SPUs. 6.3 Nexus Device Credits The LNS Server that Nexus LX operates on uses a server licensing scheme based on device installation credits. From an initial pool of LNS device credits a credit is removed every time an SPU is installed and returned every time an SPU is removed. The Device Credit Information dialog box (Select Tools Credit Info) indicates the LNS device credit status for the LNS Server. For the LNS Server to be operational Days Remaining should be Unlimited and Deficit Credits should be 0. Nexus LX 49

54 Additionally, the status bar displays a summary of the current device credit status listing the number of remaining device credits and if this value is OK (>10), Low (<10) or in deficit (<0). If the number of SPUs commissioned uses up all of the Licensed Credits and causes the LNS Network to go into Deficit Credits, then more LNS device credits need to be added to the server. Note that once in deficit there is a 14-day grace period after which the LNS Server License will expire and the network will be inoperable. To add new device credits to the server contact Stanilite. 6.4 Commissioning the Nexus System Stanilite recommends that this stage of the commissioning process be performed by 2 people with walkie-talkies or mobile phones. It is important to make regular backups of the Nexus database during the commissioning process. Refer to Nexus Database (shown on page 29). The Nexus Program See The Nexus Program (shown on page 11) for information about the following topics: Starting Nexus Logging in to Nexus Changing the password Closing Nexus The Nexus window Step 1: Register the Installation Name For information about registering the name of the installation, see Changing the Installation Name (shown on page 12). Step 2: Commission the Routers For information about commissioning the routers, see Step 6: Commission the Routers (shown on page 45) and Commissioning the NUN (shown on page 25). Step 3: Enter the Router Location Details This step may already have been completed as part of the preparation for commissioning testing process. Once you have commissioned your routers you must enter the router location and reference information. This information consists of the following: You must enter reference information for all fittings whether they are routers or SPUs. This information forms part of the electronic logbook and is essential for system maintenance. The system cannot be handed over to the customer without this information being correctly entered. Building (e.g. Admin) Floor (e.g. Gnd) Position (e.g. West Corridor near lifts) Area (e.g. NW Corner, at Fire stair 1) 50 Nexus LX

55 DB (e.g. 2) CCT (e.g. CB 21) DWG (e.g. ABC123) Grid Ref (e.g. C4) For more information about entering these details, see Edit Location Details for Routers, Repeaters and SPUs (shown on page 28). Step 4: Commission the SPUs The next task is to commission the fittings. For information about doing this, see Commissioning SPUs (shown on page 27). Note: Commission SPUs in sequence in the order they are wired on the channel. Note that if for some reason a fitting cannot be reached to push its test button, the fitting can be commissioned via an alternative method to the one described in Commissioning SPUs (shown on page 27). Reserve a position for the fitting by clicking on the reserve button (see section Commissioning SPUs (shown on page 27)) and continue to commission as many fittings as possible using the regular method. To commission an inaccessible fitting, follow this procedure: Note: The LED(s) have to be clearly visible if you have more than one fitting to commission by the following method. 1 Return to the Network Utility software. 2 Place a tick next to the fittings on the channel being worked on. 3 Click on the icon. 4 Commissioned fittings will have CnfgOnln in the State column. Uncommissioned fittings will have AppUncnfg in the State column. 5 Position the person pressing the buttons where he or she can see the LED of the fitting in question. One at a time, place a tick in the checkbox of each uncommissioned fitting, then select the icon to wink by Neuron_ID until the LED flashes orange Note down the Neuron_ID. 6 Right click the row and select Reset Node. 7 Return to Nexus. 8 Recommission the reserved channel sequence number (see section Commissioning SPUs (shown on page 27)). Check the Use NID box and enter the Neuron_ID into the NID field then press Commission. 9 Confirm that the LED is now a static red. 10 Repeat this process for remaining inaccessible fittings. When all the channels are commissioned you are ready to perform the commissioning discharge test. Step 5: Carry Out the Initial Emergency Lighting Discharge Test It is more efficient, if possible, to discharge test the whole site at one time to minimize the disruption to both the site and the discharge testing. Nexus LX 51

56 For information about performing a Discharge Test, see Using Groups (shown on page 18). Step 6: Print Any Reports You may need to print the following reports during the course of commissioning: Work instruction. SPU Decommi/Reserved. SPU Status. These reports will help you to determine: Which fittings, if any, are defective or have failed their discharge test, and their location. The current status of commissioned fittings. You will need to print the following reports: SPU Details Router Location SPU Discharge Test Results Scheduled Group Discharge Test These reports form the site Emergency Lighting logbook and must be given to the authority responsible for construction. For more information about reports, see Reports (shown on page 23). Step 7: Save the Database For information about saving the database, see section Nexus Database (shown on page 29). 6.5 Nexus Error Messages Error Message Run time error number(number) : error description (error location: LNS, #number) There was an error starting Nexus LX and the program will exit. Error description. Form name There was an error starting the LNS Server for Nexus LX and the program will exit. An LNS Database exits on this hard disk with the same path as the one being created. Please contact Stanilite Product Support. Possible Causes/Action Error generated by LNS. If there is any mention of licensing all of the allocated device credits may have been used and the license has expired. Contact Stanilite support for additional device credits. For all other messages, copy the error message and contact Stanilite support. Various causes usually related to an LNS error. Copy the Error Description and Form name and contact Stanilite support. LNS database may be corrupted. Contact Stanilite support. If deleting LNS database it may not have entirely deleted using the delete database utility. Delete C:\lnsdb folder. 52 Nexus LX

57 Error Message The help File could not be opened. The file may be missing or corrupted. The commissioning of the device not complete. The commission operation for the current unit has been terminated. Please try again. There was an error communicating with the device. The commission operation has been terminated. This device is not recognised by Nexus LX or you are trying to install a device of a different type to the Installation Window currently open. Please try again. A new service pin event has been started. There was an error commissioning the Router/Repeater _ x The commissioning of the Repeater not complete. The commission operation for the current repeater has been terminated. Please press OK and try again. There was an error commissioning the Router due to a communications problem. Correct the problem and try again. Router-x There was an error communicating with the NUN. The commission operation has been terminated. There was a problem communicating with the Network Utility Node (NUN). The Nexus Server cannot send the Blink message unless the NUN is operating properly. Check the connections to the NUN and if necessary reinstall the NUN. There was an error creating the Group Network Variable NV_group_x. Please contact Stanilite support. Possible Causes/Action No help file present in the expected location. Search for Nexushlp.hlp file using Windows Explorer. If found place it in the c:\program files\nexuslx folder. If not present contact Stanilite support for the file. There was a problem when commissioning the device. Could be communications or LNS database related. Check communications using NUN. If unable to resolve contact Stanilite support. The communications test performed on the unit while commissioning failed. Check communication to the unit using the NUN. The program ID of the device is not recognised by Nexus LX. Unit may require loading of firmware. Contact Stanilite support. There was a problem commissioning the device. Could be communications or LNS database related. Check communications using the NUN. If unable to resolve contact Stanilite support There was a problem commissioning the device. Could be communications or LNS database related. Check communications using the NUN. If unable to resolve contact Stanilite support. The communications test performed on the unit while commissioning failed. Check communication to the unit using the NUN. The communications tests performed on the NUN while commissioning failed. Check the connections to the NUN. Unable to communicate with the NUN. Check the connections to the NUN. Unable to create the network variable used to send group test messages. If the group is empty click on the tools tab of the group dialog box and click repair group. Contact Stanilite support if unable to resolve. Nexus LX 53

58 Error Message There was an error assigning the new Group for SPU x. The device may not be communicating properly. The action was terminated. There was an error deleting and re-creating the Group Network Variable NV_group_x. Please contact Stanilite support. There was an error removing the Group Network Variable. Please contact Stanilite support. Firmware chosen is incompatible with this chip. There was an error loading the Delete Database Utility. A required file may be missing or corrupted. Re-start the application once it has shutdown. There was an error starting the Load Database Utility. A required file may be missing or corrupted. Re-start the application once it has shutdown. There was an error loading the Save Database Utility. A required file may be missing or corrupted. Re-start the application once it has shutdown. There was an error in trying to Print. Please check that there is a printer available in Control Panel. Possible Causes/Action Unable to bind the unit to the group network variable. Check communications to the unit using the NUN. If the group is empty click on the tools tab of the group dialog box and click repair group. Contact Stanilite support if unable to resolve. Unable to recreate a group network variable. If the group is empty click on the tools tab of the group dialog box and click repair group. Contact Stanilite support if unable to resolve. Unable to remove a group network variable. Contact Stanilite support. Firmware that is being loaded into the neuron of the unit is incompatible. Choose the correct firmware for the chip type. Contact Stanilite support if unable to resolve. Unable to locate the Delete Database executable. Search for Delete_Database.exe file using Windows Explorer. If found place it in the c:\program files\nexuslx folder. If not present contact Stanilite support for the file. Unable to locate the Load Database executable. Search for the Load_Database.exe file using Windows Explorer. If found place it in the c:\program files\nexuslx folder. If not present contact Stanilite support for the file. Unable to locate the Save Database executable. Search for the Save_Database.exe file using Windows Explorer. If found place it in the c:\program files\nexuslx folder. If not present contact Stanilite support for the file. Unable to print. Ensure the printer is installed and connected to the computer. 54 Nexus LX

59 6.6 SPU LED Colour Meanings Every Nexus SPU has a tricolour LED with the following possible states: SPU fitting is COMMISSIONED OFF GREEN steady SPU not powered or Battery not charging or If Spitfire, lamp not present or Still in last state when wink-mode stopped (press button or run short test or turn power off and on to reset). Neuron chip power-up self-test result faulty or Pushbutton has been pushed and held down RED steady Normal case: SPU commissioned, battery charging and, if Spitfire, lamp present. RED pulsing (Red/Off) Testing case: SPU under test. YELLOW steady SPU still in previous wink-mode state, (press button or run short test or turn power off and on to reset). YELLOW Pulsating consistently at a second rate (YELLOW/OFF) YELLOW/OFF Pulsating Intermittently at irregular rate: Under NEXUSLX wink-mode command or NUN wink-mode command. Under wink-mode command and some network messages are being lost. The possible causes of which are: The Data Cable is broken. The Data Cable has a short. The Data Cable is not terminated properly at one of the devices. If shielded cable used, the shielding is not terminated properly. The Channel cable is not terminated properly at one or both ends. The Channel cabling is incorrectly wired with a tee-off branch. The Channel cabling is too long for the cable characteristics. There are too many SPUs in the Channel. There is too much noise on the Channel Nexus LX 55

60 SPU fitting is UNCOMMISSIONED OFF GREEN steady SPU not powered or Battery not charging or If Spitfire, lamp not present or Still in last state when wink-mode stopped (press button or run short test or turn power off and on to reset). Neuron chip power-up self-test result faulty or Pushbutton has been pushed and held down GREEN/OFF pulsing PID is not nefw003b SPU uncommissioned (unconfigured) and otherwise normal. RED/YELLOW pulsing PID is nefw003b GREEN/OFF pulsing PID is nefw003b YELLOW/OFF and YELLOW/GREEN pulsing consistently SPU uncommissioned and with a fault: Battery not charging or If Spitfire, lamp not present Under NUN wink-mode command (Pulsing Green/Off is normal uncommissioned state and pulsing YELLOW/Off is wink-mode state, so both together will vary from YELLOW/Off to YELLOW/Green depending on the different rates of pulse and the times they overlap each other). YELLOW/OFF and YELLOW/GREEN pulsing Intermittently at irregular rate YELLOW varying in intensity Under NUN wink-mode command and some network messages are being lost. The possible causes of which are: The Data Cable is broken. The Data Cable has a short. The Data Cable is not terminated properly at one of the devices. If shielded cable used, the shielding is not terminated properly. The Channel cable is not terminated properly at one or both ends. The Channel cabling is incorrectly wired with a tee-off branch. The Channel cabling is too long for the cable characteristics. There are too many SPUs in the Channel. There is too much noise on the Channel SPU uncommissioned before wink-mode state. When wink is stopped, SPU uncommissioned the LED is locked on orange, with the uncommissioned pulsing GREEN in the background (press button or run short test or turn power off and on to reset). 56 Nexus LX

61 SPU Status - LED Pattern Table SPU Status UNCOMMISSIONED COMMISSIONED NORMAL GREEN/OFF pulsing RED steady (PID is not nefw003b) RED/YELLOW pulsing (PID is nefw003b) UNDER TEST N/A RED/OFF pulsing WINK MODE YELLOW/OFF and YELLOW/GREEN pulsing YELLOW/OFF pulsing FITTING FAULTY NEURON FAULTY GREEN/OFF pulsing (PID is nefw003b) GREEN Steady OFF POWER FAIL OFF OFF GREEN Steady Nexus LX 57

62

63 C H A P T E R 7 7. Sample Consultant Specifications In This Chapter Emergency Light Fittings Data Network Computer Hardware Computer Software Communications System Programming and Commissioning Emergency Light Fittings The Fittings shall be manufactured to comply with AS/NZS The Fittings shall be installed in compliance with AS/NZS 2293 and AS Each Fitting shall contain a microcontroller responsible for data communications and for the control and monitoring of the emergency functions of the Fitting. The microcontroller in each emergency light fitting shall monitor the operation of: Switched active mains supply (on/off) Battery charging (on/off) Emergency inverter or power supply output (on/off) Emergency lamp current (on/off) Emergency lamp light (on/off) Emergency test button (on/off) Normal lamp/light (on/off) (if appropriate). The microcontroller in each emergency light fitting shall be able to connect or disconnect the emergency unit from the mains supply in order to test the emergency operation of the unit in the event of power failure. It shall record the battery discharge time achieved during this test. Each fitting shall store the result of its last discharge test in non-volatile memory. The system shall not require factory pre-programming of fittings; the server on site shall issue each fitting with a Network address identification number during commissioning of the system. 7.2 Data Network The Data Network shall be installed in accordance with the AS/ACIF S009 cabling standard by a registered cabling provider where it is intended to connect the Nexus server to the Public Switched Telephone Network (PSTN) via a modem or other device. Nexus LX 59

64 7.3 Computer Hardware Pentium III processor based PC (or better) or compatible running Windows 2000 Professional or XP professional, with at least 256Mb RAM, 20GB 7200rpm HDD, CD-RW Drive, 1.4 Mb FDD, 15" (or better) SVGA Monitor, 56kbps Modem (or better), mouse and pad, one free internal PCI BUS slot, plus Inkjet/Bubble Jet printer (or better) and paper. The network functionality and testing facilities are dependent upon a PC being present. 7.4 Computer Software The software shall: Be fully compatible with Windows 2000 or later; Have a graphical user interface capable of representing the network topology and the state of the Fittings in real time on the screen; Allow additions and deletions of Fittings, or Fittings to be moved without interfering with the rest of the network and without the need to reprogram any other fittings; Allow the end user to create and delete test groups and allow any Fitting to be moved to a test group using standard Windows functions (Drag and Drop or Cut and Paste); Include a dynamic Maintenance Group that contains all faulty Fittings within the System; Contain a Maintenance logbook recording all discharge test results as well as system maintenance actions; Provide a facility for location information to be entered into a database detailing all relevant information for the Server, Routers and Fittings Incorporate a communications diagnostic test application for testing the data communications network. 7.5 Communications The communications system protocol shall be Echelon LonTalk. The network communications medium shall be a shielded single twisted pair data cable rated UL Level 4 with 22AWG stranded conductors. The network communication speed shall be at least 78 kbps. A complete status poll update shall take no longer than one (1) second per fitting and the Fittings shall in any case update their status on the Server as changes occur. The Network shall be divided into Channel Segments containing not more than 50 emergency light Fittings. Each Channel Segment shall be not more than 1000m in data cable length. The data cable in any Channel Segment shall not have any tee-offs. It shall be one continuous run of cable with Fittings connected along its length in a daisy-chain. Both ends of a Channel Segment shall be terminated with a Channel Terminator. The Channel Terminators shall be contained within the Fittings at the ends of the Segment. Channel segments may be connected end to end through a Repeater to form a Channel. 60 Nexus LX

65 Each Channel shall be connected to the system backbone (Trunk) through a Router. The Trunk may itself consist of channel segments. Routers shall connect along the length of the trunk in a daisy-chain. The data network shall be capable of incorporating fibre optic and Ethernet channel links in addition to the twisted pair data cable channels. 7.6 System Programming and Commissioning The installing electrician shall carry out commissioning of fittings onto the Network Communication System. Installation of the system shall be a four-stage process: Stage 1 Stage 2 Stage 3 Stage 4 Design, specification and tendering. Installation, wiring and data cabling testing Setup server and software, program fittings onto the network, creating database, practical completion. End user operation training. At the time of commissioning, all routers and repeaters are to be clearly labeled with the network address assigned by the server and all emergency fittings are to be clearly labeled with the Channel Sequence Number. All descriptive information required by the front-end software package is to be entered by the commissioning contractor and saved in the system database for the system server, routers and emergency luminaires. Detailed "As Installed" drawings must be provided upon completion of the system installation providing the following information: Location of the system server, routers and emergency luminaires. Data cable installation routes and exact graphical detail of the data cable installation between the routers and the server and the emergency luminaires and the routers. All routers and emergency luminaires must be labeled with the network address assigned by the system sever and must match the label attached to the router or emergency luminaire. Nexus LX 61

66

67 8. Glossary of Terms ADDRESS Each node in a Nexus system has an address. The address consists of a number of LONWorks elements: Domain, Subnet, Node, Group and Neuron_ID. In addition it has two Nexus specific elements: Channel Sequence Number and SPU_ID. AUSTRALIAN STANDARD / NEW ZEALAND STANDARD 2293 (AS/NZS 2293) The STANDARD that sets out the requirements for the design, installation and operation of emergency evacuation lighting systems for buildings. Divided into 3 parts: - Part 1, System design, installation and operation; - Part 2, Inspection and maintenance; - Part 3, Emergency luminaires and exit signs. AUSTRALIAN STANDARD 3000 (AS 3000) Electrical installations - Buildings, structures and premises (SAA Wiring Rules). The STANDARD that defines the method of installation for the wiring of medium to high voltage electrical installations. CHANNEL A collection of Channel Segments connected end to end by Repeaters. The channel is connected at one point by a Router to the trunk channel. In Nexus a channel corresponds to a LONWorks subnet because it is served entirely by one Router. The maximum number of nodes in a channel is determined by the LONWorks subnet limit of 127 nodes. This includes the router and repeater nodes on that channel. CHANNEL SEGMENT A section of data communication-cable used as the physical transport medium for Packets of data. Limited to no longer than 1000 m in length, terminated at each end with a Terminator. Stanilite recommends that no more than 50 SPUs be connected to each segment to avoid signal attenuation due to excessive loading. Channel segments can be connected by Repeaters to form Channels. CHANNEL SEQUENCE NUMBER The Channel Sequence Number is used to register each fitting as it is commissioned. It consists of two parts: the Channel is the channel to which the node is connected; the Sequence is the order of that fitting along the channel. For example, the first fitting on Channel 2 will have a Channel Sequence Number of 2-1, the next would be 2-2 and so on. Fittings can be inserted in a preexisting sequence if required. For example, 3 fittings could be inserted between the two mentioned: 2-2.1, 2-2.2, The purpose of the Channel Sequence Number is to intrinsically identify the relative data cable location of a node. DEVICE CREDIT A device credit is a royalty payment made by Stanilite to Echelon for each node commissioned using the LNS network operating system. Device credit royalties are not payable by the end user of a Nexus system, but they are allocated by Stanilite to Nexus installations and are automatically accounted for by the Nexus system. For instance, a site with say 1500 nodes will have at least 1500 device credits allocated to it. If nodes are added to the site, Stanilite will provide sufficient additional credits. DOMAIN The first level of LONWorks addressing. The domain identifier can be 0, 1, 3, or 6 bytes long. The default Nexus domain is C8(hex). A single node may be a member of up to 2 domains. ECHELON The name of the corporation that developed the LONWorks communications and control system, the LONTalk protocol and Neuron microcontrollers. Etherlon Router/Repeater Contains an Ethernet transceiver, a TPXF78 transceiver and a router module. Can be configured as a router or repeater from Ethernet to TPXF78. Manufactured by CTI Products Inc in the USA as a standard LONWorks product. FTR Router / Repeater Contains a fibre optic transceiver (FTR), a TPXF78 transceiver and a router module. Can be configured as a router or repeater from fibre to TPXF78. Manufactured by CBL Systems Corporation in the USA as a standard LONWorks product. Nexus LX 63

68 GROUP A LONTalk addressing construct. Each node in a Lonworks network can belong to up to 15 groups. There can be up to 256 different groups in a LONWorks domain. Groups are used to make a collection of nodes that can be addressed with a single message they are used in Nexus to group SPUs for emergency lighting discharge tests. Group addressing is independent of subnet/node addressing. kbps Kilobits per second. The term used to describe the speed of data transfer in digital form from one location to another. A standard Nexus node communicates at 78kbps. LNS LonWorks Network Services. LNS is a network operating system provided by Echelon that runs in a 32-bit Windows environment. It provides network management tools for use by top level user interface programs such as Nexus. LON Local Operating Network. The name used by ECHELON for their Neuron based distributed communications and control network. LONTalk The ANSI/EIA Control Networking Standard communications protocol created by ECHELON. This protocol is a set of rules that determines how data is transferred over a Local Operating Network. MAINTENANCE GROUP A collection of all the SPUs with either status or test faults. NEURON The name given to the microcontroller developed by ECHELON, manufactured by CYPRESS and TOSHIBA, that forms the basic component in every LON node. Neuron_ID A 48 bit identifier permanently and uniquely assigned to each Neuron microcontroller at the time of manufacture. Nexus Server The PC used to interface between the Nexus system and its user. This PC runs the Nexus program and is connected either internally or externally to a LONWorks interface device which provides the connection to the LONWorks network. The intelligent Network device that connects to the Network cable through a transceiver and functions as a source or destination of PACKETS of data. Every NODE contains a NEURON chip. This along with other software and firmware coded addresses, allows each NODE to be contacted over the Network, individually or in groups. It is also the third level of LONTalk addressing. There may be up to 127 nodes in a subnet. NUN The Network Utility Node is a device that is used in conjunction with the NUP to test the data communications of a Nexus network. It is a node that connects to the trunk and is usually located near the Nexus Server. NUP The Network Utility Program is used in conjunction with the NUN to test the data communications of a Nexus network. It is a program that runs on the Nexus Server and provides the ability to discover nodes and then manipulate them as well as packet count them. PACKET A defined quantity of data transmitted on the Network to LON specifications. Forms a complete message including source and destination addresses with command instructions and data. All Network data is in PACKETS. PACKET COUNT A measure of the quality of communications between two nodes. PCC10 A LONWorks interface device manufactured by Echelon. A Type II PC card that connects to the PCMCIA port of a notebook PC being used as a Nexus Server. It provides an external connection to the TPXF78 trunk. 64 Nexus LX

69 PCLTA20 A LONWorks interface device manufactured by Echelon. It connects to the PCI bus inside the Nexus Server and externally to the TPXF78 trunk. REPEATER Connects two segments of a Channel together to extend the length of a Channel or to increase the number of nodes connected to the Channel. Transfers all data Packets from one segment of a Channel to the other and boosts the signal strength in the process. Counts as 1 NODE on each segment of the Channel. of the standard Stanilite data cable. The function of the terminator is to absorb signal energy at the end of a data cable to prevent unwanted reflections which would otherwise distort the signal. TPXF78 Refers to the standard Stanilite data transceiver. It is a transformer isolated coupling filter designed to operate with differential Manchester encoded data running at 78 kbps. It connects to a level 4 twisted pair data cable with a characteristic impedance of 100 ohms. ROUTER The device that connects a branch Channel to the main Trunk. Selectively transfers data PACKETS from one Channel to the other (and boosts the signal strength in the process), when the Network destination address of the PACKET lies on the other side of the Router. By the LONWorks definition, a subnet must lie completely on one side of a router. In Nexus every node on the far side of a router (ie the side away from the trunk) is in the same subnet and is in the same channel. SPU Single Point Unit. The term for an emergency light fitting (unit) that stands alone (at a single point) and includes its own rechargeable battery and battery charger. When normal mains power to it fails, it automatically energises its emergency lamp until the power is restored or the battery discharges. SPU ID This is a purely sequential number applied to an SPU as it is commissioned. SPUs on a site are numbered from 1 onwards. SUBNET The second level of LONTalk addressing. There may be up to 255 subnets in a domain. The subnet corresponds to the Nexus channel although the number of Nexus channels is limited by the single level of routers imposed by Nexus. TERMINATOR A small device that must be attached to both ends of a Channel Segment. It consists of a passive network of components that forms a complex impedance equal to the characteristic impedance Nexus LX 65