18
edits
Changes
no edit summary
==GPRS Settings==
==GPRS Settings==
[[File:GPRS.png|right]]
[[File:GPRS 2.PNG|right]]
These settings define the main parameters for {{{model|FMB1YX}}}. <br/ >
These settings define the main parameters for {{{model|FMB1YX}}}. <br/ >
GPRS Context:
GPRS Context:
* Device ability to enable or disable GPRS connection.
* Device ability to enable or disable GPRS connection.
APN:
APN:
*Access point name, mandatory parameter which is used connect to internet (GPRS). Access Point Name is a gateway between mobile operator and public internet. It can be obtained from your SIM card provider.
*Access point name, a mandatory parameter which is used to connect to the internet (GPRS). Access Point Name is the name of a gateway between a mobile operator and the public internet. It can be obtained from your SIM card provider.
APN Username:
APN Username:
*Access point name username (optional – depending on operator)
*Access point name username (optional – depending on operator)
APN Password:
APN Password:
*Access point name password (optional – depending on operator). <br>
*Access point name password (optional – depending on operator). <br>
Limit connection errors:
*When enabled (default option) device will try to open GPRS or socket and if it fails it will introduce additional delays on the next try. The delays are incremented based on the consecutive network errors received:
1. No delays<br>
2. 1 minute.<br>
3. 1 minute.<br>
4. 2 minutes.<br>
5. 2 minutes.<br>
6. 4 minutes.<br>
7. 6 minutes.<br>
8. 8 minutes.<br>
9. 10 minutes.<br>
Once 10 minutes is reached and if errors continue to occur the delay will not reset. When connection is succesful the delay resets. This feature is enabled for every socket and SIM1 or SIM2 (if available) GPRS context.
*When disabled (option introduced from 03.29.00.Rev.10 base firmware version) device will spam the network with GPRS or socket related network operations with no additional delays. This might introduce operators bans on some devices if the network signal quality is poor and device tries its best to connect to the network.
GPRS Authentication:
GPRS Authentication:
* Some operators use a specific type of authentication for GPRS sessions – CHAP or PAP. 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 authentification for GPRS sessions. It could be CHAP or PAP authentifications. In configurator's GPRS settings there are option to select which GPRS authentification could be used. Information about the APN details and authentification should be provided by your GSM operator. <br />
{{{txt_sim2|SIM1 and SIM2 ''GPRS Settings'' can be configured separately. }}}
{{{txt_sim2|SIM1 and SIM2 ''GPRS Settings'' can be configured separately. }}}
<br>
<br>
*This feature can be disabled in the device configuration if the device GPRS settings are configured before installation or during installation of device.
*This feature can be disabled in the device configuration if the device GPRS settings are configured before installation or during installation of device.
}}}
}}}
==Transfer APN File==
==Transfer APN File==
[[File:Transfer APN File .png|right]]
[[File:Transfer APN File .png|right]]
*Server Port
*Server Port
Protocol:
Protocol:
*Defines GPRS data transport protocol, used for data transfers – <span style="color:#F6A83E">TCP</span> or <span style="color:#F6A83E">UDP</span>. From the device side TCP and UDP work almost the same, only difference is that UPD doesn't need additional confirmation from server side, that the data packet was received. TCP has that, and uses more network data for the confirmation. Protocol to use can be select through CFG.
*Defines GPRS data transport protocol, used for data transfers – <span style="color:#F6A83E">TCP</span> or <span style="color:#F6A83E">UDP</span>. From the device side TCP and UDP work almost the same, 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.
TLS encryption:
TLS encryption:
*An additional option is the use of TLS encryption for sending records to the main server and backup server.
*An additional option is the use of TLS encryption for sending records to the main server and backup server.
[[File:Record settings.png|right]]
[[File:Record settings.png|right]]
Open Link Timeout:
Open Link Timeout:
*The parameter used to define a timeout between the fleet management device and the server. If the device already sent all records, it waits for a timeout to close the link. “Open link timeout” will refresh after sending a new record. If you want to keep a constant link with a server, increasing the value of the parameter is needed.
*The parameter 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 confugured 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.
Server Response Timeout:
Server Response Timeout:
*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 send the same record again. Be aware of the fact that if the implementation of data sending protocols isn't correct, it can cause issues when clients claim that the device sends the same data over and over.
*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.
[[File:Alert.png|left|20px|link=]] NOTE! If Data [[Codec|protocols]] are not implemented correctly, device will not send data correctly. <br>
Network Ping Timeout:
Network Ping Timeout:
*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.
*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. This functionality works only for Record and Backup Servers. '''Network Ping Timeout should be always lower than Open Link Timeout.'''
Sort by:
Sort by:
* Can be set either Newest or Oldest. For example if the Oldest is marked the the device first will send the Oldest information, if Newest then Device will send the newest information. Also if there was no connection for some time, the device saves the records to the internal storage, when signal is recovered and if the sorting is set on Newest the device will sent first the Newest record rather than the Older records. If Oldest is set then the device will sent all the records from Oldest to Newest, but it may take some time while the Newest record will be sent. If high priority in I/O section is set then I/O parameter will be sent first.
* Can be set either Newest or Oldest. For example if the Oldest is marked the device first will send the Oldest information, if Newest then Device will send the newest information. If the device had no connection (GSM or GPRS) due to bad coverage or being in an area with no signal. Device continues to save records into internal memory, once GSM and GPRS are recovered device will start sending saved data to server. In this example, if Oldest is configured - until newest data is seen on the server all of the oldest records have to be sent first. If Newest is configured - previous data and track won't be seen until newest data is sent first. If high priority on I/O parameters or Features are configured device will send the generated records with High Priority first.
ACK Type:
ACK Type:
*Determines what method the device uses to receive confirmation from the server <span style="color:#F6A83E">TCP/IP</span> or <span style="color:#F6A83E">AVL</span>. <span style="color:#F6A83E">TCP/IP</span> means that the confirmation will be included in the TCP/IP layer and no additional message will be needed. <span style="color:#F6A83E">AVL</span> means that the device will expect an additional AVL message from the server,
*Determines what method the device uses to receive confirmation from the server <span style="color:#F6A83E">TCP/IP</span> or <span style="color:#F6A83E">AVL</span>. <span style="color:#F6A83E">TCP/IP</span> means that the confirmation will be included in the TCP/IP layer and no additional message will be needed to acknowledge the record receiving. <span style="color:#F6A83E">AVL</span> means that the device will expect an additional AVL message from the server - according to the Data sending protocols described [[Codec|here]].