Line 20: |
Line 20: |
| <br> | | <br> |
| {{{auto_apn| | | {{{auto_apn| |
| + | |
| ==Auto APN== | | ==Auto APN== |
| [[File:Auto APN Search.png|right]] | | [[File:Auto APN Search.png|right]] |
Line 25: |
Line 26: |
| This setting allows the device to automatically search for APN information based on inserted SIM card. <br> This feature is used form 03.25.15.Rev.32 and up, explained in more detail in [[Auto_APN_feature_for_FM_trackers|this page]]. | | This setting allows the device to automatically search for APN information based on inserted SIM card. <br> This feature is used form 03.25.15.Rev.32 and up, explained in more detail in [[Auto_APN_feature_for_FM_trackers|this page]]. |
| }}} | | }}} |
| + | |
| ==Transfer APN File== | | ==Transfer APN File== |
− |
| |
| APN file Upload / Download <br /> [[File:Transfer APN File .png|right]] | | APN file Upload / Download <br /> [[File:Transfer APN File .png|right]] |
| Connect to the device using configurator and look for Transfer APN file section. Press the Upload button and locate your APN_list.bin file. (binary APN list can be named differently, make sure to use the correct file). This transfer APN File option is valid from 03.25.15.Rev.32 and up. | | Connect to the device using configurator and look for Transfer APN file section. Press the Upload button and locate your APN_list.bin file. (binary APN list can be named differently, make sure to use the correct file). This transfer APN File option is valid from 03.25.15.Rev.32 and up. |
| <br> | | <br> |
| <br> | | <br> |
| + | |
| ==First Server Settings== | | ==First Server Settings== |
| [[Image:Example Server settings.png|right]] | | [[Image:Example Server settings.png|right]] |
− | In the main destination server Domain and Port needs to be inputted, and allows setting the protocol used for data transfers – <span style="color:#F6A83E">TCP</span> or <span style="color:#F6A83E">UDP</span>. An additional option is the use of TLS/DTLS encryption for sending records to the main server and backup server. Also in the Domain settings, can be written either IP address or Domain. <br> | + | In the main destination server Domain and Port needs to be written, and allows setting the protocol used for data transfers – <span style="color:#F6A83E">TCP</span> or <span style="color:#F6A83E">UDP</span>. <br> An additional option is the use of TLS/DTLS encryption for sending records to the main server and backup server. Also in the Domain settings, can be written either IP address or Domain. <br> |
| <br> | | <br> |
| <br> | | <br> |
Line 40: |
Line 42: |
| <br> | | <br> |
| ==Second Server Settings== | | ==Second Server Settings== |
− | | + | [[File:Screenshot 9.png|right]] |
− | Backup server has 4 different modes:
| + | Second server has 4 different modes: <br> |
− | | + | Disable: |
− | *<span style="color:#F6A83E">Disable</span>: backup server is not used.
| + | *Second server is not used. |
− | *<span style="color:#F6A83E">Backup</span>: 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.
| + | Backup: |
− | *<span style="color:#F6A83E">Duplicate</span>: records are sent to both servers (main and backup), records are deleted from SD-card (or Flash storage) only if both servers accepted the records.
| + | *Records are sent to second server if main server is not available (for example fails to open link) or when main server response timeout is reached successively 5 times. |
− | *<span style="color:#F6A83E">EGTS</span>: records are sent to both servers (main and backup), records are sent to the backup server using the EGTS protocol. '''RNIS''' system is supported with EGTS protocol. <br />
| + | Duplicate: |
| + | *Records are sent to both servers (main and second), records are deleted from SD-card (or Flash storage) only if both servers accepted the records. |
| + | EGTS: |
| + | *Records are sent to both servers (main and second), records are sent to the backup server using the EGTS protocol. '''RNIS''' system is supported with EGTS protocol. <br /> |
| Domain and Port needs to be inputted, and allows setting the protocol used for data transfers – <span style="color:#F6A83E">TCP</span> or <span style="color:#F6A83E">UDP</span>. An additional option is the use of TLS/DTLS encryption for sending records to the main server and backup server. | | Domain and Port needs to be inputted, and allows setting the protocol used for data transfers – <span style="color:#F6A83E">TCP</span> or <span style="color:#F6A83E">UDP</span>. An additional option is the use of TLS/DTLS encryption for sending records to the main server and backup server. |
| <br> | | <br> |
| <br> | | <br> |
− | <br>
| + | |
− | <br>
| |
− | <br>
| |
| ==Records Settings== | | ==Records Settings== |
| [[File:Record settings.png|right]] | | [[File:Record settings.png|right]] |
− | {{{model|FMB1YX}}} device will send the newest records first when <span style="color:#F6A83E">Newest</span> is selected in ''Records Settings'', 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.<br />''Data Link Timeout'' is used to set termination timeout for link between {{{model|FMB1YX}}} and AVL application. If {{{model|FMB1YX}}} has already sent all records it waits for the new records before closing the link (except for Deep Sleep mode, for more information refer to {{{ctrSleepModes|[[Template:FMB Sleep modes#Deep Sleep mode]]}}}). If new records are generated during the period of this timeout and the minimum count to send is reached, the records are sent to the AVL application. This option is useful when GSM operator charges for link activation.<br />''Server Response Timeout'' is used to set a period of time waiting for the response from the server-side. | + | {{{model|FMB1YX}}} device will send the newest records first if <span style="color:#F6A83E">Newest</span> is selected in ''Records Settings'', and if <span style="color:#F6A83E">Oldest</span> then it will sent Oldest records. <br> When <span style="color:#F6A83E">Newest</span> is selected it 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.<br /> |
− | <br> | + | |
| + | Open Link Timeout: |
| + | *Is used to set termination timeout for link between {{{model|FMB1YX}}} and AVL application. <br> |
| + | If {{{model|FMB1YX}}} has already sent all records it waits for the new records before closing the link (except for Deep Sleep mode, for more information refer to {{{ctrSleepModes|[[Template:FMB Sleep modes#Deep Sleep mode]]}}}). If new records are generated during the period of this timeout and the minimum count to send is reached, the records are sent to the AVL application. This option is useful when GSM operator charges for link activation.<br> |
| + | |
| + | Server Response Timeout: |
| + | *Is used to set a period of time waiting for the response from the server-side. |
| + | |
| + | Network Ping Timeout: |
| + | *Enables network ping after timeout to prevent link close by operator. <br> |
| '''ACK Type''' determines what method the device uses to receive confirmation from the server. <br> | | '''ACK Type''' determines what method the device uses to receive confirmation from the server. <br> |
| + | |
| '''AVL''' means that the device will expect an additional AVL message from the server, | | '''AVL''' means that the device will expect an additional AVL message from the server, |
| '''TCP/IP''' means that the confirmation will be included in the TCP/IP layer and no additional message will be needed. | | '''TCP/IP''' means that the confirmation will be included in the TCP/IP layer and no additional message will be needed. |
Line 64: |
Line 77: |
| ==FOTA WEB Settings== | | ==FOTA WEB Settings== |
| [[File:Fotawebsets.png|right]] | | [[File:Fotawebsets.png|right]] |
− | These settings are used to configure FOTA WEB server connection parameters. ''Status'' enables or disables FOTA WEB functionality. If the Status is enabled then it means that CFG can be uploaded to FOTA WEB. The address and port number of the FOTA website are entered to ''Domain'' and ''Port'' fields. ''Period'' is used to set the timeout of repeat connections to the FOTA WEB server.<br> | + | These settings are used to configure FOTA WEB server connection parameters. |
| + | Status: |
| + | *Enables or disables FOTA WEB functionality. If the Status is enabled then it means that CFG can be uploaded to FOTA WEB. |
| + | Domain Port: |
| + | *The address and port number of the FOTA website are entered to ''Domain'' and ''Port'' fields. |
| + | Period: |
| + | *Is used to set the timeout of repeat connections to the FOTA WEB server.<br> |
| + | |
| From 03.27.XX firmware version, FOTA WEB connection period randomizer is added. The randomizer will choose a +-2.5 period for each connection. For example, then the connection period is set to 30 minutes, device with each connection will choose a new connection (from 27.5 min to 32.5 minutes). This also applies to the "web_connect" SMS/GRRS command. This has been implemented to ensure smoother operation of FOTA WEB services by spreading out large numbers of simultaneous device connections over a longer timeframe. | | From 03.27.XX firmware version, FOTA WEB connection period randomizer is added. The randomizer will choose a +-2.5 period for each connection. For example, then the connection period is set to 30 minutes, device with each connection will choose a new connection (from 27.5 min to 32.5 minutes). This also applies to the "web_connect" SMS/GRRS command. This has been implemented to ensure smoother operation of FOTA WEB services by spreading out large numbers of simultaneous device connections over a longer timeframe. |
| }}} | | }}} |