Contributions:BioPacLogger - Revision history

Mellinger: /* Synopsis */

2025-07-01T13:49:51Z

Synopsis

← Older revision		Revision as of 13:49, 1 July 2025
Line 1:		Line 1:
	==Synopsis==		==Synopsis==
	The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier.<br><br>		The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier.<br><br>
	In this wiki, we will discuss implementing the MP160 as a BCI2000 logger.		On this wiki page, we will discuss implementing the MP160 as a BCI2000 logger.

	==Location==		==Location==

Lingling: /* Video Overview */

2023-10-06T14:42:14Z

Video Overview

← Older revision		Revision as of 14:42, 6 October 2023
Line 16:		Line 16:
	==Video Overview==		==Video Overview==
	<br>		<br>
	<youtube alignment="center" dimensions="900"></youtube>		<youtube alignment="center" dimensions="900">https://youtu.be/fPQDVUc3yPA</youtube>
	<br>		<br>

Lingling: /* Hardware Set Up */

2023-10-06T14:40:05Z

Hardware Set Up

← Older revision		Revision as of 14:40, 6 October 2023
Line 41:		Line 41:

	==Hardware Set Up==		==Hardware Set Up==
	Figure 1 shows all the necessary hardware from MP160. Make sure you have the MP160 and a wireless amplifier, the power supply for the MP160, an Ethernet USB adapter, and an Ethernet cable that can connect your MP160 with the BCI2000 PC. You will also need the Windows BCI2000 PC that will be running BCI2000. The hardware connection is simple(Figure 2). Using the Ethernet cable, plug one end into the MP160 and the other end into the Ethernet USB adapter. Then connect the adapter to the BCI2000 PC. Alternatively, if your PC has an Ethernet port, you could directly connect the PC with the MP160 using an Ethernet cable.		Figure 2 shows all the necessary hardware from MP160. Make sure you have the MP160 and a wireless amplifier, the power supply for the MP160, an Ethernet USB adapter, and an Ethernet cable that can connect your MP160 with the BCI2000 PC. You will also need the Windows BCI2000 PC that will be running BCI2000. The hardware connection is simple(Figure 3). Using the Ethernet cable, plug one end into the MP160 and the other end into the Ethernet USB adapter. Then connect the adapter to the BCI2000 PC. Alternatively, if your PC has an Ethernet port, you could directly connect the PC with the MP160 using an Ethernet cable.
	<gallery mode="traditional" widths=650px heights=600px>		<gallery mode="traditional" widths=650px heights=600px>
	File:All_device_3_min.png\|Figure 1: BioPac hardware.		File:All_device_3_min.png\|Figure 2: BioPac hardware.
	File:Connect_together_2_min.jpeg\|Figure 2: Hardware connection.		File:Connect_together_2_min.jpeg\|Figure 3: Hardware connection.
	</gallery>		</gallery>

Lingling: /* Data Loss */

2023-10-06T14:39:22Z

Data Loss

← Older revision		Revision as of 14:39, 6 October 2023
Line 32:		Line 32:

	===Data Loss===		===Data Loss===
	Data loss can occur due to variations in the interval acquisition time for each MP160 data block. Consider a block size of 100 samples (as referenced in Figure 3) with the MP160 sampling rate being 1000Hz. Ideally, BCI2000 should acquire a block of data in 100ms. However, the actual time may vary.		Data loss can occur due to variations in the interval acquisition time for each MP160 data block. Consider a block size of 100 samples (as referenced in Figure 1) with the MP160 sampling rate being 1000Hz. Ideally, BCI2000 should acquire a block of data in 100ms. However, the actual time may vary.
	The following scenarios explain potential instances of data loss:		The following scenarios explain potential instances of data loss:
	Scenario 1: BCI2000 starts acquiring block#1 in only 97ms and begins acquiring the next block at 198ms. Given the manual assignment of timestamps, the last sample's timestamp in block#1 remains at 200ms. This overlap between block#1 and block#2, from 198ms to 200ms, leads BCI2000 to discard the earlier data, resulting in data loss.		Scenario 1: BCI2000 starts acquiring block#1 in only 97ms and begins acquiring the next block at 198ms. Given the manual assignment of timestamps, the last sample's timestamp in block#1 remains at 200ms. This overlap between block#1 and block#2, from 198ms to 200ms, leads BCI2000 to discard the earlier data, resulting in data loss.
	Scenario 2: BCI2000 starts acquiring block#2 at 198ms and completes it at 309ms, 11ms later than expected. The acquisition of the next block then begins at 310ms. However, because the last sample of block#2 has a timestamp of 298ms, a gap occurs between block#2 and block#3.		Scenario 2: BCI2000 starts acquiring block#2 at 198ms and completes it at 309ms, 11ms later than expected. The acquisition of the next block then begins at 310ms. However, because the last sample of block#2 has a timestamp of 298ms, a gap occurs between block#2 and block#3.
	<gallery mode="traditional" widths=650px heights=600px>		<gallery mode="traditional" widths=650px heights=600px>
	File:Data_loss_3.png\|Figure 3: why MP160 data loss happened.		File:Data_loss_3.png\|Figure 1: why MP160 data loss happened.
	</gallery>		</gallery>


	==Hardware Set Up==		==Hardware Set Up==

Lingling at 14:35, 6 October 2023

2023-10-06T14:35:50Z

@@ Line 13: / Line 13: @@
 William Engelhardt (engelhardt@neurotechcenter.org)
 ==Video Overview==
@@ Line 25: / Line 22: @@
 To enable the extension in your CMake configuration, enable <code>EXTENSIONS_BIOPACLOGGER</code> in the Extensions folder of the CMake GUI and then generate the BCI2000 Visual Studio solution in CMake. Next, open the solution with Visual Studio and rebuild the  <code>BCI2000FrameworkSigSrcModule</code>. Then rebuild any signal source module with which you want to use the extension.
 Once the extension is built into the source module, you can enable it by appending <code>--BioPacLogger=1</code>  to the source module <tt>start executable</tt> command in your batch file.
 ==BCI2000 and MP160 Synchronization==
@@ Line 53: / Line 40: @@
 </gallery>
-===BioPacBlockSize===
+==Hardware Set Up==
-The number of samples acquired from the MP160 at a time. The recommended range is 100 ms to 8 seconds. The latency of the MP160 signal is one MP160 block duration plus the hardware buffer delay (roughly 25 ~27ms). That is
+Figure 1 shows all the necessary hardware from MP160. Make sure you have the MP160 and a wireless amplifier, the power supply for the MP160, an Ethernet USB adapter, and an Ethernet cable that can connect your MP160 with the BCI2000 PC. You will also need the Windows BCI2000 PC that will be running BCI2000. The hardware connection is simple(Figure 2). Using the Ethernet cable, plug one end into the MP160 and the other end into the Ethernet USB adapter. Then connect the adapter to the BCI2000 PC. Alternatively, if your PC has an Ethernet port, you could directly connect the PC with the MP160 using an Ethernet cable.
-MP160 latency = BioPacBlockSize/BioPacSamplingRate + (25~27ms).
+<gallery mode="traditional" widths=650px heights=600px>
-===BioPacSamplingRate===
+==Calibration==
-The MP160 supports the following sampling rates: 0.1, 0.125, 0.2, 0.25, 0.4, 0.5, 0.625, 1, 1.25, 2, 2.5, 4, 5, 6.25, 10, 20, 25, 40, 50, 62.5, 100, 125, 200, 250, 400, 500, 625, 1000, 1250, 2000, 2500, 4000, 5000, 6250, 10000, 12500, 20000, 25000, 40000, 50000, 100000, 20000HZ.
+For skin conductance measurements, we need to first calibrate the amplifier before data are acquired. After configuration setup, press “Set Config”, and a dialog will pop up. Then disconnect the leads to the electrodes and press “Calibrate”. Once the calibration is successful, you can reconnect the patient and record data.
 ==Data Scale==
@@ Line 103: / Line 83: @@
 File: Equation.png|Figure 4: Data Scale Equation.
 </gallery>
 ==See also==

Lingling: /* Synopsis */

2023-10-06T14:29:17Z

Synopsis

← Older revision		Revision as of 14:29, 6 October 2023
Line 1:		Line 1:
	==Synopsis==		==Synopsis==
	The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier.<br>		The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier.<br><br>
	In this wiki, we will discuss implementing the MP160 as a BCI2000 logger.		In this wiki, we will discuss implementing the MP160 as a BCI2000 logger.

Lingling: /* Synopsis */

2023-10-06T14:29:02Z

Synopsis

← Older revision		Revision as of 14:29, 6 October 2023
Line 1:		Line 1:
	==Synopsis==		==Synopsis==
	The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier. In this wiki, we will discuss implementing the MP160 as a BCI2000 logger.		The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier.<br>
			In this wiki, we will discuss implementing the MP160 as a BCI2000 logger.

	==Location==		==Location==

Lingling: /* Functional Description */

2023-10-06T14:28:30Z

Functional Description

← Older revision		Revision as of 14:28, 6 October 2023
Line 20:		Line 20:
	<youtube alignment="center" dimensions="900"></youtube>		<youtube alignment="center" dimensions="900"></youtube>
	<br>		<br>

	~~==Functional Description==~~
	The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier.

	In this tutorial, we will implement the MP160, BN-RSPEC, BN-EGG2, BN-EMG2, and BN-PPGED into BCI2000, which will allow us to acquire the respiration signal, electrogastrogram, electromyogram, and electrodermal signal.

	==Integration into BCI2000==		==Integration into BCI2000==

Lingling: /* Synopsis */

2023-10-06T14:26:06Z

Synopsis

← Older revision		Revision as of 14:26, 6 October 2023
Line 1:		Line 1:
	==Synopsis==		==Synopsis==
	The ~~BioPacLogger~~ module ~~enables~~ signal acquisition from ~~BioPac~~ MP160		The MP160 is implemented as both a BCI2000 source module and as a “logger.” As a source module, the MP160 is treated as the time base for data acquisition. This means that any peripheral devices will be sampled with respect to the MP160. You should implement the MP160 as a bci2000 source module if this is your primary electrophysiological signal acquisition device. As a logger, the MP160 is implemented alongside a primary electrophysiological amplifier. This means data acquired from the MP160 is resampled to the primary source device. You should implement the MP160 as a logger if you are using it to acquire additional biometric information (such as skin conductance or respiration) but want to use another device for your primary electrophysiological amplifier. In this wiki, we will discuss implementing the MP160 as a BCI2000 logger.

	==Location==		==Location==

Lingling: /* Data Loss */

2023-08-07T15:54:09Z

Data Loss

← Older revision		Revision as of 15:54, 7 August 2023
Line 51:		Line 51:
	Data loss can occur due to variations in the interval acquisition time for each MP160 data block. Consider a block size of 100 samples (as referenced in Figure 3) with the MP160 sampling rate being 1000Hz. Ideally, BCI2000 should acquire a block of data in 100ms. However, the actual time may vary.		Data loss can occur due to variations in the interval acquisition time for each MP160 data block. Consider a block size of 100 samples (as referenced in Figure 3) with the MP160 sampling rate being 1000Hz. Ideally, BCI2000 should acquire a block of data in 100ms. However, the actual time may vary.
	The following scenarios explain potential instances of data loss:		The following scenarios explain potential instances of data loss:
	Scenario 1: BCI2000 starts acquiring block#1 in only 97ms and begins acquiring the next ~~buffer~~ at 198ms. Given the manual assignment of timestamps, the last sample's timestamp in block#1 remains at 200ms. This overlap between block#1 and block#2, from 198ms to 200ms, leads BCI2000 to discard the earlier data, resulting in data loss.		Scenario 1: BCI2000 starts acquiring block#1 in only 97ms and begins acquiring the next block at 198ms. Given the manual assignment of timestamps, the last sample's timestamp in block#1 remains at 200ms. This overlap between block#1 and block#2, from 198ms to 200ms, leads BCI2000 to discard the earlier data, resulting in data loss.
	Scenario 2: BCI2000 starts acquiring block#2 at 198ms and completes it at 309ms, 11ms later than expected. The acquisition of the next ~~buffer~~ then begins at 310ms. However, because the last sample of block#2 has a timestamp of 298ms, a gap occurs between block#2 and block#3.		Scenario 2: BCI2000 starts acquiring block#2 at 198ms and completes it at 309ms, 11ms later than expected. The acquisition of the next block then begins at 310ms. However, because the last sample of block#2 has a timestamp of 298ms, a gap occurs between block#2 and block#3.
	<gallery mode="traditional" widths=650px heights=600px>		<gallery mode="traditional" widths=650px heights=600px>
	File:Data_loss_3.png\|Figure 3: why MP160 data loss happened.		File:Data_loss_3.png\|Figure 3: why MP160 data loss happened.