Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:0
-
Epic Link:
-
Team:Telescope and Site
-
Urgent?:No
Description
While you are looking at the Hexapod and Rotator code, please see how difficult it would be to use a single socket for communications, instead of a pair of sockets, one of which is only read from and the other only written to.
This makes the PXI and CSC code simpler and more robust because we don't have to deal the problem of having just one socket connected.
Also, if it's not too much work, it would be a significant improvement to have the server end on the PXI and the client end running on the CSC and EUI. That way the host addresses are configured in the higher-level code (CSC and EUI), where they are easier to maintain.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Summary | Use a single socket to connect to the low-level controller | Use a single socket to connect to the Hexapod and Rotator PXIs |
| Description |
While you are looking at the Hexapod and Rotator code, please see how difficult it would be to use a single (bidirectional) socket for communications, instead of a pair of unidirectional sockets.
This makes the PXI and CSC code simpler and more robust because we don't have to deal the problem of having just one socket connected. |
While you are looking at the Hexapod and Rotator code, please see how difficult it would be to use a single (bidirectional) socket for communications, instead of a pair of unidirectional sockets.
This makes the PXI and CSC code simpler and more robust because we don't have to deal the problem of having just one socket connected. Also, if it's not too much work, it would be a significant improvement to have the server end on the PXI and the client end running on the CSC and EUI. That way the host addresses are configured in the higher-level code (CSC and EUI), where they are easier to maintain. |
| Description |
While you are looking at the Hexapod and Rotator code, please see how difficult it would be to use a single (bidirectional) socket for communications, instead of a pair of unidirectional sockets.
This makes the PXI and CSC code simpler and more robust because we don't have to deal the problem of having just one socket connected. Also, if it's not too much work, it would be a significant improvement to have the server end on the PXI and the client end running on the CSC and EUI. That way the host addresses are configured in the higher-level code (CSC and EUI), where they are easier to maintain. |
While you are looking at the Hexapod and Rotator code, please see how difficult it would be to use a single socket for communications, instead of a pair of sockets, one of which is only read from and the other only written to.
This makes the PXI and CSC code simpler and more robust because we don't have to deal the problem of having just one socket connected. Also, if it's not too much work, it would be a significant improvement to have the server end on the PXI and the client end running on the CSC and EUI. That way the host addresses are configured in the higher-level code (CSC and EUI), where they are easier to maintain. |
| Epic Link |
|
| Epic Link | DM-32113 [ 770361 ] |
| Story Points | 0 |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Reviewers | Russell Owen [ rowen ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |