Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Story Points:3
-
Epic Link:
-
Sprint:TSSW Sprint - Jan 31 - Feb 14
-
Team:Telescope and Site
-
Urgent?:No
Description
Reading data from FTDI devices in an asynchronous way results in bogged data while reading from the same device in a synchronous way doesn't. Investigate why and fix.
I tried enabling the ESS CSC again on Monday and it went into FAULT state because the temperature sensors didn't output any data. Therefore I took the sensor readout box off the sensors and connected it to my MacBook for debugging purposes. At first I found very weird behavior which I tracked down to me starting a thread, that reads the data from the sensor, twice. Once I realized that, I could make sure in my test code that the thread was only started once and all went back to normal. In the end it turned out that the code was fine but the docker container was lacking privileges to read data from the FTDI device. This has been fixed now, the sensor readout box has been reinstalled, the CSC started and data are entering in the EFD again.