(One intermediate revision by one other user not shown)
Line 1:
Line 1:
=External RTK coordinate via CAN/RS232 interface with FMC650=
==Authorized Read Notification==
==Overview==
'''Important: ''iButton Read Notification'' feature has been replaced with ''Authorized Read Notification'' starting from Firmware Ver.03.30.00''' <br>
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.
The following specifications indicate the minimum firmware and configurator version requirement to use RTK coordinate acquisition via CAN on FMC650.
Authorized read notification feature allows the control of selected DOUT for a configured period, when '''Authorized ID''' is read using '''1-Wire''', '''RFID Reader''' or when '''Authorized Beacon''' is detected. If Authorized ID List is empty or Beacon detection is set to '''All''', then any detected ID or Beacon can control selected DOUT. Parameter '''Depend on Ignition''' allows to disable DOUT control, while Ignition is being detected. It is necessary to select at least one source for this functionality to work.
*<b>Platform:</b> FM65
Authorized Read Notification parameters:
*<b>Device:</b> FMC650
*<b>Firmware version:</b> 03.01.03.Rev.228
*<b>Configurator version:</b> B.FMX6_R.192
==Method of Operation==
*'''Output Control''' – available scenario settings for module Digital output activation/deactivation
When the RTK option is enabled, the device always tries to use RTK sources first and falls back to internal GNSS if needed.
*'''DOUT ON Duration''' – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2}}} should be active or inactive.
*'''Authorization ID List Checking''' - Provides Authorized ID information from a designated source.
**FMB devices that do not have RS232 will have support for 1-Wire and Beacon only.
**FMB devices that do not have RS232 and 1-Wire will have support for Beacon only.
*'''Depend on Ignition''' - Output will be triggered only if ignition is off.
'''Source priority'''
'''Note:''' Authorized read notification is disabled in '''deep sleep''', '''online deep sleep''' and '''ultra deep sleep''' modes.
#'''RS232 (primary RTK source)'''
#:*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.
#'''CAN RTK (secondary RTK source)'''
#:*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.
#'''Internal GNSS (GNS) Fallback'''
#:*If neither RS232 nor CAN provide valid RTK data, the device uses the internal GNSS receiver (GNS) for coordinates.
#'''RTK Disabled'''
#:*If the RTK option is disabled, coordinates are always taken from the internal GNSS receiver.
'''RTK data from CAN'''
When CAN is used as the RTK source, the device reads:
*'''Latitude'''
*'''Longitude'''
*'''Altitude'''
*'''Ground speed'''
*'''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.
==Configurator Setup==
This section describes how to enable RTK as a location source and configure RS232 and CAN usage through the Configurator.
'''Enabling RTK as a location source'''
[[File:Source Location from RTK.png|right]]
#Open the Configurator and connect to the FMC650 device.
#Navigate to the System tab.
#Find the option “Source Location from RTK” in the '''System Settings''' section.
#Set this option to '''Enable'''.
When enabled, the device will use RTK data from RS232/CAN if available, with automatic fallback to internal GNSS.
For advanced configuration (e.g. via commands):
Source Location from RTK <br>
'''Parameter ID:''' 55000 <br>
'''Values:'''
*'''0''' – Disabled (device uses only internal GNSS)
*'''1''' – Enabled (device uses RTK sources if available)
Configuring RS232 for RTK Use
If you plan to use an external RTK receiver via RS232:
#Open the RS232/RS485 tab in the Configurator.
#For COM1 or COM2 (or both), set the mode to RTK.
Relevant parameter IDs:
*'''COM1 mode''' – Parameter ID 151
*'''COM2 mode''' – Parameter ID 173
*'''RTK mode''' – Value 60
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.
[[File:RS232 settings - RTK.png|right]]
'''Using CAN as the RTK Source'''
CAN-based RTK is used in the following cases:
*None of the RS232 COM ports are configured in RTK mode, or
*RS232 RTK data is not valid or not present.
When those conditions are met and valid CAN RTK data is received:
*The device uses CAN as the coordinate source.
*The device continuously monitors the time between RTK messages.
*If CAN RTK messages are delayed by more than 2 seconds, the device automatically reverts to internal GNSS to avoid stale coordinates.
<br>
RTK data taken from CAN includes:
*'''Latitude
*'''Longitude
*'''Altitude
*'''Ground speed
*'''Course
Configuration of RTK over CAN (e.g. PGN, source address, bitrate) depends on your external CAN/ISOBUS/RTK infrastructure and should follow that system’sdocumentation.
'''ISOBUS Data Visibility'''
When used in ISOBUS or similar environments:
[[File:ISOBUS - RTK.png]]
*RTK-related data from CAN is visible in the ISOBUS section of the Configurator.
*This allows you to verify that RTK data is being received and interpreted correctly by the device.
==Active Location Source Monitoring==
To understand which source is currently being used for position data, you can check the '''Location Source''' parameter.
'''Location Source Values'''
In the Configurator:
#Navigate to the '''I/O''' tab (or equivalent I/O monitoring view).
#Find the parameter '''Location Source'''.
[[File:Location source.png]]
Possible values:
*'''0 – GNS'''
Location is taken from the internal GNSS receiver. This is the default when RTK is disabled or when no valid RTK data is available.
*'''1 – RS232'''
Location is taken from the RTK receiver connected via RS232.
*'''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. This helps distinguish normal GNSS use from “RTK expected but not available” situations.
This parameter is used for diagnostics and for confirming that your device is using the intended RTK source.
==NMEA Fix Type Monitoring (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.
'''Configurator Steps'''
#Open the Configurator.
#Go to the I/O tab (or relevant section).
#Locate the parameter '''NMEA Fix Type'''.
[[File:NMEA Fix Type.png]]
'''Note:''' This parameter is '''only available when coordinate data is received via RS232 RTK'''.
'''NMEA Fix Type Values'''
*'''NotValid''' - No valid GNSS fix is available.<br>
*'''GPS''' - Standard GPS fix using satellites only.<br>
Important: iButton Read Notification feature has been replaced with Authorized Read Notification starting from Firmware Ver.03.30.00
Authorized read notification feature allows the control of selected DOUT for a configured period, when Authorized ID is read using 1-Wire, RFID Reader or when Authorized Beacon is detected. If Authorized ID List is empty or Beacon detection is set to All, then any detected ID or Beacon can control selected DOUT. Parameter Depend on Ignition allows to disable DOUT control, while Ignition is being detected. It is necessary to select at least one source for this functionality to work.
Authorized Read Notification parameters:
Output Control – available scenario settings for module Digital output activation/deactivation
DOUT ON Duration – a value in seconds, for how long DOUT1/DOUT2 should be active or inactive.
Authorization ID List Checking - Provides Authorized ID information from a designated source.
FMB devices that do not have RS232 will have support for 1-Wire and Beacon only.
FMB devices that do not have RS232 and 1-Wire will have support for Beacon only.
Depend on Ignition - Output will be triggered only if ignition is off.
Note: Authorized read notification is disabled in deep sleep, online deep sleep and ultra deep sleep modes.
