Changes

Line 1: Line 1:  
==Mobile data settings==   
 
==Mobile data settings==   
 
[[File:Mobile Data Settings.png|right|500px]]
 
[[File:Mobile Data Settings.png|right|500px]]
These settings define the main parameters for {{{model|FTC881}}}. <br/ >
+
These settings define the main parameters for {{{model|FTC921}}}. <br/ >
    
'''APN:'''
 
'''APN:'''
Line 11: Line 11:  
'''GPRS Authentication:'''
 
'''GPRS Authentication:'''
 
* Some operators use a specific type of authentication for GPRS sessions – Normal (PAP) or Secured (CHAP). If any of these is used, APN should be entered as "chap:<APN>" or "pap:<APN>" respectively. E.g. if the 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. <br />
 
* Some operators use a specific type of authentication for GPRS sessions – Normal (PAP) or Secured (CHAP). If any of these is used, APN should be entered as "chap:<APN>" or "pap:<APN>" respectively. E.g. if the 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. <br />
 +
<br>
 +
<br>
    
==Server settings==   
 
==Server settings==   
Line 19: Line 21:  
*Server Port
 
*Server Port
 
'''Data protocol'''
 
'''Data protocol'''
*TCP (Transmission control protocol) or UDP (User datagram protocol). Changing this parameter will alter how the device communicates. For more information on the protocol differences of Teltonika devices, refer here [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols]
+
*TCP (Transmission control protocol) or UDP (User datagram protocol). Changing this parameter will alter how the device communicates. From the device side, TCP and UDP work almost the same, the only difference is that UDP doesn't need additional confirmation from the server side, that the data packet was received. TCP has that and uses more network data for the confirmation. The desired data transfer protocol can be selected through the configurator. For more information on the protocol differences of Teltonika devices, refer here [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols]
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
    
==Server communication settings==
 
==Server communication settings==
Line 26: Line 33:  
'''Open link timeout (s)'''
 
'''Open link timeout (s)'''
   −
*The parameter is used to define a timeout between the fleet management device and the server. If the device has sent all records, device holds the link for duration of the configured timeout. “Open link timeout” will refresh after device sends a new record. If there is a need to keep a constant link with a server, increasing the value of the parameter is needed.
+
*The parameter is used to define a timeout between the fleet management device and the server. If the device has sent all records, the device holds the link for the duration of the configured timeout. The “Open link timeout” timer will refresh after the device sends a new record. If there is a need to keep a constant link with a server, increasing the value of the parameter is needed.
    
'''Response timeout (s)'''
 
'''Response timeout (s)'''
*Is used to set a period of time waiting for the response from the server-side. If there is no response from the server during the timeout, the device will close the link and according to device configuration resend the same packet
+
*It is used to set a period waiting for the response from the server side. If there is no response from the server during the timeout, the device will close the link and according to device configuration resend the same packet
    
'''Keep-alive ping timeout (s)'''
 
'''Keep-alive ping timeout (s)'''
*enables network ping after timeout to prevent link close by operator. For example, if the operator closes the active link after 15 minutes when no data is sent, you can set the "network ping" timeout to 10 minutes then the device sends a 0xFF byte to server to keep the link open. Keep-alive ping timeout should be always lower than Open Link Timeout.
+
*The device will ping the server periodically, so the server or operator will not close the link. The keep-alive ping timeout value should always be lower than the open link timeout.
 +
<br>
 +
<br>
 +
<br>
 +
<br>
 +
<br>
    
==FOTA Web settings==
 
==FOTA Web settings==
[[File:FTC FOTA WEB.jpg|right|500px]]
+
[[File:FOTA web settings newest.png|right|500px]]
 
'''domain'''
 
'''domain'''
 
*Domain which points to FOTA Web.  
 
*Domain which points to FOTA Web.  
Line 45: Line 57:  
*FOTA Web pinger port
 
*FOTA Web pinger port
   −
[[Category:{{{model}}} Configuration]]
+
For more information on FOTA WEB, please refer [https://wiki.teltonika-gps.com/view/FOTA_WEB|here].