GPS signal is handled by the kgpsd daemon. By default, this daemon sends the received nmea frames to both virtual ports /dev/nmea1 and /dev/nmea2. Once a program reads a line from a virtual port, this line is deleted. Thus, only one program should read a virtual port at a time.

By default, the packet forwarder reads the /dev/nmea1 virtual port.

The number of virtual ports can be increased using the /etc/kgpsd.conf configuration file.

To determine whether GPS signal is properly received, NMEA sentences can be monitored using the following command:

cat /dev/nmea2
# ctrl-c to exit 

The GGA sentences contain 2 fields that indicate the quality of the GPS signal.

• The number of satellites being tracked. To calculate coordinates at least 4 satellites are required. If less than 4 satellites are being received, then 0 is always written. A maximum of 12 satellites can be received at the same time.
• The fix quality. Receiving 4 satellites is not enough, a few sets of data are required to calculate coordinates. This sets of data can belong to receive (up to 15 minutes the first time). When the fix quality is equal to 1, it means the data is valid.

Example of correct GGA sentence:

$GNGGA,194640.00,4530.70229,N,00914.26728,E,1,12,4.31,184.9,M,47.1,M,,*41

In this example, the fix quality is OK (1) and 12 satellites are received.

Examples of bad GGA sentence:

• Frames like the one below, indicates that not enough satellites are received.

$GNGGA,152451.00,,,,,0,00,99.99,,,,,,*7E

• Frames like the one below, indicates that the set of data is not valid.

$GNGGA,163411.00,,,,,0,04,24.77,,,,,,*7A

In case the number of received satellites is small, the value of the field fixed_altitude in the /etc/kgpsd.conf configuration file can be set to yes.

# 2D/3D Altitude management
fixed_altitude=yes

It will result in losing the altitude, however, only 3 satellites will be necessary to receive correct frames.

• Some NMEA frames contain UTC time.
• GPS possesses two signal features:
  1. PPS (Pulse per second) feature: It sends a hardware signal to produce a one-hertz clock. Pulse is produced at the beginning of each second.
  2. TAI offset information: It sends current TAI offset and time of next leap second insertion in UTC time (if any insertion is planned).

KGPSd is the daemon managing hardware GPS component on Wirnet™ iBTS firmware.
KGPSd configuration file is /etc/kgpsd.conf.
Configurations concerning leap second features are:

• leap_second_feature: “yes” means the feature is activated (binary message will be sent sometimes).
• leap_second_file: Filename where information about leap second will be written (each time a correct answer is received from GPS component).
• leap_second_period: When daemon starts, for every 10 seconds, leap second information is checked until it is received.

Example of kgpsd configuration file for this feature:

# Leap second management
## no: no leap second information is given, yes: information given
leap_second_feature=no
## where leap second information is written (this is not directly usable by NTPd)
leap_second_file=/tmp/kgpsd_leap_file.list
## Leap second information is looked for at first GPS fix after daemon start and then after given period
leap_second_period=2592000

To get the temperature inside the Wirnet iBTS CPU use the following command:

cat /sys/class/hwmon/hwmon1/temp1_input

It is necessary to divide the result by 1000 to get the temperature in degrees Celsius (°C).

To get the temperature inside the gateway casing use the following command:

• Wirnet iBTS:

  cat /sys/class/hwmon/hwmon0/temp1_input

• Wirnet iFemtoCell:

  cat /sys/class/hwmon/hwmon0/temp1_input

It is necessary to divide the result by 1000 to get the temperature in degrees Celsius (°C).

A light sensor can be used to know if the Wirnet™ iBTS casing door is opened or closed.
To use the light sensor use the following command:

# echo "0.1000" > /sys/bus/iio/devices/iio\:device2/in_illuminance_integration_time
# cat /sys/bus/iio/devices/iio\:device2/in_illuminance_input 
47.240000 => opened casing
# cat /sys/bus/iio/devices/iio\:device2/in_illuminance_input
0.880000 => closed casing

The three RJ45 connectors (PoE, LOCAL and debug) integrate 2 LEDS, one Green and one Orange.
The behavior of the LEDs is detailed hereafter:

Precision on the DEBUG Orange Led behavior: