OpenViBE forum

The OpenViBE community
It is currently Mon Dec 17, 2018 5:22 am

All times are UTC




Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Sat Mar 17, 2018 3:58 pm 
Offline

Joined: Mon Feb 05, 2018 5:40 pm
Posts: 8
I am using Openvibe 2.0.1 for windows with the Emotiv headset. I am aware of the current driver issues, so I changed the ID from 0 to 4096 and built the programs, however the emotiv driver does not appear on the drop down list in the sever acquisition client. Could someone please provide some insight? Any help is appreciated.

-Thanks


Top
 Profile  
Reply with quote  
PostPosted: Tue Mar 20, 2018 10:33 am 
Offline

Joined: Tue Dec 04, 2012 3:53 pm
Posts: 772
Location: INRIA Rennes, FRANCE
Hi Jmann,

the build process needs to be able to discover and use the Emotiv SDK during the build. If the discovery of the SDK works can be seen from the text output the build writes to the console. You may need to tell the build the exact path to your version of the SDK. This can be done by modifying the file

extras/cmake-modules/FindThirdPartyEmotivAPI.cmake

with a text editor.

Hope this helps,
Jussi


Top
 Profile  
Reply with quote  
PostPosted: Tue Mar 20, 2018 10:06 pm 
Offline

Joined: Mon Feb 05, 2018 5:40 pm
Posts: 8
I have made the changes, and use "C:/Program Files/community-sdk-master*" and "C:/Program Files/community-sdk-master/include*" as files paths. That helped quite a bit, and now I have one more error occurring. I have seen these issues in previous posts, but they are on Linux.

Code:
Found Emotiv API 3.x
Found emotiv Research API 3.x
[FAILED] lib Emotiv edk.lib


I have tried to include the path to the Emotiv Lib folder, but to no avail. Am I missing another path?


Top
 Profile  
Reply with quote  
PostPosted: Wed Mar 21, 2018 9:05 am 
Offline

Joined: Tue Dec 04, 2012 3:53 pm
Posts: 772
Location: INRIA Rennes, FRANCE
Hi,

the required lib might be called something else in newer versions. Try to check what other .lib files you have there, and then change the cmakelists.txt to include that library instead of edk.lib. If on the other hand you already see edk.lib, you should give its path in cmakelists.txt to the line of code that tries to find the lib.

Cheers,
Jussi


Top
 Profile  
Reply with quote  
PostPosted: Wed Mar 21, 2018 7:28 pm 
Offline

Joined: Mon Feb 05, 2018 5:40 pm
Posts: 8
I added ${PATH_Candidates} to line 54, and Emotiv now appears on the drop down. Is this what you meant by telling the build the exact path to the version of the SDK?

Code:
FIND_LIBRARY(LIB_EmotivAPI edk PATHS ${OV_EMOTIV_PATHS} ${PATH_Candidates} )


Going forward, I thought by changing the m_ui32UserID from 0 to 4096 in the file "ovasCDriverEmotiv.cpp" would resolve the driver issues as in (viewtopic.php?f=5&t=9825&start=15) for the current emotiv driver to work.
Have I missed a vital step, or does the Emotiv driver not work even with the changes?


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Americanized by Maƫl Soucaze.