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
But we have experienced times when this configuration is wrong (how?) and the object needs to be initialized with pb_board_number = 0. It is unknown why this happens and the error message from the underlying driver is unhelpful.
We need to document this or we can work around this problem by trying to initialize communicatons with the PB board with 0 and 1 and simply use the value that doesn't throw an error!
That is, we would put a try/except around this code and try different values of pb_board_number
Sometimes it seems that the pb_board_number for the pulse blaster hardware changes!
In the past we have initializes PulseBlaster objects with pb_board_number = 1
But we have experienced times when this configuration is wrong (how?) and the object needs to be initialized with pb_board_number = 0. It is unknown why this happens and the error message from the underlying driver is unhelpful.
We need to document this or we can work around this problem by trying to initialize communicatons with the PB board with 0 and 1 and simply use the value that doesn't throw an error!
That is, we would put a try/except around this code and try different values of pb_board_number
https://github.com/qt3uw/qt3-utils/blob/main/src/qt3utils/pulsers/pulseblaster.py#L51
This would become problematic, however, if we ever need to communicate with the PB over both board numbers simultaneously.
The text was updated successfully, but these errors were encountered: