DRAFT Observation Night Full Moon +1d

Attendance Onkar, Gabriel, Roy briefly

Date & Time 11/8/22, 1900-

Spaces Occupied 401 Control room and Dome

Goals

1. (Onkar) Test new FireNex
2. (Onkar) Investigate/Fix Motherboard Ethernet Port on Data Computer
3. (Gabriel) Investigate TCP/IP Stuff
4. Point Scope & Write it up in Wiki
5. Astrometric calibration with M67 or NGC188
   1. Need sidereal tracking, not solar
   2. So point on high star
   3. Use https://archive.stsci.edu/cgi-bin/dss_form to find images
6. Write up tracking vs (auto)guiding
7. Write wiki for general telescope use

Log

Gabriel Investigate TCP/IP Stuff

1. Tried setting up TCP/IP server on T.C.S - SUCCESS
   1. Go to DFMTCS (program), open Options→ Communication→ TCP/IP→Activate Connection. TCP/IP address and port configurable while TCP/IP server is offline.
   2. Service status exists on the bottom right of DFMTCS program under "Communication" box
2. Tried connecting the T.C.S(telescope control system) to the D.C(data computer) - FAILED
   1. Tried connecting the said computers directly via ethernet cable -FAILED (D.C didn't recognize the connection - checked with ipconfig and windows control panel on DC. T.C.S recognized connection but documented "no internet access"). 
      1. Not sure if network established, just no internet OR if machine just detected a cable connection.
         1. What does it mean when Windows reports "no internet access"?
   2. Tried connecting through university local area network, D.C recognizes T.C.S TCP/IP address (could get pings)
      1. No connection possible through DFM TCP client, this could be DFM client issue( ?)
3. Tried connecting the T.C.S. to localhost/TCP address via TCP/IP - SUCCESS
   1. Tried through DFM TCP/IP client -FAILED (Attempt to update SET RATE (Command #16) didn't cause update on DFMTCS)
   2. Tried TCP/IP client of off internet "wifly communication test" -SUCCESS (but buggy)
   3. Note: Don't know if T.C.S connects to address directly through localhost or through local network and then its IP address
4. Overall: Success issuing TCP/IP commands to DFMTCS over wifly communication test software running on TCS connected to localhost or self-reported IP. Need to figure out how to connect DC to TCS and issue wifly commands more reliably over this connection.
5. Command used for testing was command #16 (per UMBC_Observatory_DFM_Telescope_Manual(aka man721.doc ) page 43)

Pointing Scope

1. Opened SharpCap
2. Opened TheSky6
3. Connecting CMOS to DC
   1. Originally connected LBD cable to CMOS, then to DC – Failed. Red LED lit on remote end
   2. Then disconnected everything
   3. Then connected LBD to DC, then to CMOS. – Success. Green LED lit on remote end
4. Detecting CMOS in SharpCap
   1. After successful connection between DC and CMOS (measured by LED on LBD?(ask Onkar))
   2. SharpCap was not seeing  

Other Notes

1. Seems like we need to connect LDB to DC before CMOS for successful connection