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.

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

New version of GUI not recognizing the old Acquisition board #577

Open
HiroyukiKato7 opened this issue Jul 7, 2023 · 8 comments
Open

New version of GUI not recognizing the old Acquisition board #577

HiroyukiKato7 opened this issue Jul 7, 2023 · 8 comments

Comments

@HiroyukiKato7
Copy link

HiroyukiKato7 commented Jul 7, 2023

We have been using Open-Ephys 4.5 plugin GUI without any issues. However, when we updated the GUI to the latest version, it failed to recognize our Open-Ephys Acquisition board. We rolled back the GUI to the old 4.5 version, and it works without a problem.
Is there a compatibility issue between the new GUI versions and the old acquisition boards? My board was purchased back in September 2018. We run the GUI on Windows 10.

@jsiegle
Copy link
Member

jsiegle commented Jul 7, 2023

Just to check – are you using the Acquisition Board plugin from the "Rhythm Plugins," and not the "OE FPGA Acquisition Board" plugin?

@HiroyukiKato7
Copy link
Author

Yes, we have been using Rhythm FPGA Plugin. Do we need to switch for the new GUI?

@jsiegle
Copy link
Member

jsiegle commented Jul 7, 2023

In the latest version, the required plugin can be accessed by first installing the "Rhythm Plugins" via the Plugin Installer (ctrl-P), or selecting the default configuration (ctrl-D) for the Acq. Board. The plugin is now called "Acquisition Board" rather than "Rhythm FPGA." If you've already done those things, let us know.

@HiroyukiKato7
Copy link
Author

Thanks! Now it recognizes the board. However, I have a problem setting up the new GUI.
I have 2*64 channel probes connected to the board. When I chose to save 128 channels plus two ADC, as you see in the attached screenshot, somehow the GUI saves ADC1-3 and ch2-128. So, it saves ADC3 instead of ch1. Do you have any idea why this happens? It may be related to issue #438, but I am not sure.

screenshot

@jsiegle
Copy link
Member

jsiegle commented Jul 7, 2023

Can you double-check the ordering of the channel map? For example, it looks like channel 129 (ADC1) is mapped to channel 96. I think you only want to be reordering channels 1-128, and leaving the ADCs (129-136) in the original order.

@HiroyukiKato7
Copy link
Author

Oh, you are right. It's weird, but it seems that all the values in the channel map shifts by 1 when I load the map that we used to use for GUI ver 4.5. Has there been a change regarding something like 0-indexing?

@jsiegle
Copy link
Member

jsiegle commented Jul 7, 2023

The channel map JSON files have been simplified, but I believe the indexing conventions should be the same as before. The latest format is documented here: https://open-ephys.github.io/gui-docs/User-Manual/Plugins/Channel-Map.html#saving-and-loading-channel-mappings

@HiroyukiKato7
Copy link
Author

It seems that our older map starts at 1, instead of 0 in the current version.
Anyway, this solved my problems. Thanks for your prompt answers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants