User manual

Unit ID: A unique Unit ID is entered in this field. This value must be unique for each unit on the system.

If the device is to be used on FleetLinc or the DataGate you must contact CES Wireless

Technologies to obtain a unique Unit ID.

Server IP Address: In order for the device to send data to the proper location it must be programmed

with the IP Address of the Server where the Fleet-Control application is running. For example, to have the

device send data to the FleetLinc servers the IP Address to enter is “216.139.231.204”. Another method

of entering the IP Address for FleetLinc is by clicking on the left button. The IP Address of the

FleetLinc server will be filled in automatically. Clicking on the right button will insert the IP Address

of the DataGate server.

If using a different IP Address please note that it should be a static IP Address. If it is dynamic then the

devices will no longer be able to communicate with it if it changes, which it will.

Port Number: The port number used by the device to communicate to the server is entered here. It is

recommended to leave the value unchanged (2400). If using the device with FleetLinc or the DataGate the

port must be set to 2400. If changed for other uses the port must also be changed in FleetControl.

Note: If the device will be reporting to your server you must configure the firewall or

router to route data received on the programmed port to the IP Address of the server. If

there is a firewall on the server it must be configured to allow FleetControl to have full access. The Port

set here should also be configured so that data can be sent and received. Please contact your local

Information Technology expert for assistance in configuring the firewall and/or router. CES support

personnel can only assist with the device and software configurations.

Protocol: Select the protocol the device should use (UDP or TCP). If the device is to be used with

FleetLinc the protocol should be UDP.

UDP is a connectionless protocol for sending and receiving packets across a network. UDP does not

provide a guarantee that the receiver will receive packets in the right order; in fact, there is no guarantee

that the packets will arrive at all.

TCP is a connection-based protocol which guarantees that the receiver will receive exactly what the

sender sent - there will be no errors and it will be in the correct order.

UDP is much faster than TCP because there is no extra overhead for error-checking above the packet

level. This extra overhead also uses more data.

If a Garmin device is being interfaced to a GPS206 then the TCP protocol must be selected.

Wake Up Packet Interval: Program the report period for the Wake Up packet to be sent. The wake up

packet is useful on systems where other packets are sent infrequently (i.e. every hour as opposed to every

5 minutes). In most configurations the Wake Up Packet Interval can be set to 0 (off). Note – the

Wake Up Packet does use data and it will effect the data usage.

Automatic Reset Interval: Program the interval at which the device should do an automatic reset. It is

recommended that the unit be configured to perform an automatic reset every 4 hours. The minimum

value is 4. To turn this off (not recommended) a value of 0 can be entered.