Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-22067

Diagnose failure to command rotator

    XMLWordPrintable

    Details

    • Story Points:
      2
    • Epic Link:
    • Sprint:
      TSSW Sprint - Oct 28 - Nov 10, TSSW Sprint - Nov 11 - Nov 22
    • Team:
      Telescope and Site

      Description

      In rotator testing at SLAC DM-21951 we discovered that commands from the Python CSC were being ignored.

      This ticket is to diagnose the problem. I propose to make use the fake cRIO controller in the ts_rotator package to talk to the real vendor's CSC, monitor the data in the commands sent by that CSC, and compare it to the data in the commands sent by the Python CSC.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-22146 Test the Rotator/ Hexapod CSC based on ts_salobj

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-21951 Support November 1 rotator tests at SLAC

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-22066 Fix issues discovered in SLAC rotator testing

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            rowen Russell Owen added a comment -

            I spent one day on this getting the vendor's middleware CSC running and talking to my mock rotator controller. I discovered that the enterControl command sent by the middleware is byte-for-byte identical to the one sent by my CSC. At this point I think my CSC is doing the right thing and the problem lies elsewhere. Unfortunately that will be difficult to prove until we have further access to real cRIOs or a working simulator.

            Show
            rowen Russell Owen added a comment - I spent one day on this getting the vendor's middleware CSC running and talking to my mock rotator controller. I discovered that the enterControl command sent by the middleware is byte-for-byte identical to the one sent by my CSC. At this point I think my CSC is doing the right thing and the problem lies elsewhere. Unfortunately that will be difficult to prove until we have further access to real cRIOs or a working simulator.
            Hide
            Permalink
            rowen Russell Owen added a comment - - edited

            We have identified the most likely cause of the problem. A screen shot of the EUI shows that the cRIO was in "GUI" control mode, which means commands from the CSC are ignored.

            I have updated the CSC code for the hexapod and rotator to reject commands if the controller is in this state, as part of DM-22066

            Show
            rowen Russell Owen added a comment - - edited We have identified the most likely cause of the problem. A screen shot of the EUI shows that the cRIO was in "GUI" control mode, which means commands from the CSC are ignored. I have updated the CSC code for the hexapod and rotator to reject commands if the controller is in this state, as part of DM-22066

              People

              Assignee:
              rowen Russell Owen
              Reporter:
              rowen Russell Owen
              Watchers:
              Russell Owen, Te-Wei Tsai, Tiago Ribeiro
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.