-
Notifications
You must be signed in to change notification settings - Fork 24
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
LDD driver initialization err #29
Comments
No, for TEC controller it is 2051. For laser driver boards (LDD family) it is 3040. What addresses do you refere to? Multiple hosts can be addressed by multiple instances and do NOT require unique settings for the parameter id 3040 (or 2051) e.g.: If your boards are connected via RS485 they need unique settings for parameter id 3040 (or 2051). You connect to a single host and add the address to the communication, e.g.: |
@jscman thx for the response! That what I tried from the example code given, but it does not execute properly on the ldd1301. I even used the command tool and sent serial to the device and I got a parameter not available response: Let me know if there is something I'm missing here. |
Ah, I see. It looks like this is related to some of the newer meerstetter boards having different commands. There was a similar issue with the (LDD-1321) which was solved by a metype = "LDD-1321". |
The example code is specific to the LDD-112x family. I have renamed the example from example_LDD.py to example_LDD_112x.py to make this clearer. There should also be a 'LDD-130x' metype now. |
ldd parameter device address is incorrect in commands, i think it should be 2051 instead of 3040
also example code does not mention how to initialize multiple ldd objects with different addresses (which may cause errors)
The text was updated successfully, but these errors were encountered: