31,703
edits
Changes
Template:Networking rut manual gps (view source)
Revision as of 13:42, 30 July 2019
, 13:42, 30 July 2019Created page with "==Summary== The <b>Global Positioning System</b> (<b>GPS</b>) is a space-based radionavigation system. This chapter is an overview of the GPS service in {{{name}}} routers...."
==Summary==
The <b>Global Positioning System</b> (<b>GPS</b>) is a space-based radionavigation system. This chapter is an overview of the GPS service in {{{name}}} routers.
==Map==
The <b>Map</b> page displays the device's current coordinates and position on the map. To see the device's location on the map, make sure to attach the GPS antenna on the router and enable GPS in the [[{{{name}}}_GPS#General|General]] page.
The figure below is an example of the Map page:
[[File:{{{file_map}}}]]
==General==
The <b>General</b> is used to enable the GPS service and the support for different types satellites. Once you turn on GPS, you can check the [[{{{name}}}_GPS#Map|Map]] page in order to see if the router has obtained a GPS fix. It is very important to attach the GPS antenna on the router and place it outside (not inside of a building). The router will not be likely to obtain a GPS fix otherwise.
The figure below is an example of the General page and the table below provides information on the fields contained in that page:
[[File:{{{file_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the GPS service ON or OFF</td>
</tr>
<tr>
<td>Galileo NMEA support<span class="asterisk">*</span></td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns support for Galileo satellites ON or OFF</td>
</tr>
<tr>
<td>Glonass NMEA support<span class="asterisk">*</span></td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns support for Glonass satellites ON or OFF</td>
</tr>
<tr>
<td>BeiDou NMEA support<span class="asterisk">*</span></td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns support for BeiDou satellites ON or OFF</td>
</tr>
</table>
<span class="asterisk">*</span>Changing these options requires a modem reboot. Therefore, if you make changes to these options and save them, the router will lose cellular connectivity for about 30 seconds.
==NMEA==
The <b>NMEA</b> page is used to configure settings related to NMEA sentence collecting and forwarding.
===NMEA forwarding===
----
The <b>NMEA forwarding</b> section is used to configure and enable NMEA forwarding. The figure below is an example of the NMEA forwarding section and the table below provides information on the fields contained in that section:
[[File:{{{file_nmea_forwarding}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns NMEA forwarding ON or OFF</td>
</tr>
<tr>
<td>Hostname</td>
<td>ip | host; Default: <b>192.168.1.5</b></td>
<td>IP address or hostname of the server to which NMEA data will be forwarded to</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; Default: <b>8500</b></td>
<td>Port number to which NMEA data will be forwarded to</td>
</tr>
<tr>
<td>Protoocl</td>
<td>TCP | UDP; Default: <b>TCP</b></td>
<td>Protocol that will be used to send NMEA data</td>
</tr>
</table>
===NMEA forwarding cache===
----
The router <b>caches NMEA forwarding</b> information if NMEA forwarding is enabled. This section is used to select the memory type where the cache will be stored and the maximum amount of data that will be saved:
[[File:{{{file_nmea_cache}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Type</td>
<td>ram | flash; Default: <b>ram</b></td>
<td>Selects which type of memory will be used for storing NMEA forwarding cache</td>
</tr>
<tr>
<td>Maximum sentences</td>
<td>integer; Default: <b>5000</b></td>
<td>Maximum amount of NMEA sentences that will be saved in the cache before older entries are replaced by new ones</td>
</tr>
<tr>
<td>File</td>
<td>filepath; default: <b>none</b></td>
<td>Location of the file where NMEA forwarding cache information will be stored. This field becomes visible only when the selected memory type is "flash"</td>
</tr>
</table>
===NMEA collecting===
----
The <b>NMEA collecting</b> section is used to enable NMEA sentence gathering and storing. The figure below is an example of the NMEA collecting section and the table below provides information on the fields contained in that section:
[[File:{{{file_nmea_collecting}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns NMEA sentence collecting ON or OFF</td>
</tr>
<tr>
<td>Location</td>
<td>filepath; Default: <b>none</b></td>
<td>Location of the file where NMEA sentences will be stored. This field becomes visible only when NMEA collecting is enabled</td>
</tr>
</table>
===NMEA sentence settings===
----
The <b>NMEA sentence settings</b> section provides the possibility to configure which NMEA sentences will be forwarded or collected and at what frequency. The figure below is an example of the NMEA sentence settings section and the table below provides information on the fields contained in that section:
[[File:{{{file_nmea_sentence}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Forwarding enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Enables forwarding for selected NMEA sentence</td>
</tr>
<tr>
<td>Forwarding interval</td>
<td>integer; Default: <b>5</b></td>
<td>NMEA sentence forwarding frequency in seconds</td>
</tr>
<tr>
<td>Collecting enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Enables collecting for selected NMEA sentences</td>
</tr>
<tr>
<td>Collecting interval</td>
<td>integer; Default: <b>5</b></td>
<td>NMEA sentence collecting frequency in seconds</td>
</tr>
</table>
<br>
<b>NMEA sentence refference table</b>:
<table class="nd-othertables_3">
<tr>
<th width=250>NMEA sentence name</th>
<th width=902>Description</th>
</tr>
<tr>
<td><b>GPGSV</b></td>
<td>Number of GPS satellites in view</td>
</tr>
<tr>
<td><b>GPGGA</b></td>
<td>GPS fix data</td>
</tr>
<tr>
<td><b>GPVTG</b></td>
<td>Track made good and speed relative to the ground</td>
</tr>
<tr>
<td><b>GPRMC</b></td>
<td>Recommended minimum specific GPS/Transit data</td>
</tr>
<tr>
<td><b>GPGSA</b></td>
<td>GPS DOP and active satellites</td>
</tr>
<tr>
<td><b>GLGSA</b></td>
<td>GLONASS DOP and active satellites</td>
</tr>
<tr>
<td><b>GLGSV</b></td>
<td>Number of GLONASS satellites in view</td>
</tr>
<tr>
<td><b>GNGNS</b></td>
<td>GNSS position fix from more than one constellation (e.g., GPS + GLONASS)</td>
</tr>
<tr>
<td><b>GAGSV</b></td>
<td>Number of Galileo satelites in view</td>
</tr>
<tr>
<td><b>PQGSV</b></td>
<td>Detailed satellite data (used in BeiDou sentences)</td>
</tr>
<tr>
<td><b>PQGSA</b></td>
<td>Overall satellite data (used in BeiDou sentences)</td>
</tr>
</table>
==HTTPS==
The <b>HTTPS</b> page can be used to configure data sending to an HTTP(S) server.
===HTTPS/HTTP Server Settings===
----
The <b>HTTPS/HTTP Server Settings</b> section is used to enable GPS data sending to an HTTP or HTTPS server:
[[File:{{{file_https_settings}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns data sending to HTTP/HTTPS ON or OFF</td>
</tr>
<tr>
<td>URL</td>
<td>ip | host; Default: <b>192.168.1.5</b></td>
<td>IP address or hostname of the HTTP/HTTPS server</td>
</tr>
</table>
===TAVL Settings===
----
The <b>TAVL Settings</b> section is used to select which data will be sent to the TAVL server:
[[File:{{{file_tavl_settings}}}]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Send GSM signal</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes GSM signal strength information in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send analog input</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes analog input state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (1)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #1 state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (2)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #2 state in GPS data package to be sent to server</td>
</tr>
</table>
==AVL==
The <b>AVL</b> page is used to set up GPS data sending to an AVL server.
===AVL Server Settings===
----
The <b>AVL Server Settings</b> section is used to configure the main parameters of data sending to an AVL server. The figure below is an example of the AVL Server Settings section and the table below provides information on the fields contained in that section:
[[File:{{{file_avl_settings}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns data sending to AVL server ON or OFF</td>
</tr>
<tr>
<td>Hostname</td>
<td>ip | host; Default: <b>192.168.1.5</b></td>
<td>IP address or hostname of the AVL server</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; Default: <b>8500</b></td>
<td>Port number of the AVL server to which router will be connecting to</td>
</tr>
<tr>
<td>Protoocl</td>
<td>TCP | UDP; Default: <b>TCP</b></td>
<td>Protocol that will be used for communication with the AVL server</td>
</tr>
</table>
===Main rule===
----
[[File:{{{file_main_rule}}}]]
===Secondary Rules===
----
[[File:{{{file_secondary_rules}}}]]
===GPS Configuration===
----
[[File:{{{file_gps_configuration}}}]]
===TAVL Settings===
----
The <b>TAVL Settings</b> section is used to select which data will be sent to the TAVL server:
[[File:{{{file_tavl_settings}}}]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Send GSM signal</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes GSM signal strength information in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send analog input</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes analog input state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (1)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #1 state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (2)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #2 state in GPS data package to be sent to server</td>
</tr>
</table>
==GPS Geofencing==
A <b>geofence</b> is a virtually defined boundary for a real-world geographic area. The GPS Geofencing page provides you with the possibility to set this custom area and apply rules that will inform you when the device leaves or enters the geofence.
[[File:{{{file_geofencing_add}}}]]
The figure below is an example of GPS Geofencing configuration and the table below provides information related to that configuration:
[[File:{{{file_geofencing_details}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the Geofence rule ON or OFF</td>
</tr>
<tr>
<td>Longitude (X)</td>
<td>degrees [-180.000000..180.000000]; Default: <b>0.000000</b></td>
<td>East-west position of a point on the Earth's surface. Combining this and the Latitude information will produce a point on the world map that will serve as the center of the geofence area</td>
</tr>
<tr>
<td>Latitude (Y)</td>
<td>degrees [-90.000000..90.000000]; Default: <b>0.000000</b></td>
<td>North-south position of a point on the Earth's surface. Combining this and the Longitude information will produce a point on the world map that will serve as the center of the geofence area</td>
</tr>
<tr>
<td>Radius</td>
<td>integer [1..999999]; Default: <b>200</b></td>
<td>Radius (in meters) of the geofence area</td>
</tr>
<tr>
<td>Generate event on</td>
<td>Exit | Enter | Enter/Exit; Default: <b>Exit</b></td>
<td>Specifies whether the rule should be triggered when the device enters the geofence area, leaves it or on both events</td>
</tr>
<tr>
<td>Get current coordinates</td>
<td>- (interactive button)</td>
<td>Obtains the device's current coordinates and places them in the Longitude and Latitude fields</td>
</tr>
</table>
==See also==
<ul>
<li>[[{{{name}}}_Protocols|{{{name}}} GPS protocols]]</li>
</ul>
[[Category:{{{name}}} WebUI]]
The <b>Global Positioning System</b> (<b>GPS</b>) is a space-based radionavigation system. This chapter is an overview of the GPS service in {{{name}}} routers.
==Map==
The <b>Map</b> page displays the device's current coordinates and position on the map. To see the device's location on the map, make sure to attach the GPS antenna on the router and enable GPS in the [[{{{name}}}_GPS#General|General]] page.
The figure below is an example of the Map page:
[[File:{{{file_map}}}]]
==General==
The <b>General</b> is used to enable the GPS service and the support for different types satellites. Once you turn on GPS, you can check the [[{{{name}}}_GPS#Map|Map]] page in order to see if the router has obtained a GPS fix. It is very important to attach the GPS antenna on the router and place it outside (not inside of a building). The router will not be likely to obtain a GPS fix otherwise.
The figure below is an example of the General page and the table below provides information on the fields contained in that page:
[[File:{{{file_general}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the GPS service ON or OFF</td>
</tr>
<tr>
<td>Galileo NMEA support<span class="asterisk">*</span></td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns support for Galileo satellites ON or OFF</td>
</tr>
<tr>
<td>Glonass NMEA support<span class="asterisk">*</span></td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns support for Glonass satellites ON or OFF</td>
</tr>
<tr>
<td>BeiDou NMEA support<span class="asterisk">*</span></td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns support for BeiDou satellites ON or OFF</td>
</tr>
</table>
<span class="asterisk">*</span>Changing these options requires a modem reboot. Therefore, if you make changes to these options and save them, the router will lose cellular connectivity for about 30 seconds.
==NMEA==
The <b>NMEA</b> page is used to configure settings related to NMEA sentence collecting and forwarding.
===NMEA forwarding===
----
The <b>NMEA forwarding</b> section is used to configure and enable NMEA forwarding. The figure below is an example of the NMEA forwarding section and the table below provides information on the fields contained in that section:
[[File:{{{file_nmea_forwarding}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns NMEA forwarding ON or OFF</td>
</tr>
<tr>
<td>Hostname</td>
<td>ip | host; Default: <b>192.168.1.5</b></td>
<td>IP address or hostname of the server to which NMEA data will be forwarded to</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; Default: <b>8500</b></td>
<td>Port number to which NMEA data will be forwarded to</td>
</tr>
<tr>
<td>Protoocl</td>
<td>TCP | UDP; Default: <b>TCP</b></td>
<td>Protocol that will be used to send NMEA data</td>
</tr>
</table>
===NMEA forwarding cache===
----
The router <b>caches NMEA forwarding</b> information if NMEA forwarding is enabled. This section is used to select the memory type where the cache will be stored and the maximum amount of data that will be saved:
[[File:{{{file_nmea_cache}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Type</td>
<td>ram | flash; Default: <b>ram</b></td>
<td>Selects which type of memory will be used for storing NMEA forwarding cache</td>
</tr>
<tr>
<td>Maximum sentences</td>
<td>integer; Default: <b>5000</b></td>
<td>Maximum amount of NMEA sentences that will be saved in the cache before older entries are replaced by new ones</td>
</tr>
<tr>
<td>File</td>
<td>filepath; default: <b>none</b></td>
<td>Location of the file where NMEA forwarding cache information will be stored. This field becomes visible only when the selected memory type is "flash"</td>
</tr>
</table>
===NMEA collecting===
----
The <b>NMEA collecting</b> section is used to enable NMEA sentence gathering and storing. The figure below is an example of the NMEA collecting section and the table below provides information on the fields contained in that section:
[[File:{{{file_nmea_collecting}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns NMEA sentence collecting ON or OFF</td>
</tr>
<tr>
<td>Location</td>
<td>filepath; Default: <b>none</b></td>
<td>Location of the file where NMEA sentences will be stored. This field becomes visible only when NMEA collecting is enabled</td>
</tr>
</table>
===NMEA sentence settings===
----
The <b>NMEA sentence settings</b> section provides the possibility to configure which NMEA sentences will be forwarded or collected and at what frequency. The figure below is an example of the NMEA sentence settings section and the table below provides information on the fields contained in that section:
[[File:{{{file_nmea_sentence}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Forwarding enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Enables forwarding for selected NMEA sentence</td>
</tr>
<tr>
<td>Forwarding interval</td>
<td>integer; Default: <b>5</b></td>
<td>NMEA sentence forwarding frequency in seconds</td>
</tr>
<tr>
<td>Collecting enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Enables collecting for selected NMEA sentences</td>
</tr>
<tr>
<td>Collecting interval</td>
<td>integer; Default: <b>5</b></td>
<td>NMEA sentence collecting frequency in seconds</td>
</tr>
</table>
<br>
<b>NMEA sentence refference table</b>:
<table class="nd-othertables_3">
<tr>
<th width=250>NMEA sentence name</th>
<th width=902>Description</th>
</tr>
<tr>
<td><b>GPGSV</b></td>
<td>Number of GPS satellites in view</td>
</tr>
<tr>
<td><b>GPGGA</b></td>
<td>GPS fix data</td>
</tr>
<tr>
<td><b>GPVTG</b></td>
<td>Track made good and speed relative to the ground</td>
</tr>
<tr>
<td><b>GPRMC</b></td>
<td>Recommended minimum specific GPS/Transit data</td>
</tr>
<tr>
<td><b>GPGSA</b></td>
<td>GPS DOP and active satellites</td>
</tr>
<tr>
<td><b>GLGSA</b></td>
<td>GLONASS DOP and active satellites</td>
</tr>
<tr>
<td><b>GLGSV</b></td>
<td>Number of GLONASS satellites in view</td>
</tr>
<tr>
<td><b>GNGNS</b></td>
<td>GNSS position fix from more than one constellation (e.g., GPS + GLONASS)</td>
</tr>
<tr>
<td><b>GAGSV</b></td>
<td>Number of Galileo satelites in view</td>
</tr>
<tr>
<td><b>PQGSV</b></td>
<td>Detailed satellite data (used in BeiDou sentences)</td>
</tr>
<tr>
<td><b>PQGSA</b></td>
<td>Overall satellite data (used in BeiDou sentences)</td>
</tr>
</table>
==HTTPS==
The <b>HTTPS</b> page can be used to configure data sending to an HTTP(S) server.
===HTTPS/HTTP Server Settings===
----
The <b>HTTPS/HTTP Server Settings</b> section is used to enable GPS data sending to an HTTP or HTTPS server:
[[File:{{{file_https_settings}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns data sending to HTTP/HTTPS ON or OFF</td>
</tr>
<tr>
<td>URL</td>
<td>ip | host; Default: <b>192.168.1.5</b></td>
<td>IP address or hostname of the HTTP/HTTPS server</td>
</tr>
</table>
===TAVL Settings===
----
The <b>TAVL Settings</b> section is used to select which data will be sent to the TAVL server:
[[File:{{{file_tavl_settings}}}]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Send GSM signal</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes GSM signal strength information in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send analog input</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes analog input state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (1)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #1 state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (2)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #2 state in GPS data package to be sent to server</td>
</tr>
</table>
==AVL==
The <b>AVL</b> page is used to set up GPS data sending to an AVL server.
===AVL Server Settings===
----
The <b>AVL Server Settings</b> section is used to configure the main parameters of data sending to an AVL server. The figure below is an example of the AVL Server Settings section and the table below provides information on the fields contained in that section:
[[File:{{{file_avl_settings}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enabled</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns data sending to AVL server ON or OFF</td>
</tr>
<tr>
<td>Hostname</td>
<td>ip | host; Default: <b>192.168.1.5</b></td>
<td>IP address or hostname of the AVL server</td>
</tr>
<tr>
<td>Port</td>
<td>integer [0..65535]; Default: <b>8500</b></td>
<td>Port number of the AVL server to which router will be connecting to</td>
</tr>
<tr>
<td>Protoocl</td>
<td>TCP | UDP; Default: <b>TCP</b></td>
<td>Protocol that will be used for communication with the AVL server</td>
</tr>
</table>
===Main rule===
----
[[File:{{{file_main_rule}}}]]
===Secondary Rules===
----
[[File:{{{file_secondary_rules}}}]]
===GPS Configuration===
----
[[File:{{{file_gps_configuration}}}]]
===TAVL Settings===
----
The <b>TAVL Settings</b> section is used to select which data will be sent to the TAVL server:
[[File:{{{file_tavl_settings}}}]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Send GSM signal</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes GSM signal strength information in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send analog input</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes analog input state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (1)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #1 state in GPS data package to be sent to server</td>
</tr>
<tr>
<td>Send digital input (2)</td>
<td>yes | no; Default: <b>no</b></td>
<td>Includes digital input #2 state in GPS data package to be sent to server</td>
</tr>
</table>
==GPS Geofencing==
A <b>geofence</b> is a virtually defined boundary for a real-world geographic area. The GPS Geofencing page provides you with the possibility to set this custom area and apply rules that will inform you when the device leaves or enters the geofence.
[[File:{{{file_geofencing_add}}}]]
The figure below is an example of GPS Geofencing configuration and the table below provides information related to that configuration:
[[File:{{{file_geofencing_details}}}]]
<table class="nd-mantable">
<tr>
<th>Field name</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>yes | no; Default: <b>no</b></td>
<td>Turns the Geofence rule ON or OFF</td>
</tr>
<tr>
<td>Longitude (X)</td>
<td>degrees [-180.000000..180.000000]; Default: <b>0.000000</b></td>
<td>East-west position of a point on the Earth's surface. Combining this and the Latitude information will produce a point on the world map that will serve as the center of the geofence area</td>
</tr>
<tr>
<td>Latitude (Y)</td>
<td>degrees [-90.000000..90.000000]; Default: <b>0.000000</b></td>
<td>North-south position of a point on the Earth's surface. Combining this and the Longitude information will produce a point on the world map that will serve as the center of the geofence area</td>
</tr>
<tr>
<td>Radius</td>
<td>integer [1..999999]; Default: <b>200</b></td>
<td>Radius (in meters) of the geofence area</td>
</tr>
<tr>
<td>Generate event on</td>
<td>Exit | Enter | Enter/Exit; Default: <b>Exit</b></td>
<td>Specifies whether the rule should be triggered when the device enters the geofence area, leaves it or on both events</td>
</tr>
<tr>
<td>Get current coordinates</td>
<td>- (interactive button)</td>
<td>Obtains the device's current coordinates and places them in the Longitude and Latitude fields</td>
</tr>
</table>
==See also==
<ul>
<li>[[{{{name}}}_Protocols|{{{name}}} GPS protocols]]</li>
</ul>
[[Category:{{{name}}} WebUI]]
