Title Page

  • Camera Assembly Version (SPIKE. LINUS etc)

  • Reason for maintenance/disassembly (test, focus, change config, etc)

  • Conducted on

  • Prepared by

  • Address
  • Personnel


1. Rack test (est 20 mins plus setup time if no faults found)

  • 1.1 Apply 24V ground power and check PMU powers up with no CB trips.

  • 1.2 Plug in monitor to PXI, power up PXI and check console for errors.

  • 1.3 Plug in monitor toServer, power up Crystal Server and check console for errors.

  • 1.4 Connect to WiFi and ping the server, PXI and POS-AV on, and respectively.

  • 1.5 Power up the POSAV and check for green lights on LAN, PPS (antenna connected) and IMU (tube connected).

2. Camera Tube Test (est 2 hours plus setup time if no faults found)

  • 2.1 Apply power to camera tube (either via rack or test PMU)

  • 2.2 Power up each camera. Check input voltage (either via screen or Ethernet)

  • 2.3 Ping each Camera

  • 2.4 Run FE2 focus cycle on each camera.

  • 2.5 Conduct Lens calibration procedure and publish results.

  • 2.6 Energise servo motor. Park, Arm, Zero and Run.

  • 2.7 Capture logs and check the motion and velocity of tube during exposure period.

  • 2.8 Ensure logs match the number of swathes and step in the test

  • 2.9 Ensure times in the log are in UTC, match the file timestamps and are consistent with the test timing.

  • 2.10 Tether the cameras and run a test capturing video over two swathes. Then check:

  • 2.10.1 Logs contain correct number of steps

  • 2.10.2 Clips contain the expected number of clips (noting known issue that first and last frame will be missing when tethered (does this happen for MAG SSD?)

3. System Test (Bench) (est 4 hours if no faults found)

  • 3.1 Conduct the Rack and Camera Tube tests as described above.

  • 3.2 Running the POSAV controller app, confirm that the EVENT1 events are logged during the swathe test.

  • 3.3 Run a stress test with cameras tethered. Two flight lines of at least 10 mins each. Check:

  • 3.3.1 Consistent logging and clip frame counts for all cameras.

  • 3.3.2 No faults

4. System Test (On ACFT)

  • This test only needs to be run after a hardware or software modification. For an abbreviated version of this test see the ICA data and manual.

  • 4.1 This test only needs to be run when after a hardware of software modification or after refitting the system to the aircraft. A shorter daily procedure is provided in XXXXX.

  • 4.2 Run a ‘5 minute’ version of the stress test and check logs and frames.

  • 4.3 Test each UI feature (full survey workflow).

  • 4.4 Test EVENT1, PPS and other log events as required.


  • Other comments

Sign Off

  • Operator/Pilot's signature

  • QA signature

The templates available in our Public Library have been created by our customers and employees to help get you started using SafetyCulture's solutions. The templates are intended to be used as hypothetical examples only and should not be used as a substitute for professional advice. You should seek your own professional advice to determine if the use of a template is permissible in your workplace or jurisdiction. You should independently determine whether the template is suitable for your circumstances.