Pulse Pal not connected?

122 views
Skip to first unread message

Hyunwoo Jang

unread,
Apr 30, 2021, 3:35:48 AM4/30/21
to Open Ephys
Hi all, I am using open ephys 2.0 and pulse pal 2.1.
Both devices are properly installed and all softwares are setup.
I am trying to control Pulse Pal within the Open Ephys GUI,
However the plugin says Pulse Pal is not connected.
Do anyone know how to resolve this issue?

Thank you in advance.


화면 캡처 2021-04-30 163409.png

Josh Siegle

unread,
Apr 30, 2021, 2:11:31 PM4/30/21
to Open Ephys, Hyunwoo Jang, Josh Sanders
Hi Hyunwoo,

Unfortunately, I don’t have a Pulse Pal on hand for troubleshooting at the moment, so I’m cc’ing Josh Sanders (creator of the Pulse Pal). Josh, is there anything in this initialization code that could be causing problems with Pulse Pal v2? Would you be able to try connecting to one of your Pulse Pals via the GUI, and see if it works?

Josh


On Apr 30, 2021, at 12:35 AM, Hyunwoo Jang <jang...@gmail.com> wrote:

Hi all, I am using open ephys 2.0 and pulse pal 2.1.
Both devices are properly installed and all softwares are setup.
I am trying to control Pulse Pal within the Open Ephys GUI,
However the plugin says Pulse Pal is not connected.
Do anyone know how to resolve this issue?

Thank you in advance.


<화면 캡처 2021-04-30 163409.png>

--
You received this message because you are subscribed to the Google Groups "Open Ephys" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-ephys+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-ephys/f6ac8ab0-9db9-491a-aa2a-84377622bca1n%40googlegroups.com.
<화면 캡처 2021-04-30 163409.png>

Josh Siegle

unread,
Apr 30, 2021, 8:35:52 PM4/30/21
to Josh Sanders, Open Ephys, Hyunwoo Jang
Thanks for testing that out!

Could it be the same problem that was identified in this issue? https://github.com/open-ephys/plugin-GUI/issues/371

In that case, a (temporary) fix would be to try plugging the device into a different USB port.

Josh


On Apr 30, 2021, at 4:19 PM, Josh Sanders <jo...@sanworks.io> wrote:

Hi Josh,

I downloaded the latest GUI. With a Pulse Pal connected, I dragged the Pulse Pal sink into the signal chain. The debug console shows:

Searching for Pulse Pal...
ofSerial: unable to open portError: Could not find a device.

It has been a while since I viewed the code - the PulsePal::initialize() method in our repo requires a user-supplied serial port argument, but the Open Ephys plugin was improved with an auto-discovery loop (lines 101-114). If I'm reading the code correctly, the loop has ofSerial open each serial port in a list of detected ports, and try to retrieve a firmware version with getFirmwareVersionFromPulsePal(). I could imagine this failing if serial.getDeviceList() is returning hardware other than serial ports (my device manager shows only Pulse Pal on COM21 under 'Ports (COM & LPT)'. Is there any chance the latest version of the Open Ephys GUI is using a new version of ofSerial that isn't backwards compatible? It's also possible that the changes in Windows 10 require an update to the latest version of ofSerial. I'll try to look into this more this week (I'll need to set up visual studio, admittedly!) In a future version of the plugin, it may be useful to include a user-provided serial port name in the sink UI, in case auto-discovery fails.

All the best,

Josh Sanders


Hyunwoo Jang

unread,
Jun 3, 2021, 5:57:14 AM6/3/21
to Open Ephys
Hi, thanks for your help.
I changed the port of Pulse Pal to COM2 and COM14 (it was originally set to COM11) but no vail. Reconnecting to another USB port also did not work.
I also found that debug console is emitting ofserial error as below.
Do you have any ideas on this issue? Thank you.

화면 캡처 2021-06-03 185542.png

2021년 5월 1일 토요일 오전 9시 35분 52초 UTC+9에 josh....@gmail.com님이 작성:

Josh Siegle

unread,
Jun 3, 2021, 1:11:02 PM6/3/21
to Hyunwoo Jang, Josh Sanders, Open Ephys
Any ideas about what could be going on, Josh?

On Jun 3, 2021, at 2:57 AM, Hyunwoo Jang <jang...@gmail.com> wrote:

Hi, thanks for your help.
I changed the port of Pulse Pal to COM2 and COM14 (it was originally set to COM11) but no vail. Reconnecting to another USB port also did not work.
I also found that debug console is emitting ofserial error as below.
Do you have any ideas on this issue? Thank you.

To view this discussion on the web visit https://groups.google.com/d/msgid/open-ephys/028843ef-4774-49c5-adc3-aec565f6e830n%40googlegroups.com.
<화면 캡처 2021-06-03 185542.png>

Josh Siegle

unread,
Jun 7, 2021, 3:30:37 PM6/7/21
to Josh Sanders, Buccino Alessio Paolo, Hyunwoo Jang, Open Ephys
@josh – make sure you include two dots after the CMake command, to indicate that the CMakeLists.txt is one directory up:

cmake -G "Visual Studio 16 2019" -A x64 ..

Let me know if that works!

If you’re still stuck after running in Debug mode, we can get in touch with Alessio.

On Jun 7, 2021, at 12:02 PM, Josh Sanders <jo...@sanworks.io> wrote:

Hi Josh,

I'm honestly not sure, beyond what I suggested earlier.
I need the code in a debugger to be more helpful.
I installed Visual Studio 2019 and Cmake and tried to run Cmake as per this, but I got an error:
CMake Error: The source directory "C:/Users/Josh/Desktop/plugin-GUI-master/Build" does not appear to contain CMakeLists.txt.

I copied CMakeLists.txt from the root folder into the Build folder and reran, but it crashed with this:
CMake Error at CMakeLists.txt:18 (message):
  Please run cmake inside the Build folder to build the binaries in the
  predefined paths.

Any help would be appreciated.

Also, who is Alessio Buccino? He seems to have made changes to the self-discovery code that is crashing.

Thanks,

Josh Sanders


Josh Siegle

unread,
Jun 9, 2021, 7:36:51 PM6/9/21
to Josh Sanders, Buccino Alessio Paolo, Hyunwoo Jang, Open Ephys
Thanks for figuring this out! We will include the ofSerial changes in the next release.

Hyunwoo, please let us know if renaming the device to COM5 fixes the issue!

Josh


On Jun 8, 2021, at 10:06 AM, Josh Sanders <jo...@sanworks.io> wrote:

Hi Josh and Hyunwoo,

I managed to get the source installed, and I think I've identified the issue (also the solution to issue# 371)
The Open Ephys GUI failed to detect my device at port COM13.
As of Windows update# KB115831, serial ports above COM9 need to be named \\\\.\\COMN where N is the port number.
OfSerial has this update in their latest code - but the latest code has a zillion new OfSerial dependencies - so it was simpler to mod what we have.
I updated ofSerial.cpp (attached) to use the correct port naming scheme, and tested it with ports below and above COM9.
The file to update is in the repository here: \plugin-GUI-master\Source\Processors\Serial\

Hyunwoo, I suspect that your port renaming experiment may have failed because COM2 is generally reserved by Windows (new devices start enumerating at COM3) and COM14 was above COM9.
As a quick experiment, if you rename the device to COM5, does it run?
In case you had some other way of doing it, I renamed from Device Manager > Ports (COM & LPT) > Arduino Due (COMX) > Port Settings > Advanced > 'COM Port Number' drop menu on the bottom

Thanks,

Josh Sanders

On Mon, Jun 7, 2021 at 5:22 PM Josh Sanders <jo...@sanworks.io> wrote:
Hi Josh,

Tried it, but no dice:

C:\Users\Josh\Desktop\plugin-GUI-master\Build>cmake -G "Visual Studio 16 2019" -A x64 ..

CMake Error at CMakeLists.txt:18 (message):
  Please run cmake inside the Build folder to build the binaries in the
  predefined paths.

  Set the OE_DONT_CHECK_BUILD_PATH cmake variable to TRUE to disable this
  error


-- Configuring incomplete, errors occurred!

C:\Users\Josh\Desktop\plugin-GUI-master\Build>

What should I try next?

Josh Sanders


Reply all
Reply to author
Forward
0 new messages