The following steps describe the process for updating your TrueView vA firmware for both TrueView 2DIS version A and TrueView 3DIS (imaging systems) version A. Version B and later systems have no control box and use a different firmware.
The latest firmware update for all TrueView vA systems is available for download and installation from the Downloads -> Software section of your Reckon account, search for “True View Firmware”, or by logging into the GeoCue FTP site, using your client credentials provided with the initial licensing information, and browsing for the “TrueViewFirmware” folder found in the root. The TrueView vA firmware is the same for all models except the TV250, but the CoreConfiguration file is different for each model.
Current CCU Firmware: v4.0.0 Note: True View 410 systems running v2.0.10 and earlier need to be updated first to v2.0.14 before updating to v4.0.0.
Current CCU Firmware for TV250: v3.0.5.2
Current Camera Firmware: v00.72.01
- The TrueView firmware downloaded from the users Geocue FTP account which contains the folders “Camera” and “CCU”. Within the CCU folder will be individual firmware copies specific to your sensor model (e.g. TrueView515). Within this folder will contain the firmware.zip and the updated CoreConfiguration.json for your sensor model. Do not unzip this “firmware.zip” file. The TrueView camera firmware is provided as a firmware.bin file. It is important not to get the two mixed up!
- Copy the firmware.zip compressed (zipped) folder and CoreConfiguration.json from the applicable system model folder to the top level of the UMS drive for the TrueView System.
- Plug the UMS drive into the TrueView System.
- When installing firmware v3.0.5.2 or newer over v3.0.5.1 or older firmware, the TrueView camera firmware must be updated as well to v00.72.01. Otherwise, the cameras should be already updated and the camera update instructions here can be skipped.
- Remove the SD cards from both cameras and insert them into a laptop.
- If the flight photos currently on them have not been backed up, do so now.
- Erase all data from the two camera SD cards.
- Copy the provided firmware.bin, note the bin format, not the zipped folder, (version 72.01) file into the top level of each camera SD card.
- Re-insert both camera SD cards into the cameras.
- Connect the TrueView controller box to TrueView system.
- Power on the TrueView system.
- All three lights will blink yellow initially.
- After roughly 5 seconds, the SYS light will blink white. This indicates the firmware upgrade is in progress.
- After no more than ten minutes, the SYS light changes to solid white indicating the update has completed. For systems with a readout display, it will say, “Firmware Updated”.
- If the update progress exceeds ten minutes, power off the TrueView system and check the update.log file on the UMS for messages.
- Once complete, the system will begin its normal start up procedure. The battery light will blink until the battery voltage is checked. The light will then turn a solid green, yellow, or red to indicate the battery level. Once the TrueView LEDs reach this state, move to step 7. See the model specific Hardware Users Guide for more information on the light sequences during system startup.
- Power off the TrueView system.
- Remove the SD cards from both cameras and insert into a laptop.
- The firmware.bin file should no longer be present at this point, indicating a successful update.
- Replace the SD cards into their respective cameras.
- Remove the UMS drive from the TrueView system and insert into a laptop.
- The zipped firmware folder should no longer be present on the UMS.
- A file named “Update.log” should now be present.
- When updating to firmware v2.2.x or later from an earlier version, there may be numerous files dumped from the internal memory to clear it before the first Cycle with the later firmware.
- Open the update log and verify the firmware has been updated to the latest version, “update True View firmware to 4.0.0”.
- Ensure you have a saved copy of your System Configuration file (SCF), and the Core Configuration file (CCF) that comes with the firmware update somewhere other than the UMS.
- After confirming a successful update of the firmware, ensure you have a saved copy of your System Configuration file (SCF), and the Core Configuration file (CCF) that comes with the firmware update somewhere other than the UMS. Then, format the UMS to ExFAT. Always perform a full format even if the UMS is already in the ExFAT format as it helps reset the UMS to ready it for continued use.
- Copy your saved System Configuration file (SCF), and the Core Configuration file (CCF) that comes with the firmware update back to the UMS. The CCF must always come from the firmware being installed as parameters are added/modified/removed with new releases. However, you will need to verify any settings you may have customized so they’re not reset to defaults, for example, image transfer on wind-down or proximity mode, and most importantly, ensure the “AOSAvailable” parameter in the CCF file is set to zero for all models, except the TV250, where it should be set to two. Please note:
- The CCF file version may change and so will the last modified date.
- The GNSS_lever_arm values do not need to match between the old and new CCF file so long as the GNSS_lever_arm_change parameter is set to “false” in the new file. Which is what it should be unless you’re doing a new install on a different airframe type.
- The camera SD Cards should be formatted at this time using the built-in format option in the CCF for CCU firmware v3.0.7.1 and later, with camera firmware v00.72.01.
- In CCFSection8, set both the “CameraStorageFormat” and “CamereStorageFormatConfirm” to true in the CCF on the UMS.
- Start the system to format the camera SD Cards during initialization.
- Both the “CameraStorageFormat” and “CamereStorageFormatConfirm” in the CCF will be set back to false during startup so that subsequent initializations will not format again until you manually modify the CCF requesting them to be formatted.
- Run a test Cycle to verify everything is functioning as expected.
