TrueView 435 Hardware User Guide
23
TrueView 435 Hardware User Guide
10/26/2021
The System Configuration file (SCF), SystemConfiguration.json, must reside on the TrueView USB
Mass Storage and is copied into the Cycle\System folder upon creation of each Cycle. The SCF contains
information on the calibration parameters of all components for each TrueView system and is used by
TrueView EVO to process TrueView data. The latest calibration file for each sensor is stored on the
TrueView Reckon portal.
Core Configuration File (CCF)
TrueView System settings are stored internally to the system but can be changed by modifying the
CoreConfiguration.json file on the UMS. The system identifies if the file has been modified, then
operates accordingly. Features may be turned on or off by using a true or false Boolean in the Core
Configuration file. Other fields can be configured with a numeric value, such as the Battery Status
Percentage or Proximity Mode Distance.
Note: It is recommended to open and modify the Core Configuration file with
The following sections describe the most common sections of the Core Configuration file that a user
may wish to modify.
CCFSection6
–
POS
Figure 32 - Core Configuration - POS
This section is applicable for CCU firmware v2.1.7 and later.
If the “GNSS_lever_arm_change” is
true
, the TrueView is configured to update the lever arms in the
APX unit to the values ascribed in this section. A user should only modify “GNSS_lever_arm_x”,
“GNSS_lever_arm_y”, or “GNSS_lever_arm_z” if they are not using the system on a drone integrated
by GeoCue. Updating the lever arms using this section of the Core Configuration file replaces the need
to log into the APX-15 to update those values. See
Measuring GNSS Lever Arm Offsets
in this guide.
The values shown in Figure 32 are the standard TrueView 410 mounted on an M600 with the GNSS
antenna secured on the top mounting plate not integral to the control box with an LED readout.