Using gTec Nautilus amp with P300 speller

This forum deals with BCI2000 configuration issues.
Post Reply
iwalk
Posts: 2
Joined: 14 Nov 2013, 15:31

Using gTec Nautilus amp with P300 speller

Post by iwalk » 28 Sep 2016, 15:59

I'm using the Nautlius amp with BCI2000 and would like to sanity check by completing the P300 speller tutorial.

However, when trying to collect training data, the spelling matrix does not flash. I have isolated that this is related
to the use of the Naulitus bioamp as I've tested the stimulus presentation flashes with the signal generator and the
gUSBamp. I'm trying to determine the proper way to modify the p300 speller demo to use the Nautilus amp.

At present I have simply duplicated P3Speller_gUSBamp and replaced "Start executable gUSBampSource --local" with
"Start executable gNautilusSource --local". However, I'm unsure of what to do for the parameter file. I initially ignored it by
commenting it out. I then attempted to duplicate the param file for the gUSBamp and replacing reference to "gUSBampADC" with "gNautilusampADC". The flashing seems to be prevented due to the module not being able to acquire EEG and timing out for the Nautilus. I have pasted the system log below for reference. I notice in the log that the battery and link levels seems to be off because I fully charged the amp and it's located within 2 feet of the base station.

Any help is greatly appreciated.

System Setup:
Windows 7 (dual boot on Mac)
gNeedAccess (64 bit)
BCI2000 (64 bit)


System Log (when no param file is referenced for gNautilus):
2016-09-28T12:43:37 - BCI2000 Started.
2016-09-28T12:43:37 - Started "gNautilusSource".
2016-09-28T12:43:37 - Started "P3SignalProcessing".
2016-09-28T12:43:37 - SignalProcessing: Waiting for configuration ...
2016-09-28T12:43:37 - Started "P3Speller".
2016-09-28T12:43:37 - SignalSource: Waiting for configuration ...
2016-09-28T12:43:37 - Application: Waiting for configuration ...
2016-09-28T12:43:37 - Loaded parameter file "C:\Program Files (x86)\BCI2000 v3.6.beta.R5388\BCI2000.x64.extensions\prog\../parms/examples/P3Speller_CopySpelling.prm".
2016-09-28T12:43:42 - Operator set configuration.
2016-09-28T12:43:42 - SignalSource error, DataIOFilter::Preflight: gNautilusADC::Preflight:
SamplingRate can currently only be 250Hz or 500Hz.
2016-09-28T12:44:38 - Operator set configuration.
2016-09-28T12:44:41 - Application, P3SpellerTask::Preflight:
Due to a sample block duration of 32ms, the actual value of PreRunDuration for stimulus 1 will be 1984ms rather than 2000ms.
2016-09-28T12:44:41 - Application, P3SpellerTask::Preflight:
Due to a sample block duration of 32ms, the actual value of PostRunDuration for stimulus 1 will be 1984ms rather than 2000ms.
2016-09-28T12:44:41 - SignalProcessing: P3SignalProcessing initialized.
2016-09-28T12:44:41 - Application, P3SpellerTask::Preflight:
Due to a sample block duration of 32ms, the actual value of PreSequenceDuration for stimulus 1 will be 480ms rather than 500ms.
2016-09-28T12:44:41 - Application, P3SpellerTask::Preflight:
Due to a sample block duration of 32ms, the actual value of PostSequenceDuration for stimulus 1 will be 736ms rather than 750ms.
2016-09-28T12:44:41 - Application, P3SpellerTask::Preflight:
Due to a sample block duration of 32ms, the actual value of StimulusDuration for stimulus 1 will be 0ms rather than 31.25ms.
2016-09-28T12:44:41 - Application, P3SpellerTask::Preflight:
Due to a sample block duration of 32ms, the actual value of ISIMinDuration for stimulus 1 will be 32ms rather than 62.5ms.
2016-09-28T12:44:41 - Application, P3SpellerTask::Preflight:
Due to a sample block duration of 32ms, the actual value of ISIMaxDuration for stimulus 1 will be 32ms rather than 62.5ms.
2016-09-28T12:44:41 - Application, ParallelPortFilter::AutoConfig:
No parallel ports detected.
2016-09-28T12:44:41 - Application: P3Speller initialized.
2016-09-28T12:44:45 - SignalSource: GNautilusSource initialized.
2016-09-28T12:44:46 - SignalSource, gNautilusDevice::GetData:
Link Quality fell below 10%.
2016-09-28T12:44:46 - SignalSource, gNautilusDevice::GetData:
Battery Level has fallen below 10%.
2016-09-28T12:44:46 - SignalSource, gNautilusDevice::GetData:
Battery Level has fallen below 5%.
2016-09-28T12:44:47 - Operator started operation.
2016-09-28T12:44:47 - SignalSource: GNautilusSource running.
2016-09-28T12:44:47 - SignalProcessing: P3SignalProcessing running.
2016-09-28T12:44:47 - Application: P3Speller running.
2016-09-28T12:48:15 - SignalSource warning, DataIOFilter::Process: gNautilusADC::Process:
Data acquisition timeout.
2016-09-28T12:48:15 - SignalSource warning, DataIOFilter::Process:
Average block duration is off by more than 5%.
Nominal: 32.0001ms, Actual: 44.671ms.
2016-09-28T12:48:15 - SignalProcessing: P3SignalProcessing suspended.
2016-09-28T12:48:15 - SignalSource warning, DataIOFilter::Process: gNautilusADC::Process:
Write buffer overflow, data loss occurred (current buffer size is 62 blocks == 1.984s), inserting NaNs -- SourceBufferSize is reasonably large, processing may be too slow to keep up with incoming data.
2016-09-28T12:48:15 - Application: P3Speller suspended.
2016-09-28T12:48:15 - Operation suspended.
2016-09-28T12:48:15 - SignalSource: GNautilusSource suspended.
2016-09-28T12:48:15 - SignalSource warning, DataIOFilter::Resting:
Average block duration is off by more than 5%.
Nominal: 32.0001ms, Actual: 30.3248ms.
2016-09-28T12:48:16 - SignalSource error, gNautilusDevice::GetData:
Error: The data ready event hasn't been triggered within a reasonable time.
2016-09-28T12:48:16 - SignalSource error, gNautilusDevice::GetData:
Error on GDS_GetData: Data acquisition is not running.
2016-09-28T12:48:16 - SignalSource error, gNautilusDevice::EndAcquisition:
Error on GDS_StopAcqusition: Data acquisition is not running.
2016-09-28T12:48:16 - SignalSource error:
Lost connection to SignalSource.

pbrunner
Posts: 344
Joined: 17 Sep 2010, 12:43

Re: Using gTec Nautilus amp with P300 speller

Post by pbrunner » 04 Oct 2016, 11:18

Ivan,

the g.Nautilus works well with the P300 speller demo. I see from your log files that you have set the wrong sampling rate though. If you check out the parameter of the gNautilus (see link below) you see that you can only use 250 or 500 Hz as sampling rates. Let me know if this fixes the issue. If not I can help you via a TeamViewer session.

http://www.bci2000.org/wiki/index.php/C ... :gNautilus

Regards, Peter

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest