fts: Update hard coded limits

[ShreyaSut]

Description

Needed to expand the hard limits for the FTS agent because the agent was previously for the ACT FTS. The current FTS is the SO FTS, which has a larger stage allowing for a wider range of motion. It uses an Aerotech controller still, allowing us to use the previous agent modified with the expanded limits. This SO FTS will stay at the site and will be used for SAT and LAT bandpass measurements.

Motivation and Context

The previous hard limits were preventing us from testing the SO FTS mirror stage at its limits of travel. Changing the limits from +/- 74.8 mm to +/-80 mm allowed us to command and test the FTS mirror stage at its limits of travel.

How Has This Been Tested?

Tested on the hardware at site.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[BrianJKoopman]

This sounds fine to me, but I have a few questions:

• Will this agent be used with the ACT FTS again ever?
• Does the ACT FTS have some protection in hardware from moving past this 74.8 limit, like a limit switch?

Also, please update the docstring a couple lines below this change to state the new limits.

[ShreyaSut]

This sounds fine to me, but I have a few questions:

• Will this agent be used with the ACT FTS again ever?
• Does the ACT FTS have some protection in hardware from moving past this 74.8 limit, like a limit switch?

Also, please update the docstring a couple lines below this change to state the new limits.

No, I don't expect it to be used with the ACT FTS again unless something were to happen to the SO FTS and we needed to use a backup. The ACT FTS does not have limit switches but the travel is generally bounded by a metal cutout on the base of the FTS from which the mirror on the stage sticks out, so I expect that would set a hard limit.

Docstring updated with the new limits.

[ShreyaSut]

Hey Brain, Sorry about the late response — I missed this last week, but responded to it this morning on GitHub, let me know if you don't see the response. Thanks, Shreya

…

________________________________ From: Brian Koopman ***@***.***> Sent: Wednesday, November 26, 2025 9:58 AM To: simonsobs/socs ***@***.***> Cc: Shreya Sutariya ***@***.***>; Assign ***@***.***> Subject: Re: [simonsobs/socs] FTS: updated hard coded limits (PR #954) @BrianJKoopman commented on this pull request. This sounds fine to me, but I have a few questions: * Will this agent be used with the ACT FTS again ever? * Does the ACT FTS have some protection in hardware from moving past this 74.8 limit, like a limit switch? Also, please update the docstring a couple lines below this change to state the new limits. — Reply to this email directly, view it on GitHub<#954 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATUUVXMKUJKACIKQDFGGMTD36XE2ZAVCNFSM6AAAAACNCN2M5KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTKMJRGY2TIOBVHE>. You are receiving this because you were assigned.Message ID: ***@***.***>

[BrianJKoopman]

Thanks for answering those questions, and for the docstring change!

[ShreyaSut]

Thank you, Brian! And apologies for the autocorrect misspelling in the last email..

…

________________________________ From: Brian Koopman ***@***.***> Sent: Monday, December 1, 2025 6:55 PM To: simonsobs/socs ***@***.***> Cc: Shreya Sutariya ***@***.***>; Assign ***@***.***> Subject: Re: [simonsobs/socs] FTS: updated hard coded limits (PR #954) Merged #954<#954> into main. — Reply to this email directly, view it on GitHub<#954 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATUUVXOZX7X55PEMUBACSI337TPOZAVCNFSM6AAAAACNCN2M5KVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRRGI4TCNZWGA4DSMA>. You are receiving this because you were assigned.Message ID: ***@***.***>