Tohban Report 2013-12-04

From RHESSI Wiki

Revision as of 22:24, 4 September 2014 by Lglesener (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Tohban Reports
Start Date: 27 Nov 2013
End Date: 4 Dec 2013
Tohban: Jim McTiernan
Tohban email: jimm@ssl.berkeley.edu
Next Tohban: TBD
List all reports



Contents

Solar Activity

Pretty Quiet. Six AR's on the disk, and 5 rotating off. Far side looks pretty quiet.

How many GOES flares occurred?

 Flares above B, C, M, X class were     11    13     0     0

And how many of these are listed in the RHESSI flare list?

 Flares above B, C, M, X class were      6    10     0     0

And how many had EXCELLENT coverage?

 Flares above B, C, M, X class were      1     2     0     0

There were RHESSI flares/GOES flares 170 / 24 over the time range 26-Nov-13 03-Dec-13

Memory Management

The SSR is empty at the end of each set of daily passes. Decimation was changed from active/vigorous to normal/vigorous on 29-November 2013.

Spacecraft Status

The cold plates, 1 and 2 were at 119.2 and 117.6 K, for the most recent pass, 4-dec-2013 18:17 UT.

Data Gaps

Dropped one app_id 1 packet on 27-Nov, no dropped app_id 102 packets.

Detector issues

Nothing unusual...

Other notes

Multiple ADP resets, here is an email from Mark Lewis:

The timeline below includes the ADP commanding surrounding the errors. These commands are executed out of the ATS at transition times between Day/Night and there is a special short run done at orbital midnight. The timeline and plots show that a read error occurs while a new table is being read and the subsequent /iadprun command does not start the ADP running. Two minutes and ten seconds later the ADP checksum error is reported. During those 2:10 the ADP error counter counts up, and then goes back to zero after the checksum error is reported.

During the three errors which occurred during a midnight run, the new table is loaded and run and then switched back to the nominal Night table entirely within this 2:10 period. The second table read and /iadprun run appear to be ignored. However, the next time a transition occurs, outside the 2:10 time period, it works. The checksum continues to report an error, until we reset the ADP, I believe that is by design. Martin is looking the the VC3 data to see what can be learned.

The adp_ps.pdf plot is particularly interesting, since it shows the iadp_5p2v (ADP EEPROM) power supply misbehaving, since the CPU reset last week. Dave Curtis has been asked to give his opinion the the matter.

Below is Jeremy's detailed sequence of commands sent via the ATS and times TLM goes out of limits for all 4 ADP anomalies so far. In general we have seen 3 anomalies during the midnight run and one during the day run. So they have all happened during eclipse. I include the battery voltage during these anomalies and it isn't unusually low at these times. I have also included the Day and Night RTS definitions at the end.

1st (Midnight) (Battery = 28.7 V)

=====================================

2013 333/00:37:39 512 N IADPSTOP 2013 333/00:37:49 513 N IADPPTER VALUE=12 2013 333/00:37:50 514 N IADPRTER VALUE=5 2013 333/00:37:51 515 N IADPRUN

2013/333 00:38:00 IDPU_ERRCODE=34 2013/333 00:38:00 IADP_STAT_READ=1

2013 333/00:38:51 516 N IADPSTOP 2013 333/00:39:01 517 N IADPPTER VALUE=29 2013 333/00:39:02 518 N IADPRTER VALUE=1 2013 333/00:39:03 519 N IADPRUN

2013/333 00:40:10 IDPU_ERRCODE=35 2013/333 00:40:10 IADP_STAT_READ=0 2013/333 00:40:10 IADP_DSPSVC1=41656


2nd (Day) (Battery = 26.7 V)

=====================================

2013 333/20:00:42 93 N SCRTSSTART RTSNUM=RTS21

2013 333/20:00:42 /IADPSTOP 2013 333/20:00:52 /IADPPTER VALUE=28 2013 333/20:00:53 /IADPRTER VALUE=0 2013 333/20:00:54 /IADPRUN

2013/333 20:01:00 IDPU_ERRCODE=34 2013/333 20:01:00 IADP_STAT_READ=1

2013/333 20:03:10 IDPU_ERRCODE=35 2013/333 20:03:10 IADP_STAT_READ=0 2013/333 20:03:10 IADP_DSPSVC1=41656


3rd (Midnight) (Battery = 28.6 V)

=====================================

2013 334/09:58:11 362 N IADPSTOP 2013 334/09:58:21 363 N IADPPTER VALUE=12 2013 334/09:58:22 364 N IADPRTER VALUE=5 2013 334/09:58:23 365 N IADPRUN

2013/334 09:58:30 IDPU_ERRCODE=34 2013/334 09:58:30 IADP_STAT_READ=1

2013 334/09:59:23 366 N IADPSTOP 2013 334/09:59:33 367 N IADPPTER VALUE=29 2013 334/09:59:34 368 N IADPRTER VALUE=1 2013 334/09:59:35 369 N IADPRUN

2013/334 10:00:40 IDPU_ERRCODE=35 2013/334 10:00:40 IADP_STAT_READ=0 2013/334 10:00:40 IADP_DSPSVC1=41656


4th (Midnight) (Battery = 28.6 V)

=====================================

2013/336 23:53:12 412 N IADPSTOP 2013/336 23:53:22 413 N IADPPTER VALUE=12 2013/336 23:53:23 414 N IADPRTER VALUE=5 2013/336 23:53:24 415 N IADPRUN

2013/336 23:53:40 IADP_STAT_READ=1 2013/336 23:53:40 IDPU_ERRCODE=34

2013/336 23:54:24 416 N IADPSTOP 2013/336 23:54:34 417 N IADPPTER VALUE=29 2013/336 23:54:35 418 N IADPRTER VALUE=1 2013/336 23:54:36 419 N IADPRUN

2013/336 23:55:40 IDPU_ERRCODE=35 2013/336 23:55:40 IADP_STAT_READ=0 2013/336 23:55:40 IADP_DSPSVC1=41656


RTS definitions

=====================================

RTS 20 (Night): 00:00:00 /IADPSTOP 00:00:10 /IADPPTER VALUE=29 00:00:01 /IADPRTER VALUE=1 00:00:01 /IADPRUN

RTS 21 (Day): 00:00:00 /IADPSTOP 00:00:10 /IADPPTER VALUE=28 00:00:01 /IADPRTER VALUE=0 00:00:01 /IADPRUN


Spacecraft Management

Decimation Active/Vigorous, Normal/Vigorous
HLAT Decimation Rear decimation weight 6, no front decimation
Night time data (fronts) +/- 4 minutes
Night time data (rears) Enabled
Require extra passes? No
Requirement for moving pointer? No
Attenuator operation Normal
Detector problems? None
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox