Some notes on Contec KT88 EEG amplifier
Posted on: 23/01/2011
- In: Projects | Software
- 7 Comments
I’ve just posted that old program to read data from KT88-1016 amplifier here:
http://tech.groups.yahoo.com/group/conteckt88/files/
- look for file named eegRead.zip
It’s written in C++ and should complie without problems with Borland C++ Builder 6.0 – which can be downloaded from torrent.
Also, I threw there a OpenViBe driver sketch - kt88-1016-openvibe.zip – to use Contec KT88 with OpenViBe BCI software. Disclaimer: It has only basic functionality and some features like configuration still has to be done.
7 Responses to "Some notes on Contec KT88 EEG amplifier"
Dear Alexandra,
thank you for posting this contribution on your blog. There are a couple of users on the OpenViBE forum looking forward for such code to start with. Even if not totally finished, this is a good piece of work that other users can start hacking. Do you mind if I forward it to our forum ?
Best regards,
Yann
Dear Alexandra,
actually, you know that OpenViBE is L-GPL v2+. So putting this code in the official release (even after a user modifies it) requires that L-GPL v2+ is adopted. I encourage you to chose this license
Please contact me when the license choice is made so I can spread your code on the OpenViBE forum appropriately.
Best regards,
Yann
Alexandra Elbakyan
Brain-Computer Interfaces group at TheNeuroNetwork
23/01/2011 at 6:36 PM
Thanks so much for posting the OpenViBE driver. Would this driver require modifications in order to use it with KT88 systems that have different numbers of channels?
24/01/2011 at 9:44 AM
Sure
Right now, even COM port name is hardcoded – the driver expects the device to hang on the COM3 port, while it can be anywhere – COM4, COM5 etc. Number of channels is predefined too.
But it shouldn’t take that much effort to create a GUI interface that will allow to specify these values without recompiling (probably, I even will do it later in free time…) – and OpenViBe documentation describes how to make the GUI step-by-step.
Apart from COM port name / numbers of channels, different device models may require different sequences of bytes to control the device. These control bytes can be captured with any software for monitoring serial ports, so they won’t be a serious obstacle too.