Running pDTPClient - Revision history

Wac002 at 20:29, 17 September 2020

2020-09-17T20:29:04Z

← Older revision		Revision as of 20:29, 17 September 2020
Line 35:		Line 35:
	#Start mode: RQT, RQR, RQS, RQFS, GS, ABRT		#Start mode: RQT, RQR, RQS, RQFS, GS, ABRT
	MODE = RQS		MODE = RQS
	#Time to run client in seconds: 0 for disable.		#Time to run the client in seconds: 0 for disable.
	RTIME = 0		RTIME = 0
	#UDP recv timeout in microsecounds, 0 to disable		#UDP recv timeout in microsecounds, 0 to disable
Line 80:		Line 80:

	=== Adapt the config file ===		=== Adapt the config file ===
	You can adapt the config file to use localhost to connect to the emulator when it is running.		You can adapt the config file to use <code>IP = localhost</code> to connect to the emulator when it is running.

Wac002 at 20:26, 17 September 2020

2020-09-17T20:26:56Z

← Older revision		Revision as of 20:26, 17 September 2020
Line 61:		Line 61:

	<code>./pDTPClient --config <location/config.conf></code>		<code>./pDTPClient --config <location/config.conf></code>

			== Using a hardware emulator ==
			The hardware emulator can be obtained from the [https://git.app.uib.no/pct/pDTP pDTP repo]

			=== Starting the emulator ===
			Load server with only constant data:
			<syntaxhighlight lang="bash">
			python3 server_emulator.py
			</syntaxhighlight>
			Load a file with data:
			<syntaxhighlight lang="bash">
			python3 server_emulator.py -f <FILENAME>
			</syntaxhighlight>
			Increase verbosity (prints all debug messages to console. Note that these can be viewed in debug.log as well):
			<syntaxhighlight lang="bash">
			python3 server_emulator.py -v
			</syntaxhighlight>

			=== Adapt the config file ===
			You can adapt the config file to use localhost to connect to the emulator when it is running.

Wac002 at 14:27, 4 February 2020

2020-02-04T14:27:57Z

← Older revision		Revision as of 14:27, 4 February 2020
Line 18:		Line 18:

	There is also a consideration to be made with the size of the queue between the pDTPClient and the file writer/parser.		There is also a consideration to be made with the size of the queue between the pDTPClient and the file writer/parser.

			The config file in the next section is a good starting point on an optimal configuration.

	== The config file ==		== The config file ==

Wac002 at 14:27, 4 February 2020

2020-02-04T14:27:14Z

← Older revision		Revision as of 14:27, 4 February 2020
Line 15:		Line 15:

	== Optimal configuration ==		== Optimal configuration ==
	Due to the RUs ability to max out the 10Gbit link with small package sizes (high burst) and the Linux kernels inability to process large amounts of packages, ~~and~~ optimal configuration is advised.		Due to the RUs ability to max out the 10Gbit link with small package sizes (high burst) and the Linux kernels inability to process large amounts of packages, an optimal configuration is advised.

	There is also a consideration to be made with the size of the queue between the pDTPClient and the file writer/parser.		There is also a consideration to be made with the size of the queue between the pDTPClient and the file writer/parser.

Wac002 at 14:19, 4 February 2020

2020-02-04T14:19:27Z

← Older revision		Revision as of 14:19, 4 February 2020
Line 13:		Line 13:
	== Simplified diagram of offload chain ==		== Simplified diagram of offload chain ==
	[[File:offload-system.png\|750px]]		[[File:offload-system.png\|750px]]

	== Optimal configuration ==		== Optimal configuration ==
			Due to the RUs ability to max out the 10Gbit link with small package sizes (high burst) and the Linux kernels inability to process large amounts of packages, and optimal configuration is advised.

			There is also a consideration to be made with the size of the queue between the pDTPClient and the file writer/parser.

	== The config file ==		== The config file ==

Wac002 at 08:30, 4 February 2020

2020-02-04T08:30:59Z

← Older revision		Revision as of 08:30, 4 February 2020
Line 6:		Line 6:

	The pDTPClient handles the proton Data Transfer Protocol (pDTP) using UDP.		The pDTPClient handles the proton Data Transfer Protocol (pDTP) using UDP.
	pDTP ~~have~~ three main modes; Request read (RQR), a single packet from 1 byte to 4080 ~~byte~~. Request stream (RQS), a single packet ~~upto~~ 65535 packets. And request full stream (RQFS). For more in depth details about pDTP see:		pDTP has three main modes; Request read (RQR), a single packet from 1 byte to 4080 bytes. Request stream (RQS), a single packet up to 65535 packets. And request full stream (RQFS). For more in-depth details about pDTP see:
	[[Media:PDTP.pdf \| pDTP spesification]]		[[Media:PDTP.pdf \| pDTP spesification]]

	If the ~~filewriter~~ is enabled the client will produce a time and date stamped file that in a binary format.		If the file writer is enabled the client will produce time and date stamped file that in a binary format.

			== Simplified diagram of offload chain ==
			[[File:offload-system.png\|750px]]
			== Optimal configuration ==

	== The config file ==		== The config file ==

Wac002 at 15:08, 3 February 2020

2020-02-03T15:08:14Z

← Older revision		Revision as of 15:08, 3 February 2020
Line 8:		Line 8:
	pDTP have three main modes; Request read (RQR), a single packet from 1 byte to 4080 byte. Request stream (RQS), a single packet upto 65535 packets. And request full stream (RQFS). For more in depth details about pDTP see:		pDTP have three main modes; Request read (RQR), a single packet from 1 byte to 4080 byte. Request stream (RQS), a single packet upto 65535 packets. And request full stream (RQFS). For more in depth details about pDTP see:
	[[Media:PDTP.pdf \| pDTP spesification]]		[[Media:PDTP.pdf \| pDTP spesification]]

			If the filewriter is enabled the client will produce a time and date stamped file that in a binary format.

	== The config file ==		== The config file ==
	The config file exists to load the diffrent settings of the client in a easy manner.		The config file exists to load the diffrent settings of the client in a easy manner.
	~~<code>~~<nowiki>#Config file for the settings to the pDTPClient		<nowiki>#Config file for the settings to the pDTPClient
	#IP adress to the PRU		#IP adress to the PRU
	IP = 192.168.100.200		IP = 192.168.100.200
Line 43:		Line 45:
	NOWAIT = 0		NOWAIT = 0
	#Set maximize flag		#Set maximize flag
	MAXIMIZE = 0</nowiki~~></code~~>		MAXIMIZE = 0</nowiki>

	== Starting the client ==		== Starting the client ==

Wac002 at 14:25, 3 February 2020

2020-02-03T14:25:33Z

@@ Line 11: / Line 11: @@
 == The config file ==
 The config file exists to load the diffrent settings of the client in a easy manner.
-<code> </code>
+<code><nowiki>#Config file for the settings to the pDTPClient
 == Starting the client ==
+The client can be run with the command:

Wac002 at 13:53, 3 February 2020

2020-02-03T13:53:53Z

← Older revision		Revision as of 13:53, 3 February 2020
Line 1:		Line 1:
	[[Main Page]] -> [[Control & Readout Software Documentation and Howto's]] -> [[Running pDTPClient]]		[[Main Page]] -> [[Control & Readout Software Documentation and Howto's]] -> [[Running pDTPClient]]

	== ~~Getting Started~~ ==
	*[[Media:Requirements.pdf \| Requirements]]		== Use case ==
	~~pDTPClient~~
	The main task of this program is to get data from the proton Readout Unit (pRU) hardware to a host computer for storage or parsing.		The main task of this program is to get data from the proton Readout Unit (pRU) hardware to a host computer for storage or parsing.

	The pDTPClient handles the proton Data Transfer Protocol (pDTP) using UDP. pDTP have three main modes; Request read (RQR), a single packet from 1 byte to 4080 byte. Request stream (RQS), a single packet upto 65535 packets. And request full stream (RQFS)		The pDTPClient handles the proton Data Transfer Protocol (pDTP) using UDP.
			pDTP have three main modes; Request read (RQR), a single packet from 1 byte to 4080 byte. Request stream (RQS), a single packet upto 65535 packets. And request full stream (RQFS). For more in depth details about pDTP see:
			[[Media:PDTP.pdf \| pDTP spesification]]

	The config file:		== The config file ==
			The config file exists to load the diffrent settings of the client in a easy manner.
			<code> </code>

	Starting the client:		== Starting the client ==
			a

Wac002 at 13:27, 3 February 2020

2020-02-03T13:27:11Z

← Older revision		Revision as of 13:27, 3 February 2020
Line 1:		Line 1:
			[[Main Page]] -> [[Control & Readout Software Documentation and Howto's]] -> [[Running pDTPClient]]

			== Getting Started ==
			*[[Media:Requirements.pdf \| Requirements]]
	pDTPClient		pDTPClient
	The main task of this program is to get data from the proton Readout Unit (pRU) hardware to a host computer for storage or parsing.		The main task of this program is to get data from the proton Readout Unit (pRU) hardware to a host computer for storage or parsing.