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

Implicit FMCLinkController configuration in e.g. ConfigureHeadstage64 is not registered #40

Closed
jonnew opened this issue Jan 23, 2024 · 0 comments · Fixed by #41
Closed

Implicit FMCLinkController configuration in e.g. ConfigureHeadstage64 is not registered #40

jonnew opened this issue Jan 23, 2024 · 0 comments · Fixed by #41
Labels
bug Something isn't working

Comments

@jonnew
Copy link
Member

jonnew commented Jan 23, 2024

In the following workflow, FMCLinkController is implicity configured by HS64 (ConfigureHeadstage64). However, it is not registered in as a subject there. This means that another conflicting ConfigureFMCLinkController node can be placed in series with HS64 without error. Additionally, the FMCLinkController device is not a member of the HS64's device subscription set, so getting Port status information from it is not currently possible.

image
@jonnew jonnew added the bug Something isn't working label Jan 23, 2024
@glopesdev glopesdev mentioned this issue Jan 23, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Provide reusable hub device naming strategy open-ephys/bonsai-onix1
1 participant
@jonnew