-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choosing device by serial number? #130
Comments
Actually there is a field called
But it seems that this is only used on Windows, through the module tdc_001.py . On Linux, the apt.py module is used instead, and there is no access to the serial number. (Should not this be documented?)
Another confusing attribute is this, which obviously relates to the virtual serial port over USB:
But the "id" number changes upon each re-connection of the device. What I expect is the access to the 8-digit number recorded permanently into, and printed on, each Thorlabs' controller. |
OK, I can see in the But issuing a command that explicitly calls it,
only gives the following result: These bytes contain no unique serial number. Both my controllers report exactly the same. A solution for Linux: Until a fix is issued, apparently the only reliable source of serial number is in the USB descriptor. This can be filtered as such:
|
The above PR fixes this simply by exposing the serial number to the end user. If the PR is merged, this issue will be solved. |
In my experiment, I use X-Y positioning with two Thorlabs TDC001 servo controllers. Of course, it is essential to identify X and Y axes correctly by controller serial number, so that the program never swaps them at startup. This could lead to crashes.
But I cannot find out how to achieve this with instrumental.
Apparently, there is no access to the serial numbers. Should I dig into the code and try to reimplement similar functionality regarding serial numbers as found e.g. in https://github.com/felix92/thorpy (though that module imports
usb.core
to read the serial number contained in the USB device descriptor)?The text was updated successfully, but these errors were encountered: