Test-AC: Difference between revisions

Latest revision as of 09:34, 8 May 2026

Introduction

Teltonika OBD devices are able to read data from heavy duty vehicles. With the OBD to FMS adapter, clients are able to connect OBD devices to their heavy duty vehicles which have FMS female connector (usually located under the front panel). Cable is only applicable with the European truck.

Cable pinout scheme

**Cable pinout scheme:**
OBD 16PF		FMS 12PM
4/5	=>	1
6	=>	6
14	=>	9
16	=>	12

DISCLAIMER: PLEASE MAKE SURE THE FMS PINOUT OF YOUR HEAVY DUTY VEHICLE IS AS REFERRED ON THE PROVIDED PINOUT SCHEME. IN CASE OF INCORRECT PINOUT PLEASE CONTACT YOUR HEAVY DUTY VEHICLE DEALERSHIP. THE CLIENT IS RESPONSIBLE FOR ALL THE ISSUES, WHICH MIGHT OCCUR BY INCORRECT INSTALLATION.

NOTE: Please use OBD devices with the latest firmware which has implemented J1939 protocol support.

FMS Plug Location

Even though the FMS cable is standardized cable – its placement in the vehicle might differ depending on manufacturer and depending on vehicle trim level.

These examples identify the most common locations for the FMS plug.

Behind the Fuse panel on passenger side – for Example SCANIA S/R/G/P Euro6 Series

Near the Fuse panel on passenger side – for example DAF XF Euro6

Behind the Radio on lower deck – for example Volvo FH Euro5 and Renault T Euro6

Behind the Tachograph on upper deck – for example Mercedes Actros MP5 Euro6

Device Configuration

1. Connect your OBD device to PC via USB or Bluetooth.
2. Open Teltonika Configurator and find your device in the list.
3. Select your device from the list.
4. Navigate to System and under System Settings Enable Codec 8 Extended protocol.
5. Open OBD II section on the left.
6. In General -> OBD II Settings -> OBD Feature select ELD.
7. In OBD VIN settings-> VIN Source select prefered source. Some heavy duty vehicles may not automaticly provide VIN number, in that case we recommend to setup VIN manually.

8. Save the configuration by pressing Save to device on the top.
9. New section with J1939 parameters can be found in ELD section on the right bottom.

Supported Parameter List

The full supported parameter list for OBD devices can be found in the following pages:

Downloads

This functionality requires the latest OBD configurator and firmware for optimal performance.

Ordering and Specifications

For more information about OBD-II to FMS adapter specifications and ordering, please visit OBD-II TO FMS ADAPTER web page.

@@ Line 1: / Line 1: @@
-=RTK Coordinate via CAN Integration with FMC650=
+__TOC__
-==Overview==
-Activating '''RTK (Real-Time Kinematic)''' coordinate acquisition enables the FMC650 device to process RTK data from CAN.
-When configured, the RTK module can provide high-precision coordinates using:
-*RTK receiver via RS232
-*RTK data via CAN
-*Internal GNSS receiver (GNS) as fallback
-The device automatically chooses the best available source based on configuration and data quality.
-==How It Works==
-When the RTK option is enabled, the device always tries to use RTK sources first and falls back to internal GNSS if needed.
-===Source priority===
-#<b>RS232 (primary RTK source)</b>
-#:*The device checks whether any COM port (COM1 or COM2) is configured in RTK mode.
-#:*If at least one COM port is configured for RTK and valid data is present, coordinates are taken from RS232.
-#<b>CAN RTK (secondary RTK source)</b>
-#:*If RS232 RTK data is not available or is invalid, the device checks the CAN RTK status.
-#:*If valid CAN RTK data is available, coordinates are taken from CAN.
-#:*A timing check is applied:
-#:**If the time difference between received CAN RTK frames is greater than 2 seconds, the device automatically switches to the internal GNSS receiver (GNS) to keep coordinates up to date.
-#<b>Internal GNSS (GNS) fallback</b>
-#:*If neither RS232 nor CAN provide valid RTK data, the device uses the internal GNSS receiver (GNS) for coordinates.
-#<b>RTK disabled</b>
-#:*If the RTK option is disabled, coordinates are always taken from the internal GNSS receiver.
-===RTK data from CAN===
+==Introduction==
-When CAN is used as the RTK source, the device reads:
+[[Image:Cable112224402.jpg|thumb|400x300px|right]]
-*Latitude
+Teltonika OBD devices are able to read data from heavy duty vehicles. With the OBD to FMS adapter, clients are able to connect OBD devices to their heavy duty vehicles which have FMS female connector (usually located under the front panel). Cable is only applicable with the European truck.
-*Longitude
+<br><br><br><br><br><br><br><br><br><br><br><br><br><br>
-*Altitude
+==Cable pinout scheme==
-*Ground speed
+[[Image:OBD-FMS-scheme.png|thumb|400x300px|right]]
-*Course
-These values are taken from standard CAN messages designed for GNSS/RTK data. Exact PGNs and signal layouts depend on whether external RTK/ECD/ISOBUS system is being used.
+{| class="wikitable"
-==General Information==
+|+'''Cable pinout scheme:'''
-*<b>Platform:</b> FM65
+!'''OBD 16PF'''
-*<b>Device:</b> FMC650
+!
-*<b>Firmware version:</b> 03.01.03.Rev.227
+!'''FMS 12PM'''
-*<b>Configurator version:</b> B.FMX6_R.192
+|-
-These versions indicate the minimum firmware and configurator level required to use RTK coordinate acquisition via CAN on FMC650.
+|4/5
-==Configurator Setup==
+|=>
-This section describes how to enable RTK as a location source and configure RS232 and CAN usage through the Configurator.
+|1
-.1 Enabling RTK as a location source
+|-
-. Open the Configurator and connect to the FMC650 device.
+|6
-. Navigate to the System tab.
+|=>
-. Find the option “Source Location from RTK”
+|6
-. Set this option to Enable.
+|-
-When enabled, the device will use RTK data from RS232/CAN if available, with
+|14
-automatic fallback to internal GNSS.
+|=>
-For advanced configuration (e.g. via commands):
+|9
-• Source Location from RTK
+|-
-o Parameter ID: 55000
+|16
-o Values:
+|=>
-▪ 0 – Disabled (device uses only internal GNSS)
+|12
-▪ 1 – Enabled (device uses RTK sources if available)
+|}
-.2 Configuring RS232 for RTK use
-If you plan to use an external RTK receiver via RS232:
-. Open the RS232/RS485 tab in the Configurator.
+'''DISCLAIMER:''' ''PLEASE MAKE SURE THE FMS PINOUT OF YOUR HEAVY DUTY VEHICLE IS AS REFERRED ON THE PROVIDED PINOUT SCHEME. IN CASE OF INCORRECT PINOUT PLEASE CONTACT YOUR HEAVY DUTY VEHICLE DEALERSHIP. THE CLIENT IS RESPONSIBLE FOR ALL THE ISSUES, WHICH MIGHT OCCUR BY INCORRECT INSTALLATION.''
-. For COM1 or COM2 (or both), set the mode to RTK.
-Relevant parameter IDs:
+'''NOTE:''' ''Please use OBD devices with the latest firmware which has implemented J1939 protocol support.''
-• COM1 mode – Parameter ID 151
-• COM2 mode – Parameter ID 173
+==FMS Plug Location==
-• Value for RTK mode – 60
+Even though the FMS cable is standardized cable – its placement in the vehicle might differ depending on manufacturer and depending on vehicle trim level.
-If at least one COM port is configured to RTK mode and valid RTK data is received, the
-device will use RS232 as the main coordinate source.
+These examples identify the most common locations for the FMS plug.
-.3 Using CAN as the RTK source
-CAN-based RTK is used in the following cases:
+==== Behind the Fuse panel on passenger side – for Example SCANIA S/R/G/P Euro6 Series [[File:Scania R-series 1.3.png|frameless|1000x1000px]] ====
-• None of the RS232 COM ports are configured in RTK mode, or
-• RS232 RTK data is not valid or not present.
+==== Near the Fuse panel on passenger side – for example DAF XF Euro6 [[File:DAF XF 1.3.png|frameless|1000x1000px]] ====
-When those conditions are met and valid CAN RTK data is received:
-• The device uses CAN as the coordinate source.
+==== Behind the Radio on lower deck – for example Volvo FH Euro5 and Renault T Euro6 [[File:Volvo FH 1.3.png|frameless|1000x1000px]] ====
-• The device continuously monitors the time between RTK messages.
-• If CAN RTK messages are delayed by more than 2 seconds, the device
+==== Behind the Tachograph on upper deck – for example Mercedes Actros MP5 Euro6 [[File:Mercedes Actros 1.3.png|frameless|1000x1000px]] ====
-automatically reverts to internal GNSS to avoid stale coordinates.
-RTK data taken from CAN includes:
-• Latitude
+==Device Configuration==
-• Longitude
+. Connect your OBD device to PC via USB or Bluetooth.<br>
-• Altitude
+. Open '''Teltonika Configurator''' and find your device in the list.<br>
-• Ground speed
+. Select your device from the list.<br>
-• Course
+. Navigate to '''System''' and under '''System Settings''' Enable '''Codec 8 Extended''' protocol.<br>
-Configuration of RTK over CAN (e.g. PGN, source address, bitrate) depends on your
+. Open '''OBD II''' section on the left.<br>
-external CAN/ISOBUS/RTK infrastructure and should follow that system’s
+. In '''General''' -> '''OBD II Settings''' -> '''OBD Feature''' select '''ELD'''.<br>
-documentation.
+. In '''OBD VIN settings'''-> '''VIN Source''' select prefered source. Some heavy duty vehicles may not automaticly provide VIN number, in that case we recommend to setup VIN manually.<br>
-.4 ISOBUS data visibility
+[[File:OBD II Settings.png|500x500px]]<br>
-When used in ISOBUS or similar environments:
+. Save the configuration by pressing '''Save to device''' on the top.<br>
-• RTK-related data from CAN is visible in the ISOBUS section of the Configurator.
+. New section with J1939 parameters can be found in '''ELD''' section on the right bottom.<br>
-• This allows you to verify that RTK data is being received and interpreted correctly
+[[File:ELD Settings.png|500x500px]]<br>
-by the device.
-. Monitoring the Active Location Source
+==Supported Parameter List==
-To understand which source is currently being used for position data, you can check the
-Location Source parameter.
+The full supported parameter list for OBD devices can be found in the following pages:
-.1 Location Source values
+*[[FMB001 Teltonika Data Sending Parameters ID]]
-In the Configurator:
+*[[FMB003 Teltonika Data Sending Parameters ID]]
-. Navigate to the I/O tab (or equivalent I/O monitoring view).
+*[[FMC003 Teltonika Data Sending Parameters ID]]
-. Find the parameter “Location Source”.
+*[[FMM003 Teltonika Data Sending Parameters ID]]
-Possible values:
+*[[FMM00A Teltonika Data Sending Parameters ID]]
-• 0 – GNS
-Location is taken from the internal GNSS receiver.
+==Downloads==
-o This is the default when RTK is disabled or when no valid RTK data is
+This functionality requires the latest OBD [[Teltonika Configurator versions|configurator]] and [[Firmware versions#OBD trackers|firmware]] for optimal performance.
-available.
-• 1 – RS232
+==Ordering and Specifications==
-Location is taken from the RTK receiver connected via RS232.
+For more information about '''OBD-II to FMS adapter''' specifications and ordering, please visit [https://www.teltonika-gps.com/products/accessories/data-cables/obd-ii-to-fms-adapter OBD-II TO FMS ADAPTER] web page.
-• 2 – CAN
-Location is taken from RTK data arriving over CAN.
-• 3 – Err
-Location is taken from the internal GNSS receiver, but this status indicates that
-RTK data from RS232 and/or CAN is invalid or unavailable.
-o This helps distinguish normal GNSS use from “RTK expected but not
-available” situations.
-This parameter is especially useful for diagnostics and for confirming that your device is
-using the intended RTK source.
-. Monitoring NMEA Fix Type (RS232 RTK Only)
-When RTK coordinates are received via RS232, you can also monitor the NMEA Fix Type
-to understand the quality of the GNSS/RTK fix.
-.1 Where to find it
-. Open the Configurator.
-. Go to the I/O tab (or relevant section).
-. Locate the parameter “NMEA Fix Type”.
-This parameter is only available when coordinate data is received via RS232 RTK.
-.2 NMEA Fix Type values
-Value Description
-NotValid No valid GNSS fix is available.
-GPS Standard GPS fix using satellites only.
-DGNSS Differential GNSS fix (e.g. DGNSS, SBAS, etc.).
-NotApplicable Fix quality is not applicable in the current context.
-RTK_Fixed RTK Fixed; high-precision RTK fix (including xFill if
-supported by the receiver).
-RTK_Float RTK Float; typically, a converging RTK solution or
-similar intermediate status.
-INS_DR INS Dead Reckoning; position estimated by inertial
-sensors and previous GNSS/RTK data.
-This information is helpful for:
-• Verifying that the external RTK receiver is working correctly
-• Assessing overall RTK performance and stability
-• Logging and diagnostics in advanced deployments
-. Parameter ID and AVL ID
-Below is a list of AVLID and Configurator ID assigned to specific item
-Name Parameter ID AVL ID
-RTK Longitude 151790 14145
-RTK Latitud 151800 14146
-RTK Altitude 151810 14147
-RTK Speed 151820 14148
-RTK Angle 151830 14149
-Source Location from RTK 55000 -
-Location Source 53050 10919
-NMEA Fix Type 53060 10920