Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Story Points:2
-
Sprint:TSSW Sprint - Jun 8 - Jun 22
-
Team:Telescope and Site
-
Urgent?:No
Description
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we do see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at DM-25243):
The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds).
Attachments
Issue Links
- relates to
-
- Done
-
- Done
-
- Done
-
- Done
-
- Done
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link |
|
| Description | If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result: |
| Attachment | track_v0_1_long_enterFault.png [ 44217 ] |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result: |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result: !track_v0_1_long_enterFault.png|thumbnail! |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result: !track_v0_1_long_enterFault.png|thumbnail! |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at DM-25434): !track_v0_1_long_enterFault.png|thumbnail! |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at DM-25434): !track_v0_1_long_enterFault.png|thumbnail! |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at [ !track_v0_1_long_enterFault.png|thumbnail! |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at [ !track_v0_1_long_enterFault.png|thumbnail! |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds. |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink mode by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds. |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds. |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how is that decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds. |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds. |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds. |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command at time equals 6 seconds). |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command at time equals 6 seconds). |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds). |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we did see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds). |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we does see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds). |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we does see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds). |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we do see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds). |
| Description |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This time could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we do see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds). |
If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we do see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.
The following is the figure to show the simulation result (detail is at !track_v0_1_long_enterFault.png|thumbnail! The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds). |
| Labels | HexRot MainTelescope | HexRot MainTelescope ccw-rotator-integration-test |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Attachment | slewWithoutNewTrackCmd.png [ 44428 ] |
| Attachment | trackWithNoNewTrackCmdAfterSomeTime.png [ 44439 ] |
| Attachment | trackAndEnterFaultAfterSlewDoneWithoutNewTrackCmd.png [ 44456 ] |
| Attachment | trackAndEnterFaultAtTrackStateWithoutNewTrackCmd.png [ 44459 ] |
| Attachment | trackAndFaultAndClearError.png [ 44461 ] |
| Attachment | trackAndFaultAndClearErrorFinalTrack9_5secMagnify.png [ 44462 ] | |
| Attachment | trackAndFaultAndClearErrorFinalTrack9_5sec.png [ 44463 ] |
| Story Points | 3 | 2 |
| Reviewers | Russell Owen [ rowen ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Attachment | image-2020-06-22-10-58-59-157.png [ 44498 ] |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |