This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
tcs:legacy_tcs_socket_communction [2014/02/13 13:24] scott [ALL keyword] |
tcs:legacy_tcs_socket_communction [2017/02/10 17:14] (current) scott |
||
---|---|---|---|
Line 3: | Line 3: | ||
===Overview=== | ===Overview=== | ||
- | Legacy TCS only allows remote telescope communication and control through a serial port on the main TCS computer. In order to allow network communication and control of the telescope we have built software called Telcom to convert tcp/ip sockets to serial communication. To make sure this software is up and running on the BOK telescope you can check the website http://bokpop.as.arizona.edu and look for the table marked telemetry. This webpage queries the telcom server about once a second. | + | Legacy TCS only allows remote telescope communication and control through a serial port on the main TCS computer. In order to allow network communication and control of the telescope we have built software called Telcom to convert tcp/ip sockets to serial communication. To make sure this software is up and running on the BOK telescope you can check the website http://bok.as.arizona.edu: |
+ | === === | ||
+ | You can find a list of legacy TCS commands [[tcs: | ||
===== Request syntax ===== | ===== Request syntax ===== | ||
==== ==== | ==== ==== | ||
Line 47: | Line 49: | ||
An example string: | An example string: | ||
- | | BOK TCS 123 0 2231:27.64 +314312.0 | + | ^ BOK TCS 123 0 2231:27.64 +314312.0 |
It should be noted that all strings returned on the Telcom socket will end with a carriage return (\r). | It should be noted that all strings returned on the Telcom socket will end with a carriage return (\r). |