Differences

This shows you the differences between two versions of the page.

--- tcs:limit_logic [2019/05/21 17:08]
scott
+++ tcs:limit_logic [2019/08/24 13:29] (current)
scott
@@ Line 5: / Line 5: @@
-===== New Constraints On Bias and Paddle Rates =====
-We would like to implement a new upper limit on Bias and Paddle (Guide and Drift) rates. There is still discussion about what exactly the upper limit will be but we are currently hovering around 300 arc seconds per second. If a rate is sent to TCS that is higher than the limit one of two things will happen:
-  - the rate won't change
+===== Limits (Completed) =====
-  - the rate will be set to the max rate
-** Note you will not be able to slew with bias rates or the paddle. **
-===== Limits =====
 The new limit logic discussed is a four tiered limit logic. There will be two software limits (S<sub>1</sub> and S<sub>2</sub>) and two hardware limits (H<sub>1</sub> and H<sub>2</sub>).
@@ Line 21: / Line 14: @@
 ** S<sub>1</sub> **
-S<sub>1</sub> will act like the current software horizon limits in that You can get passed S<sub>1</sub> by tracking, with bias rates or with the paddle guide and drift rates. You will not be able to move below S<sub>1</sub> using the standard goto functions in TCS. You will be able to move out of this limit but at a reduced rate (around 300 arcseconds per second).
+S<sub>1</sub> will act like slew limits in that You can get past S<sub>1</sub> by tracking, with bias rates or with the paddle guide and drift rates. You can move past an S<sub>1</sub> limit but the telescope will stop at the limit. You can the send the move command again and the telescope will continue at a very reduced rate.
 ** S<sub>2</sub> **
-S<sub>2</sub> will be a no go zone by goto functions, bias rates and the paddle. Hitting this software limit will be functionally equivalent to hitting the cancel button on the GUI. The telescope will ramp down and come to a stop. You will be able to back out of this limit.
+S<sub>2</sub> will be a no go zone by goto functions, bias rates and the paddle. Hitting this software limit will be functionally equivalent to hitting the cancel button on the GUI. The telescope will ramp down and come to a stop. You will be able to back out of this limit. If you try to move past this limit with the paddle you will move a little but tcs will cancel the move and send the telescope back to the limit.
 ** H<sub>1</sub> **
@@ Line 38: / Line 31: @@
 This is the last hardware limit and will function the same as the final hardware limit currently at most of our telescopes. As soon as it is hit, it will cut power to the drive system either by powering off the drives or by activating the Safe Torque Off option. You will not be able to back out of this limit with the control system. It will have to be done manually.
+===== New Constraints On Bias and Paddle Rates (TODO) =====
+We would like to implement a new upper limit on Bias and Paddle (Guide and Drift) rates. There is still discussion about what exactly the upper limit will be but we are currently hovering around 300 arc seconds per second. If a rate is sent to TCS that is higher than the limit one of two things will happen:
+  - the rate won't change
+  - the rate will be set to the max rate
+** Note you will not be able to slew with bias rates or the paddle. **
 ==== Differences From Current System ====

MOON

User Tools

Site Tools

Differences

Page Tools