Dart RTLS User Guide Document D2119 Rev F Dart RTLS User Guide
CONFIDENTIAL INFORMATION OF Zebra Enterprise Solutions, A ZEBRA TECHNOLOGY COMPANY UNAUTHORIZED USE IS STRICTLY PROHIBITED. Dart and DartTag are trademarks of Zebra Enterprise Solutions, A Zebra Technologies Company. © Zebra Enterprise Solutions, A Zebra Technologies Company 1988 - 2016. All rights reserved. This document has been made available as part of the license that has been granted to an authorized user of Zebra Enterprise Solutions software.
Contents 1 General Description 7 Concept of operation ............................................................................................... 7 Dart RTLS Hub ......................................................................................................... 8 Dart RTLS Receiver .................................................................................................. 8 DartTags ..........................................................................................................
Contents 8 Configuring output control 43 9 Hub administration 47 Access protection on the Hub ............................................................................... 48 Hub Log-In .............................................................................................................. 49 Log-In Rules ..................................................................................................... 49 Roles and Permissions ................................................................
Contents 13 Status 97 Viewing Receiver status ........................................................................................ 97 Viewing Receiver List .......................................................................................... 101 Viewing Tag status............................................................................................... 103 14 Data Security 105 SSH user password .............................................................................................
1 General Description The Dart Real Time Locating System (RTLS) Ultra-Wideband (UWB) system is designed for the tracking of personnel and/or equipment. A base system is defined as one Hub, four or more Receivers, one or more reference tags, and multiple DartTags for tracking individual assets or personnel. In This Section Concept of operation .............................................................................. 7 Dart RTLS Hub .......................................................................
General Description Dart RTLS Hub The Dart RTLS Hub houses a single board CPU that: Interprets the data sent from the Receivers. Generates the identity and location of each DartTag within a designated area. The Hub LAN interface makes the results available to client computers for further processing and display. The following figure shows the front view of the Dart RTLS Hub. The Hub accepts input power of 100-240 Volts AC and provides power to the Receivers over a CAT 5E cable.
General Description pulses from the DartTags and generates packets of information, which are in turn sent to the Hub over a CAT5E cable. You can connect the Receivers directly to a Hub port connection or in a daisy chain to other Receivers. Each Receiver receives 48VDC from the previous Receiver (or from the Hub if it is the first Receiver in the line) and passes the 48VDC on to the next Receiver in line via the CAT 5E cable.
General Description A unique 4-byte hexadecimal ID that is programmed by the factory into the Receiver. This unique Receiver ID is used to identify the Receiver in the Dart Hub configuration. DartTags The DartTags are UWB transmit-only devices that communicate wirelessly with the Receivers. They have a nominal center frequency of 6.55 GHz with a peak and average power compliant with FCC Part 15 regulations.
Unpacking Dart RTLS 2 Unpacking Dart RTLS Typically, a Dart RTLS System is shipped with the following items: Dart RTLS Hub, with mounting brackets and power cord Dart Receivers DartTags To unpack Dart RTLS: 1 Open the shipping container and carefully remove the contents. 2 Return all packing materials to the shipping container and save it. 3 Ensure that all items listed above are included in the shipment. 4 Check each item for damage.
3 Installing the Dart RTLS hardware Before installation, review the Safety and Installation Warnings and Cautions document – D26819. Dart RTLS is a precision tracking system and requires a degree of exactness in installation. Specifically, the Receiver and reference tag locations are critical to insure optimum performance. The accuracy of these positions directly influences the accuracy of the results.
Installing the Dart RTLS hardware need a minimum of three Receivers. The ideal installation is a rectangular box with Receivers in each of the four corners, installed as high as possible (near the ceiling) and with the antenna of each Receiver pointing towards the center of the box. Placing the cables You can install a cable in the open or install it professionally. Zebra recommends that you check all cable connections with a cable tester prior to installing the system.
4 Connecting the Receiver cables You can connect Receivers directly to a Hub port connection or in a daisy chain to other Receivers. Each Receiver receives 48VDC from the previous Receiver (or from the Hub, if it is the first Receiver in the line) and passes the 48VDC on to the next Receiver in line via the CAT 5E cable. Location data throughput varies depending on the configuration of the receivers.
Connecting the Receiver cables 4 Connect the remaining end of the second CAT 5E cable to the RJ45 connector marked "IN" of Receiver #2. 5 Connect a third CAT 5E cable to the RJ45 connector marked "OUT" of Receiver #2. 6 Connect the remaining end of the third CAT 5E cable to the RJ45 connector marked "IN" of Receiver #3. 7 Connect the last (fourth) CAT 5E cable to the RJ45 connector marked "OUT" of Receiver #3.
5 Connecting multiple hubs The Hubs can be connected in Daisy chain configuration to synchronize their clocks which will enable hubs to use receiver from other hubs whose clocks are in sync with each other. The front panel of the Hub has 2 RJ45 connectors that are used for clock synchronization marked as CLOCK IN and OUT. There are 8 other RJ45 connectors that are used for connecting receivers, (marked numbers 1 through 8 under RECEIVERS) to the hub.
Connecting multiple hubs 6 For optimal performance, the CAT 5E cable needs to be less than 1000 feet. 7 Limit number of hubs used for clock sync to 8. DO NOT create a loop by connecting the last hub on the daisy chain back to first hub in the daisy chain. The result can be unpredictable and system will not function properly.
Connecting to the Dart RTLS Hub 6 Connecting to the Dart RTLS Hub Configuring and retrieving data requires a computer connection to the Dart RTLS Hub. You can connect the computer to the Hub through a direct connection or through a LAN. These are the default IP settings for the Hub: IP Address 192.168.1.204 Subnet mask: 255.255.255.0 Default gateway address: 192.168.1.1 In This Section System Requirements...........................................................................
Connecting to the Dart RTLS Hub For applications using maps using WMF (windows metafile format) or EMF (enhanced metafile format), you must also download Java Advanced Imaging, version 1.1.3, from http://download.java.net/media/jai/builds/release/1_1_3/jai-1_1_3-lib-windows-i586-jre.exe. Connecting the Dart RTLS Hub to a PC through a LAN If you can access the 192.168.1 subnet through your LAN, you can directly connect the Hub to the LAN.
Connecting to the Dart RTLS Hub Entering the IP address of the hub on a web browser used to take the user to the hub GUI web page where Hub Administration and Management tasks could be performed. For Hubs with FW Version 5.0.0 or higher, entering the IP address on a web browser will instead direct the user to a web page about Zebra Hub Manager, its usage and download link.
Connecting to the Dart RTLS Hub Google Chrome: Enter the IP address of the hub and click on the link to Zebra Hub Manager Click Keep D2119 Dart RTLS User Guide 22
Connecting to the Dart RTLS Hub Double click on zebraHubManager.jar to launch or look up zebraHubManager.jar in Download folder and double click on it to launch.
Connecting to the Dart RTLS Hub Click Open to launch the Zebra Hub Manager or Save to save zebraHubManager.jar to Download folder. If Save option is selected in previous step, click Open to launch Zebra Hub Manager or look for zebraHubManager.ja in Download folder and double click to launch.
Connecting to the Dart RTLS Hub Zebra Hub Manager Zebra Hub Manager is a stand-alone Java application. It not only allows user to connect to hub to start the Hub Administration and Management application, and also manages hub connection parameters as profile. A profile contains a set of parameters/settings needed for connecting to a hub. A profile can be created and saved for future usage or just for one time hub access. Saved profiles are organized in folders.
Connecting to the Dart RTLS Hub 2 On the left hand side pane, click on All Profiles, and right click. Select either ‘New Folder’ or ‘New Profile’ 3 ‘New Folder’ creates a new folder for saving your profiles. This way the user can organize the different hub profiles under different categories (folders). For example – Profiles for all hubs in physical location G1 can be created in a folder named ‘G1’. 4 ‘New Profile’ creates a new profile for the hub the user intends to access.
Connecting to the Dart RTLS Hub With a saved or newly created profile, click Connect on the Zebra Hub Manager, the hub manger retrieves and starts the Hub Administration and Management application residing on the target Hub. The look and feel of the Hub Administration and Management application hasn’t changed and is similar to the Hub GUI accessed using the web browser for FW versions earlier than 5.0.0.
Connecting to the Dart RTLS Hub Required ports for connecting to the Dart RTLS Hub When connecting to the Dart Hub through a network, you oftentimes need to contact your Network administrator to unblock ports for access. The following table lists the ports that are needed for all Dart RTLS functions.
Configuring Dart RTLS 7 Configuring Dart RTLS Now that your computer is connected to the Dart RTLS Hub, you can configure the Dart RTLS for tracking with one or more reference tags. Before you do this, you should familiarize yourself with setting up a single reference tag (on page 34) and then add additional reference tags as required. To configure a single reference system: Configure the Hub network parameters. (on page 30) Establish a user-defined coordinate system.
Configuring Dart RTLS On windows, the Java run-time parameters can be changed using the Java Control Panel (accessing from Control Panel). From the Java Control Panel, Select Java tab, then the Java Runtime Environment Setting dialog appears. Inside the table, increase the corresponding Runtime Parameters. Following are few options available to change heap size: -Xms(size): set initial Java heap size. -Xmx(size): set maximum Java heap size.
Configuring Dart RTLS 3 In the Administration view, on the Network tab, modify the IP settings as needed. 4 For the new IP settings to take effect, click Save. Establishing a user-defined coordinate system For tag localization, you must establish the positions of the Receivers and reference tag for the system to operate properly. This requires that you define an origin and measure the x, y, and z positions of each receiver and reference tag (in feet or meters) with respect to that origin.
Configuring Dart RTLS To establish a user-defined coordinate system: 1 Choose an origin (0, 0, 0) point. 2 Measure the (x, y, z) coordinates of each Receiver from the (0, 0, 0) point. Make measurements to the front of the antenna. 3 Measure the (x, y, z) position of the reference tag from the (0, 0, 0) point. Configuring Receivers Next, you need to define the location of each active Receiver within the system.
Configuring Dart RTLS 2 In the Table View on the Configuration page, under Hub Setup, in the RTLS Receiver or Proximity Receiver table, right-click a row and select Add to add a receiver (optional). 3 To modify a setting for a Receiver, double-click the respective field in the row for the Receiver that requires editing; to complete the edit, press Enter or click any other table cell. Enabled: Double-click this field to activate or deactivate a Receiver for data collection.
Configuring Dart RTLS output a P-packet, indicating that a tag is visible by that Receiver but position information is not available. For more information on P-packets, see System Output (on page 83). Read Range: Select a value to control the Receiver sensitivity. The value can be from 1 to 25 if in coarse range control mode, or from 1 to 54 if in fine range control mode.
Configuring Dart RTLS Updating hub FPGA firmware or receiver firmware Once timing is established and the system is running, the reference tag is continuously monitored for presence and is used to update timing information. This monitoring is not required for accurate location data computation, but it is provided as real-time information about the status of the reference tag.
Configuring Dart RTLS 5 Click Save for the new configuration to take effect. Configuring health tag In addition to reference tags, health tags can be configured. Health tags are used to monitor system RTLS health over time. To configure a health tag: 1 Start Hub Administration and Management application, click Configuration.
Configuring Dart RTLS area is available to all Receivers, these Receivers should belong to a single Virtual Group. However, in cases where obstructions (such as walls or large machinery) make complete coverage undependable, installing extra Receivers helps, especially when properly configured into additional Virtual Groups. A Virtual Group is a predefined group of Receivers for which Dart RTLS calculates and reports positions.
Configuring Dart RTLS and top right corners) by right-clicking on the table header or table rows, and selecting Append or Insert; then click Auto to generate the remaining vertices of the rectangle. Click Save to save the input X-Y bounds; then click Exit to close the dialog box. For a differently shaped area, right-click on the table header or table rows, and select Append or Insert, enter the vertices, and click Save; then click Exit. To remove a vertex, right-click and select Remove.
Configuring Dart RTLS Z space to track must be surrounded by receivers and the X-Y-Z distances need to be relatively equivalent. In most installations, it is not practical to install receivers in positions where the X-Y-Z criteria yield accurate results. 1D and 2D—Select if you want the system to perform 2-D calculations when three or more RTLS Receivers detect the tag transmission; alternatively, it provides 1D position data when two RTLS Receivers detect the tag transmission.
Configuring Dart RTLS data output. Example 3—Groups having a mixture of equal and unique priorities. For example, there could be four Virtual Groups with the following results from a given tag transmission: Virtual Group 1 with priority 1 does not compute data successfully. Virtual Group 2 with priority 2 does compute data successfully. Virtual Group 3 with priority 2 does compute data successfully. Virtual Group 4 with priority 3 does compute data successfully.
Configuring Dart RTLS To delete a virtual group, right-click the respective row and select Remove 4 Repeat Step 3 for every Virtual Group to be used by this Hub. 5 Click Save for the Virtual Group configuration to take effect.
8 Configuring output control By default, the Dart RTLS Hub provides a data output stream in various formats For information on available output data formats, see System output (on page 83) You can modify the data output from the Hub to: Enable output of diagnostic messages (D-packets) from the Hub. Indicate the quality of data provided from the Hub for Locate and Non-locate data. To configure output control: 1 Start Hub Administration and Management application, click Administration.
Configuring output control firmware restart, or after saving the configuration. For non-critical errors or events, the system sends the corresponding D-packet only once each time an event or warning condition occurs. For critical system errors, the system sends the D-packets continuously until the error is cleared.
Configuring output control helpful when assessing why location data is different than expected. It can be useful in identifying undesirable reflected signals that may be causing Receivers to contribute to location computations. Dart Output Stream With RTLS data information, the Dart data output stream has the location data message in following format: ,,,,,,, , Detect Details. Select to include detect details in the locate.
Configuring output control When ‘N’ packets are enabled, non-locates generate ‘N’ packets instead of ‘P’ packets. 3 Click Save.
9 Hub administration You can use the Hub Administration and Management application to administer the Dart RTLS Hub. In This Section Access protection on the Hub ............................................................. 48 Hub Log-In ............................................................................................ 49 Event Log ............................................................................................... 52 Uploading certificates to Zebra Hub .................................
Hub administration Access protection on the Hub UWH1200 Hub provides optional role based access control and keeps a log of events with details on hub access and configuration changes. The access control setting on the ‘Main’ tab lets the user select if Open Access is preferred or Sign-in Based Access is preferred. With Open Access, anyone accessing the hub will have administrator access and only one user access is allowed at a time.
Hub administration Hub Log-In The hub is shipped with the following default user name and password – Username : admin Password : Admin1234 Both user name and password are case sensitive. A valid password should have a minimum length of 8 characters and should contain at least 1 uppercase character, 1 lowercase character and 1 number.
Hub administration Administrator - Administrator has full access to the hubs configuration and settings. Administrator can create users and assign roles to the users. Administrator can also change passwords for the users and delete the user accounts. Operator – Operator has access to all the features on the hub GUI except creating or modifying user accounts. Operator also cannot change hub network settings (NTP, Network, SNMP). Operator can change the password of his/her own account.
Hub administration Operator access To log-in and change password 1 2 3 4 Start Hub Administration and Management application, click Administration Log in as operator, under Sign In tab, using the username and password provided by your administrator. Click on Login. Click Change Password. Enter the Current Password and New Password (twice) to change the password for the operator account. Click Save. For security, click LogOut after the session is done.
Hub administration Event Log The hub supports event logging on hub user access and configuration changes. Event Log can be viewed only when System Access Control on the Main Tab is set to ‘Sign-In Based Access’ and user is logged in as an Administrator. The events are logged for the following actions User log in/log out, User account create/delete or password change. Changes on Administration page Changes on Configuration page Action or setting changes on diagnostic page.
Hub administration Uploading certificates to Zebra Hub 1 Uploading the certificate to the hub, the user may need to covert received certificate into three files: - Hub certificate in PEM format - CA certificate contain the whole certificate path from hub certificate issuer to a trusted CA in PEM format - unencrypted private key in PEM format 2 Start Hub Administration and Management application, click Administration, then enter Sign In tab.
Hub administration 5 Browse or input the path to three certificate files as list in step 1. 6 Click Upload. Defining the measurement units for coordinates You can specify whether Dart RTLS should store configuration information in feet or meters. To define the measurement unit system: 1 Start Hub Administration and Management application, click Administration.
Hub administration The NTP daemon synchronizes the system time with a user-specified NTP server. For more information about NTP and a list of public time servers, check the NTP Website at http://www.ntp.org. Proper operation of the NTP System Clock Synchronization feature requires that you specify the DNS setting. Check with your system administrator to determine what DNS setting to use for your network.
Hub administration D2119 Dart RTLS User Guide 56
Hub administration Shutting down the Hub processor Before you turn off power to the Dart RTLS Hub, Zebra recommends that you shut down the Hub processing software. To shut down the Hub processing software: 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, on the Main tab, click Shutdown Hub.
Hub administration Rebooting the Hub processor If rebooting the hub processor is needed, follow the steps below. To reboot the Hub processing software: 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, on the Main tab, click Reboot Hub. 3 When prompted, click OK, then Hub Administration and Management application exits.
Hub administration Configuring SNMP The Dart SNMP agent is compliant with the protocols SNMPv1, SNMPv2c, and SNMPv3. It supports MIB II (RFC 1213 MIB) and SNMPv2 MIB and is compliant with generic traps outlined in RFC-1215. To enable or disable SNMP functionality: 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, on the SNMP tab, select or clear the Enable the SNMP Agent check box. 3 Click Save.
Hub administration the hub via SNMP. The value 0.0.0.0 represents any host. Permission: The permission type granted to the specified community, which can be any of the following: None—Does not allow any operations. Read only—Allows specified community to get information from the Hub. Read Write—Allows getting information from and setting information on the Hub. Notify—Allows SNMP trap notifications to be sent to the community on the host specified via IP Address.
Hub administration Backing up and restoring Hub configuration data Dart RTLS lets you back up or restore Hub configuration settings. It preserves all configuration settings, including Receiver and reference tag locations, virtual group settings, and user maps. This feature is useful for preserving data, moving configuration settings from one Hub to another, moving configuration settings to/from System Builder, and backing up settings on the Hub while evaluating alternative settings.
Hub administration Uploading new Hub RTLS firmware You can easily change the Hub RTLS firmware to a different version. Before beginning a firmware upload, make sure the client machine can access the hub RTLS firmware through a CD, hard drive, or local network. Uploading hub RTLS firmware is non-reversible. Therefore, make sure you install the proper firmware to the Hub. To upload Dart Hub RTLS firmware: 1 Start Hub Administration and Management application, click Administration.
Hub administration to enable Preserve reference matrix during the Hub FW upload process. Upon hub reboot after new firmware is loaded, the preserved reference matrix is used and Dart hub does not require re-referencing.
Hub administration FPGA firmware to hub hardware (Only for Hub FW 4.1.0 and lower). Uploading new Receiver firmware Uploading the receiver firmware to a different version is straight forward process. It includes two steps: upload receiver firmware to the hub, and install the firmware to Receivers. Before you start, make sure the client machine can access the receiver firmware through a CD, hard drive, or local network. Uploading receiver firmware is non-reversible.
Hub administration After uploading the receiver firmware to the hub, the Upload Receiver Firmware table contains firmware change status for each detected receiver. The hub checks firmware version of each detected receiver to determine if a firmware change is available, and shows the result in the “Firmware Change Available?” column. Rx #: Hexadecimal receiver number as configured; if not configured, leave blank. Receiver ID: The unique 4-byte hexadecimal ID programmed into the receiver.
Hub administration 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, click the Advanced tab to open the web page. 3 Select desired read range control mode, coarse or fine. 4 Check Normalized Data Quality Indication (DQI) to select normalized DQI mode or deselect the option for default DQI mode. 5 Click Save for the user settings to take effect.
Hub administration reasons. To be able to automatically retry after initial failure is a big convenience for the customer. Dart RTLS system provides user the choice to enable automatic retry. Reference suspension should only be used when on-site maintenance is an integral part of using the RTLS system. To turn on/off reference tag suspension: 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, click the Advanced tab to open the web page.
Hub administration control password used for logging in (as administrator or operator). To configure the system to enable reference suspension protection: 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, select the Advanced tab 3 Check or uncheck Confirmation on Critical Change box to enable or disable reference suspension protection.
Hub administration If Suspend Reference Tag is enabled, then a confirmation message box is shown which looks as follows If Password Required on Confirmation is selected, after confirming changing by clicking YES button on either of above confirmation message box, a password input message box will show up. Failing to provide correct password will cause the saving operation to abort.
Hub administration New algorithm incorporates pre-pruning and pruning. Pre-pruning is an improvement in location algorithm which detects and removes late receivers. Only significant reflection issues can be resolved with pre-pruning. Algorithm always performs pre-pruning. Example: Without pre-pruning: ‘Locates %’ are less due to non-convergence. With pre-pruning: ‘Locates %’ improve, as bad receivers are removed.
Hub administration By default, this receiver pruning based location algorithm is disabled. The user can enable it using Hub Administration and Management application. After the pruning algorithm enabled, whenever Dart RTLS system fails to produce a good tag location from a tag blink in the standard fashion, it starts analyzing and pruning received timings and will most likely output a valid tag location.
Hub administration until 6 receivers are left. To configure the system to enable receiver pruning based location algorithm: 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, select the Advanced tab 3 Check or un-check Enhance Locate Algorithm via Receiver Pruning to enable or disable the receiver pruning based location algorithm. 4 Click Save for the user settings to take effect.
Hub administration To enable best effort pruning 1 Start Hub Administration and Management application, click Administration. 2 In the Administration view, select the Advanced tab 3 Click Enhance Locate Algorithm via Receiver Pruning first if it is not enabled. 4 Click Best Effort Pruning. 5 Click Save to make the change take effect. Configuration Recovery Configuration Recovery provides a method to recover from undesirable configuration changes. Configuration Recovery is non-reversible.
Hub administration By clicking Ok, the Configuration Recovery feature is available. The Configuration Recovery allows the user to restore a new configuration or the factory default Dart hub configuration. It also allows the user to backup current Dart hub configuration for further investigation.
Hub administration Admin User Access An admin account is provided with Dart hub that is accessible through the RS232 port. This user account has limited capability and is provided to allow IP address reset, user password resets, and to restore factory configuration settings. The UWH-1200 RS-232 port is a host male connector, to connect to a computer, a female to female null cable is required (such as L-com CSNULL9FF-5A WWW.L-COM.COM).
Hub administration admin user choices are as follows: Reset GUI Password: removes all accounts except the default administrator account and resets its password to factory default. Reverts the System Access Control setting to “Open Access”. Reset Configuration: resets hub configuration settings (with the exception of IP address) to the factory default configuration. Reset IP address: resets the Dart hub network setting (IP address, subnet mask) to the default IP Address: 192.168.1.204 Subnet mask: 255.255.
10 Demo software Dart RTLS uses a JAVA™ client applet as a utility for displaying initial system check-out and results (the location of tags and receivers). This utility serves as a demo. Most likely, you will need to obtain client software that is tailored to a more specific application.
Demo software Background Grid: Select the check box to display background grid; then enter a value to modify the spacing. Site Map: Select the desired site map to be displayed as geographic background by clicking on the corresponding radio button. The Default_Site provides blank background.
Demo software If required, right-click the map and select an option to zoom in or out, resize to fit, or rotate the map. Viewing and filtering the raw data stream from the Hub You can view, record, and filter the raw data stream of location data from the Hub. To view and filter the raw data stream from the Hub: 1 Start the Hub Administration and Management application, click Demonstration. 2 In the Demonstration view, right-click the map and select Check Raw Data.
Demo software Tag to show: Select whether to view data for all tags or for a specific tag. If you select Specify a tag, enter a Tag ID into the respective field. Under Raw Data Report, you can: Control the output flow of Hub data to this display, by selecting Stop Display or Start Display. Record the raw data stream to a text file by selecting Start Record. When prompted, enter a file name for saving the logged data. To stop recording entirely, click Stop Record.
Demo software Changing the site map You can change the site map of the 2-D grid that displays the graphical results by adding customized background files to the Hub. Map files must be in .jpg, .gif, .emf or .wmf format. To change the site map: 1 Start the Hub Administration and Management application, click Configuration. 2 In the Configuration view, click Configure Site Map.
11 System output Dart RTLS system provides different outputs format options, Dart and Z-SLMF, which are supported on TCP ports 5117and 5118 respectively. All tag data from the Dart hub, are coded in ASCII and sent over the LAN interface. To retrieve tag data from the Hub, you need a client program using the stream communication protocol and a connection to the output port. This section describes the format of tag data in the Dart output data stream In This Section Basic system output ......................
System Output enough information is available to calculate the position), or 1-, 2-, or 3-D calculations are unsuccessful. You also use P-packets to show data from a Proximity Receiver. N: Extended Non-locate packet (N-Packet). N packets give extended information for a non-locate ‘P’ packet. N packets contain the detect details and when enabled, are sent instead of the non-locate P packets. D: Diagnostic packet (D-packet).
System Output except for P type data, is a Virtual Group ID (in decimal). The tag location data is computed from the time of flight measurements of the Receivers within the virtual group. In the case of P type data, is the Rx # of the Receiver that detected the transmission. is a Line Feed character (with ASCII code = 0x0A) to terminate a location data string. The following is an example of system output from a Dart RTLS Hub. T,0021F7B1,29.53,18.38,1.52,12,1433877485.930,4,*,G0.
System Output Where is the Geometric Dilution of Precision value for the location data with prefix of ‘G’. When the GDOP result is not meaningful this field contains an asterisk. Non-locate Details Non-locate details is an optional field that is available for the output data stream. This information helps assess why location data is not available for a particular tag event. Non-locate details can take on the values described in the following table. Value P Description Only presence data expected.
System Output P,00002294,1.1,2.2,8.5,12,1161175614.527,B1,C1 In this example, Receiver units A1, B1, and D1 have detected tag 00002294; the Non-locate details (C1) indicates that a location computation was not made because virtual group 1 could not converge on a good location computation. This information likely means that one or more of the Receivers reporting tag 00002294 are getting an indirect signal (reflection) instead of a direct signal from the tag.
System Output Locate Details You can enable Locate details for the output data stream (see Configuring output control (on page 43)). Locate details TLS describes which Receivers were used in a location computation. The output appears in the following format, with an additional field : ,,,,,,,, where describes the Receivers involved in the location computation.
System Output Example 2: T,00201B47,81.1,47.7,5.0,12,1433424563.235,4,3.09,G0.34,S41-S81-S42-S82S43-S84,HC2P2-H41-H81R2-HFF-H42-H82R2-H43-H84P2 o o o o S41-S81-S42-S82-S43-S84 – receivers 41, 81, 42, 82, 43 and 84 were used for this locate computation. HC2P2-H84P2 – receivers C2 and 84 saw the blink but were pre-pruned in virtual group 2. H41-HFF-H42-H43 – receivers 41, FF, 42 and 43 saw the blink and were not pruned or pre-pruned in any virtual groups.
12 Diagnostics Dart RTLS provides low-level tests that you can use to determine the receive range of each active Receiver. For example, you can detect: Whether a reference signal is in a good position for all Receivers within a reference group. Whether a particular Receiver is receiving tag transmissions adequately. What Receivers are detecting a tag (possibly in error, due to reflections). Cabling problems with connections to Receivers. Diagnostic testing interrupts normal system operation.
Diagnostics Receiver test With the Receiver Test, you can: Examine the real-time data collection of tag information (Tag Report field), as illustrated in the figure. Information is presented as Rx #: Receiver ID => tag: tag ID. Run a timed test to get a list of all tags that a Receiver detects (Result field). The test results in accumulated tag data per Receiver, showing the total number of good or missing tag packets per Receiver along with the calculated transmit frequency for each detected tag.
Diagnostics Total tags = 18. To run a timed test: 1 Start the Hub Administration and Management application, click Diagnostics. 2 In the Diagnostics view, on the Receiver Test tab, from the Rx # list inside Receiver section, select the receiver for which you want to run the test, or select All to include all receivers. 3 Optionally, from the Timer list in Timer section, select a particular time or select Off. 4 Click Start to run the test.
Diagnostics grouping and average tag reception rates. The Hub software lists inconsistencies as islands within a virtual group. Battery status of Reference tags: Shows the battery level and indicates if the battery is low. You can control the following System test parameters: Tags: Select All Reference Tags, Tag List or All Tags to determine what rate of tags each Receiver detects.
Diagnostics 6 Interpret the test results Under Tag Packet Receiving Rate: Examine the reference tags or tags in the Ref Tag or Tag ID field. If a reference tag is not detected, it is shown in red. Also check the battery icon , which indicates the battery status of the reference tag. Green signals a good status, red icon means that the battery is low and you should replace the tag. Examine the Rx # columns, which display the average receive rate of the tag over the test time.
Diagnostics To run a Cable Test: 1 Start the Hub Administration and Management application, click Diagnostics. 2 In the Diagnostics view, on the Cable Test tab, from the Hub Port(s) list, specify the hub port or all hub ports. 3 Click Start to run the test. 4 After start, on each selected hub port, the system detects receiver one by one. Whenever a new receiver is detected, a communication test is performed between the hub and that receiver, and the statistics on error(s) are collected.
Diagnostics cable fault is within a daisy chain. This test provides guidance on the locations of potentially poor cable connections. Some connection errors (such as termination errors on the power line of the cable) may be exhibited further downstream. In this case, additional debug with physical cable testers or cable replacement will be needed.
13 Status You can use the Status view to examine the current status of the system and verify the proper operation of reference tags and Receivers. All status information updates every 10 seconds. In This Section Viewing Receiver status ...................................................................... 97 Viewing Receiver List ........................................................................ 101 Viewing Tag status .............................................................................
Status The tab displays the UWH-1200 hub and Receiver daisy chains connected to each hub port. Receivers are drawn in different rectangular box shapes, depending on their capability: A rectangular icon, , represents a Receiver that does not support firmware upgrade; A rectangular icon with the bottom-right corner missing, compatible with firmware upgrades; A rectangular icon with the bottom-right and upper-left corner missing, a receiver compatible with ISO/IEEE formatted tags.
Status visual notification of a large maintenance icon is shown at bottom-left corner of UWH1200 Dart Hub. This notification can only be cleared by rebooting UWH-1200 hub. In case of auto recovery from system fault, care has been take in Dart RTLS firmware so that reference timing established before system fault is preserved, and will be used after auto recovery. The port is color coded either grey or blue representing the port speed.
Status Reduced read range A special character ‘^’ is appended if the receiver has read range less than the maximum (25 in coarse range control mode or 54 in fine range control mode). In the following example, the Receiver #01 has an External antenna that is set at a read range setting of “24”. Mismatched read range: A special character ‘~’ is appended if the receiver has different read range setting than configured. This condition should not happen in normal condition.
Status Error message (red), such as: Receiver is not configured. Receiver communication loss. Viewing Receiver List The Receiver List tab contains detail information, including receiver read range, temperature, hardware information for all Receivers detected by the hub. To view Receiver status: 1 Start the Hub Administration and Management application, click Status. 2 On the Receiver List tab, examine the displayed information. This tab is automatically refreshed every 1 minute.
Status This tab contains information for all receivers detected by the hub: Rx #: The receiver # of the receiver being configured. Otherwise, left blank. Rx ID: Corresponding Receiver ID for the detected receiver. Temp: The current temperature in Celsius at the receiver. Volt: The current input voltage at the receiver RF Card Serial No: Serial number for the Receiver RF board. Dig Card Serial No: Serial number for the Receiver Digital board.
Status receiver is not configured. 3 Presence Detect: Indicates a receiver (RTLS or Proximity) is configured to output presence data. This is left blank if the receiver is not configured. Read Range: Read range setting of a receiver (1 – 25 in coarse range control mode or 1 – 54 in fine range control mode). When blank, the receiver is not configured. Remote Rx#: Receiver number of the receiver as configured on the remote hub. This field is 00 if the receiver is local or not remote.
14 Data Security Data security in Dart hub is allowed via SSH tunneling. In This Section SSH user password ............................................................................ 105 Non-secure data output .................................................................... 106 SSH user password When manufactured, the SSH user is created in each Dart hub unit for creating SSH tunnel with Dart hub and receiving output data in an encrypted fashion.
Data Security 3 Check Change Password, Change SSH Password dialog appears. 4 Type the current SSH password and the new SSH password in input boxes, and click Save to accept it. Non-secure data output By default, Dart hub support output data in both secured and none-secured format. User can force data output only in secured fashion. To disable non-secure data output: 1 Start the Hub Administration and Management application, click Administration.
Appendix A: Information Data (I-packets) Dart Hub provides output data stream that are available on TCP port 5117. The data from the dart hub is coded in ASCII and sent over the LAN interface. To retrieve tag data from the hub, you need a client program using the TCP communication protocol and a connection to the output port.
Appendix B: Diagnostics Output Data (D-packets) Evt_id Evt_msg Description Info 0 Tag Resets Tag Reset (due to low battery?) Extended information from the tag 1 Dart Wand turned tag on Dart wand turned on a tag which was previously off 0 2 Dart Wand turned tag off Dart wand turned a tag off which was previously on 0 3 Dart Wand changed tag blink rate Dart wand changed the blink rate of the tag 0 4 Whereport turned tag on Tag, previously off, was turned on upon entering a (configured) W
Appendix B: Diagnostics Output Data (D-packets) Receiver ‘I’ packet format: Format of receiver information packet is as follows: I,Rx number,Overflow count, CRC error count,Bad header count,Bad packet format count,timestamp,evt_id,evt_msg Rx number – active receiver number Overflow count – FIFO overflow count CRC error count- Number of packet CRC errors Bad header count – Bad message header count Bad packet format count – Number of packet format errors timestamp - timestamp of reporting time evt_id - ev
Appendix B: Diagnostics Output Data (D-packets) Appendix B: Diagnostic Output Data (Dpackets) This section contains descriptions for all D-packets that Dart UWB RTLS may output. D-packets are sent to the output stream only when enabled on the Output Control tab of the Hub Configuration form (See Configuring output control (on page 43)). These messages are either error or warning messages that are useful both during initial installation and for continuous monitoring of the Dart RTLS system.
Appendix B: Diagnostics Output Data (D-packets) Initialization D-packets Operation Actions No Receiver detected No Receiver enabled No Receiver activated No reference tag enabled No virtual group enabled Enabled Receiver detected Enabled Receiver not detected Unknown Receiver detected Receiver 00 detected Receiver has detected a reference tag Reference tag not found Receiver firmware upgrade available Receiver firmware mismatch Reference ta
Appendix B: Diagnostics Output Data (D-packets) Operation D-packets Active Receiver communication lost Active Receiver communication OK Reference tag detected Reference tag lost Reference tag battery low Reference tag battery OK Receiver does not see reference tag Receiver has detected the reference tag Active Receiver loss of referencing Server is alive Hub Failure Health state change CPU temperature too high USB Rx Failure Health tag failure Health tag
Appendix B: Diagnostics Output Data (D-packets) No Receiver detected No Receiver activated Enabled Receiver not detected Enabled Receiver detected Unknown Receiver detected Description: No Receivers have been detected by the Hub. Recommended Action: Verify connections and power from the Hub to the Receiver (s). Message Type: This error packet will be sent continuously until the error condition is cleared.
Appendix B: Diagnostics Output Data (D-packets) Receiver 00 detected Reference tag not found Receiver has detected a reference tag Receiver firmware upgrade available Description: Old Receiver (with 1 byte serial number) shipped with ’00’ ID has not been configured to a valid serial number. Recommended Action: Configure the serial number on the receiver to something other than ‘00’ (configuration has to be manually done on the side of the receiver).
Appendix B: Diagnostics Output Data (D-packets) Reference tag suspended Description: All enabled reference tags are suspended as required by configuration.
Appendix B: Diagnostics Output Data (D-packets) Health State Change USB Rx Failure Health tag not found Health tag detected NTP sync succeeded NTP sync failed Description: This D-packet message is sent when there is a change in system health state. Recommended Action: None. Message Type: The event packet is sent only once whenever a change in system health state is detected.
Appendix B: Diagnostics Output Data (D-packets) Remote Hub Connection failed Description: An attempt to connect to a remote hub failed at UNIX time of . Recommended Action: Check network cable and whether remote hub is functioning. Message Type: This event packet will be sent after every retry to connect with the remote hub and will persist until a connection can be established.
Appendix B: Diagnostics Output Data (D-packets) Reference tag detected Reference tag battery low Reference tag battery OK Receiver does not see reference tag Receiver has detected a reference tag Description: A reference tag with tag ID , configured to be at location( x,y,z), is detected with a tag battery level of at UNIX time of . Recommended Action: None.
Appendix B: Diagnostics Output Data (D-packets) Active Receiver communication lost Active Receiver communication OK Active Receiver loss of referencing Server is alive Hub Failure Description: An active Receiver with a Receiver # , which is configured to be at location (x, y, z), has lost normal communication to the Hub. The field is always 0, and represents the last time (in UTC format) when the Hub is still able to communicate with the Receiver.
Appendix B: Diagnostics Output Data (D-packets) Health State Change CPU temperature too high USB Rx Failure Health Tag Failure Health tag battery low Description: This D-packet message is sent when there is a change in system health state. Recommended Action: None. Message Type: The event packet is sent only once whenever a change in system health state is detected.
Appendix B: Diagnostics Output Data (D-packets) Health tag battery OK Health tag not found Health tag detected NTP sync succeeded NTP sync failed Remote Hub Connection failed Description: A health tag configured at location (x, y, z) recovered from battery low condition. When a health tag gets into battery low condition, once its battery status is at a value above the threshold, it exits from battery low condition and send this D-packet once Recommended Action: None.
Appendix B: Diagnostics Output Data (D-packets) Remote Hub Connections succeeded Hub Sync 100M Clock error Hub Sync 100M clock good Description: An attempt to connect to a remote hub succeeded at UNIX time of . Recommended Action: None. Message Type: This event packet will be sent once when an attempt to connect with the remote hub succeeds.
Appendix B: Diagnostics Output Data (D-packets) D-Packet D-packet ID Message Type Continuous Message? Active Receiver communication OK 17 Status Receiver firmware upgrade available -18 Warning Receiver firmware mis-match -19 Warning Server is alive 1 Status Reference pair broken -24 Error Reference tag suspended 25 Status Reference tag suspension fail -25 Error Receiver loss of referencing -35 Error Restart start 2 Status Restart end 3 Status Health state change 4 Status
Appendix C: Receiver read range settings The Dart hub provides two control modes for Receiver read range: coarse mode and fine mode. Coarse control mode is the default mode, which allows read range setting of a Receiver to be set from 1 to 25, where 1 is the smallest read range setting and 25 is the largest read range setting. In fine control mode, read range settings vary from 1 to 54, where 1 is the least sensitive (shortest read range) and 54 is the most sensitive (longest read range) setting.
Dart RTLS read range based on the UWB Coarse Range setting Estimated Range ( Feet) 1,000 UWC-1100 High Gain Antenna 100 UWC-1200 Mid Gain Antenna 10 UWC-1300 Omni Antenna 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 "Read Range" Setting D2119 Dart RTLS User Guide 126
Appendix D: Hub Health Monitoring Appendix D: Hub Health Monitoring This section contains details of the health monitor module inside the Dart RTLS hub. Health monitor is a new feature inside hub RTLS firmware that latches the health of the Dart RTLS system and sends out D packets when there is a change in the health status.
Appendix D: Hub Health Monitoring Bit number Error Type 0 Configuration Error 1 No Rx detected 2 No Rx activated 3 Enabled Rx not detected 4 Reference tag not found 5 Reference suspension failed 6 CPU temperature high 7 Hub Failure 8 Health tag not found 9 USB Rx failure 10 NTP Sync failure 11 Remote Hub Connection fail 12 Hub Sync clock error 10-15 Reserved 16 Rx communication loss 17 Reference tag loss 18 Rx referencing loss 19 Reference pair broken 20 Health tag fa
Appendix D: Hub Health Monitoring 18 Health tag battery low Health Status Change MessageUpon system status change, may it be because of changes of Current_Health_State, Outstanding_Error_Types or Outstanding_Warning_Types, Dart RTLS system will send out a diagnostic message of type “Health state change” in Dart output data stream. This diagnostic message has syntax as below.
Appendix D: Hub Health Monitoring D2119 Dart RTLS User Guide 130
Appendix E: Cabling guidelines Appendix E: Cabling guidelines Shielded Cat5E cable assembly recommendations Dart RTLS may use shielded CAT 5E cables with a minimum of 24 AWG. Alternatively, you may use shielded CAT 6E cables and solid cables. You must connect the cable connector to the cable shield. The following table lists acceptable parts for shielded CAT 5E stranded and shielded 24 AWG cables.
Appendix E: Cabling guidelines D2119 Dart RTLS User Guide 132
Appendix E: Cabling guidelines Cable length planning guideline You can connect Receivers directly to a Hub port connection or in a daisy chain to other Receivers. Each Receiver receives 48VDC from the previous Receiver (or from the Hub, if it is the first Receiver in the line) and passes the 48VDC on to the next Receiver in line via the CAT 5E cable. This CAT 5E cable also provides a clock source and serial communication to the Receivers.
Appendix E: Cabling guidelines Daisy chain with 1000 feet from the Dart Hub to Receiver 1 and Receiver 1 to Receiver 2 Dart Hub Sen 1 1000' Dart Hub Sen 2 1000' Sen 1 1000' Dart Hub Sen 2 Sen 1 Dart Hub 1000' 1000' 1000' Dart Hub 1000' Sen 1 1000' Dart Hub 1000' Sen 2 1000' 900' Sen 5 700' Sen 4 800' Sen 3 Sen 5 800' Sen 4 900' 400' 600' 700' 800' Sen 6 Sen 5 Sen 4 Sen 3 300' 500' 600' 700' Sen 7 Sen 5 Sen 4 Sen 3 Sen 2 Sen 1 1000' 600' 300' 400' 500' Sen 6 Sen
Appendix E: Cabling guidelines Daisy chain with 1000 feet from Dart Hub to Receiver 1, Receiver 1 to Receiver 2, and Receiver 2 to Receiver 3 Dart Hub Sen 1 1000' Dart Hub Sen 2 1000' Sen 1 1000' Dart Hub Sen 2 Sen 1 Dart Hub 1000' 1000' 1000' Dart Hub 1000' Sen 1 1000' Dart Hub 1000' Sen 1 1000' 1000' Sen 5 700' Sen 4 800' Sen 3 1000' 600' 700' 1000' Sen 5 Sen 4 Sen 3 Sen 2 500' 600' 1000' Sen 5 Sen 4 Sen 3 Sen 2 400' 500' 1000' Sen 5 Sen 4 Sen 3 Sen 2 300' 400'
Appendix E: Cabling guidelines Daisy chain with equal cable length between Hub and Receivers Dart Hub Sen 1 300' Dart Hub Sen 2 400' Dart Hub Sen 2 500' Sen 1 600' Dart Hub Sen 1 Dart Hub Sen 2 Sen 1 800' Dart Hub Sen 2 Sen 3 Sen 2 900' Sen 4 Sen 4 800' Sen 3 900' 900' 600' 700' 800' Sen 6 800' Sen 5 900' Sen 7 Sen 6 Sen 5 Sen 4 400' Sen 7 Sen 6 Sen 5 Sen 8 500' 600' 700' Sen 7 Sen 6 Sen 5 Sen 8 300' 400' 500' 600' 700' 800' 800' Sen 1 900' Sen 3 Sen 6 Se
Appendix F: Air Filter Maintenance This section includes information on air filter replacement and cleaning for UWH-1200 hub 1) Filters are to be replaced or cleaned when they are visibly dirty. When replacing or cleaning filter, Hub does not need to be turned off as long as this operation is completed within ½ hour. 2) To remove filter, remove 4 thumb screws (use a Philips screw driver to remove if needed) and detach frame from hub. Remove the dirty filter from the frame. Figure 1.
Regulatory Information Appendix G: HTTPS Support Appendix G: HTTPS Support Dart Hub now provides better HTTPS support to establish secure connection. In the process of establishing HTTPS connection to the hub, some verification can be enabled or disabled from Zebra Hub Manager (for Hub FW version 5.0.0 and up). The following fashions of HTTPS connection are supported by Dart Hub and Zebra Hub Manager.
Regulatory Information Appendix G: HTTPS Support Continue when it appears. To enable the HTTPS only mode In profile settings using Zebra Hub Manager, check Enable HTTPS, uncheck Certificate Verification and Certificate Common Name Verification.
Regulatory Information Appendix G: HTTPS Support To enable this type of secure connection, in the profile settings in Zebra Hub Manager, input the fully qualified domain name in Hub IP or Domain Name box, check Enable HTTPS, uncheck Certificate Verification, and check Certificate Common Name Verification.
Regulatory Information Appendix G: HTTPS Support 5 Browse or input the path to three certificate files as list in step 1. 6 Click Upload. Uploading CA certificate to Zebra Hub Manager 1 On Zebra Hub Manager, click on Accept CA Certificate, browse to the location where the CA certificate exists and click Load.
Regulatory Information Regulatory Information Regulatory Information This section includes regulatory information for: Canada (on page 142) U.S. (on page 142) EU (on page 143) Canada regulatory information The hub and receivers comply with CAN ICES-3(A)/NMB-3(A). The tags comply with RS-220 and RSS-GEN. Refer to document number D1685 for additional details for the tags. This Class A digital apparatus complies with Canadian ICES-003.
Regulatory Information Regulatory Information RF Notice Any changes or modifications to Zebra Enterprise Solutions (ZES) equipment not expressly approved by ZES could void the user’s authority to operate the equipment. EU regulatory information Refer to document number D1685 for details for the tags.
Specifications This section lists specifications for Dart UWB RTLS. Dart RTLS General Specifications Mode of Operation Precision relocation using time-differences of arrival Accuracy ± 1 foot (without signal averaging) ± 4 inches (with signal averaging) Maximum number of Receivers per Hub 64 Data throughput per Receiver high-speed pair 2.
Specifications Model UWH-1200 Ports Power 2- RJ45 Ethernet ETH0 & ETH1 (ETH1 is not used) 8 – RJ45 (Clock, Data & Power to Receivers) 2 –RJ45 (clock in & clock out currently not used) 1- RS232 – This connector is a host male connector, in order to connect to a computer which will be a host as well, a female to female null cable is required (such as L-com CSNULL9FF-5A WWW.L-COM.
Zebra customer support All Dart RTLS documentation and firmware updates (including the Dart RTLS User Manual) may be downloaded from the Customer Portal. After logging into the Customer Portal, click on “Content” from the menu bar, select “Dart UWB (Current Customers)” from the “Search In” drop-down list, then press “Go!” If you are a first-time Customer Portal user, you can obtain a user name and password by following these steps: 1 Go to the Zebra Support Center Login page: http://www.zebra.
