Drivers: gtec gMobiLab+ driver

  • NB: Document updated for OpenViBE 1.0.1 (updated 18.sep.2015)

OpenViBE and gMobiLab+

OpenViBE compilation currently cannot support both gTec gUSBAmp and gMobiLab+ in the same Acquisition Server executable. By default, gUSBAmp is preferred in the compilation, if both SDKs are found on the system. The Windows installer of OpenViBE has only gUSBAmp compiled in, as its perceived as the one more often used.

To enable gMobiLab+, you need to recompile OpenViBE. Note that you will need the gMOBIlabCAPI from gtec installed. Once you have this, follow the instructions here. Now, after you have the OpenViBE source code downloaded and extracted, you can proceed with the compilation unless you have gUSBAmp CAPI on the same system. You can disable the detection for gUSBAmp by editing cmake-modules/FindThirdPartyGUSBAmpCAPI.cmake. Add one line at the top,


You can then compile OpenViBE as usually. If everything went well, you should see gMobiLab+ in the Acquisition Server’s driver list.

After compilation, usually the greatest ‘difficulty’ in getting gMobiLab+ working with OpenViBE is actually in pairing the device over bluetooth with your computer. gTec provides instructions for this. Here’s our own executive summary.

On Windows

The usual Windows bluetooth pairing seems to work using the gtec provided PIN. Observe the paired device and take note of its COM port. Enter this to the Acquisition Server driver settings in a format like “//./COM1“, but without the parentheses.

On Linux

First make sure Bluetooth is enabled in the system. Then, for example, using Ubuntu 12.04, the following worked to pair the device,

bash# hcitool scan
# gives some MAC style code XX:XX:XX:XX:...
bash# bluez-simple-agent hci# XX:XX:XX:XX:...
bash# bluez-test-serial XX:XX:XX:XX:...
Connected /dev/rfcomm0 to XX:XX:XX:XX:...

Replace the XX:XX:… with the device id given by hcitool. When asked, enter the PIN code supplied with the amplifier. On Ubuntu 14.04, you can also do the pairing with the graphical bluetooth interface before running bluez-test-serial.

After /dev/rfcomm0 has been successfully connected with your gMobilab, you can start OpenViBE Acquisition Server in another terminal. Note that by default /dev/rfcomm0 might not be accessible by you and the connection fails! If that happens, you can try to start Acquisition server using root priviledges with sudo to address this problem. Alternatively you might give the device wider priviledges.

Happy hacking!

This entry was posted in Documentation, Acquisition Server documentation and tagged , . Bookmark the permalink.