| Line 1: |
| - |
[[Image:esl_server_sw_dashboard.png|600px|]]
|
+ |
[[Image:esl_server_sw_dashboard.png|franeless|right|400px|]]
|
| |
=Overview= |
|
=Overview= |
| |
|
+ |
==First Steps==
|
| |
|
+ |
{| class="wikitable" cellpadding="30"
|
| |
|
+ |
|-
|
| |
|
+ |
|<strong> This process should only take approximately 5 minutes and is recommended and free. </strong><br>
|
| |
|
+ |
<br><br>
|
| |
|
+ |
<h2>Registration</h2><br><i>Without a license, the software can only connect to a single base station and can only manage:</i>
|
| |
|
+ |
<ul>
|
| |
|
+ |
<li>20 labels at <= 2.9" screen diameter.</li>
|
| |
|
+ |
<li>3 labels at >= 2.9" screen diameter. </li>
|
| |
|
+ |
</ul>
|
| |
|
|
|
| |
|
+ |
<span style="color:red">If your license has not been activated yet, the ESL server will show a warning in the top left corner. </span><br> To enter the
|
| |
|
+ |
license page, either press on the warning or go to ‘Advanced’ > ‘License’
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|Step 1: After accessing the licensing page click on the blue hyperlink to register. <br><span style="color:green"> <strong> Note the Unique ID boxed in Green.</strong></span><br>Step 2: Click on Sign Up
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|Step 3: Fill out the login page. It should look some thing like this: <br><span style="color:red"> <strong> Notice* the street number is on a different field </strong></span><br>Step 4: Click Register
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|You should see a registration screen that looks like this.
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|Step 5: Click "Confirm My Email Address"
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|An Email Address Confirmation notification should appear.
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|Step 6: Log back into the registration screen and input the Unique ID for your device from Step 1.<br><i>If you don't have it, just repeat step 1 to retrieve it.</i>
|
| |
|
+ |
<br>It should look something like this.
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|Step 7: Click on Request to generate the software key.<br> The software key will be generated below the Request button. <br><i>This may take a few seconds to generate.</i>
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|Step 8: Copy the Generated Key to your clipboard:
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|Step 9: Go back to step 1 and paste the license key and click Confirm}
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|-
|
| |
|
+ |
|You should see the following in a few seconds:
|
| |
|
+ |
|[[Image:not_licensed.png|500px|]]
|
| |
|
+ |
|}
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
=Activation= |
|
=Activation= |
| - |
To reactivate these ESLs place them nearby the connected Base Station and go to ESLs > Reactivate ESLs
|
+ |
{| class="wikitable" cellpadding="30"
|
| - |
Select the Base Station and variant, supply the address range and press ‘Start’
|
+ |
|-
|
| - |
After pressing this button, to number of ESLs that have been reactivated so far will be shown.
|
+ |
|<h3>Deactivated ESL Tag</h3>
|
| - |
Since the ESLs will only wake-up for a split second every few minutes, it can take more than 15 minutes before all
|
+ |
| [[Image:deactivated_esl_tag.png|200px|]]
|
| - |
ESLs have been successfully reactivated. You can verify this by checking whether the ‘DEACTIVATED’ message has
|
+ |
|
|
| - |
disappeared from the screen. `
|
+ |
|-
|
| |
|
+ |
|<h3>Reactivation Process</h3>
|
| |
|
+ |
|[[Image:reactivation_screen.png|400px|]]
|
| |
|
+ |
|To reactivate these ESLs place them nearby the connected Base Station and go to<strong> ESLs > Reactivate ESLs </strong> <br>Select the Base Station and variant, supply the address range and press ‘Start’
|
| |
|
+ |
|}
|
| |
|
|
|
| |
|
+ |
After pressing this button, the number of ESLs that have been reactivated so far will be shown. Since the ESLs will only wake-up for a split second every few minutes, it can take more than 15 minutes before all
|
| |
|
+ |
ESLs have been successfully reactivated. You can verify this by checking whether the ‘DEACTIVATED’ message has disappeared from the screen.
|
| |
|
|
|
| |
Active ESLs will be periodically search for a Base Station, so as soon as a Base Station is within range, they will |
|
Active ESLs will be periodically search for a Base Station, so as soon as a Base Station is within range, they will |
| - |
associate with it and start sending data requests and status information to it. When a Base Station is turned off or an
|
+ |
associate with it and start sending data requests and status information to it.
|
| - |
ESL is moved out of range, an ESL will time out after a couple of minutes and starts seeking for another Base Station
|
|
|
| - |
in range. See chapter 6.1.3 Action dropdown for more information about configuring ESLs.
|
|
|
| - |
It might be possible that even though the ESLs are working properly, they still don’t connect to the Base Station. This
|
|
|
| - |
might be caused by strong interference on the default RF-channel of the Base Station. To resolve this problem, see
|
|
|
| - |
chapter 5.4 Energy scan.
|
|
|
| |
|
|
|
| |
|
+ |
When a Base Station is turned off or an ESL is moved out of range, an ESL will time out after a couple of minutes and starts seeking for another Base Station
|
| |
|
+ |
in range.
|
| |
|
+ |
<i>See chapter 6.1.3 Action dropdown for more information about configuring ESLs.</i>
|
| |
|
+ |
<br>
|
| |
|
|
|
| |
|
+ |
It might be possible that even though the ESLs are working properly, they still don’t connect to the Base Station.
|
| |
|
+ |
This might be caused by strong interference on the default RF-channel of the Base Station.
|
| |
|
+ |
<i>To resolve this problem, see chapter 5.4 Energy scan.</i>
|
| |
|
|
|
| |
=Dashboard= |
|
=Dashboard= |
| |
|
|
|
| |
|
+ |
[[Image:dashboard_4.png|600px|]]
|
| |
|
+ |
<br>
|
| |
The dashboard is the main page of the ESL Web Server, which gives you a quick impression on the status of the ESL |
|
The dashboard is the main page of the ESL Web Server, which gives you a quick impression on the status of the ESL |
| |
system. |
|
system. |
| - |
If everything is fine, all tiles are green.
|
+ |
<br>
|
| - |
If there is a warning a tile turns orange
|
+ |
====<span style="color:green"> If everything is fine, all tiles are GREEN </span>.====
|
| - |
If there’s an error, then a tile turns red.
|
|
|
| |
|
|
|
| - |
Figure 11: Dashboard overview tiles
|
+ |
====<span style="color:orange"> If there is a warning a tile turns ORANGE</span>.====
|
| |
|
|
|
| |
|
+ |
====<span style="color:red"> If there’s an error, then a tile turns RED.</span>====
|
| |
|
|
|
| |
|
|
|
| |
In total there are 4 groups that can change status: ESLs, Base Stations, Database and Links. |
|
In total there are 4 groups that can change status: ESLs, Base Stations, Database and Links. |
| |
===ESL=== |
|
===ESL=== |
| Line 29: |
| |
|
|
|
| |
|
+ |
[[Image:dashboard_8.png|600px|]]
|
| |
====Link status====Shows how many ESLs have been linked and how many active ESLs are not linked. |
|
====Link status====Shows how many ESLs have been linked and how many active ESLs are not linked. |
| |
|
|
|
| |
====Connection status====Shows the connection status of all ESLs that have been linked, which can be good, poor and |
|
====Connection status====Shows the connection status of all ESLs that have been linked, which can be good, poor and |
| |
disconnected. |
|
disconnected. |
| |
|
|
|
| |
====Image status====Shows how many ESLs are showing the latest image, how many are still busy updating the image and |
|
====Image status====Shows how many ESLs are showing the latest image, how many are still busy updating the image and |
| |
how many failed to update (i.e. due to being disconnected or due to a hardware failure). |
|
how many failed to update (i.e. due to being disconnected or due to a hardware failure). |
