From: IN%"lhuber@nmsu.edu" 3-DEC-1998 22:02:51.37 To: IN%"SIMMONS@pisces.colorado.edu" CC: Subj: RE: Updated EUV Instrument template Karen, I have reviewed and ingested your changes to EUVINST.CAT. For reference, here is the latest version as I have it. Perhaps you could work off this version for future updates. Lyle ---------- X-Sun-Data-Type: default X-Sun-Data-Name: euvinst.cat X-Sun-Charset: us-ascii X-Sun-Content-Lines: 797 PDS_VERSION_ID = PDS3 LABEL_REVISION_NOTE = "Karen Simmons, June 1998; September 1998; November 1998" RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 80 OBJECT = INSTRUMENT INSTRUMENT_HOST_ID = GLL INSTRUMENT_ID = EUV OBJECT = INSTRUMENT_INFORMATION INSTRUMENT_NAME = "EXTREME ULTRAVIOLET SPECTROMETER" INSTRUMENT_TYPE = "EXTREME ULTRAVIOLET SPECTROMETER" INSTRUMENT_DESC = " Instrument Information ====================== Instrument Id : EUV Instrument Host Id : GLL Instrument Name : EXTREME ULTRAVIOLET SPECTROMETER Instrument Type : EXTREME ULTRAVIOLET SPECTROMETER Instrument Description ====================== The Galileo Ultraviolet Spectrometer investigation uses data obtained by two instruments. The Ultraviolet Spectrometer (UVS) covers the wavelength range from 113 to 432 nm and was the original instrument selected for the Galileo Orbiter. The Extreme Ultraviolet Spectrometer (EUV) was added to the Orbiter payload after the Challenger accident in 1986. The EUV instrument is described in this document; the UVS instrument is discussed in a separate document. The Galileo EUV instrument is an objective grating spectrograph covering the wavelength range from 54-128 nm in 128 contiguous intervals of 0.59 nm. The EUV instrument consists of the flight spare Voyager Ultraviolet Spectrograph [BROADFOOT_ETAL_1977] and an electrical interface to adapt it to the Galileo command and data bus. The instrument has been modified from its Voyager configuration to increase its field of view in the dispersion direction by 70%, and the grating has been changed to increase the dispersion by 40%. The EUV instrument components are summarized in Table 1. TABLE 1 Summary of Galileo EUV characteristics ----------------------------------------------------------------- Location EUV instrument Spinning section, Bay 4 Logic module Spinning section, Bay 5 Field of view Orientation Perpendicular to spin axis Long axis of slit parallel to spin axis Size 0.17 deg (dispersion direction) 0.86 deg (cross-dispersion direction) Optical configuration Objective grating spectrograph with mechanical grille collimator Detector Microchannel plates & self-scanned anode array 128 channels scanned at 3125 Hz Grating Holographically fabricated 842 lines / mm iridium coated Dispersion 0.59 nm / channel Wavelength range 54 - 128 nm Aperture 40 x 60 mm Spectral half-width 3.5 nm Minimum integration time 20.8 ms (see Operational Considerations note) Best spatial resolution 0.36 deg Instrument EUV mass 10.46 kg Logic module mass 2.3 kg Total mass 12.76 kg Power consumption 5.85 W Instrument Optics ================= An objective grating spectrograph is used for observations of point sources. An open, or reflective, optical system is required for wavelengths less than 104 nm, the shortest wavelength transmitted by a refractive material. The low reflective efficiencies at these wavelengths, except at grazing incidence, limit an instrument intended for the study of weak emissions to a single reflection. We have adapted the objective grating design to observe extended sources by restricting the field of view in the dispersion direction. The field is restricted by a series of mechanical stops, a collimator, controlling the angle at which the grating is illuminated. The combination of grating and collimator has the properties described by [HALE&WADSWORTH_1896] and [BEUTLER_1945]. The collimator is designed to induce negligible Fresnel diffraction, but the mechanical structure causes a loss of about 2/3 in effective aperture; scattering from the edges of the aperture plates complicates the analysis of the spectrum to some extent. In this instrument, separation of spectral features from the scattering background is straightforward. The collimator restricts the field of view in the dispersion direction to 0.17 degrees FWHM, but is essentially open in the cross-dispersion direction; the field of view in this long direction is defined by the angular width of the detector in the image plane and is about 0.87 degrees. The 40 x 60 nm diffraction grating has a spherical radius curvature of 400.1 mm. The grating was fabricated holographically, and included corrections to flatten the field at the image plane. The surface was coated with iridium to enhance the EUV reflectivity. The dispersion required to match the desired wavelength range to the length of the detector is 5.9 nm / mm, yielding a ruling density of 851 lines / mm. The instrument has two distinctly different spatial and spectral resolutions depending on the nature of the source. (1) An extended line emission source, filling the field of view of the instrument, produces a triangular intensity distribution in the image plane 0.17 degrees in half- width; this corresponds to a spectral half-width of 3.5 nm. (2) A point source is accurately imaged in the image plane and the width of a detector element, 0.029 degrees, determines both the spectral and spatial resolutions. Both spatial and spectral resolution may be improved to some extent through spectral analysis. Instrument Detector =================== The photon-counting detector uses a 128-element, linear, self-scanned anode array to collect the output of a dual microchannel plate (MCP) electron multiplier. This detector was developed for the Voyager instrument [BROADFOOT&SANDEL1977]. The 128 narrow aluminum anodes, each 3 mm long, are deposited on 0.1 mm centers for a total collecting length of 13 mm in the dispersion direction. The specially designed 18 mm diameter MCPs have a rectangular active area corresponding to the collecting area of the anode array. Photons diffracted by the grating to the detector eject photoelectrons from the MCP. These photoelectrons undergo about 10E6 amplification through the cascaded microchannel plates. The pulse of electrons falls on the self-scanned anode array where the charge is stored. The anodes are accessed sequentially by a shift register and Field Effect Transistor (FET) switches contained in the single integrated circuit. The scanning circuitry discharges each anode into a charge sensitive amplifier. If the charge pulse exceeds a fixed threshold, the memory location corresponding to the anode is incremented. The access time is 320 ms per anode; therefore, single random photo events can be recorded on any one of the 128 anodes with a rate of about 300 per second on each anode with a coincidence loss of about 10% of the events; such a loss can be corrected statistically. This is a satisfactorily high rate for the emissions from Jupiter and the plasma torus. Instrument Microprocessor and Electronics ========================================= The EUV uses an RCA 1802 CMOS microprocessor for command parsing spacecraft time and sector recognition and synchronization, and instrument control. The microprocessor and support logic, the bus adaptor, and the DMA logic are identical to that for the UVS. New designs were required for a 4 kbyte Random Access Memory (RAM) and a simulator for the Flight Data System (FDS) from the Voyager spacecraft. The simulator allowed us to transform the data from the EUV channel to the Galileo spacecraft without modifying the original Voyager-style hardware. The EUV Microprocessor Logic differs from the UVS in two ways: (1) there is no Cold Start Mode, and (2) the microprocessor is responsible for data buffering, formatting, and transmission from the EUV channel Spectrometer to the Galileo Command and Data System (CDS). It receives commands, and spacecraft timing and sector information via the Bus Adaptor and associated Direct Memory Access (DMA) logic. The DMA logic also handles the function of loading and verifying program memory, and of reading out telemetry data from the microprocessor telemetry data buffer. The FDS Simulator performs all interface tasks to simulate the Voyager FDS, including gated clocks, discrete I/O, and serial-to-parallel conversion of the two EUV channel data lines. This logic also contains the handshaking circuitry necessary to achieve 20.8 ms integration periods (see Operational Considerations). The Bus Adaptor serves as the bi-directional interface between the Galileo spacecraft and the EUV. The spacecraft bus is defined to contain four signals. These include a 806.4 kHz clock, the Real Time Interrupt (RTI) timing signal, and one line for serial communications in both directions. The bus adaptor circuitry electrically isolates the EUV from the spacecraft, and allows for 8-bit information flow to and from the EUV. Data Handling And Spacecraft Interface ====================================== To ease the adaptation of the Voyager instrument to the Galileo spacecraft, changes to the spectrograph enclosure were minimized, and an external logic box was constructed to interface the EUV spectrograph and electronics to the Galileo bus. This design restricts the rate at which the spectrum can be read from the EUV memory to 20.8 ms. During this time the spacecraft rotates by 0.37 degrees, which defines the spatial resolution in the roll (dispersion) direction. See Operational Considerations for updates to these parameters. Because of its late addition to the spacecraft the EUV instrument shares a telemetry channel with the Heavy Ion Counter (HIC). A procedure was implemented in the logic box that time-tags detected photons as the information is read from the memory in the spectrograph enclosure. The procedure is based on the concept of a sector. A sector is a time corresponding to a programmable number of 20.8 ms intervals, or equivalently, a number of 0.37 degree sections of the band swept out on the sky by the EUV field of view. See Operational Considerations for updates to these parameters. For encounter operations, this number is usually 1 to give the best available spatial resolution, but for cruise observations it may be much larger. The crossing of sector boundaries is marked in the telemetry stream by a unique byte. Between sector boundaries, the wavelength position of each photo event recorded in the spectrograph memory is telemetered. Synchronizing the sector boundaries with spacecraft roll phase then permits reconstruction, on the ground, of the wavelength and sector of origin of each detected photon. To remain within the allocated telemetry rate during encounter operations, it is necessary to restrict processing of data to that portion of the roll when Jupiter and the plasma torus are in the EUV field of view. Two additional data buffers were used during pre-Jupiter encounter mode operations. The first of these, called the wavelength buffer, is a 128- element buffer that accumulates the spectrum over all sectors. The second, the sector buffer, has an element corresponding to each of the sectors and sums all photo events detected in a particular sector into the appropriate element. Thus data in the wavelength buffer represent the spectrum averaged over all sectors, and data in the sector buffer represent the spatial variation in the intensity summed over the passband of the EUV instrument. Cruise observations consisted mainly of mapping He 58.4 nm and H Lyman-alpha emissions from the local interstellar medium. For these investigations, data were recorded over the full range of roll phase. High spatial resolution was less important than for encounters. Science Objectives ================== The scientific objectives of the Galileo Extreme Ultraviolet Spectrometer (EUV) investigation include the following: (1) INTERPLANETARY MEDIUM: The interplanetary medium is supplied with atoms of hydrogen and helium by the interstellar wind (ISW). Both species are detectable by the EUV through their resonance scattering of solar photons at 121.6 (Lyman-alpha) and 58.4 nm [THOMAS1978]. Gravitational focusing by the Sun produces a cone of enhanced helium abundance downwind from the Sun: the density and shape of this cone reflects the velocity distribution of atoms in the ISW. By contrast, a cavity in the hydrogen medium is created by charge exchange with solar wind protons, and the atoms of hydrogen experience a repulsion due to radiation pressure that is comparable to solar gravity. The size and shape of the cavity depends on variables such as the solar wind, Lyman-alpha and EUV fluxes (all of which vary with solar longitude and latitude), as well as the characteristics of the ISW itself. Processes occurring at the heliopause may also affect the cavity. By carrying out a systematic program of H and He measurements over the course of the mission, EUV enhances our knowledge of the ISW and of the processes that affect its passage through the solar system. (2) VENUS: While the UV spectrum has been extensively studied, very little is known about the EUV spectrum of Venus. EUV measured the disc-integrated intensity of He 58.4 nm, O+ 83.4 nm, O 98.9 nm, and H 102.6 and 121.6 nm features. This was the best EUV spectrum of Venus to date. These emissions are produced in the upper thermosphere by a variety of processes [HORD_ETAL_1991]. (3) EARTH AND MOON: EUV measurements of the Earth's upper atmosphere on the Earth 1 and Earth 2 flybys found the spectrum to be similar to that of Venus (at 3.5 nm resolution). Following the Earth 2 flyby, the EUV mapped the radial falloff of the Earth's geocoronal Lyman-alpha intensity. Combined with the UVS measurements of the Earth's geotail, these observations provide important constraints on geocoronal processes. (4) STARS: Stellar observations provide EUV calibrations. A joint experiment with the Voyager UVS showed that the calibration star, alpha Eridani, is variable. (5) COMETS: The EUV successfully measured Lyman-alpha emissions from Comet Levy and Comet Tsuchiya-Kiuchi. No other EUV emissions were obvious. (6) ASTEROIDS: The EUV experiment is not particularly suitable for observing asteroids, since it is not mounted on the scan platform and the flybys occurred too quickly. The EUV was not operating during the Ida encounter. EUV did observe the region around Gaspra, but there was no obvious detection of the asteroid itself. (7) JOVIAN THERMOSPHERE: The thermosphere of Jupiter is characterized by unexpectedly high temperatures (of order 1100 K in the upper thermosphere) and by unexpectedly bright UV emissions from molecular hydrogen. Lyman-alpha emission from H shows an equatorial bulge that sometimes extends across the morning terminator. None of these phenomena are well understood. Diffuse fluxes of soft electrons have been proposed (the 'electroglow' concept) but the existence, the energy, source, and the need for such electrons all remain controversial [CLARKEETAL1989A]. The ionospheric electron density profiles measured by radio occultation techniques from the Pioneer and Voyager spacecraft are also poorly understood [ESHLEMANETAL1979]. Emission, heating, and ionization are slightly linked processes, and a careful study of spectral, horizontal, vertical, and diurnal and other time variations is an important objective for the Galileo UVS and EUV experiments. (8) JOVIAN AURORA: The Jovian aurora have been observed at X-ray, EUV, UV, and IR wavelengths [CLARKEETAL1989A]. There is considerable uncertainty about the nature of the primary particles, and indeed there may be several different types of aurora, produced by the precipitation of energetic electrons, protons, and heavy ions (oxygen and sulfur from the Io torus). In the UV, the dominant emissions are H Lyman-alpha and the Werner and Lyman bands of H2. The spectrum of H2 bands clearly show the effects of absorption by acetylene, indicating that the primary particles penetrate at least as deep as the homopause [GLADSTONE&SKINNER1989]. The Lyman-alpha emission shows none of the Doppler-shifted component to be expected from precipitating protons or hydrogen atoms [CLARKEETAL1989B]. The X-rays may be bremsstrahlung or emissions from torus ions [METZGERETAL1983]. The IR emissions are attributed to CH4, C2H2, and other trace gases; they indicate enhanced temperatures in auroral 'hot spots'. These hot spots are located on the traditional 'auroral zone' lying at the feet of magnetotail field lines, whereas the UV and EUV emissions are observed at the feet of lines intersecting the Io torus. In both cases the emissions are preferentially seen near 180 degrees System III longitude. In the southern hemisphere, there is a broader clumping of UV emissions around 0 degrees longitude. Galileo's mostly equatorial orbits mean that the aurora will be observed near the northern or southern limbs, allowing excellent longitudinal resolution at the cost of lesser latitude resolution. The spectral effects of atmospheric absorption will be enhanced. Jupiter's rapid rotation will facilitate the determination of longitudinal dependencies of the emissions on each orbit. The possibility of correlations between the aurora and conditions in the Io torus will be explored. (9) SATELLITES: The Galileo EUV will measure the EUV reflectivity of Callisto's surface. (10) IO TORUS: The torus of Io is produced by the ejection of material from Io, its subsequent ionization mostly by charged particle bombardment, and the pickup of the resultant ions by the rotating magnetic field of Jupiter [STROBEL1989]. Prior to ionization, the neutral material leaving Io forms a 'neutral cloud' under the influences of Jovian gravity and, for some species, radiation pressure. Conditions in the torus thus reflect the surface and atmospheric composition of Io and the nature and efficiency of the escape and ionization processes, as well as the complex interaction of the ionized material with the magnetic and gravitational fields of Jupiter and with the rest of the magnetosphere. Information on these materials and processes can be gained by measuring the abundance and distribution of the neutral and ionized species. The EUV instrument will perform this task for the ionized states of sulfur and oxygen. The UV instrument will measure neutral sulfur and oxygen. The relative abundances of the neutral and ionized states of these gases reflect local plasma density and especially the electron temperature. The EUV will observe the torus on inbound orbital legs, for a period equal to several Jovian rotations and comparable to a revolution of Io; thus the data will reveal many dynamical aspects of the torus in addition to its composition. Spatial resolution will be best at the sunward ansa, which will be viewed from about 20 Jovian radii (Rj) on the early orbits. The absolute brightness of the emissions, especially those from ionized sulfur and oxygen in the EUV are of great importance because the emissions are a major cooling process for the heated torus plasma, whose energy balance is not fully understood [STROBEL1989]. The range of variability in torus conditions with time is also inadequately explored: the combination of an approximately two-year timebase and high spatial resolution offered by Galileo will be invaluable. (11) MAGNETOSPHERE: There are many processes in the exosphere of Jupiter, on the constantly irradiated satellites, in the Io torus, and in the magnetosphere in general, that might provide sources of neutral atoms in the magnetosphere. We might expect to find hydrogen in addition to oxygen and sulfur. The EUV instrument will search for such material at times when the radiation noise in the instrument is at a minimum. (12) JOINT INVESTIGATIONS: Collaborative studies are planned with the fields and particles investigators. Our goal is to improve our understanding of the transportation of sulfur and oxygen ions from the Io plasma torus to their ultimate precipitation in the Jupiter auroral region. The in-situ particle measurements will describe the ion and electron populations in the Io torus. Ultraviolet emissions from torus ions, and possibly neutrals, in the 55-430 nanometer range provide temperature, radiative energy loss, and compositional information that will help constrain physical conditions of the torus. In-situ measurements of the torus can only be made on the two passages of the spacecraft through the torus region. EUV and UVS will obtain torus data on every orbit of Jupiter, extending and measuring variability over the full length of the mission. Ultraviolet measurements of auroral emissions from atomic and molecular hydrogen will depend on the knowledge of the quantity and energy distribution of electrons impacting the upper atmosphere of Jupiter. Operational Considerations ========================== Inflight calibration suggests an EUV detector read-out time interval of 21.4 ms. For a spacecraft spin rate of 3.15 rpm, this detector read-out time interval yields a spatial sector size of 0.404 deg. The EUV instrument has operated nominally since launch. Calibration Description ======================= The Galileo EUV instrument was calibrated on the ground before flight. Several documents and data files exist. Inflight calibrations were also obtained. The Principal Investigator requests that, until the end of the Galileo mission (EOM), any data users who wish calibration information beyond that provided in the literature should contact the team. Calibration documents include these references: 1. Galileo EUV Functional Requirement Document [GLL-625-205], 4-2024, Rev A. 2. 'Galileo UVS Calibration Report, Preliminary Version', McClintock, W., March 1989, Internal UVS Team document 3. UVS/EUV instrument paper, [HORD_ETAL_1992], 'Galileo Ultraviolet Spectrometer Experiment', Space Science Reviews, 60: 503-530, 1992. 4. Galileo-EUV Voyager-UVS Cross Calibration, preliminary draft, Sandel, B.R., et al, June 1993, Internal UVS Team document Pre-flight EUV calibrations were performed at the Lunar and Planetary Laboratory (LPL) in Tucson and at LASP in Colorado. These included: instrument absolute sensitivity, telescope off-axis light rejection, spectrometer scattered light, field of view size and spectral line shape and wavelength scale. Spacecraft interface measurements were made during spacecraft matting. These included the alignment of the UVS optic axis. Other calibrations included component calibration, such as the detector timing response and sensitivity. Inflight calibrations include: a) cross-calibration activities between the UVS and EUV instruments during the Lyman-alpha All Sky mapping, b) Earth 1 and Earth 2 cross-calibration (X-cal), and c) several boresight observations by the platform instruments during the cruise, Earth 1 and Earth 2 periods involving several stars. One X-cal between the Galileo UVS, Galileo EUV and the Voyager 2 UVS was performed [SANDELETAL1993]. Two EUV star calibrations are currently planned during the Orbital period. Calibration stars are Kappa Vel and Alpha Eri. During All-Sky cruise observations, several other stars and comets have been detected. Calibration Data ================ The flight instrument wavelength scale was defined from the laboratory calibration measurements at LPL. The following email describes the result. Several publications in the PDS archived list of UVS/EUV publications describe the use of the wavelength and sensitivity calibrations. Specific publications are also noted in the data_set label. From: LOONEY::SANDEL 27-NOV-1990 17:22:38.38 To: ZODIAC::PRYOR, SANDEL CC: Subj: EUV sensitivity et al. Wayne, I think that a linear wavelength scale is fine. I have been using a scale that puts He 584 in channel 5.81 and H Ly alpha in 112.70. This gives wavelength (A) = 549.63 + 5.913*channel or channel = -92.96 + 0.169125*wavelength (A). The numbers that went into the sensitivity curve in the instrument paper follow: wvlgnth sens sigma 58.4 39.3 6.9 wavelength in nm 62.6 40.6 15. sens in count/sec/kR 67.8 34.1 5.5 sigma in count/sec/kR 74.0 32.8 8.0 82.7 30.6 9.0 90.6 26.6 4.6 102.5 18.2 3.2 104.8 13.8 2.4 110.7 8.04 1.3 116.0 4.49 0.72 121.6 3.78 0.64 58.4 38.8 6.8 88.7 27.5 5.0 92.4 26.0 4.9 96.4 18.2 3.6 103.0 17.3 3.0 106.0 10.5 1.8 121.6 3.35 0.56 Instrument Modes ================ For the 1989 launch Galileo used a Venus-Earth-Earth-Gravity Assist (VEEGA) trajectory to achieve Jupiter orbit. Operations from launch to the Jupiter orbit insertion on Dec 7, 1995 are called Phase 1. Phase 2 (also called P2 and P2A) covers all Jupiter orbital operations. Phase 1 used the original instrument and spacecraft software while Phase 2 used code generated to optimize downlink telemetry efficiency. The EUV used three distinct data acquisition modes: Phase 1 Encounter Mode, Phase 1 Cruise Mode and Phase 2 Mode. The Phase 1 Encounter mode recorded the seven bit wavelength address of each detected photon. As the instrument FOV sweeps around the ribbon of sky, the topmost bit of the telemetered byte was used to code the sky position, divided into 'sky sectors'. A full telemetered rotation was therefore needed in order to interpret the position of the detected photons. In Encounter Mode, housekeeping information was also placed in the instrument telemetry stream. It included a Wavelength Integration Buffer (WIB) and a Sector Integration Buffer (SIB). All photons were summed in these buffers, which in turn were systematically read out in the periodic housekeeping bytes. An Appendix to the EUV Functional Requirements Document provides detailed information on the interpretation of the telemetry stream for Encounter Mode. The VEEGA mission cruise periods presented limited downlink capability until the High Gain Antenna was to be released after Earth 1. The WIB and SIB arrays devised for the Encounter Mode provided the basic concept for a Phase 1 Cruise Mode, where an internal instrument memory area was used to hold a matrix configured for a few, selectable wavelengths integrated over a few fairly large sky sectors. In this way, full sky maps of Lyman-alpha and Helium were obtained with Memory Read Outs (MROs), sent to the ground in the engineering telemetry stream. These EUV MROs produced an excellent data set all the way from post-turn-on (Dec 27, 1989) through the last pre-Jupiter load period (Oct. 1995). The Phase 2 Mode was based on the concepts used in the Phase 1 Cruise Mode. In Phase 2, the internal matrix was expanded by removing the original Encounter Mode code. The new Phase 2 EUV program, software Version 4.1, provides a matrix capable of 1092 16-bit words. The division of the matrix is controlled by the Fixed Pattern Noise Table (FPNT). V4.1 processes photons faster than the earlier codes. All the Modes control the selection of photons based on a FPNT concept used by the Voyager UVS logic design. The FPNT is basically a Look-up-Table of detector locations and specifies some instructions as to how to treat the photons: ignore, register or sum together, as Phase 2 Super Pixels. (The Phase 1 and Phase 2 codes act on the table slightly differently; use the program supplied for each Phase.) The EUV command supplies the number of sky sectors, which, along with the number of Super Pixels, defines the internal data matrix organization. This matrix is read out as either: 1) a set of Real Time packets or 2) a two minute stream of bytes placed onto the tape recorder. Engineering Data ================ The EUV housekeeping information is contained in the last 24 bytes of every realtime buffer dump and is also reported every 2 rims in the LRS/record data. value explanation of housekeeping values: ----------------------------------------------------------------------------- 0 7E FIDUCIAL 1 7E FIDUCIAL 2 YY transition sector pair mod 64 value: how many pixel pairs to ignore before starting integration (there are 256 pixel pairs between RTI's (almost)) these have further been subdivided into 4 groups of 64). Recall that a pixel pair takes 330 microseconds to process, 256 pixel pairs*330e-6=0.08448 seconds; 1 RTI= 0.06666 seconds. 3 5A=90 active pixels x 2 taken directly from FPN data matrix is usually 45 pixels by 24 sectors command echo: 4 58=88dec echo of commanded starting angle 5 0B echo of commanded HV level(03) + Count bit set(8) 6 01 echo of commanded scans/sector 7 18=24dec echo of commanded sectors Time at last integration start: 8 A3 next to least significant byte of spacecraft RIM counter 9 E0 least significant byte of spacecraft RIM counter End time = 3448924 = 34a3e0 10 MF mod 91 (minor frame count) 11 RR mod 10 (RTI count) Angles: 12 E6 most significant byte of delta Theta (delta Theta is in degrees covered in 66 2/3 msec (1 RTI), increment is 360/16,777,216 degrees) 13 A5 least significant byte of delta Theta 3.14 rpm = E6A5 2.89 rpm = D270 14 TT most significant byte of Theta (Theta increment=360/65,536 degrees) 15 TT least significant byte of Theta 16 41 software version #, expect 41 for version 4.1 17 00 msbyte of 16 bit integration counter (# of spins where we actually integrated) 18 66 lsbyte of 16 bit integration counter 0066 = 182 integrations 19 01 real time RTI (exact current RTI when you read out address EFB, 1 of 2 real-time values in housekeeping) 20 ZZ transition sector pair mod 200 (decimal) value: how many pixel pairs to ignore before starting integration 21 38=56 real-time minor frame counter (associated with EFB) for real time data this should always be 56, because the last packet of a buffer dump is always read out on minor frame 56. 22 01 The number of times the s/w has had to wait to sync up with s/c time. This value should be one, since there is one sync up when the microprocessor starts. Any count greater than one indicates that s/w is too busy and is overwriting the s/c RTI 8 before it can determine that it is really in sync. 23 00 spare Data Buffer Configuration ========================= The Phase 2 FPNTs are described below. File: TORUS1:[GLL_RAW.INFO]PHASE2_FPNT.DOC - of 5 June, 1996 also see: DISKH:[GLLSEQ.LIB]ORBITAL_FIXED_PAT_TABLES.FPN *************************************************************** * This is draft of the set of DMLs for the Fixed Pattern Noise * Table for the G1 torus and Jupiter observations * Edited Nov 18,94 KES. * With add'l Jupiter table input from Ian,Edited Nov 21,94 KES * With add'l All-purpose table input from Ian, Nov 22,94 KES * * Add'l updates for changes in Neil's s/w= 1) all values are * now 2*accumulator value, 2) there is no longer a FPN * ID value in location 125, 3) there MUST be a ZERO value * in location 126 and 4) location 127 must be 2 times the * number of active accumulators. Feb 24,1995-kes * JPL testing revealed an error in the AURORA FPN. Pixel 92 & 93 * were 3D when they should have been 3E. May 1995 - JG * * Pixels are labeled from 0 to 127. A value in a location * assigns a 'superpixel' reference number; several locs * with the same superpixel value indicates these pixels * will be summed into the same superpixel value. It is also * appropriate to call a superpixel an accumulator. Within * the Phase II instr. s/w, the micro reads the accumulator * number from the even location and uses it as a micro address * in which it accumulates the pixel-pair photons for that * even-odd pair. 126 must be zero because the location is * used. The values being two times their pixel-pair value * saves micro multiplication time in calculating the address. * * These FPN sets assume 24 sectors and therefore 45 pixels * If any new FPN tables are constructed containing MORE THAN 45 pixels * then it is IMPERATIVE that a 24EUV command using only one sector * be used before the new FPN is loaded. (It would be followed by * the FPN load, a new 24EUV command and a 24CLR cmd.) If this is * not done then the uP may overwrite itself. ALWAYS load a new FPN * followed by the new 24EUV command. 23-Aug,95 -KES * * The 24EUV Phase II commands are still TBD; the format is: * EUVCMD,NORM,COUNT,gain=3,start_angle,CRUISE,scans_per_sector,num_sectors * * A preliminary J0-G1 cmd is, as an example, * EUVCMD,NORM,COUNT,03,58,CRUISE,1,18 * to give 88 (dec, 58hex)= Starting Angle, 1 scan/sector, and 24d sectors * * (orig. cruise cmd: EUVCMD,NORM,COUNT,03,01,CRUISE,19,23) * * (Footnote on counting nomenclature. EUV has a 128 byte buffer * for the FPN table. The buffer is assigned usage beginning at * location zero; the first pixel to be counted occurs at FPN * number zero. The pixel channels are also numbered from 0-127. * Phase II assumes a zero value indicates a 'don't use'. * *************************************************************** +++++++++++++++++++++++++++Below are the corrected tables++++++++++++++ For TORUS observations: 24DML,0F00, pixels 02,02,02,02,04,04,04,04,06,06, 0 to 9 06,06,08,08,08,08,0A,0A,0C,0C, 10 to 19 0E,0E,10,10,12,12,14,14,16,16, 20 to 29 18,18,1A,1A,1C,1C,1E,1E,20,20, 30 to 39 22,22,24,24,26,26,28,28,2A,2A, 40 to 49 2C,2C,2E,2E,30,30,32,32,32,32, 50 to 59 34,34,36,36 60 to 64 24DML,0F40, 36,36,38,38,38,38, 64 to 69 3A,3A,3A,3A,3C,3C,3C,3C,3E,3E, 70 to 79 3E,3E,40,40,40,40,42,42,42,42, 80 to 89 44,44,44,44,46,46,48,48,48,48, 90 to 99 4A,4A,4A,4A,4C,4C,4C,4C,4E,4E, 100 to 109 50,50,52,52,54,54,56,56,56,56, 110 to 119 58,58,58,58,5A,5A,00,5A 120 to 127 For Jupiter AURORA AND AIRGLOW observations: 24DML,0F00, pixels 02,02,02,02,04,04,06,06,08,08, 0 to 9 08,08,0A,0A,0A,0A,0C,0C,0C,0C, 10 to 19 0E,0E,0E,0E,10,10,10,10,12,12, 20 to 29 12,12,14,14,14,14,16,16,16,16, 30 to 39 18,18,18,18,1A,1A,1A,1A,1C,1C, 40 to 49 1C,1C,1E,1E,1E,1E,20,20,20,20, 50 to 59 22,22,22,22 60 to 63 24DML,0F40, 24,24,26,26,28,28, 64 to 69 2A,2A,2C,2C,2E,2E,2E,2E,30,30, 70 to 79 32,32,34,34,36,36,38,38,3A,3A, 80 to 89 3C,3C,3E,3E,40,40,42,42,44,44, 90 to 99 46,46,46,46,48,48,48,48,4A,4A, 100 to 109 4C,4C,4E,4E,50,50,52,52,54,54, 110 to 119 56,56,58,58,5A,5A,00,5A 120 to 127 =========================================================================== For ALL-PURPOSE observations (when you cannot change tables): 24DML,0F00, pixels 02,02,02,02,04,04,04,04,06,06, 0 to 9 06,06,08,08,08,08,0A,0A,0A,0A, 10 to 19 0C,0C,0E,0E,10,10,12,12,14,14, 20 to 29 16,16,18,18,1A,1A,1C,1C,1E,1E, 30 to 39 20,20,20,20,22,22,24,24,26,26, 40 to 49 28,28,2A,2A,2A,2A,2C,2C,2C,2C, 50 to 59 2E,2E,2E,2E 60 to 64 24DML,0F40, 30,30,30,30,32,32, 64 to 69 32,32,34,34,34,34,36,36,38,38, 70 to 79 3A,3A,3C,3C,3E,3E,3E,3E,40,40, 80 to 89 40,40,42,42,42,42,44,44,44,44, 90 to 99 46,46,46,46,48,48,48,48,4A,4A, 100 to 109 4C,4C,4E,4E,50,50,52,52,54,54, 110 to 119 56,56,58,58,5A,5A,00,5A 120 to 127 *************************************************************** The Phase 1 software version number is Version 2.1; the Phase 2 is Version 4.1. Phase 2 housekeeping reports the version as well, at location word 17. " END_OBJECT = INSTRUMENT_INFORMATION OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "BEUTLER_1945" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "BROADFOOT_ETAL_1977" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "BROADFOOT&SANDEL1977" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "CLARKEETAL1989A" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "CLARKEETAL1989B" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "ESHLEMANETAL1979" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "GLADSTONE&SKINNER1989" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "GLL-625-205" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "HALE&WADSWORTH_1896" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "HORD_ETAL_1991" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "HORD_ETAL_1992" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "MCCLINTOCK1989" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "METZGERETAL1983" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "SANDELETAL1993" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "STROBEL1989" END_OBJECT = INSTRUMENT_REFERENCE_INFO OBJECT = INSTRUMENT_REFERENCE_INFO REFERENCE_KEY_ID = "THOMAS1978" END_OBJECT = INSTRUMENT_REFERENCE_INFO END_OBJECT = INSTRUMENT END