Contributions:NIDAQLogger - Revision history

Mellinger: /* Location */

2011-05-06T12:50:52Z

Location

← Older revision		Revision as of 12:50, 6 May 2011
Line 4:		Line 4:
	==Location==		==Location==
	The file(s) should be in the following directory:		The file(s) should be in the following directory:
	http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/NIDAQ-Logging/		http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/NIDAQ-MX/NIDAQ-Logging/

	==Versioning==		==Versioning==

Mellinger: /* Location */

2011-04-27T13:27:17Z

Location

← Older revision		Revision as of 13:27, 27 April 2011
Line 4:		Line 4:
	==Location==		==Location==
	The file(s) should be in the following directory:		The file(s) should be in the following directory:
	http://{{SERVERNAME}}/svn/trunk/src/~~shared~~/~~modules~~/~~signalsource~~/		http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/NIDAQ-Logging/

	==Versioning==		==Versioning==

Jrenga at 22:07, 7 September 2010

2010-09-07T22:07:33Z

← Older revision		Revision as of 22:07, 7 September 2010
Line 27:		Line 27:
	==Functional Description==		==Functional Description==
	Acquires signals using National Instruments Data Acquisition boards, other devices, and the computer. Device(s) must be connected to computer beforehand.		Acquires signals using National Instruments Data Acquisition boards, other devices, and the computer. Device(s) must be connected to computer beforehand.

			==Adding and Compiling==
			To add and compile the NIDAQLogger module, make sure the latest NIDAQ MX drivers are installed on your computer.
			When that is done, go into the C:\Program Files\National Instruments\NI-DAQ\DAQmx ANSI C Dev\ folder. Inside are two folders: lib and include. The lib folder will contain the NIDAQmx.lib file (inside of the folder msvc). Copy that into the project's library folder. Inside of the include folder is the NIDAQmx.h file, which contains the function prototypes needed to use the NIDAQLogger module. Move this file into the project's include folder. Make sure the project links the new .lib file, and that the NIDAQLogger.h and NIDAQLogger.cpp files include the NIDAQmx.h file correctly. The NIDAQLogger should now be able to compile normally.

	==Parameters==		==Parameters==

Jrenga: /* Location */

2010-08-31T23:24:05Z

Location

← Older revision		Revision as of 23:24, 31 August 2010
Line 3:		Line 3:

	==Location==		==Location==
	~~Not yet in the repository.~~		The file(s) should be in the following directory:
	(~~It would~~ be in the following directory:		http://{{SERVERNAME}}/svn/trunk/src/shared/modules/signalsource/
	http://{{SERVERNAME}}/svn/trunk/src/~~contrib~~/~~SignalSource~~/~~NIDAQLogger)~~

	==Versioning==		==Versioning==

Jrenga at 20:34, 3 August 2010

2010-08-03T20:34:25Z

← Older revision		Revision as of 20:34, 3 August 2010
Line 16:		Line 16:
	*Known to compile under: --		*Known to compile under: --
	*Broken since: --		*Broken since: --

			==Testing==
			The NIDAQLogger has been tested with the USB-6009 and PCI-6024E National Instruments boards at sampling rates up to and including 4096Hz, with sample block sizes up to and including 1024 samples/block. Both devices were running under DAQmx driver version 8.9.5 .

			==Known Issues==
			There are a couple of known issues with the NIDAQLogger that are listed below:
			*Occasional "glitching" may occur : the condition known as "glitching" is when some data gets swapped with slightly older data, producing a result that looks wrong.
			*The NIDAQLogger, when coupled with the NIDAQmx Source Module, does not currently work at sampling rates above 8192Hz.
			*Poor results may occur if the NIDAQLogger is used within 5 minutes of starting the BCI2000 computer up.

	==Functional Description==		==Functional Description==
	Acquires signals using National Instruments Data Acquisition boards, other devices, and the computer. Device must be connected to computer beforehand.		Acquires signals using National Instruments Data Acquisition boards, other devices, and the computer. Device(s) must be connected to computer beforehand.

	==Parameters==		==Parameters==
Line 36:		Line 45:
	*<b>1</b> - this indicates the port is <b>ACTIVE</b>		*<b>1</b> - this indicates the port is <b>ACTIVE</b>

	<i>Important: If both the NIDAQLogger and the NIDAQFilter[[Contributions:NIDAQFilter]] are being used, and both are using the digital lines on the same device, make sure that any port that is being referenced in a parameter is referenced only once. One port cannot use both digital input and digital output functionality, and will cause BCI2000 to throw an error, saying that the line is RESERVED. </i>		<i>Important: If both the NIDAQLogger and the NIDAQFilter (see [[Contributions:NIDAQFilter]]) are being used, and both are using the digital lines on the same device, make sure that any port that is being referenced in a parameter is referenced only once. One port cannot use both digital input and digital output functionality, and will cause BCI2000 to throw an error, saying that the line is RESERVED. </i>
	====Example====		====Example====
	Let's assume that the user wants to use one device for both analog and digital input. The device has 8 Analog Input ports and 12 Digital I/O ports.		Let's assume that the user wants to use one device for both analog and digital input. The device has 8 Analog Input ports and 12 Digital I/O ports.

Jrenga at 20:40, 27 July 2010

2010-07-27T20:40:23Z

← Older revision		Revision as of 20:40, 27 July 2010
Line 28:		Line 28:
	*<code>--LogAnaIn</code> (for analog input)		*<code>--LogAnaIn</code> (for analog input)
	The format for the inputs for the above flags is as follows: <code>[flag]="[device name]-[port specification]"</code>		The format for the inputs for the above flags is as follows: <code>[flag]="[device name]-[port specification]"</code>
	Note that if <code>--LogNIDAQ</code> is used, that at least one of the ~~three~~ above flags MUST be used.		Note that if <code>--LogNIDAQ</code> is used, that at least one of the two above flags MUST be used.
	====Device Specification====		====Device Specification====
	The device name (usually) is to be written as "Dev1" or "Dev2" (without the ""). Afterwards, use a - to indicate the device name is finished. If the device number is unclear, run the program with the <code>--LogNIDAQin</code> flag activated, and look at the Operator Log. The devices (along with their number) will be listed.		The device name (usually) is to be written as "Dev1" or "Dev2" (without the ""). Afterwards, use a - to indicate the device name is finished. If the device number is unclear, run the program with the <code>--LogNIDAQin</code> flag activated, and look at the Operator Log. The devices (along with their number) will be listed.
Line 36:		Line 36:
	*<b>1</b> - this indicates the port is <b>ACTIVE</b>		*<b>1</b> - this indicates the port is <b>ACTIVE</b>

	<i>Important ~~Note~~: If ~~using~~ the ~~logger with~~ the NIDAQFilter and using digital ~~input / output~~, make sure only ~~one of the programs uses a specified digital line~~. If both ~~programs attempt to use the same channel for conflicting purposes~~, ~~the programs~~ will throw ~~errors indicating~~ the line is RESERVED.</i>		<i>Important: If both the NIDAQLogger and the NIDAQFilter[[Contributions:NIDAQFilter]] are being used, and both are using the digital lines on the same device, make sure that any port that is being referenced in a parameter is referenced only once. One port cannot use both digital input and digital output functionality, and will cause BCI2000 to throw an error, saying that the line is RESERVED. </i>
	====Example====		====Example====
	Let's assume that the user wants to use one device for both analog and digital input. The device has 8 Analog Input ports and 12 Digital I/O ports.		Let's assume that the user wants to use one device for both analog and digital input. The device has 8 Analog Input ports and 12 Digital I/O ports.
Line 42:		Line 42:

	The user needs to use 3 flags to accomplish this:		The user needs to use 3 flags to accomplish this:
	*<code>--LogNIDAQin=1</code>		*<code>--LogNIDAQin=1</code> -> This flag activates the NIDAQLogger for use.
	**This flag activates the NIDAQLogger for use.		*<code>--LogDigiIn="Dev1-000100000100"</code> -> This flag indicates that the user wants to use digital I/O. "Dev1" is the name of the device connected to the computer that she wants to use. <code>0001000000100</code> indicates that the user wants ports 4 and 10 (the <b>1</b>'s) as <b>ACTIVE</b>.
	*<code>--LogDigiIn="Dev1-000100000100"</code>		*<code>--LogAnaIn="Dev1-00011000"</code> -> This flag indicates that she wants to use analog output. "Dev1" is the name of the device connected to the computer that she wants to use. <code>00011000</code> indicates that she wants to the use ports 3 and 4 on analog input.
	**This flag indicates that the user wants to use digital I/O.
	**"Dev1" is the name of the device connected to the computer that she wants to use.
	**<code>0001000000100</code> indicates that the user wants ports 4 and 10 (the <b>1</b>'s) as <b>ACTIVE</b>.
	*<code>--LogAnaIn="Dev1-00011000"</code>
	**This flag indicates that she wants to use analog output.
	**"Dev1" is the name of the device connected to the computer that she wants to use.
	**<code>00011000</code> indicates that she wants to the use ports 3 and 4 on analog input.
	The full command (assuming she uses this with SignalGenerator.exe) that the user would use is the following:		The full command (assuming she uses this with SignalGenerator.exe) that the user would use is the following:

Line 63:		Line 56:
	**<i>This parameter will be here if the </i><code>--LogNIDAQ</code><i> flag is being used</i>.		**<i>This parameter will be here if the </i><code>--LogNIDAQ</code><i> flag is being used</i>.

	The parameters will be located under the <b>Source</b> tab, in the section labeled <i>~~LogNIDAQ~~</i>.		The parameters will be located under the <b>Source</b> tab, in the section labeled <i>NILogger</i>.

	==States==		==States==
Line 80:		Line 73:
	the states that will be created are the following:		the states that will be created are the following:

	*NIDev1DINPUT3		<code>
	*NIDev1DINPUT9		NIDev1DINPUT3 NIDev1DINPUT9 NIDev1AINPUT0
	*NIDev1AINPUT0		NIDev1AINPUT2 NIDev1AINPUT3
	*NIDev1AINPUT2		</code>
	*NIDev1AINPUT3

	==Acquired Data==		==Acquired Data==
	The data (analog) that is acquired by the device is translated to make sure that all of the data will fit inside of the state's parameters. Due to this fact, the data needs to be translated back in order to return it to units of milliVolts (mV). This can be done by subtracting the data by (2000*upper voltage bound). For example, if the data was logged with the range -10V to 10V, then the data must be subtracted by 20,000.		The data (analog) that is acquired by the device is translated to make sure that all of the data will fit inside of the state's parameters. Due to this fact, the data needs to be translated back in order to return it to units of milliVolts (mV). This can be done by subtracting the data by (2000*upper voltage bound). For example, if the data was logged with the range -10V to 10V, then the data must be subtracted by 20,000.

Jrenga at 20:40, 26 July 2010

2010-07-26T20:40:26Z

← Older revision		Revision as of 20:40, 26 July 2010
Line 35:		Line 35:
	*<b>0</b> - this indicates the port is <b>INACTIVE</b>.		*<b>0</b> - this indicates the port is <b>INACTIVE</b>.
	*<b>1</b> - this indicates the port is <b>ACTIVE</b>		*<b>1</b> - this indicates the port is <b>ACTIVE</b>

			<i>Important Note: If using the logger with the NIDAQFilter and using digital input / output, make sure only one of the programs uses a specified digital line. If both programs attempt to use the same channel for conflicting purposes, the programs will throw errors indicating the line is RESERVED.</i>
	====Example====		====Example====
	Let's assume that the user wants to use one device for both analog and digital input. The device has 8 Analog Input ports and 12 Digital I/O ports.		Let's assume that the user wants to use one device for both analog and digital input. The device has 8 Analog Input ports and 12 Digital I/O ports.

Jrenga at 20:33, 26 July 2010

2010-07-26T20:33:02Z

Jrenga at 20:31, 22 July 2010

2010-07-22T20:31:15Z

← Older revision		Revision as of 20:31, 22 July 2010
Line 18:		Line 18:

	==Functional Description==		==Functional Description==
	Acquires~~/Generates~~ signals ~~to/from~~ National Instruments Data Acquisition boards, other devices, and the computer. Device must be connected to computer beforehand.		Acquires signals using National Instruments Data Acquisition boards, other devices, and the computer. Device must be connected to computer beforehand.

	==Parameters==		==Parameters==
	===Command Line Parameters===		===Command Line Parameters===
	====Initializing NIDAQLogger====		====Initializing NIDAQLogger====
	To begin using the NIDAQLogger module, use the <code>--~~LogNIDAQ~~</code> flag ~~(on SignalGenerator.exe)~~, set equal to <b>1</b>.		To begin using the NIDAQLogger module, use the <code>--LogNIDAQin</code> flag, and set it equal to <b>1</b>.
	To activate device(s) for specific functions, use the following flags:		To activate device(s) for specific functions, use the following flags:
	*<code>--~~LogNIDIO~~</code> (for digital input~~/output~~)		*<code>--LogDigiIn</code> (for digital input)
	*<code>--~~LogNIAI~~</code> (for analog input)		*<code>--LogAnaIn</code> (for analog input)
	*<code>--LogNIAO</code> (for analog output)
	The format for the inputs for the above flags is as follows: <code>[flag]="[device name]-[port specification]"</code>		The format for the inputs for the above flags is as follows: <code>[flag]="[device name]-[port specification]"</code>
	Note that if <code>--LogNIDAQ</code> is used, that at least one of the three above flags MUST be used.		Note that if <code>--LogNIDAQ</code> is used, that at least one of the three above flags MUST be used.
	====Device Specification====		====Device Specification====
	The device name (usually) is to be written as "~~dev1~~" or "~~dev2~~" (without the ""). Afterwards, use a - to indicate the device name is finished.		The device name (usually) is to be written as "Dev1" or "Dev2" (without the ""). Afterwards, use a - to indicate the device name is finished. If the device number is unclear, run the program with the <code>--LogNIDAQin</code> flag activated, and look at the Operator Log. The devices (along with their number) will be listed.
	====~~Digital~~ Port Specifications====		====Port Specifications====
	There are three acceptable states that the user can specify for each ~~digital~~ port:		There are three acceptable states that the user can specify for each port:
	*<b>0</b> - this indicates the port is <b>INACTIVE</b>.		*<b>0</b> - this indicates the port is <b>INACTIVE</b>.
	*<b>1</b> - this indicates the port is to be used as <b>INPUT</b>
	*<b>2</b> - this indicates the port is to be used as <b>OUTPUT</b>
	~~====Analog Port Specifications====~~
	~~There are two acceptable states that the user can specify for each analog port (both input and output):~~
	*<b>0</b> - this indicates the port is <b>INACTIVE</b>
	*<b>1</b> - this indicates the port is <b>ACTIVE</b>		*<b>1</b> - this indicates the port is <b>ACTIVE</b>
	====Example====		====Example====
	Let's assume that the user wants to use one device for both digital input~~/output and analog output~~. The device has 2 Analog ~~Output~~ ports and 12 Digital I/O ports.		Let's assume that the user wants to use one device for both analog and digital input. The device has 8 Analog Input ports and 12 Digital I/O ports.
	The user also wants to use the ~~1st~~ analog ~~output port, the 7th digital port as Digital Output~~, and the 4th and 10th digital ports ~~as Digital Input~~.		The user also wants to use the 3rd and 4th analog input ports, and the 4th and 10th digital ports for digital input.

	The user needs to use 3 flags to accomplish this:		The user needs to use 3 flags to accomplish this:
	*<code>--~~LogNIDAQ~~=1</code>		*<code>--LogNIDAQin=1</code>
	**This flag activates the NIDAQLogger for use.		**This flag activates the NIDAQLogger for use.
	*<code>--~~LogNIDIO~~="~~dev1~~-~~000100200100~~"</code>		*<code>--LogDigiIn="Dev1-000100000100"</code>
	**This flag indicates that the user wants to use digital I/O.		**This flag indicates that the user wants to use digital I/O.
	**"~~dev1~~" is the name of the device connected to the computer that she wants to use.		**"Dev1" is the name of the device connected to the computer that she wants to use.
	**<code>~~0001000200100~~</code> indicates that the user wants ~~to use~~ ports 4 and 10 (the <b>1</b>'s) as <b>~~INPUT</b>, and port 7 (the <b>2</b>) as <b>OUTPUT~~</b>		**<code>0001000000100</code> indicates that the user wants ports 4 and 10 (the <b>1</b>'s) as <b>ACTIVE</b>.
	*<code>--~~LogNIAO~~="~~dev1~~-10"</code>		*<code>--LogAnaIn="Dev1-00011000"</code>
	**This flag indicates that she wants to use analog output.		**This flag indicates that she wants to use analog output.
	**"~~dev1~~" is the name of the device connected to the computer that she wants to use.		**"Dev1" is the name of the device connected to the computer that she wants to use.
	**<code>10</code> indicates that she wants to the use ~~port 1~~ on analog ~~output~~.		**<code>00011000</code> indicates that she wants to the use ports 3 and 4 on analog input.
			The full command (assuming she uses this with SignalGenerator.exe) that the user would use is the following:

	~~The full command that the user would use is the following:~~		<code>SignalGenerator.exe --LogNIDAQin=1 --LogDigiIn="Dev1-000100000100" --LogAnaIn="Dev1-00011000"</code>

	~~<code>SignalGenerator.exe --LogNIDAQ=1 --LogNIDIO="dev1-000100200100" --LogNIAO="dev1-10"</code>~~
	===BCI2000 Parameters===		===BCI2000 Parameters===
	There are three possible parameters that the user will be able to use. They are outlined below:		There are three possible parameters that the user will be able to use. They are outlined below:
	*<b>#~~IVRange~~</b> - the available voltage ranges for analog input for the given device (where <b>#</b> will be replaced by the device name)		*<b>#IVRanges</b> - the available voltage ranges for analog input for the given device (where <b>#</b> will be replaced by the device name)
	**<i>This parameter will only be enabled if the </i><code>--~~LogNIAI~~</code><i> flag is being used</i>.		**<i>This parameter will only be enabled if the </i><code>--LogAnaIn</code><i> flag is being used</i>..
	*<b>#~~OVRange</b> - the available voltage ranges for analog output for the given device (where <b>#</b> will be replaced by the device name)~~		*<b>#InSampleRate</b> - the sampling rate for the NIDAQLogger
	**<i>This parameter will only be enabled if the </i><code>--LogNIAO</code><i> flag is being used, or there are multiple possible ranges</i>.
	*<b>NIDAQSampleRate</b> - the sampling rate for the NIDAQLogger
	**<i>This parameter will be here if the </i><code>--LogNIDAQ</code> flag is being used</i>.		**<i>This parameter will be here if the </i><code>--LogNIDAQ</code> flag is being used</i>.

Line 74:		Line 66:
	The states that are available are dependent on the port specifications declared in the command line parameters. The format for the states is the following:		The states that are available are dependent on the port specifications declared in the command line parameters. The format for the states is the following:

	<b>~~NIdev~~#[A:D][INPUT~~:OUTPUT]~~#</b>		<b>NIDev#[A:D]INPUT#</b>

	*The first <b>#</b> refers to the device number.		*The first <b>#</b> refers to the device number.
	*The second <b>#</b> refers to the line number (starting at <b>0</b>).		*The second <b>#</b> refers to the line number (starting at <b>0</b>).
	*The <b>[A:D]</b> denotes if the state refers to an analog (<b>A</b>) or a digital (<b>D</b>) channel.		*The <b>[A:D]</b> denotes if the state refers to an analog (<b>A</b>) or a digital (<b>D</b>) channel.
	*The <b>[INPUT:OUTPUT]</b> denotes if the state refers to an <b>input</b> or <b>output</b> channel.

	For example, if the command parameters look like this:		For example, if the command parameters look like this:

	<code>SignalGenerator.exe --~~LogNIDAQ~~=1 --~~LogNIDIO~~="~~dev1~~-~~000100200100~~" --~~LogNIAO~~="~~dev1~~-10"</code>		<code>SignalGenerator.exe --LogNIDAQin=1 --LogDigiIn="Dev1-000100000100" --LogAnaIn="Dev1-10011000"</code>

	the states that will be created are the following:		the states that will be created are the following:

	*~~NIdev1DINPUT3~~		*NIDev1DINPUT3
	*~~NIdev1DOUTPUT6~~		*NIDev1DINPUT9
	*~~NIdev1DINPUT9~~		*NIDev1AINPUT0
	*~~NIdev1AOUTPUT0~~		*NIDev1AINPUT2
			*NIDev1AINPUT3

			==Acquired Data==
			The data (analog) that is acquired by the device is translated to make sure that all of the data will fit inside of the state's parameters. Due to this fact, the data needs to be translated back in order to return it to units of milliVolts (mV). This can be done by subtracting the data by (2000*upper voltage bound). For example, if the data was logged with the range -10V to 10V, then the data must be subtracted by 20,000.

Jrenga at 18:30, 29 June 2010

2010-06-29T18:30:54Z

← Older revision		Revision as of 18:30, 29 June 2010
Line 61:		Line 61:
	<code>SignalGenerator.exe --LogNIDAQ=1 --LogNIDIO="dev1-000100200100" --LogNIAO="dev1-10"</code>		<code>SignalGenerator.exe --LogNIDAQ=1 --LogNIDIO="dev1-000100200100" --LogNIAO="dev1-10"</code>
	===BCI2000 Parameters===		===BCI2000 Parameters===
	~~If either~~ the <code>--LogNIAI</code> or the <code>--LogNIAO</code> ~~flags are~~ used, there ~~will be a parameter in~~ the ~~configuration box (under Source)~~		There are three possible parameters that the user will be able to use. They are outlined below:
	~~that~~ will ~~allow users to specify~~ the ~~voltage range they want the device to work under~~. ~~There will be as many range~~ parameters ~~as there are devices connected~~		*<b>#IVRange</b> - the available voltage ranges for analog input for the given device (where <b>#</b> will be replaced by the device name)
	~~that use analog functionality. It~~ will be ~~labeled as~~ <b>~~dev#VRanges~~</b>, ~~where # represents~~ the ~~device number~~.		**<i>This parameter will only be enabled if the </i><code>--LogNIAI</code><i> flag is being used</i>.
			*<b>#OVRange</b> - the available voltage ranges for analog output for the given device (where <b>#</b> will be replaced by the device name)
			**<i>This parameter will only be enabled if the </i><code>--LogNIAO</code><i> flag is being used, or there are multiple possible ranges</i>.
			*<b>NIDAQSampleRate</b> - the sampling rate for the NIDAQLogger
			**<i>This parameter will be here if the </i><code>--LogNIDAQ</code> flag is being used</i>.

			The parameters will be located under the <b>Source</b> tab, in the section labeled <i>LogNIDAQ</i>.

	==States==		==States==

← Older revision		Revision as of 20:33, 26 July 2010
Line 32:		Line 32:
	The device name (usually) is to be written as "Dev1" or "Dev2" (without the ""). Afterwards, use a - to indicate the device name is finished. If the device number is unclear, run the program with the <code>--LogNIDAQin</code> flag activated, and look at the Operator Log. The devices (along with their number) will be listed.		The device name (usually) is to be written as "Dev1" or "Dev2" (without the ""). Afterwards, use a - to indicate the device name is finished. If the device number is unclear, run the program with the <code>--LogNIDAQin</code> flag activated, and look at the Operator Log. The devices (along with their number) will be listed.
	====Port Specifications====		====Port Specifications====
	There are ~~three~~ acceptable states that the user can specify for each port:		There are two acceptable states that the user can specify for each port:
	*<b>0</b> - this indicates the port is <b>INACTIVE</b>.		*<b>0</b> - this indicates the port is <b>INACTIVE</b>.
	*<b>1</b> - this indicates the port is <b>ACTIVE</b>		*<b>1</b> - this indicates the port is <b>ACTIVE</b>
Line 55:		Line 55:

	===BCI2000 Parameters===		===BCI2000 Parameters===
	There are ~~three~~ possible parameters that the user will be able to use. They are outlined below:		There are two possible parameters that the user will be able to use. They are outlined below:
	*<b>#IVRanges</b> - the available voltage ranges for analog input for the given device (where <b>#</b> will be replaced by the device name)		*<b>#IVRanges</b> - the available voltage ranges for analog input for the given device (where <b>#</b> will be replaced by the device name)
	**<i>This parameter will only be enabled if the </i><code>--LogAnaIn</code><i> flag is being used</i>..		**<i>This parameter will only be enabled if the </i><code>--LogAnaIn</code><i> flag is being used</i>.
	*<b>#InSampleRate</b> - the sampling rate for the NIDAQLogger		*<b>#InSampleRate</b> - the sampling rate for the NIDAQLogger
	**<i>This parameter will be here if the </i><code>--LogNIDAQ</code> flag is being used</i>.		**<i>This parameter will be here if the </i><code>--LogNIDAQ</code><i> flag is being used</i>.

	The parameters will be located under the <b>Source</b> tab, in the section labeled <i>LogNIDAQ</i>.		The parameters will be located under the <b>Source</b> tab, in the section labeled <i>LogNIDAQ</i>.