all | frequencies |
|
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|---|
manuals | photos | label |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 3 4 |
|
Users Manual | Users Manual | 1.33 MiB | January 17 2024 | |||
1 2 3 4 |
|
Users Manual revised | Users Manual | 1.32 MiB | May 25 2022 / June 02 2022 | |||
1 2 3 4 |
|
Internal Photos | Internal Photos | 2.26 MiB | April 29 2022 / June 03 2022 | |||
1 2 3 4 |
|
External Photos | External Photos | 481.76 KiB | January 17 2024 | |||
1 2 3 4 |
|
ID Label Location Info | ID Label/Location Info | 285.02 KiB | April 29 2022 / June 03 2022 | |||
1 2 3 4 |
|
2.911 Attestation Letter | Attestation Statements | 55.61 KiB | January 17 2024 | |||
1 2 3 4 |
|
2.911 Attestation Letter Agent Authorization Agreement | Attestation Statements | 952.43 KiB | January 17 2024 | |||
1 2 3 4 |
|
Antenna information | Test Report | 2.69 MiB | January 17 2024 | |||
1 2 3 4 | Block Diagram | Block Diagram | January 17 2024 | confidential | ||||
1 2 3 4 |
|
Confidentiality Request | Cover Letter(s) | 55.82 KiB | January 17 2024 | |||
1 2 3 4 | Operational Description | Operational Description | January 17 2024 | confidential | ||||
1 2 3 4 |
|
Permissive Change Letter | Cover Letter(s) | 244.92 KiB | January 17 2024 | |||
1 2 3 4 |
|
RF Exposure Evaluation | RF Exposure Info | 248.03 KiB | January 17 2024 | |||
1 2 3 4 |
|
Test Setup Photos | Test Setup Photos | 558.71 KiB | January 17 2024 | |||
1 2 3 4 |
|
Test report | Test Report | 973.83 KiB | January 17 2024 | |||
1 2 3 4 |
|
Test report Annex 1 measurement diagrams | Test Report | 2.17 MiB | January 17 2024 | |||
1 2 3 4 | Tune Up Info | Parts List/Tune Up Info | January 17 2024 | confidential | ||||
1 2 3 4 |
|
FCC Confidentiality Request | Cover Letter(s) | 246.25 KiB | April 29 2022 / June 03 2022 | |||
1 2 3 4 | Operational Description | Operational Description | April 29 2022 | confidential | ||||
1 2 3 4 | Schematics | Schematics | April 29 2022 | confidential | ||||
1 2 3 4 |
|
Test Setup Photos - 15B | Test Setup Photos | 1.08 MiB | April 29 2022 / June 03 2022 | |||
1 2 3 4 |
|
Test report 15B - ext photos | Test Report | 1.51 MiB | April 29 2022 / June 03 2022 | |||
1 2 3 4 |
|
Test report 15B - plots | Test Report | 361.16 KiB | April 29 2022 / June 03 2022 | |||
1 2 3 4 |
|
Test report 15B - report | Test Report | 548.19 KiB | April 29 2022 / June 03 2022 | |||
1 2 3 4 | Test Setup Photos | April 29 2022 / June 02 2022 | ||||||
1 2 3 4 |
|
Test Setup Photos - UWB revised | Test Setup Photos | 595.23 KiB | May 20 2022 / June 02 2022 | |||
1 2 3 4 | Test Report | April 29 2022 / June 02 2022 | ||||||
1 2 3 4 |
|
Test report UWB - ext photos revised | Test Report | 1.05 MiB | May 20 2022 / June 02 2022 | |||
1 2 3 4 | Test Report | April 29 2022 / June 02 2022 | ||||||
1 2 3 4 |
|
Test report UWB - plots revised | Test Report | 5.19 MiB | May 20 2022 / June 02 2022 | |||
1 2 3 4 | Test Report | April 29 2022 / June 02 2022 | ||||||
1 2 3 4 |
|
Test report UWB - report revised | Test Report | 1010.36 KiB | May 20 2022 / June 02 2022 |
1 2 3 4 | Users Manual | Users Manual | 1.33 MiB | January 17 2024 |
Eliko RTLS Installation Guide Tallinn 2021 CONTENTS DOCUMENT SCOPE AND PURPOSE.................................................................... 3 TERMINOLOGY .......................................................................................... 3 1. SYSTEM COMPONENTS AND CONNECTIVITY .................................................... 4 2. ANCHOR INSTALLATION ........................................................................... 6 a. Anchor coordinate measurement .......................................................... 7 b. Correction factors for anchor coordinates ............................................ 7 3. ELIKO RTLS SERVER SETUP ..................................................................... 9 a. Starting up the Eliko RTLS server ....................................................... 9 b. Anchors Network .............................................................................. 9 c. Clients Network ............................................................................... 9 d. Wi-Fi network ................................................................................... 9 4. CONNECTING TO THE ELIKO RTLS MANAGER .................................................. 9 a. Wi-Fi enabled laptop ......................................................................... 9 b. Cable-based ethernet connection via Anchor network port ......................10 c. Connect a PC directly to Client network port .........................................10 5. ELIKO RTLS ANCHOR AND TAG FEEDBACK.....................................................10 6. CLIENT NETWORK .................................................................................12 7. ELIKO RTLS MANAGER ...........................................................................12 a. Layout plan ...................................................................................12 b. Anchors list ...................................................................................13 c. Tags list ........................................................................................14 d. Dashboard .....................................................................................15 8. CLIENT SOFTWARE INTEGRATION ..............................................................16 9. TURNING OFF THE SYSTEM ......................................................................16 2 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee DOCUMENT SCOPE AND PURPOSE This installation guide is designed to help users install the Eliko RTLS system. TERMINOLOGY GUI Graphical User Interface LoS Line of sight NLoS Non-line of sight PoE Power over Ethernet RTLS Real-Time Location System UWB Ultra-Wideband 3 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 1. SYSTEM COMPONENTS AND CONNECTIVITY The Eliko RTLS consists of:
Optionally used for setting up the system:
Eliko RTLS Anchors Anchors can be used in two different configurations:
Anchors in standard configuration use a Power over Ethernet (PoE) con-
nector for both power and data trans-
mission (note: anchors can also be powered by micro-USB, and Ethernet can be used for data transmission only). All Ethernet cables starting with cat 5 are compatible with the Eliko RTLS system. Eliko recommends using 8 core Ethernet cables. Anchors in Wi-Fi configuration use internal Wi-Fi modules for data trans-
mission and are meant for temporary setups or for installations where draw-
ing cables is complicated. Anchors in Wi-Fi configuration must be powered with micro-USB cables or PoE injectors. Eliko RTLS Tags Tags communicate with anchors over UWB and measure the distances on which the coordinate calculations are based. The tags are battery powered and can be charged or be powered by an external source such as a forklift. Eliko RTLS Server the Eliko RTLS Server is an Ubuntu Linux machine with multiple roles. It creates the RTLS anchor network, calculates coor-
dinates, connects the Eliko RTLS with any third-party information system and hosts the Eliko RTLS Manager. Eliko RTLS Manager Graphical user interface (GUI) for system setup, con-
figuration and visualisation. PoE Switch The switch is necessary in a standard setup in which case all anchors must be connected to the switch via ethernet cables. The switch trans-
fers data from the anchors to the Eliko RTLS Server and powers the anchors. PoE Extender The PoE Extender is a convenient way to extend the network by using a switch that is powered by a PoE port. Instead of drawing cables to each anchor separately, a PoE extend-
er can be used to draw one cable to the extender and draw cables from the extender to the anchors. The extender transfers data from the anchors to the Eliko RTLS Server and powers the an-
chors. Wi-Fi repeater The Wi-Fi repeater is useful if the distance to the Eliko RTLS server is longer than 90 m or there are obstructions that do not allow Wi-Fi connection to the anchors. If you are using your local Wi-Fi network, then using Wi-Fi repeaters is not needed because the anchors can be configured to communicate through the local Wi-Fi network to the server. USB charging dock USB charging dock to charge the tags and update multiple devices at the same time. Contact Eliko for additional consultation for other connectivity options. 4 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Figure 1. A small-scale Eliko RTLS network with ethernet connectivity. Figure 2. A small-scale Eliko RTLS network with Wi-Fi connectivity. 5 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 2. ANCHOR INSTALLATION In order to cover the entire tracking area, it is usually best to install the anchors at an elevated position, misaligned and close to the edges of the tracking area (but not in the corners). In special rooms, such as corridors, the anchors should be placed using a trapezoid or rhombus pattern. The anchors should be placed on the wall using Eliko RTLS wall mounts (see Figure 5).. The wall mounts have moving heads that you can use to adjust the anchor position. The anchors can be positioned in any direc-
tion on the wall or even upside down when attached to the ceiling. Make sure there Figure 3. Best practices for different rooms/areas. 6 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee are no objects close to the anchors block-
ing the LoS. Although the performance of the anchor is very similar in all directions, in more difficult scenarios it is recommend-
ed that the anchor side with the Ethernet port faces the direction of least interest. In square-shaped rooms it is best to mount anchors to the ceiling as displayed in Fig-
ure 3; if this is not possible, then use the alternative option displayed in Figure 3. When anchors are mounted to the ceiling, they do not need to be horizontal with the ceiling. Please note, anchors should be al-
ways installed in locations where they are at least 20 cm away from the users. NB! When using 3D features we recommend 6 anchors. For 3D setup, there is no straightforward practice for getting the best results, and there is a lot more to take account of. Every tracking area should be investigated sepa-
rately. Therefore, we recommend contacting our customer support when there is a need for 3D features. Contact Eliko for additional help in deter-
mining the exact anchor locations. a. Anchor coordinate measurement The Eliko RTLS needs you to turn your physical surroundings into a XYZ-space in order to determine the accurate anchor locations. The anchor locations must be measured very accurately. Any inaccuracies will adversely affect the overall accuracy of the tag positioning coordinates. First, determine a point in your tracking area that will be your zero-coordinate point in the X- and Y-axes (0;0). This reference point is how you identify the location of all the anchors. For example, if your tracking area has perpendicular, straight walls that can act as X- and Y-axes, then your reference point is the corner of the intersection of these two. Measure the coordinates relative to the tracking area zero point for all of the an-
chors. Even if you track objects only in 2D
(the XY-plane), it is important to measure the Z-coordinate of the anchors as well. Usually, this is the height of the anchors from the tracking area floor. Coordinates can be measured manually with a simple tape measure or a hand-held laser distance meter. However, we recommend using professional land surveyor services for the most accurate results, especially in large-scale setups. NB! Mark down the anchor serial numbers before fixing them on the walls. You will need the serial numbers later when you insert the coordinates into the Eliko RTLS Manager. Contact Eliko for additional help in measur-
ing the anchor locations. b. Correction factors for anchor coordinates Since anchors are physical three-dimen-
sional objects, they have their own local zero-coordinate points. The distance from an anchor to a tag is measured between the antennas located inside of each devices casings. The antennas inside the anchors have fixed coordinates relative to the sym-
bol on the front side of the anchor (Figure 4). The correction factors for determining the precise location of the anchor are: 0 mm for the X-axis, 15mm for the Y-axis and 36 mm for the Z-axis. Figure 4. Local coordinate system for the anchors. 7 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee NB! The coordinate axes displayed in Figure 4 dont necessarily match with the overall coordinate system. The correction factors should be used only for very accurate (less than 50 cm) anchor coordinate measurements. Otherwise, they can be ignored. Figure 5. Eliko anchor and anchor mount thread for universal fixtures micro USB ethernet cable 8 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 3. ELIKO RTLS SERVER SETUP a. Starting up the Eliko RTLS server The Eliko RTLS Server is an Ubuntu Linux machine with dual ethernet interfaces one for the anchor network (Anchors Network) and the other for integration with the cli-
ents system (Clients Network). Addition-
ally, the RTLS Server includes an optional integrated Wi-Fi module, so connections to the RTLS anchors and/or to the clients ap-
plication logic may also be done wirelessly. NB! Before power-up, attach Wi-Fi antennas to the server. If there are no Wi-Fi anten-
nas with the server, then the server does not have Wi-Fi. After attaching the Wi-Fi antennas, connect the anchors to the Anchors Network port, and after that connect the servers Client Network port with the local network router. After this, you can plug in the server into the power supply. Press the power button to start the server. Wait for a couple of minutes for all of the anchors to come on-
line. A blinking LED light indicates that the anchor has been powered. b. Anchors Network On the Anchors Network, the RTLS Server runs a DHCP server and leases IP addresses for everyone that asks for it. In the most common case, a PoE switch is connected to Anchors Network port of the RTLS Server. The anchors will be connected to the PoE switch. The RTLS anchors, PoE switch(es), optional additional ethernet switches and cables make up the RTLS anchor network. c. Clients Network The RTLS Server has another ethernet port called the Clients Network, which is meant for connecting the RTLS Server to the clients network. The Clients Network is configured to ask for an IP address from an external DHCP server residing in the clients network. It is the responsibility of the Clients Network administrator to configure their DHCP server in a way that it leases an IP address for the RTLS Server. d. Wi-Fi network Additional to the cable-based Anchors Net-
work and Clients Network connections, the RTLS Server includes an integrated Wi-Fi module. The RTLS Servers Wi-Fi network is logically connected to Anchors Network, so everyone connecting with this Wi-Fi obtains an IP address, leased by the DHCP server running on the RTLS Server. 4. CONNECTING TO THE ELIKO RTLS MANAGER There are three options to access the Eliko RTLS Manager web interface:
a. Wi-Fi enabled laptop For connecting a Wi-Fi enabled laptop, which is located close enough to the RTLS Server, the easiest way is using the wireless network provided by the RTLS Server. The name of this network may be Eliko-RTLSS-
BS-XXXX, KIORTLSS-BS-XXXX or KIORTLSS-AP-
XXXX, where XXXX is a 4-digit number which is unique among all the RTLS Servers. Just look this network up on your laptop and create a connection to it. This connection is protected by a password, which you can find as a sticker on the bottom of the RTLS Server. Please note that on some operating systems, the laptop will assume it gets in-
ternet access through this Wi-Fi connection, which is not true. After clicking connect on the laptop, it may be shown for quite a long time that establishing the connection is still in progress, while the connection is actually created with a couple of seconds. This means it would be okay to verify the 9 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee connection just a couple of seconds after clicking the connect button, without waiting for the progress indicator to finish. When connected via Wi-Fi, you can access the Eliko RTLS Manager web interface by using your web browser to access the fol-
lowing URL: http://10.8.4.1 b. Cable-based ethernet connection via Anchor network port For a cable-based ethernet connection, the easier way is to connect the PC behind the Anchors Network and leave the Clients Net-
work unused. The PC should be configured to obtain an IP address from an external DHCP server (this configuration may already be the default one). If the RTLS anchors are connected via Wi-Fi, the Anchors Net-
work port of the RTLS Server is empty and a simple ethernet cable may be used to con-
nect the PC. If the Anchors Network port is already occupied by a network switch, then the PC should be connected behind any switch residing in the Anchors Network. Note that PoE functionality is not required for connecting the PC, so you can also use a non-PoE port for this connection. For this cable-based connection, there is no pass-
word to access the Eliko RTLS Manager web interface. You can just use your browser to access the following URL: http://10.8.4.1 c. Connect a PC directly to Client network port It is also possible to connect a PC directly to the Clients Network port, but this may be more complicated to configure. The Cli-
ents Network interface expects an exter-
nal DHCP server to lease an IP address to the RTLS Server. With the current case, the clients PC should have a DHCP server run-
ning for this purpose. When connecting via the Clients Network port, you cant access the same URL as mentioned in the previous options. You need to use the admin panel of your DHCP server to find the IP address it has leased to the RTLS Server. You can then access the RTLS Manager web inter-
face by using your web browser and this IP address as the URL. Contact ELIKO for additional consultation for other connectivity options 5. ELIKO RTLS ANCHOR AND TAG FEEDBACK Both the anchors and the tags are equipped with an LED light on the front side of the device. This is used as a feedback indi-
cator to give the user information about the devices status. The following tables describe the different combinations for the LED colour and interval. The Eliko RTLS anchors are automatically turned on when they are connected to a power supply (either by an ethernet cable connected to a PoE switch or by a micro-USB adapter). To restart the anchor, just unplug it from the power supply for a few seconds. The Eliko RTLS tags have an on/off button. Hold the button for 2 seconds to turn it on. A white LED fade-in followed by a blinking light indicates that the tag is online. To turn it off, hold the button again for 2 seconds. A white LED fade-out appears and the blinking stops now the tag is offline. A quick press (less than a second) will re-
start the tag. 10 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Table 1. Different statuses of the anchor and the corresponding LED statuses. LED colour LED interval Indication description Green Yellow Red Blinking Blinking Blinking Device is powered and in range of tags Device is powered, no tags in range Hardware/software error. If restarting the anchor doesnt work please contact Eliko Figure 6. The Eliko Tag. Table 2. Different statuses of the tag and the corresponding LED indications. LED colour LED interval Indication description USB status White White Green Yellow Green Yellow Red Red Fade-in Fade-out On On Blinking Blinking On Blinking Device start up Device shut down Battery full Battery charging In range OK Either Either Connected Connected Disconnected No valid anchors responding Disconnected Battery empty, connect charger Disconnected Hardware/software If restarting the tag doesnt work please contact Eliko error. Either 11 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 6. CLIENT NETWORK If you connect the Eliko RTLS Servers Client Network port to your companys network router, you need to make sure your network has a DHCP server running. After the Eliko RTLS Server has obtained an IP address from your network, you must iden-
tify this address. Usually, this can be done by accessing the admin page of your net-
work router. Look up the Eliko RTLS Server IP address under the name KIO-RTLSS. The Eliko RTLS Manager can be accessed from your network by using a web browser to access a URL like http://10.10.10.10
(replace 10.10.10.10 with the IP address your network has leased for the Eliko RTLS Server). 7. ELIKO RTLS MANAGER Go to the previously obtained server IP address to access the Eliko RTLS Manager using any browser. Read and accept the Eliko RTLS EULA. Now you are ready to start configuring the system. Figure 7. View of the Eliko RTLS Manager front page. a. Layout plan Click the Start setting up the system button on the Welcome page. You can see the Plan configuration panel on the right side of the page and an interactive window on the left. You can start by uploading the plan image. If you dont want to use plan at the moment, you can just click the Set Anchors button to move forward to the anchors configuration page. 12 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Figure 8. Plan configuration page. Add a floorplan (optional) of your tracking area by clicking Upload. Next, go to Con-
figure the axes to match the X- and Y-axes on the plan with the actual zero coordinate and axes. The positive direction of an axis can be changed by clicking on the Invert X (Y) button. Also, you can switch axes by clicking the Switch axes button. Click and hold down left mouse button to drag floorplan to the position that you want. Click and hold the resizing icon on the top right corner of the floorplan to resize the plan. Another option is to adjust the plan coordinates. Plan coordinates enable you to resize the image and move it around to match the anchor placement. Click Save changes button to save the changes. Next, go to the list of anchors by clicking the Anchors menu button. b. Anchors list Figure 9. floorplan resizing icon Under the Anchors tab you should see all of the anchors with their S/N that are connected to the server. The green or red dot in front of each anchor indicates if it is on- or offline. You can also adjust anchor coordinates under the Anchors tab. To save the coor-
dinates click the Save new anchor coordi-
nates button. 13 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Under the Anchors tab you may also see the Change anchors role pop-up menu. You cant configure roles anymore because after recent improvements to our system, we do not use roles and we have not yet removed these rudiments from the Eliko RTLS Manager. All the anchors are visible as having role A at the moment. Figure 10. View of the anchors list. c. Tags list The Tags tab gives you an overview of all the tags that have been connected to the server. Tags have a green/red/yellow colour indication for being on- or offline or in standstill mode. Since the tags operate on batteries, it is important to keep an eye on the battery level to avoid data loss during tracking. For 2D positioning, you must define the fixed height of the tag, which should be as close to the real height of the tag as possible. Each tag has a configurable update rate. The highest update rate available in the Eliko RTLS Manager is 10 times per second
(10 Hz), while the lowest is once per min-
ute. It is possible to select update rates as high as 150 times per second (150 Hz) by using the Eliko RTLSS Communication Protocol. Contact ELIKO to receive the PDF version of this document or find it under the System/Documentation tab. You can also use the option for dynamic update interval, which is useful when the tracked object is occasionally stationary. The location data is received with high update interval while the tag is moving, and when it stays stationary it will reduce the update rate to the level of low update interval. High update interval can only be smaller or equal to low update interval. Offline tags show the date and time of when the last coordinate was calculated. Also, the system saves and displays the tags last position before going offline on the dashboard, which can be useful for locat-
ing the tag. 14 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Figure 11. View of the tags list. d. Dashboard The dashboard is a visualisation tool where you can see all of the tags moving in real time. Here you can also see if the anchors are placed correctly relative to the floor-
plan. Different options allow you to display all devices or, for example, only online de-
vices. Default screen refresh rate is 10 Hz. You can use the dashboard to verify the positioning accuracy of the Eliko RTLS sys-
tem. For example, walk through the tracking area to make sure the physical location of the tag matches the displayed location on the floorplan. Information about every de-
vice is shown while clicking on the icons on the map. The system displays the devices serial number, alias (for tags), battery lev-
el (for tags) and current coordinate. Figure 12. Visualisation options for the dashboard. 15 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 8. CLIENT SOFTWARE INTEGRATION The Eliko RTLS Server communicates with external parties via TCP ports. It can act both as a TCP server or a client. The Eliko RTLS Server is always listening for incoming TCP connection requests on port 25025. You can use the Eliko RTLS Servers IP address and port 25025 to create a connection to the Eliko RTLS Server from your own appli-
cation. You can then configure the Eliko RTLS from your own application, as well as to get live positioning data. Alternatively, the Eliko RTLS Server can instead act as a 9. TURNING OFF THE SYSTEM TCP client and connect to your server. For that, go to the System/General Settings tab on the Eliko RTLS Manager and select the IP address and TCP port your server is listening from. Additional instructions on how to integrate the Eliko RTLS to your own application can be found under the System/Documenta-
tion tab in the Eliko RTLS Manager. Do not unplug the server directly from the mains power because it can possibly corrupt the file system. To power down, use the on/
off button on the server. After the server power indicator light has turned off, it is safe to unplug the devices. NOTICE:
This device complies with Part 15 of the FCC Rules [and contains license-exempt trans-
mitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canadas licence-exempt RSS standard(s)]. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that may cause undesired operation. Lmetteur/rcepteur exempt de licence contenu dans le prsent appareil est conforme aux CNR dInnovation, Sciences et Dveloppement conomique Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes:
(1) lappareil ne doit pas produire de brouillage, et
(2) lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. NOTICE:
Changes or modifications made to this equipment not expressly approved by Eliko may void the FCC authorization to operate this equipment. NOTICE:
The range of the devices may be negatively affected by devices operating at the same wavelenght. 16 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee NOTICE:
According to FCC rules, the anchors may only be operated indoors. Operation outdoors is in violation of 47 U.S.C. 301 and could subject the operator to serious legal penal-
ties. NOTICE:
This equipment has been tested and found to comply with the limits for a Class B digi-
tal device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help. NOTICE:
FCC Regulations 15.521 Techical Requirements Applicable for All UWB Devices.
(a) UWB devices may not be employed for the operation of toys. Operation onboard an aircraft, a ship or a satellite is prohibited. Date Version
(Version.Revision) Edited By Description of Change 12.10.2020 20201012_1 07.07.2021 20210707_2 T. Pikkmaa T. Pikkmaa Initial document Revision 17 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee
1 2 3 4 | Users Manual revised | Users Manual | 1.32 MiB | May 25 2022 / June 02 2022 |
Eliko RTLS Installation Guide Tallinn 2021 CONTENTS DOCUMENT SCOPE AND PURPOSE.................................................................... 3 TERMINOLOGY .......................................................................................... 3 1. SYSTEM COMPONENTS AND CONNECTIVITY .................................................... 4 2. ANCHOR INSTALLATION ........................................................................... 6 a. Anchor coordinate measurement .......................................................... 7 b. Correction factors for anchor coordinates ............................................ 7 3. ELIKO RTLS SERVER SETUP ..................................................................... 9 a. Starting up the Eliko RTLS server ....................................................... 9 b. Anchors Network .............................................................................. 9 c. Clients Network ............................................................................... 9 d. Wi-Fi network ................................................................................... 9 4. CONNECTING TO THE ELIKO RTLS MANAGER .................................................. 9 a. Wi-Fi enabled laptop ......................................................................... 9 b. Cable-based ethernet connection via Anchor network port ......................10 c. Connect a PC directly to Client network port .........................................10 5. ELIKO RTLS ANCHOR AND TAG FEEDBACK.....................................................10 6. CLIENT NETWORK .................................................................................12 7. ELIKO RTLS MANAGER ...........................................................................12 a. Layout plan ...................................................................................12 b. Anchors list ...................................................................................13 c. Tags list ........................................................................................14 d. Dashboard .....................................................................................15 8. CLIENT SOFTWARE INTEGRATION ..............................................................16 9. TURNING OFF THE SYSTEM ......................................................................16 2 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee DOCUMENT SCOPE AND PURPOSE This installation guide is designed to help users install the Eliko RTLS system. TERMINOLOGY GUI Graphical User Interface LoS Line of sight NLoS Non-line of sight PoE Power over Ethernet RTLS Real-Time Location System UWB Ultra-Wideband 3 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 1. SYSTEM COMPONENTS AND CONNECTIVITY The Eliko RTLS consists of:
Optionally used for setting up the system:
Eliko RTLS Anchors Anchors can be used in two different configurations:
Anchors in standard configuration use a Power over Ethernet (PoE) con-
nector for both power and data trans-
mission (note: anchors can also be powered by micro-USB, and Ethernet can be used for data transmission only). All Ethernet cables starting with cat 5 are compatible with the Eliko RTLS system. Eliko recommends using 8 core Ethernet cables. Anchors in Wi-Fi configuration use internal Wi-Fi modules for data trans-
mission and are meant for temporary setups or for installations where draw-
ing cables is complicated. Anchors in Wi-Fi configuration must be powered with micro-USB cables or PoE injectors. Eliko RTLS Tags Tags communicate with anchors over UWB and measure the distances on which the coordinate calculations are based. The tags are battery powered and can be charged or be powered by an external source such as a forklift. Eliko RTLS Server the Eliko RTLS Server is an Ubuntu Linux machine with multiple roles. It creates the RTLS anchor network, calculates coor-
dinates, connects the Eliko RTLS with any third-party information system and hosts the Eliko RTLS Manager. Eliko RTLS Manager Graphical user interface (GUI) for system setup, con-
figuration and visualisation. PoE Switch The switch is necessary in a standard setup in which case all anchors must be connected to the switch via ethernet cables. The switch trans-
fers data from the anchors to the Eliko RTLS Server and powers the anchors. PoE Extender The PoE Extender is a convenient way to extend the network by using a switch that is powered by a PoE port. Instead of drawing cables to each anchor separately, a PoE extend-
er can be used to draw one cable to the extender and draw cables from the extender to the anchors. The extender transfers data from the anchors to the Eliko RTLS Server and powers the an-
chors. Wi-Fi repeater The Wi-Fi repeater is useful if the distance to the Eliko RTLS server is longer than 90 m or there are obstructions that do not allow Wi-Fi connection to the anchors. If you are using your local Wi-Fi network, then using Wi-Fi repeaters is not needed because the anchors can be configured to communicate through the local Wi-Fi network to the server. USB charging dock USB charging dock to charge the tags and update multiple devices at the same time. Contact Eliko for additional consultation for other connectivity options. 4 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Figure 1. A small-scale Eliko RTLS network with ethernet connectivity. Figure 2. A small-scale Eliko RTLS network with Wi-Fi connectivity. 5 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 2. ANCHOR INSTALLATION In order to cover the entire tracking area, it is usually best to install the anchors at an elevated position, misaligned and close to the edges of the tracking area (but not in the corners). In special rooms, such as corridors, the anchors should be placed using a trapezoid or rhombus pattern. The anchors should be placed on the wall using Eliko RTLS wall mounts (see Figure 5).. The wall mounts have moving heads that you can use to adjust the anchor position. The anchors can be positioned in any direc-
tion on the wall or even upside down when attached to the ceiling. Make sure there Figure 3. Best practices for different rooms/areas. 6 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Coordinates can be measured manually with a simple tape measure or a hand-held laser distance meter. However, we recommend using professional land surveyor services for the most accurate results, especially in large-scale setups. NB! Mark down the anchor serial numbers before fixing them on the walls. You will need the serial numbers later when you insert the coordinates into the Eliko RTLS Manager. Contact Eliko for additional help in measur-
ing the anchor locations. b. Correction factors for anchor coordinates Since anchors are physical three-dimen-
sional objects, they have their own local zero-coordinate points. The distance from an anchor to a tag is measured between the antennas located inside of each devices casings. The antennas inside the anchors have fixed coordinates relative to the sym-
bol on the front side of the anchor (Figure 4). The correction factors for determining the precise location of the anchor are: 0 mm for the X-axis, 15mm for the Y-axis and 36 mm for the Z-axis. are no objects close to the anchors block-
ing the LoS. Although the performance of the anchor is very similar in all directions, in more difficult scenarios it is recommend-
ed that the anchor side with the Ethernet port faces the direction of least interest. In square-shaped rooms it is best to mount anchors to the ceiling as displayed in Fig-
ure 3; if this is not possible, then use the alternative option displayed in Figure 3. When anchors are mounted to the ceiling, they do not need to be horizontal with the ceiling. Please note, anchors should be al-
ways installed in locations where they are at least 20 cm away from the users. NB! When using 3D features we recommend 6 anchors. For 3D setup, there is no straightforward practice for getting the best results, and there is a lot more to take account of. Every tracking area should be investigated sepa-
rately. Therefore, we recommend contacting our customer support when there is a need for 3D features. Contact Eliko for additional help in deter-
mining the exact anchor locations. a. Anchor coordinate measurement The Eliko RTLS needs you to turn your physical surroundings into a XYZ-space in order to determine the accurate anchor locations. The anchor locations must be measured very accurately. Any inaccuracies will adversely affect the overall accuracy of the tag positioning coordinates. First, determine a point in your tracking area that will be your zero-coordinate point in the X- and Y-axes (0;0). This reference point is how you identify the location of all the anchors. For example, if your tracking area has perpendicular, straight walls that can act as X- and Y-axes, then your reference point is the corner of the intersection of these two. Measure the coordinates relative to the tracking area zero point for all of the an-
chors. Even if you track objects only in 2D
(the XY-plane), it is important to measure the Z-coordinate of the anchors as well. Usually, this is the height of the anchors from the tracking area floor. Figure 4. Local coordinate system for the anchors. 7 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee NB! The coordinate axes displayed in Figure 4 dont necessarily match with the overall coordinate system. The correction factors should be used only for very accurate (less than 50 cm) anchor coordinate measurements. Otherwise, they can be ignored. Figure 5. Eliko anchor and anchor mount thread for universal fixtures micro USB ethernet cable 8 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 3. ELIKO RTLS SERVER SETUP a. Starting up the Eliko RTLS server The Eliko RTLS Server is an Ubuntu Linux machine with dual ethernet interfaces one for the anchor network (Anchors Network) and the other for integration with the cli-
ents system (Clients Network). Addition-
ally, the RTLS Server includes an optional integrated Wi-Fi module, so connections to the RTLS anchors and/or to the clients ap-
plication logic may also be done wirelessly. NB! Before power-up, attach Wi-Fi antennas to the server. If there are no Wi-Fi anten-
nas with the server, then the server does not have Wi-Fi. After attaching the Wi-Fi antennas, connect the anchors to the Anchors Network port, and after that connect the servers Client Network port with the local network router. After this, you can plug in the server into the power supply. Press the power button to start the server. Wait for a couple of minutes for all of the anchors to come on-
line. A blinking LED light indicates that the anchor has been powered. b. Anchors Network On the Anchors Network, the RTLS Server runs a DHCP server and leases IP addresses for everyone that asks for it. In the most common case, a PoE switch is connected to Anchors Network port of the RTLS Server. The anchors will be connected to the PoE switch. The RTLS anchors, PoE switch(es), optional additional ethernet switches and cables make up the RTLS anchor network. c. Clients Network The RTLS Server has another ethernet port called the Clients Network, which is meant for connecting the RTLS Server to the clients network. The Clients Network is configured to ask for an IP address from an external DHCP server residing in the clients network. It is the responsibility of the Clients Network administrator to configure their DHCP server in a way that it leases an IP address for the RTLS Server. d. Wi-Fi network Additional to the cable-based Anchors Net-
work and Clients Network connections, the RTLS Server includes an integrated Wi-Fi module. The RTLS Servers Wi-Fi network is logically connected to Anchors Network, so everyone connecting with this Wi-Fi obtains an IP address, leased by the DHCP server running on the RTLS Server. 4. CONNECTING TO THE ELIKO RTLS MANAGER There are three options to access the Eliko RTLS Manager web interface:
a. Wi-Fi enabled laptop For connecting a Wi-Fi enabled laptop, which is located close enough to the RTLS Server, the easiest way is using the wireless network provided by the RTLS Server. The name of this network may be Eliko-RTLSS-
BS-XXXX, KIORTLSS-BS-XXXX or KIORTLSS-AP-
XXXX, where XXXX is a 4-digit number which is unique among all the RTLS Servers. Just look this network up on your laptop and create a connection to it. This connection is protected by a password, which you can find as a sticker on the bottom of the RTLS Server. Please note that on some operating systems, the laptop will assume it gets in-
ternet access through this Wi-Fi connection, which is not true. After clicking connect on the laptop, it may be shown for quite a long time that establishing the connection is still in progress, while the connection is actually created with a couple of seconds. This means it would be okay to verify the 9 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee connection just a couple of seconds after clicking the connect button, without waiting for the progress indicator to finish. When connected via Wi-Fi, you can access the Eliko RTLS Manager web interface by using your web browser to access the fol-
lowing URL: http://10.8.4.1 b. Cable-based ethernet connection via Anchor network port For a cable-based ethernet connection, the easier way is to connect the PC behind the Anchors Network and leave the Clients Net-
work unused. The PC should be configured to obtain an IP address from an external DHCP server (this configuration may already be the default one). If the RTLS anchors are connected via Wi-Fi, the Anchors Net-
work port of the RTLS Server is empty and a simple ethernet cable may be used to con-
nect the PC. If the Anchors Network port is already occupied by a network switch, then the PC should be connected behind any switch residing in the Anchors Network. Note that PoE functionality is not required for connecting the PC, so you can also use a non-PoE port for this connection. For this cable-based connection, there is no pass-
word to access the Eliko RTLS Manager web interface. You can just use your browser to access the following URL: http://10.8.4.1 c. Connect a PC directly to Client network port It is also possible to connect a PC directly to the Clients Network port, but this may be more complicated to configure. The Cli-
ents Network interface expects an exter-
nal DHCP server to lease an IP address to the RTLS Server. With the current case, the clients PC should have a DHCP server run-
ning for this purpose. When connecting via the Clients Network port, you cant access the same URL as mentioned in the previous options. You need to use the admin panel of your DHCP server to find the IP address it has leased to the RTLS Server. You can then access the RTLS Manager web inter-
face by using your web browser and this IP address as the URL. Contact ELIKO for additional consultation for other connectivity options 5. ELIKO RTLS ANCHOR AND TAG FEEDBACK Both the anchors and the tags are equipped with an LED light on the front side of the device. This is used as a feedback indi-
cator to give the user information about the devices status. The following tables describe the different combinations for the LED colour and interval. The Eliko RTLS anchors are automatically turned on when they are connected to a power supply (either by an ethernet cable connected to a PoE switch or by a micro-USB adapter). To restart the anchor, just unplug it from the power supply for a few seconds. The Eliko RTLS tags have an on/off button. Hold the button for 2 seconds to turn it on. A white LED fade-in followed by a blinking light indicates that the tag is online. To turn it off, hold the button again for 2 seconds. A white LED fade-out appears and the blinking stops now the tag is offline. A quick press (less than a second) will re-
start the tag. 10 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Table 1. Different statuses of the anchor and the corresponding LED statuses. LED colour LED interval Indication description Green Yellow Red Blinking Blinking Blinking Device is powered and in range of tags Device is powered, no tags in range Hardware/software error. If restarting the anchor doesnt work please contact Eliko Figure 6. The Eliko Tag. White White Green Yellow Green Yellow Red Red Fade-in Fade-out On On On Blinking Blinking Blinking Table 2. Different statuses of the tag and the corresponding LED indications. LED colour LED interval Indication description USB status Device start up Device shut down Battery full Battery charging In range OK Either Either Connected Connected Disconnected No valid anchors responding Disconnected Battery empty, connect charger Disconnected Hardware/software If restarting the tag doesnt work please contact Eliko error. Either 11 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 6. CLIENT NETWORK If you connect the Eliko RTLS Servers Client Network port to your companys network router, you need to make sure your network has a DHCP server running. After the Eliko RTLS Server has obtained an IP address from your network, you must iden-
tify this address. Usually, this can be done by accessing the admin page of your net-
work router. Look up the Eliko RTLS Server IP address under the name KIO-RTLSS. The Eliko RTLS Manager can be accessed from your network by using a web browser to access a URL like http://10.10.10.10
(replace 10.10.10.10 with the IP address your network has leased for the Eliko RTLS Server). 7. ELIKO RTLS MANAGER Go to the previously obtained server IP address to access the Eliko RTLS Manager using any browser. Read and accept the Eliko RTLS EULA. Now you are ready to start configuring the system. Figure 7. View of the Eliko RTLS Manager front page. a. Layout plan Click the Start setting up the system button on the Welcome page. You can see the Plan configuration panel on the right side of the page and an interactive window on the left. You can start by uploading the plan image. If you dont want to use plan at the moment, you can just click the Set Anchors button to move forward to the anchors configuration page. 12 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Figure 8. Plan configuration page. Add a floorplan (optional) of your tracking area by clicking Upload. Next, go to Con-
figure the axes to match the X- and Y-axes on the plan with the actual zero coordinate and axes. The positive direction of an axis can be changed by clicking on the Invert X (Y) button. Also, you can switch axes by clicking the Switch axes button. Click and hold down left mouse button to drag floorplan to the position that you want. Click and hold the resizing icon on the top right corner of the floorplan to resize the plan. Another option is to adjust the plan coordinates. Plan coordinates enable you to resize the image and move it around to match the anchor placement. Click Save changes button to save the changes. Next, go to the list of anchors by clicking the Anchors menu button. b. Anchors list Figure 9. floorplan resizing icon Under the Anchors tab you should see all of the anchors with their S/N that are connected to the server. The green or red dot in front of each anchor indicates if it is on- or offline. You can also adjust anchor coordinates under the Anchors tab. To save the coor-
dinates click the Save new anchor coordi-
nates button. 13 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Under the Anchors tab you may also see the Change anchors role pop-up menu. You cant configure roles anymore because after recent improvements to our system, we do not use roles and we have not yet removed these rudiments from the Eliko RTLS Manager. All the anchors are visible as having role A at the moment. Figure 10. View of the anchors list. c. Tags list The Tags tab gives you an overview of all the tags that have been connected to the server. Tags have a green/red/yellow colour indication for being on- or offline or in standstill mode. Since the tags operate on batteries, it is important to keep an eye on the battery level to avoid data loss during tracking. For 2D positioning, you must define the fixed height of the tag, which should be as close to the real height of the tag as possible. Each tag has a configurable update rate. The highest update rate available in the Eliko RTLS Manager is 10 times per second
(10 Hz), while the lowest is once per min-
ute. It is possible to select update rates as high as 150 times per second (150 Hz) by using the Eliko RTLSS Communication Protocol. Contact ELIKO to receive the PDF version of this document or find it under the System/Documentation tab. You can also use the option for dynamic update interval, which is useful when the tracked object is occasionally stationary. The location data is received with high update interval while the tag is moving, and when it stays stationary it will reduce the update rate to the level of low update interval. High update interval can only be smaller or equal to low update interval. Offline tags show the date and time of when the last coordinate was calculated. Also, the system saves and displays the tags last position before going offline on the dashboard, which can be useful for locat-
ing the tag. 14 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee Figure 11. View of the tags list. d. Dashboard The dashboard is a visualisation tool where you can see all of the tags moving in real time. Here you can also see if the anchors are placed correctly relative to the floor-
plan. Different options allow you to display all devices or, for example, only online de-
vices. Default screen refresh rate is 10 Hz. You can use the dashboard to verify the positioning accuracy of the Eliko RTLS sys-
tem. For example, walk through the tracking area to make sure the physical location of the tag matches the displayed location on the floorplan. Information about every de-
vice is shown while clicking on the icons on the map. The system displays the devices serial number, alias (for tags), battery lev-
el (for tags) and current coordinate. Figure 12. Visualisation options for the dashboard. 15 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee 8. CLIENT SOFTWARE INTEGRATION The Eliko RTLS Server communicates with external parties via TCP ports. It can act both as a TCP server or a client. The Eliko RTLS Server is always listening for incoming TCP connection requests on port 25025. You can use the Eliko RTLS Servers IP address and port 25025 to create a connection to the Eliko RTLS Server from your own appli-
cation. You can then configure the Eliko RTLS from your own application, as well as to get live positioning data. Alternatively, the Eliko RTLS Server can instead act as a 9. TURNING OFF THE SYSTEM TCP client and connect to your server. For that, go to the System/General Settings tab on the Eliko RTLS Manager and select the IP address and TCP port your server is listening from. Additional instructions on how to integrate the Eliko RTLS to your own application can be found under the System/Documenta-
tion tab in the Eliko RTLS Manager. Do not unplug the server directly from the mains power because it can possibly corrupt the file system. To power down, use the on/
off button on the server. After the server power indicator light has turned off, it is safe to unplug the devices. NOTICE:
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that may cause undesired operation. NOTICE:
Changes or modifications made to this equipment not expressly approved by Eliko may void the FCC authorization to operate this equipment. NOTICE:
The range of the devices may be negatively affected by devices operating at the same wavelenght. NOTICE:
According to FCC rules, the anchors may only be operated indoors. Operation outdoors is in violation of 47 U.S.C. 301 and could subject the operator to serious legal penal-
ties. 16 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee NOTICE:
This equipment has been tested and found to comply with the limits for a Class B digi-
tal device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help. NOTICE:
FCC Regulations 15.521 Techical Requirements Applicable for All UWB Devices.
(a) UWB devices may not be employed for the operation of toys. Operation onboard an aircraft, a ship or a satellite is prohibited. Date Version
(Version.Revision) Edited By Description of Change 12.10.2020 20201012_1 07.07.2021 20210707_2 T. Pikkmaa T. Pikkmaa Initial document Revision 17 Aiandi 13/1 | Tallinn 12918 | EstoniaTel: +372 6599 881 | support@eliko.ee | www.eliko.ee
1 2 3 4 | ID Label Location Info | ID Label/Location Info | 285.02 KiB | April 29 2022 / June 03 2022 |
Label info and label location for Eliko TAG Idnentification label is located on backside of device and contains following information:
1. M/N: modelnumber 2. PWR(USB): Average current consumption from USB port 3. BATTERY: information about internal battery 4. FCC ID: Federal Communications Commission identification number 5. BARCODE: CODE128 barcode containing device serial number 6. S/N: Device serial number in hexadecimal (numbers 0-9 and letters A-F) Figure 1 Example of label Figure 2 Label location on product
1 2 3 4 | 2.911 Attestation Letter | Attestation Statements | 55.61 KiB | January 17 2024 |
Certification Attestation Sta 47 CFR section 2.911(d)(5)(i) Attestation Statement ant mu 47 CFR section 2.911(d)(5)(ii) Attestation Statement i cin httos://www.fec.gov/supplych: overedlist intodeliko.ee Ajandi 13/1, 12918 Tallinn, Estonia Date: November 29, 2023 tements Attn:
Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 USA ELIKO Tehnoloog a Arenduskeskus OU (the applicant) certifies that, as of the date of the filing of this application, the applicant is not identified on the as an entity produ covered equipment. Thank you, Signature Name Indrek uiso Title CEO Company ELIKO Tehnoloogia Arenduskeskus OU Tel # +372 5088791 To Whom It May Concern:
ELIKO Tehnoloogia Arenduskeskus OU certifies that as of the date of the application the equipment for which authorization is sought is not covered equipment prohibited from receiving an equipment authorization pursuant to section 2.903 of the FCC rules. If the equipment for which the applicant seeks authorization is produced by any of he entities identified on the current , including affiliates or subsidiaries of the named companies, the applic st include an explanation on why the equipment is not covered equipment. Covered List Covered List i
- The Commissions is published by the Public Safety and Homeland Security Bureau and posted on the Commissions website. This Covered List, which is periodically updated, identifies particular equipment, produced by particular entities, that constitutes covered equipment. 2 Letters should be placed on appropriate letterhead Covered List SENSING THE FUTURE
1 2 3 4 | 2.911 Attestation Letter Agent Authorization Agreement | Attestation Statements | 952.43 KiB | January 17 2024 |
U.S. Agent Designation for Service of Process ATTENTION:
Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 USA REGARDING: FCC Certification Section 2.911(d)(7) Information Designated U.S. Agent Company Name: Approve-IT, Inc. Contact Name: Nathan Grinager Street Address: 8011 34th Ave South, Suite 342 City/Province/Zip: Bloomington, MN 55425 Telephone No: 651-247-1678 Email: team@approve-it.net FRN #: 0027533835 This letter is to confirm that we (the Designated U.S. Agent) have accepted the responsibility to act as the Designated U.S. Agent for Service of Process as required by section 47 CFR 2.911(d)(7) on behalf of the Applicant noted below. U.S. Agent Signature:
Date:
Signed by (Printed Name/Title): Nathan Grinager / Co-President
*This letter is valid indefinitely for all applications submitted within the period of 11/29/2023 11/29/2024. The Applicant confirms its explicit consent and acknowledges that they must maintain an agent for no less than one year after terminating all marketing and importation OR the conclusion of any Commission-
related proceeding involving the equipment. The applicant further acknowledges their responsibility to inform the FCC whenever the Designated U.S. Agent information above changes. Applicant Company name: ELIKO Tehnoloogia Arenduskeskus OU Grantee FRN: 0024908154 FCC ID: 2AF2I-TAG Contact Name: Indrek Ruiso Street Address: Aiandi 13/1 City/Province/Zip: Tallinn, 12918 Telephone No:+3725088791 Email:Indrek.ruiso@eliko.ee Applicant Signature:
Date:
Signed by (Printed Name/Title): Indrek Ruiso Document Ref: 8SAV9-4BDZS-BAWYG-FZTRQ Page 1 of 1 12.05.202312.06.2023 Signature Certificate Reference number: 8SAV9-4BDZS-BAWYG-FZTRQ Signer Timestamp Signature Indrek Ruiso Email: indrek.ruiso@eliko.ee Sent:
Viewed:
Signed:
01 Dec 2023 09:09:43 UTC 05 Dec 2023 15:13:47 UTC 05 Dec 2023 15:14:06 UTC Recipient Verification:
Email verified 05 Dec 2023 15:13:47 UTC IP address: 90.190.98.174 Location: Tallinn, Estonia Nathan Grinager Email: ngrinager@approve-it.net Sent:
Viewed:
Signed:
01 Dec 2023 09:09:43 UTC 05 Dec 2023 17:30:21 UTC 06 Dec 2023 14:20:22 UTC Recipient Verification:
Email verified 05 Dec 2023 17:30:21 UTC IP address: 75.72.140.220 Location: Plymouth, United States Document completed by all parties on:
06 Dec 2023 14:20:22 UTC Page 1 of 1 Signed with PandaDoc PandaDoc is a document workflow and certified eSignature solution trusted by 50,000+ companies worldwide.
1 2 3 4 | Confidentiality Request | Cover Letter(s) | 55.82 KiB | January 17 2024 |
EN |
mis CO FID TAL TY REQUES for Certification Service in USA Federal Communication Commission Equipment Authorization Division, Application Processing Branch 7435 Oakland Mills Road Columbia, MD 21048 2023/ 12/12 TO WHOM IT MAY CONCERN Pursuant to Paragraphs 0.457 and 0.459 of the Commissions Rules (47 C.F.R.) and Section 552(b) (4) of the Freedom of information Act, we requests confidentiality for the following products:
FCC ID 2AF2I-TAG Model name KT5D34UB For the product stated above, we request that the following information be held confidentia we Long-Term Short-Term Exhibits Confidentiality Confidentiality External Photos Internal Photos Block Diagram Schematics Test Setup Photos Users Manual Parts List Tune Up Operational Description The long-term confidentiality exhibits contain our trade secrets and proprietary information that could be of benefit to our competitors. The short-term confidentiality on the basis of ensuring that business sensitive information remains confidential until the actual marketing of our new device, which is planned for 2024/04/01 If you have any uestions, please feel free to contact me at the address shown below Sincerely, Name /Titl ndrek Ruiso Company: KO Tehnoloogia Arenduskeskus OU Address: Aiandi 13/1, Tallinn, 12918, Estonia Phone: +372 50 88791 E-Mail: Indrek.ruiso@eliko.ee
1 2 3 4 | Permissive Change Letter | Cover Letter(s) | 244.92 KiB | January 17 2024 |
infodeliko.ee e eluiko Aiandi 13/1, 12918 Tallinn, Estonia 17. Jan 2024 Federal Communication Commission Equipment Authorization Division, Application Processing Branch 7435 Oakland Mills Road Columbia, MD 21048 PCII Request Eliko Tag, FCC ID: 2AF2I-TAG granted on 6. Feb 2022 TO WHOM IT MAY CONCERN Pursuant to CFR 2.1043, Eliko Tehnoloogia Arenduskeskus hereby requests a Permissive Change Class II. Reason:
Add UWB radio channel 5 operation. Modifications:
- Changes in firmware configuration to enable channel 5 operation
- no hardware changes
- no modification in the housing The following new exhibits will be uploaded:
- Test report on radiated measurements for Channel 5 operation
- RF Exposure Info for Channel 5 operation
- External Photos, ... Indrek Ruiso CEO Eliko Tehnoloogia Arenduskeskus Aiandi 13/1, Tallinn 12918, Estonia info@eliko.ee
1 2 3 4 | FCC Confidentiality Request | Cover Letter(s) | 246.25 KiB | April 29 2022 / June 03 2022 |
CONFIDENTIALITY REQUEST for Certification Service in USA Federal Communication Commission Equipment Authorization Division, Application Processing Branch 7435 Oakland Mills Road Columbia, MD 21048 March 16, 2022 TO WHOM IT MAY CONCERN Pursuant to Paragraphs 0.457 and 0.459 of the Commissions Rules (47 C.F.R.) and Section 552(b) (4) of the Freedom of Information Act, we requests confidentiality for the following products:
FCC ID Model name 2AF2I-TAG ELIKO TAG For the product stated above, we request that the following information be held confidential;
a Long-Term Exhibits Confidentiality Block Diagram x Schematics Kl Operational Description xX!
The long-term confidentiality exhibits contain our trade secrets and proprietary information that could be of benefit to our competitors. If you have any questions, please feel free to contact me at the address shown below. Sincerely, Ruiso Tehnoloogia Arenduskeskus OU ess: Aiandi 13/1, 12918 Tallinn, Estonia Phone: +372 6599 881 E-Mail: info@eliko.ee
1 2 3 4 | Test Setup Photos - UWB revised | Test Setup Photos | 595.23 KiB | May 20 2022 / June 02 2022 |
1 2 3 4 | Test report UWB - ext photos revised | Test Report | 1.05 MiB | May 20 2022 / June 02 2022 |
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2024-01-17 | 6144.9 ~ 6833.6 | UWB - Ultra Wideband Transmitter | Class II Permissive Change |
2 | JAB - Part 15 Class B Digital Device | |||
3 | 2022-06-03 | JAB - Part 15 Class B Digital Device | Original Equipment | |
4 | 2022-06-02 | 3677.9 ~ 4338.4 | UWB - Ultra Wideband Transmitter |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 3 4 | Effective |
2024-01-17
|
||||
1 2 3 4 |
2022-06-03
|
|||||
1 2 3 4 |
2022-06-02
|
|||||
1 2 3 4 | Applicant's complete, legal business name |
Eliko Tehnoloogia Arenduskeskus
|
||||
1 2 3 4 | FCC Registration Number (FRN) |
0024908154
|
||||
1 2 3 4 | Physical Address |
Aiandi 13/1
|
||||
1 2 3 4 |
Tallinn, N/A
|
|||||
1 2 3 4 |
Estonia
|
|||||
app s | TCB Information | |||||
1 2 3 4 | TCB Application Email Address |
t******@cetecom.com
|
||||
1 2 3 4 |
t******@cetecom.com
|
|||||
1 2 3 4 | TCB Scope |
A2: Low Power Transmitters (except Spread Spectrum) and radar detectors operating above 1 GHz
|
||||
1 2 3 4 |
A1: Low Power Transmitters below 1 GHz (except Spread Spectrum), Unintentional Radiators, EAS (Part 11) & Consumer ISM devices
|
|||||
app s | FCC ID | |||||
1 2 3 4 | Grantee Code |
2AF2I
|
||||
1 2 3 4 | Equipment Product Code |
TAG
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 3 4 | Name |
I******** R******
|
||||
1 2 3 4 | Title |
CEO
|
||||
1 2 3 4 | Telephone Number |
+3726********
|
||||
1 2 3 4 | Fax Number |
+372 ********
|
||||
1 2 3 4 |
i******@eliko.ee
|
|||||
app s | Technical Contact | |||||
n/a | ||||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 2 3 4 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 3 4 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 3 4 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 3 4 | Equipment Class | UWB - Ultra Wideband Transmitter | ||||
1 2 3 4 | JAB - Part 15 Class B Digital Device | |||||
1 2 3 4 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Trackable tag for indoor positioning system | ||||
1 2 3 4 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 3 4 | Yes | |||||
1 2 3 4 | Modular Equipment Type | Does not apply | ||||
1 2 3 4 | Purpose / Application is for | Class II Permissive Change | ||||
1 2 3 4 | Original Equipment | |||||
1 2 3 4 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | Yes | ||||
1 2 3 4 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 3 4 | Grant Comments | Output Power listed is Peak EIRP. End-users and installers must be provided with installation instructions and transmitter operating conditions for satisfying RF exposure compliance. This device is certified for mobile use. C2PC change to add channel 5. | ||||
1 2 3 4 | C2PC change to add channel 5 to the UWB part. | |||||
1 2 3 4 | Output Power listed is Peak EIRP. Antennas mounted on outdoor structures such, as antennas mounted on the outside of a building or on a telephone pole, or any fixed outdoors infrastructure are prohibited for use with this device. | |||||
1 2 3 4 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 3 4 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 3 4 | Firm Name |
cetecom advanced GmbH
|
||||
1 2 3 4 |
CETECOM GmbH
|
|||||
1 2 3 4 | Name |
G******** S****
|
||||
1 2 3 4 |
N******** J********
|
|||||
1 2 3 4 | Telephone Number |
49-68********
|
||||
1 2 3 4 |
+49 2********
|
|||||
1 2 3 4 | Fax Number |
49-68********
|
||||
1 2 3 4 |
+49 2********
|
|||||
1 2 3 4 |
g******@cetecomadvanced.com
|
|||||
1 2 3 4 |
n******@cetecom.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15F | CC | 3677.9 | 4338.4 | 0.00028 | |||||||||||||||||||||||||||||||||||
1 | 2 | 15F | CC | 6144.9 | 6833.6 | 0.00073 | |||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 15B | CC | ||||||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
3 | 1 | 15B | CC | ||||||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
4 | 1 | 15F | CC | 3677.90000000 | 4338.40000000 | 0.0002800 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC