Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_auxiliary_telescope, ts_main_telescope
-
Labels:
-
Story Points:3
-
Epic Link:
-
Sprint:TSSW Sprint - Dec 06 - Dec 20
-
Team:Telescope and Site
-
Urgent?:No
Description
Modify the ESS CSC to support data clients which communicate with sensor data servers. This will allow different kinds of remote sensors, including those connected to a LabJack, but this ticket just adds a base client and an RPi client; adding a LabJack data client will be done on a different ticket.
Changes:
- Add BaseDataClient, MockDataClient, register_data_client_class and get_data_client_class to ts_ess_common. Putting it here instead of ts_ess_csc avoids circular dependencies for future data clients such as the LabJack client. Each data client has its own config schema.
- Add RPiDataClient to ts_ess_csc.
- Update the CSC config schema to support data clients.
- Update the CSC config schema to put data for all ESS instances in the same data file. The CSC picks the correct piece of configuration based on its SAL index.
- Update the config schema version from v1 to v2.
- Add an ESS/v2 directory to ts_config_ocs, with a single file "default.yaml" that contains configuration for all existing ESS instances.
Tiago Ribeiro requested that I make this version compatible with ts_idl v3.5.0/3.6.0. In order to do that I added a local version of ErrorCode to ts_ess_csc and filed
DM-32972to remove it once ts_idl v3.7.0 is released.Other changes:
Now that we are serving ts_common documentation, I suggest that the RPi protocol documentation be moved to ts_ess_control – either on this ticket (I am happy to do that, but it adds a new PR) or on a new ticket (which I am happy to file).
Pull requests: