-
Notifications
You must be signed in to change notification settings - Fork 22
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
Support for KST101 #14
Comments
Hello! I'm glad that my code is useful. The first message is due to the fact that the KST101 controller is not a "known" stage in my detection code. Try adding somewhere elif controller_type in (26,):
return 'KST101' Tell me what happens then. Cheers, |
Hey Laurent, many thanks for your really fast response!! Thats really awesome and really helpful. Many thanks for any help. Cheers, |
Hello! Simply try to find an updated Laurent |
Dear Laurent, many thanks for your input. This partially solves the problem. Unfortunately I still get an error (while the code can read the position, so there is a connection). I used the test.py. Constructed: SingleControllerPort('/dev/ttyUSB0',26001669) During handling of the above exception, another exception occurred: Traceback (most recent call last): Do you have any idea what would have to be changed? Many thanks in advance. |
I'll have a look on Monday (I don't have a Windows computer at home), to see if an updated configuration file can help. Unfortunately I don't have the hardware... Can you post your modified version somewhere? (a github repository would do) |
I just made a fork with my changes (I hope you can access it). Sorry I am not an Git expert. The code as it is works with the other stages, but not yet with the KST101. |
Ok, so I've had a look in the software. Let's try the following: In If it works, I suggest doing instead the following: First, edit to add 26 to the line: elif controller_type in (27, 63, 83, 2197): to get: elif controller_type in (26, 27, 63, 83, 2197): Then you should add a sub-condition to detect the correct type. Unfortunately it won't work with the same logic, because it doesn't seem that it uses the same methods as the TDC for stage detection. Let me know? |
Thanks!! So when I did the first (exchange of KST101 into ZST213(B)), it gave me:
so it worked (it recognized the ZST213(B), e.g. I could also move it with s.position. But the parameters were all wrong (not corresponding to the MG17APTServer file. I then added '26' as described and included:
So I think if I get the sub-condition right, it should work. Can you help? |
Hello, |
@lucduempelmann, would you be willing to help me get things going? I've tried on both Windows and Mac and can't seem to get the device to be discovered (trying with a KDC101). |
Hi, sure, I am happy to help! I didn't test for the KDC101 yet, but will do that next week and let you know.
I assume you download and used my modified version (from 29.10.18), right? This was working fine for me, until I received some new KST101 stages, which couldn't be detected/controlled. Somehow I assume due to a new serial number, the controller_type was not 26 anymore but 4294 (which had to be added in the code). Then it worked again. Maybe you have this problem. I will update this updated version next week.
|
I was able to get it working on my mac by replacing pyserial with pylibftdi. However, the status_homed property always returns true. I am using your updated server file but that still does not help. |
Hi Knoose, so I checked the software with the KDC101 and a Z812B actuator and everything works nicely. But I am using it on Linux. I also tried Windows, but this didn't work for me due to the libraries etc. But maybe this could be fixed, will give an update. |
Hello,
your code really works great for the old APT controller, and also for the KDC101. So many thanks for this, it has really been a great help!!!
Now we need to work with the stepper controller KST101 and actuator ZST213. Although it recognizes something, and also displays the current position (so the connection is there), there is an error message displaying:
Constructed: SingleControllerPort('/dev/ttyUSB1',26001669)
If you see this message, please send a mail with the following information:
- controller type
- stage type
- this data: <MGSG_HW_GET_INFO>(dest=0x1, src=0x50, serial_number=26000000, model_number=b'KST101\x00\x00', type=16, firmware_version=b'\x07\x00\x01\x00', notes_b'KST101 Stepper Controller v 3.1 1\x00', empty_space=b'162009Nov\x00\x00\x00', hw_version=3, mod_state=32, nchs=1)
Unhandled message <MGMSG_MOT_GET_STATUSUPDATE>(dest=0x1, src0x50, chan_ident=1, position=0, enc_count=0, status_bits=2147483648)
Destructed: <None on SingleControllerPort('/dev/ttyUSB1', 26001669) channel 1>
Destructed: SingleControllerPort('/dev/ttyUSB1', 26001669)
Unhandled message <MGMSG_MOT_GET_STATUSUPDATE>(dest=0x1, src0x50, chan_ident=1, position=0, enc_count=0, status_bits=2147483648)
Unhandled message <MGMSG_MOT_GET_STATUSUPDATE>(dest=0x1, src0x50, chan_ident=1, position=0, enc_count=0, status_bits=2147483648)
Unhandled message <MGMSG_MOT_GET_STATUSUPDATE>(dest=0x1, src0x50, chan_ident=1, position=0, enc_count=0, status_bits=2147483648)
.....
.....
this message display until I switch off the controller.
Do you know if something in the code has to be adapted, so we can use this stage? Many thanks for any inputs / help.
Best,
Luc
The text was updated successfully, but these errors were encountered: