Changes

[[image:RS232485.png]]

[[image:RS232485.png]]

==RS-485 interface==

==RS-485 interface==

RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br/>When activated RS-485 driver chip draws constant 30mA current, when entering Sleep or Deep sleep RS-485 will be powered off.

RS-485 supports only half-duplex communication, which means data is transferred only one way at a time.<br/>When activated RS-485 driver chip draws constant 30mA current when entering Sleep or Deep sleep RS-485 will be powered off.

===RS-485 modes===

===RS-485 modes===

* RS-485 receive (FMB silent) mode:

* RS-485 receive (FMB silent) mode:

RS485 Works in receive mode. Support debug and testing commands. When command is received answer is sent after that it back up to Receive mode.<br/>

RS485 Works in receive mode. Support debug and testing commands. When the command is received answer is sent after that it back up to Receive mode.<br/>

* RS-485 transmit (FMB log) mode:

* RS-485 transmit (FMB log) mode:

* RS-485 TCP receive (ASCII/Binary) modes:

* RS-485 TCP receive (ASCII/Binary) modes:

In TCP ASCII/Binary mode a link with an external device using text messages can be established. Buffered modes save information until link with server is established and records are sent.

In TCP ASCII/Binary mode a link with an external device using text messages can be established. Buffered modes save the information until link with the server is established and records are sent.

* RS-485 receive (TCP ASCII/Binary Buffered) mode :

* RS-485 receive (TCP ASCII/Binary Buffered) mode :

RS485 works in receive mode. When data received from server RS485 is switched to transmit mode. If data server is not available, data will be saved in buffer.

RS485 works in receive mode. When data received from server RS485 is switched to transmit mode. If the data server is not available, data will be saved in the buffer.

==RS-232 Interface==

==RS-232 Interface==

RS-232 supports full-duplex communication which means the data can be both sent and received at the same time as they use separate transmission lines. Most of the modes are the same as for {{{model|FMB640}}}.

RS-232 supports full-duplex communication which means the data can be both sent and received at the same time as they use separate transmission lines. Most of the modes are the same as for {{{model|FMB640}}}.

{{{model|FMB640}}} RS-232 connection diagram is shown on the figure below.

{{{model|FMB640}}} RS-232 connection diagram is shown in the figure below.

<br>

<br>

RS232 connection diagram:<br>

RS232 connection diagram:<br>

===RS-232 modes===

===RS-232 modes===

Silent, Log mode, NMEA, LLS, TCP ASCII and TCP Binary modes, TCP ASCII/Binary Buffered modes are identical to those of FMBXXX RS-232 and RS-485 modes. In RS-232 LLS mode only one LLS fuel level sensor can be connected.

Silent, Log mode, NMEA, LLS, TCP ASCII, and TCP Binary modes, TCP ASCII/Binary Buffered modes are identical to those of FMBXXX RS-232 and RS-485 modes. In RS-232 LLS mode only one LLS fuel level sensor can be connected.

* RS-232 LCD mode:

* RS-232 LCD mode:

In this mode user is able to communicate with the server through terminal. A link between FMB device and the server has to be established for this mode to function properly.

In this mode, the user is able to communicate with the server through the terminal. A link between FMB device and the server has to be established for this mode to function properly.

* RS-232 RFID HID/RFID MF7 mode:

* RS-232 RFID HID/RFID MF7 mode:

Radio-frequency identification (RFID) is the use of a wireless non-contact system that uses radio-frequency electromagnetic fields to transfer data from a tag attached to an object, for the purposes of automatic identification and tracking. FMB640 can be configured in a way to use with an RFID reader. When an RFID of some sorts (typically a plastic card with a magnetic line) is used with an RFID reader which is connected to FMB640, the device creates a record with the data that the RFID reader has read and can be sent to a server with all other information. RFID ID is activated  like an I/O parameter <br><br>

Radio-frequency identification (RFID) is the use of a wireless non-contact system that uses radio-frequency electromagnetic fields to transfer data from a tag attached to an object, for the purposes of automatic identification and tracking. FMB640 can be configured in a way to use with an RFID reader. When an RFID of some sort (typically a plastic card with a magnetic line) is used with an RFID reader that is connected to FMB640, the device creates a record with the data that the RFID reader has read and can be sent to a server with all other information. RFID ID is activated  like an I/O parameter <br><br>

<br>

<br>

[[image:FMB640_RS232_RFID.png]]

[[image:FMB640_RS232_RFID.png]]

<br>

<br>

To set up FMB640 so it can be connected to an RFID reader, some parameters have to be set up. Go to RS232 \ RS485 and set up COM1 or COM2 settings to RFID Mode or RFID MF7 Mode (the used mode depends on the mode that the RFID reader works). See Figure 922. The Baudrates foreach mode are: <br><br>

To set up FMB640 so it can be connected to an RFID reader, some parameters have to be set up. Go to RS232 \ RS485 and set up COM1 or COM2 settings to RFID Mode or RFID MF7 Mode (the used mode depends on the mode that the RFID reader works). See Figure 922. The Baudrates for each mode are: <br><br>

RFID Mode – 57600<br>

RFID Mode – 57600<br>

RFID MF7 Mode – 9600<br>

RFID MF7 Mode – 9600<br>

[[image:FMB640_RS232_RFIDconf.png]]

[[image:FMB640_RS232_RFIDconf.png]]

<br>

<br>

The difference between ''RFID HID Mode'' and ''RFID MF7 Mode'' is that in ''RFID HID Mode'' {{{model|FMB640}}} understands RFID messages that are in hexadecimal format and ''RFID MF7 Mode'' interpretes messages that are in decimal format. The type of RFID message sent to {{{model|FMB640}}} depends on the RFID reader. For example, ''RFID HID'' mode message looks like "$aa$02$03$04$17$89$00$01" while ''MF7 mode'' message is of following format: "1213141519".<br/>The selected mode has to correspond to the RFID reader's mode.<br/>Please contact your local sales representative for more information about RFID IDs and devices.

The difference between ''RFID HID Mode'' and ''RFID MF7 Mode'' is that in ''RFID HID Mode'' {{{model|FMB640}}} understands RFID messages that are in hexadecimal format and ''RFID MF7 Mode'' interprets messages that are in decimal format. The type of RFID message sent to {{{model|FMB640}}} depends on the RFID reader. For example, ''RFID HID'' mode message looks like "$aa$02$03$04$17$89$00$01" while ''MF7 mode'' message is of following format: "1213141519".<br/>The selected mode has to correspond to the RFID reader's mode.<br/>Please contact your local sales representative for more information about RFID IDs and devices.

* REC to LCD mode: In this mode records are sent via ports.

* REC to LCD mode: In this mode, records are sent via ports.

This is an example view that is displayed in Terminal :

This is an example view that is displayed in Terminal :

* ATOL Tachograph mode: This mode is used to connect ATOL tachograph.

* ATOL Tachograph mode: This mode is used to connect ATOL tachograph.

* UL202-2 Fuel Sensor: Select this mode to make Ultrasonic Fuel Sensors to work on COM port.

* UL202-2 Fuel Sensor: Select this mode to make Ultrasonic Fuel Sensors work on COM port.

* Satellite Backup mode:  

* Satellite Backup mode:  

Since 00.02.05 firmware version device supports Iridium devices which can send short burst data (SBD) to server. This means that some data can be sent from FM device to server through satellites.

Since 00.02.05 firmware version device supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from the FM device to the server through satellites.

In order to get those records you have to connect device to FM64 COM1 or COM2 port. Select COM1 or COM2 mode Satellite backup mode. Those settings could be found in RS232/RS485 TAB in configurator. Baud rate for satellite devices is 19200 bps. Furthermore TSM232 functionality should be enabled. These settings can be found in Features TAB in Short burst data settings. See picture belowDevice supports Iridium devices which can send short burst data (SBD) to server. This means that some data can be sent from FM device to server through satellites.

In order to get those records, you have to connect device to FM64 COM1 or COM2 port. Select COM1 or COM2 mode Satellite backup mode. Those settings could be found in RS232/RS485 TAB in the configurator. Baud rate for satellite devices is 19200 bps. Furthermore, TSM232 functionality should be enabled. These settings can be found in the Features TAB in Short burst data settings. See picture below device supports Iridium devices which can send short burst data (SBD) to the server. This means that some data can be sent from the FM device to the server through satellites.

* RS-232 Garmin mode:

* RS-232 Garmin mode:

Garmin provides a Fleet Management Interface Tool Kit, once {{{model|FMB640}}} is connected to the navigator it enables the driver to have a "screen" in their vehicle for real-time navigation and messaging, and offers job dispatch capabilities to help them be more efficient.<br/>{{{model|FMB640}}} and Garmin operational diagram is shown on the figure below.

Garmin provides a Fleet Management Interface Tool Kit, once {{{model|FMB640}}} is connected to the navigator it enables the driver to have a "screen" in their vehicle for real-time navigation and messaging, and offers job dispatch capabilities to help them be more efficient.<br/>{{{model|FMB640}}} and Garmin operational diagram is shown in the figure below.

{{{image|[[Image:FMB640_garmin_block.png|800px|center]]}}}

{{{image|[[Image:FMB640_garmin_block.png|800px|center]]}}}

Garmin configuration is shown on the figure below. <br>

Garmin configuration is shown in the figure below. <br>

[[image:FMB640_RS232_Garmin.png]]

[[image:FMB640_RS232_Garmin.png]]

==LLS SENSOR==

==LLS SENSOR==

LLS sensor series liquid level sensors are solid-state capacitive devices with no moving parts. The sensors use capacitive technology to produce accurate liquid level measurements of standard factory grade DIESEL OIL and PURE GASOLINE (BENZINE) carbon fuels. The LLS sensor liquid level sensors are strictly prohibited to use in any liquids which are not the factory grade carbon fuels or contain: BIOFUEL, METHANOL, ETHANOL, UREA and similar aggressive components in pure form or as additives for factory grade carbon fuels for use in INTERNAL COMBUSTION ENGINES. Operating media – Diesel fuel (oil), pure gasoline (benzene). <br>

LLS sensor series liquid level sensors are solid-state capacitive devices with no moving parts. The sensors use capacitive technology to produce accurate liquid level measurements of standard factory-grade DIESEL OIL and PURE GASOLINE (BENZINE) carbon fuels. The LLS sensor liquid level sensors are strictly prohibited to use in any liquids which are not the factory-grade carbon fuels or contain: BIOFUEL, METHANOL, ETHANOL, UREA and similar aggressive components in pure form or as additives for factory-grade carbon fuels for use in INTERNAL COMBUSTION ENGINES. Operating media – Diesel fuel (oil), pure gasoline (benzene). <br>

In order to use LLS fuel counter the newest firmware version is needed which can be obtained from Teltonika or a representative. Firmware is updated over GPRS or using cable update method. <br>

In order to use the LLS fuel counter, the newest firmware version is needed which can be obtained from Teltonika or a representative. Firmware is updated over GPRS or using a cable update method. <br>

The LLS fuel sensor must be connected to the FMB640 device. <br>

The LLS fuel sensor must be connected to the FMB640 device. <br>

* Messages can be up to 199 characters long;

* Messages can be up to 199 characters long;

* Messages can also be generated from device and sent to dispatcher/office;

* Messages can also be generated from device and sent to dispatcher/office;

* Messages received will be notified to driver through a pop-up alert on Garmin screen;

* Messages received will be notified to the driver through a pop-up alert on Garmin screen;

* Garmin provides a "virtual keyboard" for text communication.

* Garmin provides a "virtual keyboard" for text communication.

Stop (Destination) Protocol:

Stop (Destination) Protocol:

* Garmin can display a list of Stops/Jobs reported to the device in a separate category called "My Stops";

* Garmin can display a list of Stops/Jobs reported to the device in a separate category called "My Stops";

* Driver has ability to navigate directly to Stop from the list;

* Driver has the ability to navigate directly to Stop from the list;

* Garmin can provide status of a current Stop in progress;

* Garmin can provide the status of a current Stop in progress;

* Garmin can indicate whether the driver has stopped at the location;

* Garmin can indicate whether the driver has stopped at the location;

* Garmin can inform how far the driver has progressed through the list of Stops;

* Garmin can inform how far the driver has progressed through the list of Stops;

Data Deletion Protocol:

Data Deletion Protocol:

* Dispatcher/office has the ability to wipe clean the data on Garmin PND;

* Dispatcher/office has the ability to wipe clean the data on Garmin PND;

* It allows to clean messages in inbox and remove stops.

* It allows to clean messages in the inbox and remove stops.

===Enhanced protocols===

===Enhanced protocols===

Status Protocol:

Status Protocol:

* Up-to-the-minute communications that allow drivers to automatically send status updates;

* Up-to-the-minute communications that allow drivers to automatically send status updates;

* Driver's units can store up to 16 status indicators such as start/stop shift, on/off break etc.

* Driver's units can store up to 16 status indicators such as start/stop shift, on/off the break, etc.

===Supported features on TAVL client application===

===Supported features on TAVL client application===

TAVL client application lets user use the following features of Garmin FMI:

TAVL client application lets the user use the following features of Garmin FMI:

* Text messaging;

* Text messaging;

* Destination message;

* Destination message;

===Text messaging===

===Text messaging===

Text messaging feature lets user communicate with the driver (user that operates Garmin device) by sending text messages via GPRS.

Text messaging feature lets users communicate with the driver (the user that operates Garmin device) by sending text messages via GPRS.

===Destination message===

===Destination message===

Destination message is used to inform the driver of a new destination. When Garmin device receives a destination message from the server it displays it as a Stop to the driver and also gives the driver an ability to start navigating to the Stop location. New destination in TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first.

A destination message is used to inform the driver of a new destination. When the Garmin device receives a destination message from the server it displays it as a Stop to the driver and also gives the driver an ability to start navigating to the Stop location. A new destination in TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first.

===ETA request message===

===ETA request message===

''Estimated Time of Arrival'' request message is used when user wants to know an expected arrival time to currently active destination and the distance (in meters) from current object location to the destination.

''Estimated Time of Arrival'' request message is used when the user wants to know an expected arrival time to currently active destination and the distance (in meters) from the current object location to the destination.