ActiChamp and BCI2000 new version

This forum deals with BCI2000 configuration issues.
cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

ActiChamp and BCI2000 new version

Post by cmontilla » 15 Sep 2026, 06:58

I am trying to use my ActiChamp amplifier with the new version of BCI2000 that I compiled (version 3.6.9546).

However, when I click "Set Config," I get the following error in Operator Module:

2026-09-15T11:22:32.253 - SignalSource warning, DataIOFilter::Resting: actiCHampBufferedADC::Process:
Data acquisition timeout.
2026-09-15T11:22:32.261 - SignalSource error:
Lost connection to SignalSource.

I am using the same parameter file as in version 3.6.7385, which is the one I used previously. (I have tried configuring the parameters manually, but the same error keeps appearing.)

Any suggestions are welcome.

Thanks

mellinger
Posts: 1360
Joined: 12 Feb 2003, 11:06

Re: ActiChamp and BCI2000 new version

Post by mellinger » 15 Sep 2026, 09:20

Thanks for your helpful bug report.
I found and fixed an issue that is related to your problem, but I could not test because I don't have an ActiChamp available.

Please update to the latest SVN version and recompile.

cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

Re: ActiChamp and BCI2000 new version

Post by cmontilla » 16 Sep 2026, 04:34

I try to test and I get the following error now:


2026-09-16T10:30:46.840 - Application: P3Speller initialized.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.388 - SignalSource warning, DataIOFilter::Resting: actiCHampBufferedADC::Process:
Data acquisition timeout.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.388 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.389 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 0.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 1.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 2.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 3.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 4.
2026-09-16T10:30:50.390 - SignalSource error, actiCHampDevice::output_data:
Error in module 5.
2026-09-16T10:30:50.398 - SignalSource error:
Lost connection to SignalSource.

mellinger
Posts: 1360
Joined: 12 Feb 2003, 11:06

Re: ActiChamp and BCI2000 new version

Post by mellinger » 16 Sep 2026, 05:59

It seems your ActiChamp device reports hardware errors.

Which ActiChamp model are you using?

Can you use the vendor software to make sure the device works as intended?

cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

Re: ActiChamp and BCI2000 new version

Post by cmontilla » 16 Sep 2026, 06:25

It is the 32-channel ActiChamp (not the Plus version).
I have used it, I have a program (BrainVision Pycorder) where I view the signal being recorded in real time, and the amplifier works correctly.
It works properly in BCI2000 version 3.6.7385.
The only thing is that I added the filter module exactly as explained here: (in BCI2000 version 3.6.7385 works)

https://www.bci2000.org/mediawiki/index ... urceFilter

mellinger
Posts: 1360
Joined: 12 Feb 2003, 11:06

Re: ActiChamp and BCI2000 new version

Post by mellinger » 16 Sep 2026, 12:41

It might be that you compiled BCI2000 in debug mode, whereas r7385 was built in release mode.
Certain bugs may show up in debug mode rather than release mode (and vice versa).

Could you rebuild the ActiChamp source module in release mode and try again?

cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

Re: ActiChamp and BCI2000 new version

Post by cmontilla » 17 Sep 2026, 05:08

Yes, I have rebuild in release mode, now I see the new error:

Short read, data will be invalid.
Lost connection to SignalSource.

mellinger
Posts: 1360
Joined: 12 Feb 2003, 11:06

Re: ActiChamp and BCI2000 new version

Post by mellinger » 17 Sep 2026, 08:14

That's quite interesting, I didn't think this error message would be triggered.
I've expanded the message a bit, could you update and run again and report the expanded error messsage?

Thanks!

cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

Re: ActiChamp and BCI2000 new version

Post by cmontilla » 17 Sep 2026, 08:41

Of course!!

Short read, data will be invalid, requested: 2688, received: 0.


Thank you very much for your patience.

mellinger
Posts: 1360
Joined: 12 Feb 2003, 11:06

Re: ActiChamp and BCI2000 new version

Post by mellinger » 17 Sep 2026, 09:14

It might work now.

cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

Re: ActiChamp and BCI2000 new version

Post by cmontilla » 18 Sep 2026, 04:14

I'm getting the error again:
Lost connection to SignalSource.

Could it be due to my .prm file? Although I get that error with the default configuration as well... (I try in release and debug mode)

mellinger
Posts: 1360
Joined: 12 Feb 2003, 11:06

Re: ActiChamp and BCI2000 new version

Post by mellinger » 18 Sep 2026, 05:43

You might experiment with different values of the SampleBlockSize parameter.

Could you provide me with the error message prior to "Lost connection to SignalSource"?

cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

Re: ActiChamp and BCI2000 new version

Post by cmontilla » 18 Sep 2026, 06:11

2026-09-18T12:08:28.688 - BCI2000 Started.
2026-09-18T12:08:29.069 - SignalProcessing: Waiting for configuration ...
2026-09-18T12:08:29.100 - SignalSource: Waiting for configuration ...
2026-09-18T12:08:29.186 - Application: Waiting for configuration ...
2026-09-18T12:09:54.480 - Operator set configuration.
2026-09-18T12:09:55.586 - SignalSource: ActiCHampSource initialized.
2026-09-18T12:09:55.596 - SignalProcessing: P3SignalProcessing initialized.
2026-09-18T12:09:56.355 - Application: P3Speller initialized.
2026-09-18T12:09:58.018 - SignalSource error:
Lost connection to SignalSource.

I'm trying out other combinations to see if I can share some news soon.

Thank you very much.

mellinger
Posts: 1360
Joined: 12 Feb 2003, 11:06

Re: ActiChamp and BCI2000 new version

Post by mellinger » 18 Sep 2026, 09:20

I fixed another bug, maybe you want to give it a try.

cmontilla
Posts: 24
Joined: 29 May 2026, 05:05

Re: ActiChamp and BCI2000 new version

Post by cmontilla » 19 Sep 2026, 11:45

I keep getting the same error in the Operator log in the release mode....

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests