2019-04-10T00:58:34.657Z,1554857914.657 [Supervisor](DEBUG): Initializing supervisor.
2019-04-10T00:58:34.660Z,1554857914.660 [SyncHandler](DEBUG): Created PCaller Thread at 404514E0
2019-04-10T00:58:34.661Z,1554857914.661 [SyncHandler](INFO): Protected caller Thread ID is 808
2019-04-10T00:58:34.662Z,1554857914.662 [ComponentRegistry](DEBUG): Component "controlThread" handled in its own thread.
2019-04-10T00:58:34.663Z,1554857914.663 [controlThread ThreadHandler](DEBUG): Created PCaller Thread at 404814E0
2019-04-10T00:58:34.663Z,1554857914.663 [controlThread ThreadHandler](INFO): Protected caller Thread ID is 809
2019-04-10T00:58:34.666Z,1554857914.666 [ComponentRegistry](DEBUG): SyncComponent "CycleStarter" handled in the control thread.
2019-04-10T00:58:34.678Z,1554857914.678 [ComponentRegistry](DEBUG): Component "CommandLine" handled in its own thread.
2019-04-10T00:58:34.679Z,1554857914.679 [CommandLine ThreadHandler](DEBUG): Created PCaller Thread at 404B14E0
2019-04-10T00:58:34.680Z,1554857914.680 [CommandLine ThreadHandler](INFO): Protected caller Thread ID is 810
2019-04-10T00:58:34.681Z,1554857914.681 [ComponentRegistry](DEBUG): Component "logger" handled in its own thread.
2019-04-10T00:58:34.681Z,1554857914.681 [logger ThreadHandler](DEBUG): Created PCaller Thread at 404E14E0
2019-04-10T00:58:34.682Z,1554857914.682 [logger ThreadHandler](INFO): Protected caller Thread ID is 811
2019-04-10T00:58:34.684Z,1554857914.684 [ComponentRegistry](DEBUG): SyncComponent "LogSplitter" handled in the control thread.
2019-04-10T00:58:34.684Z,1554857914.684 [Supervisor](INFO): Looking for Config files in directory: Config/
2019-04-10T00:58:34.686Z,1554857914.686 [Supervisor](INFO): Opening Config file at: Config/secure.cfg
2019-04-10T00:58:34.779Z,1554857914.779 [ComponentRegistry](DEBUG): Loaded Config Component "Config/secure
2019-04-10T00:58:34.780Z,1554857914.780 [Supervisor](INFO): Opening Config file at: Config/Navigation.cfg
2019-04-10T00:58:34.979Z,1554857914.979 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Navigation
2019-04-10T00:58:34.980Z,1554857914.980 [Supervisor](INFO): Opening Config file at: Config/Estimation.cfg
2019-04-10T00:58:35.115Z,1554857915.115 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Estimation
2019-04-10T00:58:35.116Z,1554857915.116 [Supervisor](INFO): Opening Config file at: Config/Sensor.cfg
2019-04-10T00:58:35.571Z,1554857915.571 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Sensor
2019-04-10T00:58:35.572Z,1554857915.572 [Supervisor](INFO): Opening Config file at: Config/vehicle.cfg
2019-04-10T00:58:36.011Z,1554857916.011 [ComponentRegistry](DEBUG): Loaded Config Component "Config/vehicle
2019-04-10T00:58:36.011Z,1554857916.011 [Supervisor](INFO): Opening Config file at: Config/Simulator.cfg
2019-04-10T00:58:36.476Z,1554857916.476 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Simulator
2019-04-10T00:58:36.477Z,1554857916.477 [Supervisor](INFO): Opening Config file at: Config/Servo.cfg
2019-04-10T00:58:36.797Z,1554857916.797 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Servo
2019-04-10T00:58:36.798Z,1554857916.798 [Supervisor](INFO): Opening Config file at: Config/Control.cfg
2019-04-10T00:58:37.520Z,1554857917.520 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Control
2019-04-10T00:58:37.520Z,1554857917.520 [Supervisor](INFO): Opening Config file at: Config/Science.cfg
2019-04-10T00:58:37.913Z,1554857917.913 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Science
2019-04-10T00:58:37.914Z,1554857917.914 [Supervisor](INFO): Opening Config file at: Config/Derivation.cfg
2019-04-10T00:58:38.062Z,1554857918.062 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Derivation
2019-04-10T00:58:38.063Z,1554857918.063 [Supervisor](INFO): Opening Config file at: Config/workSite.cfg
2019-04-10T00:58:38.166Z,1554857918.166 [ComponentRegistry](DEBUG): Loaded Config Component "Config/workSite
2019-04-10T00:58:38.167Z,1554857918.167 [Supervisor](INFO): Opening Config file at: Config/Guidance.cfg
2019-04-10T00:58:38.247Z,1554857918.247 [Supervisor](INFO): Opening Config file at: Config/Sample.cfg
2019-04-10T00:58:38.347Z,1554857918.347 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Sample
2019-04-10T00:58:38.347Z,1554857918.347 [Supervisor](INFO): Opening Config file at: Config/logger.cfg
2019-04-10T00:58:38.541Z,1554857918.541 [ComponentRegistry](DEBUG): Loaded Config Component "Config/logger
2019-04-10T00:58:38.541Z,1554857918.541 [Supervisor](INFO): Opening Config file at: Config/BIT.cfg
2019-04-10T00:58:38.747Z,1554857918.747 [ComponentRegistry](DEBUG): Loaded Config Component "Config/BIT
2019-04-10T00:58:38.749Z,1554857918.749 [Supervisor](INFO): Looking for Config files in directory: Config/lrauv-makai/
2019-04-10T00:58:38.750Z,1554857918.750 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/secure.cfg
2019-04-10T00:58:38.832Z,1554857918.832 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/Battery.cfg
2019-04-10T00:58:39.062Z,1554857919.062 [ComponentRegistry](DEBUG): Loaded Config Component "Config/Battery
2019-04-10T00:58:39.062Z,1554857919.062 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/Navigation.cfg
2019-04-10T00:58:39.156Z,1554857919.156 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/Sensor.cfg
2019-04-10T00:58:39.329Z,1554857919.329 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/vehicle.cfg
2019-04-10T00:58:39.541Z,1554857919.541 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/Simulator.cfg
2019-04-10T00:58:39.625Z,1554857919.625 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/Servo.cfg
2019-04-10T00:58:39.721Z,1554857919.721 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/Control.cfg
2019-04-10T00:58:39.813Z,1554857919.813 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/Science.cfg
2019-04-10T00:58:39.963Z,1554857919.963 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/logger.cfg
2019-04-10T00:58:40.066Z,1554857920.066 [Supervisor](INFO): Opening Config file at: Config/lrauv-makai/BIT.cfg
2019-04-10T00:58:40.163Z,1554857920.163 [Supervisor](INFO): Looking for Config files in directory: Config/lrauv-makai/root/
2019-04-10T00:58:40.164Z,1554857920.164 [Supervisor](IMPORTANT): Reading configuration overrides from Data/persisted.cfg
2019-04-10T00:58:40.168Z,1554857920.168 [Module Loader](DEBUG): Loading Module at Modules/Simulator.so
2019-04-10T00:58:40.265Z,1554857920.265 [Module Loader](DEBUG): Loaded Module: Simulator (This is the module containing the Simulator)
2019-04-10T00:58:40.266Z,1554857920.266 [Module Loader](DEBUG): Loading Module at Modules/Servo.so
2019-04-10T00:58:40.393Z,1554857920.393 [BuoyancyServo] Loaded
2019-04-10T00:58:40.393Z,1554857920.393 [ComponentRegistry](DEBUG): SyncComponent "BuoyancyServo" handled in the control thread.
2019-04-10T00:58:40.408Z,1554857920.408 [ElevatorServo] Loaded
2019-04-10T00:58:40.408Z,1554857920.408 [ComponentRegistry](DEBUG): SyncComponent "ElevatorServo" handled in the control thread.
2019-04-10T00:58:40.423Z,1554857920.423 [MassServo] Loaded
2019-04-10T00:58:40.424Z,1554857920.424 [ComponentRegistry](DEBUG): SyncComponent "MassServo" handled in the control thread.
2019-04-10T00:58:40.439Z,1554857920.439 [RudderServo] Loaded
2019-04-10T00:58:40.439Z,1554857920.439 [ComponentRegistry](DEBUG): SyncComponent "RudderServo" handled in the control thread.
2019-04-10T00:58:40.453Z,1554857920.453 [ThrusterServo] Loaded
2019-04-10T00:58:40.453Z,1554857920.453 [ComponentRegistry](DEBUG): SyncComponent "ThrusterServo" handled in the control thread.
2019-04-10T00:58:40.454Z,1554857920.454 [Module Loader](DEBUG): Loaded Module: Servo (This is the module containing motor controllers)
2019-04-10T00:58:40.454Z,1554857920.454 [Module Loader](DEBUG): Loading Module at Modules/BIT.so
2019-04-10T00:58:40.587Z,1554857920.587 [SBIT](DEBUG): Construct Startup Built In Test.
2019-04-10T00:58:40.616Z,1554857920.616 [SBIT] Loaded
2019-04-10T00:58:40.616Z,1554857920.616 [ComponentRegistry](DEBUG): SyncComponent "SBIT" handled in the control thread.
2019-04-10T00:58:40.617Z,1554857920.617 [IBIT](DEBUG): Construct Initiated Built In Test.
2019-04-10T00:58:40.644Z,1554857920.644 [IBIT] Loaded
2019-04-10T00:58:40.645Z,1554857920.645 [ComponentRegistry](DEBUG): SyncComponent "IBIT" handled in the control thread.
2019-04-10T00:58:40.648Z,1554857920.648 [CBIT](DEBUG): Construct Continuous Built In Test.
2019-04-10T00:58:41.032Z,1554857921.032 [CBIT] Loaded
2019-04-10T00:58:41.032Z,1554857921.032 [ComponentRegistry](DEBUG): SyncComponent "CBIT" handled in the control thread.
2019-04-10T00:58:41.032Z,1554857921.032 [Module Loader](DEBUG): Loaded Module: BIT (Contains the BuiltInTest components, such as C Built In Test)
2019-04-10T00:58:41.033Z,1554857921.033 [Module Loader](DEBUG): Loading Module at Modules/Science.so
2019-04-10T00:58:41.214Z,1554857921.214 [Aanderaa_O2] Loaded
2019-04-10T00:58:41.214Z,1554857921.214 [ComponentRegistry](DEBUG): SyncComponent "Aanderaa_O2" handled in the control thread.
2019-04-10T00:58:41.224Z,1554857921.224 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_density
2019-04-10T00:58:41.229Z,1554857921.229 [CTD_Seabird](INFO): created writer for : sea_water_density
2019-04-10T00:58:41.231Z,1554857921.231 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): depth
2019-04-10T00:58:41.236Z,1554857921.236 [CTD_Seabird](INFO): created writer for : depth
2019-04-10T00:58:41.236Z,1554857921.236 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_pressure
2019-04-10T00:58:41.242Z,1554857921.242 [CTD_Seabird](INFO): created writer for : sea_water_pressure
2019-04-10T00:58:41.242Z,1554857921.242 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_salinity
2019-04-10T00:58:41.247Z,1554857921.247 [CTD_Seabird](INFO): created writer for : sea_water_salinity
2019-04-10T00:58:41.248Z,1554857921.248 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_temperature
2019-04-10T00:58:41.253Z,1554857921.253 [CTD_Seabird](INFO): created writer for : sea_water_temperature
2019-04-10T00:58:41.254Z,1554857921.254 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): sea_water_electrical_conductivity
2019-04-10T00:58:41.259Z,1554857921.259 [CTD_Seabird](INFO): created writer for : sea_water_electrical_conductivity
2019-04-10T00:58:41.260Z,1554857921.260 [CTD_Seabird](DEBUG): LcmSlateWriter::add(): speed_of_sound_in_sea_water
2019-04-10T00:58:41.265Z,1554857921.265 [CTD_Seabird](INFO): created writer for : speed_of_sound_in_sea_water
2019-04-10T00:58:41.291Z,1554857921.291 [CTD_Seabird] Loaded
2019-04-10T00:58:41.292Z,1554857921.292 [ComponentRegistry](DEBUG): Component "CTD_Seabird" handled in its own thread.
2019-04-10T00:58:41.293Z,1554857921.293 [CTD_Seabird ThreadHandler](DEBUG): Created PCaller Thread at 406654E0
2019-04-10T00:58:41.293Z,1554857921.293 [CTD_Seabird ThreadHandler](INFO): Protected caller Thread ID is 890
2019-04-10T00:58:41.319Z,1554857921.319 [ESPComponent] Loaded
2019-04-10T00:58:41.319Z,1554857921.319 [ComponentRegistry](DEBUG): SyncComponent "ESPComponent" handled in the control thread.
2019-04-10T00:58:41.333Z,1554857921.333 [PAR_Licor] Loaded
2019-04-10T00:58:41.333Z,1554857921.333 [ComponentRegistry](DEBUG): SyncComponent "PAR_Licor" handled in the control thread.
2019-04-10T00:58:41.381Z,1554857921.381 [WetLabsBB2FL] Loaded
2019-04-10T00:58:41.381Z,1554857921.381 [ComponentRegistry](DEBUG): Component "WetLabsBB2FL" handled in its own thread.
2019-04-10T00:58:41.382Z,1554857921.382 [WetLabsBB2FL ThreadHandler](DEBUG): Created PCaller Thread at 406954E0
2019-04-10T00:58:41.382Z,1554857921.382 [WetLabsBB2FL ThreadHandler](INFO): Protected caller Thread ID is 891
2019-04-10T00:58:41.383Z,1554857921.383 [Module Loader](DEBUG): Loaded Module: Science (Contains the science components)
2019-04-10T00:58:41.384Z,1554857921.384 [Module Loader](DEBUG): Loading Module at Modules/Derivation.so
2019-04-10T00:58:41.423Z,1554857921.423 [DepthRateCalculator] Loaded
2019-04-10T00:58:41.424Z,1554857921.424 [ComponentRegistry](DEBUG): SyncComponent "DepthRateCalculator" handled in the control thread.
2019-04-10T00:58:41.429Z,1554857921.429 [PitchRateCalculator] Loaded
2019-04-10T00:58:41.430Z,1554857921.430 [ComponentRegistry](DEBUG): SyncComponent "PitchRateCalculator" handled in the control thread.
2019-04-10T00:58:41.445Z,1554857921.445 [SpeedCalculator] Loaded
2019-04-10T00:58:41.446Z,1554857921.446 [ComponentRegistry](DEBUG): SyncComponent "SpeedCalculator" handled in the control thread.
2019-04-10T00:58:41.467Z,1554857921.467 [TempGradientCalculator] Loaded
2019-04-10T00:58:41.467Z,1554857921.467 [ComponentRegistry](DEBUG): SyncComponent "TempGradientCalculator" handled in the control thread.
2019-04-10T00:58:41.473Z,1554857921.473 [YawRateCalculator] Loaded
2019-04-10T00:58:41.473Z,1554857921.473 [ComponentRegistry](DEBUG): SyncComponent "YawRateCalculator" handled in the control thread.
2019-04-10T00:58:41.507Z,1554857921.507 [ElevatorOffsetCalculator] Loaded
2019-04-10T00:58:41.507Z,1554857921.507 [ComponentRegistry](DEBUG): SyncComponent "ElevatorOffsetCalculator" handled in the control thread.
2019-04-10T00:58:41.507Z,1554857921.507 [Module Loader](DEBUG): Loaded Module: Derivation (Contains the base derivation components)
2019-04-10T00:58:41.508Z,1554857921.508 [Module Loader](DEBUG): Loading Module at Modules/Trigger.so
2019-04-10T00:58:41.534Z,1554857921.534 [Module Loader](DEBUG): Loaded Module: Trigger (Contains triggers for use in missions)
2019-04-10T00:58:41.535Z,1554857921.535 [Module Loader](DEBUG): Loading Module at Modules/Navigation.so
2019-04-10T00:58:41.637Z,1554857921.637 [DeadReckonUsingMultipleVelocitySources] Loaded
2019-04-10T00:58:41.637Z,1554857921.637 [ComponentRegistry](DEBUG): SyncComponent "DeadReckonUsingMultipleVelocitySources" handled in the control thread.
2019-04-10T00:58:41.697Z,1554857921.697 [DeadReckonUsingSpeedCalculator] Loaded
2019-04-10T00:58:41.697Z,1554857921.697 [ComponentRegistry](DEBUG): SyncComponent "DeadReckonUsingSpeedCalculator" handled in the control thread.
2019-04-10T00:58:41.756Z,1554857921.756 [DeadReckonWithRespectToSeafloor] Loaded
2019-04-10T00:58:41.757Z,1554857921.757 [ComponentRegistry](DEBUG): SyncComponent "DeadReckonWithRespectToSeafloor" handled in the control thread.
2019-04-10T00:58:41.777Z,1554857921.777 [NavChart] Loaded
2019-04-10T00:58:41.778Z,1554857921.778 [ComponentRegistry](DEBUG): SyncComponent "NavChart" handled in the control thread.
2019-04-10T00:58:41.782Z,1554857921.782 [UniversalFixResidualReporter] Loaded
2019-04-10T00:58:41.782Z,1554857921.782 [ComponentRegistry](DEBUG): SyncComponent "UniversalFixResidualReporter" handled in the control thread.
2019-04-10T00:58:41.782Z,1554857921.782 [Module Loader](DEBUG): Loaded Module: Navigation (Contains the base navigation components)
2019-04-10T00:58:41.783Z,1554857921.783 [Module Loader](DEBUG): Loading Module at Modules/Sensor.so
2019-04-10T00:58:42.878Z,1554857922.878 [AcousticModem_Benthos_ATM900] Loaded
2019-04-10T00:58:42.879Z,1554857922.879 [ComponentRegistry](DEBUG): SyncComponent "AcousticModem_Benthos_ATM900" handled in the control thread.
2019-04-10T00:58:42.950Z,1554857922.950 [DataOverHttps] Loaded
2019-04-10T00:58:42.950Z,1554857922.950 [ComponentRegistry](DEBUG): Component "DataOverHttps" handled in its own thread.
2019-04-10T00:58:42.951Z,1554857922.951 [DataOverHttps ThreadHandler](DEBUG): Created PCaller Thread at 409714E0
2019-04-10T00:58:42.952Z,1554857922.952 [DataOverHttps ThreadHandler](INFO): Protected caller Thread ID is 892
2019-04-10T00:58:42.965Z,1554857922.965 [Depth_Keller] Loaded
2019-04-10T00:58:42.965Z,1554857922.965 [ComponentRegistry](DEBUG): SyncComponent "Depth_Keller" handled in the control thread.
2019-04-10T00:58:43.056Z,1554857923.056 [NAL9602] Loaded
2019-04-10T00:58:43.057Z,1554857923.057 [ComponentRegistry](DEBUG): SyncComponent "NAL9602" handled in the control thread.
2019-04-10T00:58:43.062Z,1554857923.062 [Onboard] Loaded
2019-04-10T00:58:43.062Z,1554857923.062 [ComponentRegistry](DEBUG): SyncComponent "Onboard" handled in the control thread.
2019-04-10T00:58:43.065Z,1554857923.065 [Radio_Surface] Loaded
2019-04-10T00:58:43.066Z,1554857923.066 [ComponentRegistry](DEBUG): Component "Radio_Surface" handled in its own thread.
2019-04-10T00:58:43.067Z,1554857923.067 [Radio_Surface ThreadHandler](DEBUG): Created PCaller Thread at 409A14E0
2019-04-10T00:58:43.067Z,1554857923.067 [Radio_Surface ThreadHandler](INFO): Protected caller Thread ID is 893
2019-04-10T00:58:44.352Z,1554857924.352 [BPC1] Loaded
2019-04-10T00:58:44.352Z,1554857924.352 [ComponentRegistry](DEBUG): SyncComponent "BPC1" handled in the control thread.
2019-04-10T00:58:44.383Z,1554857924.383 [BR_Ping1D](CRITICAL): No configuration setting for: BR_Ping1D.minrange
2019-04-10T00:58:44.385Z,1554857924.385 [BR_Ping1D](CRITICAL): No configuration setting for: BR_Ping1D.maxrange
2019-04-10T00:58:44.387Z,1554857924.387 [BR_Ping1D](CRITICAL): No configuration setting for: BR_Ping1D.soundspeed
2019-04-10T00:58:44.389Z,1554857924.389 [BR_Ping1D](CRITICAL): No configuration setting for: BR_Ping1D.automode
2019-04-10T00:58:44.391Z,1554857924.391 [BR_Ping1D](CRITICAL): No configuration setting for: BR_Ping1D.gainindex
2019-04-10T00:58:44.393Z,1554857924.393 [BR_Ping1D](CRITICAL): No configuration setting for: BR_Ping1D.minconfidence
2019-04-10T00:58:44.395Z,1554857924.395 [BR_Ping1D](CRITICAL): No configuration setting for: BR_Ping1D.pingenable
2019-04-10T00:58:44.397Z,1554857924.397 [BR_Ping1D] Loaded
2019-04-10T00:58:44.398Z,1554857924.398 [ComponentRegistry](DEBUG): SyncComponent "BR_Ping1D" handled in the control thread.
2019-04-10T00:58:44.398Z,1554857924.398 [Module Loader](DEBUG): Loaded Module: Sensor (Contains the sensor components)
2019-04-10T00:58:44.399Z,1554857924.399 [Module Loader](DEBUG): Loading Module at Modules/Estimation.so
2019-04-10T00:58:44.462Z,1554857924.462 [Module Loader](DEBUG): Loaded Module: Estimation (Contains the base estimation components)
2019-04-10T00:58:44.462Z,1554857924.462 [Module Loader](DEBUG): Loading Module at Modules/Control.so
2019-04-10T00:58:44.528Z,1554857924.528 [VerticalControl](DEBUG): Construct VerticalControl.
2019-04-10T00:58:44.612Z,1554857924.612 [VerticalControl] Loaded
2019-04-10T00:58:44.612Z,1554857924.612 [ComponentRegistry](DEBUG): SyncComponent "VerticalControl" handled in the control thread.
2019-04-10T00:58:44.613Z,1554857924.613 [HorizontalControl](DEBUG): Construct HorizontalControl.
2019-04-10T00:58:44.670Z,1554857924.670 [HorizontalControl] Loaded
2019-04-10T00:58:44.671Z,1554857924.671 [ComponentRegistry](DEBUG): SyncComponent "HorizontalControl" handled in the control thread.
2019-04-10T00:58:44.671Z,1554857924.671 [SpeedControl](DEBUG): Construct SpeedControl.
2019-04-10T00:58:44.673Z,1554857924.673 [SpeedControl] Loaded
2019-04-10T00:58:44.673Z,1554857924.673 [ComponentRegistry](DEBUG): SyncComponent "SpeedControl" handled in the control thread.
2019-04-10T00:58:44.674Z,1554857924.674 [LoopControl](DEBUG): Construct LoopControl.
2019-04-10T00:58:44.675Z,1554857924.675 [LoopControl] Loaded
2019-04-10T00:58:44.675Z,1554857924.675 [ComponentRegistry](DEBUG): SyncComponent "LoopControl" handled in the control thread.
2019-04-10T00:58:44.675Z,1554857924.675 [Module Loader](DEBUG): Loaded Module: Control (Contains the Control components, such as Depth, Heading, and Speed Control)
2019-04-10T00:58:44.676Z,1554857924.676 [Module Loader](DEBUG): Loading Module at Modules/Sample.so
2019-04-10T00:58:44.689Z,1554857924.689 [Module Loader](DEBUG): Loaded Module: Sample (This is a Sample Module of Sample Components)
2019-04-10T00:58:44.690Z,1554857924.690 [Module Loader](DEBUG): Loading Module at Modules/Guidance.so
2019-04-10T00:58:44.963Z,1554857924.963 [Module Loader](DEBUG): Loaded Module: Guidance (Contains behaviors and commands)
2019-04-10T00:58:44.967Z,1554857924.967 [ComponentRegistry](DEBUG): SyncComponent "MissionManager" handled in the control thread.
2019-04-10T00:58:44.968Z,1554857924.968 [ComponentRegistry](DEBUG): SyncComponent "Reporter" handled in the control thread.
2019-04-10T00:58:44.974Z,1554857924.974 [ComponentRegistry](DEBUG): Component "NavChartDb" handled in its own thread.
2019-04-10T00:58:44.975Z,1554857924.975 [NavChartDb ThreadHandler](DEBUG): Created PCaller Thread at 40ACE4E0
2019-04-10T00:58:44.976Z,1554857924.976 [NavChartDb ThreadHandler](INFO): Protected caller Thread ID is 894
2019-04-10T00:58:44.981Z,1554857924.981 [Supervisor](INFO): Main Thread ID is 9999
2019-04-10T00:58:44.981Z,1554857924.981 [Supervisor](DEBUG): Running supervisor.
2019-04-10T00:58:44.981Z,1554857924.981 [CommandLine ThreadHandler](INFO): Handler Thread ID is 895
2019-04-10T00:58:44.984Z,1554857924.984 [controlThread ThreadHandler](INFO): Handler Thread ID is 896
2019-04-10T00:58:44.984Z,1554857924.984 [controlThread](DEBUG): Initializing ControlThread
2019-04-10T00:58:44.986Z,1554857924.986 [SBIT](INFO): Initialize SBIT Component.
2019-04-10T00:58:44.987Z,1554857924.987 [SBIT](IMPORTANT): git: 2019-03-18-31-ge98d5dc
2019-04-10T00:58:44.987Z,1554857924.987 [SBIT](INFO): git hash: e98d5dc50cbc39e402f19b9946ff4dc0776c8725
2019-04-10T00:58:44.987Z,1554857924.987 [SBIT](IMPORTANT): Kernel Release: 2.6.27.8
2019-04-10T00:58:44.989Z,1554857924.989 [SBIT](INFO): Kernel Reporting Different Version From Configuration.
Kernel Expected: #2 PREEMPT Thu Jan 11 20:13:48 PST 2018
Kernel Reported: #1 PREEMPT Thu Feb 21 11:17:40 PST 2019
2019-04-10T00:58:44.990Z,1554857924.990 [SBIT](INFO): Beginning SBIT in 24.000000 seconds.
2019-04-10T00:58:44.990Z,1554857924.990 [IBIT](INFO): Initialize IBIT Component.
2019-04-10T00:58:44.991Z,1554857924.991 [CBIT](DEBUG): Initialize CBIT Component.
2019-04-10T00:58:44.992Z,1554857924.992 [logger ThreadHandler](INFO): Handler Thread ID is 897
2019-04-10T00:58:45.002Z,1554857925.002 [CBIT](DEBUG): Initialized mux pins.
2019-04-10T00:58:45.002Z,1554857925.002 [CBIT](DEBUG): Initializing the watchdog timer.
2019-04-10T00:58:45.010Z,1554857925.010 [CTD_Seabird ThreadHandler](INFO): Handler Thread ID is 898
2019-04-10T00:58:45.011Z,1554857925.011 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T00:58:45.015Z,1554857925.015 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T00:58:45.016Z,1554857925.016 [WetLabsBB2FL ThreadHandler](INFO): Handler Thread ID is 900
2019-04-10T00:58:45.017Z,1554857925.017 [WetLabsBB2FL](INFO): Powering down
2019-04-10T00:58:45.026Z,1554857925.026 [CBIT](INFO): Last reboot was NOT due to watchdog timer.
2019-04-10T00:58:45.026Z,1554857925.026 [CBIT](DEBUG): Initializing heartbeat.
2019-04-10T00:58:45.046Z,1554857925.046 [DataOverHttps ThreadHandler](INFO): Handler Thread ID is 901
2019-04-10T00:58:45.047Z,1554857925.047 [DataOverHttps](DEBUG): dashIP=134.89.2.23 starts with a digit so assuming it is a numeric IP
2019-04-10T00:58:45.055Z,1554857925.055 [Radio_Surface ThreadHandler](INFO): Handler Thread ID is 902
2019-04-10T00:58:45.071Z,1554857925.071 [NavChartDb ThreadHandler](INFO): Handler Thread ID is 903
2019-04-10T00:58:45.074Z,1554857925.074 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US1WC07M.000
2019-04-10T00:58:45.074Z,1554857925.074 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US1WC07M.000
2019-04-10T00:58:45.074Z,1554857925.074 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US2WC11M.000
2019-04-10T00:58:45.074Z,1554857925.074 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US2WC11M.000
2019-04-10T00:58:45.074Z,1554857925.074 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US3CA52M.000
2019-04-10T00:58:45.075Z,1554857925.075 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US3CA52M.000
2019-04-10T00:58:45.075Z,1554857925.075 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US4CA60M.000
2019-04-10T00:58:45.075Z,1554857925.075 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US4CA60M.000
2019-04-10T00:58:45.075Z,1554857925.075 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA50M.000
2019-04-10T00:58:45.075Z,1554857925.075 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA50M.000
2019-04-10T00:58:45.076Z,1554857925.076 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA61M.000
2019-04-10T00:58:45.076Z,1554857925.076 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA61M.000
2019-04-10T00:58:45.076Z,1554857925.076 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA62M.000
2019-04-10T00:58:45.076Z,1554857925.076 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA62M.000
2019-04-10T00:58:45.076Z,1554857925.076 [NavChartDb](INFO): Looking for Electronic Nav Chart file at: Resources/ElectronicNavigationCharts/US5CA83M.000
2019-04-10T00:58:45.076Z,1554857925.076 [NavChartDb](INFO): Already Loaded Electronic Nav Chart data from US5CA83M.000
2019-04-10T00:58:45.098Z,1554857925.098 [CBIT](DEBUG): Deactivating GF circuits.
2019-04-10T00:58:45.098Z,1554857925.098 [CBIT](DEBUG): Deactivating emergency mode.
2019-04-10T00:58:45.134Z,1554857925.134 [CBIT](DEBUG): Backplane powered.
2019-04-10T00:58:45.138Z,1554857925.138 [DepthRateCalculator](DEBUG): Initializing DepthRateCalculator.
2019-04-10T00:58:45.139Z,1554857925.139 [PitchRateCalculator](DEBUG): Initializing PitchRateCalculator.
2019-04-10T00:58:45.139Z,1554857925.139 [SpeedCalculator](DEBUG): Initializing SpeedCalculator.
2019-04-10T00:58:45.139Z,1554857925.139 [TempGradientCalculator](DEBUG): Initializing TempGradientCalculator.
2019-04-10T00:58:45.140Z,1554857925.140 [YawRateCalculator](DEBUG): Initializing YawRateCalculator.
2019-04-10T00:58:45.140Z,1554857925.140 [ElevatorOffsetCalculator](DEBUG): Initializing ElevatorOffsetCalculator.
2019-04-10T00:58:45.141Z,1554857925.141 [DeadReckonUsingSpeedCalculator](DEBUG): Initializing DeadReckonUsingSpeedCalculator component.
2019-04-10T00:58:45.142Z,1554857925.142 [NavChart](DEBUG): Initialize NavChart Navigation.
2019-04-10T00:58:45.143Z,1554857925.143 [UniversalFixResidualReporter](DEBUG): Initializing UniversalFixResidualReporter component.
2019-04-10T00:58:45.147Z,1554857925.147 [VerticalControl](DEBUG): Initialize VerticalControlComponent.
2019-04-10T00:58:45.149Z,1554857925.149 [HorizontalControl](DEBUG): Initialize HorizontalControlComponent.
2019-04-10T00:58:45.150Z,1554857925.150 [SpeedControl](DEBUG): Initialize SpeedControlComponent.
2019-04-10T00:58:45.150Z,1554857925.150 [LoopControl](DEBUG): Initialize LoopControlComponent.
2019-04-10T00:58:45.151Z,1554857925.151 [MissionManager](INFO): Loading Mission: Missions/Startup.xml
2019-04-10T00:58:45.173Z,1554857925.173 [Startup:A.GoToSurface](DEBUG): Construct GoToSurface.
2019-04-10T00:58:45.209Z,1554857925.209 [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-04-10T00:58:45.210Z,1554857925.210 [MissionManager](INFO): Loading Mission: Missions/Default.xml
2019-04-10T00:58:45.295Z,1554857925.295 [MissionManager](INFO): DefineArg Default.ElapsedSinceDefaultStarted = 0.000000 min
2019-04-10T00:58:45.296Z,1554857925.296 [Default:A.Wait](DEBUG): Construct Wait.
2019-04-10T00:58:45.314Z,1554857925.314 [Default:B.GoToSurface](DEBUG): Construct GoToSurface.
2019-04-10T00:58:45.389Z,1554857925.389 [Default:CheckIn:Read_Iridium:A_Timeout:A.Execute](DEBUG): Construct Execute.
2019-04-10T00:58:45.419Z,1554857925.419 [Default:CheckIn:C.Wait](DEBUG): Construct Wait.
2019-04-10T00:58:45.441Z,1554857925.441 [Default:E.Execute](DEBUG): Construct Execute.
2019-04-10T00:58:45.458Z,1554857925.458 [Radio_Surface](INFO): Powering up
2019-04-10T00:58:45.461Z,1554857925.461 [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-04-10T00:58:45.471Z,1554857925.471 [controlThread](DEBUG): Component order: CycleStarter,Aanderaa_O2,ESPComponent,PAR_Licor,AcousticModem_Benthos_ATM900,Depth_Keller,NAL9602,Onboard,BPC1,BR_Ping1D,PAR_Licor,Depth_Keller,DepthRateCalculator,PitchRateCalculator,SpeedCalculator,TempGradientCalculator,YawRateCalculator,ElevatorOffsetCalculator,DeadReckonUsingMultipleVelocitySources,DeadReckonUsingSpeedCalculator,DeadReckonWithRespectToSeafloor,NavChart,UniversalFixResidualReporter,MissionManager,VerticalControl,HorizontalControl,SpeedControl,LoopControl,BuoyancyServo,ElevatorServo,MassServo,RudderServo,ThrusterServo,SBIT,IBIT,CBIT,Reporter,LogSplitter,
2019-04-10T00:58:45.559Z,1554857925.559 [ESPComponent](INFO): powering down ESP
2019-04-10T00:58:46.282Z,1554857926.282 [PAR_Licor](INFO): A/D timeout, 12 tries over 127 ms

2019-04-10T00:58:46.283Z,1554857926.283 [PAR_Licor] Data Fault, FailCount= 1
2019-04-10T00:58:46.283Z,1554857926.283 [PAR_Licor](ERROR): Data Fault
2019-04-10T00:58:46.283Z,1554857926.283 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T00:58:46.284Z,1554857926.284 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T00:58:46.303Z,1554857926.303 [Depth_Keller](ERROR): Pressure reading out of range: 1895.684326 decibar
2019-04-10T00:58:46.359Z,1554857926.359 [DepthRateCalculator](ERROR): Depth measurement is not active
2019-04-10T00:58:46.392Z,1554857926.392 [BuoyancyServo](DEBUG): Initializing EZServoServo.
2019-04-10T00:58:46.426Z,1554857926.426 [BuoyancyServo](DEBUG): Initializing BuoyancyServo.
2019-04-10T00:58:46.428Z,1554857926.428 [ElevatorServo](DEBUG): Initializing EZServoServo.
2019-04-10T00:58:46.448Z,1554857926.448 [ElevatorServo](DEBUG): Initializing ElevatorServo.
2019-04-10T00:58:46.449Z,1554857926.449 [MassServo](DEBUG): Initializing EZServoServo.
2019-04-10T00:58:46.454Z,1554857926.454 [MassServo](DEBUG): Initializing MassServo.
2019-04-10T00:58:46.456Z,1554857926.456 [RudderServo](DEBUG): Initializing EZServoServo.
2019-04-10T00:58:46.463Z,1554857926.463 [RudderServo](DEBUG): Initializing RudderServo.
2019-04-10T00:58:46.464Z,1554857926.464 [ThrusterServo](DEBUG): Initializing EZServoServo.
2019-04-10T00:58:46.475Z,1554857926.475 [ThrusterServo](DEBUG): Initializing ThrusterServo.
2019-04-10T00:58:46.478Z,1554857926.478 [CommandLine](FAULT): Scheduling is paused
2019-04-10T00:58:46.478Z,1554857926.478 [CBIT](INFO): Critical error at 20190410T005844
2019-04-10T00:58:46.478Z,1554857926.478 [Supervisor](INFO): Stop Mission called by CBIT::checkCriticals
2019-04-10T00:58:46.483Z,1554857926.483 [CBIT](ERROR): Data Fault in component: PAR_Licor
2019-04-10T00:58:46.483Z,1554857926.483 [CBIT](INFO): Clearing failed state for component PAR_Licor
2019-04-10T00:58:46.483Z,1554857926.483 [PAR_Licor] No Fault, FailCount= 1
2019-04-10T00:58:46.914Z,1554857926.914 [BR_Ping1D](INFO): startup: 0
2019-04-10T00:58:46.914Z,1554857926.914 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T00:58:46.926Z,1554857926.926 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T00:58:46.926Z,1554857926.926 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T00:58:46.927Z,1554857926.927 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T00:58:46.927Z,1554857926.927 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T00:58:46.927Z,1554857926.927 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T00:58:46.927Z,1554857926.927 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T00:58:46.927Z,1554857926.927 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T00:58:47.434Z,1554857927.434 [PAR_Licor](INFO): A/D timeout, 9 tries over 138 ms

2019-04-10T00:58:47.434Z,1554857927.434 [PAR_Licor] Data Fault, FailCount= 1
2019-04-10T00:58:47.434Z,1554857927.434 [PAR_Licor](ERROR): Data Fault
2019-04-10T00:58:47.475Z,1554857927.475 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:47.475Z,1554857927.475 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:47.476Z,1554857927.476 [BR_Ping1D](INFO): startup: 1
2019-04-10T00:58:47.476Z,1554857927.476 [BR_Ping1D](INFO): UART requesting status
2019-04-10T00:58:47.476Z,1554857927.476 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T00:58:47.482Z,1554857927.482 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T00:58:47.490Z,1554857927.490 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T00:58:47.777Z,1554857927.777 [CBIT](ERROR): Data Fault in component: PAR_Licor
2019-04-10T00:58:47.777Z,1554857927.777 [CBIT](INFO): Clearing failed state for component PAR_Licor
2019-04-10T00:58:47.778Z,1554857927.778 [PAR_Licor] No Fault, FailCount= 1
2019-04-10T00:58:47.817Z,1554857927.817 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:47.817Z,1554857927.817 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:47.818Z,1554857927.818 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:47.818Z,1554857927.818 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:47.818Z,1554857927.818 [BR_Ping1D](INFO): elapsed 0.9043
2019-04-10T00:58:47.818Z,1554857927.818 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:47.819Z,1554857927.819 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:47.819Z,1554857927.819 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:47.819Z,1554857927.819 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:48.332Z,1554857928.332 [PAR_Licor](INFO): A/D timeout, 9 tries over 144 ms

2019-04-10T00:58:48.332Z,1554857928.332 [PAR_Licor] Data Fault, FailCount= 2
2019-04-10T00:58:48.332Z,1554857928.332 [PAR_Licor](ERROR): Data Fault
2019-04-10T00:58:48.371Z,1554857928.371 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:48.371Z,1554857928.371 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:48.371Z,1554857928.371 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:48.371Z,1554857928.371 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:48.371Z,1554857928.371 [BR_Ping1D](INFO): elapsed 1.4576
2019-04-10T00:58:48.372Z,1554857928.372 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:48.372Z,1554857928.372 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:48.372Z,1554857928.372 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:48.372Z,1554857928.372 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:48.402Z,1554857928.402 [CBIT](ERROR): Data Fault in component: PAR_Licor
2019-04-10T00:58:48.402Z,1554857928.402 [CBIT](INFO): Clearing failed state for component PAR_Licor
2019-04-10T00:58:48.402Z,1554857928.402 [PAR_Licor] No Fault, FailCount= 2
2019-04-10T00:58:48.621Z,1554857928.621 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:48.621Z,1554857928.621 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:48.622Z,1554857928.622 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:48.622Z,1554857928.622 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:48.622Z,1554857928.622 [BR_Ping1D](INFO): elapsed 1.7081
2019-04-10T00:58:48.622Z,1554857928.622 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:48.622Z,1554857928.622 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:48.622Z,1554857928.622 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:48.623Z,1554857928.623 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:49.130Z,1554857929.130 [PAR_Licor](INFO): A/D timeout, 8 tries over 134 ms

2019-04-10T00:58:49.130Z,1554857929.130 [PAR_Licor] Data Fault, FailCount= 3
2019-04-10T00:58:49.130Z,1554857929.130 [PAR_Licor](ERROR): Data Fault
2019-04-10T00:58:49.171Z,1554857929.171 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:49.171Z,1554857929.171 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:49.171Z,1554857929.171 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:49.171Z,1554857929.171 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:49.171Z,1554857929.171 [BR_Ping1D](INFO): elapsed 2.2575
2019-04-10T00:58:49.172Z,1554857929.172 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:49.172Z,1554857929.172 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:49.172Z,1554857929.172 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:49.172Z,1554857929.172 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:49.306Z,1554857929.306 [CBIT](ERROR): Data Fault in component: PAR_Licor
2019-04-10T00:58:49.306Z,1554857929.306 [CBIT](CRITICAL): Data Fault in component: PAR_Licor
2019-04-10T00:58:49.417Z,1554857929.417 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:49.417Z,1554857929.417 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:49.417Z,1554857929.417 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:49.417Z,1554857929.417 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:49.418Z,1554857929.418 [BR_Ping1D](INFO): elapsed 2.5038
2019-04-10T00:58:49.418Z,1554857929.418 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:49.418Z,1554857929.418 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:49.418Z,1554857929.418 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:49.418Z,1554857929.418 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:49.459Z,1554857929.459 [CBIT](INFO): Critical error at 20190410T005849
2019-04-10T00:58:49.822Z,1554857929.822 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:49.822Z,1554857929.822 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:49.822Z,1554857929.822 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:49.822Z,1554857929.822 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:49.822Z,1554857929.822 [BR_Ping1D](INFO): elapsed 2.9086
2019-04-10T00:58:49.823Z,1554857929.823 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:49.823Z,1554857929.823 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:49.823Z,1554857929.823 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:49.823Z,1554857929.823 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:50.233Z,1554857930.233 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:50.233Z,1554857930.233 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:50.234Z,1554857930.234 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:50.234Z,1554857930.234 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:50.234Z,1554857930.234 [BR_Ping1D](INFO): elapsed 3.3202
2019-04-10T00:58:50.234Z,1554857930.234 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:50.234Z,1554857930.234 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:50.235Z,1554857930.235 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:50.235Z,1554857930.235 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:50.630Z,1554857930.630 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:50.630Z,1554857930.630 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:50.631Z,1554857930.631 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:50.631Z,1554857930.631 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:50.631Z,1554857930.631 [BR_Ping1D](INFO): elapsed 3.7171
2019-04-10T00:58:50.631Z,1554857930.631 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:50.631Z,1554857930.631 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:50.631Z,1554857930.631 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:50.632Z,1554857930.632 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:51.033Z,1554857931.033 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:51.033Z,1554857931.033 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:51.034Z,1554857931.034 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:51.034Z,1554857931.034 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:51.035Z,1554857931.035 [BR_Ping1D](INFO): elapsed 4.1207
2019-04-10T00:58:51.035Z,1554857931.035 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:51.035Z,1554857931.035 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:51.035Z,1554857931.035 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:51.035Z,1554857931.035 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:51.439Z,1554857931.439 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:51.439Z,1554857931.439 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:51.439Z,1554857931.439 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:51.439Z,1554857931.439 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:51.439Z,1554857931.439 [BR_Ping1D](INFO): elapsed 4.5255
2019-04-10T00:58:51.440Z,1554857931.440 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:51.440Z,1554857931.440 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:51.440Z,1554857931.440 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:51.440Z,1554857931.440 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:51.841Z,1554857931.841 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:51.841Z,1554857931.841 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:51.842Z,1554857931.842 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:51.842Z,1554857931.842 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:51.842Z,1554857931.842 [BR_Ping1D](INFO): elapsed 4.9285
2019-04-10T00:58:51.843Z,1554857931.843 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:51.843Z,1554857931.843 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:51.843Z,1554857931.843 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:51.843Z,1554857931.843 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:52.245Z,1554857932.245 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:52.246Z,1554857932.246 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:52.246Z,1554857932.246 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:52.246Z,1554857932.246 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:52.246Z,1554857932.246 [BR_Ping1D](INFO): elapsed 5.3326
2019-04-10T00:58:52.247Z,1554857932.247 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:52.247Z,1554857932.247 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T00:58:52.247Z,1554857932.247 [BR_Ping1D] Data Fault, FailCount= 1
2019-04-10T00:58:52.247Z,1554857932.247 [BR_Ping1D](ERROR): Data Fault
2019-04-10T00:58:52.314Z,1554857932.314 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T00:58:52.649Z,1554857932.649 [BR_Ping1D](INFO): Stop
2019-04-10T00:58:52.649Z,1554857932.649 [BR_Ping1D](INFO): uninitialize
2019-04-10T00:58:52.649Z,1554857932.649 [BR_Ping1D](INFO): Powering down
2019-04-10T00:58:53.054Z,1554857933.054 [BR_Ping1D](INFO): Stopping
2019-04-10T00:58:53.457Z,1554857933.457 [BR_Ping1D](INFO): Stopping
2019-04-10T00:58:53.862Z,1554857933.862 [BR_Ping1D](INFO): Stopped
2019-04-10T00:58:53.931Z,1554857933.931 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T00:58:53.931Z,1554857933.931 [BR_Ping1D] No Fault, FailCount= 1
2019-04-10T00:58:54.265Z,1554857934.265 [BR_Ping1D](INFO): Start
2019-04-10T00:58:54.670Z,1554857934.670 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:55.086Z,1554857935.086 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:55.086Z,1554857935.086 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:55.086Z,1554857935.086 [BR_Ping1D](INFO): startup: 0
2019-04-10T00:58:55.086Z,1554857935.086 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T00:58:55.098Z,1554857935.098 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T00:58:55.098Z,1554857935.098 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T00:58:55.098Z,1554857935.098 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T00:58:55.098Z,1554857935.098 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T00:58:55.099Z,1554857935.099 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T00:58:55.099Z,1554857935.099 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T00:58:55.099Z,1554857935.099 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T00:58:55.183Z,1554857935.183 [CBIT](CRITICAL): Environmental Failure. Press:14.797977 PSI. Humidity:37%. Temp:25 C. ABORTING MISSION
2019-04-10T00:58:55.477Z,1554857935.477 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:55.629Z,1554857935.629 [CBIT](INFO): Critical error at 20190410T005855
2019-04-10T00:58:55.862Z,1554857935.862 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T00:58:55.862Z,1554857935.862 [Aanderaa_O2] Communications Fault, FailCount= 1
2019-04-10T00:58:55.863Z,1554857935.863 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T00:58:55.881Z,1554857935.881 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:55.881Z,1554857935.881 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:55.881Z,1554857935.881 [BR_Ping1D](INFO): startup: 1
2019-04-10T00:58:55.882Z,1554857935.882 [BR_Ping1D](INFO): UART requesting status
2019-04-10T00:58:55.882Z,1554857935.882 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T00:58:55.890Z,1554857935.890 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T00:58:55.898Z,1554857935.898 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T00:58:55.913Z,1554857935.913 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T00:58:56.386Z,1554857936.386 [Aanderaa_O2](INFO): Powering down
2019-04-10T00:58:56.478Z,1554857936.478 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:56.478Z,1554857936.478 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:56.478Z,1554857936.478 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:56.478Z,1554857936.478 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:56.478Z,1554857936.478 [BR_Ping1D](INFO): elapsed 1.3919
2019-04-10T00:58:56.479Z,1554857936.479 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:56.479Z,1554857936.479 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:56.479Z,1554857936.479 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:56.479Z,1554857936.479 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:56.689Z,1554857936.689 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:56.689Z,1554857936.689 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:56.690Z,1554857936.690 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:56.690Z,1554857936.690 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:56.690Z,1554857936.690 [BR_Ping1D](INFO): elapsed 1.6035
2019-04-10T00:58:56.690Z,1554857936.690 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:56.690Z,1554857936.690 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:56.691Z,1554857936.691 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:56.691Z,1554857936.691 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:57.094Z,1554857937.094 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:57.094Z,1554857937.094 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:57.094Z,1554857937.094 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:57.094Z,1554857937.094 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:57.094Z,1554857937.094 [BR_Ping1D](INFO): elapsed 2.0080
2019-04-10T00:58:57.095Z,1554857937.095 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:57.095Z,1554857937.095 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:57.095Z,1554857937.095 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:57.095Z,1554857937.095 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:57.127Z,1554857937.127 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T00:58:57.127Z,1554857937.127 [Aanderaa_O2] No Fault, FailCount= 1
2019-04-10T00:58:57.498Z,1554857937.498 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:57.498Z,1554857937.498 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:57.498Z,1554857937.498 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:57.499Z,1554857937.499 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:57.499Z,1554857937.499 [BR_Ping1D](INFO): elapsed 2.4123
2019-04-10T00:58:57.499Z,1554857937.499 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:57.499Z,1554857937.499 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:57.499Z,1554857937.499 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:57.499Z,1554857937.499 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:57.914Z,1554857937.914 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:57.914Z,1554857937.914 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:57.914Z,1554857937.914 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:57.914Z,1554857937.914 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:57.915Z,1554857937.915 [BR_Ping1D](INFO): elapsed 2.8281
2019-04-10T00:58:57.915Z,1554857937.915 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:57.915Z,1554857937.915 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:57.915Z,1554857937.915 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:57.915Z,1554857937.915 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:58.062Z,1554857938.062 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T00:58:58.062Z,1554857938.062 [CTD_Seabird] Communications Fault, FailCount= 1
2019-04-10T00:58:58.062Z,1554857938.062 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T00:58:58.305Z,1554857938.305 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:58.306Z,1554857938.306 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:58.306Z,1554857938.306 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:58.306Z,1554857938.306 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:58.306Z,1554857938.306 [BR_Ping1D](INFO): elapsed 3.2198
2019-04-10T00:58:58.306Z,1554857938.306 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:58.307Z,1554857938.307 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:58.307Z,1554857938.307 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:58.307Z,1554857938.307 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:58.323Z,1554857938.323 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T00:58:58.470Z,1554857938.470 [CTD_Seabird](INFO): Powering down
2019-04-10T00:58:58.710Z,1554857938.710 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:58.710Z,1554857938.710 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:58.710Z,1554857938.710 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:58.710Z,1554857938.710 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:58.711Z,1554857938.711 [BR_Ping1D](INFO): elapsed 3.6242
2019-04-10T00:58:58.711Z,1554857938.711 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:58.711Z,1554857938.711 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:58.711Z,1554857938.711 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:58.711Z,1554857938.711 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:59.113Z,1554857939.113 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:59.114Z,1554857939.114 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:59.114Z,1554857939.114 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:59.114Z,1554857939.114 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:59.114Z,1554857939.114 [BR_Ping1D](INFO): elapsed 4.0278
2019-04-10T00:58:59.114Z,1554857939.114 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:59.115Z,1554857939.115 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:59.115Z,1554857939.115 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:59.115Z,1554857939.115 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:59.526Z,1554857939.526 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:59.526Z,1554857939.526 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:59.526Z,1554857939.526 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:59.526Z,1554857939.526 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:59.527Z,1554857939.527 [BR_Ping1D](INFO): elapsed 4.4401
2019-04-10T00:58:59.527Z,1554857939.527 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:59.527Z,1554857939.527 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:59.527Z,1554857939.527 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:59.527Z,1554857939.527 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:58:59.551Z,1554857939.551 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T00:58:59.551Z,1554857939.551 [CTD_Seabird] No Fault, FailCount= 1
2019-04-10T00:58:59.862Z,1554857939.862 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T00:58:59.864Z,1554857939.864 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T00:58:59.923Z,1554857939.923 [BR_Ping1D](INFO): Starting
2019-04-10T00:58:59.923Z,1554857939.923 [BR_Ping1D](INFO): readConfig
2019-04-10T00:58:59.923Z,1554857939.923 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:58:59.923Z,1554857939.923 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:58:59.924Z,1554857939.924 [BR_Ping1D](INFO): elapsed 4.8371
2019-04-10T00:58:59.924Z,1554857939.924 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:58:59.924Z,1554857939.924 [BR_Ping1D](INFO): No UART data
2019-04-10T00:58:59.924Z,1554857939.924 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:58:59.924Z,1554857939.924 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:00.326Z,1554857940.326 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:00.326Z,1554857940.326 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:00.326Z,1554857940.326 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:00.326Z,1554857940.326 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:00.326Z,1554857940.326 [BR_Ping1D](INFO): elapsed 5.2399
2019-04-10T00:59:00.327Z,1554857940.327 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:00.327Z,1554857940.327 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T00:59:00.327Z,1554857940.327 [BR_Ping1D] Data Fault, FailCount= 2
2019-04-10T00:59:00.327Z,1554857940.327 [BR_Ping1D](ERROR): Data Fault
2019-04-10T00:59:00.343Z,1554857940.343 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T00:59:00.729Z,1554857940.729 [BR_Ping1D](INFO): Stop
2019-04-10T00:59:00.729Z,1554857940.729 [BR_Ping1D](INFO): uninitialize
2019-04-10T00:59:00.729Z,1554857940.729 [BR_Ping1D](INFO): Powering down
2019-04-10T00:59:01.134Z,1554857941.134 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:01.537Z,1554857941.537 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:01.942Z,1554857941.942 [BR_Ping1D](INFO): Stopped
2019-04-10T00:59:01.959Z,1554857941.959 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T00:59:01.959Z,1554857941.959 [BR_Ping1D] No Fault, FailCount= 2
2019-04-10T00:59:02.346Z,1554857942.346 [BR_Ping1D](INFO): Start
2019-04-10T00:59:02.750Z,1554857942.750 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:03.154Z,1554857943.154 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:03.154Z,1554857943.154 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:03.154Z,1554857943.154 [BR_Ping1D](INFO): startup: 0
2019-04-10T00:59:03.155Z,1554857943.155 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T00:59:03.166Z,1554857943.166 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T00:59:03.166Z,1554857943.166 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T00:59:03.166Z,1554857943.166 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T00:59:03.166Z,1554857943.166 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T00:59:03.167Z,1554857943.167 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T00:59:03.167Z,1554857943.167 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T00:59:03.167Z,1554857943.167 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T00:59:03.557Z,1554857943.557 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:03.961Z,1554857943.961 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:03.961Z,1554857943.961 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:03.962Z,1554857943.962 [BR_Ping1D](INFO): startup: 1
2019-04-10T00:59:03.962Z,1554857943.962 [BR_Ping1D](INFO): UART requesting status
2019-04-10T00:59:03.962Z,1554857943.962 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T00:59:03.970Z,1554857943.970 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T00:59:03.978Z,1554857943.978 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T00:59:04.366Z,1554857944.366 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:04.366Z,1554857944.366 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:04.366Z,1554857944.366 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:04.366Z,1554857944.366 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:04.366Z,1554857944.366 [BR_Ping1D](INFO): elapsed 1.2116
2019-04-10T00:59:04.367Z,1554857944.367 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:04.367Z,1554857944.367 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:04.367Z,1554857944.367 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:04.367Z,1554857944.367 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:04.770Z,1554857944.770 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:04.770Z,1554857944.770 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:04.770Z,1554857944.770 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:04.771Z,1554857944.771 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:04.771Z,1554857944.771 [BR_Ping1D](INFO): elapsed 1.6160
2019-04-10T00:59:04.771Z,1554857944.771 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:04.771Z,1554857944.771 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:04.771Z,1554857944.771 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:04.771Z,1554857944.771 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:05.174Z,1554857945.174 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:05.174Z,1554857945.174 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:05.174Z,1554857945.174 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:05.174Z,1554857945.174 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:05.174Z,1554857945.174 [BR_Ping1D](INFO): elapsed 2.0197
2019-04-10T00:59:05.175Z,1554857945.175 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:05.175Z,1554857945.175 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:05.175Z,1554857945.175 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:05.175Z,1554857945.175 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:05.578Z,1554857945.578 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:05.578Z,1554857945.578 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:05.578Z,1554857945.578 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:05.578Z,1554857945.578 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:05.578Z,1554857945.578 [BR_Ping1D](INFO): elapsed 2.4236
2019-04-10T00:59:05.579Z,1554857945.579 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:05.579Z,1554857945.579 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:05.579Z,1554857945.579 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:05.579Z,1554857945.579 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:05.981Z,1554857945.981 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:05.982Z,1554857945.982 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:05.982Z,1554857945.982 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:05.982Z,1554857945.982 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:05.982Z,1554857945.982 [BR_Ping1D](INFO): elapsed 2.8275
2019-04-10T00:59:05.982Z,1554857945.982 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:05.983Z,1554857945.983 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:05.983Z,1554857945.983 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:05.983Z,1554857945.983 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:06.367Z,1554857946.367 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T00:59:06.367Z,1554857946.367 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 1
2019-04-10T00:59:06.367Z,1554857946.367 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T00:59:06.386Z,1554857946.386 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:06.386Z,1554857946.386 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:06.386Z,1554857946.386 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:06.386Z,1554857946.386 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:06.387Z,1554857946.387 [BR_Ping1D](INFO): elapsed 3.2319
2019-04-10T00:59:06.387Z,1554857946.387 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:06.387Z,1554857946.387 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:06.387Z,1554857946.387 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:06.387Z,1554857946.387 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:06.403Z,1554857946.403 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T00:59:06.771Z,1554857946.771 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T00:59:06.929Z,1554857946.929 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:06.929Z,1554857946.929 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:06.930Z,1554857946.930 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:06.930Z,1554857946.930 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:06.930Z,1554857946.930 [BR_Ping1D](INFO): elapsed 3.7754
2019-04-10T00:59:06.930Z,1554857946.930 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:06.930Z,1554857946.930 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:06.931Z,1554857946.931 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:06.931Z,1554857946.931 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:07.193Z,1554857947.193 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:07.194Z,1554857947.194 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:07.194Z,1554857947.194 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:07.194Z,1554857947.194 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:07.194Z,1554857947.194 [BR_Ping1D](INFO): elapsed 4.0396
2019-04-10T00:59:07.194Z,1554857947.194 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:07.195Z,1554857947.195 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:07.195Z,1554857947.195 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:07.195Z,1554857947.195 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:07.579Z,1554857947.579 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T00:59:07.579Z,1554857947.579 [Aanderaa_O2] Communications Fault, FailCount= 2
2019-04-10T00:59:07.579Z,1554857947.579 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T00:59:07.598Z,1554857947.598 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:07.598Z,1554857947.598 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:07.598Z,1554857947.598 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:07.598Z,1554857947.598 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:07.599Z,1554857947.599 [BR_Ping1D](INFO): elapsed 4.4440
2019-04-10T00:59:07.599Z,1554857947.599 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:07.599Z,1554857947.599 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:07.599Z,1554857947.599 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:07.599Z,1554857947.599 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:07.627Z,1554857947.627 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T00:59:07.627Z,1554857947.627 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T00:59:07.627Z,1554857947.627 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 1
2019-04-10T00:59:08.102Z,1554857948.102 [Aanderaa_O2](INFO): Powering down
2019-04-10T00:59:08.122Z,1554857948.122 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:08.122Z,1554857948.122 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:08.122Z,1554857948.122 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:08.122Z,1554857948.122 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:08.122Z,1554857948.122 [BR_Ping1D](INFO): elapsed 4.9677
2019-04-10T00:59:08.123Z,1554857948.123 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:08.123Z,1554857948.123 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:08.123Z,1554857948.123 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:08.123Z,1554857948.123 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:08.407Z,1554857948.407 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:08.407Z,1554857948.407 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:08.407Z,1554857948.407 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:08.407Z,1554857948.407 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:08.408Z,1554857948.408 [BR_Ping1D](INFO): elapsed 5.2528
2019-04-10T00:59:08.408Z,1554857948.408 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:08.408Z,1554857948.408 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T00:59:08.408Z,1554857948.408 [BR_Ping1D] Data Fault, FailCount= 3
2019-04-10T00:59:08.408Z,1554857948.408 [BR_Ping1D](ERROR): Data Fault
2019-04-10T00:59:08.423Z,1554857948.423 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T00:59:08.812Z,1554857948.812 [BR_Ping1D](INFO): Stop
2019-04-10T00:59:08.812Z,1554857948.812 [BR_Ping1D](INFO): uninitialize
2019-04-10T00:59:08.812Z,1554857948.812 [BR_Ping1D](INFO): Powering down
2019-04-10T00:59:08.904Z,1554857948.904 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T00:59:08.904Z,1554857948.904 [Aanderaa_O2] No Fault, FailCount= 2
2019-04-10T00:59:09.221Z,1554857949.221 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:09.629Z,1554857949.629 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:09.664Z,1554857949.664 [SBIT](IMPORTANT): Beginning Startup BIT
2019-04-10T00:59:09.668Z,1554857949.668 [CBIT](IMPORTANT): Beginning ground fault scan
2019-04-10T00:59:10.003Z,1554857950.003 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T00:59:10.003Z,1554857950.003 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T00:59:10.041Z,1554857950.041 [BR_Ping1D](INFO): Stopped
2019-04-10T00:59:10.144Z,1554857950.144 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T00:59:10.144Z,1554857950.144 [BR_Ping1D] No Fault, FailCount= 3
2019-04-10T00:59:10.422Z,1554857950.422 [BR_Ping1D](INFO): Start
2019-04-10T00:59:10.830Z,1554857950.830 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:11.233Z,1554857951.233 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:11.233Z,1554857951.233 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:11.234Z,1554857951.234 [BR_Ping1D](INFO): startup: 0
2019-04-10T00:59:11.234Z,1554857951.234 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T00:59:11.247Z,1554857951.247 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T00:59:11.247Z,1554857951.247 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T00:59:11.247Z,1554857951.247 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T00:59:11.247Z,1554857951.247 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T00:59:11.247Z,1554857951.247 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T00:59:11.247Z,1554857951.247 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T00:59:11.248Z,1554857951.248 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T00:59:11.641Z,1554857951.641 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:12.111Z,1554857952.111 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:12.111Z,1554857952.111 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:12.111Z,1554857952.111 [BR_Ping1D](INFO): startup: 1
2019-04-10T00:59:12.111Z,1554857952.111 [BR_Ping1D](INFO): UART requesting status
2019-04-10T00:59:12.111Z,1554857952.111 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T00:59:12.119Z,1554857952.119 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T00:59:12.126Z,1554857952.126 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T00:59:12.510Z,1554857952.510 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:12.510Z,1554857952.510 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:12.510Z,1554857952.510 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:12.510Z,1554857952.510 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:12.510Z,1554857952.510 [BR_Ping1D](INFO): elapsed 1.2764
2019-04-10T00:59:12.511Z,1554857952.511 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:12.511Z,1554857952.511 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:12.511Z,1554857952.511 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:12.511Z,1554857952.511 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:12.913Z,1554857952.913 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:12.913Z,1554857952.913 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:12.913Z,1554857952.913 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:12.914Z,1554857952.914 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:12.914Z,1554857952.914 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T00:59:12.914Z,1554857952.914 [CTD_Seabird] Communications Fault, FailCount= 2
2019-04-10T00:59:12.914Z,1554857952.914 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T00:59:12.915Z,1554857952.915 [BR_Ping1D](INFO): elapsed 1.6810
2019-04-10T00:59:12.915Z,1554857952.915 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:12.915Z,1554857952.915 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:12.915Z,1554857952.915 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:12.916Z,1554857952.916 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:13.063Z,1554857953.063 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T00:59:13.303Z,1554857953.303 [NAL9602](INFO): Powering up NAL9602
2019-04-10T00:59:13.319Z,1554857953.319 [CTD_Seabird](INFO): Powering down
2019-04-10T00:59:13.320Z,1554857953.320 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:13.320Z,1554857953.320 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:13.321Z,1554857953.321 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:13.321Z,1554857953.321 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:13.321Z,1554857953.321 [BR_Ping1D](INFO): elapsed 2.0869
2019-04-10T00:59:13.321Z,1554857953.321 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:13.321Z,1554857953.321 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:13.321Z,1554857953.321 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:13.322Z,1554857953.322 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:13.723Z,1554857953.723 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:13.724Z,1554857953.724 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:13.724Z,1554857953.724 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:13.724Z,1554857953.724 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:13.724Z,1554857953.724 [BR_Ping1D](INFO): elapsed 2.4903
2019-04-10T00:59:13.724Z,1554857953.724 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:13.725Z,1554857953.725 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:13.725Z,1554857953.725 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:13.725Z,1554857953.725 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:14.125Z,1554857954.125 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:14.126Z,1554857954.126 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:14.137Z,1554857954.137 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:14.138Z,1554857954.138 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:14.139Z,1554857954.139 [BR_Ping1D](INFO): elapsed 2.9046
2019-04-10T00:59:14.139Z,1554857954.139 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:14.139Z,1554857954.139 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:14.139Z,1554857954.139 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:14.139Z,1554857954.139 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:14.267Z,1554857954.267 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T00:59:14.267Z,1554857954.267 [CTD_Seabird] No Fault, FailCount= 2
2019-04-10T00:59:14.529Z,1554857954.529 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:14.529Z,1554857954.529 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:14.530Z,1554857954.530 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:14.530Z,1554857954.530 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:14.530Z,1554857954.530 [BR_Ping1D](INFO): elapsed 3.2962
2019-04-10T00:59:14.530Z,1554857954.530 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:14.531Z,1554857954.531 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:14.531Z,1554857954.531 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:14.531Z,1554857954.531 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:14.662Z,1554857954.662 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T00:59:14.664Z,1554857954.664 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T00:59:14.933Z,1554857954.933 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:14.934Z,1554857954.934 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:14.934Z,1554857954.934 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:14.934Z,1554857954.934 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:14.934Z,1554857954.934 [BR_Ping1D](INFO): elapsed 3.7003
2019-04-10T00:59:14.934Z,1554857954.934 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:14.935Z,1554857954.935 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:14.935Z,1554857954.935 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:14.935Z,1554857954.935 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:15.337Z,1554857955.337 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:15.337Z,1554857955.337 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:15.337Z,1554857955.337 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:15.338Z,1554857955.338 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:15.338Z,1554857955.338 [BR_Ping1D](INFO): elapsed 4.1039
2019-04-10T00:59:15.338Z,1554857955.338 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:15.338Z,1554857955.338 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:15.338Z,1554857955.338 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:15.339Z,1554857955.339 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:15.741Z,1554857955.741 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:15.741Z,1554857955.741 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:15.742Z,1554857955.742 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:15.742Z,1554857955.742 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:15.742Z,1554857955.742 [BR_Ping1D](INFO): elapsed 4.5082
2019-04-10T00:59:15.742Z,1554857955.742 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:15.743Z,1554857955.743 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:15.743Z,1554857955.743 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:15.743Z,1554857955.743 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:16.145Z,1554857956.145 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:16.145Z,1554857956.145 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:16.145Z,1554857956.145 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:16.146Z,1554857956.146 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:16.146Z,1554857956.146 [BR_Ping1D](INFO): elapsed 4.9119
2019-04-10T00:59:16.146Z,1554857956.146 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:16.146Z,1554857956.146 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:16.146Z,1554857956.146 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:16.147Z,1554857956.147 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:16.549Z,1554857956.549 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:16.550Z,1554857956.550 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:16.550Z,1554857956.550 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:16.550Z,1554857956.550 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:16.550Z,1554857956.550 [BR_Ping1D](INFO): elapsed 5.3164
2019-04-10T00:59:16.550Z,1554857956.550 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:16.551Z,1554857956.551 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T00:59:16.551Z,1554857956.551 [BR_Ping1D] Data Fault, FailCount= 4
2019-04-10T00:59:16.551Z,1554857956.551 [BR_Ping1D](ERROR): Data Fault
2019-04-10T00:59:16.611Z,1554857956.611 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T00:59:16.951Z,1554857956.951 [BR_Ping1D](INFO): Stop
2019-04-10T00:59:16.951Z,1554857956.951 [BR_Ping1D](INFO): uninitialize
2019-04-10T00:59:16.952Z,1554857956.952 [BR_Ping1D](INFO): Powering down
2019-04-10T00:59:17.361Z,1554857957.361 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:17.761Z,1554857957.761 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:18.166Z,1554857958.166 [BR_Ping1D](INFO): Stopped
2019-04-10T00:59:18.239Z,1554857958.239 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T00:59:18.239Z,1554857958.239 [BR_Ping1D] No Fault, FailCount= 4
2019-04-10T00:59:18.569Z,1554857958.569 [BR_Ping1D](INFO): Start
2019-04-10T00:59:18.973Z,1554857958.973 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:19.358Z,1554857959.358 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T00:59:19.358Z,1554857959.358 [Aanderaa_O2] Communications Fault, FailCount= 3
2019-04-10T00:59:19.358Z,1554857959.358 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T00:59:19.377Z,1554857959.377 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:19.377Z,1554857959.377 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:19.377Z,1554857959.377 [BR_Ping1D](INFO): startup: 0
2019-04-10T00:59:19.378Z,1554857959.378 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T00:59:19.390Z,1554857959.390 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T00:59:19.392Z,1554857959.392 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T00:59:19.392Z,1554857959.392 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T00:59:19.393Z,1554857959.393 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T00:59:19.393Z,1554857959.393 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T00:59:19.396Z,1554857959.396 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T00:59:19.396Z,1554857959.396 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T00:59:19.495Z,1554857959.495 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T00:59:19.496Z,1554857959.496 [CBIT](FAULT): Communications Fault in component: Aanderaa_O2
2019-04-10T00:59:19.882Z,1554857959.882 [Aanderaa_O2](INFO): Powering down
2019-04-10T00:59:19.902Z,1554857959.902 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:19.902Z,1554857959.902 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:19.903Z,1554857959.903 [BR_Ping1D](INFO): startup: 1
2019-04-10T00:59:19.903Z,1554857959.903 [BR_Ping1D](INFO): UART requesting status
2019-04-10T00:59:19.903Z,1554857959.903 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T00:59:19.910Z,1554857959.910 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T00:59:19.918Z,1554857959.918 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T00:59:20.185Z,1554857960.185 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:20.185Z,1554857960.185 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:20.185Z,1554857960.185 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:20.185Z,1554857960.185 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:20.186Z,1554857960.186 [BR_Ping1D](INFO): elapsed 0.8079
2019-04-10T00:59:20.186Z,1554857960.186 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:20.186Z,1554857960.186 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:20.186Z,1554857960.186 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:20.186Z,1554857960.186 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:20.590Z,1554857960.590 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:20.590Z,1554857960.590 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:20.590Z,1554857960.590 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:20.590Z,1554857960.590 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:20.590Z,1554857960.590 [BR_Ping1D](INFO): elapsed 1.2126
2019-04-10T00:59:20.591Z,1554857960.591 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:20.591Z,1554857960.591 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:20.591Z,1554857960.591 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:20.591Z,1554857960.591 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:20.655Z,1554857960.655 [CBIT](IMPORTANT): Ground fault detected
mA:
CHAN A0 (Batt): -0.006743
CHAN A1 (24V): -0.127990
CHAN A2 (12V): -0.004831
CHAN A3 (5V): -0.002016
CHAN B0 (3.3V): -0.000848
CHAN B1 (3.15aV): -0.001599
CHAN B2 (3.15bV): -0.001356
CHAN B3 (GND): 0.000306
OPEN: -0.001091
Full Scale Calc: 4.765 mA, -1.589 mA
2019-04-10T00:59:20.995Z,1554857960.995 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:20.996Z,1554857960.996 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:20.996Z,1554857960.996 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:20.996Z,1554857960.996 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:20.996Z,1554857960.996 [BR_Ping1D](INFO): elapsed 1.6185
2019-04-10T00:59:20.996Z,1554857960.996 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:20.997Z,1554857960.997 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:20.997Z,1554857960.997 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:20.997Z,1554857960.997 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:21.397Z,1554857961.397 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:21.398Z,1554857961.398 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:21.398Z,1554857961.398 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:21.398Z,1554857961.398 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:21.398Z,1554857961.398 [BR_Ping1D](INFO): elapsed 2.0207
2019-04-10T00:59:21.399Z,1554857961.399 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:21.399Z,1554857961.399 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:21.399Z,1554857961.399 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:21.399Z,1554857961.399 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:21.801Z,1554857961.801 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:21.801Z,1554857961.801 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:21.802Z,1554857961.802 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:21.802Z,1554857961.802 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:21.802Z,1554857961.802 [BR_Ping1D](INFO): elapsed 2.4243
2019-04-10T00:59:21.802Z,1554857961.802 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:21.802Z,1554857961.802 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:21.803Z,1554857961.803 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:21.803Z,1554857961.803 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:22.206Z,1554857962.206 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:22.206Z,1554857962.206 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:22.206Z,1554857962.206 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:22.206Z,1554857962.206 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:22.206Z,1554857962.206 [BR_Ping1D](INFO): elapsed 2.8288
2019-04-10T00:59:22.207Z,1554857962.207 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:22.207Z,1554857962.207 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:22.207Z,1554857962.207 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:22.207Z,1554857962.207 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:22.609Z,1554857962.609 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:22.609Z,1554857962.609 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:22.610Z,1554857962.610 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:22.610Z,1554857962.610 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:22.610Z,1554857962.610 [BR_Ping1D](INFO): elapsed 3.2323
2019-04-10T00:59:22.610Z,1554857962.610 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:22.610Z,1554857962.610 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:22.611Z,1554857962.611 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:22.611Z,1554857962.611 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:23.014Z,1554857963.014 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:23.014Z,1554857963.014 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:23.014Z,1554857963.014 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:23.014Z,1554857963.014 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:23.014Z,1554857963.014 [BR_Ping1D](INFO): elapsed 3.6367
2019-04-10T00:59:23.015Z,1554857963.015 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:23.015Z,1554857963.015 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:23.015Z,1554857963.015 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:23.015Z,1554857963.015 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:23.417Z,1554857963.417 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:23.417Z,1554857963.417 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:23.418Z,1554857963.418 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:23.418Z,1554857963.418 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:23.418Z,1554857963.418 [BR_Ping1D](INFO): elapsed 4.0404
2019-04-10T00:59:23.418Z,1554857963.418 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:23.418Z,1554857963.418 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:23.419Z,1554857963.419 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:23.419Z,1554857963.419 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:23.833Z,1554857963.833 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:23.833Z,1554857963.833 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:23.833Z,1554857963.833 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:23.833Z,1554857963.833 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:23.834Z,1554857963.834 [BR_Ping1D](INFO): elapsed 4.4559
2019-04-10T00:59:23.835Z,1554857963.835 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:23.835Z,1554857963.835 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:23.835Z,1554857963.835 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:23.835Z,1554857963.835 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:24.211Z,1554857964.211 [NAL9602](INFO): NAL9602 initialized
2019-04-10T00:59:24.232Z,1554857964.232 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:24.232Z,1554857964.232 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:24.232Z,1554857964.232 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:24.232Z,1554857964.232 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:24.233Z,1554857964.233 [BR_Ping1D](INFO): elapsed 4.8549
2019-04-10T00:59:24.233Z,1554857964.233 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:24.233Z,1554857964.233 [BR_Ping1D](INFO): No UART data
2019-04-10T00:59:24.233Z,1554857964.233 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T00:59:24.233Z,1554857964.233 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T00:59:24.655Z,1554857964.655 [BR_Ping1D](INFO): Starting
2019-04-10T00:59:24.655Z,1554857964.655 [BR_Ping1D](INFO): readConfig
2019-04-10T00:59:24.655Z,1554857964.655 [BR_Ping1D](INFO): startup: 2
2019-04-10T00:59:24.655Z,1554857964.655 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T00:59:24.655Z,1554857964.655 [BR_Ping1D](INFO): elapsed 5.2776
2019-04-10T00:59:24.656Z,1554857964.656 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T00:59:24.656Z,1554857964.656 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T00:59:24.656Z,1554857964.656 [BR_Ping1D] Data Fault, FailCount= 5
2019-04-10T00:59:24.656Z,1554857964.656 [BR_Ping1D](ERROR): Data Fault
2019-04-10T00:59:25.183Z,1554857965.183 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T00:59:25.183Z,1554857965.183 [CBIT](CRITICAL): Data Fault in component: BR_Ping1D
2019-04-10T00:59:25.206Z,1554857965.206 [NAL9602](DEBUG): Fix Requested
2019-04-10T00:59:25.221Z,1554857965.221 [BR_Ping1D](INFO): Stop
2019-04-10T00:59:25.221Z,1554857965.221 [BR_Ping1D](INFO): uninitialize
2019-04-10T00:59:25.221Z,1554857965.221 [BR_Ping1D](INFO): Powering down
2019-04-10T00:59:25.461Z,1554857965.461 [CBIT](INFO): Critical error at 20190410T005925
2019-04-10T00:59:25.625Z,1554857965.625 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:26.036Z,1554857966.036 [BR_Ping1D](INFO): Stopping
2019-04-10T00:59:26.429Z,1554857966.429 [BR_Ping1D](INFO): Stopped
2019-04-10T00:59:27.717Z,1554857967.717 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T00:59:27.717Z,1554857967.717 [CTD_Seabird] Communications Fault, FailCount= 3
2019-04-10T00:59:27.718Z,1554857967.718 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T00:59:27.743Z,1554857967.743 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T00:59:27.743Z,1554857967.743 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-04-10T00:59:28.122Z,1554857968.122 [CTD_Seabird](INFO): Powering down
2019-04-10T00:59:30.035Z,1554857970.035 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T00:59:30.035Z,1554857970.035 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 2
2019-04-10T00:59:30.035Z,1554857970.035 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T00:59:30.307Z,1554857970.307 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T00:59:30.439Z,1554857970.439 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T00:59:31.335Z,1554857971.335 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T00:59:31.335Z,1554857971.335 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 2
2019-04-10T00:59:33.671Z,1554857973.671 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T00:59:33.671Z,1554857973.671 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T00:59:53.946Z,1554857993.946 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T00:59:53.947Z,1554857993.947 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 3
2019-04-10T00:59:53.947Z,1554857993.947 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T00:59:54.175Z,1554857994.175 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T00:59:54.350Z,1554857994.350 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T00:59:55.287Z,1554857995.287 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T00:59:55.287Z,1554857995.287 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 3
2019-04-10T00:59:57.630Z,1554857997.630 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T00:59:57.631Z,1554857997.631 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:00:00.078Z,1554858000.078 [BPC1](ERROR): BPC1A: No match for serial number 03FE in BPC1A's battery stick inventory (sticks 1-32 in onboard configuration file).
2019-04-10T01:00:00.080Z,1554858000.080 [BPC1](ERROR): BPC1B: No match for serial number 0451 in BPC1B's battery stick inventory (sticks 32-63 in onboard configuration file).
2019-04-10T01:00:00.080Z,1554858000.080 [BPC1](FAULT): Failed to parse data from all battery packs.
2019-04-10T01:00:00.080Z,1554858000.080 [BPC1] Data Fault, FailCount= 1
2019-04-10T01:00:00.080Z,1554858000.080 [BPC1](ERROR): Data Fault
2019-04-10T01:00:00.096Z,1554858000.096 [CBIT](ERROR): Data Fault in component: BPC1
2019-04-10T01:00:02.916Z,1554858002.916 [SBIT](IMPORTANT): SBIT PASSED
2019-04-10T01:00:02.963Z,1554858002.963 [CommandLine](IMPORTANT): got command configSet list
2019-04-10T01:00:02.963Z,1554858002.963 [CommandLine](IMPORTANT): Listing configuration overrides from Data/persisted.cfg
2019-04-10T01:00:02.964Z,1554858002.964 [CommandLine](IMPORTANT): DropWeight.loadAtStartup=0 bool;

2019-04-10T01:00:02.964Z,1554858002.964 [CommandLine](IMPORTANT): Rowe_600LCM.loadAtStartup=0 bool;

2019-04-10T01:00:03.311Z,1554858003.311 [MissionManager](IMPORTANT): Started mission Startup
2019-04-10T01:00:03.311Z,1554858003.311 [Startup] Running Loop=1
2019-04-10T01:00:03.312Z,1554858003.312 [Startup](DEBUG): Aggregate::initialize Startup
2019-04-10T01:00:03.312Z,1554858003.312 [Startup:A.GoToSurface] Running Loop=1
2019-04-10T01:00:03.312Z,1554858003.312 [Startup:A.GoToSurface](DEBUG): Initialize GoToSurfaceComponent.
2019-04-10T01:00:03.312Z,1554858003.312 [Startup:A.GoToSurface](DEBUG): No depth rate setting specified. Using default value of nan m/s.
2019-04-10T01:00:03.313Z,1554858003.313 [Startup:A.GoToSurface](DEBUG): No pitch setting specified. Using default value of nan degrees.
2019-04-10T01:00:03.313Z,1554858003.313 [Startup:A.GoToSurface](DEBUG): No speed setting specified. Using default value of 1.000000 m/s.
2019-04-10T01:00:03.313Z,1554858003.313 [Startup:A.GoToSurface](DEBUG): No surface timeout specified. Using default value of 1000.000000 seconds.
2019-04-10T01:00:03.314Z,1554858003.314 [Startup:A.GoToSurface](INFO): Received pitch timeout configuration 60.000000 seconds.
2019-04-10T01:00:03.316Z,1554858003.316 [Startup:StartupSatComms] Running Loop=1
2019-04-10T01:00:03.316Z,1554858003.316 [Startup:StartupSatComms](DEBUG): Aggregate::initialize Startup:StartupSatComms
2019-04-10T01:00:03.316Z,1554858003.316 [Startup:StartupSatComms:A] Running Loop=1
2019-04-10T01:00:03.731Z,1554858003.731 [Startup:StartupSatComms:A](DEBUG): Initialize ReadDataComponent to sense latitude_fix
2019-04-10T01:00:17.830Z,1554858017.830 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:00:17.831Z,1554858017.831 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 4
2019-04-10T01:00:17.831Z,1554858017.831 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:00:17.880Z,1554858017.880 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:00:18.234Z,1554858018.234 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:00:19.080Z,1554858019.080 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:00:19.080Z,1554858019.080 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 4
2019-04-10T01:00:21.466Z,1554858021.466 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:00:21.467Z,1554858021.467 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:00:41.666Z,1554858041.666 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:00:41.667Z,1554858041.667 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 5
2019-04-10T01:00:41.667Z,1554858041.667 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:00:41.732Z,1554858041.732 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:00:42.071Z,1554858042.071 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:00:42.916Z,1554858042.916 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:00:42.916Z,1554858042.916 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 5
2019-04-10T01:00:45.302Z,1554858045.302 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:00:45.303Z,1554858045.303 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:00:45.348Z,1554858045.348 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:00:45.348Z,1554858045.348 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 1
2019-04-10T01:00:45.348Z,1554858045.348 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-04-10T01:00:45.349Z,1554858045.349 [DeadReckonUsingSpeedCalculator](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:00:45.349Z,1554858045.349 [DeadReckonUsingSpeedCalculator] Software Fault, FailCount= 1
2019-04-10T01:00:45.349Z,1554858045.349 [DeadReckonUsingSpeedCalculator](ERROR): Software Fault
2019-04-10T01:00:45.351Z,1554858045.351 [DeadReckonWithRespectToSeafloor](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:00:45.351Z,1554858045.351 [DeadReckonWithRespectToSeafloor] Software Fault, FailCount= 1
2019-04-10T01:00:45.351Z,1554858045.351 [DeadReckonWithRespectToSeafloor](ERROR): Software Fault
2019-04-10T01:00:45.362Z,1554858045.362 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-04-10T01:00:45.362Z,1554858045.362 [CBIT](ERROR): Software Fault in component: DeadReckonUsingSpeedCalculator
2019-04-10T01:00:45.362Z,1554858045.362 [CBIT](ERROR): Software Fault in component: DeadReckonWithRespectToSeafloor
2019-04-10T01:00:45.759Z,1554858045.759 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-04-10T01:00:45.759Z,1554858045.759 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 1
2019-04-10T01:00:45.760Z,1554858045.760 [CBIT](INFO): Clearing failed state for component DeadReckonUsingSpeedCalculator
2019-04-10T01:00:45.760Z,1554858045.760 [DeadReckonUsingSpeedCalculator] No Fault, FailCount= 1
2019-04-10T01:00:45.760Z,1554858045.760 [CBIT](INFO): Clearing failed state for component DeadReckonWithRespectToSeafloor
2019-04-10T01:00:45.760Z,1554858045.760 [DeadReckonWithRespectToSeafloor] No Fault, FailCount= 1
2019-04-10T01:00:46.149Z,1554858046.149 [DeadReckonUsingSpeedCalculator](DEBUG): Initializing DeadReckonUsingSpeedCalculator component.
2019-04-10T01:01:03.512Z,1554858063.512 [Startup:StartupSatComms:A](INFO): Timed out from 2019-04-10T01:00:03.3Z
2019-04-10T01:01:03.512Z,1554858063.512 [Startup:StartupSatComms:A] Stopped
2019-04-10T01:01:03.512Z,1554858063.512 [Startup:StartupSatComms:B] Running Loop=1
2019-04-10T01:01:03.915Z,1554858063.915 [Startup:StartupSatComms:B](DEBUG): Initialize ReadDataComponent to sense platform_communications
2019-04-10T01:01:05.504Z,1554858065.504 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:01:05.504Z,1554858065.504 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 6
2019-04-10T01:01:05.504Z,1554858065.504 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:01:05.541Z,1554858065.541 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:01:05.906Z,1554858065.906 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:01:06.768Z,1554858066.768 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:01:06.768Z,1554858066.768 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 6
2019-04-10T01:01:09.138Z,1554858069.138 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:01:09.139Z,1554858069.139 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:01:24.812Z,1554858084.812 [DataOverHttps](INFO): setting available, lastComms_.elapsed()=0.004909
2019-04-10T01:01:29.338Z,1554858089.338 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:01:29.339Z,1554858089.339 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 7
2019-04-10T01:01:29.339Z,1554858089.339 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:01:29.377Z,1554858089.377 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:01:29.742Z,1554858089.742 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:01:30.596Z,1554858090.596 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:01:30.596Z,1554858090.596 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 7
2019-04-10T01:01:32.975Z,1554858092.975 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:01:32.975Z,1554858092.975 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:01:36.750Z,1554858096.750 [DataOverHttps](INFO): Sending 25 bytes from file Logs/20190410T005205/Courier0004.lzma
2019-04-10T01:01:37.556Z,1554858097.556 [DataOverHttps](INFO): Moved sent file to Logs/20190410T005205/Courier0004.lzma.bak
2019-04-10T01:01:37.556Z,1554858097.556 [DataOverHttps](INFO): SBD MOMSN=10522513
2019-04-10T01:01:49.588Z,1554858109.588 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:01:49.589Z,1554858109.589 [Aanderaa_O2] No Fault, FailCount= 3
2019-04-10T01:01:51.334Z,1554858111.334 [DataOverHttps](INFO): Sending 314 bytes from file Logs/20190410T005537/Courier0000.lzma
2019-04-10T01:01:52.139Z,1554858112.139 [DataOverHttps](INFO): Moved sent file to Logs/20190410T005537/Courier0000.lzma.bak
2019-04-10T01:01:52.140Z,1554858112.140 [DataOverHttps](INFO): SBD MOMSN=10522515
2019-04-10T01:01:53.175Z,1554858113.175 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:01:53.175Z,1554858113.175 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 8
2019-04-10T01:01:53.175Z,1554858113.175 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:01:53.221Z,1554858113.221 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:01:53.221Z,1554858113.221 [CBIT](FAULT): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:01:53.579Z,1554858113.579 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:01:58.059Z,1554858118.059 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:01:58.059Z,1554858118.059 [CTD_Seabird] No Fault, FailCount= 3
2019-04-10T01:01:58.178Z,1554858118.178 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:01:58.180Z,1554858118.180 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:02:00.042Z,1554858120.042 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:02:00.042Z,1554858120.042 [Aanderaa_O2] Communications Fault, FailCount= 1
2019-04-10T01:02:00.042Z,1554858120.042 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:02:00.099Z,1554858120.099 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:02:00.566Z,1554858120.566 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:02:01.319Z,1554858121.319 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:02:01.319Z,1554858121.319 [Aanderaa_O2] No Fault, FailCount= 1
2019-04-10T01:02:03.709Z,1554858123.709 [Startup:StartupSatComms:B](INFO): Timed out from 2019-04-10T01:01:03.5Z
2019-04-10T01:02:03.709Z,1554858123.709 [Startup:StartupSatComms:B] Stopped
2019-04-10T01:02:03.709Z,1554858123.709 [Startup:StartupSatComms](INFO): Completed Startup:StartupSatComms
2019-04-10T01:02:03.710Z,1554858123.710 [Startup:StartupSatComms] Stopped
2019-04-10T01:02:03.710Z,1554858123.710 [Startup:StartupSatComms](DEBUG): Aggregate::uninitialize Startup:StartupSatComms
2019-04-10T01:02:03.711Z,1554858123.711 [Startup](INFO): Completed Startup
2019-04-10T01:02:03.711Z,1554858123.711 [MissionManager](INFO): Startup is completed.
2019-04-10T01:02:03.711Z,1554858123.711 [MissionManager](INFO): Uninitializing Mission Startup
2019-04-10T01:02:03.711Z,1554858123.711 [Startup] Stopped
2019-04-10T01:02:03.711Z,1554858123.711 [Startup](DEBUG): Aggregate::uninitialize Startup
2019-04-10T01:02:03.712Z,1554858123.712 [Startup:A.GoToSurface] Stopped
2019-04-10T01:02:03.712Z,1554858123.712 [Startup:A.GoToSurface](DEBUG): Uninitialize GoToSurfaceComponent.
2019-04-10T01:02:04.125Z,1554858124.125 [MissionManager](IMPORTANT): Started mission Default
2019-04-10T01:02:04.125Z,1554858124.125 [Default] Running Loop=1
2019-04-10T01:02:04.126Z,1554858124.126 [Default](DEBUG): Aggregate::initialize Default
2019-04-10T01:02:04.126Z,1554858124.126 [Default:B.GoToSurface] Running Loop=1
2019-04-10T01:02:04.126Z,1554858124.126 [Default:B.GoToSurface](DEBUG): Initialize GoToSurfaceComponent.
2019-04-10T01:02:04.126Z,1554858124.126 [Default:B.GoToSurface](DEBUG): No depth rate setting specified. Using default value of nan m/s.
2019-04-10T01:02:04.126Z,1554858124.126 [Default:B.GoToSurface](DEBUG): No pitch setting specified. Using default value of nan degrees.
2019-04-10T01:02:04.127Z,1554858124.127 [Default:B.GoToSurface](DEBUG): No speed setting specified. Using default value of 1.000000 m/s.
2019-04-10T01:02:04.127Z,1554858124.127 [Default:B.GoToSurface](DEBUG): No surface timeout specified. Using default value of 1000.000000 seconds.
2019-04-10T01:02:04.127Z,1554858124.127 [Default:B.GoToSurface](INFO): Received pitch timeout configuration 60.000000 seconds.
2019-04-10T01:02:04.128Z,1554858124.128 [Default:A.Wait] Running Loop=1
2019-04-10T01:02:04.128Z,1554858124.128 [Default:A.Wait](DEBUG): Initialize Wait Component.
2019-04-10T01:02:09.933Z,1554858129.933 [DataOverHttps](INFO): Sending 25 bytes from file Logs/20190410T005537/Courier0004.lzma
2019-04-10T01:02:10.739Z,1554858130.739 [DataOverHttps](INFO): Moved sent file to Logs/20190410T005537/Courier0004.lzma.bak
2019-04-10T01:02:10.740Z,1554858130.740 [DataOverHttps](INFO): SBD MOMSN=10522528
2019-04-10T01:02:11.230Z,1554858131.230 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:02:11.230Z,1554858131.230 [CTD_Seabird] Communications Fault, FailCount= 1
2019-04-10T01:02:11.230Z,1554858131.230 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:02:11.392Z,1554858131.392 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:02:11.634Z,1554858131.634 [CTD_Seabird](INFO): Powering down
2019-04-10T01:02:11.759Z,1554858131.759 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:02:11.759Z,1554858131.759 [Aanderaa_O2] Communications Fault, FailCount= 2
2019-04-10T01:02:11.759Z,1554858131.759 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:02:11.797Z,1554858131.797 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:02:12.282Z,1554858132.282 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:02:12.608Z,1554858132.608 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:02:12.608Z,1554858132.608 [CTD_Seabird] No Fault, FailCount= 1
2019-04-10T01:02:12.979Z,1554858132.979 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:02:12.981Z,1554858132.981 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:02:13.008Z,1554858133.008 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:02:13.008Z,1554858133.008 [Aanderaa_O2] No Fault, FailCount= 2
2019-04-10T01:02:17.440Z,1554858137.440 [Default:A.Wait](INFO): Done Waiting.
2019-04-10T01:02:17.440Z,1554858137.440 [Default:A.Wait] Stopped
2019-04-10T01:02:17.440Z,1554858137.440 [Default:A.Wait](DEBUG): Uninitialize Wait Component.
2019-04-10T01:02:17.854Z,1554858137.854 [Default:CheckIn] Running Loop=1
2019-04-10T01:02:17.854Z,1554858137.854 [Default:CheckIn](DEBUG): Aggregate::initialize Default:CheckIn
2019-04-10T01:02:17.855Z,1554858137.855 [Default:CheckIn:Read_GPS] Running Loop=1
2019-04-10T01:02:18.247Z,1554858138.247 [Default:CheckIn:Read_GPS](DEBUG): Initialize ReadDataComponent to sense time_fix
2019-04-10T01:02:23.474Z,1554858143.474 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:02:23.474Z,1554858143.474 [Aanderaa_O2] Communications Fault, FailCount= 3
2019-04-10T01:02:23.474Z,1554858143.474 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:02:23.513Z,1554858143.513 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:02:23.514Z,1554858143.514 [CBIT](FAULT): Communications Fault in component: Aanderaa_O2
2019-04-10T01:02:23.998Z,1554858143.998 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:02:26.030Z,1554858146.030 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:02:26.030Z,1554858146.030 [CTD_Seabird] Communications Fault, FailCount= 2
2019-04-10T01:02:26.030Z,1554858146.030 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:02:26.346Z,1554858146.346 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:02:26.434Z,1554858146.434 [CTD_Seabird](INFO): Powering down
2019-04-10T01:02:27.554Z,1554858147.554 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:02:27.554Z,1554858147.554 [CTD_Seabird] No Fault, FailCount= 2
2019-04-10T01:02:27.774Z,1554858147.774 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:02:27.776Z,1554858147.776 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:02:40.826Z,1554858160.826 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:02:40.826Z,1554858160.826 [CTD_Seabird] Communications Fault, FailCount= 3
2019-04-10T01:02:40.826Z,1554858160.826 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:02:40.898Z,1554858160.898 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:02:40.899Z,1554858160.899 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-04-10T01:02:41.230Z,1554858161.230 [CTD_Seabird](INFO): Powering down
2019-04-10T01:02:46.537Z,1554858166.537 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:02:46.537Z,1554858166.537 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 2
2019-04-10T01:02:46.537Z,1554858166.537 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-04-10T01:02:46.539Z,1554858166.539 [DeadReckonUsingSpeedCalculator](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:02:46.539Z,1554858166.539 [DeadReckonUsingSpeedCalculator] Software Fault, FailCount= 2
2019-04-10T01:02:46.539Z,1554858166.539 [DeadReckonUsingSpeedCalculator](ERROR): Software Fault
2019-04-10T01:02:46.540Z,1554858166.540 [DeadReckonWithRespectToSeafloor](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:02:46.540Z,1554858166.540 [DeadReckonWithRespectToSeafloor] Software Fault, FailCount= 2
2019-04-10T01:02:46.541Z,1554858166.541 [DeadReckonWithRespectToSeafloor](ERROR): Software Fault
2019-04-10T01:02:46.555Z,1554858166.555 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-04-10T01:02:46.556Z,1554858166.556 [CBIT](ERROR): Software Fault in component: DeadReckonUsingSpeedCalculator
2019-04-10T01:02:46.556Z,1554858166.556 [CBIT](ERROR): Software Fault in component: DeadReckonWithRespectToSeafloor
2019-04-10T01:02:46.963Z,1554858166.963 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-04-10T01:02:46.963Z,1554858166.963 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 2
2019-04-10T01:02:46.963Z,1554858166.963 [CBIT](INFO): Clearing failed state for component DeadReckonUsingSpeedCalculator
2019-04-10T01:02:46.963Z,1554858166.963 [DeadReckonUsingSpeedCalculator] No Fault, FailCount= 2
2019-04-10T01:02:46.964Z,1554858166.964 [CBIT](INFO): Clearing failed state for component DeadReckonWithRespectToSeafloor
2019-04-10T01:02:46.964Z,1554858166.964 [DeadReckonWithRespectToSeafloor] No Fault, FailCount= 2
2019-04-10T01:02:47.345Z,1554858167.345 [DeadReckonUsingSpeedCalculator](DEBUG): Initializing DeadReckonUsingSpeedCalculator component.
2019-04-10T01:04:24.714Z,1554858264.714 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T01:04:24.714Z,1554858264.714 [BR_Ping1D] No Fault, FailCount= 5
2019-04-10T01:04:25.094Z,1554858265.094 [BR_Ping1D](INFO): Start
2019-04-10T01:04:25.499Z,1554858265.499 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:25.916Z,1554858265.916 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:25.916Z,1554858265.916 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:25.916Z,1554858265.916 [BR_Ping1D](INFO): startup: 0
2019-04-10T01:04:25.916Z,1554858265.916 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T01:04:25.935Z,1554858265.935 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T01:04:25.936Z,1554858265.936 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T01:04:25.937Z,1554858265.937 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T01:04:25.937Z,1554858265.937 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T01:04:25.937Z,1554858265.937 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T01:04:25.938Z,1554858265.938 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T01:04:25.944Z,1554858265.944 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T01:04:26.320Z,1554858266.320 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:26.728Z,1554858266.728 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:26.729Z,1554858266.729 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:26.729Z,1554858266.729 [BR_Ping1D](INFO): startup: 1
2019-04-10T01:04:26.729Z,1554858266.729 [BR_Ping1D](INFO): UART requesting status
2019-04-10T01:04:26.729Z,1554858266.729 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T01:04:26.738Z,1554858266.738 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T01:04:26.746Z,1554858266.746 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T01:04:27.128Z,1554858267.128 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:27.128Z,1554858267.128 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:27.129Z,1554858267.129 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:27.129Z,1554858267.129 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:27.129Z,1554858267.129 [BR_Ping1D](INFO): elapsed 1.2125
2019-04-10T01:04:27.129Z,1554858267.129 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:27.129Z,1554858267.129 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:27.130Z,1554858267.130 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:27.130Z,1554858267.130 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:27.521Z,1554858267.521 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:27.522Z,1554858267.522 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:27.522Z,1554858267.522 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:27.522Z,1554858267.522 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:27.522Z,1554858267.522 [BR_Ping1D](INFO): elapsed 1.6058
2019-04-10T01:04:27.522Z,1554858267.522 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:27.523Z,1554858267.523 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:27.523Z,1554858267.523 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:27.523Z,1554858267.523 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:27.911Z,1554858267.911 [NAL9602](FAULT): MT Queue status failed to be acquired within timeout. Will not retry this session.
2019-04-10T01:04:27.926Z,1554858267.926 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:27.926Z,1554858267.926 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:27.927Z,1554858267.927 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:27.927Z,1554858267.927 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:27.927Z,1554858267.927 [BR_Ping1D](INFO): elapsed 2.0106
2019-04-10T01:04:27.927Z,1554858267.927 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:27.927Z,1554858267.927 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:27.928Z,1554858267.928 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:27.928Z,1554858267.928 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:28.332Z,1554858268.332 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:28.332Z,1554858268.332 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:28.332Z,1554858268.332 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:28.332Z,1554858268.332 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:28.333Z,1554858268.333 [BR_Ping1D](INFO): elapsed 2.4161
2019-04-10T01:04:28.333Z,1554858268.333 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:28.333Z,1554858268.333 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:28.333Z,1554858268.333 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:28.333Z,1554858268.333 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:28.730Z,1554858268.730 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:28.750Z,1554858268.750 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:28.751Z,1554858268.751 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:28.751Z,1554858268.751 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:28.751Z,1554858268.751 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:28.751Z,1554858268.751 [BR_Ping1D](INFO): elapsed 2.8346
2019-04-10T01:04:28.751Z,1554858268.751 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:28.752Z,1554858268.752 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:28.752Z,1554858268.752 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:28.752Z,1554858268.752 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:29.138Z,1554858269.138 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:29.138Z,1554858269.138 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:29.138Z,1554858269.138 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:29.138Z,1554858269.138 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:29.139Z,1554858269.139 [BR_Ping1D](INFO): elapsed 3.2222
2019-04-10T01:04:29.139Z,1554858269.139 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:29.139Z,1554858269.139 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:29.139Z,1554858269.139 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:29.139Z,1554858269.139 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:29.542Z,1554858269.542 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:29.542Z,1554858269.542 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:29.542Z,1554858269.542 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:29.542Z,1554858269.542 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:29.542Z,1554858269.542 [BR_Ping1D](INFO): elapsed 3.6259
2019-04-10T01:04:29.543Z,1554858269.543 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:29.543Z,1554858269.543 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:29.543Z,1554858269.543 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:29.543Z,1554858269.543 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:29.946Z,1554858269.946 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:29.946Z,1554858269.946 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:29.946Z,1554858269.946 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:29.946Z,1554858269.946 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:29.946Z,1554858269.946 [BR_Ping1D](INFO): elapsed 4.0299
2019-04-10T01:04:29.947Z,1554858269.947 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:29.947Z,1554858269.947 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:29.947Z,1554858269.947 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:29.947Z,1554858269.947 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:30.350Z,1554858270.350 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:30.350Z,1554858270.350 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:30.351Z,1554858270.351 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:30.351Z,1554858270.351 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:30.351Z,1554858270.351 [BR_Ping1D](INFO): elapsed 4.4344
2019-04-10T01:04:30.351Z,1554858270.351 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:30.351Z,1554858270.351 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:30.351Z,1554858270.351 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:30.352Z,1554858270.352 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:30.753Z,1554858270.753 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:30.753Z,1554858270.753 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:30.754Z,1554858270.754 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:30.754Z,1554858270.754 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:30.754Z,1554858270.754 [BR_Ping1D](INFO): elapsed 4.8375
2019-04-10T01:04:30.754Z,1554858270.754 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:30.754Z,1554858270.754 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:30.755Z,1554858270.755 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:30.755Z,1554858270.755 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:31.168Z,1554858271.168 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:31.168Z,1554858271.168 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:31.169Z,1554858271.169 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:31.169Z,1554858271.169 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:31.169Z,1554858271.169 [BR_Ping1D](INFO): elapsed 5.2526
2019-04-10T01:04:31.169Z,1554858271.169 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:31.169Z,1554858271.169 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T01:04:31.169Z,1554858271.169 [BR_Ping1D] Data Fault, FailCount= 1
2019-04-10T01:04:31.170Z,1554858271.170 [BR_Ping1D](ERROR): Data Fault
2019-04-10T01:04:31.185Z,1554858271.185 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T01:04:31.572Z,1554858271.572 [BR_Ping1D](INFO): Stop
2019-04-10T01:04:31.572Z,1554858271.572 [BR_Ping1D](INFO): uninitialize
2019-04-10T01:04:31.572Z,1554858271.572 [BR_Ping1D](INFO): Powering down
2019-04-10T01:04:31.973Z,1554858271.973 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:32.366Z,1554858272.366 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:32.775Z,1554858272.775 [BR_Ping1D](INFO): Stopped
2019-04-10T01:04:32.790Z,1554858272.790 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T01:04:32.791Z,1554858272.791 [BR_Ping1D] No Fault, FailCount= 1
2019-04-10T01:04:33.177Z,1554858273.177 [BR_Ping1D](INFO): Start
2019-04-10T01:04:33.582Z,1554858273.582 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:33.597Z,1554858273.597 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:33.996Z,1554858273.996 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:33.996Z,1554858273.996 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:33.997Z,1554858273.997 [BR_Ping1D](INFO): startup: 0
2019-04-10T01:04:33.997Z,1554858273.997 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T01:04:34.010Z,1554858274.010 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T01:04:34.011Z,1554858274.011 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T01:04:34.011Z,1554858274.011 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T01:04:34.011Z,1554858274.011 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T01:04:34.012Z,1554858274.012 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T01:04:34.012Z,1554858274.012 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T01:04:34.013Z,1554858274.013 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T01:04:34.400Z,1554858274.400 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:34.799Z,1554858274.799 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:34.799Z,1554858274.799 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:34.799Z,1554858274.799 [BR_Ping1D](INFO): startup: 1
2019-04-10T01:04:34.799Z,1554858274.799 [BR_Ping1D](INFO): UART requesting status
2019-04-10T01:04:34.799Z,1554858274.799 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T01:04:34.806Z,1554858274.806 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T01:04:34.814Z,1554858274.814 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T01:04:35.202Z,1554858275.202 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:35.202Z,1554858275.202 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:35.202Z,1554858275.202 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:35.202Z,1554858275.202 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:35.203Z,1554858275.203 [BR_Ping1D](INFO): elapsed 1.2058
2019-04-10T01:04:35.203Z,1554858275.203 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:35.203Z,1554858275.203 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:35.203Z,1554858275.203 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:35.203Z,1554858275.203 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:35.601Z,1554858275.601 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:35.601Z,1554858275.601 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:35.602Z,1554858275.602 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:35.602Z,1554858275.602 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:35.602Z,1554858275.602 [BR_Ping1D](INFO): elapsed 1.6053
2019-04-10T01:04:35.602Z,1554858275.602 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:35.602Z,1554858275.602 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:35.603Z,1554858275.603 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:35.603Z,1554858275.603 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:36.003Z,1554858276.003 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:36.003Z,1554858276.003 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:36.004Z,1554858276.004 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:36.004Z,1554858276.004 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:36.004Z,1554858276.004 [BR_Ping1D](INFO): elapsed 2.0071
2019-04-10T01:04:36.004Z,1554858276.004 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:36.004Z,1554858276.004 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:36.004Z,1554858276.004 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:36.005Z,1554858276.005 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:36.410Z,1554858276.410 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:36.411Z,1554858276.411 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:36.411Z,1554858276.411 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:36.411Z,1554858276.411 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:36.411Z,1554858276.411 [BR_Ping1D](INFO): elapsed 2.4144
2019-04-10T01:04:36.411Z,1554858276.411 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:36.412Z,1554858276.412 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:36.412Z,1554858276.412 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:36.412Z,1554858276.412 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:36.810Z,1554858276.810 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:36.824Z,1554858276.824 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:36.825Z,1554858276.825 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:36.825Z,1554858276.825 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:36.825Z,1554858276.825 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:36.825Z,1554858276.825 [BR_Ping1D](INFO): elapsed 2.8284
2019-04-10T01:04:36.825Z,1554858276.825 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:36.826Z,1554858276.826 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:36.826Z,1554858276.826 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:36.826Z,1554858276.826 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:37.232Z,1554858277.232 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:37.232Z,1554858277.232 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:37.233Z,1554858277.233 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:37.233Z,1554858277.233 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:37.233Z,1554858277.233 [BR_Ping1D](INFO): elapsed 3.2363
2019-04-10T01:04:37.233Z,1554858277.233 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:37.233Z,1554858277.233 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:37.234Z,1554858277.234 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:37.234Z,1554858277.234 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:37.633Z,1554858277.633 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:37.633Z,1554858277.633 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:37.633Z,1554858277.633 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:37.633Z,1554858277.633 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:37.633Z,1554858277.633 [BR_Ping1D](INFO): elapsed 3.6365
2019-04-10T01:04:37.634Z,1554858277.634 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:37.634Z,1554858277.634 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:37.635Z,1554858277.635 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:37.635Z,1554858277.635 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:38.026Z,1554858278.026 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:38.026Z,1554858278.026 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:38.026Z,1554858278.026 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:38.026Z,1554858278.026 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:38.026Z,1554858278.026 [BR_Ping1D](INFO): elapsed 4.0296
2019-04-10T01:04:38.027Z,1554858278.027 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:38.027Z,1554858278.027 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:38.027Z,1554858278.027 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:38.027Z,1554858278.027 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:38.432Z,1554858278.432 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:38.432Z,1554858278.432 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:38.432Z,1554858278.432 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:38.432Z,1554858278.432 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:38.433Z,1554858278.433 [BR_Ping1D](INFO): elapsed 4.4357
2019-04-10T01:04:38.433Z,1554858278.433 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:38.433Z,1554858278.433 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:38.433Z,1554858278.433 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:38.433Z,1554858278.433 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:38.834Z,1554858278.834 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:38.834Z,1554858278.834 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:38.835Z,1554858278.835 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:38.835Z,1554858278.835 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:38.835Z,1554858278.835 [BR_Ping1D](INFO): elapsed 4.8381
2019-04-10T01:04:38.835Z,1554858278.835 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:38.835Z,1554858278.835 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:38.835Z,1554858278.835 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:38.836Z,1554858278.836 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:39.238Z,1554858279.238 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:39.238Z,1554858279.238 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:39.238Z,1554858279.238 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:39.238Z,1554858279.238 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:39.238Z,1554858279.238 [BR_Ping1D](INFO): elapsed 5.2416
2019-04-10T01:04:39.239Z,1554858279.239 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:39.239Z,1554858279.239 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T01:04:39.239Z,1554858279.239 [BR_Ping1D] Data Fault, FailCount= 2
2019-04-10T01:04:39.239Z,1554858279.239 [BR_Ping1D](ERROR): Data Fault
2019-04-10T01:04:39.286Z,1554858279.286 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T01:04:39.638Z,1554858279.638 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:39.652Z,1554858279.652 [BR_Ping1D](INFO): Stop
2019-04-10T01:04:39.652Z,1554858279.652 [BR_Ping1D](INFO): uninitialize
2019-04-10T01:04:39.652Z,1554858279.652 [BR_Ping1D](INFO): Powering down
2019-04-10T01:04:40.056Z,1554858280.056 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:40.464Z,1554858280.464 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:40.851Z,1554858280.851 [BR_Ping1D](INFO): Stopped
2019-04-10T01:04:40.865Z,1554858280.865 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T01:04:40.865Z,1554858280.865 [BR_Ping1D] No Fault, FailCount= 2
2019-04-10T01:04:41.258Z,1554858281.258 [BR_Ping1D](INFO): Start
2019-04-10T01:04:41.665Z,1554858281.665 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:42.062Z,1554858282.062 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:42.062Z,1554858282.062 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:42.063Z,1554858282.063 [BR_Ping1D](INFO): startup: 0
2019-04-10T01:04:42.063Z,1554858282.063 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T01:04:42.076Z,1554858282.076 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T01:04:42.078Z,1554858282.078 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T01:04:42.090Z,1554858282.090 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T01:04:42.090Z,1554858282.090 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T01:04:42.090Z,1554858282.090 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T01:04:42.091Z,1554858282.091 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T01:04:42.092Z,1554858282.092 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T01:04:42.466Z,1554858282.466 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:42.481Z,1554858282.481 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:42.888Z,1554858282.888 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:42.888Z,1554858282.888 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:42.889Z,1554858282.889 [BR_Ping1D](INFO): startup: 1
2019-04-10T01:04:42.889Z,1554858282.889 [BR_Ping1D](INFO): UART requesting status
2019-04-10T01:04:42.889Z,1554858282.889 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T01:04:42.907Z,1554858282.907 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T01:04:42.914Z,1554858282.914 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T01:04:43.288Z,1554858283.288 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:43.289Z,1554858283.289 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:43.289Z,1554858283.289 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:43.289Z,1554858283.289 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:43.289Z,1554858283.289 [BR_Ping1D](INFO): elapsed 1.2264
2019-04-10T01:04:43.289Z,1554858283.289 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:43.290Z,1554858283.290 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:43.290Z,1554858283.290 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:43.290Z,1554858283.290 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:43.681Z,1554858283.681 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:43.681Z,1554858283.681 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:43.681Z,1554858283.681 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:43.682Z,1554858283.682 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:43.682Z,1554858283.682 [BR_Ping1D](INFO): elapsed 1.6189
2019-04-10T01:04:43.682Z,1554858283.682 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:43.682Z,1554858283.682 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:43.682Z,1554858283.682 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:43.683Z,1554858283.683 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:44.094Z,1554858284.094 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:44.094Z,1554858284.094 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:44.094Z,1554858284.094 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:44.094Z,1554858284.094 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:44.095Z,1554858284.095 [BR_Ping1D](INFO): elapsed 2.0318
2019-04-10T01:04:44.095Z,1554858284.095 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:44.095Z,1554858284.095 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:44.095Z,1554858284.095 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:44.095Z,1554858284.095 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:44.486Z,1554858284.486 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:44.500Z,1554858284.500 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:44.500Z,1554858284.500 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:44.501Z,1554858284.501 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:44.501Z,1554858284.501 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:44.501Z,1554858284.501 [BR_Ping1D](INFO): elapsed 2.4381
2019-04-10T01:04:44.501Z,1554858284.501 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:44.501Z,1554858284.501 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:44.501Z,1554858284.501 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:44.502Z,1554858284.502 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:44.909Z,1554858284.909 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:44.909Z,1554858284.909 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:44.909Z,1554858284.909 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:44.910Z,1554858284.910 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:44.910Z,1554858284.910 [BR_Ping1D](INFO): elapsed 2.8469
2019-04-10T01:04:44.910Z,1554858284.910 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:44.910Z,1554858284.910 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:44.910Z,1554858284.910 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:44.911Z,1554858284.911 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:45.311Z,1554858285.311 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:45.311Z,1554858285.311 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:45.311Z,1554858285.311 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:45.312Z,1554858285.312 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:45.312Z,1554858285.312 [BR_Ping1D](INFO): elapsed 3.2489
2019-04-10T01:04:45.312Z,1554858285.312 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:45.312Z,1554858285.312 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:45.312Z,1554858285.312 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:45.312Z,1554858285.312 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:45.702Z,1554858285.702 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:45.702Z,1554858285.702 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:45.702Z,1554858285.702 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:45.703Z,1554858285.703 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:45.703Z,1554858285.703 [BR_Ping1D](INFO): elapsed 3.6399
2019-04-10T01:04:45.703Z,1554858285.703 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:45.703Z,1554858285.703 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:45.703Z,1554858285.703 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:45.703Z,1554858285.703 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:46.106Z,1554858286.106 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:46.106Z,1554858286.106 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:46.107Z,1554858286.107 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:46.107Z,1554858286.107 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:46.107Z,1554858286.107 [BR_Ping1D](INFO): elapsed 4.0441
2019-04-10T01:04:46.107Z,1554858286.107 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:46.107Z,1554858286.107 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:46.107Z,1554858286.107 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:46.108Z,1554858286.108 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:46.516Z,1554858286.516 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:46.516Z,1554858286.516 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:46.516Z,1554858286.516 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:46.516Z,1554858286.516 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:46.517Z,1554858286.517 [BR_Ping1D](INFO): elapsed 4.4537
2019-04-10T01:04:46.517Z,1554858286.517 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:46.517Z,1554858286.517 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:46.517Z,1554858286.517 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:46.517Z,1554858286.517 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:46.915Z,1554858286.915 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:46.915Z,1554858286.915 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:46.915Z,1554858286.915 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:46.915Z,1554858286.915 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:46.915Z,1554858286.915 [BR_Ping1D](INFO): elapsed 4.8524
2019-04-10T01:04:46.915Z,1554858286.915 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:46.916Z,1554858286.916 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:46.916Z,1554858286.916 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:46.916Z,1554858286.916 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:47.318Z,1554858287.318 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:47.319Z,1554858287.319 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:47.319Z,1554858287.319 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:47.319Z,1554858287.319 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:47.319Z,1554858287.319 [BR_Ping1D](INFO): elapsed 5.2563
2019-04-10T01:04:47.319Z,1554858287.319 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:47.319Z,1554858287.319 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T01:04:47.320Z,1554858287.320 [BR_Ping1D] Data Fault, FailCount= 3
2019-04-10T01:04:47.320Z,1554858287.320 [BR_Ping1D](ERROR): Data Fault
2019-04-10T01:04:47.349Z,1554858287.349 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T01:04:47.718Z,1554858287.718 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:47.732Z,1554858287.732 [BR_Ping1D](INFO): Stop
2019-04-10T01:04:47.733Z,1554858287.733 [BR_Ping1D](INFO): uninitialize
2019-04-10T01:04:47.733Z,1554858287.733 [BR_Ping1D](INFO): Powering down
2019-04-10T01:04:47.815Z,1554858287.815 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:04:47.815Z,1554858287.815 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 3
2019-04-10T01:04:47.815Z,1554858287.815 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-04-10T01:04:47.817Z,1554858287.817 [DeadReckonUsingSpeedCalculator](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:04:47.817Z,1554858287.817 [DeadReckonUsingSpeedCalculator] Software Fault, FailCount= 3
2019-04-10T01:04:47.817Z,1554858287.817 [DeadReckonUsingSpeedCalculator](ERROR): Software Fault
2019-04-10T01:04:47.819Z,1554858287.819 [DeadReckonWithRespectToSeafloor](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:04:47.819Z,1554858287.819 [DeadReckonWithRespectToSeafloor] Software Fault, FailCount= 3
2019-04-10T01:04:47.819Z,1554858287.819 [DeadReckonWithRespectToSeafloor](ERROR): Software Fault
2019-04-10T01:04:47.841Z,1554858287.841 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-04-10T01:04:47.842Z,1554858287.842 [CBIT](ERROR): Software Fault in component: DeadReckonUsingSpeedCalculator
2019-04-10T01:04:47.842Z,1554858287.842 [CBIT](ERROR): Software Fault in component: DeadReckonWithRespectToSeafloor
2019-04-10T01:04:48.141Z,1554858288.141 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:48.155Z,1554858288.155 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-04-10T01:04:48.155Z,1554858288.155 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 3
2019-04-10T01:04:48.155Z,1554858288.155 [CBIT](INFO): Clearing failed state for component DeadReckonUsingSpeedCalculator
2019-04-10T01:04:48.155Z,1554858288.155 [DeadReckonUsingSpeedCalculator] No Fault, FailCount= 3
2019-04-10T01:04:48.156Z,1554858288.156 [CBIT](INFO): Clearing failed state for component DeadReckonWithRespectToSeafloor
2019-04-10T01:04:48.156Z,1554858288.156 [DeadReckonWithRespectToSeafloor] No Fault, FailCount= 3
2019-04-10T01:04:48.541Z,1554858288.541 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:48.545Z,1554858288.545 [DeadReckonUsingSpeedCalculator](DEBUG): Initializing DeadReckonUsingSpeedCalculator component.
2019-04-10T01:04:48.938Z,1554858288.938 [BR_Ping1D](INFO): Stopped
2019-04-10T01:04:48.968Z,1554858288.968 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T01:04:48.968Z,1554858288.968 [BR_Ping1D] No Fault, FailCount= 3
2019-04-10T01:04:49.337Z,1554858289.337 [BR_Ping1D](INFO): Start
2019-04-10T01:04:49.747Z,1554858289.747 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:50.149Z,1554858290.149 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:50.149Z,1554858290.149 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:50.150Z,1554858290.150 [BR_Ping1D](INFO): startup: 0
2019-04-10T01:04:50.150Z,1554858290.150 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T01:04:50.162Z,1554858290.162 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T01:04:50.163Z,1554858290.163 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T01:04:50.163Z,1554858290.163 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T01:04:50.163Z,1554858290.163 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T01:04:50.163Z,1554858290.163 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T01:04:50.164Z,1554858290.164 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T01:04:50.165Z,1554858290.165 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T01:04:50.546Z,1554858290.546 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:50.560Z,1554858290.560 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:50.964Z,1554858290.964 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:50.964Z,1554858290.964 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:50.964Z,1554858290.964 [BR_Ping1D](INFO): startup: 1
2019-04-10T01:04:50.965Z,1554858290.965 [BR_Ping1D](INFO): UART requesting status
2019-04-10T01:04:50.965Z,1554858290.965 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T01:04:50.974Z,1554858290.974 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T01:04:50.982Z,1554858290.982 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T01:04:51.368Z,1554858291.368 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:51.369Z,1554858291.369 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:51.369Z,1554858291.369 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:51.369Z,1554858291.369 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:51.369Z,1554858291.369 [BR_Ping1D](INFO): elapsed 1.2193
2019-04-10T01:04:51.369Z,1554858291.369 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:51.370Z,1554858291.370 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:51.370Z,1554858291.370 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:51.370Z,1554858291.370 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:51.764Z,1554858291.764 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:51.764Z,1554858291.764 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:51.765Z,1554858291.765 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:51.765Z,1554858291.765 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:51.765Z,1554858291.765 [BR_Ping1D](INFO): elapsed 1.6152
2019-04-10T01:04:51.765Z,1554858291.765 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:51.765Z,1554858291.765 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:51.766Z,1554858291.766 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:51.766Z,1554858291.766 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:52.169Z,1554858292.169 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:52.169Z,1554858292.169 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:52.169Z,1554858292.169 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:52.169Z,1554858292.169 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:52.170Z,1554858292.170 [BR_Ping1D](INFO): elapsed 2.0199
2019-04-10T01:04:52.170Z,1554858292.170 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:52.170Z,1554858292.170 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:52.170Z,1554858292.170 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:52.171Z,1554858292.171 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:52.569Z,1554858292.569 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:52.570Z,1554858292.570 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:52.570Z,1554858292.570 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:52.570Z,1554858292.570 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:52.570Z,1554858292.570 [BR_Ping1D](INFO): elapsed 2.4205
2019-04-10T01:04:52.570Z,1554858292.570 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:52.571Z,1554858292.571 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:52.571Z,1554858292.571 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:52.571Z,1554858292.571 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:52.971Z,1554858292.971 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:52.971Z,1554858292.971 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:52.972Z,1554858292.972 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:52.972Z,1554858292.972 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:52.972Z,1554858292.972 [BR_Ping1D](INFO): elapsed 2.8221
2019-04-10T01:04:52.972Z,1554858292.972 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:52.972Z,1554858292.972 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:52.972Z,1554858292.972 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:52.973Z,1554858292.973 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:53.378Z,1554858293.378 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:53.378Z,1554858293.378 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:53.378Z,1554858293.378 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:53.378Z,1554858293.378 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:53.378Z,1554858293.378 [BR_Ping1D](INFO): elapsed 3.2287
2019-04-10T01:04:53.379Z,1554858293.379 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:53.379Z,1554858293.379 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:53.379Z,1554858293.379 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:53.379Z,1554858293.379 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:53.778Z,1554858293.778 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:53.792Z,1554858293.792 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:53.793Z,1554858293.793 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:53.793Z,1554858293.793 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:53.793Z,1554858293.793 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:53.793Z,1554858293.793 [BR_Ping1D](INFO): elapsed 3.6434
2019-04-10T01:04:53.793Z,1554858293.793 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:53.794Z,1554858293.794 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:53.794Z,1554858293.794 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:53.794Z,1554858293.794 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:53.815Z,1554858293.815 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:04:53.816Z,1554858293.816 [Aanderaa_O2] No Fault, FailCount= 3
2019-04-10T01:04:54.200Z,1554858294.200 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:54.200Z,1554858294.200 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:54.201Z,1554858294.201 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:54.201Z,1554858294.201 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:54.201Z,1554858294.201 [BR_Ping1D](INFO): elapsed 4.0513
2019-04-10T01:04:54.201Z,1554858294.201 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:54.201Z,1554858294.201 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:54.202Z,1554858294.202 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:54.202Z,1554858294.202 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:54.613Z,1554858294.613 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:54.613Z,1554858294.613 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:54.613Z,1554858294.613 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:54.614Z,1554858294.614 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:54.614Z,1554858294.614 [BR_Ping1D](INFO): elapsed 4.4640
2019-04-10T01:04:54.614Z,1554858294.614 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:54.614Z,1554858294.614 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:54.614Z,1554858294.614 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:54.615Z,1554858294.615 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:54.993Z,1554858294.993 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:54.993Z,1554858294.993 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:54.994Z,1554858294.994 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:54.994Z,1554858294.994 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:54.994Z,1554858294.994 [BR_Ping1D](INFO): elapsed 4.8442
2019-04-10T01:04:54.994Z,1554858294.994 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:54.994Z,1554858294.994 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:54.995Z,1554858294.995 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:54.995Z,1554858294.995 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:55.402Z,1554858295.402 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:55.402Z,1554858295.402 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:55.402Z,1554858295.402 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:55.402Z,1554858295.402 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:55.402Z,1554858295.402 [BR_Ping1D](INFO): elapsed 5.2525
2019-04-10T01:04:55.403Z,1554858295.403 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:55.403Z,1554858295.403 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T01:04:55.403Z,1554858295.403 [BR_Ping1D] Data Fault, FailCount= 4
2019-04-10T01:04:55.403Z,1554858295.403 [BR_Ping1D](ERROR): Data Fault
2019-04-10T01:04:55.418Z,1554858295.418 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T01:04:55.801Z,1554858295.801 [BR_Ping1D](INFO): Stop
2019-04-10T01:04:55.801Z,1554858295.801 [BR_Ping1D](INFO): uninitialize
2019-04-10T01:04:55.801Z,1554858295.801 [BR_Ping1D](INFO): Powering down
2019-04-10T01:04:56.209Z,1554858296.209 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:56.606Z,1554858296.606 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:56.620Z,1554858296.620 [BR_Ping1D](INFO): Stopping
2019-04-10T01:04:57.024Z,1554858297.024 [BR_Ping1D](INFO): Stopped
2019-04-10T01:04:57.041Z,1554858297.041 [CBIT](INFO): Clearing failed state for component BR_Ping1D
2019-04-10T01:04:57.041Z,1554858297.041 [BR_Ping1D] No Fault, FailCount= 4
2019-04-10T01:04:57.428Z,1554858297.428 [BR_Ping1D](INFO): Start
2019-04-10T01:04:57.819Z,1554858297.819 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:58.223Z,1554858298.223 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:58.223Z,1554858298.223 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:58.223Z,1554858298.223 [BR_Ping1D](INFO): startup: 0
2019-04-10T01:04:58.223Z,1554858298.223 [BR_Ping1D](INFO): UART setting parameters ...
2019-04-10T01:04:58.234Z,1554858298.234 [BR_Ping1D](INFO): 42520200EC030000F4017A02
2019-04-10T01:04:58.235Z,1554858298.235 [BR_Ping1D](INFO): XXX autoMode1: 01
2019-04-10T01:04:58.235Z,1554858298.235 [BR_Ping1D](INFO): XXX autoMode2: 
2019-04-10T01:04:58.236Z,1554858298.236 [BR_Ping1D](INFO): XXX autoMode3: 1
2019-04-10T01:04:58.236Z,1554858298.236 [BR_Ping1D](INFO): 42520100EB030000840100
2019-04-10T01:04:58.236Z,1554858298.236 [BR_Ping1D](INFO): 42520400EA03000060E31600DE02
2019-04-10T01:04:58.237Z,1554858298.237 [BR_Ping1D](INFO): 42520100EE030000870116
2019-04-10T01:04:58.631Z,1554858298.631 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:59.037Z,1554858299.037 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:59.037Z,1554858299.037 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:59.037Z,1554858299.037 [BR_Ping1D](INFO): startup: 1
2019-04-10T01:04:59.038Z,1554858299.038 [BR_Ping1D](INFO): UART requesting status
2019-04-10T01:04:59.038Z,1554858299.038 [BR_Ping1D](INFO): 42520000BA0400005201
2019-04-10T01:04:59.046Z,1554858299.046 [BR_Ping1D](INFO): 42520000BF0400005701
2019-04-10T01:04:59.054Z,1554858299.054 [BR_Ping1D](INFO): 42520000B30400004B01
2019-04-10T01:04:59.438Z,1554858299.438 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:59.438Z,1554858299.438 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:59.439Z,1554858299.439 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:59.439Z,1554858299.439 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:59.439Z,1554858299.439 [BR_Ping1D](INFO): elapsed 1.2156
2019-04-10T01:04:59.439Z,1554858299.439 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:59.439Z,1554858299.439 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:59.439Z,1554858299.439 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:59.440Z,1554858299.440 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:04:59.842Z,1554858299.842 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:04:59.857Z,1554858299.857 [BR_Ping1D](INFO): Starting
2019-04-10T01:04:59.857Z,1554858299.857 [BR_Ping1D](INFO): readConfig
2019-04-10T01:04:59.857Z,1554858299.857 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:04:59.857Z,1554858299.857 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:04:59.857Z,1554858299.857 [BR_Ping1D](INFO): elapsed 1.6340
2019-04-10T01:04:59.857Z,1554858299.857 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:04:59.858Z,1554858299.858 [BR_Ping1D](INFO): No UART data
2019-04-10T01:04:59.858Z,1554858299.858 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:04:59.858Z,1554858299.858 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:00.256Z,1554858300.256 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:00.256Z,1554858300.256 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:00.257Z,1554858300.257 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:00.257Z,1554858300.257 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:00.257Z,1554858300.257 [BR_Ping1D](INFO): elapsed 2.0337
2019-04-10T01:05:00.257Z,1554858300.257 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:00.257Z,1554858300.257 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:00.258Z,1554858300.258 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:00.258Z,1554858300.258 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:00.665Z,1554858300.665 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:00.665Z,1554858300.665 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:00.665Z,1554858300.665 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:00.665Z,1554858300.665 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:00.666Z,1554858300.666 [BR_Ping1D](INFO): elapsed 2.4422
2019-04-10T01:05:00.666Z,1554858300.666 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:00.666Z,1554858300.666 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:00.666Z,1554858300.666 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:00.666Z,1554858300.666 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:01.062Z,1554858301.062 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:01.062Z,1554858301.062 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:01.063Z,1554858301.063 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:01.063Z,1554858301.063 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:01.063Z,1554858301.063 [BR_Ping1D](INFO): elapsed 2.8396
2019-04-10T01:05:01.063Z,1554858301.063 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:01.063Z,1554858301.063 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:01.063Z,1554858301.063 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:01.064Z,1554858301.064 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:01.459Z,1554858301.459 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:01.459Z,1554858301.459 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:01.460Z,1554858301.460 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:01.460Z,1554858301.460 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:01.460Z,1554858301.460 [BR_Ping1D](INFO): elapsed 3.2365
2019-04-10T01:05:01.460Z,1554858301.460 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:01.460Z,1554858301.460 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:01.460Z,1554858301.460 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:01.461Z,1554858301.461 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:01.865Z,1554858301.865 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:01.865Z,1554858301.865 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:01.865Z,1554858301.865 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:01.865Z,1554858301.865 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:01.865Z,1554858301.865 [BR_Ping1D](INFO): elapsed 3.6420
2019-04-10T01:05:01.866Z,1554858301.866 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:01.866Z,1554858301.866 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:01.866Z,1554858301.866 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:01.866Z,1554858301.866 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:02.269Z,1554858302.269 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:02.269Z,1554858302.269 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:02.269Z,1554858302.269 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:02.269Z,1554858302.269 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:02.270Z,1554858302.270 [BR_Ping1D](INFO): elapsed 4.0464
2019-04-10T01:05:02.270Z,1554858302.270 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:02.270Z,1554858302.270 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:02.270Z,1554858302.270 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:02.270Z,1554858302.270 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:02.666Z,1554858302.666 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:02.689Z,1554858302.689 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:02.689Z,1554858302.689 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:02.689Z,1554858302.689 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:02.689Z,1554858302.689 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:02.689Z,1554858302.689 [BR_Ping1D](INFO): elapsed 4.4660
2019-04-10T01:05:02.690Z,1554858302.690 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:02.690Z,1554858302.690 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:02.690Z,1554858302.690 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:02.690Z,1554858302.690 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:03.099Z,1554858303.099 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:03.099Z,1554858303.099 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:03.100Z,1554858303.100 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:03.100Z,1554858303.100 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:03.100Z,1554858303.100 [BR_Ping1D](INFO): elapsed 4.8767
2019-04-10T01:05:03.100Z,1554858303.100 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:03.100Z,1554858303.100 [BR_Ping1D](INFO): No UART data
2019-04-10T01:05:03.101Z,1554858303.101 [BR_Ping1D](INFO): received UART packets: 0
2019-04-10T01:05:03.101Z,1554858303.101 [BR_Ping1D](INFO): not all values verified yet
2019-04-10T01:05:03.491Z,1554858303.491 [BR_Ping1D](INFO): Starting
2019-04-10T01:05:03.491Z,1554858303.491 [BR_Ping1D](INFO): readConfig
2019-04-10T01:05:03.491Z,1554858303.491 [BR_Ping1D](INFO): startup: 2
2019-04-10T01:05:03.492Z,1554858303.492 [BR_Ping1D](INFO): UART waiting for response
2019-04-10T01:05:03.492Z,1554858303.492 [BR_Ping1D](INFO): elapsed 5.2684
2019-04-10T01:05:03.492Z,1554858303.492 [BR_Ping1D](INFO): timeout 5.0000
2019-04-10T01:05:03.492Z,1554858303.492 [BR_Ping1D](FAULT): Failed to set parameters in time during initialization.
2019-04-10T01:05:03.492Z,1554858303.492 [BR_Ping1D] Data Fault, FailCount= 5
2019-04-10T01:05:03.492Z,1554858303.492 [BR_Ping1D](ERROR): Data Fault
2019-04-10T01:05:03.547Z,1554858303.547 [CBIT](ERROR): Data Fault in component: BR_Ping1D
2019-04-10T01:05:03.547Z,1554858303.547 [CBIT](CRITICAL): Data Fault in component: BR_Ping1D
2019-04-10T01:05:03.883Z,1554858303.883 [BR_Ping1D](INFO): Stop
2019-04-10T01:05:03.883Z,1554858303.883 [BR_Ping1D](INFO): uninitialize
2019-04-10T01:05:03.883Z,1554858303.883 [BR_Ping1D](INFO): Powering down
2019-04-10T01:05:03.978Z,1554858303.978 [CBIT](INFO): Critical error at 20190410T010503
2019-04-10T01:05:04.267Z,1554858304.267 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:05:04.267Z,1554858304.267 [Aanderaa_O2] Communications Fault, FailCount= 1
2019-04-10T01:05:04.267Z,1554858304.267 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:05:04.287Z,1554858304.287 [BR_Ping1D](INFO): Stopping
2019-04-10T01:05:04.314Z,1554858304.314 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:05:04.790Z,1554858304.790 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:05:04.812Z,1554858304.812 [BR_Ping1D](INFO): Stopping
2019-04-10T01:05:05.096Z,1554858305.096 [BR_Ping1D](INFO): Stopped
2019-04-10T01:05:05.498Z,1554858305.498 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:05.531Z,1554858305.531 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:05:05.531Z,1554858305.531 [Aanderaa_O2] No Fault, FailCount= 1
2019-04-10T01:05:07.518Z,1554858307.518 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:09.542Z,1554858309.542 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:11.173Z,1554858311.173 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:05:11.173Z,1554858311.173 [CTD_Seabird] No Fault, FailCount= 3
2019-04-10T01:05:11.282Z,1554858311.282 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:05:11.284Z,1554858311.284 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:05:12.766Z,1554858312.766 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:15.594Z,1554858315.594 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:15.982Z,1554858315.982 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:05:15.982Z,1554858315.982 [Aanderaa_O2] Communications Fault, FailCount= 2
2019-04-10T01:05:15.982Z,1554858315.982 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:05:16.048Z,1554858316.048 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:05:16.506Z,1554858316.506 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:05:17.232Z,1554858317.232 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:05:17.232Z,1554858317.232 [Aanderaa_O2] No Fault, FailCount= 2
2019-04-10T01:05:18.826Z,1554858318.826 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:21.658Z,1554858321.658 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:24.334Z,1554858324.334 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:05:24.334Z,1554858324.334 [CTD_Seabird] Communications Fault, FailCount= 1
2019-04-10T01:05:24.334Z,1554858324.334 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:05:24.500Z,1554858324.500 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:05:24.738Z,1554858324.738 [CTD_Seabird](INFO): Powering down
2019-04-10T01:05:24.890Z,1554858324.890 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:25.722Z,1554858325.722 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:05:25.722Z,1554858325.722 [CTD_Seabird] No Fault, FailCount= 1
2019-04-10T01:05:26.086Z,1554858326.086 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:05:26.088Z,1554858326.088 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:05:27.698Z,1554858327.698 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:05:27.698Z,1554858327.698 [Aanderaa_O2] Communications Fault, FailCount= 3
2019-04-10T01:05:27.698Z,1554858327.698 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:05:27.718Z,1554858327.718 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:27.752Z,1554858327.752 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:05:27.752Z,1554858327.752 [CBIT](FAULT): Communications Fault in component: Aanderaa_O2
2019-04-10T01:05:28.222Z,1554858328.222 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:05:30.542Z,1554858330.542 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:32.566Z,1554858332.566 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:35.794Z,1554858335.794 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:38.626Z,1554858338.626 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:39.138Z,1554858339.138 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:05:39.138Z,1554858339.138 [CTD_Seabird] Communications Fault, FailCount= 2
2019-04-10T01:05:39.138Z,1554858339.138 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:05:39.461Z,1554858339.461 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:05:39.542Z,1554858339.542 [CTD_Seabird](INFO): Powering down
2019-04-10T01:05:40.676Z,1554858340.676 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:05:40.676Z,1554858340.676 [CTD_Seabird] No Fault, FailCount= 2
2019-04-10T01:05:40.886Z,1554858340.886 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:05:40.888Z,1554858340.888 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:05:41.858Z,1554858341.858 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:44.686Z,1554858344.686 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:47.918Z,1554858347.918 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:50.746Z,1554858350.746 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:53.574Z,1554858353.574 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:53.938Z,1554858353.938 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:05:53.938Z,1554858353.938 [CTD_Seabird] Communications Fault, FailCount= 3
2019-04-10T01:05:53.938Z,1554858353.938 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:05:54.028Z,1554858354.028 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:05:54.028Z,1554858354.028 [CBIT](FAULT): Communications Fault in component: CTD_Seabird
2019-04-10T01:05:54.342Z,1554858354.342 [CTD_Seabird](INFO): Powering down
2019-04-10T01:05:55.594Z,1554858355.594 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:05:57.615Z,1554858357.615 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:00.846Z,1554858360.846 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:03.674Z,1554858363.674 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:06.906Z,1554858366.906 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:09.734Z,1554858369.734 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:12.966Z,1554858372.966 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:15.794Z,1554858375.794 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:18.618Z,1554858378.618 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:20.638Z,1554858380.638 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:23.874Z,1554858383.874 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:26.702Z,1554858386.702 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:29.934Z,1554858389.934 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:32.762Z,1554858392.762 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:35.990Z,1554858395.990 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:38.826Z,1554858398.826 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:41.646Z,1554858401.646 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:43.666Z,1554858403.666 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:45.694Z,1554858405.694 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:48.922Z,1554858408.922 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:48.941Z,1554858408.941 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:06:48.941Z,1554858408.941 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 4
2019-04-10T01:06:48.941Z,1554858408.941 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-04-10T01:06:48.943Z,1554858408.943 [DeadReckonUsingSpeedCalculator](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:06:48.943Z,1554858408.943 [DeadReckonUsingSpeedCalculator] Software Fault, FailCount= 4
2019-04-10T01:06:48.943Z,1554858408.943 [DeadReckonUsingSpeedCalculator](ERROR): Software Fault
2019-04-10T01:06:48.944Z,1554858408.944 [DeadReckonWithRespectToSeafloor](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:06:48.944Z,1554858408.944 [DeadReckonWithRespectToSeafloor] Software Fault, FailCount= 4
2019-04-10T01:06:48.944Z,1554858408.944 [DeadReckonWithRespectToSeafloor](ERROR): Software Fault
2019-04-10T01:06:48.968Z,1554858408.968 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-04-10T01:06:48.968Z,1554858408.968 [CBIT](ERROR): Software Fault in component: DeadReckonUsingSpeedCalculator
2019-04-10T01:06:48.968Z,1554858408.968 [CBIT](ERROR): Software Fault in component: DeadReckonWithRespectToSeafloor
2019-04-10T01:06:49.355Z,1554858409.355 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-04-10T01:06:49.355Z,1554858409.355 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 4
2019-04-10T01:06:49.356Z,1554858409.356 [CBIT](INFO): Clearing failed state for component DeadReckonUsingSpeedCalculator
2019-04-10T01:06:49.356Z,1554858409.356 [DeadReckonUsingSpeedCalculator] No Fault, FailCount= 4
2019-04-10T01:06:49.356Z,1554858409.356 [CBIT](INFO): Clearing failed state for component DeadReckonWithRespectToSeafloor
2019-04-10T01:06:49.356Z,1554858409.356 [DeadReckonWithRespectToSeafloor] No Fault, FailCount= 4
2019-04-10T01:06:49.753Z,1554858409.753 [DeadReckonUsingSpeedCalculator](DEBUG): Initializing DeadReckonUsingSpeedCalculator component.
2019-04-10T01:06:51.750Z,1554858411.750 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:53.377Z,1554858413.377 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:06:53.377Z,1554858413.377 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 8
2019-04-10T01:06:53.750Z,1554858413.750 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:06:53.751Z,1554858413.751 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:06:54.978Z,1554858414.978 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:06:57.810Z,1554858417.810 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:01.042Z,1554858421.042 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:03.870Z,1554858423.870 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:06.698Z,1554858426.698 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:08.718Z,1554858428.718 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:11.950Z,1554858431.950 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:13.950Z,1554858433.950 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:07:13.951Z,1554858433.951 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 1
2019-04-10T01:07:13.951Z,1554858433.951 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:07:14.011Z,1554858434.011 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:07:14.354Z,1554858434.354 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:07:14.774Z,1554858434.774 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:15.216Z,1554858435.216 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:07:15.216Z,1554858435.216 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 1
2019-04-10T01:07:17.586Z,1554858437.586 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:07:17.587Z,1554858437.587 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:07:18.010Z,1554858438.010 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:18.030Z,1554858438.030 [Default:CheckIn:Read_GPS](INFO): Timed out from 2019-04-10T01:02:17.9Z
2019-04-10T01:07:18.030Z,1554858438.030 [Default:CheckIn:Read_GPS] Stopped
2019-04-10T01:07:18.030Z,1554858438.030 [Default:CheckIn:Read_Iridium] Running Loop=1
2019-04-10T01:07:18.436Z,1554858438.436 [Default:CheckIn:Read_Iridium](DEBUG): Initialize ReadDataComponent to sense platform_communications
2019-04-10T01:07:20.834Z,1554858440.834 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:24.066Z,1554858444.066 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:24.330Z,1554858444.330 [DataOverHttps](INFO): Sending 313 bytes from file Logs/20190410T005834/Courier0000.lzma
2019-04-10T01:07:25.135Z,1554858445.135 [DataOverHttps](INFO): Moved sent file to Logs/20190410T005834/Courier0000.lzma.bak
2019-04-10T01:07:25.136Z,1554858445.136 [DataOverHttps](INFO): SBD MOMSN=10522542
2019-04-10T01:07:26.902Z,1554858446.902 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:29.722Z,1554858449.722 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:31.746Z,1554858451.746 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:34.978Z,1554858454.978 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:37.786Z,1554858457.786 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:07:37.787Z,1554858457.787 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 2
2019-04-10T01:07:37.787Z,1554858457.787 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:07:37.806Z,1554858457.806 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:37.853Z,1554858457.853 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:07:38.190Z,1554858458.190 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:07:39.035Z,1554858459.035 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:07:39.035Z,1554858459.035 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 2
2019-04-10T01:07:41.036Z,1554858461.036 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:41.422Z,1554858461.422 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:07:41.423Z,1554858461.423 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:07:43.862Z,1554858463.862 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:44.985Z,1554858464.985 [DataOverHttps](INFO): Sending 71 bytes from file Logs/20190410T005834/Courier0004.lzma
2019-04-10T01:07:45.791Z,1554858465.791 [DataOverHttps](INFO): Moved sent file to Logs/20190410T005834/Courier0004.lzma.bak
2019-04-10T01:07:45.792Z,1554858465.792 [DataOverHttps](INFO): SBD MOMSN=10522555
2019-04-10T01:07:47.094Z,1554858467.094 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:49.926Z,1554858469.926 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:52.754Z,1554858472.754 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:54.774Z,1554858474.774 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:56.790Z,1554858476.790 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:07:58.028Z,1554858478.028 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:07:58.028Z,1554858478.028 [Aanderaa_O2] No Fault, FailCount= 3
2019-04-10T01:08:00.026Z,1554858480.026 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:01.623Z,1554858481.623 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:08:01.623Z,1554858481.623 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 3
2019-04-10T01:08:01.623Z,1554858481.623 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:08:01.680Z,1554858481.680 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:08:02.027Z,1554858482.027 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:08:02.850Z,1554858482.850 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:02.884Z,1554858482.884 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:08:02.884Z,1554858482.884 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 3
2019-04-10T01:08:05.259Z,1554858485.259 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:08:05.259Z,1554858485.259 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:08:06.082Z,1554858486.082 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:08.490Z,1554858488.490 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:08:08.490Z,1554858488.490 [Aanderaa_O2] Communications Fault, FailCount= 1
2019-04-10T01:08:08.491Z,1554858488.491 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:08:08.540Z,1554858488.540 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:08:09.014Z,1554858489.014 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:08:09.038Z,1554858489.038 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:09.750Z,1554858489.750 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:08:09.750Z,1554858489.750 [Aanderaa_O2] No Fault, FailCount= 1
2019-04-10T01:08:12.142Z,1554858492.142 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:13.636Z,1554858493.636 [DataOverHttps](INFO): Sending 1094 bytes from file Logs/20190410T003432/Express0001.lzma
2019-04-10T01:08:14.440Z,1554858494.440 [DataOverHttps](INFO): Moved sent file to Logs/20190410T003432/Express0001.lzma.bak
2019-04-10T01:08:14.440Z,1554858494.440 [DataOverHttps](INFO): SBD MOMSN=10522558
2019-04-10T01:08:14.970Z,1554858494.970 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:17.814Z,1554858497.814 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:19.822Z,1554858499.822 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:20.210Z,1554858500.210 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:08:20.210Z,1554858500.210 [Aanderaa_O2] Communications Fault, FailCount= 2
2019-04-10T01:08:20.210Z,1554858500.210 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:08:20.296Z,1554858500.296 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:08:20.734Z,1554858500.734 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:08:21.513Z,1554858501.513 [CBIT](INFO): Clearing failed state for component Aanderaa_O2
2019-04-10T01:08:21.513Z,1554858501.513 [Aanderaa_O2] No Fault, FailCount= 2
2019-04-10T01:08:23.054Z,1554858503.054 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:24.320Z,1554858504.320 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:08:24.320Z,1554858504.320 [CTD_Seabird] No Fault, FailCount= 3
2019-04-10T01:08:24.406Z,1554858504.406 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:08:24.408Z,1554858504.408 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:08:25.463Z,1554858505.463 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:08:25.463Z,1554858505.463 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 4
2019-04-10T01:08:25.463Z,1554858505.463 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:08:25.496Z,1554858505.496 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:08:25.867Z,1554858505.867 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:08:26.014Z,1554858506.014 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:26.722Z,1554858506.722 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:08:26.722Z,1554858506.722 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 4
2019-04-10T01:08:29.099Z,1554858509.099 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:08:29.099Z,1554858509.099 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:08:29.134Z,1554858509.134 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:31.926Z,1554858511.926 [Aanderaa_O2](FAULT): Failed to initialize within timeout.
2019-04-10T01:08:31.926Z,1554858511.926 [Aanderaa_O2] Communications Fault, FailCount= 3
2019-04-10T01:08:31.926Z,1554858511.926 [Aanderaa_O2](ERROR): Communications Fault
2019-04-10T01:08:31.946Z,1554858511.946 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:32.008Z,1554858512.008 [CBIT](ERROR): Communications Fault in component: Aanderaa_O2
2019-04-10T01:08:32.009Z,1554858512.009 [CBIT](FAULT): Communications Fault in component: Aanderaa_O2
2019-04-10T01:08:32.450Z,1554858512.450 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:08:35.174Z,1554858515.174 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:37.458Z,1554858517.458 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:08:37.458Z,1554858517.458 [CTD_Seabird] Communications Fault, FailCount= 1
2019-04-10T01:08:37.458Z,1554858517.458 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:08:37.624Z,1554858517.624 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:08:37.862Z,1554858517.862 [CTD_Seabird](INFO): Powering down
2019-04-10T01:08:38.006Z,1554858518.006 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:38.840Z,1554858518.840 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:08:38.840Z,1554858518.840 [CTD_Seabird] No Fault, FailCount= 1
2019-04-10T01:08:39.215Z,1554858519.215 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:08:39.216Z,1554858519.216 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:08:40.834Z,1554858520.834 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:41.454Z,1554858521.454 [DataOverHttps](INFO): Sending 141 bytes from file Logs/20190410T003432/Express0005.lzma
2019-04-10T01:08:42.259Z,1554858522.259 [DataOverHttps](INFO): Moved sent file to Logs/20190410T003432/Express0005.lzma.bak
2019-04-10T01:08:42.259Z,1554858522.259 [DataOverHttps](INFO): SBD MOMSN=10522595
2019-04-10T01:08:42.850Z,1554858522.850 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:44.870Z,1554858524.870 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:48.102Z,1554858528.102 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:49.298Z,1554858529.298 [AcousticModem_Benthos_ATM900](FAULT): failed to initialize, no bytes available on serial interface
2019-04-10T01:08:49.298Z,1554858529.298 [AcousticModem_Benthos_ATM900] Communications Fault, FailCount= 5
2019-04-10T01:08:49.299Z,1554858529.299 [AcousticModem_Benthos_ATM900](ERROR): Communications Fault
2019-04-10T01:08:49.331Z,1554858529.331 [CBIT](ERROR): Communications Fault in component: AcousticModem_Benthos_ATM900
2019-04-10T01:08:49.702Z,1554858529.702 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:08:49.849Z,1554858529.849 [DeadReckonUsingMultipleVelocitySources](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:08:49.849Z,1554858529.849 [DeadReckonUsingMultipleVelocitySources] Software Fault, FailCount= 5
2019-04-10T01:08:49.849Z,1554858529.849 [DeadReckonUsingMultipleVelocitySources](ERROR): Software Fault
2019-04-10T01:08:49.851Z,1554858529.851 [DeadReckonUsingSpeedCalculator](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:08:49.851Z,1554858529.851 [DeadReckonUsingSpeedCalculator] Software Fault, FailCount= 5
2019-04-10T01:08:49.851Z,1554858529.851 [DeadReckonUsingSpeedCalculator](ERROR): Software Fault
2019-04-10T01:08:49.853Z,1554858529.853 [DeadReckonWithRespectToSeafloor](FAULT): Unable to read the rotation from vehicle frame to navigation frame for more than 120 seconds.
2019-04-10T01:08:49.853Z,1554858529.853 [DeadReckonWithRespectToSeafloor] Software Fault, FailCount= 5
2019-04-10T01:08:49.853Z,1554858529.853 [DeadReckonWithRespectToSeafloor](ERROR): Software Fault
2019-04-10T01:08:49.863Z,1554858529.863 [CBIT](ERROR): Software Fault in component: DeadReckonUsingMultipleVelocitySources
2019-04-10T01:08:49.864Z,1554858529.864 [CBIT](ERROR): Software Fault in component: DeadReckonUsingSpeedCalculator
2019-04-10T01:08:49.864Z,1554858529.864 [CBIT](ERROR): Software Fault in component: DeadReckonWithRespectToSeafloor
2019-04-10T01:08:50.151Z,1554858530.151 [CBIT](INFO): Clearing failed state for component DeadReckonUsingMultipleVelocitySources
2019-04-10T01:08:50.151Z,1554858530.151 [DeadReckonUsingMultipleVelocitySources] No Fault, FailCount= 5
2019-04-10T01:08:50.151Z,1554858530.151 [CBIT](INFO): Clearing failed state for component DeadReckonUsingSpeedCalculator
2019-04-10T01:08:50.151Z,1554858530.151 [DeadReckonUsingSpeedCalculator] No Fault, FailCount= 5
2019-04-10T01:08:50.152Z,1554858530.152 [CBIT](INFO): Clearing failed state for component DeadReckonWithRespectToSeafloor
2019-04-10T01:08:50.152Z,1554858530.152 [DeadReckonWithRespectToSeafloor] No Fault, FailCount= 5
2019-04-10T01:08:50.537Z,1554858530.537 [DeadReckonUsingSpeedCalculator](DEBUG): Initializing DeadReckonUsingSpeedCalculator component.
2019-04-10T01:08:50.548Z,1554858530.548 [CBIT](INFO): Clearing failed state for component AcousticModem_Benthos_ATM900
2019-04-10T01:08:50.548Z,1554858530.548 [AcousticModem_Benthos_ATM900] No Fault, FailCount= 5
2019-04-10T01:08:50.934Z,1554858530.934 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:52.266Z,1554858532.266 [CTD_Seabird](FAULT): Failed to initialize within timeout.
2019-04-10T01:08:52.266Z,1554858532.266 [CTD_Seabird] Communications Fault, FailCount= 2
2019-04-10T01:08:52.267Z,1554858532.267 [CTD_Seabird](ERROR): Communications Fault
2019-04-10T01:08:52.564Z,1554858532.564 [CBIT](ERROR): Communications Fault in component: CTD_Seabird
2019-04-10T01:08:52.670Z,1554858532.670 [CTD_Seabird](INFO): Powering down
2019-04-10T01:08:52.934Z,1554858532.934 [AcousticModem_Benthos_ATM900](INFO): Powering up
2019-04-10T01:08:52.934Z,1554858532.934 [AcousticModem_Benthos_ATM900](DEBUG): Initializing AcousticModem_Benthos_ATM900.
2019-04-10T01:08:53.784Z,1554858533.784 [CBIT](INFO): Clearing failed state for component CTD_Seabird
2019-04-10T01:08:53.784Z,1554858533.784 [CTD_Seabird] No Fault, FailCount= 2
2019-04-10T01:08:54.010Z,1554858534.010 [CTD_Seabird](DEBUG): Initializing CTD_Seabird.
2019-04-10T01:08:54.019Z,1554858534.019 [CTD_Seabird](INFO): Opening uart, block timeout 10ths=20
2019-04-10T01:08:54.162Z,1554858534.162 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:54.515Z,1554858534.515 [CommandLine](IMPORTANT): got command restart application
2019-04-10T01:08:55.518Z,1554858535.518 [CommandLine ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:55.518Z,1554858535.518 [CommandLine ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:55.610Z,1554858535.610 [Supervisor](DEBUG): Uninitializing supervisor and starting cleanup.  Bye!
2019-04-10T01:08:55.610Z,1554858535.610 [CommandLine ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:55.611Z,1554858535.611 [CommandLine](INFO): Join timeout helper Thread ID is 983
2019-04-10T01:08:55.611Z,1554858535.611 [ComponentRegistry](INFO): Shutting down NavChartDb ThreadHandler
2019-04-10T01:08:55.611Z,1554858535.611 [NavChartDb ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:55.612Z,1554858535.612 [NavChartDb](INFO): Join timeout helper Thread ID is 984
2019-04-10T01:08:55.822Z,1554858535.822 [NavChartDb ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:55.822Z,1554858535.822 [NavChartDb ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:55.834Z,1554858535.834 [ComponentRegistry](INFO): Shutting down Radio_Surface ThreadHandler
2019-04-10T01:08:55.834Z,1554858535.834 [Radio_Surface ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:55.835Z,1554858535.835 [Radio_Surface](INFO): Join timeout helper Thread ID is 985
2019-04-10T01:08:55.946Z,1554858535.946 [Radio_Surface](INFO): Powering down
2019-04-10T01:08:55.947Z,1554858535.947 [Radio_Surface ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:55.947Z,1554858535.947 [Radio_Surface ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:55.948Z,1554858535.948 [ComponentRegistry](INFO): Shutting down DataOverHttps ThreadHandler
2019-04-10T01:08:55.948Z,1554858535.948 [DataOverHttps ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:55.948Z,1554858535.948 [DataOverHttps](INFO): Join timeout helper Thread ID is 986
2019-04-10T01:08:56.801Z,1554858536.801 [DataOverHttps ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:56.805Z,1554858536.805 [DataOverHttps ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:56.814Z,1554858536.814 [ComponentRegistry](INFO): Shutting down WetLabsBB2FL ThreadHandler
2019-04-10T01:08:56.814Z,1554858536.814 [WetLabsBB2FL ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:56.815Z,1554858536.815 [WetLabsBB2FL](INFO): Join timeout helper Thread ID is 987
2019-04-10T01:08:56.990Z,1554858536.990 [NAL9602](DEBUG): Fix Requested
2019-04-10T01:08:57.086Z,1554858537.086 [WetLabsBB2FL ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:57.087Z,1554858537.087 [WetLabsBB2FL](INFO): Powering down
2019-04-10T01:08:57.087Z,1554858537.087 [WetLabsBB2FL ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:57.095Z,1554858537.095 [ComponentRegistry](INFO): Shutting down CTD_Seabird ThreadHandler
2019-04-10T01:08:57.095Z,1554858537.095 [CTD_Seabird ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:57.095Z,1554858537.095 [CTD_Seabird](INFO): Join timeout helper Thread ID is 988
2019-04-10T01:08:58.034Z,1554858538.034 [CTD_Seabird](INFO): Powering down
2019-04-10T01:08:58.166Z,1554858538.166 [CTD_Seabird ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:58.166Z,1554858538.166 [CTD_Seabird](INFO): Powering down
2019-04-10T01:08:58.178Z,1554858538.178 [CTD_Seabird ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.187Z,1554858538.187 [ComponentRegistry](INFO): Shutting down logger ThreadHandler
2019-04-10T01:08:58.187Z,1554858538.187 [logger ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.187Z,1554858538.187 [logger](INFO): Join timeout helper Thread ID is 989
2019-04-10T01:08:58.206Z,1554858538.206 [logger ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:58.206Z,1554858538.206 [logger ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.211Z,1554858538.211 [ComponentRegistry](INFO): Shutting down CommandLine ThreadHandler
2019-04-10T01:08:58.211Z,1554858538.211 [CommandLine ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.211Z,1554858538.211 [ComponentRegistry](INFO): Shutting down controlThread ThreadHandler
2019-04-10T01:08:58.211Z,1554858538.211 [controlThread ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.212Z,1554858538.212 [controlThread](INFO): Join timeout helper Thread ID is 990
2019-04-10T01:08:58.224Z,1554858538.224 [controlThread ThreadHandler](INFO): Uninitializing protected caller thread.
2019-04-10T01:08:58.224Z,1554858538.224 [controlThread](DEBUG): Uninitializing ControlThread
2019-04-10T01:08:58.225Z,1554858538.225 [Aanderaa_O2](INFO): Powering down
2019-04-10T01:08:58.227Z,1554858538.227 [AcousticModem_Benthos_ATM900](INFO): Powering down
2019-04-10T01:08:58.347Z,1554858538.347 [NAL9602](INFO): Powering down
2019-04-10T01:08:58.348Z,1554858538.348 [BR_Ping1D](INFO): uninitialize
2019-04-10T01:08:58.348Z,1554858538.348 [BR_Ping1D](INFO): Powering down
2019-04-10T01:08:58.349Z,1554858538.349 [DepthRateCalculator](DEBUG): Uninitializing DepthRateCalculator.
2019-04-10T01:08:58.350Z,1554858538.350 [ElevatorOffsetCalculator](DEBUG): Uninitializing ElevatorOffsetCalculator.
2019-04-10T01:08:58.351Z,1554858538.351 [NavChart](DEBUG): Uninitialize NavChart Navigation.
2019-04-10T01:08:58.352Z,1554858538.352 [MissionManager](INFO): Uninitializing Mission Default
2019-04-10T01:08:58.352Z,1554858538.352 [Default] Stopped
2019-04-10T01:08:58.352Z,1554858538.352 [Default](DEBUG): Aggregate::uninitialize Default
2019-04-10T01:08:58.352Z,1554858538.352 [Default:B.GoToSurface] Stopped
2019-04-10T01:08:58.352Z,1554858538.352 [Default:B.GoToSurface](DEBUG): Uninitialize GoToSurfaceComponent.
2019-04-10T01:08:58.352Z,1554858538.352 [Default:CheckIn] Stopped
2019-04-10T01:08:58.352Z,1554858538.352 [Default:CheckIn](DEBUG): Aggregate::uninitialize Default:CheckIn
2019-04-10T01:08:58.352Z,1554858538.352 [Default:CheckIn:Read_Iridium] Stopped
2019-04-10T01:08:58.355Z,1554858538.355 [VerticalControl](DEBUG): Uninitialize VerticalControlComponent.
2019-04-10T01:08:58.355Z,1554858538.355 [HorizontalControl](DEBUG): Uninitialize HorizontalControlComponent.
2019-04-10T01:08:58.355Z,1554858538.355 [SpeedControl](DEBUG): Uninitialize SpeedControlComponent.
2019-04-10T01:08:58.356Z,1554858538.356 [LoopControl](DEBUG): Uninitialize LoopControlComponent.
2019-04-10T01:08:58.356Z,1554858538.356 [BuoyancyServo](DEBUG): Uninitialize Buoyancy Servo.
2019-04-10T01:08:58.356Z,1554858538.356 [BuoyancyServo](INFO): Powering down
2019-04-10T01:08:58.370Z,1554858538.370 [ElevatorServo](DEBUG): Uninitialize Elevator Servo.
2019-04-10T01:08:58.370Z,1554858538.370 [ElevatorServo](INFO): Powering down
2019-04-10T01:08:58.371Z,1554858538.371 [MassServo](DEBUG): Uninitialize Mass Servo.
2019-04-10T01:08:58.371Z,1554858538.371 [MassServo](INFO): Powering down
2019-04-10T01:08:58.372Z,1554858538.372 [RudderServo](DEBUG): Uninitialize Rudder Servo.
2019-04-10T01:08:58.372Z,1554858538.372 [RudderServo](INFO): Powering down
2019-04-10T01:08:58.373Z,1554858538.373 [ThrusterServo](DEBUG): Uninitialize Thruster Servo.
2019-04-10T01:08:58.373Z,1554858538.373 [ThrusterServo](INFO): Powering down
2019-04-10T01:08:58.374Z,1554858538.374 [SBIT](DEBUG): Uninitialize SBIT Component.
2019-04-10T01:08:58.374Z,1554858538.374 [IBIT](DEBUG): Uninitialize IBIT Component.
2019-04-10T01:08:58.374Z,1554858538.374 [CBIT](DEBUG): Uninitialize CBIT Component.
2019-04-10T01:08:58.374Z,1554858538.374 [CBIT](DEBUG): Powering off loads.
2019-04-10T01:08:58.386Z,1554858538.386 [CBIT](DEBUG): Disabling WDT.
2019-04-10T01:08:58.398Z,1554858538.398 [CBIT](DEBUG): Opening all GF detection circuits.
2019-04-10T01:08:58.399Z,1554858538.399 [controlThread ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.429Z,1554858538.429 [WetLabsBB2FL ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.434Z,1554858538.434 [CTD_Seabird ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.502Z,1554858538.502 [Radio_Surface ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.507Z,1554858538.507 [DataOverHttps ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.558Z,1554858538.558 [NavChartDb ThreadHandler](INFO): Thread cancelled.
2019-04-10T01:08:58.615Z,1554858538.615 [logger ThreadHandler](INFO): Thread cancelled.