2019-05-15T20:25:25.875Z,1557951925.875 [Supervisor](DEBUG): Initializing supervisor.
2019-05-15T20:25:25.878Z,1557951925.878 [SyncHandler](DEBUG): Created PCaller Thread at 404514E0
2019-05-15T20:25:25.879Z,1557951925.879 [SyncHandler](INFO): Protected caller Thread ID is 2686
2019-05-15T20:25:25.879Z,1557951925.879 [ComponentRegistry](DEBUG): Component "controlThread" handled in its own thread.
2019-05-15T20:25:25.880Z,1557951925.880 [controlThread ThreadHandler](DEBUG): Created PCaller Thread at 404814E0
2019-05-15T20:25:25.881Z,1557951925.881 [controlThread ThreadHandler](INFO): Protected caller Thread ID is 2687
2019-05-15T20:25:25.884Z,1557951925.884 [ComponentRegistry](DEBUG): SyncComponent "CycleStarter" handled in the control thread.
2019-05-15T20:25:25.896Z,1557951925.896 [ComponentRegistry](DEBUG): Component "CommandLine" handled in its own thread.
2019-05-15T20:25:25.897Z,1557951925.897 [CommandLine ThreadHandler](DEBUG): Created PCaller Thread at 404B14E0
2019-05-15T20:25:25.897Z,1557951925.897 [CommandLine ThreadHandler](INFO): Protected caller Thread ID is 2688
2019-05-15T20:25:25.898Z,1557951925.898 [ComponentRegistry](DEBUG): Component "logger" handled in its own thread.
2019-05-15T20:25:25.899Z,1557951925.899 [logger ThreadHandler](DEBUG): Created PCaller Thread at 404E14E0
2019-05-15T20:25:25.899Z,1557951925.899 [logger ThreadHandler](INFO): Protected caller Thread ID is 2689
2019-05-15T20:25:25.902Z,1557951925.902 [ComponentRegistry](DEBUG): SyncComponent "LogSplitter" handled in the control thread.
2019-05-15T20:25:25.902Z,1557951925.902 [Supervisor](INFO): Looking for Config files in directory: Config/
2019-05-15T20:25:25.903Z,1557951925.903 [Supervisor](INFO): Opening Config file at: Config/vehicle.cfg
2019-05-15T20:25:26.338Z,1557951926.338 [ComponentRegistry](DEBUG): Loaded Config Component "Config/vehicle
2019-05-15T20:25:26.338Z,1557951926.338 [Supervisor](INFO): Opening Config file at: Config/Derivation.cfg
2019-05-15T20:25:26.484Z,1557951926.484 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Derivation
2019-05-15T20:25:26.484Z,1557951926.484 [Supervisor](INFO): Opening Config file at: Config/Guidance.cfg
2019-05-15T20:25:26.566Z,1557951926.566 [Supervisor](INFO): Opening Config file at: Config/Sample.cfg
2019-05-15T20:25:26.665Z,1557951926.665 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Sample
2019-05-15T20:25:26.666Z,1557951926.666 [Supervisor](INFO): Opening Config file at: Config/secure.cfg
2019-05-15T20:25:26.762Z,1557951926.762 [ComponentRegistry](DEBUG): Loaded Config Component "Config/secure
2019-05-15T20:25:26.762Z,1557951926.762 [Supervisor](INFO): Opening Config file at: Config/Science.cfg
2019-05-15T20:25:27.149Z,1557951927.149 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Science
2019-05-15T20:25:27.150Z,1557951927.150 [Supervisor](INFO): Opening Config file at: Config/workSite.cfg
2019-05-15T20:25:27.253Z,1557951927.253 [ComponentRegistry](DEBUG): Loaded Config Component "Config/workSite
2019-05-15T20:25:27.254Z,1557951927.254 [Supervisor](INFO): Opening Config file at: Config/Simulator.cfg
2019-05-15T20:25:27.722Z,1557951927.722 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Simulator
2019-05-15T20:25:27.723Z,1557951927.723 [Supervisor](INFO): Opening Config file at: Config/logger.cfg
2019-05-15T20:25:27.933Z,1557951927.933 [ComponentRegistry](DEBUG): Loaded Config Component "Config/logger
2019-05-15T20:25:27.933Z,1557951927.933 [Supervisor](INFO): Opening Config file at: Config/Servo.cfg
2019-05-15T20:25:28.245Z,1557951928.245 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Servo
2019-05-15T20:25:28.246Z,1557951928.246 [Supervisor](INFO): Opening Config file at: Config/Navigation.cfg
2019-05-15T20:25:28.463Z,1557951928.463 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Navigation
2019-05-15T20:25:28.464Z,1557951928.464 [Supervisor](INFO): Opening Config file at: Config/Estimation.cfg
2019-05-15T20:25:28.608Z,1557951928.608 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Estimation
2019-05-15T20:25:28.609Z,1557951928.609 [Supervisor](INFO): Opening Config file at: Config/Sensor.cfg
2019-05-15T20:25:29.288Z,1557951929.288 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Sensor
2019-05-15T20:25:29.288Z,1557951929.288 [Supervisor](INFO): Opening Config file at: Config/Control.cfg
2019-05-15T20:25:30.042Z,1557951930.042 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Control
2019-05-15T20:25:30.042Z,1557951930.042 [Supervisor](INFO): Opening Config file at: Config/BIT.cfg
2019-05-15T20:25:30.252Z,1557951930.252 [ComponentRegistry](DEBUG): Loaded Config Component "Config/BIT
2019-05-15T20:25:30.255Z,1557951930.255 [Supervisor](INFO): Looking for Config files in directory: Config/lrauv-triton/
2019-05-15T20:25:30.255Z,1557951930.255 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/vehicle.cfg
2019-05-15T20:25:30.448Z,1557951930.448 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/secure.cfg
2019-05-15T20:25:30.532Z,1557951930.532 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/Science.cfg
2019-05-15T20:25:30.660Z,1557951930.660 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/Simulator.cfg
2019-05-15T20:25:30.746Z,1557951930.746 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/Battery.cfg
2019-05-15T20:25:30.977Z,1557951930.977 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Battery
2019-05-15T20:25:30.977Z,1557951930.977 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/logger.cfg
2019-05-15T20:25:31.074Z,1557951931.074 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/Servo.cfg
2019-05-15T20:25:31.187Z,1557951931.187 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/Navigation.cfg
2019-05-15T20:25:31.283Z,1557951931.283 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/Sensor.cfg
2019-05-15T20:25:31.441Z,1557951931.441 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/Control.cfg
2019-05-15T20:25:31.543Z,1557951931.543 [Supervisor](INFO): Opening Config file at: Config/lrauv-triton/BIT.cfg
2019-05-15T20:25:31.644Z,1557951931.644 [Supervisor](INFO): Looking for Config files in directory: Config/lrauv-triton/root/
2019-05-15T20:25:31.644Z,1557951931.644 [Supervisor](IMPORTANT): Reading configuration overrides from Data/persisted.cfg
2019-05-15T20:25:31.647Z,1557951931.647 [Module Loader](DEBUG): Loading Module at Modules/Sample.so
2019-05-15T20:25:31.661Z,1557951931.661 [Module Loader](DEBUG): Loaded Module: Sample (This is a Sample Module of Sample Components)
2019-05-15T20:25:31.661Z,1557951931.661 [Module Loader](DEBUG): Loading Module at Modules/Control.so
2019-05-15T20:25:31.726Z,1557951931.726 [VerticalControl](DEBUG): Construct VerticalControl.
2019-05-15T20:25:31.842Z,1557951931.842 [VerticalControl] Loaded
2019-05-15T20:25:31.842Z,1557951931.842 [ComponentRegistry](DEBUG): SyncComponent "VerticalControl" handled in the control thread.
2019-05-15T20:25:31.843Z,1557951931.843 [HorizontalControl](DEBUG): Construct HorizontalControl.
2019-05-15T20:25:31.913Z,1557951931.913 [HorizontalControl] Loaded
2019-05-15T20:25:31.913Z,1557951931.913 [ComponentRegistry](DEBUG): SyncComponent "HorizontalControl" handled in the control thread.
2019-05-15T20:25:31.914Z,1557951931.914 [SpeedControl](DEBUG): Construct SpeedControl.
2019-05-15T20:25:31.919Z,1557951931.919 [SpeedControl] Loaded
2019-05-15T20:25:31.919Z,1557951931.919 [ComponentRegistry](DEBUG): SyncComponent "SpeedControl" handled in the control thread.
2019-05-15T20:25:31.920Z,1557951931.920 [LoopControl](DEBUG): Construct LoopControl.
2019-05-15T20:25:31.921Z,1557951931.921 [LoopControl] Loaded
2019-05-15T20:25:31.921Z,1557951931.921 [ComponentRegistry](DEBUG): SyncComponent "LoopControl" handled in the control thread.
2019-05-15T20:25:31.921Z,1557951931.921 [Module Loader](DEBUG): Loaded Module: Control (Contains the Control components, such as Depth, Heading, and Speed Control)
2019-05-15T20:25:31.922Z,1557951931.922 [Module Loader](DEBUG): Loading Module at Modules/Servo.so
2019-05-15T20:25:32.051Z,1557951932.051 [BuoyancyServo] Loaded
2019-05-15T20:25:32.051Z,1557951932.051 [ComponentRegistry](DEBUG): SyncComponent "BuoyancyServo" handled in the control thread.
2019-05-15T20:25:32.062Z,1557951932.062 [ElevatorServo] Loaded
2019-05-15T20:25:32.063Z,1557951932.063 [ComponentRegistry](DEBUG): SyncComponent "ElevatorServo" handled in the control thread.
2019-05-15T20:25:32.073Z,1557951932.073 [MassServo] Loaded
2019-05-15T20:25:32.074Z,1557951932.074 [ComponentRegistry](DEBUG): SyncComponent "MassServo" handled in the control thread.
2019-05-15T20:25:32.085Z,1557951932.085 [RudderServo] Loaded
2019-05-15T20:25:32.085Z,1557951932.085 [ComponentRegistry](DEBUG): SyncComponent "RudderServo" handled in the control thread.
2019-05-15T20:25:32.096Z,1557951932.096 [ThrusterServo] Loaded
2019-05-15T20:25:32.096Z,1557951932.096 [ComponentRegistry](DEBUG): SyncComponent "ThrusterServo" handled in the control thread.
2019-05-15T20:25:32.097Z,1557951932.097 [Module Loader](DEBUG): Loaded Module: Servo (This is the module containing motor controllers)
2019-05-15T20:25:32.097Z,1557951932.097 [Module Loader](DEBUG): Loading Module at Modules/Derivation.so
2019-05-15T20:25:32.137Z,1557951932.137 [DepthRateCalculator] Loaded
2019-05-15T20:25:32.137Z,1557951932.137 [ComponentRegistry](DEBUG): SyncComponent "DepthRateCalculator" handled in the control thread.
2019-05-15T20:25:32.142Z,1557951932.142 [PitchRateCalculator] Loaded
2019-05-15T20:25:32.143Z,1557951932.143 [ComponentRegistry](DEBUG): SyncComponent "PitchRateCalculator" handled in the control thread.
2019-05-15T20:25:32.158Z,1557951932.158 [SpeedCalculator] Loaded
2019-05-15T20:25:32.158Z,1557951932.158 [ComponentRegistry](DEBUG): SyncComponent "SpeedCalculator" handled in the control thread.
2019-05-15T20:25:32.179Z,1557951932.179 [TempGradientCalculator] Loaded
2019-05-15T20:25:32.179Z,1557951932.179 [ComponentRegistry](DEBUG): SyncComponent "TempGradientCalculator" handled in the control thread.
2019-05-15T20:25:32.185Z,1557951932.185 [YawRateCalculator] Loaded
2019-05-15T20:25:32.185Z,1557951932.185 [ComponentRegistry](DEBUG): SyncComponent "YawRateCalculator" handled in the control thread.
2019-05-15T20:25:32.214Z,1557951932.214 [ElevatorOffsetCalculator] Loaded
2019-05-15T20:25:32.215Z,1557951932.215 [ComponentRegistry](DEBUG): SyncComponent "ElevatorOffsetCalculator" handled in the control thread.
2019-05-15T20:25:32.215Z,1557951932.215 [Module Loader](DEBUG): Loaded Module: Derivation (Contains the base derivation components)
2019-05-15T20:25:32.216Z,1557951932.216 [Module Loader](DEBUG): Loading Module at Modules/Navigation.so
2019-05-15T20:25:32.320Z,1557951932.320 [DeadReckonUsingMultipleVelocitySources] Loaded
2019-05-15T20:25:32.320Z,1557951932.320 [ComponentRegistry](DEBUG): SyncComponent "DeadReckonUsingMultipleVelocitySources" handled in the control thread.
2019-05-15T20:25:32.341Z,1557951932.341 [NavChart] Loaded
2019-05-15T20:25:32.341Z,1557951932.341 [ComponentRegistry](DEBUG): SyncComponent "NavChart" handled in the control thread.
2019-05-15T20:25:32.345Z,1557951932.345 [UniversalFixResidualReporter] Loaded
2019-05-15T20:25:32.345Z,1557951932.345 [ComponentRegistry](DEBUG): SyncComponent "UniversalFixResidualReporter" handled in the control thread.
2019-05-15T20:25:32.346Z,1557951932.346 [Module Loader](DEBUG): Loaded Module: Navigation (Contains the base navigation components)
2019-05-15T20:25:32.346Z,1557951932.346 [Module Loader](DEBUG): Loading Module at Modules/Sensor.so
2019-05-15T20:25:32.703Z,1557951932.703 [AHRS_M2] Loaded
2019-05-15T20:25:32.703Z,1557951932.703 [ComponentRegistry](DEBUG): SyncComponent "AHRS_M2" handled in the control thread.
2019-05-15T20:25:32.780Z,1557951932.780 [DataOverHttps] Loaded
2019-05-15T20:25:32.780Z,1557951932.780 [ComponentRegistry](DEBUG): Component "DataOverHttps" handled in its own thread.
2019-05-15T20:25:32.782Z,1557951932.782 [DataOverHttps ThreadHandler](DEBUG): Created PCaller Thread at 408114E0
2019-05-15T20:25:32.782Z,1557951932.782 [DataOverHttps ThreadHandler](INFO): Protected caller Thread ID is 2768
2019-05-15T20:25:32.795Z,1557951932.795 [Depth_Keller] Loaded
2019-05-15T20:25:32.796Z,1557951932.796 [ComponentRegistry](DEBUG): SyncComponent "Depth_Keller" handled in the control thread.
2019-05-15T20:25:32.800Z,1557951932.800 [DropWeight] Loaded
2019-05-15T20:25:32.801Z,1557951932.801 [ComponentRegistry](DEBUG): SyncComponent "DropWeight" handled in the control thread.
2019-05-15T20:25:32.898Z,1557951932.898 [NAL9602] Loaded
2019-05-15T20:25:32.898Z,1557951932.898 [ComponentRegistry](DEBUG): SyncComponent "NAL9602" handled in the control thread.
2019-05-15T20:25:32.914Z,1557951932.914 [Onboard] Loaded
2019-05-15T20:25:32.915Z,1557951932.915 [ComponentRegistry](DEBUG): SyncComponent "Onboard" handled in the control thread.
2019-05-15T20:25:32.918Z,1557951932.918 [Radio_Surface] Loaded
2019-05-15T20:25:32.918Z,1557951932.918 [ComponentRegistry](DEBUG): Component "Radio_Surface" handled in its own thread.
2019-05-15T20:25:32.919Z,1557951932.919 [Radio_Surface ThreadHandler](DEBUG): Created PCaller Thread at 408414E0
2019-05-15T20:25:32.920Z,1557951932.920 [Radio_Surface ThreadHandler](INFO): Protected caller Thread ID is 2769
2019-05-15T20:25:34.409Z,1557951934.409 [BPC1] Loaded
2019-05-15T20:25:34.409Z,1557951934.409 [ComponentRegistry](DEBUG): SyncComponent "BPC1" handled in the control thread.
2019-05-15T20:25:34.421Z,1557951934.421 [BR_Ping1D] Loaded
2019-05-15T20:25:34.421Z,1557951934.421 [ComponentRegistry](DEBUG): SyncComponent "BR_Ping1D" handled in the control thread.
2019-05-15T20:25:34.422Z,1557951934.422 [Module Loader](DEBUG): Loaded Module: Sensor (Contains the sensor components)
2019-05-15T20:25:34.422Z,1557951934.422 [Module Loader](DEBUG): Loading Module at Modules/Estimation.so
2019-05-15T20:25:34.672Z,1557951934.672 [Module Loader](DEBUG): Loaded Module: Estimation (Contains the base estimation components)
2019-05-15T20:25:34.672Z,1557951934.672 [Module Loader](DEBUG): Loading Module at Modules/Simulator.so
2019-05-15T20:25:34.851Z,1557951934.851 [Module Loader](DEBUG): Loaded Module: Simulator (This is the module containing the Simulator)
2019-05-15T20:25:34.851Z,1557951934.851 [Module Loader](DEBUG): Loading Module at Modules/Trigger.so
2019-05-15T20:25:34.877Z,1557951934.877 [Module Loader](DEBUG): Loaded Module: Trigger (Contains triggers for use in missions)
2019-05-15T20:25:34.877Z,1557951934.877 [Module Loader](DEBUG): Loading Module at Modules/Science.so
2019-05-15T20:25:35.291Z,1557951935.291 [CTD_NeilBrown] Loaded
2019-05-15T20:25:35.291Z,1557951935.291 [ComponentRegistry](DEBUG): Component "CTD_NeilBrown" handled in its own thread.
2019-05-15T20:25:35.292Z,1557951935.292 [CTD_NeilBrown ThreadHandler](DEBUG): Created PCaller Thread at 409CD4E0
2019-05-15T20:25:35.293Z,1557951935.293 [CTD_NeilBrown ThreadHandler](INFO): Protected caller Thread ID is 2770
2019-05-15T20:25:35.302Z,1557951935.302 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_density
2019-05-15T20:25:35.307Z,1557951935.307 [CTD_Seabird](INFO): created writer for : sea_water_density
2019-05-15T20:25:35.309Z,1557951935.309 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): depth
2019-05-15T20:25:35.314Z,1557951935.314 [CTD_Seabird](INFO): created writer for : depth
2019-05-15T20:25:35.314Z,1557951935.314 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_pressure
2019-05-15T20:25:35.319Z,1557951935.319 [CTD_Seabird](INFO): created writer for : sea_water_pressure
2019-05-15T20:25:35.320Z,1557951935.320 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_salinity
2019-05-15T20:25:35.325Z,1557951935.325 [CTD_Seabird](INFO): created writer for : sea_water_salinity
2019-05-15T20:25:35.325Z,1557951935.325 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_temperature
2019-05-15T20:25:35.330Z,1557951935.330 [CTD_Seabird](INFO): created writer for : sea_water_temperature
2019-05-15T20:25:35.331Z,1557951935.331 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_electrical_conductivity
2019-05-15T20:25:35.336Z,1557951935.336 [CTD_Seabird](INFO): created writer for : sea_water_electrical_conductivity
2019-05-15T20:25:35.336Z,1557951935.336 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): speed_of_sound_in_sea_water
2019-05-15T20:25:35.341Z,1557951935.341 [CTD_Seabird](INFO): created writer for : speed_of_sound_in_sea_water
2019-05-15T20:25:35.368Z,1557951935.368 [CTD_Seabird] Loaded
2019-05-15T20:25:35.368Z,1557951935.368 [ComponentRegistry](DEBUG): Component "CTD_Seabird" handled in its own thread.
2019-05-15T20:25:35.369Z,1557951935.369 [CTD_Seabird ThreadHandler](DEBUG): Created PCaller Thread at 409FD4E0
2019-05-15T20:25:35.370Z,1557951935.370 [CTD_Seabird ThreadHandler](INFO): Protected caller Thread ID is 2771
2019-05-15T20:25:35.384Z,1557951935.384 [PAR_Licor] Loaded
2019-05-15T20:25:35.384Z,1557951935.384 [ComponentRegistry](DEBUG): SyncComponent "PAR_Licor" handled in the control thread.
2019-05-15T20:25:35.432Z,1557951935.432 [WetLabsBB2FL] Loaded
2019-05-15T20:25:35.433Z,1557951935.433 [ComponentRegistry](DEBUG): Component "WetLabsBB2FL" handled in its own thread.
2019-05-15T20:25:35.434Z,1557951935.434 [WetLabsBB2FL ThreadHandler](DEBUG): Created PCaller Thread at 40A2D4E0
2019-05-15T20:25:35.434Z,1557951935.434 [WetLabsBB2FL ThreadHandler](INFO): Protected caller Thread ID is 2772
2019-05-15T20:25:35.435Z,1557951935.435 [Module Loader](DEBUG): Loaded Module: Science (Contains the science components)
2019-05-15T20:25:35.435Z,1557951935.435 [Module Loader](DEBUG): Loading Module at Modules/Guidance.so
2019-05-15T20:25:35.967Z,1557951935.967 [Module Loader](DEBUG): Loaded Module: Guidance (Contains behaviors and commands)
2019-05-15T20:25:35.967Z,1557951935.967 [Module Loader](DEBUG): Loading Module at Modules/BIT.so
2019-05-15T20:25:36.346Z,1557951936.346 [SBIT](DEBUG): Construct Startup Built In Test.
2019-05-15T20:25:36.388Z,1557951936.388 [SBIT] Loaded
2019-05-15T20:25:36.389Z,1557951936.389 [ComponentRegistry](DEBUG): SyncComponent "SBIT" handled in the control thread.
2019-05-15T20:25:36.390Z,1557951936.390 [IBIT](DEBUG): Construct Initiated Built In Test.
2019-05-15T20:25:36.401Z,1557951936.401 [IBIT] Loaded
2019-05-15T20:25:36.402Z,1557951936.402 [ComponentRegistry](DEBUG): SyncComponent "IBIT" handled in the control thread.
2019-05-15T20:25:36.405Z,1557951936.405 [CBIT](DEBUG): Construct Continuous Built In Test.
2019-05-15T20:25:36.545Z,1557951936.545 [CBIT] Loaded
2019-05-15T20:25:36.545Z,1557951936.545 [ComponentRegistry](DEBUG): SyncComponent "CBIT" handled in the control thread.
2019-05-15T20:25:36.546Z,1557951936.546 [Module Loader](DEBUG): Loaded Module: BIT (Contains the BuiltInTest components, such as C Built In Test)
2019-05-15T20:25:36.549Z,1557951936.549 [ComponentRegistry](DEBUG): SyncComponent "MissionManager" handled in the control thread.
2019-05-15T20:25:36.550Z,1557951936.550 [ComponentRegistry](DEBUG): SyncComponent "Reporter" handled in the control thread.
2019-05-15T20:25:36.557Z,1557951936.557 [ComponentRegistry](DEBUG): Component "NavChartDb" handled in its own thread.
2019-05-15T20:25:36.558Z,1557951936.558 [NavChartDb ThreadHandler](DEBUG): Created PCaller Thread at 40B0C4E0
2019-05-15T20:25:36.558Z,1557951936.558 [NavChartDb ThreadHandler](INFO): Protected caller Thread ID is 2773
2019-05-15T20:25:36.563Z,1557951936.563 [Supervisor](INFO): Main Thread ID is 803
2019-05-15T20:25:36.563Z,1557951936.563 [Supervisor](DEBUG): Running supervisor.
2019-05-15T20:25:36.564Z,1557951936.564 [CommandLine ThreadHandler](INFO): Handler Thread ID is 2774
2019-05-15T20:25:36.566Z,1557951936.566 [controlThread ThreadHandler](INFO): Handler Thread ID is 2775
2019-05-15T20:25:36.566Z,1557951936.566 [controlThread](DEBUG): Initializing ControlThread
2019-05-15T20:25:36.567Z,1557951936.567 [VerticalControl](DEBUG): Initialize VerticalControlComponent.
2019-05-15T20:25:36.569Z,1557951936.569 [HorizontalControl](DEBUG): Initialize HorizontalControlComponent.
2019-05-15T20:25:36.570Z,1557951936.570 [SpeedControl](DEBUG): Initialize SpeedControlComponent.
2019-05-15T20:25:36.570Z,1557951936.570 [LoopControl](DEBUG): Initialize LoopControlComponent.
2019-05-15T20:25:36.571Z,1557951936.571 [DepthRateCalculator](DEBUG): Initializing DepthRateCalculator.
2019-05-15T20:25:36.572Z,1557951936.572 [PitchRateCalculator](DEBUG): Initializing PitchRateCalculator.
2019-05-15T20:25:36.572Z,1557951936.572 [SpeedCalculator](DEBUG): Initializing SpeedCalculator.
2019-05-15T20:25:36.572Z,1557951936.572 [TempGradientCalculator](DEBUG): Initializing TempGradientCalculator.
2019-05-15T20:25:36.573Z,1557951936.573 [YawRateCalculator](DEBUG): Initializing YawRateCalculator.
2019-05-15T20:25:36.573Z,1557951936.573 [ElevatorOffsetCalculator](DEBUG): Initializing ElevatorOffsetCalculator.
2019-05-15T20:25:36.574Z,1557951936.574 [NavChart](DEBUG): Initialize NavChart Navigation.
2019-05-15T20:25:36.575Z,1557951936.575 [UniversalFixResidualReporter](DEBUG): Initializing UniversalFixResidualReporter component.
2019-05-15T20:25:36.581Z,1557951936.581 [SBIT](INFO): Initialize SBIT Component.
2019-05-15T20:25:36.582Z,1557951936.582 [SBIT](IMPORTANT): git: 2019-05-01-16-g58f4cc3
2019-05-15T20:25:36.582Z,1557951936.582 [SBIT](INFO): git hash: 58f4cc369d803afb19aea4821bdb4c673a350570
2019-05-15T20:25:36.582Z,1557951936.582 [SBIT](IMPORTANT): Kernel Release: 2.6.27.8
2019-05-15T20:25:36.583Z,1557951936.583 [SBIT](INFO): Kernel Reporting Different Version From Configuration.
Kernel Expected: #1 PREEMPT Tue Dec 18 21:19:28 PST 2018
Kernel Reported: #1 PREEMPT Thu Feb 21 11:17:40 PST 2019
2019-05-15T20:25:36.584Z,1557951936.584 [SBIT](INFO): Beginning SBIT in 28.000000 seconds.
2019-05-15T20:25:36.585Z,1557951936.585 [IBIT](INFO): Initialize IBIT Component.
2019-05-15T20:25:36.586Z,1557951936.586 [CBIT](DEBUG): Initialize CBIT Component.
2019-05-15T20:25:36.587Z,1557951936.587 [logger ThreadHandler](INFO): Handler Thread ID is 2776
2019-05-15T20:25:36.597Z,1557951936.597 [CBIT](DEBUG): Initialized mux pins.
2019-05-15T20:25:36.597Z,1557951936.597 [CBIT](DEBUG): Initializing the watchdog timer.
2019-05-15T20:25:36.605Z,1557951936.605 [DataOverHttps ThreadHandler](INFO): Handler Thread ID is 2777
2019-05-15T20:25:36.606Z,1557951936.606 [DataOverHttps](DEBUG): dashIP=134.89.2.23 starts with a digit so assuming it is a numeric IP
2019-05-15T20:25:36.617Z,1557951936.617 [Radio_Surface ThreadHandler](INFO): Handler Thread ID is 2778
2019-05-15T20:25:36.621Z,1557951936.621 [CBIT](CRITICAL): LAST REBOOT DUE TO WATCHDOG TIMER RESET.
2019-05-15T20:25:36.621Z,1557951936.621 [CBIT](DEBUG): Initializing heartbeat.
2019-05-15T20:25:36.629Z,1557951936.629 [CTD_NeilBrown ThreadHandler](INFO): Handler Thread ID is 2779
2019-05-15T20:25:36.637Z,1557951936.637 [CTD_Seabird ThreadHandler](INFO): Handler Thread ID is 2780
2019-05-15T20:25:36.638Z,1557951936.638 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:25:36.641Z,1557951936.641 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:25:36.643Z,1557951936.643 [WetLabsBB2FL ThreadHandler](INFO): Handler Thread ID is 2782
2019-05-15T20:25:36.644Z,1557951936.644 [WetLabsBB2FL](INFO): Powering down
2019-05-15T20:25:36.670Z,1557951936.670 [NavChartDb ThreadHandler](INFO): Handler Thread ID is 2783
2019-05-15T20:25:36.674Z,1557951936.674 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US1WC07M.000
2019-05-15T20:25:36.674Z,1557951936.674 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US1WC07M.000
2019-05-15T20:25:36.674Z,1557951936.674 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US2WC11M.000
2019-05-15T20:25:36.674Z,1557951936.674 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US2WC11M.000
2019-05-15T20:25:36.675Z,1557951936.675 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US3CA52M.000
2019-05-15T20:25:36.675Z,1557951936.675 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US3CA52M.000
2019-05-15T20:25:36.675Z,1557951936.675 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US4CA60M.000
2019-05-15T20:25:36.675Z,1557951936.675 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US4CA60M.000
2019-05-15T20:25:36.675Z,1557951936.675 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA50M.000
2019-05-15T20:25:36.676Z,1557951936.676 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA50M.000
2019-05-15T20:25:36.676Z,1557951936.676 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA61M.000
2019-05-15T20:25:36.676Z,1557951936.676 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA61M.000
2019-05-15T20:25:36.676Z,1557951936.676 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA62M.000
2019-05-15T20:25:36.676Z,1557951936.676 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA62M.000
2019-05-15T20:25:36.677Z,1557951936.677 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA83M.000
2019-05-15T20:25:36.677Z,1557951936.677 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA83M.000
2019-05-15T20:25:36.693Z,1557951936.693 [CBIT](DEBUG): Deactivating GF circuits.
2019-05-15T20:25:36.693Z,1557951936.693 [CBIT](DEBUG): Deactivating emergency mode.
2019-05-15T20:25:36.729Z,1557951936.729 [CBIT](DEBUG): Backplane powered.
2019-05-15T20:25:36.730Z,1557951936.730 [MissionManager](INFO): Loading Mission: Missions/Startup.xml
2019-05-15T20:25:36.740Z,1557951936.740 [Startup:A.GoToSurface](DEBUG): Construct GoToSurface.
2019-05-15T20:25:36.759Z,1557951936.759 [MissionManager](DEBUG): 
<?xml version="1.0" encoding="UTF-8"?>
<Mission xmlns="Tethys"
       xmlns:Control="Tethys/Control"
       xmlns:Guidance="Tethys/Guidance" 
       xmlns:Units="Tethys/Units"
       xmlns:Universal="Tethys/Universal"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="Tethys http://okeanids.mbari.org/tethys/Xml/Tethys.xsd
                           Tethys/Control http://okeanids.mbari.org/tethys/Xml/Control.xsd
                           Tethys/Guidance http://okeanids.mbari.org/tethys/Xml/Guidance.xsd
                           Tethys/Units http://okeanids.mbari.org/tethys/Xml/Units.xsd
                           Tethys/Universal http://okeanids.mbari.org/tethys/Xml/Universal.xsd"
       Id="Startup">

    <Guidance:GoToSurface>
        <Progression/>
    </Guidance:GoToSurface>

    <Aggregate Id="StartupSatComms">

        <Sequence/>

        <ReadDatum>
            <Timeout Duration="P1M" />
            <Universal:latitude_fix/>
        </ReadDatum>

        <ReadDatum>
            <Timeout Duration="P1M" />
            <Universal:platform_communications/>
        </ReadDatum>

    </Aggregate>

</Mission>


2019-05-15T20:25:36.760Z,1557951936.760 [MissionManager](INFO): Loading Mission: Missions/Default.xml
2019-05-15T20:25:36.831Z,1557951936.831 [MissionManager](INFO): DefineArg Default.ElapsedSinceDefaultStarted = 0.000000 min
2019-05-15T20:25:36.832Z,1557951936.832 [Default:A.Wait](DEBUG): Construct Wait.
2019-05-15T20:25:36.842Z,1557951936.842 [Default:B.GoToSurface](DEBUG): Construct GoToSurface.
2019-05-15T20:25:36.868Z,1557951936.868 [Default:CheckIn:Read_Iridium:A_Timeout:A.Execute](DEBUG): Construct Execute.
2019-05-15T20:25:36.871Z,1557951936.871 [Default:CheckIn:C.Wait](DEBUG): Construct Wait.
2019-05-15T20:25:36.893Z,1557951936.893 [Default:E.Execute](DEBUG): Construct Execute.
2019-05-15T20:25:36.896Z,1557951936.896 [MissionManager](DEBUG): 
<?xml version="1.0" encoding="UTF-8"?>
<Mission xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xmlns="Tethys"
         xmlns:Units="Tethys/Units"
         xmlns:Guidance="Tethys/Guidance"
         xmlns:Universal="Tethys/Universal"
         xsi:schemaLocation="Tethys http://okeanids.mbari.org/tethys/Xml/Tethys.xsd
                             Tethys/Units http://okeanids.mbari.org/tethys/Xml/Units.xsd
                             Tethys/Guidance http://okeanids.mbari.org/tethys/Xml/Guidance.xsd
                             Tethys/Universal http://okeanids.mbari.org/tethys/Xml/Universal.xsd"
         Id="Default">

    <DefineArg Name="ElapsedSinceDefaultStarted"><Units:minute/><Value>0</Value></DefineArg>

    <Guidance:Wait>
        <Description>
            Wait a moment to see if the scheduler starts a new mission before
            starting to actually run Default.
        </Description>
        <Sequence/>
        <Setting><Guidance:Wait.duration/><Units:second/><Value>13</Value></Setting>
    </Guidance:Wait>

    <Guidance:GoToSurface>
        <Progression/>
    </Guidance:GoToSurface>

    <Aggregate Id="CheckIn">

        <Sequence Repeat="288"/>

        <ReadDatum Id="Read_GPS">
            <Timeout Duration="P5M"/>
            <Universal:time_fix/>
        </ReadDatum>

        <ReadDatum Id="Read_Iridium">
            <Timeout Duration="P2H">
                <Guidance:Execute>
                    <Sequence/>
                    <Setting><Guidance:Execute.command/><String>Burn on</String></Setting>
                </Guidance:Execute>
                <Syslog Severity="Critical">Dropped weight due to communications timeout.</Syslog>
            </Timeout>
            <Universal:platform_communications/>
        </ReadDatum>

        <Guidance:Wait>
            <Sequence/>
            <Setting><Guidance:Wait.duration/><Units:minute/><Value>5</Value></Setting>
        </Guidance:Wait>

        <Assign><Sequence/><Arg Name="ElapsedSinceDefaultStarted"/><Elapsed><Universal:mission_started/></Elapsed></Assign>

        <Syslog Severity="Important">Default mission has been running for <Arg Name="ElapsedSinceDefaultStarted"/><Units:minute/></Syslog>

    </Aggregate>

    <Syslog Severity="Important">Restarting logs and Default mission.</Syslog>

    <Guidance:Execute>
        <Sequence/>
        <Setting><Guidance:Execute.command/><String>restart logs</String></Setting>
    </Guidance:Execute>

</Mission>


2019-05-15T20:25:36.905Z,1557951936.905 [controlThread](DEBUG): Component order: CycleStarter,AHRS_M2,Depth_Keller,DropWeight,NAL9602,Onboard,BPC1,BR_Ping1D,PAR_Licor,Depth_Keller,PAR_Licor,DepthRateCalculator,PitchRateCalculator,SpeedCalculator,TempGradientCalculator,YawRateCalculator,ElevatorOffsetCalculator,DeadReckonUsingMultipleVelocitySources,NavChart,UniversalFixResidualReporter,MissionManager,VerticalControl,HorizontalControl,SpeedControl,LoopControl,BuoyancyServo,ElevatorServo,MassServo,RudderServo,ThrusterServo,SBIT,IBIT,CBIT,Reporter,LogSplitter,
2019-05-15T20:25:36.927Z,1557951936.927 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:25:36.986Z,1557951936.986 [Depth_Keller](ERROR): Pressure reading out of range: 1925.893799 decibar
2019-05-15T20:25:37.021Z,1557951937.021 [Radio_Surface](INFO): Powering up
2019-05-15T20:25:37.031Z,1557951937.031 [DepthRateCalculator](ERROR): Depth measurement is not active
2019-05-15T20:25:37.071Z,1557951937.071 [BuoyancyServo](DEBUG): Initializing EZServoServo.
2019-05-15T20:25:37.081Z,1557951937.081 [BuoyancyServo](DEBUG): Initializing BuoyancyServo.
2019-05-15T20:25:37.082Z,1557951937.082 [ElevatorServo](DEBUG): Initializing EZServoServo.
2019-05-15T20:25:37.093Z,1557951937.093 [ElevatorServo](DEBUG): Initializing ElevatorServo.
2019-05-15T20:25:37.094Z,1557951937.094 [MassServo](DEBUG): Initializing EZServoServo.
2019-05-15T20:25:37.101Z,1557951937.101 [MassServo](DEBUG): Initializing MassServo.
2019-05-15T20:25:37.102Z,1557951937.102 [RudderServo](DEBUG): Initializing EZServoServo.
2019-05-15T20:25:37.109Z,1557951937.109 [RudderServo](DEBUG): Initializing RudderServo.
2019-05-15T20:25:37.110Z,1557951937.110 [ThrusterServo](DEBUG): Initializing EZServoServo.
2019-05-15T20:25:37.117Z,1557951937.117 [ThrusterServo](DEBUG): Initializing ThrusterServo.
2019-05-15T20:25:37.119Z,1557951937.119 [CommandLine](FAULT): Scheduling is paused
2019-05-15T20:25:37.119Z,1557951937.119 [CBIT](INFO): Critical error at 20190515T202536
2019-05-15T20:25:37.120Z,1557951937.120 [Supervisor](INFO): Stop Mission called by CBIT::checkCriticals
2019-05-15T20:25:37.331Z,1557951937.331 [DropWeight](CRITICAL): DROP WEIGHT MISSING.

2019-05-15T20:25:37.331Z,1557951937.331 [DropWeight] Hardware Fault, FailCount= 1
2019-05-15T20:25:37.331Z,1557951937.331 [DropWeight](ERROR): Hardware Fault
2019-05-15T20:25:37.388Z,1557951937.388 [CBIT](INFO): Critical error at 20190515T202537
2019-05-15T20:25:37.391Z,1557951937.391 [CBIT](ERROR): Hardware Fault in component: DropWeight
2019-05-15T20:25:37.392Z,1557951937.392 [CBIT](CRITICAL): Hardware Fault in component: DropWeight
2019-05-15T20:25:37.740Z,1557951937.740 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:25:37.753Z,1557951937.753 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:25:37.753Z,1557951937.753 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:25:37.754Z,1557951937.754 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000BBEC4D7903
2019-05-15T20:25:37.754Z,1557951937.754 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:25:38.078Z,1557951938.078 [CBIT](INFO): Critical error at 20190515T202537
2019-05-15T20:25:38.545Z,1557951938.545 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:38.545Z,1557951938.545 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:25:38.545Z,1557951938.545 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:25:38.545Z,1557951938.545 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:25:38.546Z,1557951938.546 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:25:38.949Z,1557951938.949 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:38.949Z,1557951938.949 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:38.949Z,1557951938.949 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:25:39.013Z,1557951939.013 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:25:39.013Z,1557951939.013 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:39.013Z,1557951939.013 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:39.013Z,1557951939.013 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:39.352Z,1557951939.352 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:39.352Z,1557951939.352 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:39.353Z,1557951939.353 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:39.353Z,1557951939.353 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:39.353Z,1557951939.353 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:39.756Z,1557951939.756 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:39.757Z,1557951939.757 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:39.757Z,1557951939.757 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:39.757Z,1557951939.757 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:39.757Z,1557951939.757 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:40.216Z,1557951940.216 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:40.216Z,1557951940.216 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:40.217Z,1557951940.217 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:40.217Z,1557951940.217 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:40.217Z,1557951940.217 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:40.589Z,1557951940.589 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:40.589Z,1557951940.589 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:40.589Z,1557951940.589 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:40.589Z,1557951940.589 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:40.589Z,1557951940.589 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:40.992Z,1557951940.992 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:40.993Z,1557951940.993 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:40.993Z,1557951940.993 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:40.993Z,1557951940.993 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:40.993Z,1557951940.993 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:41.466Z,1557951941.466 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:41.466Z,1557951941.466 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:41.466Z,1557951941.466 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:41.466Z,1557951941.466 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:41.466Z,1557951941.466 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:41.841Z,1557951941.841 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:41.842Z,1557951941.842 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:41.842Z,1557951941.842 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:41.842Z,1557951941.842 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:41.842Z,1557951941.842 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:42.245Z,1557951942.245 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:42.245Z,1557951942.245 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:42.246Z,1557951942.246 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:42.246Z,1557951942.246 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:42.246Z,1557951942.246 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:42.648Z,1557951942.648 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:42.648Z,1557951942.648 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:42.649Z,1557951942.649 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:42.649Z,1557951942.649 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:42.649Z,1557951942.649 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:43.053Z,1557951943.053 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:43.053Z,1557951943.053 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:43.053Z,1557951943.053 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:25:43.054Z,1557951943.054 [BR_Ping1D] Data Fault, FailCount= 1
2019-05-15T20:25:43.054Z,1557951943.054 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:25:43.137Z,1557951943.137 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:25:43.456Z,1557951943.456 [BR_Ping1D](INFO): Stop
2019-05-15T20:25:43.456Z,1557951943.456 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:25:43.456Z,1557951943.456 [BR_Ping1D](INFO): Powering down
2019-05-15T20:25:43.861Z,1557951943.861 [BR_Ping1D](INFO): Stopping
2019-05-15T20:25:44.265Z,1557951944.265 [BR_Ping1D](INFO): Stopping
2019-05-15T20:25:44.676Z,1557951944.676 [BR_Ping1D](INFO): Stopped
2019-05-15T20:25:44.802Z,1557951944.802 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:25:44.802Z,1557951944.802 [BR_Ping1D] No Fault, FailCount= 1
2019-05-15T20:25:45.074Z,1557951945.074 [BR_Ping1D](INFO): Start
2019-05-15T20:25:45.868Z,1557951945.868 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:45.869Z,1557951945.869 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:25:45.881Z,1557951945.881 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:25:45.881Z,1557951945.881 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:25:45.881Z,1557951945.881 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:25:45.882Z,1557951945.882 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:25:46.678Z,1557951946.678 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:46.678Z,1557951946.678 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:25:46.678Z,1557951946.678 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:25:46.678Z,1557951946.678 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:25:46.679Z,1557951946.679 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:25:47.081Z,1557951947.081 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:47.081Z,1557951947.081 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:47.081Z,1557951947.081 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:25:47.081Z,1557951947.081 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:25:47.145Z,1557951947.145 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:25:47.145Z,1557951947.145 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:47.145Z,1557951947.145 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:47.145Z,1557951947.145 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:47.496Z,1557951947.496 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:47.497Z,1557951947.497 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:47.497Z,1557951947.497 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:47.497Z,1557951947.497 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:47.497Z,1557951947.497 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:47.889Z,1557951947.889 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:47.890Z,1557951947.890 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:47.890Z,1557951947.890 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:47.890Z,1557951947.890 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:47.890Z,1557951947.890 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:48.292Z,1557951948.292 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:48.293Z,1557951948.293 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:48.293Z,1557951948.293 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:48.293Z,1557951948.293 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:48.293Z,1557951948.293 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:48.697Z,1557951948.697 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:48.698Z,1557951948.698 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:48.698Z,1557951948.698 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:48.698Z,1557951948.698 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:48.698Z,1557951948.698 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:49.101Z,1557951949.101 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:49.101Z,1557951949.101 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:49.101Z,1557951949.101 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:49.101Z,1557951949.101 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:49.101Z,1557951949.101 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:49.504Z,1557951949.504 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:49.505Z,1557951949.505 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:49.505Z,1557951949.505 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:49.505Z,1557951949.505 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:49.505Z,1557951949.505 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:49.689Z,1557951949.689 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:25:49.689Z,1557951949.689 [CTD_Seabird] Communications Fault, FailCount= 1
2019-05-15T20:25:49.689Z,1557951949.689 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:25:49.909Z,1557951949.909 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:49.909Z,1557951949.909 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:49.909Z,1557951949.909 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:49.909Z,1557951949.909 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:49.909Z,1557951949.909 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:49.942Z,1557951949.942 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:25:50.093Z,1557951950.093 [CTD_Seabird](INFO): Powering down
2019-05-15T20:25:50.314Z,1557951950.314 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:50.314Z,1557951950.314 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:50.314Z,1557951950.314 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:50.314Z,1557951950.314 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:50.314Z,1557951950.314 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:50.717Z,1557951950.717 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:50.717Z,1557951950.717 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:50.717Z,1557951950.717 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:50.717Z,1557951950.717 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:50.717Z,1557951950.717 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:51.120Z,1557951951.120 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:51.121Z,1557951951.121 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:51.121Z,1557951951.121 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:25:51.122Z,1557951951.122 [BR_Ping1D] Data Fault, FailCount= 2
2019-05-15T20:25:51.122Z,1557951951.122 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:25:51.198Z,1557951951.198 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:25:51.198Z,1557951951.198 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:25:51.198Z,1557951951.198 [CTD_Seabird] No Fault, FailCount= 1
2019-05-15T20:25:51.457Z,1557951951.457 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:25:51.459Z,1557951951.459 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:25:51.525Z,1557951951.525 [BR_Ping1D](INFO): Stop
2019-05-15T20:25:51.525Z,1557951951.525 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:25:51.525Z,1557951951.525 [BR_Ping1D](INFO): Powering down
2019-05-15T20:25:51.929Z,1557951951.929 [BR_Ping1D](INFO): Stopping
2019-05-15T20:25:52.332Z,1557951952.332 [BR_Ping1D](INFO): Stopping
2019-05-15T20:25:52.737Z,1557951952.737 [BR_Ping1D](INFO): Stopped
2019-05-15T20:25:52.779Z,1557951952.779 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:25:52.779Z,1557951952.779 [BR_Ping1D] No Fault, FailCount= 2
2019-05-15T20:25:53.142Z,1557951953.142 [BR_Ping1D](INFO): Start
2019-05-15T20:25:53.949Z,1557951953.949 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:53.949Z,1557951953.949 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:25:53.961Z,1557951953.961 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:25:53.961Z,1557951953.961 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:25:53.961Z,1557951953.961 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:25:53.962Z,1557951953.962 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:25:54.758Z,1557951954.758 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:54.759Z,1557951954.759 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:25:54.759Z,1557951954.759 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:25:54.759Z,1557951954.759 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:25:54.759Z,1557951954.759 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:25:55.141Z,1557951955.141 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:25:55.141Z,1557951955.141 [AHRS_M2] Data Fault, FailCount= 1
2019-05-15T20:25:55.141Z,1557951955.141 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:25:55.162Z,1557951955.162 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:55.162Z,1557951955.162 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:55.162Z,1557951955.162 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:25:55.162Z,1557951955.162 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:25:55.237Z,1557951955.237 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:25:55.237Z,1557951955.237 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:55.237Z,1557951955.237 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:55.237Z,1557951955.237 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:55.294Z,1557951955.294 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:25:55.533Z,1557951955.533 [AHRS_M2](INFO): Powering down
2019-05-15T20:25:55.623Z,1557951955.623 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:55.623Z,1557951955.623 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:55.623Z,1557951955.623 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:55.624Z,1557951955.624 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:55.624Z,1557951955.624 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:55.958Z,1557951955.958 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:55.959Z,1557951955.959 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:55.959Z,1557951955.959 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:55.959Z,1557951955.959 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:55.959Z,1557951955.959 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:56.360Z,1557951956.360 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:56.361Z,1557951956.361 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:56.361Z,1557951956.361 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:56.362Z,1557951956.362 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:56.362Z,1557951956.362 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:56.416Z,1557951956.416 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:25:56.416Z,1557951956.416 [AHRS_M2] No Fault, FailCount= 1
2019-05-15T20:25:56.745Z,1557951956.745 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:25:56.770Z,1557951956.770 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:56.770Z,1557951956.770 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:56.771Z,1557951956.771 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:56.771Z,1557951956.771 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:56.771Z,1557951956.771 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:57.168Z,1557951957.168 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:57.168Z,1557951957.168 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:57.169Z,1557951957.169 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:57.169Z,1557951957.169 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:57.169Z,1557951957.169 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:57.574Z,1557951957.574 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:57.574Z,1557951957.574 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:57.574Z,1557951957.574 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:57.574Z,1557951957.574 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:57.575Z,1557951957.575 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:57.987Z,1557951957.987 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:57.987Z,1557951957.987 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:57.987Z,1557951957.987 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:57.987Z,1557951957.987 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:57.988Z,1557951957.988 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:58.386Z,1557951958.386 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:58.386Z,1557951958.386 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:58.387Z,1557951958.387 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:58.387Z,1557951958.387 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:58.387Z,1557951958.387 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:58.785Z,1557951958.785 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:58.785Z,1557951958.785 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:58.785Z,1557951958.785 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:25:58.785Z,1557951958.785 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:25:58.785Z,1557951958.785 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:25:59.189Z,1557951959.189 [BR_Ping1D](INFO): readConfig
2019-05-15T20:25:59.189Z,1557951959.189 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:25:59.189Z,1557951959.189 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:25:59.189Z,1557951959.189 [BR_Ping1D] Data Fault, FailCount= 3
2019-05-15T20:25:59.189Z,1557951959.189 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:25:59.238Z,1557951959.238 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:25:59.592Z,1557951959.592 [BR_Ping1D](INFO): Stop
2019-05-15T20:25:59.593Z,1557951959.593 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:25:59.593Z,1557951959.593 [BR_Ping1D](INFO): Powering down
2019-05-15T20:26:00.021Z,1557951960.021 [BR_Ping1D](INFO): Stopping
2019-05-15T20:26:00.415Z,1557951960.415 [BR_Ping1D](INFO): Stopping
2019-05-15T20:26:00.821Z,1557951960.821 [BR_Ping1D](INFO): Stopped
2019-05-15T20:26:00.858Z,1557951960.858 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:26:00.858Z,1557951960.858 [BR_Ping1D] No Fault, FailCount= 3
2019-05-15T20:26:01.220Z,1557951961.220 [BR_Ping1D](INFO): Start
2019-05-15T20:26:02.028Z,1557951962.028 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:02.029Z,1557951962.029 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:26:02.041Z,1557951962.041 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:26:02.041Z,1557951962.041 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:26:02.041Z,1557951962.041 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:26:02.042Z,1557951962.042 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:26:02.836Z,1557951962.836 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:02.836Z,1557951962.836 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:26:02.836Z,1557951962.836 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:26:02.838Z,1557951962.838 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:26:02.839Z,1557951962.839 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:26:03.226Z,1557951963.226 [NAL9602](INFO): Powering up NAL9602
2019-05-15T20:26:03.243Z,1557951963.243 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:03.243Z,1557951963.243 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:03.243Z,1557951963.243 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:26:03.243Z,1557951963.243 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:26:03.323Z,1557951963.323 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:26:03.323Z,1557951963.323 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:03.324Z,1557951963.324 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:03.324Z,1557951963.324 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:03.644Z,1557951963.644 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:03.644Z,1557951963.644 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:03.645Z,1557951963.645 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:03.645Z,1557951963.645 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:03.645Z,1557951963.645 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:04.053Z,1557951964.053 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:04.053Z,1557951964.053 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:04.054Z,1557951964.054 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:04.054Z,1557951964.054 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:04.054Z,1557951964.054 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:04.452Z,1557951964.452 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:04.460Z,1557951964.460 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:04.460Z,1557951964.460 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:04.461Z,1557951964.461 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:04.461Z,1557951964.461 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:04.509Z,1557951964.509 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:26:04.509Z,1557951964.509 [CTD_Seabird] Communications Fault, FailCount= 2
2019-05-15T20:26:04.509Z,1557951964.509 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:26:04.856Z,1557951964.856 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:04.857Z,1557951964.857 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:04.857Z,1557951964.857 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:04.857Z,1557951964.857 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:04.857Z,1557951964.857 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:04.913Z,1557951964.913 [CTD_Seabird](INFO): Powering down
2019-05-15T20:26:04.923Z,1557951964.923 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:26:05.260Z,1557951965.260 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:05.260Z,1557951965.260 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:05.261Z,1557951965.261 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:05.261Z,1557951965.261 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:05.261Z,1557951965.261 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:05.323Z,1557951965.323 [SBIT](IMPORTANT): Beginning Startup BIT
2019-05-15T20:26:05.327Z,1557951965.327 [CBIT](IMPORTANT): Beginning ground fault scan
2019-05-15T20:26:05.665Z,1557951965.665 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:05.665Z,1557951965.665 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:05.665Z,1557951965.665 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:05.666Z,1557951965.666 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:05.666Z,1557951965.666 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:06.068Z,1557951966.068 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:06.069Z,1557951966.069 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:06.069Z,1557951966.069 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:06.069Z,1557951966.069 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:06.069Z,1557951966.069 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:06.162Z,1557951966.162 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:26:06.162Z,1557951966.162 [CTD_Seabird] No Fault, FailCount= 2
2019-05-15T20:26:06.257Z,1557951966.257 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:26:06.265Z,1557951966.265 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:26:06.473Z,1557951966.473 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:06.473Z,1557951966.473 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:06.473Z,1557951966.473 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:06.473Z,1557951966.473 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:06.473Z,1557951966.473 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:06.877Z,1557951966.877 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:06.877Z,1557951966.877 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:06.877Z,1557951966.877 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:06.877Z,1557951966.877 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:06.877Z,1557951966.877 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:07.353Z,1557951967.353 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:07.353Z,1557951967.353 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:07.353Z,1557951967.353 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:26:07.354Z,1557951967.354 [BR_Ping1D] Data Fault, FailCount= 4
2019-05-15T20:26:07.354Z,1557951967.354 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:26:07.870Z,1557951967.870 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:26:07.917Z,1557951967.917 [BR_Ping1D](INFO): Stop
2019-05-15T20:26:07.918Z,1557951967.918 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:26:07.918Z,1557951967.918 [BR_Ping1D](INFO): Powering down
2019-05-15T20:26:08.313Z,1557951968.313 [BR_Ping1D](INFO): Stopping
2019-05-15T20:26:08.713Z,1557951968.713 [BR_Ping1D](INFO): Stopping
2019-05-15T20:26:09.116Z,1557951969.116 [BR_Ping1D](INFO): Stopped
2019-05-15T20:26:09.354Z,1557951969.354 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:26:09.354Z,1557951969.354 [BR_Ping1D] No Fault, FailCount= 4
2019-05-15T20:26:09.520Z,1557951969.520 [BR_Ping1D](INFO): Start
2019-05-15T20:26:10.309Z,1557951970.309 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:26:10.309Z,1557951970.309 [AHRS_M2] Data Fault, FailCount= 2
2019-05-15T20:26:10.309Z,1557951970.309 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:26:10.328Z,1557951970.328 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:10.329Z,1557951970.329 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:26:10.341Z,1557951970.341 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:26:10.341Z,1557951970.341 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:26:10.341Z,1557951970.341 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:26:10.342Z,1557951970.342 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:26:10.582Z,1557951970.582 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:26:10.702Z,1557951970.702 [AHRS_M2](INFO): Powering down
2019-05-15T20:26:11.127Z,1557951971.127 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:11.127Z,1557951971.127 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:26:11.127Z,1557951971.127 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:26:11.127Z,1557951971.127 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:26:11.128Z,1557951971.128 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:26:11.528Z,1557951971.528 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:11.537Z,1557951971.537 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:11.537Z,1557951971.537 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:26:11.537Z,1557951971.537 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:26:11.601Z,1557951971.601 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:26:11.601Z,1557951971.601 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:11.601Z,1557951971.601 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:11.601Z,1557951971.601 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:11.714Z,1557951971.714 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:26:11.714Z,1557951971.714 [AHRS_M2] No Fault, FailCount= 2
2019-05-15T20:26:11.914Z,1557951971.914 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:26:11.940Z,1557951971.940 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:11.941Z,1557951971.941 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:11.941Z,1557951971.941 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:11.941Z,1557951971.941 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:11.941Z,1557951971.941 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:12.336Z,1557951972.336 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:12.337Z,1557951972.337 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:12.337Z,1557951972.337 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:12.337Z,1557951972.337 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:12.337Z,1557951972.337 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:12.740Z,1557951972.740 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:12.740Z,1557951972.740 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:12.740Z,1557951972.740 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:12.741Z,1557951972.741 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:12.741Z,1557951972.741 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:13.145Z,1557951973.145 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:13.145Z,1557951973.145 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:13.145Z,1557951973.145 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:13.145Z,1557951973.145 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:13.145Z,1557951973.145 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:13.548Z,1557951973.548 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:13.548Z,1557951973.548 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:13.549Z,1557951973.549 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:13.549Z,1557951973.549 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:13.549Z,1557951973.549 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:13.968Z,1557951973.968 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:13.968Z,1557951973.968 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:13.968Z,1557951973.968 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:13.968Z,1557951973.968 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:13.969Z,1557951973.969 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:14.342Z,1557951974.342 [NAL9602](INFO): NAL9602 initialized
2019-05-15T20:26:14.357Z,1557951974.357 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:14.357Z,1557951974.357 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:14.357Z,1557951974.357 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:14.357Z,1557951974.357 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:14.358Z,1557951974.358 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:14.790Z,1557951974.790 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:14.790Z,1557951974.790 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:14.790Z,1557951974.790 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:26:14.790Z,1557951974.790 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:26:14.790Z,1557951974.790 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:26:15.461Z,1557951975.461 [AHRS_M2](ERROR): Start data-stream UART error: serial timeout
2019-05-15T20:26:15.477Z,1557951975.477 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:26:15.500Z,1557951975.500 [BR_Ping1D](INFO): readConfig
2019-05-15T20:26:15.500Z,1557951975.500 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:26:15.500Z,1557951975.500 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:26:15.500Z,1557951975.500 [BR_Ping1D] Data Fault, FailCount= 5
2019-05-15T20:26:15.501Z,1557951975.501 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:26:15.566Z,1557951975.566 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:26:15.567Z,1557951975.567 [CBIT](CRITICAL): Data Fault in component: BR_Ping1D
2019-05-15T20:26:15.913Z,1557951975.913 [AHRS_M2](ERROR): Start data-stream UART error: serial timeout
2019-05-15T20:26:15.948Z,1557951975.948 [BR_Ping1D](INFO): Stop
2019-05-15T20:26:15.948Z,1557951975.948 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:26:15.948Z,1557951975.948 [BR_Ping1D](INFO): Powering down
2019-05-15T20:26:16.171Z,1557951976.171 [CBIT](INFO): Critical error at 20190515T202615
2019-05-15T20:26:16.597Z,1557951976.597 [AHRS_M2](ERROR): Start data-stream UART error: serial timeout
2019-05-15T20:26:16.658Z,1557951976.658 [BR_Ping1D](INFO): Stopping
2019-05-15T20:26:16.706Z,1557951976.706 [CBIT](IMPORTANT): No ground fault detected
mA:
CHAN A0 (Batt): -0.028861
CHAN A1 (24V): 0.001132
CHAN A2 (12V): -0.005052
CHAN A3 (5V): -0.002854
CHAN B0 (3.3V): -0.000664
CHAN B1 (3.15aV): -0.001340
CHAN B2 (3.15bV): -0.001293
CHAN B3 (GND): -0.000169
OPEN: 0.003416
Full Scale Calc: 4.765 mA, -1.589 mA
2019-05-15T20:26:16.785Z,1557951976.785 [BR_Ping1D](INFO): Stopped
2019-05-15T20:26:19.309Z,1557951979.309 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:26:19.309Z,1557951979.309 [CTD_Seabird] Communications Fault, FailCount= 3
2019-05-15T20:26:19.309Z,1557951979.309 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:26:19.610Z,1557951979.610 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:26:19.610Z,1557951979.610 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-05-15T20:26:19.713Z,1557951979.713 [CTD_Seabird](INFO): Powering down
2019-05-15T20:26:26.929Z,1557951986.929 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:26:26.929Z,1557951986.929 [AHRS_M2] Data Fault, FailCount= 3
2019-05-15T20:26:26.929Z,1557951986.929 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:26:27.018Z,1557951987.018 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:26:27.321Z,1557951987.321 [AHRS_M2](INFO): Powering down
2019-05-15T20:26:28.226Z,1557951988.226 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:26:28.226Z,1557951988.226 [AHRS_M2] No Fault, FailCount= 3
2019-05-15T20:26:28.533Z,1557951988.533 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:26:41.877Z,1557952001.877 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:26:41.877Z,1557952001.877 [AHRS_M2] Data Fault, FailCount= 4
2019-05-15T20:26:41.877Z,1557952001.877 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:26:41.915Z,1557952001.915 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:26:42.269Z,1557952002.269 [AHRS_M2](INFO): Powering down
2019-05-15T20:26:43.116Z,1557952003.116 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:26:43.116Z,1557952003.116 [AHRS_M2] No Fault, FailCount= 4
2019-05-15T20:26:43.483Z,1557952003.483 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:26:56.921Z,1557952016.921 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:26:56.921Z,1557952016.921 [AHRS_M2] Data Fault, FailCount= 5
2019-05-15T20:26:56.921Z,1557952016.921 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:26:56.960Z,1557952016.960 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:26:56.960Z,1557952016.960 [CBIT](CRITICAL): Data Fault in component: AHRS_M2
2019-05-15T20:26:57.313Z,1557952017.313 [AHRS_M2](INFO): Powering down
2019-05-15T20:26:57.422Z,1557952017.422 [CBIT](INFO): Critical error at 20190515T202656
2019-05-15T20:26:58.971Z,1557952018.971 [SBIT](IMPORTANT): SBIT PASSED
2019-05-15T20:26:59.049Z,1557952019.049 [CommandLine](IMPORTANT): got command configSet list
2019-05-15T20:26:59.049Z,1557952019.049 [CommandLine](IMPORTANT): Listing configuration overrides from Data/persisted.cfg
2019-05-15T20:26:59.050Z,1557952019.050 [CommandLine](IMPORTANT): PAR_Licor.loadAtStartup=1 bool;

2019-05-15T20:26:59.376Z,1557952019.376 [MissionManager](IMPORTANT): Started mission Startup
2019-05-15T20:26:59.376Z,1557952019.376 [Startup] Running Loop=1
2019-05-15T20:26:59.376Z,1557952019.376 [Startup](DEBUG): Aggregate::initialize Startup
2019-05-15T20:26:59.376Z,1557952019.376 [Startup:A.GoToSurface] Running Loop=1
2019-05-15T20:26:59.376Z,1557952019.376 [Startup:A.GoToSurface](DEBUG): Initialize GoToSurfaceComponent.
2019-05-15T20:26:59.377Z,1557952019.377 [Startup:A.GoToSurface](DEBUG): No depth rate setting specified. Using default value of nan m/s.
2019-05-15T20:26:59.378Z,1557952019.378 [Startup:A.GoToSurface](DEBUG): No pitch setting specified. Using default value of nan degrees.
2019-05-15T20:26:59.378Z,1557952019.378 [Startup:A.GoToSurface](DEBUG): No speed setting specified. Using default value of 1.000000 m/s.
2019-05-15T20:26:59.379Z,1557952019.379 [Startup:A.GoToSurface](DEBUG): No surface timeout specified. Using default value of 1000.000000 seconds.
2019-05-15T20:26:59.379Z,1557952019.379 [Startup:A.GoToSurface](INFO): Received pitch timeout configuration 60.000000 seconds.
2019-05-15T20:26:59.380Z,1557952019.380 [Startup:StartupSatComms] Running Loop=1
2019-05-15T20:26:59.380Z,1557952019.380 [Startup:StartupSatComms](DEBUG): Aggregate::initialize Startup:StartupSatComms
2019-05-15T20:26:59.380Z,1557952019.380 [Startup:StartupSatComms:A] Running Loop=1
2019-05-15T20:26:59.782Z,1557952019.782 [Startup:StartupSatComms:A](DEBUG): Initialize ReadDataComponent to sense latitude_fix
2019-05-15T20:27:36.949Z,1557952056.949 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-05-15T20:27:36.949Z,1557952056.949 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 1
2019-05-15T20:27:36.950Z,1557952056.950 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-05-15T20:27:36.960Z,1557952056.960 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-05-15T20:27:37.358Z,1557952057.358 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-05-15T20:27:37.358Z,1557952057.358 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 1
2019-05-15T20:27:59.674Z,1557952079.674 [Startup:StartupSatComms:A](INFO): Timed out from 2019-05-15T20:26:59.4Z
2019-05-15T20:27:59.674Z,1557952079.674 [Startup:StartupSatComms:A] Stopped
2019-05-15T20:27:59.674Z,1557952079.674 [Startup:StartupSatComms:B] Running Loop=1
2019-05-15T20:28:00.022Z,1557952080.022 [Startup:StartupSatComms:B](DEBUG): Initialize ReadDataComponent to sense platform_communications
2019-05-15T20:28:02.774Z,1557952082.774 [DataOverHttps](INFO): setting available, lastComms_.elapsed()=0.004573
2019-05-15T20:28:49.416Z,1557952129.416 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:28:49.416Z,1557952129.416 [CTD_Seabird] No Fault, FailCount= 3
2019-05-15T20:28:49.793Z,1557952129.793 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:28:49.822Z,1557952129.822 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:28:59.933Z,1557952139.933 [Startup:StartupSatComms:B](INFO): Timed out from 2019-05-15T20:27:59.7Z
2019-05-15T20:28:59.933Z,1557952139.933 [Startup:StartupSatComms:B] Stopped
2019-05-15T20:28:59.933Z,1557952139.933 [Startup:StartupSatComms](INFO): Completed Startup:StartupSatComms
2019-05-15T20:28:59.933Z,1557952139.933 [Startup:StartupSatComms] Stopped
2019-05-15T20:28:59.933Z,1557952139.933 [Startup:StartupSatComms](DEBUG): Aggregate::uninitialize Startup:StartupSatComms
2019-05-15T20:28:59.934Z,1557952139.934 [Startup](INFO): Completed Startup
2019-05-15T20:28:59.934Z,1557952139.934 [MissionManager](INFO): Startup is completed.
2019-05-15T20:28:59.935Z,1557952139.935 [MissionManager](INFO): Uninitializing Mission Startup
2019-05-15T20:28:59.935Z,1557952139.935 [Startup] Stopped
2019-05-15T20:28:59.935Z,1557952139.935 [Startup](DEBUG): Aggregate::uninitialize Startup
2019-05-15T20:28:59.935Z,1557952139.935 [Startup:A.GoToSurface] Stopped
2019-05-15T20:28:59.935Z,1557952139.935 [Startup:A.GoToSurface](DEBUG): Uninitialize GoToSurfaceComponent.
2019-05-15T20:29:00.279Z,1557952140.279 [MissionManager](IMPORTANT): Started mission Default
2019-05-15T20:29:00.279Z,1557952140.279 [Default] Running Loop=1
2019-05-15T20:29:00.279Z,1557952140.279 [Default](DEBUG): Aggregate::initialize Default
2019-05-15T20:29:00.279Z,1557952140.279 [Default:B.GoToSurface] Running Loop=1
2019-05-15T20:29:00.279Z,1557952140.279 [Default:B.GoToSurface](DEBUG): Initialize GoToSurfaceComponent.
2019-05-15T20:29:00.280Z,1557952140.280 [Default:B.GoToSurface](DEBUG): No depth rate setting specified. Using default value of nan m/s.
2019-05-15T20:29:00.280Z,1557952140.280 [Default:B.GoToSurface](DEBUG): No pitch setting specified. Using default value of nan degrees.
2019-05-15T20:29:00.280Z,1557952140.280 [Default:B.GoToSurface](DEBUG): No speed setting specified. Using default value of 1.000000 m/s.
2019-05-15T20:29:00.280Z,1557952140.280 [Default:B.GoToSurface](DEBUG): No surface timeout specified. Using default value of 1000.000000 seconds.
2019-05-15T20:29:00.281Z,1557952140.281 [Default:B.GoToSurface](INFO): Received pitch timeout configuration 60.000000 seconds.
2019-05-15T20:29:00.281Z,1557952140.281 [Default:A.Wait] Running Loop=1
2019-05-15T20:29:00.281Z,1557952140.281 [Default:A.Wait](DEBUG): Initialize Wait Component.
2019-05-15T20:29:03.849Z,1557952143.849 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:29:03.849Z,1557952143.849 [CTD_Seabird] Communications Fault, FailCount= 1
2019-05-15T20:29:03.849Z,1557952143.849 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:29:03.928Z,1557952143.928 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:29:04.253Z,1557952144.253 [CTD_Seabird](INFO): Powering down
2019-05-15T20:29:05.547Z,1557952145.547 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:29:05.547Z,1557952145.547 [CTD_Seabird] No Fault, FailCount= 1
2019-05-15T20:29:05.601Z,1557952145.601 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:29:05.603Z,1557952145.603 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:29:13.618Z,1557952153.618 [Default:A.Wait](INFO): Done Waiting.
2019-05-15T20:29:13.618Z,1557952153.618 [Default:A.Wait] Stopped
2019-05-15T20:29:13.618Z,1557952153.618 [Default:A.Wait](DEBUG): Uninitialize Wait Component.
2019-05-15T20:29:14.002Z,1557952154.002 [Default:CheckIn] Running Loop=1
2019-05-15T20:29:14.002Z,1557952154.002 [Default:CheckIn](DEBUG): Aggregate::initialize Default:CheckIn
2019-05-15T20:29:14.003Z,1557952154.003 [Default:CheckIn:Read_GPS] Running Loop=1
2019-05-15T20:29:14.403Z,1557952154.403 [Default:CheckIn:Read_GPS](DEBUG): Initialize ReadDataComponent to sense time_fix
2019-05-15T20:29:19.657Z,1557952159.657 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:29:19.657Z,1557952159.657 [CTD_Seabird] Communications Fault, FailCount= 2
2019-05-15T20:29:19.657Z,1557952159.657 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:29:19.686Z,1557952159.686 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:29:20.061Z,1557952160.061 [CTD_Seabird](INFO): Powering down
2019-05-15T20:29:21.291Z,1557952161.291 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:29:21.292Z,1557952161.292 [CTD_Seabird] No Fault, FailCount= 2
2019-05-15T20:29:21.405Z,1557952161.405 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:29:21.407Z,1557952161.407 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:29:34.457Z,1557952174.457 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:29:34.457Z,1557952174.457 [CTD_Seabird] Communications Fault, FailCount= 3
2019-05-15T20:29:34.457Z,1557952174.457 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:29:34.620Z,1557952174.620 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:29:34.620Z,1557952174.620 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-05-15T20:29:34.861Z,1557952174.861 [CTD_Seabird](INFO): Powering down
2019-05-15T20:29:37.880Z,1557952177.880 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-05-15T20:29:37.880Z,1557952177.880 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 2
2019-05-15T20:29:37.880Z,1557952177.880 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-05-15T20:29:37.919Z,1557952177.919 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-05-15T20:29:38.277Z,1557952178.277 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-05-15T20:29:38.277Z,1557952178.277 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 2
2019-05-15T20:31:15.612Z,1557952275.612 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:31:15.612Z,1557952275.612 [BR_Ping1D] No Fault, FailCount= 5
2019-05-15T20:31:16.001Z,1557952276.001 [BR_Ping1D](INFO): Start
2019-05-15T20:31:16.820Z,1557952276.820 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:16.820Z,1557952276.820 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:31:16.833Z,1557952276.833 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:31:16.834Z,1557952276.834 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:31:16.835Z,1557952276.835 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:31:16.836Z,1557952276.836 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:31:17.628Z,1557952277.628 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:17.628Z,1557952277.628 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:31:17.628Z,1557952277.628 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:31:17.630Z,1557952277.630 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:31:17.631Z,1557952277.631 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:31:18.078Z,1557952278.078 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:18.079Z,1557952278.079 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:18.079Z,1557952278.079 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:31:18.079Z,1557952278.079 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:31:18.153Z,1557952278.153 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:31:18.153Z,1557952278.153 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:18.153Z,1557952278.153 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:18.153Z,1557952278.153 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:18.407Z,1557952278.407 [NAL9602](FAULT): MT Queue status failed to be acquired within timeout. Will not retry this session.
2019-05-15T20:31:18.442Z,1557952278.442 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:18.442Z,1557952278.442 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:18.442Z,1557952278.442 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:18.442Z,1557952278.442 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:18.443Z,1557952278.443 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:18.841Z,1557952278.841 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:18.842Z,1557952278.842 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:18.842Z,1557952278.842 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:18.842Z,1557952278.842 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:18.842Z,1557952278.842 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:19.225Z,1557952279.225 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:19.253Z,1557952279.253 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:19.254Z,1557952279.254 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:19.254Z,1557952279.254 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:19.254Z,1557952279.254 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:19.254Z,1557952279.254 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:19.637Z,1557952279.637 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:19.638Z,1557952279.638 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:19.638Z,1557952279.638 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:19.638Z,1557952279.638 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:19.638Z,1557952279.638 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:20.041Z,1557952280.041 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:20.042Z,1557952280.042 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:20.042Z,1557952280.042 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:20.042Z,1557952280.042 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:20.042Z,1557952280.042 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:20.441Z,1557952280.441 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:20.442Z,1557952280.442 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:20.442Z,1557952280.442 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:20.442Z,1557952280.442 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:20.442Z,1557952280.442 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:20.846Z,1557952280.846 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:20.846Z,1557952280.846 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:20.846Z,1557952280.846 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:20.847Z,1557952280.847 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:20.847Z,1557952280.847 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:21.256Z,1557952281.256 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:21.256Z,1557952281.256 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:21.256Z,1557952281.256 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:21.256Z,1557952281.256 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:21.257Z,1557952281.257 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:21.673Z,1557952281.673 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:21.673Z,1557952281.673 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:21.674Z,1557952281.674 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:21.674Z,1557952281.674 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:21.674Z,1557952281.674 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:22.067Z,1557952282.067 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:22.068Z,1557952282.068 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:22.068Z,1557952282.068 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:31:22.068Z,1557952282.068 [BR_Ping1D] Data Fault, FailCount= 1
2019-05-15T20:31:22.068Z,1557952282.068 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:31:22.119Z,1557952282.119 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:31:22.462Z,1557952282.462 [BR_Ping1D](INFO): Stop
2019-05-15T20:31:22.462Z,1557952282.462 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:31:22.462Z,1557952282.462 [BR_Ping1D](INFO): Powering down
2019-05-15T20:31:22.865Z,1557952282.865 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:23.382Z,1557952283.382 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:23.680Z,1557952283.680 [BR_Ping1D](INFO): Stopped
2019-05-15T20:31:23.707Z,1557952283.707 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:31:23.707Z,1557952283.707 [BR_Ping1D] No Fault, FailCount= 1
2019-05-15T20:31:24.073Z,1557952284.073 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:24.101Z,1557952284.101 [BR_Ping1D](INFO): Start
2019-05-15T20:31:24.900Z,1557952284.900 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:24.900Z,1557952284.900 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:31:24.913Z,1557952284.913 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:31:24.913Z,1557952284.913 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:31:24.913Z,1557952284.913 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:31:24.914Z,1557952284.914 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:31:25.694Z,1557952285.694 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:25.694Z,1557952285.694 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:31:25.694Z,1557952285.694 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:31:25.695Z,1557952285.695 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:31:25.696Z,1557952285.696 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:31:26.102Z,1557952286.102 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:26.102Z,1557952286.102 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:26.102Z,1557952286.102 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:31:26.102Z,1557952286.102 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:31:26.177Z,1557952286.177 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:31:26.177Z,1557952286.177 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:26.177Z,1557952286.177 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:26.177Z,1557952286.177 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:26.502Z,1557952286.502 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:26.502Z,1557952286.502 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:26.502Z,1557952286.502 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:26.503Z,1557952286.503 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:26.503Z,1557952286.503 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:26.901Z,1557952286.901 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:26.916Z,1557952286.916 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:26.916Z,1557952286.916 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:26.916Z,1557952286.916 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:26.917Z,1557952286.917 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:26.917Z,1557952286.917 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:27.324Z,1557952287.324 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:27.324Z,1557952287.324 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:27.324Z,1557952287.324 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:27.325Z,1557952287.325 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:27.325Z,1557952287.325 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:27.728Z,1557952287.728 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:27.728Z,1557952287.728 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:27.728Z,1557952287.728 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:27.728Z,1557952287.728 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:27.728Z,1557952287.728 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:28.118Z,1557952288.118 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:28.118Z,1557952288.118 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:28.118Z,1557952288.118 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:28.118Z,1557952288.118 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:28.118Z,1557952288.118 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:28.521Z,1557952288.521 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:28.521Z,1557952288.521 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:28.521Z,1557952288.521 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:28.521Z,1557952288.521 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:28.522Z,1557952288.522 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:28.926Z,1557952288.926 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:28.926Z,1557952288.926 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:28.926Z,1557952288.926 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:28.926Z,1557952288.926 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:28.926Z,1557952288.926 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:29.330Z,1557952289.330 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:29.330Z,1557952289.330 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:29.330Z,1557952289.330 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:29.330Z,1557952289.330 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:29.330Z,1557952289.330 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:29.733Z,1557952289.733 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:29.733Z,1557952289.733 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:29.734Z,1557952289.734 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:29.734Z,1557952289.734 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:29.734Z,1557952289.734 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:30.133Z,1557952290.133 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:30.148Z,1557952290.148 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:30.148Z,1557952290.148 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:30.148Z,1557952290.148 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:31:30.148Z,1557952290.148 [BR_Ping1D] Data Fault, FailCount= 2
2019-05-15T20:31:30.148Z,1557952290.148 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:31:30.171Z,1557952290.171 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:31:30.556Z,1557952290.556 [BR_Ping1D](INFO): Stop
2019-05-15T20:31:30.556Z,1557952290.556 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:31:30.556Z,1557952290.556 [BR_Ping1D](INFO): Powering down
2019-05-15T20:31:30.959Z,1557952290.959 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:31.411Z,1557952291.411 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:31.764Z,1557952291.764 [BR_Ping1D](INFO): Stopped
2019-05-15T20:31:31.800Z,1557952291.800 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:31:31.800Z,1557952291.800 [BR_Ping1D] No Fault, FailCount= 2
2019-05-15T20:31:32.169Z,1557952292.169 [BR_Ping1D](INFO): Start
2019-05-15T20:31:32.965Z,1557952292.965 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:32.980Z,1557952292.980 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:32.980Z,1557952292.980 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:31:32.993Z,1557952292.993 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:31:32.994Z,1557952292.994 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:31:32.995Z,1557952292.995 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:31:32.996Z,1557952292.996 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:31:33.788Z,1557952293.788 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:33.788Z,1557952293.788 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:31:33.788Z,1557952293.788 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:31:33.789Z,1557952293.789 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:31:33.790Z,1557952293.790 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:31:34.184Z,1557952294.184 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:34.184Z,1557952294.184 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:34.185Z,1557952294.185 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:31:34.185Z,1557952294.185 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:31:34.249Z,1557952294.249 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:31:34.249Z,1557952294.249 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:34.249Z,1557952294.249 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:34.249Z,1557952294.249 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:34.581Z,1557952294.581 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:34.582Z,1557952294.582 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:34.582Z,1557952294.582 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:34.582Z,1557952294.582 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:34.582Z,1557952294.582 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:34.990Z,1557952294.990 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:34.990Z,1557952294.990 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:34.990Z,1557952294.990 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:34.990Z,1557952294.990 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:34.990Z,1557952294.990 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:35.390Z,1557952295.390 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:35.390Z,1557952295.390 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:35.390Z,1557952295.390 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:35.391Z,1557952295.391 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:35.391Z,1557952295.391 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:35.789Z,1557952295.789 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:35.804Z,1557952295.804 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:35.804Z,1557952295.804 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:35.804Z,1557952295.804 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:35.804Z,1557952295.804 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:35.804Z,1557952295.804 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:36.212Z,1557952296.212 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:36.212Z,1557952296.212 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:36.212Z,1557952296.212 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:36.213Z,1557952296.213 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:36.213Z,1557952296.213 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:36.677Z,1557952296.677 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:36.677Z,1557952296.677 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:36.677Z,1557952296.677 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:36.677Z,1557952296.677 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:36.678Z,1557952296.678 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:37.012Z,1557952297.012 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:37.012Z,1557952297.012 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:37.012Z,1557952297.012 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:37.013Z,1557952297.013 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:37.013Z,1557952297.013 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:37.425Z,1557952297.425 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:37.426Z,1557952297.426 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:37.426Z,1557952297.426 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:37.426Z,1557952297.426 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:37.426Z,1557952297.426 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:37.825Z,1557952297.825 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:37.826Z,1557952297.826 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:37.826Z,1557952297.826 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:37.826Z,1557952297.826 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:37.826Z,1557952297.826 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:38.217Z,1557952298.217 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:38.217Z,1557952298.217 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:38.218Z,1557952298.218 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:31:38.218Z,1557952298.218 [BR_Ping1D] Data Fault, FailCount= 3
2019-05-15T20:31:38.218Z,1557952298.218 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:31:38.265Z,1557952298.265 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:31:38.625Z,1557952298.625 [BR_Ping1D](INFO): Stop
2019-05-15T20:31:38.625Z,1557952298.625 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:31:38.625Z,1557952298.625 [BR_Ping1D](INFO): Powering down
2019-05-15T20:31:38.705Z,1557952298.705 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-05-15T20:31:38.705Z,1557952298.705 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 3
2019-05-15T20:31:38.705Z,1557952298.705 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-05-15T20:31:38.716Z,1557952298.716 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-05-15T20:31:39.025Z,1557952299.025 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:39.040Z,1557952299.040 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:39.058Z,1557952299.058 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-05-15T20:31:39.058Z,1557952299.058 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 3
2019-05-15T20:31:39.444Z,1557952299.444 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:39.847Z,1557952299.847 [BR_Ping1D](INFO): Stopped
2019-05-15T20:31:39.862Z,1557952299.862 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:31:39.862Z,1557952299.862 [BR_Ping1D] No Fault, FailCount= 3
2019-05-15T20:31:40.238Z,1557952300.238 [BR_Ping1D](INFO): Start
2019-05-15T20:31:41.055Z,1557952301.055 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:41.055Z,1557952301.055 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:31:41.069Z,1557952301.069 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:31:41.070Z,1557952301.070 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:31:41.071Z,1557952301.071 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:31:41.072Z,1557952301.072 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:31:41.853Z,1557952301.853 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:41.869Z,1557952301.869 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:41.869Z,1557952301.869 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:31:41.869Z,1557952301.869 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:31:41.870Z,1557952301.870 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:31:41.871Z,1557952301.871 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:31:42.276Z,1557952302.276 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:42.276Z,1557952302.276 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:42.276Z,1557952302.276 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:31:42.276Z,1557952302.276 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:31:42.349Z,1557952302.349 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:31:42.349Z,1557952302.349 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:42.349Z,1557952302.349 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:42.349Z,1557952302.349 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:42.672Z,1557952302.672 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:42.673Z,1557952302.673 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:42.673Z,1557952302.673 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:42.673Z,1557952302.673 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:42.673Z,1557952302.673 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:43.069Z,1557952303.069 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:43.070Z,1557952303.070 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:43.070Z,1557952303.070 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:43.070Z,1557952303.070 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:43.070Z,1557952303.070 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:43.469Z,1557952303.469 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:43.470Z,1557952303.470 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:43.470Z,1557952303.470 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:43.470Z,1557952303.470 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:43.470Z,1557952303.470 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:43.875Z,1557952303.875 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:43.875Z,1557952303.875 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:43.875Z,1557952303.875 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:43.876Z,1557952303.876 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:43.876Z,1557952303.876 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:44.282Z,1557952304.282 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:44.282Z,1557952304.282 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:44.282Z,1557952304.282 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:44.282Z,1557952304.282 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:44.282Z,1557952304.282 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:44.748Z,1557952304.748 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:44.748Z,1557952304.748 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:44.748Z,1557952304.748 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:44.748Z,1557952304.748 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:44.748Z,1557952304.748 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:45.085Z,1557952305.085 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:45.119Z,1557952305.119 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:45.119Z,1557952305.119 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:45.119Z,1557952305.119 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:45.119Z,1557952305.119 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:45.119Z,1557952305.119 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:45.517Z,1557952305.517 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:45.518Z,1557952305.518 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:45.518Z,1557952305.518 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:45.518Z,1557952305.518 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:45.518Z,1557952305.518 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:45.921Z,1557952305.921 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:45.922Z,1557952305.922 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:45.922Z,1557952305.922 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:45.922Z,1557952305.922 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:45.922Z,1557952305.922 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:46.297Z,1557952306.297 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:46.298Z,1557952306.298 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:46.298Z,1557952306.298 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:31:46.298Z,1557952306.298 [BR_Ping1D] Data Fault, FailCount= 4
2019-05-15T20:31:46.298Z,1557952306.298 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:31:46.319Z,1557952306.319 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:31:46.704Z,1557952306.704 [BR_Ping1D](INFO): Stop
2019-05-15T20:31:46.705Z,1557952306.705 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:31:46.705Z,1557952306.705 [BR_Ping1D](INFO): Powering down
2019-05-15T20:31:47.110Z,1557952307.110 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:47.513Z,1557952307.513 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:47.909Z,1557952307.909 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:47.928Z,1557952307.928 [BR_Ping1D](INFO): Stopped
2019-05-15T20:31:47.954Z,1557952307.954 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:31:47.954Z,1557952307.954 [BR_Ping1D] No Fault, FailCount= 4
2019-05-15T20:31:48.332Z,1557952308.332 [BR_Ping1D](INFO): Start
2019-05-15T20:31:49.129Z,1557952309.129 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:49.129Z,1557952309.129 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:31:49.141Z,1557952309.141 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:31:49.142Z,1557952309.142 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:31:49.143Z,1557952309.143 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:31:49.144Z,1557952309.144 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:31:50.002Z,1557952310.002 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:50.002Z,1557952310.002 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:31:50.002Z,1557952310.002 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:31:50.003Z,1557952310.003 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:31:50.004Z,1557952310.004 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:31:50.348Z,1557952310.348 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:50.348Z,1557952310.348 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:50.348Z,1557952310.348 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:31:50.348Z,1557952310.348 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:31:50.413Z,1557952310.413 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:31:50.413Z,1557952310.413 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:50.413Z,1557952310.413 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:50.413Z,1557952310.413 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:50.741Z,1557952310.741 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:50.769Z,1557952310.769 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:50.770Z,1557952310.770 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:50.770Z,1557952310.770 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:50.770Z,1557952310.770 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:50.770Z,1557952310.770 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:51.173Z,1557952311.173 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:51.174Z,1557952311.174 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:51.174Z,1557952311.174 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:51.174Z,1557952311.174 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:51.174Z,1557952311.174 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:51.562Z,1557952311.562 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:51.562Z,1557952311.562 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:51.562Z,1557952311.562 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:51.562Z,1557952311.562 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:51.563Z,1557952311.563 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:51.958Z,1557952311.958 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:51.958Z,1557952311.958 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:51.958Z,1557952311.958 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:51.958Z,1557952311.958 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:51.958Z,1557952311.958 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:52.360Z,1557952312.360 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:52.361Z,1557952312.361 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:52.361Z,1557952312.361 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:52.361Z,1557952312.361 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:52.361Z,1557952312.361 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:52.761Z,1557952312.761 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:52.775Z,1557952312.775 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:52.776Z,1557952312.776 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:52.776Z,1557952312.776 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:52.776Z,1557952312.776 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:52.776Z,1557952312.776 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:53.180Z,1557952313.180 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:53.180Z,1557952313.180 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:53.180Z,1557952313.180 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:53.180Z,1557952313.180 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:53.180Z,1557952313.180 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:53.580Z,1557952313.580 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:53.580Z,1557952313.580 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:53.580Z,1557952313.580 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:53.580Z,1557952313.580 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:53.580Z,1557952313.580 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:53.974Z,1557952313.974 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:53.974Z,1557952313.974 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:53.975Z,1557952313.975 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:31:53.975Z,1557952313.975 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:31:53.975Z,1557952313.975 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:31:54.379Z,1557952314.379 [BR_Ping1D](INFO): readConfig
2019-05-15T20:31:54.380Z,1557952314.380 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:31:54.380Z,1557952314.380 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:31:54.380Z,1557952314.380 [BR_Ping1D] Data Fault, FailCount= 5
2019-05-15T20:31:54.380Z,1557952314.380 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:31:54.421Z,1557952314.421 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:31:54.421Z,1557952314.421 [CBIT](CRITICAL): Data Fault in component: BR_Ping1D
2019-05-15T20:31:54.777Z,1557952314.777 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:54.797Z,1557952314.797 [BR_Ping1D](INFO): Stop
2019-05-15T20:31:54.797Z,1557952314.797 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:31:54.797Z,1557952314.797 [BR_Ping1D](INFO): Powering down
2019-05-15T20:31:54.905Z,1557952314.905 [CBIT](INFO): Critical error at 20190515T203154
2019-05-15T20:31:55.202Z,1557952315.202 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:55.600Z,1557952315.600 [BR_Ping1D](INFO): Stopping
2019-05-15T20:31:55.998Z,1557952315.998 [BR_Ping1D](INFO): Stopped
2019-05-15T20:31:56.801Z,1557952316.801 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:31:57.240Z,1557952317.240 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:31:57.240Z,1557952317.240 [AHRS_M2] No Fault, FailCount= 5
2019-05-15T20:31:57.589Z,1557952317.589 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:32:00.037Z,1557952320.037 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:02.869Z,1557952322.869 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:04.524Z,1557952324.524 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:32:04.524Z,1557952324.524 [CTD_Seabird] No Fault, FailCount= 3
2019-05-15T20:32:04.877Z,1557952324.877 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:32:04.884Z,1557952324.884 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:32:06.105Z,1557952326.105 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:08.933Z,1557952328.933 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:10.933Z,1557952330.933 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:32:10.933Z,1557952330.933 [AHRS_M2] Data Fault, FailCount= 1
2019-05-15T20:32:10.933Z,1557952330.933 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:32:10.972Z,1557952330.972 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:32:11.325Z,1557952331.325 [AHRS_M2](INFO): Powering down
2019-05-15T20:32:11.749Z,1557952331.749 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:12.203Z,1557952332.203 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:32:12.203Z,1557952332.203 [AHRS_M2] No Fault, FailCount= 1
2019-05-15T20:32:12.537Z,1557952332.537 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:32:13.769Z,1557952333.769 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:15.813Z,1557952335.813 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:17.429Z,1557952337.429 [BPC1](INFO): Calculating totals. Valid battery stick count: 56. Valid reserve battery stick count: 6.
2019-05-15T20:32:17.432Z,1557952337.432 [BPC1](INFO): Received data from all battery sticks.
2019-05-15T20:32:17.929Z,1557952337.929 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:32:17.929Z,1557952337.929 [CTD_Seabird] Communications Fault, FailCount= 1
2019-05-15T20:32:17.929Z,1557952337.929 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:32:18.247Z,1557952338.247 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:32:18.333Z,1557952338.333 [CTD_Seabird](INFO): Powering down
2019-05-15T20:32:19.029Z,1557952339.029 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:19.474Z,1557952339.474 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:32:19.474Z,1557952339.474 [CTD_Seabird] No Fault, FailCount= 1
2019-05-15T20:32:19.677Z,1557952339.677 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:32:19.678Z,1557952339.678 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:32:21.865Z,1557952341.865 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:25.093Z,1557952345.093 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:25.881Z,1557952345.881 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:32:25.881Z,1557952345.881 [AHRS_M2] Data Fault, FailCount= 2
2019-05-15T20:32:25.881Z,1557952345.881 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:32:25.952Z,1557952345.952 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:32:26.273Z,1557952346.273 [AHRS_M2](INFO): Powering down
2019-05-15T20:32:27.119Z,1557952347.119 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:32:27.119Z,1557952347.119 [AHRS_M2] No Fault, FailCount= 2
2019-05-15T20:32:27.485Z,1557952347.485 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:32:27.909Z,1557952347.909 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:31.229Z,1557952351.229 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:32.729Z,1557952352.729 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:32:32.729Z,1557952352.729 [CTD_Seabird] Communications Fault, FailCount= 2
2019-05-15T20:32:32.729Z,1557952352.729 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:32:32.823Z,1557952352.823 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:32:33.133Z,1557952353.133 [CTD_Seabird](INFO): Powering down
2019-05-15T20:32:33.977Z,1557952353.977 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:34.466Z,1557952354.466 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:32:34.466Z,1557952354.466 [CTD_Seabird] No Fault, FailCount= 2
2019-05-15T20:32:34.473Z,1557952354.473 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:32:34.481Z,1557952354.481 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:32:36.260Z,1557952356.260 [DataOverHttps](INFO): Sending 25 bytes from file Logs/20190515T200927/Courier0007.lzma
2019-05-15T20:32:36.805Z,1557952356.805 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:37.066Z,1557952357.066 [DataOverHttps](INFO): Moved sent file to Logs/20190515T200927/Courier0007.lzma.bak
2019-05-15T20:32:37.067Z,1557952357.067 [DataOverHttps](INFO): SBD MOMSN=11069885
2019-05-15T20:32:40.041Z,1557952360.041 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:40.829Z,1557952360.829 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:32:40.829Z,1557952360.829 [AHRS_M2] Data Fault, FailCount= 3
2019-05-15T20:32:40.829Z,1557952360.829 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:32:40.883Z,1557952360.883 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:32:41.221Z,1557952361.221 [AHRS_M2](INFO): Powering down
2019-05-15T20:32:42.070Z,1557952362.070 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:32:42.070Z,1557952362.070 [AHRS_M2] No Fault, FailCount= 3
2019-05-15T20:32:42.433Z,1557952362.433 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:32:42.857Z,1557952362.857 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:46.173Z,1557952366.173 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:47.525Z,1557952367.525 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:32:47.525Z,1557952367.525 [CTD_Seabird] Communications Fault, FailCount= 3
2019-05-15T20:32:47.525Z,1557952367.525 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:32:47.735Z,1557952367.735 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:32:47.735Z,1557952367.735 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-05-15T20:32:47.929Z,1557952367.929 [CTD_Seabird](INFO): Powering down
2019-05-15T20:32:48.929Z,1557952368.929 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:51.757Z,1557952371.757 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:53.777Z,1557952373.777 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:55.777Z,1557952375.777 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:32:55.777Z,1557952375.777 [AHRS_M2] Data Fault, FailCount= 4
2019-05-15T20:32:55.777Z,1557952375.777 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:32:55.809Z,1557952375.809 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:32:55.844Z,1557952375.844 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:32:56.169Z,1557952376.169 [AHRS_M2](INFO): Powering down
2019-05-15T20:32:57.015Z,1557952377.015 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:32:57.015Z,1557952377.015 [AHRS_M2] No Fault, FailCount= 4
2019-05-15T20:32:57.381Z,1557952377.381 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:32:59.013Z,1557952379.013 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:01.857Z,1557952381.857 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:05.089Z,1557952385.089 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:07.913Z,1557952387.913 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:10.725Z,1557952390.725 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:33:10.725Z,1557952390.725 [AHRS_M2] Data Fault, FailCount= 5
2019-05-15T20:33:10.725Z,1557952390.725 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:33:10.741Z,1557952390.741 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:10.813Z,1557952390.813 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:33:10.814Z,1557952390.814 [CBIT](CRITICAL): Data Fault in component: AHRS_M2
2019-05-15T20:33:11.117Z,1557952391.117 [AHRS_M2](INFO): Powering down
2019-05-15T20:33:11.249Z,1557952391.249 [CBIT](INFO): Critical error at 20190515T203310
2019-05-15T20:33:12.749Z,1557952392.749 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:14.773Z,1557952394.773 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:16.793Z,1557952396.793 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:20.025Z,1557952400.025 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:22.853Z,1557952402.853 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:26.085Z,1557952406.085 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:28.917Z,1557952408.917 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:32.145Z,1557952412.145 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:34.973Z,1557952414.973 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:37.801Z,1557952417.801 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:39.838Z,1557952419.838 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-05-15T20:33:39.839Z,1557952419.839 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 4
2019-05-15T20:33:39.839Z,1557952419.839 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-05-15T20:33:39.849Z,1557952419.849 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-05-15T20:33:40.242Z,1557952420.242 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-05-15T20:33:40.243Z,1557952420.243 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 4
2019-05-15T20:33:41.033Z,1557952421.033 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:43.857Z,1557952423.857 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:47.089Z,1557952427.089 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:49.921Z,1557952429.921 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:52.749Z,1557952432.749 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:54.769Z,1557952434.769 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:33:56.789Z,1557952436.789 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:00.017Z,1557952440.017 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:02.845Z,1557952442.845 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:06.077Z,1557952446.077 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:08.909Z,1557952448.909 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:12.141Z,1557952452.141 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:14.179Z,1557952454.179 [Default:CheckIn:Read_GPS](INFO): Timed out from 2019-05-15T20:29:14.0Z
2019-05-15T20:34:14.179Z,1557952454.179 [Default:CheckIn:Read_GPS] Stopped
2019-05-15T20:34:14.179Z,1557952454.179 [Default:CheckIn:Read_Iridium] Running Loop=1
2019-05-15T20:34:14.575Z,1557952454.575 [Default:CheckIn:Read_Iridium](DEBUG): Initialize ReadDataComponent to sense platform_communications
2019-05-15T20:34:14.977Z,1557952454.977 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:17.793Z,1557952457.793 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:21.025Z,1557952461.025 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:23.853Z,1557952463.853 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:27.089Z,1557952467.089 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:29.916Z,1557952469.916 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:32.741Z,1557952472.741 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:34.761Z,1557952474.761 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:36.785Z,1557952476.785 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:40.021Z,1557952480.021 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:42.845Z,1557952482.845 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:46.073Z,1557952486.073 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:48.905Z,1557952488.905 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:52.133Z,1557952492.133 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:54.965Z,1557952494.965 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:34:57.789Z,1557952497.789 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:01.021Z,1557952501.021 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:03.853Z,1557952503.853 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:07.081Z,1557952507.081 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:09.909Z,1557952509.909 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:12.737Z,1557952512.737 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:14.757Z,1557952514.757 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:16.781Z,1557952516.781 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:17.623Z,1557952517.623 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:35:17.623Z,1557952517.623 [CTD_Seabird] No Fault, FailCount= 3
2019-05-15T20:35:17.961Z,1557952517.961 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:35:17.980Z,1557952517.980 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:35:20.009Z,1557952520.009 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:22.841Z,1557952522.841 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:26.069Z,1557952526.069 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:28.909Z,1557952528.909 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:32.017Z,1557952532.017 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:35:32.017Z,1557952532.017 [CTD_Seabird] Communications Fault, FailCount= 1
2019-05-15T20:35:32.017Z,1557952532.017 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:35:32.129Z,1557952532.129 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:32.169Z,1557952532.169 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:35:32.421Z,1557952532.421 [CTD_Seabird](INFO): Powering down
2019-05-15T20:35:33.367Z,1557952533.367 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:35:33.367Z,1557952533.367 [CTD_Seabird] No Fault, FailCount= 1
2019-05-15T20:35:33.769Z,1557952533.769 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:35:33.771Z,1557952533.771 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:35:34.960Z,1557952534.960 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:37.785Z,1557952537.785 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:40.648Z,1557952540.648 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-05-15T20:35:40.648Z,1557952540.648 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 5
2019-05-15T20:35:40.648Z,1557952540.648 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-05-15T20:35:40.658Z,1557952540.658 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-05-15T20:35:41.017Z,1557952541.017 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:41.065Z,1557952541.065 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-05-15T20:35:41.066Z,1557952541.066 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 5
2019-05-15T20:35:43.849Z,1557952543.849 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:46.821Z,1557952546.821 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:35:46.821Z,1557952546.821 [CTD_Seabird] Communications Fault, FailCount= 2
2019-05-15T20:35:46.821Z,1557952546.821 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:35:47.078Z,1557952547.078 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:47.138Z,1557952547.138 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:35:47.225Z,1557952547.225 [CTD_Seabird](INFO): Powering down
2019-05-15T20:35:48.335Z,1557952548.335 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:35:48.335Z,1557952548.335 [CTD_Seabird] No Fault, FailCount= 2
2019-05-15T20:35:48.569Z,1557952548.569 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:35:48.577Z,1557952548.577 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:35:49.909Z,1557952549.909 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:53.141Z,1557952553.141 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:55.969Z,1557952555.969 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:35:58.793Z,1557952558.793 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:36:01.622Z,1557952561.622 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:36:01.622Z,1557952561.622 [CTD_Seabird] Communications Fault, FailCount= 3
2019-05-15T20:36:01.622Z,1557952561.622 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:36:01.640Z,1557952561.640 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:36:01.641Z,1557952561.641 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-05-15T20:36:02.025Z,1557952562.025 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:36:02.025Z,1557952562.025 [CTD_Seabird](INFO): Powering down
2019-05-15T20:36:04.853Z,1557952564.853 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:36:08.085Z,1557952568.085 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:36:10.913Z,1557952570.913 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:36:13.741Z,1557952573.741 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:36:15.770Z,1557952575.770 [NAL9602](FAULT): GPS failed to acquire within timeout.
2019-05-15T20:36:15.770Z,1557952575.770 [NAL9602] Data Fault, FailCount= 1
2019-05-15T20:36:15.770Z,1557952575.770 [NAL9602](ERROR): Data Fault
2019-05-15T20:36:15.845Z,1557952575.845 [CBIT](ERROR): Data Fault in component: NAL9602
2019-05-15T20:36:16.154Z,1557952576.154 [NAL9602](INFO): Powering down
2019-05-15T20:36:16.994Z,1557952576.994 [CBIT](INFO): Clearing failed state for component NAL9602
2019-05-15T20:36:16.995Z,1557952576.995 [NAL9602] No Fault, FailCount= 1
2019-05-15T20:36:46.454Z,1557952606.454 [NAL9602](INFO): Powering up NAL9602
2019-05-15T20:36:54.601Z,1557952614.601 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:36:54.601Z,1557952614.601 [BR_Ping1D] No Fault, FailCount= 5
2019-05-15T20:36:54.952Z,1557952614.952 [BR_Ping1D](INFO): Start
2019-05-15T20:36:55.764Z,1557952615.764 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:55.764Z,1557952615.764 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:36:55.777Z,1557952615.777 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:36:55.778Z,1557952615.778 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:36:55.779Z,1557952615.779 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:36:55.780Z,1557952615.780 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:36:56.566Z,1557952616.566 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:56.566Z,1557952616.566 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:36:56.567Z,1557952616.567 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:36:56.568Z,1557952616.568 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:36:56.569Z,1557952616.569 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:36:56.983Z,1557952616.983 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:56.984Z,1557952616.984 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:56.984Z,1557952616.984 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:36:56.984Z,1557952616.984 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:36:57.049Z,1557952617.049 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:36:57.049Z,1557952617.049 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:57.049Z,1557952617.049 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:57.049Z,1557952617.049 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:36:57.359Z,1557952617.359 [NAL9602](INFO): NAL9602 initialized
2019-05-15T20:36:57.373Z,1557952617.373 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:57.373Z,1557952617.373 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:57.373Z,1557952617.373 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:57.374Z,1557952617.374 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:57.374Z,1557952617.374 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:36:57.781Z,1557952617.781 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:57.781Z,1557952617.781 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:57.781Z,1557952617.781 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:57.781Z,1557952617.781 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:57.781Z,1557952617.781 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:36:58.181Z,1557952618.181 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:36:58.195Z,1557952618.195 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:58.196Z,1557952618.196 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:58.196Z,1557952618.196 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:58.196Z,1557952618.196 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:58.196Z,1557952618.196 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:36:58.603Z,1557952618.603 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:58.603Z,1557952618.603 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:58.603Z,1557952618.603 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:58.603Z,1557952618.603 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:58.604Z,1557952618.604 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:36:59.003Z,1557952619.003 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:59.004Z,1557952619.004 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:59.004Z,1557952619.004 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:59.004Z,1557952619.004 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:59.004Z,1557952619.004 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:36:59.397Z,1557952619.397 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:59.398Z,1557952619.398 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:59.398Z,1557952619.398 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:59.398Z,1557952619.398 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:59.398Z,1557952619.398 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:36:59.801Z,1557952619.801 [BR_Ping1D](INFO): readConfig
2019-05-15T20:36:59.801Z,1557952619.801 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:36:59.802Z,1557952619.802 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:36:59.802Z,1557952619.802 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:36:59.802Z,1557952619.802 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:00.207Z,1557952620.207 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:00.208Z,1557952620.208 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:00.208Z,1557952620.208 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:00.208Z,1557952620.208 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:00.208Z,1557952620.208 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:00.614Z,1557952620.614 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:00.614Z,1557952620.614 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:00.614Z,1557952620.614 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:00.614Z,1557952620.614 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:00.614Z,1557952620.614 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:01.009Z,1557952621.009 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:01.024Z,1557952621.024 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:01.024Z,1557952621.024 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:01.024Z,1557952621.024 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:37:01.024Z,1557952621.024 [BR_Ping1D] Data Fault, FailCount= 1
2019-05-15T20:37:01.024Z,1557952621.024 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:37:01.071Z,1557952621.071 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:37:01.431Z,1557952621.431 [BR_Ping1D](INFO): Stop
2019-05-15T20:37:01.432Z,1557952621.432 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:37:01.432Z,1557952621.432 [BR_Ping1D](INFO): Powering down
2019-05-15T20:37:01.836Z,1557952621.836 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:02.229Z,1557952622.229 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:02.628Z,1557952622.628 [BR_Ping1D](INFO): Stopped
2019-05-15T20:37:02.651Z,1557952622.651 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:37:02.651Z,1557952622.651 [BR_Ping1D] No Fault, FailCount= 1
2019-05-15T20:37:03.033Z,1557952623.033 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:03.047Z,1557952623.047 [BR_Ping1D](INFO): Start
2019-05-15T20:37:03.851Z,1557952623.851 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:03.852Z,1557952623.852 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:37:03.865Z,1557952623.865 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:37:03.865Z,1557952623.865 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:37:03.865Z,1557952623.865 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:37:03.866Z,1557952623.866 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:37:04.645Z,1557952624.645 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:04.645Z,1557952624.645 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:37:04.646Z,1557952624.646 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:37:04.646Z,1557952624.646 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:37:04.646Z,1557952624.646 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:37:05.053Z,1557952625.053 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:05.053Z,1557952625.053 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:05.053Z,1557952625.053 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:37:05.053Z,1557952625.053 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:37:05.117Z,1557952625.117 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:37:05.117Z,1557952625.117 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:05.117Z,1557952625.117 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:05.117Z,1557952625.117 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:05.457Z,1557952625.457 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:05.457Z,1557952625.457 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:05.458Z,1557952625.458 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:05.458Z,1557952625.458 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:05.458Z,1557952625.458 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:05.861Z,1557952625.861 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:05.861Z,1557952625.861 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:05.862Z,1557952625.862 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:05.862Z,1557952625.862 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:05.862Z,1557952625.862 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:06.261Z,1557952626.261 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:06.275Z,1557952626.275 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:06.276Z,1557952626.276 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:06.276Z,1557952626.276 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:06.276Z,1557952626.276 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:06.276Z,1557952626.276 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:06.684Z,1557952626.684 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:06.684Z,1557952626.684 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:06.684Z,1557952626.684 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:06.684Z,1557952626.684 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:06.684Z,1557952626.684 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:07.083Z,1557952627.083 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:07.083Z,1557952627.083 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:07.084Z,1557952627.084 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:07.084Z,1557952627.084 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:07.084Z,1557952627.084 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:07.480Z,1557952627.480 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:07.480Z,1557952627.480 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:07.481Z,1557952627.481 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:07.481Z,1557952627.481 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:07.481Z,1557952627.481 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:07.881Z,1557952627.881 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:07.881Z,1557952627.881 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:07.881Z,1557952627.881 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:07.881Z,1557952627.881 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:07.881Z,1557952627.881 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:08.290Z,1557952628.290 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:08.290Z,1557952628.290 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:08.290Z,1557952628.290 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:08.290Z,1557952628.290 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:08.290Z,1557952628.290 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:08.688Z,1557952628.688 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:08.688Z,1557952628.688 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:08.689Z,1557952628.689 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:08.689Z,1557952628.689 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:08.689Z,1557952628.689 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:09.089Z,1557952629.089 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:09.104Z,1557952629.104 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:09.104Z,1557952629.104 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:09.104Z,1557952629.104 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:37:09.104Z,1557952629.104 [BR_Ping1D] Data Fault, FailCount= 2
2019-05-15T20:37:09.104Z,1557952629.104 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:37:09.182Z,1557952629.182 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:37:09.511Z,1557952629.511 [BR_Ping1D](INFO): Stop
2019-05-15T20:37:09.512Z,1557952629.512 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:37:09.512Z,1557952629.512 [BR_Ping1D](INFO): Powering down
2019-05-15T20:37:09.912Z,1557952629.912 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:10.305Z,1557952630.305 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:10.713Z,1557952630.713 [BR_Ping1D](INFO): Stopped
2019-05-15T20:37:10.750Z,1557952630.750 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:37:10.750Z,1557952630.750 [BR_Ping1D] No Fault, FailCount= 2
2019-05-15T20:37:11.112Z,1557952631.112 [BR_Ping1D](INFO): Start
2019-05-15T20:37:11.921Z,1557952631.921 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:11.921Z,1557952631.921 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:37:11.933Z,1557952631.933 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:37:11.933Z,1557952631.933 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:37:11.933Z,1557952631.933 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:37:11.934Z,1557952631.934 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:37:12.321Z,1557952632.321 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:12.747Z,1557952632.747 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:12.747Z,1557952632.747 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:37:12.747Z,1557952632.747 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:37:12.749Z,1557952632.749 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:37:12.750Z,1557952632.750 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:37:13.144Z,1557952633.144 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:13.144Z,1557952633.144 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:13.144Z,1557952633.144 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:37:13.144Z,1557952633.144 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:37:13.213Z,1557952633.213 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:37:13.213Z,1557952633.213 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:13.214Z,1557952633.214 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:13.214Z,1557952633.214 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:13.540Z,1557952633.540 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:13.541Z,1557952633.541 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:13.541Z,1557952633.541 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:13.541Z,1557952633.541 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:13.541Z,1557952633.541 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:13.942Z,1557952633.942 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:13.943Z,1557952633.943 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:13.943Z,1557952633.943 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:13.943Z,1557952633.943 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:13.943Z,1557952633.943 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:14.348Z,1557952634.348 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:14.348Z,1557952634.348 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:14.348Z,1557952634.348 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:14.349Z,1557952634.349 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:14.349Z,1557952634.349 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:14.749Z,1557952634.749 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:14.749Z,1557952634.749 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:14.750Z,1557952634.750 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:14.750Z,1557952634.750 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:14.750Z,1557952634.750 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:15.149Z,1557952635.149 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:15.163Z,1557952635.163 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:15.164Z,1557952635.164 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:15.164Z,1557952635.164 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:15.164Z,1557952635.164 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:15.164Z,1557952635.164 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:15.571Z,1557952635.571 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:15.571Z,1557952635.571 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:15.571Z,1557952635.571 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:15.572Z,1557952635.572 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:15.572Z,1557952635.572 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:15.971Z,1557952635.971 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:15.971Z,1557952635.971 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:15.972Z,1557952635.972 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:15.972Z,1557952635.972 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:15.972Z,1557952635.972 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:16.362Z,1557952636.362 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:16.362Z,1557952636.362 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:16.362Z,1557952636.362 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:16.363Z,1557952636.363 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:16.363Z,1557952636.363 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:16.769Z,1557952636.769 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:16.769Z,1557952636.769 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:16.770Z,1557952636.770 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:16.770Z,1557952636.770 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:16.770Z,1557952636.770 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:17.174Z,1557952637.174 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:17.174Z,1557952637.174 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:17.174Z,1557952637.174 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:37:17.174Z,1557952637.174 [BR_Ping1D] Data Fault, FailCount= 3
2019-05-15T20:37:17.174Z,1557952637.174 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:37:17.202Z,1557952637.202 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:37:17.581Z,1557952637.581 [BR_Ping1D](INFO): Stop
2019-05-15T20:37:17.581Z,1557952637.581 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:37:17.581Z,1557952637.581 [BR_Ping1D](INFO): Powering down
2019-05-15T20:37:17.977Z,1557952637.977 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:17.997Z,1557952637.997 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:18.402Z,1557952638.402 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:18.800Z,1557952638.800 [BR_Ping1D](INFO): Stopped
2019-05-15T20:37:18.838Z,1557952638.838 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:37:18.838Z,1557952638.838 [BR_Ping1D] No Fault, FailCount= 3
2019-05-15T20:37:19.197Z,1557952639.197 [BR_Ping1D](INFO): Start
2019-05-15T20:37:20.001Z,1557952640.001 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:20.015Z,1557952640.015 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:20.015Z,1557952640.015 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:37:20.029Z,1557952640.029 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:37:20.030Z,1557952640.030 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:37:20.031Z,1557952640.031 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:37:20.032Z,1557952640.032 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:37:20.819Z,1557952640.819 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:20.819Z,1557952640.819 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:37:20.820Z,1557952640.820 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:37:20.820Z,1557952640.820 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:37:20.820Z,1557952640.820 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:37:21.218Z,1557952641.218 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:21.219Z,1557952641.219 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:21.219Z,1557952641.219 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:37:21.219Z,1557952641.219 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:37:21.293Z,1557952641.293 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:37:21.293Z,1557952641.293 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:21.293Z,1557952641.293 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:21.293Z,1557952641.293 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:21.617Z,1557952641.617 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:21.617Z,1557952641.617 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:21.617Z,1557952641.617 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:21.617Z,1557952641.617 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:21.618Z,1557952641.618 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:22.017Z,1557952642.017 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:22.032Z,1557952642.032 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:22.032Z,1557952642.032 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:22.032Z,1557952642.032 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:22.032Z,1557952642.032 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:22.032Z,1557952642.032 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:22.439Z,1557952642.439 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:22.439Z,1557952642.439 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:22.440Z,1557952642.440 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:22.440Z,1557952642.440 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:22.440Z,1557952642.440 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:22.840Z,1557952642.840 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:22.840Z,1557952642.840 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:22.840Z,1557952642.840 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:22.840Z,1557952642.840 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:22.841Z,1557952642.841 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:23.232Z,1557952643.232 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:23.233Z,1557952643.233 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:23.233Z,1557952643.233 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:23.233Z,1557952643.233 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:23.233Z,1557952643.233 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:23.637Z,1557952643.637 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:23.637Z,1557952643.637 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:23.637Z,1557952643.637 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:23.637Z,1557952643.637 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:23.637Z,1557952643.637 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:24.041Z,1557952644.040 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:24.041Z,1557952644.041 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:24.041Z,1557952644.041 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:24.041Z,1557952644.041 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:24.041Z,1557952644.041 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:24.451Z,1557952644.451 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:24.451Z,1557952644.451 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:24.451Z,1557952644.451 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:24.451Z,1557952644.451 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:24.451Z,1557952644.451 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:24.848Z,1557952644.848 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:24.857Z,1557952644.857 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:24.857Z,1557952644.857 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:24.858Z,1557952644.858 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:24.858Z,1557952644.858 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:25.249Z,1557952645.249 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:25.264Z,1557952645.264 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:25.264Z,1557952645.264 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:25.264Z,1557952645.264 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:37:25.264Z,1557952645.264 [BR_Ping1D] Data Fault, FailCount= 4
2019-05-15T20:37:25.264Z,1557952645.264 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:37:25.310Z,1557952645.310 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:37:25.671Z,1557952645.671 [BR_Ping1D](INFO): Stop
2019-05-15T20:37:25.671Z,1557952645.671 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:37:25.671Z,1557952645.671 [BR_Ping1D](INFO): Powering down
2019-05-15T20:37:26.108Z,1557952646.108 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:26.465Z,1557952646.465 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:26.869Z,1557952646.869 [BR_Ping1D](INFO): Stopped
2019-05-15T20:37:26.921Z,1557952646.921 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-05-15T20:37:26.921Z,1557952646.921 [BR_Ping1D] No Fault, FailCount= 4
2019-05-15T20:37:27.273Z,1557952647.273 [BR_Ping1D](INFO): Start
2019-05-15T20:37:28.073Z,1557952648.073 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:28.092Z,1557952648.092 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:28.092Z,1557952648.092 [BR_Ping1D](INFO): UART setting parameters ...
2019-05-15T20:37:28.105Z,1557952648.105 [BR_Ping1D](INFO): Sending UART packet: 42520200EC030000F4017A02
2019-05-15T20:37:28.105Z,1557952648.105 [BR_Ping1D](INFO): Sending UART packet: 42520100EB030000018401
2019-05-15T20:37:28.105Z,1557952648.105 [BR_Ping1D](INFO): Sending UART packet: 42520400EA03000000EED11C6003
2019-05-15T20:37:28.106Z,1557952648.106 [BR_Ping1D](INFO): Sending UART packet: 42520100EE030000018701
2019-05-15T20:37:28.900Z,1557952648.900 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:28.901Z,1557952648.901 [BR_Ping1D](INFO): UART requesting status
2019-05-15T20:37:28.901Z,1557952648.901 [BR_Ping1D](INFO): Sending UART packet: 42520000BA0400005201
2019-05-15T20:37:28.902Z,1557952648.902 [BR_Ping1D](INFO): Sending UART packet: 42520000BF0400005701
2019-05-15T20:37:28.902Z,1557952648.902 [BR_Ping1D](INFO): Sending UART packet: 42520000B30400004B01
2019-05-15T20:37:29.292Z,1557952649.292 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:29.293Z,1557952649.293 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:29.293Z,1557952649.293 [BR_Ping1D](ERROR): Using more than 1 sec to receive one packet, resetting UART
2019-05-15T20:37:29.293Z,1557952649.293 [BR_Ping1D](INFO): Reset of UART receiver requested
2019-05-15T20:37:29.357Z,1557952649.357 [BR_Ping1D](INFO): device response: 00A8
2019-05-15T20:37:29.357Z,1557952649.357 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:29.357Z,1557952649.357 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:29.357Z,1557952649.357 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:29.697Z,1557952649.697 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:29.697Z,1557952649.697 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:29.697Z,1557952649.697 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:29.697Z,1557952649.697 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:29.697Z,1557952649.697 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:30.101Z,1557952650.101 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:30.101Z,1557952650.101 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:30.101Z,1557952650.101 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:30.102Z,1557952650.102 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:30.102Z,1557952650.102 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:30.505Z,1557952650.505 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:30.505Z,1557952650.505 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:30.505Z,1557952650.505 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:30.506Z,1557952650.506 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:30.506Z,1557952650.506 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:30.909Z,1557952650.909 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:30.909Z,1557952650.909 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:30.909Z,1557952650.909 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:30.909Z,1557952650.909 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:30.910Z,1557952650.910 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:31.309Z,1557952651.309 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:31.323Z,1557952651.323 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:31.324Z,1557952651.324 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:31.324Z,1557952651.324 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:31.324Z,1557952651.324 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:31.324Z,1557952651.324 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:31.734Z,1557952651.734 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:31.735Z,1557952651.735 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:31.735Z,1557952651.735 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:31.735Z,1557952651.735 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:31.735Z,1557952651.735 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:32.131Z,1557952652.131 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:32.132Z,1557952652.132 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:32.132Z,1557952652.132 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:32.132Z,1557952652.132 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:32.132Z,1557952652.132 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:32.525Z,1557952652.525 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:32.525Z,1557952652.525 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:32.526Z,1557952652.526 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:32.526Z,1557952652.526 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:32.526Z,1557952652.526 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:32.928Z,1557952652.928 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:32.930Z,1557952652.930 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:32.930Z,1557952652.930 [BR_Ping1D](INFO): Not enough UART bytes for header try again on next cycle
2019-05-15T20:37:32.930Z,1557952652.930 [BR_Ping1D](INFO): received UART packets: 0
2019-05-15T20:37:32.930Z,1557952652.930 [BR_Ping1D](INFO): not all values verified yet
2019-05-15T20:37:33.334Z,1557952653.334 [BR_Ping1D](INFO): readConfig
2019-05-15T20:37:33.334Z,1557952653.334 [BR_Ping1D](INFO): UART waiting for response
2019-05-15T20:37:33.334Z,1557952653.334 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-05-15T20:37:33.334Z,1557952653.334 [BR_Ping1D] Data Fault, FailCount= 5
2019-05-15T20:37:33.334Z,1557952653.334 [BR_Ping1D](ERROR): Data Fault
2019-05-15T20:37:33.366Z,1557952653.366 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-05-15T20:37:33.366Z,1557952653.366 [CBIT](CRITICAL): Data Fault in component: BR_Ping1D
2019-05-15T20:37:33.737Z,1557952653.737 [BR_Ping1D](INFO): Stop
2019-05-15T20:37:33.737Z,1557952653.737 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:37:33.737Z,1557952653.737 [BR_Ping1D](INFO): Powering down
2019-05-15T20:37:33.856Z,1557952653.856 [CBIT](INFO): Critical error at 20190515T203733
2019-05-15T20:37:34.137Z,1557952654.137 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:34.152Z,1557952654.152 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:34.563Z,1557952654.563 [BR_Ping1D](INFO): Stopping
2019-05-15T20:37:34.963Z,1557952654.963 [BR_Ping1D](INFO): Stopped
2019-05-15T20:37:37.369Z,1557952657.369 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:40.197Z,1557952660.197 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:41.829Z,1557952661.829 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-05-15T20:37:41.829Z,1557952661.829 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 6
2019-05-15T20:37:41.829Z,1557952661.829 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-05-15T20:37:41.839Z,1557952661.839 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-05-15T20:37:42.243Z,1557952662.243 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-05-15T20:37:42.243Z,1557952662.243 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 6
2019-05-15T20:37:43.026Z,1557952663.026 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:46.257Z,1557952666.257 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:49.092Z,1557952669.092 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:52.321Z,1557952672.321 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:55.145Z,1557952675.145 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:57.977Z,1557952677.977 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:37:59.993Z,1557952679.993 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:02.013Z,1557952682.013 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:04.037Z,1557952684.037 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:07.265Z,1557952687.265 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:10.097Z,1557952690.097 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:10.969Z,1557952690.969 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:38:10.969Z,1557952690.969 [AHRS_M2] No Fault, FailCount= 5
2019-05-15T20:38:11.289Z,1557952691.289 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:38:13.325Z,1557952693.325 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:16.169Z,1557952696.169 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:18.993Z,1557952698.993 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:21.017Z,1557952701.017 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:24.245Z,1557952704.245 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:24.633Z,1557952704.633 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:38:24.633Z,1557952704.633 [AHRS_M2] Data Fault, FailCount= 1
2019-05-15T20:38:24.633Z,1557952704.633 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:38:24.714Z,1557952704.714 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:38:25.025Z,1557952705.025 [AHRS_M2](INFO): Powering down
2019-05-15T20:38:25.872Z,1557952705.872 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:38:25.872Z,1557952705.872 [AHRS_M2] No Fault, FailCount= 1
2019-05-15T20:38:26.237Z,1557952706.237 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:38:27.065Z,1557952707.065 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:30.305Z,1557952710.305 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:31.944Z,1557952711.944 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:38:31.944Z,1557952711.944 [CTD_Seabird] No Fault, FailCount= 3
2019-05-15T20:38:32.073Z,1557952712.073 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:38:32.075Z,1557952712.075 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:38:33.137Z,1557952713.137 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:36.409Z,1557952716.409 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:39.204Z,1557952719.204 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:39.589Z,1557952719.589 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:38:39.589Z,1557952719.589 [AHRS_M2] Data Fault, FailCount= 2
2019-05-15T20:38:39.589Z,1557952719.589 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:38:39.699Z,1557952719.699 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:38:39.981Z,1557952719.981 [AHRS_M2](INFO): Powering down
2019-05-15T20:38:40.842Z,1557952720.842 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:38:40.842Z,1557952720.842 [AHRS_M2] No Fault, FailCount= 2
2019-05-15T20:38:41.194Z,1557952721.194 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:38:42.017Z,1557952722.017 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:45.133Z,1557952725.133 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:38:45.133Z,1557952725.133 [CTD_Seabird] Communications Fault, FailCount= 1
2019-05-15T20:38:45.133Z,1557952725.133 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:38:45.261Z,1557952725.261 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:45.330Z,1557952725.330 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:38:45.537Z,1557952725.537 [CTD_Seabird](INFO): Powering down
2019-05-15T20:38:46.518Z,1557952726.518 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:38:46.518Z,1557952726.518 [CTD_Seabird] No Fault, FailCount= 1
2019-05-15T20:38:46.878Z,1557952726.878 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:38:46.880Z,1557952726.880 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:38:48.089Z,1557952728.089 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:51.321Z,1557952731.321 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:54.149Z,1557952734.149 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:54.537Z,1557952734.537 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:38:54.537Z,1557952734.537 [AHRS_M2] Data Fault, FailCount= 3
2019-05-15T20:38:54.537Z,1557952734.537 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:38:54.595Z,1557952734.595 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:38:54.929Z,1557952734.929 [AHRS_M2](INFO): Powering down
2019-05-15T20:38:55.794Z,1557952735.794 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:38:55.794Z,1557952735.794 [AHRS_M2] No Fault, FailCount= 3
2019-05-15T20:38:56.141Z,1557952736.141 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:38:56.965Z,1557952736.965 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:58.993Z,1557952738.993 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:38:59.933Z,1557952739.933 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:38:59.933Z,1557952739.933 [CTD_Seabird] Communications Fault, FailCount= 2
2019-05-15T20:38:59.933Z,1557952739.933 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:39:00.249Z,1557952740.249 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:39:00.337Z,1557952740.337 [CTD_Seabird](INFO): Powering down
2019-05-15T20:39:01.462Z,1557952741.462 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-05-15T20:39:01.462Z,1557952741.462 [CTD_Seabird] No Fault, FailCount= 2
2019-05-15T20:39:01.682Z,1557952741.682 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-05-15T20:39:01.683Z,1557952741.683 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-05-15T20:39:02.233Z,1557952742.233 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:05.061Z,1557952745.061 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:08.293Z,1557952748.293 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:09.485Z,1557952749.485 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:39:09.485Z,1557952749.485 [AHRS_M2] Data Fault, FailCount= 4
2019-05-15T20:39:09.485Z,1557952749.485 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:39:09.562Z,1557952749.562 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:39:09.877Z,1557952749.877 [AHRS_M2](INFO): Powering down
2019-05-15T20:39:10.724Z,1557952750.724 [CBIT](INFO): Clearing failed state for component AHRS_M2
2019-05-15T20:39:10.724Z,1557952750.724 [AHRS_M2] No Fault, FailCount= 4
2019-05-15T20:39:11.089Z,1557952751.089 [AHRS_M2](DEBUG): Initializing AHRS_M2.
2019-05-15T20:39:11.113Z,1557952751.113 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:14.361Z,1557952754.361 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:14.733Z,1557952754.733 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-05-15T20:39:14.733Z,1557952754.733 [CTD_Seabird] Communications Fault, FailCount= 3
2019-05-15T20:39:14.733Z,1557952754.733 [CTD_Seabird](ERROR): Communications Fault
2019-05-15T20:39:14.882Z,1557952754.882 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-05-15T20:39:14.883Z,1557952754.883 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-05-15T20:39:15.137Z,1557952755.137 [CTD_Seabird](INFO): Powering down
2019-05-15T20:39:17.181Z,1557952757.181 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:20.005Z,1557952760.005 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:22.029Z,1557952762.029 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:24.433Z,1557952764.433 [AHRS_M2](FAULT): Failed to acquire valid data within timeout.
2019-05-15T20:39:24.433Z,1557952764.433 [AHRS_M2] Data Fault, FailCount= 5
2019-05-15T20:39:24.433Z,1557952764.433 [AHRS_M2](ERROR): Data Fault
2019-05-15T20:39:24.486Z,1557952764.486 [CBIT](ERROR): Data Fault in component: AHRS_M2
2019-05-15T20:39:24.487Z,1557952764.487 [CBIT](CRITICAL): Data Fault in component: AHRS_M2
2019-05-15T20:39:24.825Z,1557952764.825 [AHRS_M2](INFO): Powering down
2019-05-15T20:39:24.959Z,1557952764.959 [CBIT](INFO): Critical error at 20190515T203924
2019-05-15T20:39:25.245Z,1557952765.245 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:28.077Z,1557952768.077 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:31.305Z,1557952771.305 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:34.137Z,1557952774.137 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:37.365Z,1557952777.365 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:40.193Z,1557952780.193 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:42.664Z,1557952782.664 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-05-15T20:39:42.664Z,1557952782.664 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 7
2019-05-15T20:39:42.664Z,1557952782.664 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-05-15T20:39:42.674Z,1557952782.674 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-05-15T20:39:43.021Z,1557952783.021 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:43.075Z,1557952783.075 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-05-15T20:39:43.075Z,1557952783.075 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 7
2019-05-15T20:39:46.253Z,1557952786.253 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:49.113Z,1557952789.113 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:52.321Z,1557952792.321 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:55.149Z,1557952795.149 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:57.981Z,1557952797.981 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:39:59.997Z,1557952799.997 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:02.021Z,1557952802.021 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:05.249Z,1557952805.249 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:08.081Z,1557952808.081 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:11.309Z,1557952811.309 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:14.141Z,1557952814.141 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:17.372Z,1557952817.372 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:17.865Z,1557952817.865 [CommandLine](IMPORTANT): got command 
2019-05-15T20:40:17.866Z,1557952817.866 [CommandLine](FAULT): Incomplete syntax. Try: help
2019-05-15T20:40:20.201Z,1557952820.201 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:23.025Z,1557952823.025 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:26.257Z,1557952826.257 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:29.085Z,1557952829.085 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:31.615Z,1557952831.615 [CommandLine](IMPORTANT): got command restart application
2019-05-15T20:40:32.317Z,1557952832.317 [NAL9602](DEBUG): Fix Requested
2019-05-15T20:40:32.621Z,1557952832.621 [CommandLine ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:32.621Z,1557952832.621 [CommandLine ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:32.725Z,1557952832.725 [Supervisor](DEBUG): Uninitializing supervisor and starting cleanup.  Bye!
2019-05-15T20:40:32.725Z,1557952832.725 [CommandLine ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:32.726Z,1557952832.726 [CommandLine](INFO): Join timeout helper Thread ID is 2865
2019-05-15T20:40:32.727Z,1557952832.727 [ComponentRegistry](INFO): Shutting down NavChartDb ThreadHandler
2019-05-15T20:40:32.727Z,1557952832.727 [NavChartDb ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:32.730Z,1557952832.730 [NavChartDb](INFO): Join timeout helper Thread ID is 2866
2019-05-15T20:40:32.937Z,1557952832.937 [NavChartDb ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:32.937Z,1557952832.937 [NavChartDb ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:32.957Z,1557952832.957 [ComponentRegistry](INFO): Shutting down WetLabsBB2FL ThreadHandler
2019-05-15T20:40:32.957Z,1557952832.957 [WetLabsBB2FL ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:32.957Z,1557952832.957 [WetLabsBB2FL](INFO): Join timeout helper Thread ID is 2867
2019-05-15T20:40:33.403Z,1557952833.403 [WetLabsBB2FL ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:33.403Z,1557952833.403 [WetLabsBB2FL](INFO): Powering down
2019-05-15T20:40:33.404Z,1557952833.404 [WetLabsBB2FL ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:33.409Z,1557952833.409 [ComponentRegistry](INFO): Shutting down CTD_Seabird ThreadHandler
2019-05-15T20:40:33.409Z,1557952833.409 [CTD_Seabird ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:33.409Z,1557952833.409 [CTD_Seabird](INFO): Join timeout helper Thread ID is 2868
2019-05-15T20:40:33.681Z,1557952833.681 [CTD_Seabird ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:33.681Z,1557952833.681 [CTD_Seabird](INFO): Powering down
2019-05-15T20:40:33.693Z,1557952833.693 [CTD_Seabird ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:33.701Z,1557952833.701 [ComponentRegistry](INFO): Shutting down CTD_NeilBrown ThreadHandler
2019-05-15T20:40:33.701Z,1557952833.701 [CTD_NeilBrown ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:33.701Z,1557952833.701 [CTD_NeilBrown](INFO): Join timeout helper Thread ID is 2869
2019-05-15T20:40:33.785Z,1557952833.785 [CTD_NeilBrown ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:33.785Z,1557952833.785 [CTD_NeilBrown ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:33.802Z,1557952833.802 [ComponentRegistry](INFO): Shutting down Radio_Surface ThreadHandler
2019-05-15T20:40:33.802Z,1557952833.802 [Radio_Surface ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:33.802Z,1557952833.802 [Radio_Surface](INFO): Join timeout helper Thread ID is 2870
2019-05-15T20:40:34.109Z,1557952834.109 [Radio_Surface](INFO): Powering down
2019-05-15T20:40:34.110Z,1557952834.110 [Radio_Surface ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:34.110Z,1557952834.110 [Radio_Surface ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:34.114Z,1557952834.114 [ComponentRegistry](INFO): Shutting down DataOverHttps ThreadHandler
2019-05-15T20:40:34.114Z,1557952834.114 [DataOverHttps ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:34.114Z,1557952834.114 [DataOverHttps](INFO): Join timeout helper Thread ID is 2871
2019-05-15T20:40:34.785Z,1557952834.785 [DataOverHttps ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:34.788Z,1557952834.788 [DataOverHttps ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:34.802Z,1557952834.802 [ComponentRegistry](INFO): Shutting down logger ThreadHandler
2019-05-15T20:40:34.802Z,1557952834.802 [logger ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:34.802Z,1557952834.802 [logger](INFO): Join timeout helper Thread ID is 2872
2019-05-15T20:40:34.857Z,1557952834.857 [logger ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:34.857Z,1557952834.857 [logger ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:34.862Z,1557952834.862 [ComponentRegistry](INFO): Shutting down CommandLine ThreadHandler
2019-05-15T20:40:34.862Z,1557952834.862 [CommandLine ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:34.862Z,1557952834.862 [ComponentRegistry](INFO): Shutting down controlThread ThreadHandler
2019-05-15T20:40:34.862Z,1557952834.862 [controlThread ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:34.862Z,1557952834.862 [controlThread](INFO): Join timeout helper Thread ID is 2873
2019-05-15T20:40:35.125Z,1557952835.125 [controlThread ThreadHandler](INFO): Uninitializing protected caller thread.
2019-05-15T20:40:35.125Z,1557952835.125 [controlThread](DEBUG): Uninitializing ControlThread
2019-05-15T20:40:35.126Z,1557952835.126 [AHRS_M2](INFO): Powering down
2019-05-15T20:40:35.127Z,1557952835.127 [NAL9602](INFO): Powering down
2019-05-15T20:40:35.128Z,1557952835.128 [BR_Ping1D](INFO): uninitialize
2019-05-15T20:40:35.128Z,1557952835.128 [BR_Ping1D](INFO): Powering down
2019-05-15T20:40:35.129Z,1557952835.129 [DepthRateCalculator](DEBUG): Uninitializing DepthRateCalculator.
2019-05-15T20:40:35.130Z,1557952835.130 [ElevatorOffsetCalculator](DEBUG): Uninitializing ElevatorOffsetCalculator.
2019-05-15T20:40:35.131Z,1557952835.131 [NavChart](DEBUG): Uninitialize NavChart Navigation.
2019-05-15T20:40:35.131Z,1557952835.131 [MissionManager](INFO): Uninitializing Mission Default
2019-05-15T20:40:35.131Z,1557952835.131 [Default] Stopped
2019-05-15T20:40:35.131Z,1557952835.131 [Default](DEBUG): Aggregate::uninitialize Default
2019-05-15T20:40:35.132Z,1557952835.132 [Default:B.GoToSurface] Stopped
2019-05-15T20:40:35.132Z,1557952835.132 [Default:B.GoToSurface](DEBUG): Uninitialize GoToSurfaceComponent.
2019-05-15T20:40:35.132Z,1557952835.132 [Default:CheckIn] Stopped
2019-05-15T20:40:35.132Z,1557952835.132 [Default:CheckIn](DEBUG): Aggregate::uninitialize Default:CheckIn
2019-05-15T20:40:35.132Z,1557952835.132 [Default:CheckIn:Read_Iridium] Stopped
2019-05-15T20:40:35.134Z,1557952835.134 [VerticalControl](DEBUG): Uninitialize VerticalControlComponent.
2019-05-15T20:40:35.134Z,1557952835.134 [HorizontalControl](DEBUG): Uninitialize HorizontalControlComponent.
2019-05-15T20:40:35.135Z,1557952835.135 [SpeedControl](DEBUG): Uninitialize SpeedControlComponent.
2019-05-15T20:40:35.135Z,1557952835.135 [LoopControl](DEBUG): Uninitialize LoopControlComponent.
2019-05-15T20:40:35.135Z,1557952835.135 [BuoyancyServo](DEBUG): Uninitialize Buoyancy Servo.
2019-05-15T20:40:35.135Z,1557952835.135 [BuoyancyServo](INFO): Powering down
2019-05-15T20:40:35.149Z,1557952835.149 [ElevatorServo](DEBUG): Uninitialize Elevator Servo.
2019-05-15T20:40:35.149Z,1557952835.149 [ElevatorServo](INFO): Powering down
2019-05-15T20:40:35.150Z,1557952835.150 [MassServo](DEBUG): Uninitialize Mass Servo.
2019-05-15T20:40:35.150Z,1557952835.150 [MassServo](INFO): Powering down
2019-05-15T20:40:35.151Z,1557952835.151 [RudderServo](DEBUG): Uninitialize Rudder Servo.
2019-05-15T20:40:35.151Z,1557952835.151 [RudderServo](INFO): Powering down
2019-05-15T20:40:35.152Z,1557952835.152 [ThrusterServo](DEBUG): Uninitialize Thruster Servo.
2019-05-15T20:40:35.152Z,1557952835.152 [ThrusterServo](INFO): Powering down
2019-05-15T20:40:35.153Z,1557952835.153 [SBIT](DEBUG): Uninitialize SBIT Component.
2019-05-15T20:40:35.153Z,1557952835.153 [IBIT](DEBUG): Uninitialize IBIT Component.
2019-05-15T20:40:35.153Z,1557952835.153 [CBIT](DEBUG): Uninitialize CBIT Component.
2019-05-15T20:40:35.153Z,1557952835.153 [CBIT](DEBUG): Powering off loads.
2019-05-15T20:40:35.165Z,1557952835.165 [CBIT](DEBUG): Disabling WDT.
2019-05-15T20:40:35.177Z,1557952835.177 [CBIT](DEBUG): Opening all GF detection circuits.
2019-05-15T20:40:35.178Z,1557952835.178 [controlThread ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:35.247Z,1557952835.247 [Radio_Surface ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:35.253Z,1557952835.253 [DataOverHttps ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:35.292Z,1557952835.292 [WetLabsBB2FL ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:35.295Z,1557952835.295 [CTD_Seabird ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:35.298Z,1557952835.298 [CTD_NeilBrown ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:35.328Z,1557952835.328 [NavChartDb ThreadHandler](INFO): Thread cancelled.
2019-05-15T20:40:35.384Z,1557952835.384 [logger ThreadHandler](INFO): Thread cancelled.