LEO-15 Node Profiler Log

LEO-15 Node Profiler Log

Guidelines: Temperature – if greater than air temperature it should be suspect

if less than ~4C it should be checked

Salinity – if see steady decrease over time sensor probably fouled – this

will not generally be a big jump but a slow decline

deceases could also be caused by heavy rainfall

calculation for this based on temp., conductivity and pressure so if

something looks off check these sensors

values less than 29PSU should be suspect

Pressure – atmospheric pressure is included in this value

Depth – the depth of the profiler, a value of zero means it is either on the surface

or it is not working, values should not exceed the Node Depth

Node Depth – value taken from pressure sensor mounted on the node itself

values should be between approximately 10 and 15 meters, zero means

it is either out of the water or not working

Fluorometer – values above ~15 ug/l should be suspect – check for

phytoplankton blooms

PAR – a value that repeats itself in the next line is suspect

a value of 1.85382E12 means sensor is not working

OBS – good values at LEO usually less than 100, a value of zero means

the sensor is not working, a value of 2000 means the sensor is pegged

at its highest value and data is probably invalid

Oxygen and Transmissometer data – always unreliable due to fouling. Sensors

were removed from the profilers

The observations made below were done when the respective Profiler has "home" on the bottom sitting in its bowl. The true test of when a sensor is fouled or producing poor quality data is during profiling when equilibration speed of a sensor can be monitored. Equilibration should take seconds not minutes.

Nov 8, 1996 Node A recovered, no telemetry from Node B

Dec 9, 1996 Node B Profiler 0153 fluorometry values high, transmissometer probably fouled,

OBS values high when inside bowl between profiles, Oxygen sensor fouled, Node Pressure sensor faulted off

Dec 10, 1996 Node B Profiler 1053 salinity value low – real or fouled?

Jan 13, 1997 Node B Profiler 0153 temperature drop is real – confirmed with AVHRR sea

surface temperatures

Feb 3, 1997 Node B Profiler 0153 temperature sensor failed causing bad salinity and sound

velocity calculations

Feb 4, 1997 Node B Profiler 0153 PAR sensor producing erroneous values

Feb 20, 1997 Node B Profiler 0153 faulted off

Apr 16, 1997 Node B recovered

May 5, 1997 Node A Profiler 0152 deployed, transmissometer no longer installed on profiler,

oxygen values not matching those done by Winkler titration, sensor probably

fouled, OBS values high when Profiler in bowl

Jun 4 1997 Power off to Nodes temporarily due to power glitch at RUMFS

Jun 23, 1997 Node B Profiler 0153 deployed, cover inadvertantly left on PAR sensor,

transmissometer removed from profiler, oxygen values unreliable

Jun 30, 1997 Node B Profiler PAR sensor cover removed

Jul 29, 1997 Node A recovered

Aug 1, 1997 Node B Prolfiler 0153 temperature sensor fouled, equilibration takes 15 minutes,

salinity and sound velocity calculations affected by temperature values,

fluorometer fouled,

Sep 2, 1997 Node B Profiler 0153 OBS sensor possibly fouled or sediment in bowl

Sep 15, 1997 Node B Profiler 0153 recovered

Sep 18, 1997 Node B Profiler 0153 redeployed, transmissometer and oxygen sensors

permanently removed from profiler

Jan 27, 1998 Node B Profiler 0153 fluorometer fouled

Feb 18, 1998 Node B Profiler 0153 PAR sensor fouled

May ?, 1998 Node A Profiler 0152 deployed, salinity both nodes low – may be real

May 18, 1998 Node B recovered

Jul 1998 Node A Profiler 0152 recovered, Spare Profiler deployed

Jul 1998 Node B Profiler 0153 deployed

Jul 25, 1998 Node B Profiler 0153 temperature and salinity low – conductivity and/or

temperature sensor s fouled

Aug 31, 1998 Node B Profiler 0153 fluorometer fouled

Sep 4, 1998 Power off to Nodes while Node B recovered

Sep 21, 1998 Node A Profiler 0152 OBS sensor occasional high values – muddy bowl?

Sep 24, 1998 Node B, Profiler 0153 deployed, Node A Spare Profiler recovered

Sep 28, 1998 Node B Profiler 0153 fluorometer probably fouled

Oct 23, 1998 Node B Profiler 0153 OBS values high

Nov 11, 1998 Node B Profiler 0153 PAR values low – probably fouled

Dec 18, 1998 Node B Profiler 0153 salinity values decreasing – conductivity and/or

temperature sensors fouled, sound velocity calculation suspect

Jan 29, 1999 Node B pressure sensor faulted, turned off

May 27, 1999 Node A deployed, Node B turned off

Jun 4, 1999 Node A turned off while Node B recovered

Jun 7, 1999 Node A Profiler 0152 OBS values high

Jul 14, 1999 Node A Profiler 0152 fluorometer values high – probably fouled

Jul 26, 1999 Node A Profiler 0152 recovered and Spare Profiler deployed

Sep 24, 1999 Node A Spare Profiler fluctuations in salinity – conductivity and/or temperature

sensor probably fouled

Oct 18, 1999 Node A pressure sensor faulted, back on Oct 20, 1999

Nov 17, 1999 Node A pressure sensor faulted, back on Nov 18, 1999

Dec 9, 1999 Node B redeployed with Profiler 0153, fluorometer values high, PAR values low

Jan 20, 2000 Node B faulted off, 240V GFI problem

Mar 6, 2000 Power to Nodes turned off

May 26, 2000 Node B Spare Profiler being deployed

Jun 21, 2000 Node A Profiler 0152 deployed, OBS values look high

Jul 2000 Node B Profiler 0153 deployed, Node A recovered

Aug 15, 2000 Node B Profiler 0152 salinity value steadily dropping, indicating fouling

of temperature and/or conductivity sensors

Sep 8, 2000 Node A recovered

Sep 29, 2000 Node B Profiler 0153 fluorometer probably fouled

Oct 20, 2000 Node A Profiler 0152 deployed

Oct 25, 2000 Node A Profiler 0152 fluorometer probably fouled

Nov 6, 2000 Node A Profiler 0152 OBS not working

Nov 7, 2000 Node A Profiler 0152 OBS working

Nov 13, 2000 Node A Profiler 0152 conductivity sensor probably fouled

Nov 28, 2000 Node A Profiler 0152 PAR sensor probably fouled

Dec 18, 2000 Node A no communication, GFI problems, Node A turned off

Jan 4, 2001 Node B turned off

Jun 4, 2001 Node A deployed, Profiler A (0152)

Jul 2, 2001 Node B deployed, Profiler B (1053)

Jul 12, 2001 Node A fluorometer values high – possibly fouled

Jul 13, 2001 Node B ADCP deployed

Jul 15, 2001 Node B ADCP faulted ~1715z, restarted ~0000z on July 16, 2001

240V and 15V GFI problems seen on node diagnostics

Jul 20, 2001 Node A temperature and conductivity response times slow, sensors fouled,

profiling stopped

Jul 23, 2001 Node A profiler recovered, compared with Scott SBE, cleaned, compared with

Scott SBE

Jul 24, 2001 Node B profiler (0153) recovered, Profiler 0152 deployed at Node B – fluorometry

high, Node A Spare Profiler deployed

Jul 25, 2001 Profiler 0153 compared to Scott SBE before cleaning

Aug 15, 2001 Profiler 0153 cleaned

Aug 16, 2001 Profiler 0153 compared to Scott SBE after cleaning

Aug 29, 2001 Node A Spare Profiler replaced with PCO2 Profiler, Node B Profiler 0152

replaced with Profiler 0153

Sep 4, 2001 Node B ADCP faulted off 15V and 48 V GFI errors

Sep 5, 2001 Node B ADCP cable replaced, running okay

Sep 17, 2001 Node B Profiler 0153 salinity lower than expected

Oct 10, 2001 Node A spare profiler installed, node pressure sensor faulted off no fluorometer

or PAR sensors

Node B profiler 0152 installed, fluorometer reading high probably fouled

Oct 21, 2001 Node B no communication

Nov 15, 2001 Node A spare profiler recovered, PCO₂ profiler installed

Nov 16, 2001 Node B OBS values beginning to climb – bowl probably sediment filled

Dec 4, 2001 Node A PCO₂ profiler recovered, spare profiler installed – no fluorometer or PAR

sensors

Dec 6, 2001 Node B conductivity sensor probably fouled

Jan 16, 2002 Node A spare profiler faulted off

Jan 28, 2002 Node B pressure sensor faulted off

Feb 3, 2002 Node B no data Julian Day 33

Mar 8, 2002 Node A & B no communication briefly

Mar 17, 2002 Node B no data Julian Day 75

Apr 18, 2002 Node B Profiler 0152 recovered, Node B recovered, Node A Spare Profiler

turned back on