tcs:legacy_tcs_socket_communction
Differences
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/12 13:36] scott |
tcs:legacy_tcs_socket_communction [2017/02/10 17:14] (current) scott |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====Overview===== | + | =====Legacy TCS Network Communication===== |
| - | 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:// | + | ===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:// | ||
| + | |||
| + | === === | ||
| + | You can find a list of legacy TCS commands [[tcs: | ||
| ===== Request syntax ===== | ===== Request syntax ===== | ||
| ==== ==== | ==== ==== | ||
| Line 39: | Line 43: | ||
| ==== " | ==== " | ||
| - | If you want to get multiple pieces of data from the telcom server rapidly you can use the ALL keyword. This will return a string containing all the telemetry data described above which will have to be parsed. The string gives values seperated by 1 or more white spaces. The structure of the string is given in the table below. | + | If you want to get multiple pieces of data from the telcom server rapidly you can use the ALL keyword. This will return a string containing all the telemetry data described above which will have to be parsed. The string gives values seperated by 1 or more white spaces. The table below shows the order the values are placed |
| ^Return Values | MOT | RA | DEC | HA | ST | EL | AZ | SECZ | EQ | JD | WOBBLE | DOME | UT | IIS | | ^Return Values | MOT | RA | DEC | HA | ST | EL | AZ | SECZ | EQ | JD | WOBBLE | DOME | UT | IIS | | ||
| ^Example Value |0 | 221941.92 | +314308.8 | -00:00:00 | 22:20:19 | 90.0 | +7.6 | 1.00 | D2000.000 | 2456698.3 | 1 |-78.6 | 20:27:19.1 | 0.0 | | ^Example Value |0 | 221941.92 | +314308.8 | -00:00:00 | 22:20:19 | 90.0 | +7.6 | 1.00 | D2000.000 | 2456698.3 | 1 |-78.6 | 20:27:19.1 | 0.0 | | ||
| + | |||
| + | An example string: | ||
| + | ^ 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). | ||
tcs/legacy_tcs_socket_communction.1392237385.txt.gz ยท Last modified: 2014/02/12 13:36 by scott
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
