Table of Contents

Advertisement

neat
D-SERVER - Technical Handbook
NE41 09010-02 v3.0

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the D-SERVER and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Neat D-SERVER

  • Page 1 D-SERVER - Technical Handbook NE41 09010-02 v3.0...
  • Page 2 © Copyright 2017 NEAT Electronics All rights reserved. Document number: NE41 09010-02 v3.0 Revision date: 2017-09-06 Contact NEAT Electronics AB Varuvägen 2 SE246 42 Löddeköpinge Sweden Phone: +46 46 70 70 65 Fax: +46 46 70 70 87 www.neat-group.com/se/en infosweden@neat-group.com...
  • Page 3: Table Of Contents

    D-TECT connectors 2.2.3 Set address for a D-TECT unit 2.2.4 Mount the D-TECT units 2.2.5 Power requirements Connecting D-TECT units to the D-SERVER 2.3.1 Connecting D-TECT units to a bus 2.3.2 Connect serial buses to the D-SERVER D-BOX 2.4.1 D-BOX kit 2.4.2...
  • Page 4 Accessing the D-SERVER Access the D-SERVER from a network 4.1.1 Connecting a D-SERVER to a existing LAN 4.1.2 Connecting a D-SERVER using a router 4.1.3 Direct connection between a PC and a D-SERVER 4.1.4 Web interfaces 4.1.5 Licences 4.1.6 Upload License Samba 4.2.1...
  • Page 5 Appendix A.2 Standard parts lists and spare parts Appendix B Connector tech specs Appendix B.1 Pin configuration for the serial bus from the D-SERVER Appendix B.2 Pin configuration for the serial bus to D-TECT units Appendix C D-SERVER Alarm types...
  • Page 6 Document revision history Date Version Revision details 2017-09-06 Release of v3.0 D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 7: Introduction

    This technical handbook describes how to install, configure and maintain a D-SERVER system. D-SERVER system In the D-SERVER system, a central server handles all alarms. The server collects triggered alarms, decides on the appropriate action and distributes the alarms to relevant receivers.
  • Page 8: System Components

    2.1.1 D-SERVER kit The D-SERVER can be equipped with either 2 or 4 LAN ports (the 4 LAN-port version is used throughout this documentation) and only the LAN port 1 is used (see "2.1.2 Connectors on the D-SERVER" on page 9).
  • Page 9: Connectors On The D-Server

    Cable ordered separately Reset button Not used Table 3. D-SERVER connector denominations The D-SERVER can be supplied with additional LAN ports (ports 3 and 4), but only WAN and LAN port 1 are used! D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 10: D-Server Leds

    Connect the central power supply Considerations If you want to connect a PC to the D-SERVER through a router (dynamic IP-address/ DHCP), connect the WAN port on D-SERVER to the router before connecting the power supply for the D-SERVER. Otherwise the D-SERVER might not be accessible properly.
  • Page 11: Mounting The D-Server

    • Never mount the D-SERVER standing on a short side, this blocks the ventilation intake. Mount the D-SERVER with wall brackets 5. Fit the wall brackets on the back on the D-SERVER and secure them with the sup- plied screws. 6. Mount two screws on the wall.
  • Page 12: D-Tect

    D-TECT D-TECT is a radio device for the reception and distribution of alarms and events. While the D-SERVER is the central processing unit the D-TECT is a tranceiver designed to receive incoming and distribute outgoing alarms and events. The information between the D-SERVER and the D-BOX is sent through a RS-485 cable(s) while the information between the D-BOX and D-TECT is sent through a network cable.
  • Page 13: Set Address For A D-Tect Unit

    If the address for a unit is changed while powered on the unit must be powered off and powered on again for the new address to take effect. Note that configuring a D-TECT unit requires a NEAT Programming Unit (NPU) and the software D-TECT Programmer! Picture 8.
  • Page 14: Power Requirements

    The AC adaptor must supply voltage: 12V and current: 1,5A. The nominal power comsumption is 3W. Connecting D-TECT units to the D-SERVER 2.3.1 Connecting D-TECT units to a bus 1. Connect the first D-TECT unit to the bus. Connect a network cable between the D-Box and the BUS connector on the D-TECT unit.
  • Page 15: Connect Serial Buses To The D-Server

    2.3.2 Connect serial buses to the D-SERVER Connect DB9-cables between the RS-485 connectors on the D-SERVER and D-Box. COM1 LAN4 LAN2 WiFi COM2 LAN3 LAN1 Picture 12. Connecting D-SERVER to a D-Box bus using DB9 cables D-BOX D-BOX is a unit that provides a central power supply to a chain of D-TECTs in a D- SERVER system.
  • Page 16 1 bus 2 D-BOX CONNECTION BOX FOR D-SERVER SERIAL BUS PORT 1 PORT 2 Picture 15. D-BOX connectors Denomination Bus 1 Bus 2 DC IN Port 1 Port 2 Picture 16. D-BOX connector denominations NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 17: D-Tect Ip

    The LED on the D-TECT IP indicates the connection status. LED indication Meaning The D-TECT is powered on and has a valid TCP Fixed connection with the D-SERVER. The D-TECT is powered on but has no valid TCP Blinking connection with the D-SERVER. Table 9. D-TECT IP LED indications D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 18: D-Tect Ip Connectors

    D-TECT IP can be power supplied either by a AC adaptor or by PoE (Power over Ether- net) class 2, mode A & B. The AC adaptor must supply voltage: 7.5V and current: 0.45A. Max power consump- tion is 3.3W. For recommended AC adaptors, see "Appendix G Recommended NEAT AC adaptors". 2.5.4 Mounting D-TECT IP units D-TECT IP units must be installed in locations with good radio reception, for example high up on corridor walls.
  • Page 19: D-Trex2G

    D-CALL IP D-CALL is an IP connected care phone enabling voice communication in a D-SERVER system and has all the functionality of a regular care phone i.e. it can function as a hub for radio equipment in the user’s vicinity, e.g. a DOOR alarm, PIR for movement detection etc.
  • Page 20: D-Call Ip/Gsm Kit

    D-CALL IP/GSM connectors Picture 22. D-CALL connectors Denomination Aux (Not used) IP (Ethernet, RJ45) Accumulator cover (SIM holder inside) Power switch AC (RJ11, 4/4) Line (Only used for debugging) Table 13. D-CALL IP connector denominations NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 21: Mounting D-Call Ip/Gsm Units

    6. Put the D-CALL IP/GSM on a table or side board. Or hang it on a wall by using the key hole slots on the back. Normal installations usually run the D-CALL over IP (no GSM) or over GSM (no IP). D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 22: Ip-Dect Components

    The IP-DECT Server 400 is a necessary component in a speech system since it works like a bridge between the DECT handsets and the D-SERVER SIP server thus enabling voice communication between D-CALLs and DECT handsets or SIP messages between the D-SERVER and DECT handsets in the D-SERVER system.
  • Page 23: 2.9.2 Power Requirements

    Spectralink DECT Repeater To further add coverage the IP-DECT Server 400 and each IP-DECT Base station can connect to three DECT repeaters each. More infomation is found here: http://www.spectralink.com/products/dect/infra- structure/spectralink-dect-repeater Picture 26. DECT Repeater D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 24 Table 17. Single cell star pattern setup parts Single cell chain setup Picture 28. D-DECT Server 400 in a single cell chain pattern setup No Denomination IP-DECT Server 400 DECT Repeater Table 18. Single cell chain pattern sedtup parts NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 25 12 repeaters (since it is also possible to connect repeaters directly to the IP-DECT Server 400). Picture 29. Multi cell configuration No Denomination IP-DECT Server 400 IP-DECT Base station DECT Repeater Table 19. Multi cell pattern setup parts D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 26: Extra Licenses

    2.10 DECT handsets The D-SERVER system supports the Spectralink 7722 DECT handset. 2.11 The NPU is a programming unit for configuration of several NEAT units, e.g. SMILE, ATOM, D-ATOM, D-TECT and D-CALL units. NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 27: 2.11.1 Npu Kit

    AC (RJ11 female) connector Table 21. NPU connector denominations Note that there is also a cable with a mounted RJ11 male socket on the NPU and this is used for configuring D-CALL, D-TECT etc.. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 28: 2.11.3 Npu Mounting

    1. Ensure the Windows drivers are installed on the local computer. 2. Connect the AC adapter to the AC connector. 3. Connect the USB cable to a USB port on the computer. 4. The NPU is now ready to be used for configuring units. NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 29: System Setup

    This scenario will cover how-to configure a D-Server with D-TREX 2G alarm receivers. A D-BOX together with two D-TECT’s will be used as transceivers. The D-TECT’s will communicate with the D-Server over a RS-485 bus. The end user will be equipped with a SMILE-STD button.
  • Page 30: Scenario

    D-TECTs with two D-TECT IPs. D-TECT IP is IP-based and one of several benefits is that you are not limited to a RS-485 bus to communicate with the D-SERVER. In prac- tice this means that a D-SERVER and D-TECT IPs can be located in completely different locations as long as the devices are connected by a stable internet connection.
  • Page 31: Hardware Requirements

    The demand of a cheap speech solution will be covered in this example. The example will introduce you to the built-in SIP server in the D-SERVER as well as the IP-DECT and DECT handsets. The end user will have an IP-based care phone (D-CALL) in their room.
  • Page 32: Hardware Requirements

    Another speech solution will be covered in this example. The nurses are equipped with cell phones and the end users with a D-CALL in their room. If a nurse is busy in a call the D-SERVER will try another number. The communication between the staff and end user is done over GSM.
  • Page 33 Scenario V is a repetition of Scenario IV but in this scenario we mix D-TECTs and D-TECT IPs and equip the end users with a SMILE-STD. The system has also grown in terms of devices. • It's possible to mix D-TECT and D-TECT IP in a D-SERVER installation. Hardware requirements System component...
  • Page 34: Accessing The D-Server

    Accessing the D-SERVER Access the D-SERVER from a network Accessing the D-SERVER out of the box is possible in two ways. If you choose to con- nect the D-SERVER directly to a network, you must use the WAN port. The reason you must use the WAN port is because the port is pre-configured to receive an IP-address from a DHCP server.
  • Page 35: Connecting A D-Server Using A Router

    Connecting a D-SERVER using a router 1. Connect a network cable between the PC and any of the LAN ports in the router. 2. Connect a network cable between the D-SERVER (port WAN) and any of the LAN ports the router.
  • Page 36: Direct Connection Between A Pc And A D-Server

    4.1.3 Direct connection between a PC and a D-SERVER The second way to access the D-SERVER out of the box is through a direct network connection. The D-SERVER supports auto-negotiation (MDI/MDIX) so there is no need to think about using a cross cable or straight cable.
  • Page 37: Web Interfaces

    4.1.4 Web interfaces The D-SERVER has two web interfaces and depending on selected port, you will either access the nurse or administrator web interface. Interface Port Nurse web interface Administrator web interface 48465 Table 28. Nurse and web administrator interface ports Picture 48.
  • Page 38: Licences

    SD card. If you need to upgrade your license, you will need to attach your license file in an email and send it to your local NEAT office. See "4.2.2 Backup License" for more in- formation how to save your license.
  • Page 39: Samba

    Samba D-SERVER supports Samba. To access the D-SERVER through Samba click the Windows Start button and type: \\<dserver-ipaddress> where <dserver-ipaddress> is the assigned IP address to the D-SERVER. Press Enter. In the examples below our D-SERVER has IP address 10.40.10.180.
  • Page 40 Configuration", "4.2.2 Backup License" and "4.2.3 Backup Log files" for more infor- mation. Picture 53. Available D-SERVER folders through Samba Stored Samba credentials in the Windows vault Make sure that the sysadm account credentials is not stored in Windows Vault if you have difficulties accessing the admin or www folder.
  • Page 41: Backup Configuration

    Backup Configuration Once you have logged in successfully through Samba, you can browse the config folder and view the current D-SERVER’s configuration files. To backup the current configuration simply copy all the files to safe location. Picture 55. D-SERVER configuration files SIP server configuration is not included in the config folder.
  • Page 42: Backup License

    Backup License Once you have logged in successfully through Samba you can browse the license folder. The license folder contains the D-SERVER license. To make a copy of your license copy the license to a safe location. Picture 56. D-SERVER license file 4.2.3...
  • Page 43: Backup Network Configuration

    Network Configuration. The interfaces file contains the network configuration. To backup your network configuration copy the file to a safe location. Picture 58. D-SERVER network (interface) settings file This action requires logging in with the service account. 4.2.5 Backup SIP server configuration Browse to the opensips folder which can be found in the admin folder to backup the SIP server Configuration.
  • Page 44: The User Interface

    To export the positions found in "Find User", the XML logs must be downloaded via Samba. Logs can be found in \log\user-positions. Once the D-SERVER configuration is finished, this menu is used mostly by the personnel. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 45: Alarm Configuration

    When entering the Alarm Configuration menu a Configuration guide is diplayed. This guide is intended to give an overview and the steps are very schematic and are only meant to give an orientation to the reader. Picture 61. D-SERVER Configuration guide NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 46 Planning the configuration Planning an installation in advance is an important step before configuring the D-SERVER. It is recommended to review the checklist below and prepare the answers in advance. Not all parameters are mandatory, but being prepared makes configura- tion easier.
  • Page 47 Not applicable or will not be used. Cobs destinations Only valid for COBS 3110 and SMART1 systems. ESPA destinations Not applicable or will not be used. SIP destinations Not applicable or will not be used. NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 48: Identifications

    Alarm distribution ule. You also need to setup a distribution for Assistance alarms if this feature should be used. Table 33. D-SERVER configuration check list 5.2.1 Identifications Users Add a name or room number (e.g. "Ellen Swahn" or "Apartment 1") Alarm points Add a public place (e.g.
  • Page 49: Entities

    Define the schedule (e.g. Monday: Day start at 07:00 and Night Time schedule starts 21:00) Naming the different tasks. Feature can be enabled from System parameter (feature-task-registration-enabled). Task registration NOTE! This feature requires COBS C3110 or SMART1 handsets. Table 35. Entitites sub menu items NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 50 Picture 66. Configurable device parameters The link is a clickable link and means that Clik here to read or write configuration! it is possible to read from/write to these units directly from the D-SERVER without needing an NPU. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 51: Destinations

    Distribution of alarms according to configured sequence (e.g. alarms Alarm distribution from group "Apartment 1-5" [daytime] should be sent to sequence "Personnel Day") Table 37. Routing sub menu items It's important that the administrator backups the D-SERVER configuration regularly. NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 52: Door Opening

    Door opening feature is often used together with a D-POS, D-POS ANT, WIOR and (Ferrite Antenna). System settings System settings contains misc. system settings and displays a list of various System parameters. See "5.4.1 System parameters". Picture 68. System settings menu D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 53: System Parameters

    Parameter control how the D-SERVER communi- cates on the serial bus. bus-send-retries Determines the number of times that the D-SERVER tries to send a message to a D-TECT unit if it does not reply. Parameter control how the D-SERVER communi- cates on the serial bus.
  • Page 54 If the debug logging for the serial bus is enabled (debug-serial-bus changed to other value debug-serial-bus than zero (o)), the memory card in the D-SERVER can fill up very quickly. After that, all logging will stop working. D-SERVER Technical Handbook...
  • Page 55 System parameter Description Default value Logging of signals received by the D-SERVER ap- debug-signals plication (reloading the D-SERVER settings and stopping the D-SERVER application). Logging of the SIP communication. debug-sip-task Introduced in Application v1.19.00 debug-xml-tables Logging of configuration tables.
  • Page 56 Determines for how long time the D-SERVER sends logout messages to all alarm receivers when the log-out-all-timeout-sec D-SERVER is reloaded or restarted. If not all alarm receivers are logged out when the D-SERVER is restarted, the value of this parameter may need to be increased.
  • Page 57 If no D-TREX unit has received the alarm, the D-SERVER continues imme- diately to the next step of the alarm sequence. Oth- erwise the D-SERVER waits until the duration of the paging-send-count-no-answer current step in the alarm sequence has expired.
  • Page 58 Within this time, the message for radio-tx-timeout-sec radio transmission must be successfully sent to the D-TECT, the D-TECT must transmit the radio message and report back to the D-SERVER that radio transmission is completed. Parameter control the timing of radio transmis- sions.
  • Page 59 Determines how often a status change message status-message-send-interval- (receiver “Busy” or receiver “Idle”) is re-transmit- ted by the D-SERVER if there is no reply from the alarm receiver. This applies only when an alarm receiver has been too long in “Busy” mode.
  • Page 60: Surveillance

    To receive these messages, an Alarm distribution has to be made. Define if the D-SERVER application should send out a radio message D-SERVER surveillance at a certain interval. Can be used to monitor that the D-SERVER is running. Table 40. Surveillance menu items 5.4.4 Transceivers Define which devices in the system that should act as transceivers.
  • Page 61: Sip

    If a SIP client receives an incoming call, you can configure that it should call a group of SIP clients. SIP groups Called number only have to be registered in the SIP server. Define SIP accounts used by the D-SERVER application. Used in SIP SIP accounts destinations. Table 43. SIP menu items 5.4.8...
  • Page 62: Administration

    The component "Application" can be upgraded from the menu item Upload new application. Upgrading to a newer version is possible as long as it stays in the same D-SERVER release, which means that Application v1.21.01 can be installed on a D-SERVER with v1.21.xx installed.
  • Page 63: Scenario Configuration

    : Q Do you have the radio codes of all that devices that will be used at the nursing home? Do you know who the units should belong to? 9 SMILE-STD (Radio ID: 101E) belongs to Matthew Parker. NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 64 9 Day shift starts 07:00 AM 9 Night shift starts 09:00 PM Scenario I requires D-SERVER, D-TECT and D-TREX 2G configuration. Let's start with the D-TECT configuration, thereafter the D-SERVER and finally D-TREX 2G. D-TECT configuration Read both D-TECTs configuration and change...
  • Page 65 Picture 72. Create user(s) 3. SMILE-STD (101E) is an unknown radio code for the D-SERVER. To associate 101E to Matthew Parker, go to > . When the SMILE-STD is associated to Entities Devices Matthew Parker, it's no longer an unknown radio code.
  • Page 66 7. Since we will use shifts, we need to define the Time schedule. From our checklist, we know that the Day shift starts 07:00 AM and the Night shift starts 09:00 PM. Go to > Entities Time schedule D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 67 9. In order for D-TREX 2G to receive alarms, we must configure routing. The first step is to create sequences. Create a sequence for Personnel Day and Personnel Night. Go to > Routing Alarm sequence names Picture 79. Define alarm sequence name(s) NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 68 Note that Alarm reset is configured to Yes. If someone accepts an Alarm or Assistance alarm, it will disappear from other D-TREX 2G devices. If you are configuring a fire alarm, you probably want to configure Alarm Reset to No for that specific distribution. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 69 12. The last step in the D-SERVER configuration is to change System ID to something else. This step is optional but recommended if you have several D-SERVERs run- ning in your environment. Go to System settings > System parameters and change the parameter system-id to 4000.
  • Page 70 D-TREX 2G configuration Since the System ID in the D-Server changed the System ID in D-TREX 2G must also be changed. Start by reading the D-TREX 2Gs, change System ID and finally write configuration to both D-TREX 2Gs. Picture 84. Change the System ID setting in D-TREX2G Testing Scenario I - Text solution (D-TECT) It's now time to test the scenario configuration.
  • Page 71 Daytime. Confirm the alarm. Picture 88. D-TREX2G displaying a new alarm Press the alarm button again and wait 240 seconds. If our sequences are working correctly, Emma Lopez should get an alarm message. NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 72 Emma Lopez to all other units in the system. Picture 89. Press and hold the red alarm button to send an Assistance alarm Picture 90. Assistance alarm sent confirmation in D-TREX2G Picture 91. Assistance alarm received message on D-TREX2G D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 73 To support this feature the SMILE-STD must be replaced with a SMILE-ID. This feature only works with D-ATOM and SMILE-ID as they have RFID functionality. The existing D-SERVER configuration is used but with some minor modifications. 1. Replace SMILE-STD (101E) with a SMILE-ID. The SMILE-ID in this example has radio code 28AD.
  • Page 74 Return Picture 97. Ready indication in D-TREX2G If you have trouble getting the solution to work, please check that the RFID is enabled on the SMILE-ID. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 75 Press the SMILE-ID button. Confirm the alarm by pressing the button (alarm Return disappears from the display). Wait for the three reminders to pop up in the D-TREX 2G display. Finish with a Presence/Ready. NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 76: Scenario Ii - Text Solution (D-Tect Ip)

    9 We need two personnel groups because the nurses will work in shift. - Personnel Day - Personnel Night 9 Since we only have one SMILE-STD in this scenario, one device group is enough. - Misc alarm sources D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 77 9 Day shift starts 07:00 AM 9 Night shift starts 09:00 PM Before connecting the D-TECT IP units, a D-SERVER System ID must to be set. The default System ID is set to 1, but in this scenario the System ID 4321 is used.
  • Page 78 Once you have connected a device you need to review Network and Server Settings. The D-TECT Server IP address must to be changed so it matches the D-SERVER IP ad- dress. The same goes for Server ID (System ID).
  • Page 79 To get this scenario working we also need to configure the D-SERVER and our D-TREX 2G units. Let's begin with the D-SERVER configuration. D-SERVER configuration Here's a brief overview of the D-SERVER configuration. Please note that the configu- ration is identical to Scenario 1 but the System ID have changed.
  • Page 80 Picture 106. Define the device group name(s) Picture 107. Define the device group definition(s) Picture 108. Create a time schedule D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 81 Picture 109. Add D-TREX2G destinations Picture 110. Define alarm sequence name(s) Picture 111. Define alarm sequence definition(s) Picture 112. Define the alarm distribution NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 82 Picture 113. Set the D-SERVER system ID D-TREX 2G configuration To be able to log on to the D-SERVER system with D-TREX 2G units, System ID 4321 must be set in the D-TREX 2G Programmer. Write the edited configuration to the D-TREX 2G units. Test the solution afterwards.
  • Page 83: Scenario Iii - Speech Solution (Dect)

    Messaging, but this scenario will circumvent this by calling all handsets and stop ringing when someone from the personnel answers the call/alarm. Picture 115. Scenario III overview Scenario III requires a D-SERVER SIP license. Again, review the checklist. Checklist...
  • Page 84 There's no need to configure Log-in allowed for group Apartment 1. If we had more users, we would create additional device groups for Apartment 2, Apartment 3 etc.. Picture 117. Define device group name(s) D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 85 The D-SERVER will not recognize Charlotte Miller and Emma Lopez so the next step in the configuration process is to add the personnel. Go to > Identifications Personnel and add Charlotte Miller and Emma Lopez. Picture 118. Add personnel D-CALL (ID: 0472) is an unknown radio code for the D-SERVER.
  • Page 86 Apartment 1. If the scenario had contained more apartments, a destination must be created for each Apartment. Picture 122. Add D-CALL destinations As we want the D-SERVER to send a SIP message (alarm) to our DECT phones we need to create a D-SERVER SIP account. Go to >...
  • Page 87 Next step is to create a sequence. If there would be more users the sequences could be called Apartment 2, Apartment 3 etc.. Go to > to create a sequence. Routing Alarm sequence names Picture 126. Define alarm sequence name(s) NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 88 System ID to 2222. Go to > to configure System ID. System settings System parameters Picture 129. Set the D-SERVER system ID Don’t forget to Reload the configuration once you are finished with the D-SERVER configuration. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 89 There are two important tabs when configuring the IP-DECT. The first one is found under > Configuration Make sure "Default domain" and "Proxy 1" reflects the D-SERVER IP address. Picture 130. Set the default domain IP and proxy address in the IP-DECTs NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 90 D-CALL configuration The D-CALL Programmer has several tabs, but only two are relevant to this scenario. Ensure Radio pos. 1 reflects the D-SERVER System ID and that the rest of the con- figuration in your D-CALL is similar. D-SERVER Technical Handbook...
  • Page 91 Picture 133. Set the D-SERVER system ID in D-CALL On the IP-tab make sure that network is enabled and that SIP configuration reflects the configuration in the D-SERVER. Even if NEAT Web Service should be disabled, make sure that the NEAT Web Service server address reflects your D-SERVER IP-address.
  • Page 92: Scenario Iv - Speech Solution (Gsm)

    The goal of this scenario is to configure a speech solution using GSM where the personnel uses a mobile phone as a handset. The scenario assumes that you have a D-SERVER with pre-configured D-TECT IPs. Picture 135. Scenario IV overview...
  • Page 93 Picture 137. Add device(s) Go to > and create a group for every apartment. In this Entities Device group names scenario there is only one apartment (Apartment 1). Picture 138. Create device group name(s) NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 94 Picture 141. Create alarm sequence name(s) Go to > to define the sequence. When Apartment Routing Alarm sequence definitions 1 requires assistance, the D-CALL will start with calling nr#1. If no one answers, the D-CALL will try with nr#2. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 95 Picture 144. Define alarm sequence definition(s) In this scenario the System ID is set to 1386. To configure System ID go to System > settings System parameters Picture 145. Set the D-SERVER system ID D-CALL configuration NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 96 The D-CALL Programmer has several tabs, but only three are relevant to this scenario. Make sure Radio pos. 1 reflects the D-SERVER System ID and that the rest of the con- figuration in your D-CALL is similar. Picture 146. Set the D-SERVER system ID in D-CALL On Call parameters tab, make sure that GSM is enabled.
  • Page 97 On the IP tab make sure that network is disabled. Even if NEAT Web Service should be disabled, make sure that the address reflects your D-SERVER IP address. Server Picture 148. Disable Network but ensure NEAT web service server and port is set correctly Don't forget to write the D-CALL configuration to the unit.
  • Page 98: Scenario V - Speech Solution (Gsm) With D-Tect/D-Tect Ip

    9 D-CALL (Radio ID: 6039) belongs to Apartment 2 9 D-CALL (Radio ID: 6269) belongs to Apartment 3 9 SMILE-STD (Radio ID: 101E) belongs to Apartment 1 9 SMILE-STD (Radio ID: 28AF) belongs to Apartment 2 D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 99 : Q Will you use day and night shifts? Then you need to know when the day and night shifts starts. 9 No need. D-SERVER configuration Before connecting the D-TECT IP devices to D-SERVER, a System ID must be config- ured. In this scenario System ID 1652 is chosen. Go to > System settings System to set the System ID.
  • Page 100 > to verify that the D-TECT IPs are successfully Status Connected devices connected to the D-SERVER. Picture 151. Check that the D-TECT IPs are listed in Connected devices Go to > to add the users who will stay at the nursing home.
  • Page 101 Picture 156. Add D-CALL destinations Go to > to create a sequence, one sequence for each Routing Alarm sequence names apartment. Picture 157. Create alarm sequence names NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 102 To enable our sequences we need to configure Alarm distribution. Go to > Routing Alarm distribution Picture 159. Add alarm distribution D-CALL configuration The D-CALL configuration procedure is the same for all three D-CALLs. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 103 The D-CALL Programmer has several tabs, but only three are relevant to this scenario. Make sure Radio pos. 1 reflects the D-SERVER System ID and that the rest of the con- figuration in your D-CALL is similar. Picture 160. Set the D-SERVER system ID in D-CALL tab, make sure that GSM is enabled.
  • Page 104 On the IP tab make sure that network is disabled. Even if NEAT Web Service should be disabled, make sure that the Server address reflects your D-SERVER IP. Picture 162. Disable Network but ensure NEAT web service server and port is set correctly Don't forget to write the D-CALL configuration.
  • Page 105: Troubleshooting

    Troubleshooting Is the power D-SERVER powered on and running? Check the LEDs: • PWR (red) - should be on, fixed light • APP (green) - should be on, fixed light • Network link LED (on connected network interface) Amber - should be blinking,...
  • Page 106: Ssh Clients

    System logs Picture 165. Various logs in D-SERVER NEAT support will likely ask you to attach your logs if the technical issue is complex. SSH clients Among all SSH clients, Bitvise and Putty are the most popular. Bitvise has a graphical interface and is therefore quite popular among people with limited Linux knowledge.
  • Page 107: Bitvise Configuration

    Picture 167. Putty SSH client window The advantage of an SSH client compared to traditional D-SERVER debug logs is that you can perform real time debugging. Accessing to the D-server through SSH also allows users to access kern.log and syslog. These two files are useful for identifying memory card related issues.
  • Page 108 . Browse to the path of your SSH Key and select Import Import Picture 169. Import an SSH key to Bitvise The last step is to configure login settings. Fill in host (D-SERVER IP), port 48464 and username and when done, click the button to connect.
  • Page 109: Bitvise Sftp

    Bitvise SFTP When connecting to a D-SERVER an SFTP and an xterm window opens. This section focuses on the SFTP window and how to download logs and configuration. Picture 171. Bitvise SFTP windows Changing path is required to view or download kern.log and syslog. Type the path /var/log in the address bar and press to enter that path.
  • Page 110 Right click kern.log and select to open the file in your favorite editor. Edit with... Picture 174. Select preferred text editor. Here Notepad++ is chosen NEAT recommends Notepad++ as text editor. Notepad++ can be downloaded from https://notepad-plus-plus.org/. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 111 In addition to the path /var/log, the following paths may be of interest to explore. /var/log/dserver/debug Debug logs /var/log/dserver/errors Error logs /usr/local/etc/dserver D-SERVER configuration /usr/local/etc/license D-SERVER license /etc/network Network configuration Table 48. Various log paths NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 112: Bitvise Xterm

    Bitvise xterm This section is a walkthrough how to perform real time debugging with xterm. To be able to perform real time debugging parameter debug logging in the D-SERVER System parameters (System settings > System parameters) must be enabled.
  • Page 113 File System: Disable read-only mode lsusb List connected USB devices iconv --l List known coded character sets ntpq -nc peers NTP: Servers currently used cat /sys/block/mmcblk0/device/name Memory card manufacturer installed Table 49. Other useful commands in Bitvise xterm NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 114: Console Cable

    Console cable In addition to IP debug, the D-SERVER supports debugging over a serial connection. Debugging over a serial connection requires a special debug cable that is sold separately. Contact your local NEAT sales representative for more information about the debug cable.
  • Page 115: Appendix A Technical Reference

    24 V Appendix A.2 Standard parts lists and spare parts The complete parts lists for the D-SERVER system include articles for other language versions and other frequencies. The complete lists can be can obtained from your local supplier.
  • Page 116: Appendix B Connector Tech Specs

    Appendix B Connector tech specs Appendix B.1 Pin configuration for the serial bus from the D-SERVER Picture 183 shows the pin configuration for the DB9 serial port connector on the D-SERVER. Picture 183. DB9 serial port pin configuration Pin configuration is when viewed from the front/outside.
  • Page 117: Appendix C D-Server Alarm Types

    Mains failure Mains return Battery low Smoke alarm Assault alarm Presence Ready Auto ready Action Emergency alarm Assistance alarm Radio test alarm Position info Connection alarm Connection ok Table 54. Default alarm types in D-SERVER NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 118: Appendix D Neat Standard Alarm Types

    Appendix D NEAT Standard Alarm types Number Description Number Description Meaning Reset alarm No alarm type Service call User alarm from trigger Daily report / Event User alarm from button Double press Reminder alarm Long press Passive alarm Technical failure...
  • Page 119 CMP report alarm NTP update FTP download Roaming IP network failure IP network return User call 3 User call 4 User call 5 User call 6 Seat exit alarm Pairing Table 55. NEAT Standard alarm types NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 120: Appendix E Message Format Specifiers

    : The format specifier %gt% can only be used for alarms from D-TREX2G units Note 3 (assistance alarms). : The format specifiers %st% and %ex% can only be used for alarms to COBS Note 4 units. D-SERVER Technical Handbook NE41 09010-02 v3.0...
  • Page 121 • Received alarm reason: Trigger alarm The above configuration would then have the format string: “%rt% from %nt% (%eqt%) in %lt%” This would result in the display message: “Trigger alarm from Hans (Atom) in room 102” NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 122: Appendix F Equipment List

    Appendix F Equipment list By default this equipment is loaded in the D-SERVER: Equipment 3PUSH 3PUSH+PEAR ATOM COBS C-3110 COBS CMS COBS TALK D-ATOM D-CALL D-TECT D-TECT-IP D-TREX D-TREX2G DOOR ESPA FALL FLOOD INKA PEAR PULL PULL1G PUSH PUSH+PEAR...
  • Page 123 This page intentionally left blank NE41 09010-02 v3.0 D-SERVER Technical Handbook...
  • Page 124 www.neat-group.com...

Table of Contents