Introduction:This guide will provide you with an understanding of what OxTS products offer CAN, the features offered and best practice for setup along with troubleshooting advice. |
|
||||||||||||
Contents:
|
OxTS Products that offer CAN features:
|
||||||||||||
CAN overviewWhat is CAN?The Controller Area Network (CAN) is used in e.g. vehicles for communication between ECUs, sensors and actuators. Use with OxTS productsCAN enables multiple sensors including OxTS RT and Range products to be used in conjunction to output data in real time to a centralised logger or monitoring system. Another setup could be using an OxTS RT as the centralised data hub to store its own INS (Inertial Navigation System) data along with CAN messages (up to 12) from other input sources. CAN protocolsCAN 2.0 - Default OxTS protocol, data rates up to 1Mbit/s. CAN FD - Latest protocol supporting data rates up to 8Mbit/s. DBC filesA CAN DBC file lets you convert raw CAN bus data to physical, readable data. Hardware considerationsCAN Cable - You will require a cable to connect your CAN devices that features a 120 Ohm terminating resistor between CAN High and CAN Low. This is a feature of the CAN bus. You are advised to always connect the grounds of the systems as many systems will not work unless the ground is connected.
|
![]() |
||||||||||||
OxTS CAN overviewFeatures and availability
|
|||||||||||||
OxTS CAN messagesOxTS standard CAN messages are divided into two main groups, RT and RT-Range messages. RT Inertial Navigation Systems (INS) output:
RT-Range systems output: As above they output RT INS information, identified as Hunter unit with the addition of:
|
OxTS CAN messages
|
||||||||||||
OxTS CAN configuration software |
|
||||||||||||
NAVconfig - CAN OutputSoftware - Location:
Notes: *Options only available for CAN FD. **CAN FD only available on RT3000v3 & RT500s |
CAN Output reference:
|
||||||||||||
NAVconfig - CAN AcquisitionSoftware - Location: |
CAN Acquisition reference:See CAN Output reference for details on unlabelled Acquisition configuration options.
|
||||||||||||
RT-Range Configuration Wizard - CAN Output |
|||||||||||||
|
Software - Location:
|
||||||||||||
|
|
||||||||||||
|
General (Tab)Location: CAN Message Configuration (Wizard) > General (Tab) opens in new window Settings:
|
||||||||||||
|
Message tabsRT-Range messages are grouped by type and sorted into tabbed tables. Core message tabs are always visible (eg. Hunter) but additional message tabs (eg. Target) become available when features are enabled. Message output is enabled ticking the checkbox. Individual message identifiers can by modified using the input. Individual message data rate can be changed using the drop down selector.
|
||||||||||||
CAN Output configurationCAN Output is available from OxTS RT and RT-Range S Hunter products. |
|||||||||||||
RT CAN Output setupSoftware - Location:Steps:
|
Note: Enable CAN FDs increased output rate by:
|
||||||||||||
RT-Range S Hunter CAN output setupSoftware - Location:RT-Range - Real-Time Display > Configure RT-Range > Options (Section) > CAN (Settings) Steps:
|
Note: Configure CAN options AFTER completing all previous RT-Range sections, to see all available CAN messages. Maximum message exceeded warning: |
||||||||||||
RT3000v3 Hunter CAN Output configuration:The RT3000v3 is a combination of two hardware products into one. Because of this, configuring CAN output sometimes requires the use of two software applications (NAVconfig and Configure RT-Range). It is important to understand what settings are configurable in each software application and what messages are available and where. For a general overview of where to enable messages see OxTS CAN Messages diagram (right). Software CAN output responsibilitiesNAVconfig - All output settings and RT related messages. Configure RT-Range - Range related messages. |
OxTS CAN messages
|
||||||||||||
RT3000v3 CAN Output configuration - RT messages onlySetup unit identical to RT CAN Output setup instructions. |
|
||||||||||||
RT3000v3 CAN Output configuration - Including RT-Range messages |
|
||||||||||||
Setup(RT3000v3 CAN Output configuration - RT + RT-Range messages)Turn CAN output on in NAVconfig
Configure RT-Range
|
|
||||||||||||
Modify configuration(RT3000v3 CAN Output configuration - RT + RT-Range messages)Modifying RT messages or data output settingsWhen modifying RT messages you modify in NAVconfig and must then update the RT-Range configuration as Hunter messages are related.
|
|
||||||||||||
Modifying RT-Range CAN messages onlyWhen modifying RT-Range only messages this can be done with Configure RT-Range solely.
|
|
||||||||||||
Disabling CAN output(RT3000v3 CAN Output configuration - RT + RT-Range messages)When disabling CAN output without changing your Range configuration you must do so in the following order to avoid conflict issues:
|
|
||||||||||||
CAN Acquisition configurationOnly OxTS RT products support CAN Acquisition feature. |
|||||||||||||
RT CAN Acquisition setupSoftware - Location:
|
Note: CAN Acquisition can log a max of 12 messages. If enable all selected on a list greater than 12, only the first 12 will be enabled. |
||||||||||||
Troubleshooting |
|
||||||||||||
"Locked" RT-Range messages |
Issue: CAN messages "Locked" in Configure RT-Range. Cause: CAN output has been disabled without removing RT-Range CAN messages first. Solution 1: Enable CAN Output in NAVconfig then follow Disabling CAN output. Solution 2: Warning -This will reset all RT-Range configuration settings. Reset RT-Range configuration by committing a default configuration file with no CAN messages enabled to the unit. |
||||||||||||
RT-Range CAN "Disabled" |
Issue: Cannot configure RT-Range CAN messages as showing as "Disabled"
Cause 1: Using an RT3000v3 and you have not Enabled CAN output in NAVconfig. Solution 1:
Cause 2: Using an RT3000v3 and CAN output enabled but you are using a default configuration. Configure RT-Range needs to read the CAN configuration from an RT3000v3 Range unit so the software knows what CAN settings have been enabled. Solution 2: In Configure RT-Range - Do not use default settings, instead select to read settings from range unit or follow Setup steps. |
||||||||||||
NAVconfig enabled RT messages "Locked" |
Issue: You wish to disable/modify RT CAN messages but they appear locked enabled in NAVconfig. Cause: Configuration conflict between software applications. Solution 1: Warning -This will reset all RT-Range configuration settings. Reset RT-Range configuration by committing a default configuration file with no CAN messages enabled to the unit. Solution 2: Modify RT CAN output whilst keeping your other configuration settings using NAVconfig and Configure RT-Range. > NAVconfig:
> Configure RT-Range:
|
Comments
0 comments
Please sign in to leave a comment.