Jennie W

Summary: I didn't move M_M2  picomotor on Friday 17th July.

Last Friday (LHO alog #91124) I centred the QPDB on HAM3 spi bench using M_C1 picomotor (picomotor B  ch7 which is controller 5) on HAM2.

I wrote the log the week after and checking back in the H1:SYS-MOTION_C_PICO_G_CURRENT_X_POSITION I thought I had also moved M_M2 (CH7) on picomotor driver G.

Checking back it turns out the 2000 count jump I was seeing was just the 2000 count difference between the values stored for ch8 and ch7 when I switched the selected motor to channel 7.

See the ndscope picture where the second cursor shows when the green channel H1:SYS-MOTION_C_PICO_B_SELECTEDMOTOR changed from 8 to 7 and you can see that the the yellow channel H1:SYS-MOTION_C_PICO_B_CURRENT_X_POSITION changed up by 2000 counts.

Looking at the Beckhoof screen you can see that when ch8 is selected this stored value (-2000) appears on the screen and is not there when ch7 is selected. I mistakenly thought these were reset when the selected motor was changed.

So no re-alignment of M_M2 is needed.