Update Tiger Controller Stage Commands#1114
Conversation
Now retrieve current settings before by default changing them. Goal is to modify settings as little as is possible. And importantly, greatly reduce the maximum speed...
|
After testing, now both the X and Y stages are jumping. Previously, it was only the Y stage (the X-stage was okay). The log files now state the following: 2025-07-16 09:34:27,683 - model - DEBUG - asi: ASI Stage - Current Feedback Alignment for X is 85.0 |
|
Reviewing old notes. Currently, our software does the following:
Previous e-mails... We are seeing some aggressive flyback and poor settling, and I was trying to rule out what was causing it. I think some of the stage parameters can be optimized. However, the one hint I am thing to out is why we don’t see the oscillation in the virtual joystick, but do see when we send the MOVE command either via navigate or via the tiger controller software. |
|
Checking on the Expansion microscope. The horizontal stage movement for the FTP-2000 is good. For this microscope, that is defined as Z and Y. It is the focus stage that has a problem, which for the FTP-2000, would be the equivalent of their Z stage. INFO Z: INFO X Our current parameters on the microscope, after booting our software (shown in logs): |
|
Yesterday, we learned that with the FTP-2000 stages, that some tuning parameters are automatically passed to the F axis if they are changed on the Z axis, but not all. We had set the backlash for the Z stage to 0, which is what we want, but the F axis was still operating with a backlash, causing the two stages to fight against one another a bit. I'm thinking maybe we need to create yet another class that is specific for the FTP-2000 stages. Or, we need to find a way to query the stages and see if they are linked or not, and then handle that behavior appropriately. |
|
Proposed fix. Rather than creating an FTP-2000 class, which just adds to the configuration uncertainty, we will ping the stage with |
|
Finally following up with @EvoleneP. Y stage currently shows the jitter/backlash behavior where you initiate a move and it jumps. The X axis seems to be perfectly fine. 
|
|
|
|
Scan optimized stages often have a large overshoot, so often it is set to have a backlash of -0.1 to offset the overshoot for large scan ranges. In @EvoleneP's case, she did not have scan optimized stages, but the firmware was configured in a scan-optimized format. Setting the backlash to 0 (it was -0.1), fixes the issue. |
2 participants
Now retrieve current settings before by default changing them. Goal is to modify settings as little as is possible.
And importantly, greatly reduce the maximum speed...
@EvoleneP - Please test this on your system before we meet.