*.exe.config - Revision history

Gshotts: /* DPR Settings */

2025-10-10T02:48:36Z

DPR Settings

← Older revision		Revision as of 21:48, 9 October 2025
Line 123:		Line 123:
	These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.		These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.

	~~Note: multiple DPR types are supported by adding additional DPR tags with a numeric postfix. The first postfix value past~~ the ~~first tag is 2. Examples are shown in the individual tag descriptions below~~.		Multiple DPRs of the following two groups can be configured using only basic settings.

			* DPR35G, DPR300, DPR500

	~~However, adding additional tags is unnecessary if you are using a combination of the following sets of DPRs:~~		'''OR'''

	* ~~DPR35G~~, ~~DPR300, DPR500 (need only one tag set)~~		* PureView, DPR650

	~~'''OR'''~~

	* PureView, DPR650 (need only one tag ~~set)~~		Multiple DPR types from different manufacturers or between the above groups are supported by adding additional DPR tags with a numeric postfix. The first postfix value past the first tag is 2. Examples are shown in the individual tag descriptions below.

Gshotts: /* DPR Settings */

2025-10-10T02:40:51Z

DPR Settings

← Older revision		Revision as of 21:40, 9 October 2025
Line 123:		Line 123:
	These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.		These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.

	Note: multiple DPR types are supported by adding additional DPR tags with a numeric postfix. The first postfix value past the first tag is 2. ~~This~~ is unnecessary if you are using a combination of the following sets of DPRs:		Note: multiple DPR types are supported by adding additional DPR tags with a numeric postfix. The first postfix value past the first tag is 2. Examples are shown in the individual tag descriptions below.


			However, adding additional tags is unnecessary if you are using a combination of the following sets of DPRs:

	* DPR35G, DPR300, DPR500 (need only one tag set)		* DPR35G, DPR300, DPR500 (need only one tag set)
Line 131:		Line 134:
	* PureView, DPR650 (need only one tag set)		* PureView, DPR650 (need only one tag set)


	~~Examples are shown in the individual tag descriptions below.~~

Gshotts: /* DPR Settings */

2025-10-10T02:39:53Z

DPR Settings

← Older revision		Revision as of 21:39, 9 October 2025
Line 123:		Line 123:
	These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.		These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.

	Note: multiple DPR types are supported by adding a ~~number~~ postfix ~~to the various DPR tags~~. The first postfix value past the first tag is 2. This is unnecessary if you are using a combination of the following sets of DPRs:		Note: multiple DPR types are supported by adding additional DPR tags with a numeric postfix. The first postfix value past the first tag is 2. This is unnecessary if you are using a combination of the following sets of DPRs:

	* DPR35G, DPR300, DPR500 (need only one tag set)		* DPR35G, DPR300, DPR500 (need only one tag set)
Line 131:		Line 131:
	* PureView, DPR650 (need only one tag set)		* PureView, DPR650 (need only one tag set)


			Examples are shown in the individual tag descriptions below.

Gshotts: /* DPR Settings */

2025-10-10T02:39:12Z

DPR Settings

← Older revision		Revision as of 21:39, 9 October 2025
Line 125:		Line 125:
	Note: multiple DPR types are supported by adding a number postfix to the various DPR tags. The first postfix value past the first tag is 2. This is unnecessary if you are using a combination of the following sets of DPRs:		Note: multiple DPR types are supported by adding a number postfix to the various DPR tags. The first postfix value past the first tag is 2. This is unnecessary if you are using a combination of the following sets of DPRs:

	* DPR35G, DPR300, DPR500		* DPR35G, DPR300, DPR500 (need only one tag set)

	'''OR'''		'''OR'''

	* PureView, DPR650		* PureView, DPR650 (need only one tag set)

	~~You only need one set of tags for the DPRs in those two groups, but not '''between''' the groups.~~

Gshotts: /* DPR Settings */

2025-10-10T02:38:46Z

DPR Settings

← Older revision		Revision as of 21:38, 9 October 2025
Line 123:		Line 123:
	These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.		These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.

	Note: multiple DPR types are supported by adding a number postfix to the various DPR tags. The first postfix value past the first tag is 2. This is unnecessary if you are using a combination of the following sets of ~~DPRS~~:		Note: multiple DPR types are supported by adding a number postfix to the various DPR tags. The first postfix value past the first tag is 2. This is unnecessary if you are using a combination of the following sets of DPRs:

	* DPR35G, DPR300, DPR500		* DPR35G, DPR300, DPR500

Gshotts: /* DPR Settings */

2025-10-10T02:38:30Z

DPR Settings

← Older revision		Revision as of 21:38, 9 October 2025
Line 123:		Line 123:
	These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.		These keys are used to set the type and communications mode with any Digital Pulser/Receivers (DPRs) attached to the system.

	Note: multiple DPR types are supported by adding a number postfix to the various DPR tags. The first postfix value past the first tag is 2. ~~You only need additional tags~~ if ~~the DPRs~~ you are using ~~are not on the same line in~~ the following ~~list~~:		Note: multiple DPR types are supported by adding a number postfix to the various DPR tags. The first postfix value past the first tag is 2. This is unnecessary if you are using a combination of the following sets of DPRS:

	* DPR002		* DPR35G, DPR300, DPR500
	* DPR35
	* DPR35G, DPR300, DPR500		'''OR'''

	* PureView, DPR650		* PureView, DPR650
	* PR5800
	* PR5900		You only need one set of tags for the DPRs in those two groups, but not '''between''' the groups.
	* UTEX
	* UPRS
	* Shell

Gshotts: /* NumPulsers[n] */

2025-10-10T02:36:32Z

NumPulsers[n]

← Older revision		Revision as of 21:36, 9 October 2025
Line 237:		Line 237:
	<add key="NumPulsers" value="3"></add>		<add key="NumPulsers" value="3"></add>

	If more than one DPR type is present, "n" represents the index of the next device. minimum value is 2. First postfix is always blank.		If more than one DPR type is present, "n" represents the index of the next device or device group. minimum value is 2. First postfix is always blank.
	<add key="NumPulsers" value="3"></add>		<add key="NumPulsers" value="3"></add>
	<add key="NumPulsers2" value="1"></add>		<add key="NumPulsers2" value="1"></add>

Gshotts: /* PRPort[n] */

2025-10-10T02:36:01Z

PRPort[n]

← Older revision		Revision as of 21:36, 9 October 2025
Line 241:		Line 241:
	<add key="NumPulsers2" value="1"></add>		<add key="NumPulsers2" value="1"></add>

	===PRPort[n]===		===PRPort[n] (was:Port)===
	Sets the communication (COM) port used to control the DPR, for DPR types that use a Serial port. Ignored if using ~~a “Shell” DPR~~. Current values are:		Sets the communication (COM) port used to control the DPR, for DPR types that use a Serial port. Ignored for DPRs using IP addresses. Current values are:
	; ''COMx'': Sets the COM port to use, where "x" is the assigned serial port (e.g. "COM3")		; ''COMx'': Sets the COM port to use, where "x" is the assigned serial port (e.g. "COM3")
	; ''Simulate'': tells the system to create the control for the DPR but will only simulate hardware communications. If simulation is active the [[#NumPulsers\|NumPulsers]] key will be used to determine how many DPRs to simulate, and the [[#PRType\|PRType]] key will determine the type of DPR.		; ''Simulate'': tells the system to create the control for the DPR but will only simulate hardware communications. If simulation is active the [[#NumPulsers\|NumPulsers]] key will be used to determine how many DPRs to simulate, and the [[#PRType\|PRType]] key will determine the type of DPR.

Gshotts: /* NumPulsers[n] (was:Port) */

2025-10-10T02:35:12Z

NumPulsers[n] (was:Port)

← Older revision		Revision as of 21:35, 9 October 2025
Line 233:		Line 233:
	<add key="PRIPAddress2" value="192.168.1.2"></add>		<add key="PRIPAddress2" value="192.168.1.2"></add>

	===NumPulsers[n] ~~(was:Port)~~===		===NumPulsers[n]===
	If using multiple DPRs of the same group, this lists the number of DPRs expected. If not present, the number of DPRs is assumed to be one.		If using multiple DPRs of the same group, this lists the number of DPRs expected. If not present, the number of DPRs is assumed to be one.
	<add key="NumPulsers" value="3"></add>		<add key="NumPulsers" value="3"></add>

Gshotts: /* PRIPAddress[n] (was: IPAddress) */

2025-10-10T02:34:48Z

PRIPAddress[n] (was: IPAddress)

← Older revision		Revision as of 21:34, 9 October 2025
Line 226:		Line 226:

	===PRIPAddress[n] (was: IPAddress)===		===PRIPAddress[n] (was: IPAddress)===
	Optional IP Address with which to communicate with the DPR, or the hardware used to talk to the DPR, if necessary. The IP address should be in standard format “XXX.XXX.XXX.XXX”, where “XXX” is from 0 to 255.		Optional IP Address with which to communicate with the DPR, or the I/O hardware used to talk to the DPR, if necessary. The IP address should be in standard format “XXX.XXX.XXX.XXX”, where “XXX” is from 0 to 255.
	<add key="PRIPAddress" value="192.168.1.1"></add>		<add key="PRIPAddress" value="192.168.1.1"></add>