Vocabulary
Argo configuration parameter names
| URI | http://vocab.nerc.ac.uk/collection/R18/current/ |
|---|---|
| Description | List of float configuration settings selected by the float Principal Investigator (PI). Configuration parameters may or may not be reported by the float, and do not constitute float measurements. Configuration parameters selected for a float are stored in the float 'meta.nc' file, under CONFIG_PARAMETER_NAME. Each configuration parameter name has an associated value, stored in CONFIG_PARAMETER_VALUE. Argo netCDF variable CONFIG_PARAMETER_NAME is populated by R18 prefLabel. |
| Creator | Argo Data Management Team |
| Modified | 2023-05-03 |
| Version Info | 1 |
| Identifier | R18 |
| Register Manager | British Oceanographic Data Centre |
| Register Owner | Argo Data Management Team |
Alternate Formats
Other formats for this page:
RDF/XML Turtle JSON-LDAlternate Profiles
Other views of this page:
Alternate Profiles ?Different Media Types (HTML, text, RDF, JSON etc.) and different information model views, profiles, are available for this resource.
Members
| ID ↑ | Preferred Label ↑ | Definition ↑ | Date ↑ |
|---|---|---|---|
| CC00001 | CONFIG_<PARAM>InverseGain_COUNT | <PARAM> = PRES, PSAL or TEMP. Inverse of the gain used to pack the P, T and S data, changeable via 2-way communications. | 2023-05-02 |
| CC00002 | CONFIG_<PARAM>Offset_COUNT | <PARAM> = PRES, PSAL or TEMP. Offset used to pack the P, T and S data, changeable via 2-way communications. | 2023-05-02 |
| CB00089 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>NumberOfSamples_NUMBER | Number of samples for the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00076 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>NumberOfSubSampling_NUMBER | Number of subsamplings of the data sampled in the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00074 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>PowerAcquisitionMode_NUMBER | Power acquisition mode for the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00075 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>RawDataAcquisition_NUMBER | Number of additional raw data sampled in the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00073 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>SamplingPeriod_dbar | Sampling period for the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00004 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>SamplingPeriod_seconds | Sampling period of the <short_sensor_name> during <cycle_phase_name> in the depth zone #<N> (in minutes). | 2023-05-02 |
| CB00071 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>StartPres_dbar | Start pressure to define the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00072 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>StopPres_dbar | Stop pressure to define the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00077 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>SubSampling<SubS>DataProcessingMode_NUMBER | Data processing mode for the subsampling #<SubS> of the data sampled in the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00078 | CONFIG_<short_sensor_name><cycle_phase_name>DepthZone<N>SubSampling<SubS>DataProcessingRate_NUMBER | Data processing rate for the subsampling #<SubS> of the data sampled in the depth zone #<N> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00070 | CONFIG_<short_sensor_name><cycle_phase_name>NumberOfDepthZone_NUMBER | Number of depth zones defined for the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00079 | CONFIG_<short_sensor_name><cycle_phase_name>NumberOfSamplingScheme_NUMBER | Number of sampling schemes defined for the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00085 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>NumberOfSubSampling_NUMBER | Number of subsamplings of the data sampled within the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00083 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>PowerAcquisitionMode_NUMBER | Power acquisition mode for the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00084 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>RawDataAcquisition_NUMBER | Number of additional raw data sampled within the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00082 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>SamplingPeriod_seconds | Sampling period of the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00080 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>StartTime_seconds | Start time to define the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00081 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>StopTime_seconds | Stop time to define the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00086 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>SubSampling<SubS>DataProcessingMode_NUMBER | Data processing mode for the subsampling #<SubS> of the data sampled within the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00087 | CONFIG_<short_sensor_name><cycle_phase_name>SamplingScheme<S>SubSampling<SubS>DataProcessingRate_NUMBER | Data processing rate for the subsampling #<SubS> of the data sampled within the sampling scheme #<S> of the <short_sensor_name> sensor while sampling during the <cycle_phase_name> phase of the cycle. | 2023-05-02 |
| CB00060 | CONFIG_<short_sensor_name><param>FluorescenceEmissionBandwidth_nm | Bandwidth of <short_sensor_name> for emission of <param> fluorescence measurements (in nanometer) | 2023-05-02 |
| CB00058 | CONFIG_<short_sensor_name><param>FluorescenceEmissionWavelength_nm | Wavelength of <short_sensor_name> for emission of <param> fluorescence measurements (in nanometer) | 2023-05-02 |
| CB00059 | CONFIG_<short_sensor_name><param>FluorescenceExcitationBandwidth_nm | Bandwidth of <short_sensor_name> for excitation of <param> fluorescence measurements (in nanometer) | 2023-05-02 |
| CB00057 | CONFIG_<short_sensor_name><param>FluorescenceExcitationWavelength_nm | Wavelength of <short_sensor_name> for excitation of <param> fluorescence measurements (in nanometer) | 2023-05-02 |
| CB00007 | CONFIG_<short_sensor_name>AscentSamplingPeriod_seconds | Sampling period of the <short_sensor_name> during the ascending profile (in seconds). | 2023-05-02 |
| CB00062 | CONFIG_<short_sensor_name>BetaAngle_angularDeg | Angle of Beta measurements (in degrees) | 2023-05-02 |
| CB00050 | CONFIG_<short_sensor_name>BetaBandwidth<I>_nm | Bandwidth of <short_sensor_name> Beta #<I> measurements (in nanometer). | 2023-05-02 |
| CB00049 | CONFIG_<short_sensor_name>BetaWavelength<I>_nm | Wavelength of <short_sensor_name> Beta #<I> measurements (in nanometer). | 2023-05-02 |
| CB00094 | CONFIG_<short_sensor_name>CpAscentPhaseDepthZone<N>SampleRate_hertz | Sample rate for the ascent depth zone #<N> of the <short_sensor_name> sensor used in continuous profiling mode. | 2023-05-02 |
| CB00095 | CONFIG_<short_sensor_name>CpAscentPhaseDepthZone<N>SamplingPeriod_seconds | Sampling period for the ascent depth zone #<N> of the <short_sensor_name> sensor used in continuous profiling mode. | 2023-05-02 |
| CB00093 | CONFIG_<short_sensor_name>CpAscentPhaseDepthZone<N>SlicesThickness_dbar | SlicesThickness of the ascent depth zone #<N> of the <short_sensor_name> sensor used in continuous profiling mode. | 2023-05-02 |
| CB00091 | CONFIG_<short_sensor_name>CpAscentPhaseDepthZone<N>StartPres_dbar | Start pressure to define the ascent depth zone #<N> of the <short_sensor_name> sensor used in continuous profiling mode. | 2023-05-02 |
| CB00092 | CONFIG_<short_sensor_name>CpAscentPhaseDepthZone<N>StopPres_dbar | Stop pressure to define the ascent depth zone #<N> of the <short_sensor_name> sensor used in continuous profiling mode. | 2023-05-02 |
| CB00090 | CONFIG_<short_sensor_name>CpAscentPhaseNumberOfDepthZone_NUMBER | Number of ascent depth zones defined for the <short_sensor_name> sensor used in continuous profiling mode. | 2023-05-02 |
| CB00009 | CONFIG_<short_sensor_name>DepthZone<N>DataProcessingMode_NUMBER | Data processing output of the <short_sensor_name> in the depth zone #<N> (0 : raw, 1 : average, 7 : average/median/standard deviation). | 2023-05-02 |
| CB00069 | CONFIG_<short_sensor_name>DepthZone<N>DataSynchronizationMode_NUMBER | Data of the <short_sensor_name> can be reported as they have been sampled or synchronized with one CTD parameter (PRES or TEMP or PSAL). The synchronization is done with the timely closest sample of the CTD (see float manual for details). | 2023-05-02 |
| CB00001 | CONFIG_<short_sensor_name>DepthZone<N>DepthZone<N+1>PressureThreshold_dbar | Threshold between depth zone #N and depth zone #N+1 for <short_sensor_name> (in dbar). | 2023-05-02 |
| CB00008 | CONFIG_<short_sensor_name>DepthZone<N>PowerAcquisitionMode_NUMBER | Power acquisition mode of the <short_sensor_name> in the depth zone #<N> (0 : none, 2 : pulsed, 3 : continuous). | 2023-05-02 |
| CB00002 | CONFIG_<short_sensor_name>DepthZone<N>SlicesThickness_dbar | Slices thickness for <short_sensor_name> in the depth zone #<N> (in dbar). | 2023-05-02 |
| CB00003 | CONFIG_<short_sensor_name>DescentToParkPresSamplingPeriod_seconds | Sampling period of the <short_sensor_name> during the descent to parking pressure (in seconds). | 2023-05-02 |
| CB00005 | CONFIG_<short_sensor_name>DescentToProfilePresSamplingPeriod_seconds | Sampling period of the <short_sensor_name> during the descent to profile pressure (in seconds). | 2023-05-02 |
| CB10004 | CONFIG_<short_sensor_name>DriftAtParkPresSamplingPeriod_minutes | Sampling period of the <short_sensor_name> during the drift at parking pressure (in minutes). | 2023-05-02 |
| CB00006 | CONFIG_<short_sensor_name>DriftAtProfilePresSamplingPeriod_minutes | Sampling period of the <short_sensor_name> during the drift at profile pressure (in minutes). | 2023-05-02 |
| CB00012 | CONFIG_<short_sensor_name>FirstValidSample_NUMBER | Rank of the first valid sample provided by the <short_sensor_name> (0 is the rank of the first sample). | 2023-05-02 |
| CB00066 | CONFIG_<short_sensor_name>IgnoreSamplesWhenPumpActive_LOGICAL | Ignore sample measurements acquired while the hydraulic pump is running. Values: Yes = 1, No = 0 | 2023-05-02 |
| CB00096 | CONFIG_<short_sensor_name>InAirMeasurementNumberOfSamples_NUMBER | Number of measurements sampled before and after inflating the air bladder for the <short_sensor_name> sensor during the "in air measurement" phase. | 2023-05-02 |
| CB00097 | CONFIG_<short_sensor_name>InAirMeasurementSamplingPeriod_seconds | Sampling period for the <short_sensor_name> sensor during the "in air measurement" phase. | 2023-05-02 |
| CB00054 | CONFIG_<short_sensor_name>InPumpedStream_LOGICAL | Bio Argo sensors can either be mounted separately to the Ctd or mounted within the Ctd pumped stream. Values: Yes = 1, No = 0 | 2023-05-02 |
| CB00036 | CONFIG_<short_sensor_name>MaxTransmitted<param>Fluorescence_COUNT | Minimum value of transmitted <short_sensor_name> Fluorescence of <param> measurements (in counts). | 2023-05-02 |
| CB00034 | CONFIG_<short_sensor_name>MaxTransmittedBeta_COUNT | Minimum value of transmitted <short_sensor_name> beta measurements (in counts). | 2023-05-02 |
| CB00088 | CONFIG_<short_sensor_name>MeasurementsInAir_LOGICAL | Sensors can be mounted on a stick to perform measurements in Air. Values: Yes = 1, No = 0 | 2023-05-02 |
| CB00035 | CONFIG_<short_sensor_name>MinTransmitted<param>Fluorescence_COUNT | Minimum value of transmitted <short_sensor_name> Fluorescence of <param> measurements (in counts). | 2023-05-02 |
| CB00033 | CONFIG_<short_sensor_name>MinTransmittedBeta_COUNT | Minimum value of transmitted <short_sensor_name> beta measurements (in counts). | 2023-05-02 |
| CB10008 | CONFIG_<short_sensor_name>PowerAcquisitionMode_NUMBER | Power acquisition mode of the Sensor defined by <short_sensor_name>Input options for CTD (1 : continuous, 2 : pulsed). Input options for Optode (0: none, 1 : continuous, 2 : pulsed). | 2023-05-02 |
| CB00011 | CONFIG_<short_sensor_name>PowerSwitchDelayMin_msec | Minimum waiting time needed by the <short_sensor_name> between a switch OFF and a switch ON (in milli-seconds). | 2023-05-02 |
| CB00065 | CONFIG_<short_sensor_name>TimePressureOffset_seconds | Time interval between <short_sensor_name> and pressure measurements due to the fact that the <short_sensor_name> answer is not simultaneous with the CTD/pressure answer | 2023-05-02 |
| CB00064 | CONFIG_<short_sensor_name>TurbidityWavelength_nm | Wavelength of <short_sensor_name> for Turbidity measurements (in nanometer) | 2023-05-02 |
| CB00048 | CONFIG_<short_sensor_name>VerticalPressureOffset_dbar | vertical pressure offset due to the fact that the sensor is not exactly at the Ctd pressure | 2023-05-02 |
| CB00010 | CONFIG_<short_sensor_name>WarmUpTime_msec | Time, needed after the <short_sensor_name> is powered ON, to provide its first sample (in milli-seconds). | 2023-05-02 |
| CC00003 | CONFIG_AscentAdjustmentToBuoyancy_seconds | commonly cited as 'buoyancy nudge', this controls the ascent rate, units could be COUNT or whatever is reported, i.e. for SOLOII it is seconds pump is run to adjust float rise rate on ascent. May be changeable via 2-way communications. | 2023-05-02 |
| CC00004 | CONFIG_AscentEndThreshold_dbar | Threshold used by the float to stop ascent speed control and pump actions. | 2023-05-02 |
| CC00005 | CONFIG_AscentSamplingPeriod_seconds | Sampling period during the ascending profile (in seconds). | 2023-05-02 |
| CC00007 | CONFIG_AscentSpeedFactor_NUMBER | This factor defines the speed of the ascent phase (between 0: nominal speed and 5: lowest speed). | 2023-05-02 |
| CC00008 | CONFIG_AscentSpeedMin_mm/s | Float minimum ascent speed before activating the pump. | 2023-05-02 |
| CC00009 | CONFIG_AscentSpeedStartPressureThresholdForSlowPhase_dbar | Pressure threshold to start the slow ascent speed phase. | 2023-05-02 |
| CC00006 | CONFIG_AscentSpeed_mm/s | ascent speed during upcast (can be used to estimate the profile duration). Changeable via 2-way communications. | 2023-05-02 |
| CC00010 | CONFIG_AscentTime_hours | preset duration of ascent | 2023-05-02 |
| CC00011 | CONFIG_AscentToSurfaceTimeOut_hours | maximum time a float will try to reach its target depth (surface) before aborting this step | 2023-05-02 |
| CC00012 | CONFIG_AscentVerticalThresholdForBuoyancyAction_dbar | If the float vertical motion, during CONFIG_PressureCheckTimeAscent_minutes, is less than this threshold, the float makes buoyancy adjustments. | 2023-05-02 |
| CC00013 | CONFIG_BitMaskMonthsIceDetectionActive_NUMBER | This parameter indicates for which months the ice detection algorithm is active. The bit mask is input as a 3 digit hexadecimal value in the mission file sent to the float. This parameter in the metadata file however is the decimal number of that hexadecimal value. For example for the Southern Hemisphere the default position is to have the ice detection algorithm active for all months except February. (The hexadecimal value in the mission file is 'FFD' and the number for the configuration parameter in the metafile would be 4093). The northern hemisphere default would be all months active except for August. In this case the hexadecimal value is 'F7F' and the number in the configuration parameter in the metafile would be 3967). | 2023-05-02 |
| CC00014 | CONFIG_BitMaskMonthsIceEvasionActive_NUMBER | When is ice evasion active - months in reverse order. This is a parameter for AC1 which provides the months it should be used. | 2023-05-02 |
| CC00015 | CONFIG_BuoyancyMinimum_COUNT | The minimum allowable buoyancy position in counts, overriding any other count setting. This configuration parameter prevents the movement of oil from the oil compartment of the bladder into the oil reservoir at the specified count to manage the maximum depth of a descent. In general CONFIG_BuoyancyMinimum_COUNT should be set less than the CONFIG_PistonProfile_COUNT. | 2023-05-02 |
| CC00016 | CONFIG_BuoyancyNudgeToPark_COUNT | The number of counts to change the piston position from its current position in the direction that will bring the float closer to the Park depth. It is applied after three successive pressure samples that are outside the dead band specified by CONFIG_PressureTargetToleranceDuringDrift_dbar. | 2023-05-02 |
| CC00017 | CONFIG_BuoyancyReductionFirstThreshold_dbar | First threshold of the buoyancy reduction phase (see float manual for explanations). | 2023-05-02 |
| CC00018 | CONFIG_BuoyancyReductionSecondThreshold_dbar | Second threshold of the buoyancy reduction phase (see float manual for explanations). | 2023-05-02 |
| CC00029 | CONFIG_CPActivationPressure_dbar | CP Activation Pressure | 2023-05-02 |
| CC00031 | CONFIG_CTDPumpStopPressureOffset_dbar | The pressure in decibars added to the most recently measured pressure at the surface, the sum of which is the pressure at which the conductivity, temperature and pressure sampling stops for a pumped type CTD. It is also the pressure at which the Surface phase begins. | 2023-05-02 |
| CC00032 | CONFIG_CTDPumpStopPressurePlusThreshold_dbar | The sum of CONFIG_CTDPumpStopPressure_dbar plus a pressure threshold or overlap (Poverlap). For PROVOR floats, Poverlap is defined as follows: Poverlap = bin_size/2 for PROVOR floats with software versions < 5816A00 and ARVOR floats with software versions < 5605A00.Poverlap = 0.5 dbar for PROVOR floats with software versions >= 5816A00 and ARVOR floats with software versions >=5605A00. | 2023-05-02 |
| CC00030 | CONFIG_CTDPumpStopPressure_dbar | The pressure at which the CTD pump is switched off. As the float ascends, the code looks at the pressure and if <= CONFIG_CTDPumpStopPressure, the CTD is turned off. CTDPumpStopPressure is a firmware threshold and as such, data may continue to be collected for a limited span after the threshold is recognized. Especially in floats that return high resolution discrete data, there might be data collected shallower than the cut off, due to the discrete nature of the pressure data and also due to the time necessary for the firmware to turn off the CTD once the pressure threshold is reached. For example for SOLOII floats the CTD is switched off at 1dbar, and typically the shallowest data is from 0.5 to 0.8 dbar. This shallow data should be carefully assessed for its validity. | 2023-05-02 |
| CC00019 | CONFIG_ClockAscentEndTimeProfile1_HHMM | Profiler configuration - Ascent end time - Profile 1. The expected time at the surface of Profile 1. | 2023-05-02 |
| CC00020 | CONFIG_ClockAscentEndTimeProfile2_HHMM | Profiler configuration - Ascent end time - Profile 2. The expected time at the surface of Profile 2. | 2023-05-02 |
| CC00021 | CONFIG_ClockAscentEndTimeProfile3_HHMM | Profiler configuration - Ascent end time - Profile 3. The expected time at the surface of Profile 3. | 2023-05-02 |
| CC00022 | CONFIG_ClockAscentStart_minutes | Preset time to start ascent profile, if units = MINUTES (in minutes past midnight), if units = HH (24 hour clock). Potentially phase determining, phase 0 if never changed. | 2023-05-02 |
| CC00023 | CONFIG_ClockPresetStartCycle_LOGICAL | Cycle to start at a preset time 0: Disabled; 1: Enabled. Potentially phase determining, phase 0 if never changed. | 2023-05-02 |
| CC00024 | CONFIG_ClockStartCycle_minutes | preset time to start the cycle, minutes after midnight. Potentially phase determining, phase 0 if never changed. | 2023-05-02 |
| CC00025 | CONFIG_CompensatorHyperRetraction_COUNT | setting for the compensator hyper-retraction. Phase 0. | 2023-05-02 |
| CC00026 | CONFIG_ConnectionFailureTimeOut_minutes | Is the maximum time allowed for the float to connect to the RUDICS server; i.e. it tries to connect during 30 minutes (values set for these floats) if it fails it is probably because it is under ice (that has not been detected by ISA or hanging algorithms). | 2023-05-02 |
| CC00027 | CONFIG_ConnectionInitialTimeOut_seconds | Connection time-out allowed for initial connection to the RUDICS server - i.e. is the maximum time allowed for the float to connect to the RUDICS server; i.e. it tries to connect during 30 minutes (values set for these floats) if it fails it is probably because it is under ice (that has not been detected by ISA or hanging algorithms). | 2023-05-02 |
| CC00028 | CONFIG_ConnectionTimeOut_seconds | Connection time-out, i.e. maximum transmission period for one telemetry session (an example: for this float version it is the maximum duration of the RUDICS session; for example if the RUDICS session lasts more that 2 hours (value set for these floats which are ice floats which may have stored cycles to transmits) the float disconnects and starts a new deep cycle (the remaining stored data will be transmitted next transmission session). | 2023-05-02 |
| CB00063 | CONFIG_CroverBeamAttenuationBandwidth_nm | Bandwidth of Crover for Beam attenuation measurements (in nanometer) | 2023-05-02 |
| CB00061 | CONFIG_CroverBeamAttenuationWavelength_nm | Wavelength of Crover for Beam attenuation measurements (in nanometer) | 2023-05-02 |
| CB00040 | CONFIG_CroverMaxTransmittedBeamAttenuation_m^-1 | Maximum value of transmitted Crover beam attenuation measurements (in 1/m). | 2023-05-02 |
| CB00039 | CONFIG_CroverMinTransmittedBeamAttenuation_m^-1 | Minimum value of transmitted Crover beam attenuation measurements (in 1/m). | 2023-05-02 |
| CB00014 | CONFIG_CtdMaxTransmittedPressure_dbar | Maximum value of transmitted Ctd pressure measurements (in dbar). | 2023-05-02 |
| CB00018 | CONFIG_CtdMaxTransmittedSalinity_mpsu | Maximum value of transmitted Ctd salinity measurements (in milli-PSU). | 2023-05-02 |
| CB00016 | CONFIG_CtdMaxTransmittedTemperature_mdegC | Maximum value of transmitted Ctd temperature measurements (in milli-DegC). | 2023-05-02 |
| CB00013 | CONFIG_CtdMinTransmittedPressure_dbar | Minimum value of transmitted Ctd pressure measurements (in dbar). | 2023-05-02 |
| CB00017 | CONFIG_CtdMinTransmittedSalinity_mpsu | Minimum value of transmitted Ctd salinity measurements (in milli-PSU). | 2023-05-02 |
| CB00015 | CONFIG_CtdMinTransmittedTemperature_mdegC | Minimum value of transmitted Ctd temperature measurements (in milli-DegC). | 2023-05-02 |
| CC00033 | CONFIG_CycleTime_hours | For APEX and ARVOR floats this is the total duration of one cycle, usually 240 hours (10 days). For SOLO floats this is the total duration of one cycle, assuming that all float operations reach their full time-out intervals before moving to the next float stage. Typically the actual cycle time will be shorter than this value. | 2023-05-02 |
| CC00034 | CONFIG_DebugBits_NUMBER | Awaiting clarification. A request is in with Webb for more information | 2023-05-02 |
| CC00037 | CONFIG_DeepProfileFirstFloat_LOGICAL | Some APEX floats are set to do a "profile on deployment". This means that when the float is deployed it skips the drift phase at the PARKING depth and sinks directly to the PROFILE depth and starts ascending for the first profile. Independent of the Park and Profile cycle length, the first profile is always a Deep Profile that begins at the Profile Depth. This means the float returns a CTD profile relatively soon, typically less than a day, after the float is deployed. This feature supports comparison of the initial float profile with a conventional CTD cast from the ship. The result is that the first cycle is of shorter duration with a profile depth equal to PROFILE configuration pressure (regardless of the CONFIG_ParkAndProfileCycleCounter_COUNT configuration information). (Yes = 1, No = 0). | 2023-05-02 |
| CC00035 | CONFIG_DeepestPressureAscendingProfile_dbar | deepest pressure sampled in the ascending profile - example 2000 for a profile starting at 2000 dbar | 2023-05-02 |
| CC00036 | CONFIG_DeepestPressureDescendingProfile_dbar | deepest pressure sampled in the descending profile - example 500 for a profile ending at 500 dbar | 2023-05-02 |
| CC00038 | CONFIG_DelayBeforeMissionStart_minutes | Float waiting period before the first cycle of its mission (in minutes). | 2023-05-02 |
| CC00039 | CONFIG_DepthTable_NUMBER | Depth table number for profiler sampling pressures. Phase 0. | 2023-05-02 |
| CC00040 | CONFIG_DescentAdjustmentToBuoyancy_seconds | Commonly cited as 'buoyancy nudge', this controls the descent rate, units could be COUNT or whatever is reported, i.e. for SOLOII it is seconds pump is run to adjust float descent rate from drift depth to profile depth. The SOLO-II floats are ballasted for profile depth, if the floats are poorly ballasted, float will descend quite fast to profile depth. The more pumping that is done at 1000db that is unnecessary at 2000db will save energy and it can be used as an energy saving measure. Occasionally this means the float will stop short of profile depth but won't have grounded. | 2023-05-02 |
| CC00042 | CONFIG_DescentSpeedMin_mm/s | Float minimum descent speed before activating the valve. | 2023-05-02 |
| CC00041 | CONFIG_DescentSpeed_mm/s | Descent speed during downcast (can be used to estimate the time to descent from parking pressure to profile pressure). Changeable via 2-way communications. | 2023-05-02 |
| CC00043 | CONFIG_DescentToParkPresSamplingTime_seconds | Sampling period during the descent to parking pressure (in seconds). | 2023-05-02 |
| CC00044 | CONFIG_DescentToParkTimeOut_hours | maximum time a float will try to reach its target depth (park) before aborting this step | 2023-05-02 |
| CC00045 | CONFIG_DescentToProfTimeOut_hours | maximum amount of time allowed for the float to descend to Profile pressure from Park pressure. This variable should cover DELAI/DELAY parameter required for trajectory processing. | 2023-05-02 |
| CC00046 | CONFIG_DescentVerticalThresholdForBuoyancyAction_dbar | If the float vertical motion, during CONFIG_PressureCheckTimeDescent_minutes, is less than this threshold, the float makes buoyancy adjustments. | 2023-05-02 |
| CC00047 | CONFIG_Direction_NUMBER | Ascending = 1, Descending = 2, Ascending and Descending = 3 | 2023-05-02 |
| CC00049 | CONFIG_DownTimeAutumnWinter_hours | preset duration of the down time (start of descent to start of ascent) specific to the autumn/winter period. Changeable via 2-way communications. | 2023-05-02 |
| CC00050 | CONFIG_DownTimeExpiryTimeOfDay_minutes | a time-out value (time of day, i.e. in minutes past midnight) for expiration of the down time | 2023-05-02 |
| CC00051 | CONFIG_DownTimeSpringSummer_hours | preset duration of the down time (start of descent to start of ascent) specific to the spring/summer period. Changeable via 2-way communications. | 2023-05-02 |
| CC00048 | CONFIG_DownTime_hours | preset duration of the down time (start of descent to start of ascent) - changed from : CONFIG_DownTimeInterval_hours and CONFIG_DownTimeOut. This parameter is important for trajectory files. | 2023-05-02 |
| CC00052 | CONFIG_EmergencyModeWaterLeakDetection_LOGICAL | If set to "yes", the float will transition to the Emergency mode upon detection of an internal water leak. If set to "no", the float will only log the condition to the system_log.txt file. | 2023-05-02 |
| CC00053 | CONFIG_FirstBuoyancyNudge_COUNT | test message data - initial buoyancy nudge which is used at both the beginning and end of the profile. Phase 0. | 2023-05-02 |
| CB00056 | CONFIG_FlbbSampling_NUMBER | Specifies whether the Flbb instrument is set to sample. Values: Zero disables sampling and nonzero enables sampling. | 2023-05-02 |
| CB00037 | CONFIG_FlntuMaxTransmittedTurbidity_COUNT | Maximum value of transmitted Flntu turbidity measurements (in counts). | 2023-05-02 |
| CB00038 | CONFIG_FlntuMinTransmittedTurbidity_COUNT | Minimum value of transmitted Flntu turbidity measurements (in counts). | 2023-05-02 |
| CC00054 | CONFIG_FloatReferenceDay_FloatDay | Profiler configuration - Reference day, for PROVOR and ARVOR floats this is: The day number on which the first profile is to be made. The day when the mission starts is zero. Phase 0. | 2023-05-02 |
| CC00055 | CONFIG_GPSAcquisitionEndCycle_LOGICAL | The float performs a GPS session to acquire a GPS fix at the end of the cycle (Yes=1/No=0). | 2023-05-02 |
| CC00056 | CONFIG_GPSAcquisitionEndOfLife_LOGICAL | The float performs a GPS session to acquire a GPS fix in each End Of Life transmission (Yes=1/No=0). | 2023-05-02 |
| CC00057 | CONFIG_GPSImprovedLocation_LOGICAL | Use the GPS improved location mode. This mode can be used when the float altitude is 0 meter, it provides better locations. | 2023-05-02 |
| CC00059 | CONFIG_GPSSetClockSensorCard_LOGICAL | When the float Real Time Clock is set, also set the clock of the measurement card. | 2023-05-02 |
| CC00058 | CONFIG_GPSSetClock_LOGICAL | Set the float Real Time Clock with GPS time. To disable float clock set from GPS time when at surface. | 2023-05-02 |
| CC00060 | CONFIG_GPSTimeout_seconds | Timeout for GPS acquisition. | 2023-05-02 |
| CC00062 | CONFIG_GroundingModeDeepZoneThickness_dbar | In case of grounding during the "descent to profile depth" phase, this parameter (PM18 in float user manual) defines the thickness of a new deep zone (from profile start pressure) for the purpose of data reduction. The thickness of the slices is 1 dbar in this zone. Should be set to 0 to disable this function. | 2023-05-02 |
| CC00063 | CONFIG_GroundingModeForProfileDepth_NUMBER | Action performed by the float when a grounding is detected during descent to profile depth. For PROVOR CTS5 floats: 2: the float stays on the seabed until the ascent start time, 3: the ascent starts immediately. In this float version the actions to be performed when a grounding is detected at parking depth (stored in CONFIG_GroundingMode_NUMBER) or at profile depth (stored in CONFIG_GroundingModeForProfileDepth_NUMBER) may differ. Consequently we need 2 configuration parameters. | 2023-05-02 |
| CC00064 | CONFIG_GroundingModeMinPresThreshold_dbar | If in grounding mode 0, the float changes its drift pressure only if its current pressure is greater than this value. | 2023-05-02 |
| CC00065 | CONFIG_GroundingModePresAdjustment_dbar | If in grounding mode 0, the float changes its drift pressure to its programmed one minus this value only if its current pressure is greater than this value. | 2023-05-02 |
| CC00061 | CONFIG_GroundingMode_LOGICAL | Action performed by the float when a grounding is detected. 0: the float changes its drift pressure, 1: the float stays on the seabed until the next phase of the cycle. For PROVOR CTS5 the number assigned to each mode has changed - see float manual for details for this model. | 2023-05-02 |
| CC00066 | CONFIG_HangingMode_NUMBER | Action performed by the float when a hanging is detected (see float manual for details). [JP additional comments on behaviour for PROVOR floats: The hanging mode is the same idea as the grounding mode but for an ascent phase. When the float detects a too low vertical motion after having activated its pump to try to ascend it enters in a hanging mode (it is probably stuck at the sea floor). This parameter configures (with the same idea as CONFIG_GroundingMode_NUMBER for grounding) what should be the actions to perform to try to escape from hanging (it can activate its pump and valve alternatively to try to escape or abandon the ascent and switch to the next scheduled task]. | 2023-05-02 |
| CC00067 | CONFIG_HydraulicDataTransmission_LOGICAL | The float transmits hydraulic data at the end of the cycle. The float records the pump/valve actions (time, pressure, duration); these data can be transmitted (or not) in specific SBD messages through a remote control command. Input: (Yes=1/No=0). | 2023-05-02 |
| CC00068 | CONFIG_HyperRetractionStopPressure_dbar | For Apex APF11 Iridium floats, Hyper Retraction is used to pull in an amount of oil to temporarily increase a float’s density as it leaves the ocean surface. The result of the increased float density allows a float to move through a mixed density layer more easily or allows a float to descend at a faster rate. In particular, the HyperRetractPressure is the pressure that the float uses to restore the piston back to the ParkDescentCount. | 2023-05-02 |
| CC00070 | CONFIG_IceDetectionAcousticStartPressureThreshold_dbar | Pressure threshold to start the acoustic ice detection test. Concerning ice detection and avoidance, the float uses 3 algorithms: 1) AC1: it stops profiles at a given depth for given months in the year; 2) ISA: the (well known) ISA algorithm which determines possible ice coverage from TEMP (and PSAL in this case) measurements; 3) AID: the Acoustic Ice Detection which used an acoustic altimeter to detect ice at sea surface]. | 2023-05-02 |
| CC00071 | CONFIG_IceDetectionAscentVerticalThresholdForBuoyancyAction_dbar | Similar to CONFIG_AscentVerticalThresholdForBuoyancyAction_dbar but for a float in ice detection mode. | 2023-05-02 |
| CC00072 | CONFIG_IceDetectionConnectionTimeOut_minutes | Similar to CONFIG_ConnectionTimeOut_minutes but for the first telemetry session of a float in ice detection mode(i.e. in ice detection mode the float reduces the timeout of the first Iridium connection: if the first connection fails the cycle is aborted (ice probably present) but if the first connection succeeds (waters free of ice) the float switches to the nominal timeout (CONFIG_ConnectionTimeOut_minutes) for the following transmissions of the current cycle). | 2023-05-02 |
| CC00073 | CONFIG_IceDetectionConsecutiveDetectionBeforeFloatSurfaceInhibition_Number | Number of consecutive ISA detections before float surface inhibition. If fewer consecutive ice detections are made, then the float will immediately seek the surface if mixed layer temp is warm. | 2023-05-02 |
| CC00074 | CONFIG_IceDetectionDescentVerticalThresholdToEndBuoyancyInversionPhase_dbar | When the cycle is aborted this threshold is used to detect speed inversion and to stop buoyancy inversion phase. | 2023-05-02 |
| CC00093 | CONFIG_IceDetectionEndTelemetryDay_NUMBER | Last day of the year during which telemetry is attempted during the Surface phase. When the float surfaces on a day that is not specified, it does not attempt telemetry and immediately begins the Park Descent phase for the next profiling cycle. TelemetryDays are specified with a start day and an end day. The start day is the first day of the transmit season for the year. The end day is the last day of the transmit season for the year. A setting of 0 0 disables TelemetryDays, and the float attempts telemetry during each Surface Phase. | 2023-05-02 |
| CC00092 | CONFIG_IceDetectionFirstTelemetryDay_NUMBER | First day of the year during which telemetry is attempted during the Surface phase. When the float surfaces on a day that is not specified, it does not attempt telemetry and immediately begins the Park Descent phase for the next profiling cycle. TelemetryDays are specified with a start day and an end day. The start day is the first day of the transmit season for the year. The end day is the last day of the transmit season for the year. A setting of 0 0 disables TelemetryDays, and the float attempts telemetry during each Surface Phase. | 2023-05-02 |
| CC00075 | CONFIG_IceDetectionISAMode_NUMBER | Mode of the ISA ice detection algorithm (see float manual for details). For this firmware Mar 2018 the values are (0: not used, 1: algorithm based on temperature median value, 2: algorithm based on temperature median value and associated salinities) | 2023-05-02 |
| CC00091 | CONFIG_IceDetectionMaxCycles_NUMBER | The maximum number of Ice Descent and Ice Ascent cycles the float will perform when it is unable to perform telemetry. When it has completed the specified number of cycles, the float will continue with the next profiling cycle.Range: 0–24 cyclesIf IceDescentCycles is disabled, the float will try to detect an ice cap if it cannot find the sky. If IceDescentCycles is enabled, the float will not try to detect the ice cap and will operate in accordance with “Ice Descent and Ice Ascent Cycles” where it tries to drift out from under an ice cap. | 2023-05-02 |
| CC00076 | CONFIG_IceDetectionMaxDaysNoTransmission_NUMBER | Maximum delay (in days/cycles) of no transmission due to the ice detection algorithm. This parameter is used to disable the ice detection algorithm and force the float to surface even if ice is detected. | 2023-05-02 |
| CC00077 | CONFIG_IceDetectionMixedLayerPMax_dbar | Maximum sampling pressure used by ice cover detection algorithm. i.e. start pressure threshold for ice detection algorithm) | 2023-05-02 |
| CC00078 | CONFIG_IceDetectionMixedLayerPMin_dbar | Minimum sampling pressure used by ice cover detection algorithm. (i..e end pressure threshold for ice detection algorithm) | 2023-05-02 |
| CC00079 | CONFIG_IceDetectionNoVerticalMotionTimeOut_csec | When the float is in ice detection mode if, despite of pump actions, no vertical motion is detected during this delay, the cycle is aborted. | 2023-05-02 |
| CC00080 | CONFIG_IceDetectionOilVolumeForFirstValveAction_cm^3 | Volume of the first valve action of a buoyancy inversion phase. | 2023-05-02 |
| CC00081 | CONFIG_IceDetectionOilVolumeMinForGroundingDetection_cm^3 | Similar to CONFIG_OilVolumeMinForGroundingDetection_cm^3 but for a float in a buoyancy inversion phase. | 2023-05-02 |
| CC00082 | CONFIG_IceDetectionOilVolumePerValveAction_cm^3 | Valve action duration during the buoyancy inversion phase. | 2023-05-02 |
| CC00083 | CONFIG_IceDetectionPressureInterval_dbar | Period of the ice detection algorithm. "It is the pressure interval used by the float to collect T and S samples between CONFIG_IceDetectionMixedLayerPMax_dbar and CONFIG_IceDetectionMixedLayerPMin_dbar for the TEMP comparison." Original proposed name was: CONFIG_IceDetectionPeriod_dbar | 2023-05-02 |
| CC00084 | CONFIG_IceDetectionPumpActionMaxTimeAscent_csec | Similar to CONFIG_PumpActionMaxTimeAscent_csec but for a float in ice detection mode. | 2023-05-02 |
| CC00085 | CONFIG_IceDetectionSalinityCoefficient_NUMBER | Coefficient used when Salinity is considered in the ice evasion criteria (i.e. median(TEMP) < CONFIG_IceDetection_degC+CONFIG_IceDetectionSalinityCoefficient_NUMBER*median(PSAL)). | 2023-05-02 |
| CC00086 | CONFIG_IceDetectionSpringInhibitionAscentEnd_dbar | Ice evasion depth for the spring inhibition part of the ISA algorithm. "Spring inhibition" is the first step of the ISA algorithm. If the ISA algorithm raised (with the TEMP comparison) a profile evasion in the last CONFIG_IceDetectionSpringInhibitionDelaySinceLastIceEvasion_NUMBER days, the profile is aborted (without entering in the TEMP comparison loop) at CONFIG_IceDetectionSpringInhibitionAscentEnd_dbar. | 2023-05-02 |
| CC00087 | CONFIG_IceDetectionSpringInhibitionDelaySinceLastIceEvasion_NUMBER | Maximum delay (in days/cycles) since the last ice evasion date to attempt a surfacing. This is often called the "Spring", where the float stays underwater for a time even though the temperature has warmed. "Spring inhibition" is the first step of the ISA algorithm. If the ISA algorithm raised (with the TEMP comparison) a profile evasion in the last CONFIG_IceDetectionSpringInhibitionDelaySinceLastIceEvasion_NUMBER days, the profile is aborted (without entering in the TEMP comparison loop) at CONFIG_IceDetectionSpringInhibitionAscentEnd_dbar. | 2023-05-02 |
| CC00088 | CONFIG_IceDetectionStartPressure_dbar | Start pressure of the ice detection algorithm. The float collects T and S samples from CONFIG_IceDetectionMixedLayerPMax_dbar (=50dbar) but starts the TEMP comparison at CONFIG_IceDetectionStart_dbar (=20dbar). Thus, the samples collected between 50 and 20 dbar are used for the first TEMP comparison. | 2023-05-02 |
| CC00094 | CONFIG_IceDetectionTelemetryTimeout_minutes | The amount of time in minutes allowed for the float to complete telemetry. A setting of 0 disables IceTelemetryTimeout, and the time available is instead determined by the remaining UpTime of the Ascent phase. | 2023-05-02 |
| CC00089 | CONFIG_IceDetectionTestDuration_seconds | Duration of the ice detection test. | 2023-05-02 |
| CC00069 | CONFIG_IceDetection_degC | Ice temperature in [degree Celsius/1e3] where profiles are aborted because of ice formation conditions | 2023-05-02 |
| CC00090 | CONFIG_IceEvasionStopPressure_dbar | Ice evasion depth. This is a parameter for AC1 ice algorithm which abort the profile at a prescribed depth (CONFIG_IceEvasionDepth_dbar) without any check on environmental conditions (as described in my email, AC1, ISA and AID algorithm are used together in the ice version of the CTS5). | 2023-05-02 |
| CC00095 | CONFIG_InAirMeasurementPeriodicity_NUMBER | Cycle periodicity of the "in air measurement" phase:- 0 means no "in air acquisition"- 1 means "in air acquisition" every cycle- N means "in air acquisition" one cycle every "N" cycles | 2023-05-02 |
| CC00096 | CONFIG_InAirMeasurementSamplingPeriod_seconds | Sampling period during the "in air measurement" phase. | 2023-05-02 |
| CC00097 | CONFIG_InAirMeasurementTime_minutes | Duration of the "in air measurement" phase. | 2023-05-02 |
| CC00098 | CONFIG_InternalCycle<D>LastGregDay_DD | Last day to use float cycle duration #<D> (in Gregorian day). (D is a number denoting the internal cycle label) | 2023-05-02 |
| CC00099 | CONFIG_InternalCycle<D>LastGregMonth_MM | Last month to use float cycle duration #<D> (in Gregorian month). (D is a number denoting the internal cycle label) | 2023-05-02 |
| CC00100 | CONFIG_InternalCycle<D>LastGregYear_YYYY | Last year to use float cycle duration #<D> (in Gregorian year, two digits). (D is a number denoting the internal cycle label) | 2023-05-02 |
| CC00101 | CONFIG_InternalCycleTime<D>_hours | Internal cycle duration #<D> (in hours). (D is a number denoting the internal cycle label) | 2023-05-02 |
| CC00102 | CONFIG_InternalPressureCalibrationCoef1_NUMBER | First coefficient used to compute float internal pressure in mBars from sensor counts. | 2023-05-02 |
| CC00103 | CONFIG_InternalPressureCalibrationCoef2_NUMBER | Second coefficient used to compute float internal pressure in mBars from sensor counts. | 2023-05-02 |
| CC00104 | CONFIG_LoggingVerbosity_NUMBER | Logging verbosity is an integer (values in range [0,4] for these floats) describing the parameters to be output. An integer in the range [0,4] that determines the logging verbosity with lower values producing more terse logging. A verbosity of 2 yields standard logging. | 2023-05-02 |
| CC00105 | CONFIG_MaxAttemptsGPSAcquisitionBeforeResetGPS_COUNT | Maximum number of GPS location acquisition retries before it resets the GPS. | 2023-05-02 |
| CC00106 | CONFIG_MaxCycles_NUMBER | Applies to PROVOR and ARVOR floats, profiler configuration - Number of cycles before float turns itself off, goes into end of life mode, or into recovery mode. Phase 0. | 2023-05-02 |
| CC00107 | CONFIG_MaxDelayBeforeCycleStart_minutes | The maximum extra time a float can stay on the surface after transmitting. This feature is used for SOLOII floats to try and make them stay in a particular area, e.g. near the equator for equatorial floats. If a float is drifting at the surface and moving in the direction we want, we turn the feature on to keep it drifting at the surface in a favourable direction. If the float is moving in a direction we don't want, then we turn this feature off, so the float dives immediately. Changeable via 2-way communications. | 2023-05-02 |
| CC00108 | CONFIG_MaxSizeEngineeringLogFile_kbyte | Maximum size of engineering log file. | 2023-05-02 |
| CC00109 | CONFIG_MeasureBattery_LOGICAL | measure the battery voltage and report it? (Yes = 1, No = 0) | 2023-05-02 |
| CC00110 | CONFIG_MinValveActionForSurfaceGroundingDetection_COUNT | Minimum number of surface valve attempts without change in pressure to set the surface grounding flag. | 2023-05-02 |
| CC00111 | CONFIG_MissionPreludeAutoTest_LOGICAL | If set to "yes", the float will transition to the Park Descent phase at the end of the period determined by CONFIG_MissionPreludeTime_hours only if the self test passes. If the self test fails, the float will go into Emergency mode. If set to "no", the float will transition to the Park Descent phase whether or not the self test passes. In addition, the test results, pass or fail, will be logged to the system_log.txt file. | 2023-05-02 |
| CC00112 | CONFIG_MissionPreludeTime_hours | This is the duration the float transmits test messages for (from start up) before the first dive. It’s crucial in calculating the time of the first descent. Phase 0. | 2023-05-02 |
| CC00113 | CONFIG_MissionSignature_NUMBER | Awaiting clarification. A request is in with Webb for more information | 2023-05-02 |
| CB00055 | CONFIG_NitrateSampling_NUMBER | Nitrate sampling flag. Values:<0:enable; 0:disable; >0:enable and initialize | 2023-05-02 |
| CC00114 | CONFIG_NumberOfInternalCycles_COUNT | Number of internal cycles. Note that the sub-cycle (i.e. final Argo cycle) durations are not really defined they are deduced from CONFIG_SurfaceDay_FloatDay and CONFIG_SurfaceTime_HH). | 2023-05-02 |
| CC00115 | CONFIG_NumberOfOutOfTolerancePresBeforeReposition_COUNT | Number of consecutive pressure measurements outside the target pressure interval before performing a drift readjustment. | 2023-05-02 |
| CC00116 | CONFIG_NumberOfSubCycles_NUMBER | Number of sub-cycles performs by the float during one float cycle. | 2023-05-02 |
| CB00052 | CONFIG_Ocr<param>Bandwidth<I>_nm | Bandwidth of Ocr <param> #<I> measurements (in nanometer). | 2023-05-02 |
| CB00051 | CONFIG_Ocr<param>Wavelength<I>_nm | Wavelength of Ocr<param> #<I> measurements (in nanometer). | 2023-05-02 |
| CB00030 | CONFIG_OcrMaxTransmitted<param><I>_COUNT | Maximum value of transmitted Ocr <param> #<I> measurements (in counts). | 2023-05-02 |
| CB00032 | CONFIG_OcrMaxTransmittedPar_COUNT | Maximum value of transmitted Ocr Photosynthetic Active Radiation measurements (in counts). | 2023-05-02 |
| CB00029 | CONFIG_OcrMinTransmitted<param><I>_COUNT | Minimum value of transmitted Ocr <param> #<I> measurements (in counts). | 2023-05-02 |
| CB00031 | CONFIG_OcrMinTransmittedPar_COUNT | Minimum value of transmitted Ocr Photosynthetic Active Radiation measurements (in counts). | 2023-05-02 |
| CC00117 | CONFIG_OilVolumeLastPumpActionBuoyancyAcquisition_cm^3 | Volume of the last pump action of the buoyancy acquisition phase. Original proposed name was: CONFIG_PumpActionOilVolumeBuoyancyAcquisition_cm^3 | 2023-05-02 |
| CC00118 | CONFIG_OilVolumeMaxPerPumpActionReposition_cm^3 | This information is used as a threshold for the pump action duration for reposition in the parking drift interval. The pump flow is known for each float and CONFIG_OilVolumeMaxPerPumpActionReposition_cm^3 is converted to a maxDurationOfPumpActionReposition. When a reposition should be performed, the float computes the needed pump action duration. In some specific cases the result can be a huge pump action duration and the result must be thresholded by maxDurationOfPumpActionReposition. | 2023-05-02 |
| CC00119 | CONFIG_OilVolumeMaxPerValveAction_cm^3 | This information is used as a threshold for the valve action durations. The valve flow is known for each float and CONFIG_OilVolumeMaxPerValveAction_cm^3 is converted to a maxDurationOfValveAction. During descent phases the float regularly computes a valve duration to sink to the target depth. In some specific cases the result can be a huge valve action duration and the result must have a maxDurationOfValveAction threshold. This configuration parameter can be modified via remote controls for Remocean floats, by a specialist in PROVOR vector configuration. | 2023-05-02 |
| CC00120 | CONFIG_OilVolumeMinForGroundingDetection_cm^3 | This information is a threshold used to detect a grounding of the float. If there is no vertical motion after having transferred CONFIG_OilVolumeMinForGroundingDetection_cm^3 through the valve, the grounded flag is activated and the float acts as configurated by the CONFIG_GroundingMode_LOGICAL parameter. This is a configuration parameter that may be modified via remote control, as some PROVOR floats have experienced erroneous grounding detection (under study but perhaps due to in-situ conditions). | 2023-05-02 |
| CC00121 | CONFIG_OilVolumeMinPerValveAction_cm^3 | This information is used as a threshold for the valve action durations. The valve flow is known for each float and CONFIG_OilVolumeMinPerValveAction_cm^3 is converted to a minDurationOfValveAction. During descent phases the float regularly computes a valve duration to sink to the target depth. In some specific cases the result can be a brief valve action duration and the result must have a minDurationOfValveAction threshold. | 2023-05-02 |
| CC00122 | CONFIG_OilVolumePerPumpActionAscent_cm^3 | Nominal oil volume of each pump action during ascent. | 2023-05-02 |
| CC00123 | CONFIG_OilVolumePerPumpActionDescent_cm^3 | Nominal oil volume of each pump action during descent (when the float brakes because of a too fast descent speed). | 2023-05-02 |
| CC00124 | CONFIG_OkVacuum_COUNT | Internal vacuum threshold (counts). | 2023-05-02 |
| CB00024 | CONFIG_OptodeMaxTransmittedBPhase_angularDeg | Maximum value of transmitted Optode B phase measurements (in degrees). | 2023-05-02 |
| CB00020 | CONFIG_OptodeMaxTransmittedC1Phase_angularDeg | Maximum value of transmitted Optode C1 phase measurements (in degrees). | 2023-05-02 |
| CB00022 | CONFIG_OptodeMaxTransmittedC2Phase_angularDeg | Maximum value of transmitted Optode C2 phase measurements (in degrees). | 2023-05-02 |
| CB00026 | CONFIG_OptodeMaxTransmittedDPhase_angularDeg | Maximum value of transmitted Optode D phase measurements (in degrees). | 2023-05-02 |
| CB00028 | CONFIG_OptodeMaxTransmittedTemperature_mdegC | Maximum value of transmitted Optode temperature measurements (in milli-DegC). | 2023-05-02 |
| CB00023 | CONFIG_OptodeMinTransmittedBPhase_angularDeg | Minimum value of transmitted Optode B phase measurements (in degrees). | 2023-05-02 |
| CB00019 | CONFIG_OptodeMinTransmittedC1Phase_angularDeg | Minimum value of transmitted Optode C1 phase measurements (in degrees). | 2023-05-02 |
| CB00021 | CONFIG_OptodeMinTransmittedC2Phase_angularDeg | Minimum value of transmitted Optode C2 phase measurements (in degrees). | 2023-05-02 |
| CB00025 | CONFIG_OptodeMinTransmittedDPhase_angularDeg | Minimum value of transmitted Optode D phase measurements (in degrees). | 2023-05-02 |
| CB00027 | CONFIG_OptodeMinTransmittedTemperature_mdegC | Minimum value of transmitted Optode temperature measurements (in milli-DegC). | 2023-05-02 |
| CC00125 | CONFIG_ParkAndProfileCycleCounter_COUNT | The number of profiles performed from Park depth before a deep profile is done. Changeable via 2-way communications. | 2023-05-02 |
| CC00126 | CONFIG_ParkPressure_dbar | park pressure - this may change if the float is reprogrammed and must be reported in the mission configuration settings | 2023-05-02 |
| CC00127 | CONFIG_ParkSamplesPerAverage_COUNT | If float reports average values, then this is the number of samples per value reported. For example, for a float that samples hourly during the park period for 105 hours, and reports the average P and T, this would be 105. Changeable via 2-way communications. | 2023-05-02 |
| CC00128 | CONFIG_ParkSamplingMethod_LOGICAL | Have to convert string input to LOGICAL (1 = averaged, 0 = spot sampling). Changeable via 2-way communications. | 2023-05-02 |
| CC00129 | CONFIG_ParkSamplingNumberValsReported_COUNT | Number of values reported during a single park period, e.g. a float may perform hourly sampling for 105 hrs and report this as two averaged samples for that park period. Changeable via 2-way communications. | 2023-05-02 |
| CC00131 | CONFIG_ParkSamplingPeriodSecondary_hours | Some floats have two different park sampling periods in a cycle, e.g. 1.5 hours followed by 6 hours. This is the configuration parameter for the secondary sampling period during the park phase following CONFIG_ParkSamplingPeriod_hours. Changeable via 2-way communications. | 2023-05-02 |
| CC00130 | CONFIG_ParkSamplingPeriod_hours | specifies sampling period during the park phase, e.g. for APEX floats could be hourly or for ARVOR floats 12 hourly, for SOLO/SOLOII floats this definition is: P,T,S is sampled during drift (park) every CONFIG_ParkSamplingPeriod_hours, e.g. every 2 hours. Changeable via 2-way communications. | 2023-05-02 |
| CC00132 | CONFIG_ParkTime_hours | time spent at the parking pressure, not including descending and ascending times - example 222 for 9 days and 6 hours at park pressure | 2023-05-02 |
| CC00133 | CONFIG_PistonFullExtension_COUNT | 2023-05-02 | |
| CC00134 | CONFIG_PistonFullRetraction_COUNT | 2023-05-02 | |
| CC00135 | CONFIG_PistonPark_COUNT | preset park piston position, in counts | 2023-05-02 |
| CC00136 | CONFIG_PistonPositionBallast_COUNT | 2023-05-02 | |
| CC00137 | CONFIG_PistonPositionHyperRetraction_COUNT | For Apex APF11 Iridium floats, Hyper Retraction is used to pull in an amount of oil to temporarily increase a float’s density as it leaves the ocean surface. The result of the increased float density allows a float to move through a mixed density layer more easily or allows a float to descend at a faster rate. In particular, the HyperRetractCount is the temporary piston position used when the float leaves the Surface and starts a ParkDescent. | 2023-05-02 |
| CC00138 | CONFIG_PistonPositionPressureActivation_COUNT | preset piston position for pressure activation. Can only go in phase 0. | 2023-05-02 |
| CC00139 | CONFIG_PistonProfile_COUNT | preset profile piston position, in counts | 2023-05-02 |
| CC00141 | CONFIG_PressureActivationCheckTime_hours | in pressure activated floats this parameter sets how often the float will test whether it is in the water, e.g. Every 2 hours | 2023-05-02 |
| CC00142 | CONFIG_PressureActivationMode_LOGICAL | Use the pressure activation feature. | 2023-05-02 |
| CC00143 | CONFIG_PressureActivationTimeout_seconds | The pressure activation phase starts after the first successful auto-test and ends (with the start of the float mission) at the end of the CONFIG_PressureActivationTimeout_seconds period. During this phase the float checks the external pressure and can start its mission as soon as a CONFIG_PressureActivation_dbar pressure is measured. | 2023-05-02 |
| CC00140 | CONFIG_PressureActivation_dbar | depth at which float is set to pressure activate | 2023-05-02 |
| CC00144 | CONFIG_PressureBladderMax_dbar | maximum air bladder pressure setting - units could be COUNT. Phase 0. | 2023-05-02 |
| CC00145 | CONFIG_PressureBladderTarget_dbar | Target bladder pressure - units could be COUNT. Phase 0. | 2023-05-02 |
| CC00146 | CONFIG_PressureCheckTimeAscent_minutes | Period of the pressure checks during the float ascent to surface. | 2023-05-02 |
| CC00147 | CONFIG_PressureCheckTimeBuoyancyReductionPhase_seconds | Period of the pressure checks after each valve action before checking the pressure during the buoyancy reduction phase (in seconds). | 2023-05-02 |
| CC00149 | CONFIG_PressureCheckTimeDescentToParkingDepth_seconds | The interval in seconds between float samples of the pressure to determine if the Park depth has been reached. | 2023-05-02 |
| CC00150 | CONFIG_PressureCheckTimeDescentToProfileDepth_seconds | The interval in seconds between float samples of the pressure to determine if the Profile depth has been reached. | 2023-05-02 |
| CC00148 | CONFIG_PressureCheckTimeDescent_minutes | Period of the pressure checks during the float descent (after CONFIG_BuoyancyReductionSecondThreshold_dbar). | 2023-05-02 |
| CC00151 | CONFIG_PressureCheckTimeParking_minutes | Period of the pressure checks during the float drift at park or profile depth. | 2023-05-02 |
| CC00152 | CONFIG_PressureCheckTimeStabilization_minutes | Period of the pressure checks during the float stabilization phases. | 2023-05-02 |
| CC00153 | CONFIG_PressureMaxBeforeEmergencyAscent_dbar | Emergency ascent phase start pressure (in dbars). | 2023-05-02 |
| CC00154 | CONFIG_PressureOffsetDelayBeforeResetCommand_minutes | Float waiting period before the surface ResetOffset CTD command. [NKE introduced a delay (in minutes) between the end of the transmission and the ResetOffset command (because surface pressure measurements seem to be corrupted by float transmission]. | 2023-05-02 |
| CC00155 | CONFIG_PressureOffsetResetAtSurface_LOGICAL | 2023-05-02 | |
| CC00156 | CONFIG_PressureOffsetSampledAfterTransmission_LOGICAL | The surface pressure offset is sampled only if an Iridium transmission or a GPS session occurred (to be sure that the pressure offset is sampled at the surface). Original proposed names was: CONFIG_SecuredPressureOffsetSampledAtSurface_LOGICAL | 2023-05-02 |
| CC00157 | CONFIG_PressureStartContinuousProfiling_dbar | preset pressure where continuous profiling begins on ascent. Phase variable. | 2023-05-02 |
| CC00158 | CONFIG_PressureTargetToleranceBeforeReposition_dbar | Defines the target pressure interval before performing a buoyancy readjustment to reposition during the drift at parking depth. When a PRES measurement (sampled to monitor the float drift at parking depth) is outside the [parking_pressure +- CONFIG_PressureTargetToleranceBeforeReposition_dbar] interval, the float adjust its buoyancy. | 2023-05-02 |
| CC00160 | CONFIG_PressureTargetToleranceDuringDriftAtParkingDepth_dbar | Defines the target pressure interval for float drift at parking depth (in dbars). | 2023-05-02 |
| CC00161 | CONFIG_PressureTargetToleranceDuringDriftAtProfileDepth_dbar | Defines the target pressure interval for float drift at profile depth (in dbars). | 2023-05-02 |
| CC00159 | CONFIG_PressureTargetToleranceDuringDrift_dbar | Defines the target pressure interval for float drift at parking or profile depth (in dbars). | 2023-05-02 |
| CC00163 | CONFIG_PressureTargetToleranceForStabilisationAtParkingDepth_dbar | Defines the target pressure interval for float stabilisation at parking depth (in dbars). | 2023-05-02 |
| CC00164 | CONFIG_PressureTargetToleranceForStabilisationAtProfileDepth_dbar | Defines the target pressure interval for float stabilisation at profile depth (in dbars). | 2023-05-02 |
| CC00165 | CONFIG_PressureTargetToleranceForStabilisationDuringAscent_dbar | Defines the target pressure interval for float stabilisation during ascent at a prescribed depth. The prescibed depth could be the PRES threshold to start low ascent (but I think this should not be in the definition which should stay more generic). | 2023-05-02 |
| CC00162 | CONFIG_PressureTargetToleranceForStabilisation_dbar | Defines the target pressure interval for float stabilisation at parking or profile depth (in dbars). | 2023-05-02 |
| CC00167 | CONFIG_PressureThresholdDataReductionIntermediateToDeep_dbar | The isobar that divides intermediate depths from deep depths for the purpose of data reduction with 3 depth zones (in dbars). | 2023-05-02 |
| CC00168 | CONFIG_PressureThresholdDataReductionShallowToIntermediate_dbar | The isobar that divides shallow depths from intermediate depths for the purpose of data reduction with 3 depth zones (in dbars). | 2023-05-02 |
| CC00166 | CONFIG_PressureThresholdDataReduction_dbar | The isobar that divides shallow depths from deep depths for the purpose of data reduction (in dbars). For floats with 2 depth zones. | 2023-05-02 |
| CC00169 | CONFIG_ProfileBottomBinInterval_cbar | Depth intervals for bottom depth (algorithm of data reduction). | 2023-05-02 |
| CC00170 | CONFIG_ProfileBottomSlicesThickness_dbar | Thickness of the slices for deep depths (algorithm of data reduction) (in dbars). | 2023-05-02 |
| CC00171 | CONFIG_ProfileDepthInterval_dbar | Target depth interval between final CTD samples when in the spot sampling mode. | 2023-05-02 |
| CC00172 | CONFIG_ProfileEvasionBrakingFactor_NUMBER | This factor defines the oil volume transferred from the external bladder when a profile evasion occurs and the float has to brake. The transferred oil volume is CONFIG_ProfileEvasionAscentSpeedFactor_NUMBER times the oil volume of the last pump action. | 2023-05-02 |
| CC00173 | CONFIG_ProfileIncludeTransitionBin_LOGICAL | Include transition bins between depth zones (shallow/intermediate/bottom) in the algorithm of data reduction (Yes=1/No=0). Yes: Calculate transition bin between top and middle section, and between middle and bottom section. Transition bins are: (last top bin center + Top_Bin_Interval/2) to (last top bin center + Middle_Bin_Interval/2) and (last middle bin center + Middle_Bin_Interval/2) to (last middle bin center + Bottom_Bin_Interval/2)No: Do not calculate transition bins. | 2023-05-02 |
| CC00174 | CONFIG_ProfileIntermediateBinInterval_cbar | Depth intervals for intermediate depth (algorithm of data reduction). | 2023-05-02 |
| CC00175 | CONFIG_ProfileIntermediateSlicesThickness_dbar | Thickness of the slices for intermediate depths (algorithm of data reduction) (in dbars). | 2023-05-02 |
| CC00176 | CONFIG_ProfilePressure_dbar | profile pressure - this may change if the float is reprogrammed and must be reported in the mission configuration settings | 2023-05-02 |
| CC00177 | CONFIG_ProfileSamplingMethod_LOGICAL | Have to convert string input to LOGICAL (1 = averaged, 0 = spot sampling) | 2023-05-02 |
| CC00178 | CONFIG_ProfileSurfaceBinInterval_cbar | Depth intervals for shallow depth (algorithm of data reduction). | 2023-05-02 |
| CC00179 | CONFIG_ProfileSurfaceSlicesThickness_dbar | Thickness of the slices for shallow depths (algorithm of data reduction) (in dbars). | 2023-05-02 |
| CC00180 | CONFIG_ProfileWhereChangePistonPosition_NUMBER | Use last piston position until this profile number. Can only go in phase 0. | 2023-05-02 |
| CC00181 | CONFIG_PumpActionIntervalDuringAscent_COUNT | interval between successive pump activations during ascent | 2023-05-02 |
| CC00182 | CONFIG_PumpActionMaxTimeAscent_csec | Maximum duration of a pump action during ascent (in centi-seconds). | 2023-05-02 |
| CC00183 | CONFIG_PumpActionMaxTimeBuoyancyAcquisition_csec | Maximum duration of the last pump action of the buoyancy acquisition phase. | 2023-05-02 |
| CC00184 | CONFIG_PumpActionMaxTimeReposition_csec | Maximum duration of the pump action for a drift readjustment (in centi-seconds). | 2023-05-02 |
| CC00186 | CONFIG_PumpActionTimeBuoyancyAcquisitionForInAirMeasCycle_csec | Duration of the last pump action of the buoyancy acquisition phase when a "in air measurement" phase is programmed (in centi-seconds). [For a cycle without "in air measurement phase" it is CONFIG_PumpActionTimeBuoyancyAcquisition_csec]. | 2023-05-02 |
| CC00185 | CONFIG_PumpActionTimeBuoyancyAcquisition_csec | Duration of the last pump action of the buoyancy acquisition phase (in centi-seconds). | 2023-05-02 |
| CC00187 | CONFIG_RafosSampling_minutes | Awaiting clarification. Is this a clock time or a period? Is it set or reported by the float? Probably need a more specific name. A request is in with Webbs for more information. | 2023-05-02 |
| CC00188 | CONFIG_RecoveryModeActivate_LOGICAL | Activates or deactivates recovery mode. Recovery mode is operator activated. If activated, the float remains on the surface indefinitely while transmitting its position and log files and downloading new mission and sample configuration parameters if available. If Recovery mode is then deactivated, the float will begin the Park Descent phase of a new mission. | 2023-05-02 |
| CC00190 | CONFIG_RudicsAndIridiumSessionWhenNoGPS_LOGICAL | For RUDICS transmission floats, perform also one Iridium session (to get an Iridium position) when the GPS fix is not valid. | 2023-05-02 |
| CC00189 | CONFIG_RudicsAndIridiumSession_LOGICAL | This float has a RUDICS transmission system. However it is able to connect to Iridium if the user want to get one Iridium position for each cycle. | 2023-05-02 |
| CC00192 | CONFIG_SeeksToParkPeriodsIntervals_seconds | The SEEK (settle) time for the float after descent as it 'settles' towards the drift target. For SOLO floats this is a constant. | 2023-05-02 |
| CC00191 | CONFIG_SeeksToParkPeriods_COUNT | the number of SEEKS (settles) that can be done by the float after descent as it 'settles' towards the drift target. | 2023-05-02 |
| CB00045 | CONFIG_SensorBoardShowModeOn_LOGICAL | Is the sensor board show mode ON? (Yes/No). | 2023-05-02 |
| CB00067 | CONFIG_SetClockSensorCard_LOGICAL | When the float Real Time Clock is set, also set the clock of the measurement card. | 2023-05-02 |
| CB00099 | CONFIG_SfetMaxTransmittedVrsPh_volts | Maximum value of transmitted Vrs_pH measurements (in volts). | 2023-05-02 |
| CB00098 | CONFIG_SfetMinTransmittedVrsPh_volts | Minimum value of transmitted Vrs_pH measurements (in volts). | 2023-05-02 |
| CC00193 | CONFIG_SlowAscentPistonAdjustment_COUNT | when ascent is too slow, this is used to adjust the piston position to speed ascent | 2023-05-02 |
| CB00046 | CONFIG_SunaApfFrameOutputPixelBegin_NUMBER | The Apf frame definition allows for a variable number of spectrometer pixels (also called channels) to be included in the frame. The two pixel values are configured indirectly via the wavelength range of the spectrum to be output (Suna Hardware Manual, section 4.2.3, input/output configuration parameters, data wavelength low/high.) The firmware converts the wavelength values to spectrometer pixels. | 2023-05-02 |
| CB00047 | CONFIG_SunaApfFrameOutputPixelEnd_NUMBER | The Apf frame definition allows for a variable number of spectrometer pixels (also called channels) to be included in the frame. The two pixel values are configured indirectly via the wavelength range of the spectrum to be output (Suna Hardware Manual, section 4.2.3, input/output configuration parameters, data wavelength low/high.) The firmware converts the wavelength values to spectrometer pixels. | 2023-05-02 |
| CB00041 | CONFIG_SunaDataType_NUMBER | Type of transmitted data from te Suna sensor (0 : nitrate concentration, 1 : Apf frame spectrum). | 2023-05-02 |
| CB00043 | CONFIG_SunaMaxTransmittedNitrateConcentration_umol/L | Maximum value of transmitted Suna nitrate concentration measurements (in micro-Mol/L). | 2023-05-02 |
| CB00042 | CONFIG_SunaMinTransmittedNitrateConcentration_umol/L | Minimum value of transmitted Suna nitrate concentration measurements (in micro-Mol/L). | 2023-05-02 |
| CB00053 | CONFIG_SunaWithScoop_LOGICAL | Suna with scoop which redirects flow through Suna optics | 2023-05-02 |
| CC00194 | CONFIG_SurfaceDay_FloatDay | Day of the float surfacing | 2023-05-02 |
| CC00196 | CONFIG_SurfaceTimeOut_hours | time spent on the surface (surface drift) - example 10 for a 10 hour surface drift, for NEMO(Iridium) the definition for this variable is: the time limit for staying at the surface, i.e. maximum surface time. This parameter is set for SOLOII, surface time duration is calculated for APEX and may not need to be reported. | 2023-05-02 |
| CC00195 | CONFIG_SurfaceTime_HH | Time of day of float surfacing - could be hour of the float surfacing or could be stored as seconds when set as hh:mm:ss (e.g. for PROVOR CTS5) | 2023-05-02 |
| CC00197 | CONFIG_SurfaceValveAdditionalActions_COUNT | Target number of additional valve actions performed at the surface during the buoyancy reduction phase. | 2023-05-02 |
| CC00198 | CONFIG_SurfaceValveMaxTimeAdditionalActions_csec | Maximum duration of the additional valve actions performed at the surface during the buoyancy reduction phase (in centi-seconds). | 2023-05-02 |
| CC00199 | CONFIG_SurfaceWaitPeriodAfterEmergencyAscent_minutes | Duration of the specific surface phase that occurs after an emergency ascent of the float. | 2023-05-02 |
| CC00200 | CONFIG_TargetAscentSpeed_cm/s | Speed of ascent during upcast in cm/s | 2023-05-02 |
| CC00201 | CONFIG_TelemetryAutoTestAtDeployment_LOGICAL | Perform a full auto-test (RUDICS server connection test) at float deployment (Yes=1/No=0).A full auto-test includes a connection test on the RUDICS server and a GPS fix acquisition. | 2023-05-02 |
| CC00202 | CONFIG_TelemetryEncodeMessage_LOGICAL | Encode the message before transmission (Yes=1/No=0). | 2023-05-02 |
| CC00204 | CONFIG_TelemetryMaxRetrySecondary_COUNT | Some float versions have a secondary telemetry system; in this case the float is able to perform an Iridium session (to get one Iridium position) in addition to the RUDICS version used in the main telemetry session specified by CONFIG_TelemetryMaxRetry_COUNT | 2023-05-02 |
| CC00203 | CONFIG_TelemetryMaxRetry_COUNT | Maximum number of telemetry session retries | 2023-05-02 |
| CC00205 | CONFIG_TelemetryRepeatSessionDelay_minutes | Delay before a second Iridium session performed by the float just before diving for a new cycle (in minutes). | 2023-05-02 |
| CC00206 | CONFIG_TelemetryRetransmission_COUNT | To transmit N Argos messages, the transmission duration of an Argos PROVOR float is : MAX([N*CONFIG_TransmissionRepetitionPeriod_seconds*CONFIG_TelemetryRetransmission_COUNT]/3600, CONFIG_TransmissionMaxTime_hours).So I will use CONFIG_TelemetryRetransmission_COUNT | 2023-05-02 |
| CC00207 | CONFIG_TelemetryRetryInterval_minutes | Amount of time the float waits before trying to retransmit | 2023-05-02 |
| CC00208 | CONFIG_TimeDelayAfterEndOfAscentPressureThreshold_minutes | At the end of the ascent phase, when the float detects a given pressure (Ex: 6 dbar) it waits for this time delay before starting the pump for the final buoyancy acquisition. | 2023-05-02 |
| CC00209 | CONFIG_TimeDelaybeforeDescentRetryWhenStuckAtSurface_minutes | Time delay between each new attempt to descend when the float is stuck at the surface. When the float cannot reach the pressure threshold defined by "CONFIG_BuoyancyReductionFirstThreshold_dbar" after a given number of buoyancy actions it waits a period of time specified by "CONFIG_TimeDelaybeforeDescentRetryWhenStuckAtSurface_minutes" before starting a new sequence of buoyancy actions. | 2023-05-02 |
| CC00210 | CONFIG_TimeDelaybetweenRecoveryMessage_minutes | Delay time between recovery messages in [minutes] | 2023-05-02 |
| CC00211 | CONFIG_TimeStartFirstDescentToStartFirstAscent_hours | Time, in hours, between 1st descent and 1st ascent - period between mission prelude and start of first profile. Phase 0. | 2023-05-02 |
| CC00212 | CONFIG_TransmissionEndCycle_LOGICAL | The float performs a telemetry transmission at the end of the cycle (Yes=1/No=0). | 2023-05-02 |
| CC00213 | CONFIG_TransmissionMaxTimeforRecoveryMessage_minutes | Maximum transmission time for recovery messages in [minutes] | 2023-05-02 |
| CC00214 | CONFIG_TransmissionMinTime_hours | The time the float will remain on the surface transmitting its data at the end of each cycle. At lower latitudes you may wish to increase the value of this parameter to increase the probability of reception of all of your data. | 2023-05-02 |
| CC00215 | CONFIG_TransmissionPeriodEndOfLife_minutes | Period of the Iridium transmission when in End Of Life mode (in minutes). | 2023-05-02 |
| CC00216 | CONFIG_TransmissionRepetitionPeriod_seconds | transmission repetition rate, metadata for most floats - may be variable for two-way communication | 2023-05-02 |
| CC00218 | CONFIG_TriProfileOption_LOGICAL | Profiler configuration - Tri profile option (Yes = 1, No = 0). From the first generation of PROVOR floats for which a number of configurations are allowed, i.e. if tri profile is yes, it indicates a float which performs 1 deep profile followed by two shallower profiles. | 2023-05-02 |
| CC00217 | CONFIG_TripInterval_hours | This is a conversion factor for the up and down times. If it is set to 2, then each 'interval' is equal to 2 hours (or seconds or minutes…) , if it is set to 1, then each 'interval' is equal to 1 unit. | 2023-05-02 |
| CC00219 | CONFIG_UpTime_hours | preset duration of the 'up' time (start of ascent to start of descent) - changed from : CONFIG_UpTimeInterval_hours and CONFIG_UpTimeOut. This parameter is important for trajectory files. | 2023-05-02 |
| CC00220 | CONFIG_ValveActionPeriodFactorBuoyancyReduction_NUMBER | Define the period of valve actions during the second phase of the buoyancy reduction (between CONFIG_BuoyancyReductionFirstThreshold_dbar and CONFIG_BuoyancyReductionSecondThreshold_dbar). The valve is open during CONFIG_ValveTimeActionBuoyancyReduction_csec each CONFIG_ValveTimeActionBuoyancyReduction_csec*CONFIG_ValveActionPeriodFactorBuoyancyReduction_NUMBER. | 2023-05-02 |
| CC00221 | CONFIG_ValveTimeActionBuoyancyReduction_csec | Duration of the valve actions during the second phase of the buoyancy reduction (between CONFIG_BuoyancyReductionFirstThreshold_dbar and CONFIG_BuoyancyReductionSecondThreshold_dbar). | 2023-05-02 |
| CB00044 | CONFIG_VectorBoardShowModeOn_LOGICAL | Is the vector board show mode ON? (Yes/No). | 2023-05-02 |
