search

labstreaminglayer / App-g.Tec

6 stars 2 forks source link

Three problems about the useage of g.NEEDaccess application #10

Open BiboyLin opened 3 years ago

BiboyLin commented 3 years ago

Hello, Problem 1: When I am using the g.NEEDaccess application, click the "go!" button, it will not turn to "stop", but the streams were made and send to LSL. After clicking the "go!" button many times, there will be lots of inlets found in LSL visualizer, like image And image How to solve this?

Problem 2: And I also wonder how to kill LSL inlet or progress which was formed by the last open g.NEEDaccess application?

Problem 3: The configure of the hardware will not change though the configuration setting was set. Even if I have changed the gHIamp_default.cfg file to customed 64 channels. image

Environment: Software: Self-build gNEEDaccess.exe, Professional Windows 10 Hardware: g.HIamp

cboulay commented 3 years ago

As I no longer have a g.HIamp, I can't do too much to test any changes I might make. I will suggest some things for you to do and hopefully you can test on your own.

Let's start with problem 1 only.

The fact that the streams are getting made tells me that you made it at least to here:

https://github.com/labstreaminglayer/App-g.Tec/blob/master/g.NEEDaccess/src/mainwindow.cpp#L740-L753

But somewhere above or below, success was changed from true to false. Can you identify where success changed? You'll need to use a debugger.

BiboyLin commented 3 years ago

As I no longer have a g.HIamp, I can't do too much to test any changes I might make. I will suggest some things for you to do and hopefully you can test on your own.

Let's start with problem 1 only.

The fact that the streams are getting made tells me that you made it at least to here:

https://github.com/labstreaminglayer/App-g.Tec/blob/master/g.NEEDaccess/src/mainwindow.cpp#L740-L753

But somewhere above or below, success was changed from true to false. Can you identify where success changed? You'll need to use a debugger.

Thanks for your suggestion. After I reboot the Windows, the first time I test the g.NEEDaccess application, the go! button could turn into 'stop'. But after that, the second time I clicked go!, the same issue I described happened again. And the debug output is image And I try disconnect button in this situation, the debug displayed image

cboulay commented 3 years ago

Can you please give me the debug printout from after you click 'stop' on the first time it is running?

BiboyLin commented 3 years ago

Can you please give me the debug printout from after you click 'stop' on the first time it is running?

The first time I click 'go!' and 'stop', the output is image

BiboyLin commented 3 years ago

It seems the problem happened here image Only when I use the custom-built configure file, the wrong message given GDS ERROR 10 GDS_SetConfiguration : Couldn't set configuration for device 'HR-2018.12.01'. The notch filter at the specified index for channel 1 refers to a filter that is not designed for the specified sampling rate of 512 Hz. And then the 'go!' button would not change, but the stream outlet was given, which caused the running problem later.

matzahth commented 3 years ago

I have just started using this app and had a similar issue. The solution that I found had to do with the settings of the notch and the bandpass. The default setting that is selected is not always supported by the rest of the setup, so if you open the drop down menu, you'll notice that some of them are greyed out while others can be chosen. The default choice might actually be one of those greyed out options, but you would never know that until you choose a different setting. Before realizing this issue I too was not getting the stop option and my recordings only had 16 channel instead of the desired 64. Hope this helps.