Step 3 - Configuring the local base station
The local base station is the one locally hosted on the ThingPark Enterprise All-in-One server.
Setting the antenna gain and cable loss
Set Antenna Gain and Cable loss as per the following table:
| Model | Antenna Gain | Cable loss |
|---|---|---|
| Ufispace pico (external antenna) | 1.5 dBi | 0 dB |
| Ufispace enterprise (internal antenna) | 1.4 dBi | 0 dB |
| Ufispace macro v1.5 & Browan Outdoor Micro (ODU) | Depends on antenna model | Typically ~ 0.5 dB but depends on installation |
| Milesight UG65 | 0 dBi | 0 dB |
| Milesight UG67 | Depends on antenna model | Typically ~ 0.5 dB but depends on installation |
| Kerlink iFemtoCell | 3 dBi | 0.5 dB |
| Kerlink iFemtoEvo | 3 dBi | 0.5 dB |
| Kerlink iStation | Depends on antenna model | Typically ~ 0.5 dB but depends on installation |
| Browan Indoor Femto | 0 dBi | 0 dB |
Configuring network interfaces
Starting version 2.4.1, the network configuration of the base station is directly managed from TAO's user interface.
From the Network Interface Configuration widget, click CHANGE CONFIGURATION to update the network interface settings.
You may configure up to two network interfaces on each base station.
For each interface, depending on its type, you should fill the requested
information. Mandatory fields are marked with *.
- Primary interface: as long as this interface is up-and-running, it is used by TAO to send data to external applications.
- Secondary interface: this is a rescue interface, used to send data to external applications only while the primary interface is down.
To remotely access TPE All-in-One user interface, you need a routable IP address regardless of whether it is configured as primary or secondary. This is guaranteed by ethernet and Wi-Fi types of connectivity but is not generally supported by conventional cellular connectivity.
When two interfaces are configured, TAO supports automatic failover/failback between primary and secondary interfaces. In order to automatically detect any failure on the primary interface and switchover to the secondary one, TAO relies on ICMP protocol to regularly ping one or several configurable destinations and validate the health state of each interface.
Use the PING button to verify that TAO can successfully access your ICMP destinations. Each unreachable destination is marked in red, as per the following example:
Once you are done updating the network configuration, click SAVE at the bottom of the widget.
Setting time configuration
Time synchronization is important to properly timestamp the LoRaWAN packets when they are displayed on the user interface or sent to application servers.
This time synchronization is typically fulfilled through the NTP protocol. For this, your base station must communicate with one or several NTP servers.
Follow these steps if you want to configure your base station to use NTP:
- Activate the use of NTP feature, by switching ON Use NTP server.
- Set one or several NTP servers (you may setup up to four servers).
If your deployment environment does not have access to any NTP server, you may disable
NTP and manually set the date/time from the user interface through the 
button.
Obviously, the base station's internal clock will drift over time, therefore, it is recommended to manually resynchronize the time every month or after each base station reboot.
For either mode (NTP is used or not), do not forget to set the timezone of your deployment in the Timezone field.