Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Check lock on LabBricks on connect #25

Open
caryan opened this issue Feb 19, 2015 · 4 comments
Open

Check lock on LabBricks on connect #25

caryan opened this issue Feb 19, 2015 · 4 comments
Assignees
@caryan

Comments

@caryan
Copy link
Contributor

caryan commented Feb 19, 2015

Not sure if the API allows this but we've wasted many hours with strange behaviour that we eventually track down to an unlocked LabBrick.
@caryan caryan self-assigned this Jun 19, 2015
@caryan
Copy link
Contributor Author

caryan commented Jun 19, 2015

Bump! Caused hours of grief yet again....

caryan added a commit that referenced this issue Jun 22, 2015
@caryan
Merge pull request #31 from BBN-Q/hotfix/labbrick_lock
8d5383a 
Test for Labbrick PLL lock. Closes #25.
@caryan
Copy link
Contributor Author

caryan commented Jun 22, 2015

Closed by 8d5383a

@caryan caryan closed this as completed Jun 22, 2015
@dieris
Copy link
Collaborator

dieris commented Sep 30, 2015

LabBrick gets unlocked between the check and the time the experiment starts. The error is therefore caught too late. After check and error message, the lock gets fixed again.
In other words, for consecutive experiments: 1) locked; 2) locked ... N) unlocked ERROR/WARNING at the beginning of N+1; N+1) locked ...

@dieris dieris reopened this Sep 30, 2015
@caryan
Copy link
Contributor Author

caryan commented Oct 1, 2015

Maybe we could recheck after setAll. That's the last point we touch this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@caryan caryan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@caryan @dieris