Detector 1 anneal 2012
From RHESSI Wiki
(Difference between revisions)
(Added tables of threshold changes (none)) |
|||
| Line 1: | Line 1: | ||
===Notes=== | ===Notes=== | ||
| - | |||
| - | |||
*There was a large spike in D1 on September 2 at ~07:16 UT. | *There was a large spike in D1 on September 2 at ~07:16 UT. | ||
This caused the shutters to engage and the other detectors to spike as well | This caused the shutters to engage and the other detectors to spike as well | ||
| + | * 2014 May 17: | ||
| + | ** G1 rear fast threshold from 0x45 to 0x50 | ||
| + | ** A short and negligible problem arose when it was intended to command detector 4, but used the command for G1, the "/IDPUTABLE[X]" command. The error was caught, and the "bad" threshold setting was only in place for about 3 minutes. Entire commanding sequence is below. | ||
| + | ***14-137-04:04:05 /IDPUDUMPTABL TABLE=DIBTBL1 | ||
| + | ***14-137-04:04:06 /IDPUTABLE1 OFFSET=REARFASTDAC | ||
| + | ***14-137-04:04:24 /IDPULOAD VALUE=0x50 | ||
| + | *** | ||
| + | ***14-137-04:04:30 /IDPUDUMPTABL TABLE=DIBTBL4 | ||
| + | ***14-137-04:04:31 /IDPUTABLE1 OFFSET=REARFASTDAC (the load address was set to G1 not G4) | ||
| + | ***14-137-04:04:39 /IDPULOAD VALUE=0x90 (and this was sent to G1 not G4 as intended) | ||
| + | *** | ||
| + | ***14-137-04:07:38 /IDPUTABLE4 OFFSET=REARFASTDAC | ||
| + | ***14-137-04:07:43 /IDPULOAD VALUE=0x90 (G4 rear fast was set properly) | ||
| + | *** | ||
| + | ***14-137-04:07:51 /IDPUTABLE1 OFFSET=REARFASTDAC | ||
| + | ***14-137-04:07:58 /IDPULOAD VALUE=0x50 (G1 rear fast was returned to 0x50) | ||
| + | *** | ||
| + | ***14-137-04:08:02 /IDPUDUMPTABL TABLE=DIBTBL1 | ||
===D1 front slow LLD threshold history=== | ===D1 front slow LLD threshold history=== | ||
| Line 29: | Line 45: | ||
|- | |- | ||
| post 2012 anneal || 0x45 | | post 2012 anneal || 0x45 | ||
| + | |- | ||
| + | | 2014-May-17 04:03:25 UTC || 0x50 (was 0x45) | ||
|} | |} | ||
Revision as of 00:06, 21 May 2014
Contents |
Notes
- There was a large spike in D1 on September 2 at ~07:16 UT.
This caused the shutters to engage and the other detectors to spike as well
- 2014 May 17:
- G1 rear fast threshold from 0x45 to 0x50
- A short and negligible problem arose when it was intended to command detector 4, but used the command for G1, the "/IDPUTABLE[X]" command. The error was caught, and the "bad" threshold setting was only in place for about 3 minutes. Entire commanding sequence is below.
- 14-137-04:04:05 /IDPUDUMPTABL TABLE=DIBTBL1
- 14-137-04:04:06 /IDPUTABLE1 OFFSET=REARFASTDAC
- 14-137-04:04:24 /IDPULOAD VALUE=0x50
- 14-137-04:04:30 /IDPUDUMPTABL TABLE=DIBTBL4
- 14-137-04:04:31 /IDPUTABLE1 OFFSET=REARFASTDAC (the load address was set to G1 not G4)
- 14-137-04:04:39 /IDPULOAD VALUE=0x90 (and this was sent to G1 not G4 as intended)
- 14-137-04:07:38 /IDPUTABLE4 OFFSET=REARFASTDAC
- 14-137-04:07:43 /IDPULOAD VALUE=0x90 (G4 rear fast was set properly)
- 14-137-04:07:51 /IDPUTABLE1 OFFSET=REARFASTDAC
- 14-137-04:07:58 /IDPULOAD VALUE=0x50 (G1 rear fast was returned to 0x50)
- 14-137-04:08:02 /IDPUDUMPTABL TABLE=DIBTBL1
D1 front slow LLD threshold history
| post 2012 anneal | 0x0C |
D1 front fast LLD threshold history
| post 2012 anneal | 0x22 |
D1 rear slow LLD threshold history
| post 2012 anneal | 0x30 |
D1 rear fast LLD threshold history
| post 2012 anneal | 0x45 |
| 2014-May-17 04:03:25 UTC | 0x50 (was 0x45) |
