View source for TAT100 GPRS settings

==GPRS Settings==
{|style="width: 100%;"
|[[Image:GPRS_settings.png|right]]
* <b>APN</b> - Access point name, mandatory  parameter which is used  connect to internet (GPRS).
* <b>APN Username</b> - Access point username (optional – depending on operator).
* <b>APN password</b> - Access point password (optional – depending on operator).
<br>
Some operators use specific type of authentication for GPRS session – <span style=color:#F6A83E>CHAP</span> or <span style=color:#F6A83E>PAP</span>. If any of these is used, APN should be entered as "chap:<APN>" or "pap:<APN>" respectively e.g. if operator is using APN "internet" with CHAP authentication, it should be entered as "chap:internet". Information about APN and authentication type should be provided by your GSM operator.
|}
==Server Settings==
{|style="width: 100%;"
|[[Image:Server settings tat100.png|right]]
*<b>Domain</b> - Server IP or DNS address.
*<b>Port</b> - Server port.
This section allows setting the protocol used for data transfers – <span style=color:#F6A83E>TCP</span> or <span style=color:#F6A83E>UDP</span>.
Also it is possible to choose if the encryption for sending the records should be used. 

'''Test Connection''' will generate one high-priority test record and initiates connection to the configured server. 
<br/>
{| class="wikitable" style="border-style: solid; border-width: 0px"
|+ 
|-
| style="{{{TAT100_note|}}}text-align: left; background: #F6F6FB;"         | [[Image:Bw_nb.png|50px]]
| style="{{{TAT100_note|}}}text-align: left; background: #F6F6FB;"         | '''NOTE:''' configuration must be saved to the device before testing the connection to the server. 
|}
<!--
|}
==Second Server Settings==
{|style="width: 100%;"
|[[Image:Second server settings tat100.png|right]]
Backup server settings can also be selected for ''Backup'' server.<br/>Backup server has 3 different modes:
* <code>Disable</code> - backup server is not used.
* <code>Backup</code> - records are sent to backup server if main server is not available (for example fails to open link) or when main server response timeout is reached successively 5 times.
* <code>Duplicate</code> - records are sent to both servers (main and backup), records are deleted from SD-card (or RAMS) only if both servers accepted the records.
|}
-->
==Records Settings==
{|style="width: 100%;"
|[[Image:TAT_Records settings.png|right]]
* <b>Sort by</b> - Here {{{model|TAT100}}} device will send the newest records first when <b>Newest</b> is selected, which is useful in cases when the most important parameter set is the most recent one, as a result other records will be sent right after the newest records are received by AVL application.
* <b>ACK Type</b> - Possible to choose TCP/IP or AVL type
* <b>First Power On record</b> - first Power On record is a feature that when enabled sends first record on first manual power-up by switch. It can be turned on/off also by SMS/GPRS command. <br>
<br><br><u>'''More about First Power On record feature:'''</u>
<br>This parameter has an ID 199.<br>
When enabled, the device on first power on will perform standard operations like in period record sending - time synchronization, getting GNSS fix, getting LBS data and etc. The time period of time from the moment of switching on the device and record sending strongly depends on configuration and time for fix searching. For example: 
* When the tracking source is GNSS, in good conditions (clear sky, antenna pointing upwards) the first record will be sent approximately after 2 minutes from the time the device is turned on.
* If the location source is LBS only, the record can be received even more quickly - after about 90 seconds.<br>
Depending on how bad the conditions are, the time to send a record can be significantly longer (a few additional minutes).

<table id="important" style="
  border-collapse: collapse;
  width: 100%;">
  <tr>
    <th style=" border: 1px solid #ddd; padding: 8px; padding-top: 12px; padding-bottom: 12px; text-align: left; background-color: #0054A6; color: white; ">Note</th>
  <tr>
    <td style=" border: 1px solid #ddd; padding: 8px; background-color: #f1f2f5;">Some things that should be taken in consideration:
<br> 1. Static navigation logic will be ingored for this record.
<br> 2. When working with Recovery mode scenario, this first record ''' will''' be an alarm record if ''Update frequency'' parameter is sufficiently short to generate an alarm before sending a record.
<br> 3. When setting ''First Power On'' record parameter with SMS/GPRS command, it is recommended to send this command '''before''' turning the device on. Doing it with initial delay after turning on the device may cause unstable behavior.
 </td> 
 </tr>
</table>

|}
{{{not_for_TAT100|==FOTA WEB Settings==}}}
{{{not_for_TAT100|[[Image:Fotaweb settings tat100.png|right]]}}}
{{{not_for_TAT100|These settings are used to configure FOTA WEB server connection parameters. }}}
*{{{not_for_TAT100|<b>Status</b> enables or disables FOTA WEB functionality. 
*<b>Domain</b> - Address of FOTA website.
*<b>Port</b> - Port number of FOTA website.}}}
TAT100 device does not connect to FOTA WEB periodically to preserve battery power.
*Device will automatically connect to FOTA WEB only on initial startup (when the switch is flipped from OFF to ON position). 
*Connection to FOTA WEB can also be initiated via the 'web_connect' SMS/GPRS command.<br>

<table id="important" style="
  border-collapse: collapse;
  width: 100%;">
  <tr>
    <th style=" border: 1px solid #ddd; padding: 8px; padding-top: 12px; padding-bottom: 12px; text-align: left; background-color: #0054A6; color: white; ">Note</th>
  <tr>
    <td style=" border: 1px solid #ddd; padding: 8px; background-color: #f1f2f5;">TAT devices do not follow the same logic when connecting to Fota platform. A more detailed description of Fota connection can be found [https://wiki.teltonika-gps.com/view/TAT1XY_Creating_Tasks_on_Fota HERE].
 </td> 
 </tr>
</table>

[[Category:TAT100 Configuration]]