Note to QA: Once this task is complete, update robotframework_ts_xml/scripts/Attribute_Naming.py and robotframework_ts_xml/scripts/XML_Generic.py to remove the special handling for this CSC and regenerate the test suites.

Hey Te-Wei - Can you please confirm this is done and send it to review?  Thanks.

Harini had done this already. I thought you had the related tests already. Please review this task. Thanks!

Harini started this process, but several Telemetry attributes still need to be updated:

Several failures occurred:

1) "CopleyStatusWordDrive does not conform to naming conventions."

2) "CopleyLatchingFaultStatus does not conform to naming conventions."

3) "Demand does not conform to naming conventions."

4) "Position does not conform to naming conventions."

5) "Error does not conform to naming conventions."

6) "Calibrated does not conform to naming conventions."

7) "Raw does not conform to naming conventions." 

I would like to make this change as part of DM-21699 if we can hold off until then. I was planning to implement that ticket after we are sure that we don't need the vendor's CSC code and can use my Rotator and Hexapod CSCs instead. We are planning to test the new Rotator CSC at SLAC on Monday 10/28. I beg you not to mess with the XML until then. I don't want any last-minute changes this close to a test.

Most of this was implemented in DM-21699. However, we need to coordinate with Tekniker on updating the camera cable wrap controller because it is listening to the Rotator Application telemetry topic.

The remaining problem was the Rotator Application topic and Wouter van Reeven fixed that for me when he renamed Rotator to MTRotator.