Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Story Points:3
-
Sprint:TSSW Sprint - Jul 20 - Aug 3
-
Team:Telescope and Site
-
Urgent?:No
Description
Publish the velocity or needed telemetry to DDS for rotator.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Sprint | TSSW Sprint - Jul 20 - Aug 3 [ 1034 ] |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Attachment | pt2ptMovePosPositive.png [ 44940 ] | |
| Attachment | pt2ptMoveRatePositive.png [ 44941 ] |
| Attachment | pt2ptMoveRateNegative.png [ 44942 ] | |
| Attachment | pt2ptMovePosNegative.png [ 44943 ] |
| Story Points | 2 | 3 |
Report the telemetry of velocity and no new track comand to high-level rotator CSC.
| Attachment | data.mat [ 45024 ] |
Add the raw data of Simulink model for the possible test in the high-level rotator CSC: data.mat
.
Please help to review the PR:
https://github.com/lsst-ts/ts_rotator_controller/pull/9
This PR will break the rotator CSC for the updated DDS telemetry. However, the initial test on summit will still use the original PXI code. That means the update of rotator CSC is not urgent.
Thanks!
| Reviewers | Russell Owen [ rowen ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
This looks very nice. I have a few small suggestions on github.
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |
Do the point-to-point movement in the positive direction and check the available velocity telemetry as the following:
It looks there is the problem of cha_rate_fb and chb_rate_fb. Therefore, I put the rateCmd to do the comparison as well.
Put the negative direction below:
The data of rate A and B are written in 'rotator_smlink_controller' -> 'Control Laws & Profile Generators (4 khz)' -> 'Controller' -> 'Channel-A/B velocity loop' subsystem.