Percy Zahl

Not wrong, but not the latest any more even I have not bumped up the Version Number since the move. Some new features: back-ports from Gxsm4 related to pyremote and other details are new. And I just made the adjustments for MOVE SPEED for MK3.

I committed the patch to the for some time now official and latest Gxsm3 at GitHub as we moved it over a year ago there -- the SF SVN is absolutely outdated, behind and left as it is: https://github.com/pyzahl/Gxsm3 PS: if you are adventurous you may play even with Gxsm4 (still need to forward patch this fix so), it fully supports the SRMK2/3, but is less tested and may have some issue in details. As we are moving on to a new hardware platform. Read more at https://github.com/pyzahl/Gxsm4

Glad you found it, sorry for the delay, was busy and not checking here. I'll look into patching the SVN accordingly. Now more focused on Gxsm4 and the next gen all new controller RPSPMC! But will do my best to maintain Gxsm3/SR-MK2/3 support.

Yes this is a known "issue". Move Speed calculations assumes or uses the same gain as XY-Scan. If you need a exact move speed, you need to compensate by the ratio between XY Scan vs XY Offset Gain.

added authors mapping

I have seen this one older debian system. This seam to be a desktop integration issue with the system/distro. To my best knowledge this not a Gxsm4 or meson problem. And I also found you can simply ignore it, it seams to work anyways! FAILED: install script '/usr/bin/update-desktop-database -q /usr/local/share/applications' exit code 1, stopped

I have seen this one one older debian/desktop integration issue with the system/distro. To my best knowledge this not a Gxsm4 or meson problem. And I also found you can simply ignore it, it seams to work anyways! FAILED: install script '/usr/bin/update-desktop-database -q /usr/local/share/applications' exit code 1, stopped

I looked up the (ThorLabs) KIM101. Key question is, how are you controlling this? Via python / USB? I do not see any direct trigger or control "input", digital or analog. What could be made to be activated/deactivated at DSP/real time level with some tweaks.. Did you tested that? Key question is the response time here all over and if that is going well at python time scales what is around 20..50ms at best. This not intended to be real time. What do you need or in other words: How fast are you moving...