ARIES Warm Preparations

WBS/subelement Issue or Topic Progress Imminent steps Controller/EEPROM No ability to program a Reverse-engineered EP-1 to Try to use minicom under blank EEPROM. determine that XMODEM is the MacOS/BSD/Linux to XMODEM a file protocol and there is no proprietary to EEPROM and verify same contents Pisces/ARIES EEPROMs have header. Plain XMODEM transfers from read back. [Tested under failed or been given away. should work! EP-1 may be future- NetBSD and MacOS -- 3/10] We’ve been using the last proof after all. [It is now. 3/10] one now since 2018. Generate EEPROM from scratch, see Required docs: that it fully works w/ SDSU EP-1 is a vintage • Ep-1 manual and EP.EXE for controller. [DONE for GENIII, 3/10] programmer from 1980s serial-sniffing [GENII needs testing – TO DO] that requires real DOS. Buy more blank EEPROMs. [FOUND MORE SPARES - 3/10]

Document the process. [PARTIAL] Controller/EEPROM Standard EEPROM build Using the SREC converter from Use known-good EEPROM burn file process does not work for Motorola does not generate the from GenII controller (2004 code) to EP-1 burns. Needs to be correct-looking code. understand format. [DONE 3/10] SREC or similar format. It writes to EEPROM but doesn’t Alter build process on GenII code to Must be possible; we did actually work in the controller. replicate this file. Burn to EEPROM this in 2004… and verify it works on GenII as per Required docs: above. [New build system under • 56x000 DSP complier wine works, results not tested on documentation GenII controller yet.] • Old IRL EEPROM burn files Now do the same for GenIII. [DONE and works! 3/10] Document the process. [PARTIAL]

Page 9 WBS/subelement Issue or Topic Progress Imminent steps Controller/Test Setup Set up controlled test Safe ARIES, move controller environment for benchtop harnesses to table in controlled test. configuration, Saleae and DVM, ESD protect, etc.

Page 10 WBS/subelement Issue or Topic Progress Imminent steps Controller/Verification Verify new code for legacy Tested on one “quadrant” 1. Use Saleae analyzer on each ARC-46 video board to trace previously. Serial transfers were not digital line to verify pixel and all digital clock signals and tested. line clocks analog voltages. 2. Verify serial register Required docs to proceed: communication and • ARIES wiring schematics configuration matches • H2RG manual (2005) documentation. • Datasheet for LTC1608ACG 3. Verify analog biases for H2RG. • SDSU documentation for 4. Test grounded inputs: legacy ARC-46 (Oct 2003) a. Open controller and swap • Schematics for legacy ARC- cards to get video board 46 (Oct 2003) access. b. Probe hardware inputs and outputs to ADC; adjustments Software/hardware required: needed to be in range? • Saleae analyzer c. Software: adjust DACs, • Initial testing can be done achieve observe working with SDSU/OWL to verify readout. Verify stable operation. output and noise level. 5. Look up what analog output is expected from H2RG. Set up 4- way voltage divider on breadboard to put different signals on each “quadrant” to simulate a real array. Repeat the tests of step #3. Also verify de-interlacing using SDSU interface. 6. Document results. Documented success means we move to cold testing.

Page 11 Controller/Verification Verify new code for CLIO Replicated NIRCAM test code with 1. Replace point-to-point “ball of ARC-46 rev3a video board ARIES wiring configuration. Semi- wires” testing harness with to trace all digital clock tested in lab configuration. Dsub-terminated harness. signals and analog voltages. Probably some bugs left… 2. Use Saleae analyzer on each digital line to verify pixel and Required docs: line clocks. • ARIES wiring schematics 3. Verify serial register • H2RG manual (2005) communication & configuration • Datasheet for AD7641LQFP matches documentation. • SDSU documentation for 4. Verify analog biases for H2RG. new ARC-46 (July 2011) 5. Test grounded inputs: • Schematics for rev3A ARC-46 a. Open controller and swap (May 2007) cards to get video board access. Software/hardware required: b. Probe hardware inputs and • Saleae analyzer outputs to ADC; adjustments • Initial testing can be done needed to be in range? with SDSU/OWL to verify c. Software: adjust DACs, operation. achieve observe working • Validate NIRCAM 56300 readout. Verify stable microcode with all of the output and noise level. pertinent changes to match 6. Look up what analog output is the ARIES configuration. expected from H2RG. Set up 4- • Need to scrounge Dsub way voltage divider on connectors of the breadboard to put different appropriate gender and pin signals on each “quadrant” to count for interfacing new simulate a real array. Repeat video board. Easy Digikey the tests of step #3. Also verify order otherwise. de-interlacing using SDSU interface. 7. Document results. Documented success means we move to cold testing.

Page 12 WBS/subelement Issue or Topic Progress Imminent steps Instrument/Software Add H2RG support to ARIES Two main trades: Option 1 should be evaluated against backend code. 1. Update ARIES infrastructure to Pisces first. use “device-independent” v3.5 (Can be deferred to after SDSU APIs Option 2 needs bug-fixes merged cold tests.) 2. Add H2RG support to existing from SDSU into LiL. “LiL” (Leach in Linux) interface. Prototype, decide, implement, test against initial test results using OWL and the SDSU v3.5 API. Instrument/Software Plumb more generalized Not started. Initial design, including support into ARIES GUI and housekeeping, calibration, remote data system. Expectation is to further the existing operations, and other desireables. MacOS,IOS app with compatibility (Can be deferred to after with GNUstep on Linux. Merge bug-fixes and other cold tests.) wants/needs from last “TO DO” list Alternates are: into this development effort. • PyQT interface • Web browser interface Instrument/ Merge test reports and Old wiki died with 2004 aries Merge aries wiki data into mediawiki Documentation existing documentation computer. Wiki data and on soral. onto wiki instrument data were archived. Science data are available by ssh to Wiki is observer-centric. Add soral.as.arizona.edu and a categories for test data and mediawiki instance is ready to instrument documentation. accept the aries wiki data. C.K. Updated 3 April 2019

Page 13