Glider Project Deployed Recovered Days Distance Start/
End Voltage
Air Time POC Notes Payload KMZs Data Metadata
bios_minnie-529 BIOS 2017-12-12
14:22 GMT
2018-02-26
19:24 GMT
76.21 281.8
km
11.07 Volts
10.92 Volts
2656
minutes
Curry
Aragon
Williams
14 ? kmzs

deployment Notes (14)  

Select Category: Deployment Glider All

Posted/
Updated
Category
2018-03-01 13:53 GMT
dkaragon
deployment Recovered by the AE. Don't think the SUNA was resuscitable even after trying to nueter the lamp settings.
Feb 26 19:24:28
2018-02-27 14:12 GMT
anything
deployment Recovered by AE 26-Feb-2018
2018-02-24 11:41 GMT
anything
deployment Tested the power usage as suggested by Darrell, and confirmed lamp failure:

Lamp power initially : 6623.829102
SUNA> selftest
System time , 2018-02-23T14:51:42Z
Temperatures Hs Sp Lm , 20.8 20.2 20.8
Humidity , 0.2
Electrical Mn Bd Pr C , 10.8 11.9 5.0 12.9
[2018/02/23 14:51:55] turn_dark2light()::ERROR-UV lamp malfunction
[2018/02/23 14:51:55] turn_dark2light()::ERROR-Lamp PowerUp Failed
Lamp or spec error , 20!
$Error: 1

SUNA>special setlamppower 3000
SUNA> selftest
System time , 2018-02-23T14:52:49Z
Temperatures Hs Sp Lm , 20.9 20.4 20.9
Humidity , 0.0
Electrical Mn Bd Pr C , 10.5 11.9 5.0 16.4
Lamp Power , 2700 mW
Spec Dark av sd mi ma , 700 (+/- 9) [ 665: 721]
Spec Lght av sd mi ma , 677 (+/- 15) [ 656: 700]!
Spec Integration Time , 300 ms
$Error: 1
2018-02-23 14:30 GMT
dkaragon
deployment After drilling down into the SUNA manual (SUNA170517-Rev-D, Section 4.1.1.1, Table 3), I discovered that one of the output units for the SUNA quoted in masterdata is not quite correct.
sci_suna_nitrate_mg : this is actually the mass of Nitrogen (not nitrate) in mg/L

It’s important because the proglet in software release v 8.0 logs this sensor (and not the preferred sci_suna_nitrate_um), so the conversion factor from sci_suna_nitrate_mg to sci_suna_nitrate_um has to reflect the molar mass of nitrogen, NOT nitrate.

This was ambiguous in the earlier section 1.4 of the suna manual, so I completely understand how it got confused.

Just wanted to clarify for future reference.
2018-02-12 17:53 GMT
dkaragon
deployment SEABIRD reply:

Hi Ruth,

Thank You for your email ! Sorry to hear about this problem.

Indeed it appears to be a failure to turn on the lamp. It is most likely the lamp is failing to illuminate and SUNA does not see the expected power use and ceases to keep trying to turn it on.

But I am not aware of very many premature lamp failures in V2 SUNAs.

However as a last ditch effort, it appears you are able to get a connection to the SUNA, so we could try something if you are interested...

For some understanding of the operation: When SUNA is first built, there is an entry made in the memory which contains the expected power usage of the lamp installed.

The SUNA expects to see this power use to determine whether or not the lamp is turning on. The firmware allows for some possible decrease in power usage of the lamp over time. I believe firmware allows a decrease to 75% of original value.

What if the SUNA's lamp power is lower than original ? It might be that the lamp is actually on, but fell below the threshold.
It could also be that the power is way lower and the lamp is indeed not illuminating - but you could alter the "hidden" threshold value fairly easily to explore this.

When you have a serial connection to the SUNA, enter the command "special getlamppower"

SUNA should respond with something like: Lamp power: 5901.958008

(Make note of this value as you might want to switch it back to original later)

You could program this value to ~ half of original.

Example: Enter the command "special setlamppower 3000"

You can then do "special getlamppower" again to ensure value is retained.

And follow up with a selftest again.

Note: If it works and the lamp is actually illuminating, the time the SUNA will take to ensure the lamp is warmed up will change slightly. I don't see this as being a problem through.


Other: Seeing the SUNA reports Voltage supplied to it from the glider, and also Current (Amps) used in its data frame, in principle one could calculate the power usage over time. It should be possible to see if the SUNA is indeed using less power over timeframe (year perhaps) and you could assume the lamp has changed its power usage as it is the major component of power use in the SUNA.

Please let me know if you have any questions or comments.

Kind Regards,
Darrell
2018-02-12 17:52 GMT
dkaragon
deployment More notes to go with the SUNA problems:



SUNA> selftest

System time , 2018-02-01T16:28:46Z

Extrn Disk Size; Free , 3954802688; 3492511744

Intrn Disk Size; Free , 2043904; 1688576

Fiberlite Odometer , 0393:35:11

Temperatures Hs Sp Lm , 21.4 21.2 21.6

Humidity , 0.0

Electrical Mn Bd Pr C , 11.0 11.9 5.0 16.5

[2018/02/01 16:28:59] turn_dark2light()::ERROR-UV lamp malfunction

[2018/02/01 16:28:59] turn_dark2light()::ERROR-Lamp PowerUp Failed

Lamp or spec error , 20!

$Error: 1

SUNA> sleep

$Error: 5

SUNA> slp

$Error: 5

SUNA>
Heard exit char, Leaving emulation_loop()
sci_uart_close(4): Closing SBMB:J4
Restoring bit[s] to initial state.
Lowering bit: 0
Bit(0) raise count is now 0.
bit_shared_close(): bit(0) is still in use.
Bit(0) use count is now 1.
return 0; from main()
----------------------------------------------------------------------


SciDos>u4stalk 4 38400 0
U4STALK: Program Version 1.1
Version 8.0 2017-9
Using uart port 4 at 38400 baud
Raising a total of 1 bit(s):
0
----------------------------------------------------------------------
Opening port 4:SBMB:J4
38400 baud, N81, line buf: 0, no input data timeout(secs): disabled
in queue size: 204800, out queue size: 2048
sci_uart_drain_input(4):

sci_uart_drain_input:Drained 0 chars
bit_shared_open(): bit(0) is already open.
Bit(0) use count is now 2.
bit_shared_raise(): Raising bit(0).
All the setup is done. Beginning emulation....
To exit this program:
Drop Carrier Detect for 3 seconds (i.e. unpower freewave)
--or--Type Ctrl-C and hit NO keys for 1 secs.
----------------------------------------------------------------------
�8�[2018/02/01 16:31:04] vMainNitrateTask()::INFO-Start SUNA SN:0642 V2, FW 2.5.1

[2018/02/01 16:31:04] vMainNitrateTask()::INFO-Reset from power cycling, sv default wakeup



CMD?measure 1

SATSDR0642 ��@0�Dm9� � �������������������������������� = Kq �� �� �� �[2018/02/01 16:31:25] turn_dark2light()::ERROR-UV lamp malfunction

[2018/02/01 16:31:25] turn_dark2light()::ERROR-Lamp PowerUp Failed

[2018/02/01 16:31:25] measure_Polled()::ERROR-Data Acquisition Failed.



CMD?



CMD?status

SATMSG,SUNA,0642,1416911,0.0,11.0,21.8,21.5

CMD?measure 0

SATSDR0642 ��@0���`6 � ��������������������������������A� A�� �� �� �� �

CMD?that was a dark frame, that went ok, nothing light seems to be



CMD?measure 2

SATSDR0642 ��@0��M�� � ��������������������������������A�� A� �� �� �� �[2018/02/01 16:32:42] turn_dark2light()::ERROR-UV lamp malfunction

[2018/02/01 16:32:42] turn_dark2light()::ERROR-Lamp PowerUp Failed

[2018/02/01 16:32:42] measure_Polled()::ERROR-Data Acquisition Failed.
2018-02-01 16:48 GMT
dkaragon
deployment SUNA> selftest

System time , 2018-02-01T16:23:20Z

Extrn Disk Size; Free , 3954802688; 3492511744

Intrn Disk Size; Free , 2043904; 1688576

Fiberlite Odometer , 0393:35:11

Temperatures Hs Sp Lm , 21.2 21.1 21.4

Humidity , 0.1

Electrical Mn Bd Pr C , 10.6 11.9 5.1 17.2

[2018/02/01 16:23:32] turn_dark2light()::ERROR-UV lamp malfunction

[2018/02/01 16:23:32] turn_dark2light()::ERROR-Lamp PowerUp Failed

Lamp or spec error , 20!




SENSTYPE SUNA

SENSVERS V2

SERIALNO 642

THEBRAND Satlantic

PATHLGTH 10mm

INTWIPER Missing

EXTPPORT Missing

SUPRCAPS Missing

PWRSVISR Available

USBSWTCH Available

RELAYBRD Missing

SDI12BRD Missing

ANALGBRD Missing

INTDATLG Available

APFIFACE Missing

SCHDLING Available

OWIRETLP 10aae6e7020800d8

OWIRETSP 104a8ffb02080039

OWIRETHS 10885f08030800c4

ZSPEC_SN 96702

FIBERLSN C6.D01.2423

CUSTOMID none

STUPSTUS Done

BAUDRATE 38400

MSGLEVEL Info

MSGFSIZE 2

DATFSIZE 5

OUTFRTYP Reduced_Binary

LOGFRTYP Reduced_Binary

OUTDRKFR Output

LOGDRKFR Output

LOGFTYPE Acquisition

AFILEDUR 60

ACQCOUNT 1941

CNTCOUNT 0

DCMINNO3 -5.000

DCMAXNO3 100.000

WDAT_LOW 217.00

WDAT_HGH 250.00

SDI12ADD 48

DATAMODE Real

OPERMODE Polled

OPERCTRL Samples

EXDEVTYP None

EXDEVPRE 0

EXDEVRUN Off

EXDVIVAL 0

COUNTDWN 15

FIXDDURA 60

PERDIVAL 1h

PERDOFFS 0

PERDDURA 5

PERDSMPL 5

POLLTOUT 0

APFATOFF 10.0000

STBLTIME 5

SKPSLEEP On

LAMPTOFF 35

SPINTPER 300

DRKAVERS 1

LGTAVERS 1

DRKSMPLS 1

LGTSMPLS 10

DRKDURAT 2

LGTDURAT 58

TEMPCOMP Off

SALINFIT On

BRMTRACE Off

BL_ORDER 1

FITCONCS 3

DRKCORMT SpecAverage

A_CUTOFF 1.3000

INTPRADJ On

INTPRFAC 1

INTADSTP 20

INTADMAX 20

WFIT_LOW 217.00

WFIT_HGH 240.00

LAMPTIME 1416911




CMD?measure 1

SATSDR0642
2018-02-01 16:38 GMT
dkaragon
deployment from SUNACOM manual:
3. Cumulative lamp run time.
The total expected life time of the lamp is 900 hours.

Minnie currently has 1416911 seconds = 394 hours
2018-01-22 21:50 GMT
anything
deployment Reverted suna.ini file to original params LIGHT_FRAMES_PER_SAMPLE = 1, which was used for first 30 days of mission.

Since trying 4 frames/sample, the sensor has undergone several shifts, sometimes mid-profile, and changes in drift rate. Hoping to return sensor to stable performance
2018-01-21 11:07 GMT
anything
deployment 13 Jan: increased LIGHT_FRAMES_PER_SAMPLE from 1 to 4 and MAX_FRAMES_WAIT_TIME to 15s. Power consumption increased from 6.5 amphr/day to ~8.8 ah/day

SUNA drift rate also increased by a factor 2.5
2017-12-18 02:02 GMT
anything
deployment Double yos, 950m
CTD on dive/climbs
Optode,flbbcd on dives
Suna on climbs

2017-12-17 11:35 GMT
anything
deployment Increased MAX_ALL_FRAMES_WAIT_SEC to 10 in suna.ini to eliminate science super errors

2017-12-12 22:57 GMT
dkaragon
deployment Deployed by AE.

Anna deployment aborted due to autoexec.mi transfer issue.
2017-12-12 22:55 GMT
dkaragon
configuration OS 8.0

CTD 9423
FLBBCD 4784
OPTODE 541
SUNA 642