2 axes Thorlabs.KinesisMotor - only one axis moves

[Saldenisov]

I do stage init like this.

stage = Thorlabs.KinesisMotor(str(self.serial_num))
stage.open()
stage.set_supported_channels(2)
print("Enabled channels:", stage.get_all_channels())

I will get two active channels.

To move axes I use this code

# Move X-axis
print(f"Moving X-axis to {x_new} mm")
stage.move_to(x_new * scaling_factor, channel=2, scale=True)
stage.wait_move(channel=2, timeout=move_timeout)
x = stage.get_position(channel=2, scale=True) / scaling_factor
print(f"X-axis moved to: {x}")

# Move Y-axis
print(f"Moving Y-axis to {y_new} mm")
stage.move_to(y_new * scaling_factor, channel=1, scale=True)
stage.wait_move(channel=1, timeout=move_timeout)
y = stage.get_position(channel=1, scale=True) / scaling_factor
print(f"Y-axis moved to: {y}")

The X-axis does not move, but the stage.get_position will give me the correct value.
The Y-axis moves.

What could be the issue?

[AlexShkarin]

Hi!

Could you specify the model of the motor and the driver, and what are the positions between which you are trying to move? And can you check if it works from the native Kinesis software for the same axis and positions?

I can think of several possiblities here:

• the driver can not move the motor, e.g., it is blocked or damaged
• the driver output is off (i.e., it is disable); this is especially likely for stepper motor drive,rs which might simply count the number of pulses which they are supposed to output without checking if the current is on and the output is connected to something
• the initial and final positions are too close to each other, so the motion is not noticeable

Let me know if any of these seem likely.