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

Camera MThexapod inPosition event not generated

    XMLWordPrintable

    Details

      Description

      Looking at the EFD, the EFD shows that only for actuator one a status is present.
      Actuators 2-6 always present the status zero.
      Assuming that the information from all six actuators is needed, the inPosition event is not generated because of missing information on actuators 2-6.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-29769 Update MTHexapod and MTRotator for changes to the low-level controllers

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-28998 The MTHexapod low-level controller appears to only publish application status for the first actuator

          • Done

          Task - A task that needs to be done. CAP-743 Catch all ticket for TSSW XML 9.1 work

          • Undefined - No priority assigned (may not apply or be unknown)
          • Done
          mentioned in

          Page Loading...

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            aclements Andy Clements added a comment -

            I suspect there will be some work on the CSC side of things, so assigned it to Russell Owen.  Te-Wei Tsai will probably need to be involved as well?

            Show
            aclements Andy Clements added a comment - I suspect there will be some work on the CSC side of things, so assigned it to Russell Owen .  Te-Wei Tsai  will probably need to be involved as well?
            Hide
            Permalink
            rowen Russell Owen added a comment -

            As Holger says, this is likely caused by DM-28998. We should test again once DM-28998 is fixed.

            Show
            rowen Russell Owen added a comment - As Holger says, this is likely caused by DM-28998 . We should test again once DM-28998 is fixed.
            Hide
            Permalink
            rowen Russell Owen added a comment - - edited

            It turns out that fixing this issue does not require an update to the low-level controller. See DM-28998 for details.
            On this ticket I will fix the issue in a way that is compatible with the current (pre-DM-28998) low-level controller.
            On DM-29769 I will update the code (a trivial change) for the post-DM-28998 low-level controller.

            Pull requests:

            Show
            rowen Russell Owen added a comment - - edited It turns out that fixing this issue does not require an update to the low-level controller. See DM-28998 for details. On this ticket I will fix the issue in a way that is compatible with the current (pre- DM-28998 ) low-level controller. On DM-29769 I will update the code (a trivial change) for the post- DM-28998 low-level controller. Pull requests: https://github.com/lsst-ts/ts_mthexapod/pull/44 https://github.com/lsst-ts/ts_xml/pull/444
            Hide
            Permalink
            ttsai Te-Wei Tsai added a comment -

            The update looks good to me! Please help to check the failed jenkins build/test. Thanks!

            Show
            ttsai Te-Wei Tsai added a comment - The update looks good to me! Please help to check the failed jenkins build/test. Thanks!
            Hide
            Permalink
            rowen Russell Owen added a comment -

            Thank you for the quick review. As to the Jenkins failure of ts_mthexapod: it was a timeout, which suggests the usual "slow-Jenkins" intermittent issue. I re-ran the tests and they passed, and I have run them repeatedly with no failures on my own machine, so I think things are OK.

            I released ts_mthexapod v0.17.0 and updated DM-29704 in hopes of getting this new version into cycle build 19.

            Show
            rowen Russell Owen added a comment - Thank you for the quick review. As to the Jenkins failure of ts_mthexapod: it was a timeout, which suggests the usual "slow-Jenkins" intermittent issue. I re-ran the tests and they passed, and I have run them repeatedly with no failures on my own machine, so I think things are OK. I released ts_mthexapod v0.17.0 and updated DM-29704 in hopes of getting this new version into cycle build 19.

              People

              Assignee:
              rowen Russell Owen
              Reporter:
              hdrass Holger Drass
              Reviewers:
              Te-Wei Tsai
              Watchers:
              Andy Clements, Brian Stalder, Holger Drass, Russell Owen, Te-Wei Tsai
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.