Content Comparison

...

1. Tried setting up TCP/IP server on T.C.S - SUCCESS
   1. Attempted to do this through DMF TCS by:
      1. Go to DFMTCS (
      program
      1. software),
      open
      1. Options→ Communication→ TCP/
      IP→Activate Connection. TCP/IP address and port configurable while TCP/IP server is offline. Changes made to ExCOM under communications window. Changed serial port assignment to COM4. 
      1. IP tab.
      2. From here, if the TCP/IP Server is active, you cannot change settings.
      3. To change the settings, select "No Connection", then hit the "TCP/IP Settings" button
         1. From here, you can change the Port number and can view the IP being used
   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. In order to have TCS talk to telescope via ExCOM, navigate to Options→ Communication→ExCOM tab
   1. Then Select "no connection" and modify the serial settings to communicate on serial port COM4
   2. Then select "Serial port" and enjoy
   3. NOTE: This conflicts with the default communication mode of TheSky6, which also uses COM4 to communicate with the telescope.
   4. NEED PAGE ON SERIAL PORT DISCOVERY AND USE
5. Overall: Success issuing TCP/IP I P 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.
6. Command used for testing was command #16 (per UMBC_Observatory_DFM_Telescope_Manual(aka man721.doc ) page 43)

...