You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent versions of the protocol introduced PreSetPos3 and JSSensitivity, added on to the end of 0x520 and 0x522 (set/get) for the kcubemmiparams command. (and two trailing "Reserved" bytes, but I think that can be safely ignored for the time being)
These are documented as only applying to the BBD30x devices. My guess is sending them is not actually a problem for other devices, but perhaps we should maintain them as optional somehow (e.g. default of None, which casues them to not be returned in the set) Certainly parsing should be tolerant of them being missing as the other devices might not actually return them...
Should not be too hard to do... I don't have this hardware (though have a KDC101 on order, so can test out to make sure it continues to work)
Gonna hold off on doing this until I have the hardware, but wanted to document a known change before I forgot
The text was updated successfully, but these errors were encountered:
Migrated from https://gitlab.com/yaq/thorlabs-apt-protocol/-/issues/9 opened by myself
Recent versions of the protocol introduced PreSetPos3 and JSSensitivity, added on to the end of 0x520 and 0x522 (set/get) for the kcubemmiparams command. (and two trailing "Reserved" bytes, but I think that can be safely ignored for the time being)
These are documented as only applying to the BBD30x devices. My guess is sending them is not actually a problem for other devices, but perhaps we should maintain them as optional somehow (e.g. default of None, which casues them to not be returned in the set) Certainly parsing should be tolerant of them being missing as the other devices might not actually return them...
Should not be too hard to do... I don't have this hardware (though have a KDC101 on order, so can test out to make sure it continues to work)
Gonna hold off on doing this until I have the hardware, but wanted to document a known change before I forgot
The text was updated successfully, but these errors were encountered: