Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:TSSW Sprint - Sep 12 - Sep 26
-
Team:Telescope and Site
-
Urgent?:No
Description
Read the configuration files of M2 cell controller (ts_mtm2_cell). Right now, the cell controller will read the configuration files at the hard-coded /U/config directory in the cRIO. In addition, it also gets the parameters of calculation from the server code (ts_mtm2) when the TCP/IP connection is on. This ticket is to let the cell controller reads the configuration files directly from a relative path in real-time target. The files will be copied at the deploy process of LabVIEW project.
This ticket is the phase 1. This will focus on the framework to read the relative path and the log parameters.
Attachments
Issue Links
Activity
Controller.startupScriptEngine.vi passes the directories of log/ and script/ to ScriptEngine.ScriptEngine.vi.
I tried to copy the classes to read the configuration file from the ts_mtm2. However, I realized that there might be too many dependencies and the original implementation is not good. Therefore, I think maybe I need to implement the details by myself.
I created the ReaderCsv class to read the csv configuration files. The use of it will be in the next ticket: DM-36229.
Please help to review the PR:
https://github.com/lsst-ts/ts_mtm2_cell/pull/7
For the commit 23f6e17, some vis were changed by LabVIEW itself. I guess only "ScriptEngine", "Controller*, "utils", and "Model" are important.
Thanks!
Reviewed in GitHub. Thanks!
The config/, log/, and script/ directories will be copied to the cRIO at the deployment process. The log settings are read from the config/log.json.
In the NetworkInterface.vi, the control system will read the parameters in the case strucure of "LoadConfiguration". There are two vis involved in: (1) updateControlParameters.vi and (2) updatePowerSubsystemParameters.vi.