20
edits
Changes
no edit summary
| ✔
| ✔
| ✔
| ✔
| ✔<sup>1</sup>
| ✔<sup>1</sup>
|
|
|
|
|
|
|
|
|}
|}
<sup>1</sup> – available from FW version <b>03.28.XX</b>.
<br />
{|
|[[File:Alert.png|left|link=|50px]]||<b>Do not under any circumstances connect RS485 A and B lines (or RS232 Tx and Rx) to power source.
</b>
|}
<br />
<tr>
<td style="vertical-align:middle;">[[Image:Bw_nb.png|50px]]</td>
<td style="vertical-align:middle;">Swapping RS485 A and B lines (or RS232 Tx and Rx) of the external device and also not connecting common ground first - May cause irreparable damage.</td>
</tr>
</table>
====Log mode====
====Log mode====
====RS-232 Delimiter mode====
====RS-232 Delimiter mode====
* This feature works from '''Ver.03.28.05.Rev.00+''' with Codec 8 Extended enabled.<br>
* This feature works from '''Ver.03.28.05.Rev.00+''' with Codec 8 Extended enabled.<br>
'''Delimiter mode''' have two configurable delimiters to mark start and end of packet received from external device. Delimiter is configured as HEX string, max length 3 Bytes.
''Examples:''
''Examples:''
| style="font-size:14px;" | 168
| style="font-size:14px;" | 168
|}
|}
<div style="text-align: center;">Table 1. START and END delimiters are configurable via SMS/GPRS Configurator</div>
{| class="wikitable"
{| class="wikitable" style="width:100%;"
|- style="font-size:15px; background-color:#9CF;"
|- style="font-size:15px; background-color:#9CF;"
! Start delimiter
! Start delimiter
|}
|}
<div style="text-align: center;">Table 2. Functionality description by delimiter configuration</div>
'''Baudrate and parity configurable in base functionality'''
* New IO element '''Serial Packet''' ID:109:
When '''Delimiter mode''' is selected and packet is received via RS232 FMB will save record with added '''Serial Packet''' IO element with HIGH priority. If any other mode than
{| class="wikitable" style="text-align:center;"
'''Delimiter''' is selected “Serial Packet” IO element will not be saved in records;
'''Serial Packet''' length will be variable, max length 257 bytes;
While no '''Serial Packet''' is received from external device FMB will save other periodic or eventual records without '''Serial Packet''' IO element.
{| class="wikitable" style="text-align:center; font-size:15px;"
|- style="background-color:#9CF;"
|- style="background-color:#9CF;"
! colspan="11" style="font-size:12px;" | Record with Serial Packet
! colspan="11" | Record with Serial Packet
|- style="font-size:12px;"
|-
| rowspan="2" | Preamble 4 bytes
| rowspan="2" | Preamble 4 bytes
| AVL Data length
| AVL Data length
| rowspan="2" | Payload, 255 Bytes
| rowspan="2" | Payload, 255 Bytes
| CRC
| CRC
|- style="font-size:12px;"
|-
| 4 Bytes
| 4 Bytes
| 8 Bytes
| 8 Bytes
|}
|}
<div style="text-align: center;">Table 3. Example of serial packet with Codec8 Extended Protocol</div>
'''Index:''' Indicates the number of generated payload. Starting from 0 index.
'''Data Length:''' Length of payload.
'''Payload:''' Data parsed by delimiter functionality.
'''Note:''' Delimiter IO element is string type. Each type of IO elements has identifier byte that identify how many IOs of that type stored in record.
'''IO Types:'''
* 1byte IO elements
* 2 bytes IO elements
* 4 bytes IO elements
* 8 bytes IO elements
* String IO elements
{| class="wikitable" style="width:100%;"
|-
|-
| Event ID
! style="background-color:#efefef;" | Event ID
! 109 (delimiter)
|-
|-
| Total IO count
| style="background-color:#efefef;" | Total IO count
| All configured + 1 (delimiter)
| All configured + 1 (delimiter)
|-
|-
| 1 byte IO’s count
| style="background-color:#efefef;" | 1 byte IO’s count
| All configured 1 byte IO’s count
| All configured 1 byte IO’s count
|-
|-
| 1 byte IOs
| style="background-color:#efefef;" | 1 byte IOs
| All configured 1 byte IOs
| All configured 1 byte IOs
|-
|-
| 2 bytes IO’s count
| style="background-color:#efefef;" | 2 bytes IO’s count
| All configured 2 bytes IO’s count
| All configured 2 bytes IO’s count
|-
|-
| 2 bytes IOs
| style="background-color:#efefef;" | 2 bytes IOs
| All configured 2 bytes IOs
| All configured 2 bytes IOs
|-
|-
| 4 bytes IO’s count
| style="background-color:#efefef;" | 4 bytes IO’s count
| All configured 4 bytes IO’s count
| All configured 4 bytes IO’s count
|-
|-
| 4 bytes IOs
| style="background-color:#efefef;" | 4 bytes IOs
| All configured 4 bytes IOs
| All configured 4 bytes IOs
|-
|-
| 8 bytes IO’s count
| style="background-color:#efefef;" | 8 bytes IO’s count
| All configured 8 bytes IO’s count
| All configured 8 bytes IO’s count
|-
|-
| 8 bytes IOs
| style="background-color:#efefef;" | 8 bytes IOs
| All configured 8 bytes IOs
| All configured 8 bytes IOs
|- style="background-color:#FF9;"
|- style="background-color:#efefef;"
| String type IO’s count
| String type IO’s count
| -
| style="background-color:#FF9;" | All string type IO’s count
| All string type IO’s count
|-
|-
| String type IOs
| style="background-color:#efefef;" | String type IOs
| ID, index, length, serial packet
| ID, index, length, serial packet
|-
|-
| …
| style="background-color:#efefef;" | …
| …
| …
| …
|}
|}
<div style="text-align: center;">Table 4. Record structure</div>
<br>
String type IO count byte will be added to the record only if record was generated with event ID equal to serial packet. Regular records that were generated not by Serial Packet will NOT have string type IO count identifier byte.
===== Configurable parameters =====
------------------
[[File:RS232 delimiter.jpg|alt=|thumb|center|934x425px]]
<div style="text-align: center;">''New RS232 mode '''Delimiter'''''</div>
<br>
[[File:RS232 delimiter startstop.jpg|alt=|thumb|center|934x425px]]
<div style="text-align: center;">''Start and Stop Delimeter for new RS232 mode '''Delimiter''' value in HEX''</div>
<br>
<br>
==Garmin protocols==
==Garmin protocols==
The following is a list of protocols supported and the corresponding list of features/benefits. {{{model|FMB125}}} can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of {{{model|FMB125}}} and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.
The following is a list of protocols supported and the corresponding list of features/benefits. {{{model|FMB125}}} can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of {{{model|FMB125}}} and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.
