DaqWiki - Recent changes [en]

Raspbian

Olchansk — Thu, 24 Sep 2026 00:38:59 GMT

install RPi5 from scratch

← Older revision		Revision as of 00:38, 24 September 2026
(2 intermediate revisions by the same user not shown)
Line 10:		Line 10:
	* bullseye is debian 11		* bullseye is debian 11
	* bookworm is debian 12		* bookworm is debian 12
			* trixie is debian 13

	= install RPi4 from scratch =		= install RPi4 from scratch =
Line 63:		Line 64:
	* same as above		* same as above
	* use 2025-05-13-raspios-bookworm-arm64-lite.img.xz		* use 2025-05-13-raspios-bookworm-arm64-lite.img.xz
	* after enabling boot from network, vcgencmd reports		* update the firmware - rpi-eeprom-update
			* change boot order to network first - raspi-config
			* after enabling boot from network and rebooting, "vcgencmd bootloader_config" reports
	<pre>		<pre>
	[all]		[all]
	BOOT_UART=1		BOOT_UART=1
	POWER_OFF_ON_HALT=0		POWER_OFF_ON_HALT=0
	BOOT_ORDER=~~0xf461~~		BOOT_ORDER=0xf21
	</pre>		</pre>

RPI

Dfujimoto — Wed, 23 Sep 2026 23:40:21 GMT

RPi5 boot from network

← Older revision	Revision as of 23:40, 23 September 2026
(4 intermediate revisions by the same user not shown)
(No difference)

DS-DM

Olchansk — Fri, 18 Sep 2026 03:01:52 GMT

DS20k block register map

← Older revision		Revision as of 03:01, 18 September 2026
Line 2,428:		Line 2,428:
	109 \| 0x20260626 \| GDM \| ROL \| rtc_32khz_counter_latched \| counts RTC chip 32khz pulses		109 \| 0x20260626 \| GDM \| ROL \| rtc_32khz_counter_latched \| counts RTC chip 32khz pulses
	110 \| 0x20260626 \| GDM \| RO \| rtc_1pps_period \| RTC 1pps period, 125 MHz		110 \| 0x20260626 \| GDM \| RO \| rtc_1pps_period \| RTC 1pps period, 125 MHz
			111 \| 0x20260911 \| CDM \| ROLB \| cdm_hitmap_grand_or_counter_latched \| CDM hitmap grand_or counter
			112 \| 0x20260911 \| GDM \| ROLB \| gdm_hitmap_grand_or_counter_latched \| GDM hitmap grand_or counter
			113 \| 0x20260911 \| GDM \| RW \| conf_gdm_hitmap_trigger \| GDM hitmap trigger settings
	</pre>		</pre>

EMMA

Olchansk — Wed, 16 Sep 2026 22:53:59 GMT

MPDD32 development station

← Older revision		Revision as of 22:53, 16 September 2026
(One intermediate revision by the same user not shown)
Line 113:		Line 113:
	ssh emma@daq13.triumf.ca		ssh emma@daq13.triumf.ca
	mhttpd -D		mhttpd -D
	open https://daq13.triumf.ca/		open https://daq13.triumf.ca/emma/
	go to "Programs" page, start mserver, mlogger, ~~feemma~~, ana		go to "Programs" page, start mserver, mlogger, tmfe_mdpp32, ana
	</pre>		</pre>
	* to update, rebuild ~~feemma~~:		* to update, rebuild tmfe_mdpp32:
	<pre>		<pre>
	ssh emma@daq13		ssh emma@daq13
	cd online/src		cd online/src
	edit ~~feemma~~.cxx		edit tmfe_mdpp32.cxx
	make		make
	</pre>		</pre>
	* to run ~~feemma~~:		* to run tmfe_mdpp32:
	<pre>		<pre>
	ssh emma@lxdaq21		ssh emma@lxdaq21
	online/src/~~feemma~~.exe -h daq13		online/src/tmfe_mdpp32.exe -h daq13:6066
	</pre>		</pre>
	* to update, rebuild emmana		* to update, rebuild emmana
Line 134:		Line 134:
	edit mdpp32_module.cxx		edit mdpp32_module.cxx
	make		make
	./emmana.exe -~~R8082~~ --jsroot		./emmana.exe -R7076 --jsroot
	</pre>		</pre>

Cluster Offsite Access

Lindner — Tue, 15 Sep 2026 18:20:50 GMT

ssh jump host

← Older revision		Revision as of 18:20, 15 September 2026
(5 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	Instructions for off-site HTTPS and SSH access		=== Instructions for off-site HTTPS and SSH access ===

			As of late 2026, the majority of DAQ and PSD experimental hosts will be moved fully behind the
			TRIUMF firewall. After hosts are moved behind the firewall it will no longer be possibly to
			directly access these hosts with HTTPS or SSH.

			Access will be possible via VPN. If you have TRIUMF VPN client running you will be able to access the hosts via HTTPS or SSH as normal.

			There are also a couple other options for accessing TRIUMF hosts from offsite.

			=== HTTPS proxy ===

			The https proxy is provided by Ivanti, who also provide the VPN client.

			To use the proxy you first go to

			https://vpn.triumf.ca/

			You will be asked to login using your two-factor TRIDENT authentication. There is a window in your browser that shows that you are logged in.

			Once you login you will get a page with some bookmarked hosts. This will include the daq00 DAQ webpage. If you click
			on it you will be redirected to the DAQ main page. It will take a little while to get used to the proxy URL mangling.

			Here's some examples of the URL mangling

			1)
			https://mpmt-daq03.triumf.ca/

			becomes

			https://vpn.triumf.ca/,DanaInfo=mpmt-daq03.triumf.ca,SSL+

			2)
			https://ucnelog.triumf.ca/elog/

			becomes

			https://vpn.triumf.ca/elog/,DanaInfo=ucnelog.triumf.ca,SSL+

			3)
			https://daq00.triumf.ca/DaqWiki/index.php/Main_Page

			becomes

			https://vpn.triumf.ca/DaqWiki/index.php/,DanaInfo=daq00.triumf.ca,SSL+Main_Page

			=== ssh jump host ===

			TRIUMF has a temporary jump host called hoop.triumf.ca. Once you have it setup you can from outside TRIUMF do the following to login to an internal TRIUMF host like tucan01.ucn.triumf.ca. For instance you can do

			<pre>
			ssh -J hoop.triumf.ca ucn@tucan01.ucn.triumf.ca
			</pre>

			You are not allowed to actually ssh to just hoop; you can only access hoop to jump somewhere else.

			Contact a DAQ group member if you need access to the jump host.

			'''This jump host is just a temporary solution. In the longer term a different solution will be provided.'''

Cluster Offsite Access

Lindner — Tue, 15 Sep 2026 17:39:50 GMT

Created page with "Instructions for off-site HTTPS and SSH access"

New page

Instructions for off-site HTTPS and SSH access

Sysman

Lindner — Tue, 15 Sep 2026 17:39:34 GMT

Computer clusters

← Older revision		Revision as of 17:39, 15 September 2026
Line 26:		Line 26:
	* [[graphics_benchmarks]]		* [[graphics_benchmarks]]
	* [[VMs]] DAQ VMs		* [[VMs]] DAQ VMs
			* [[Cluster Offsite Access]] Instructions for off-site HTTPS and SSH access

	== Linux documentation ==		== Linux documentation ==

DAQ VMs

Lindner — Tue, 15 Sep 2026 16:51:17 GMT

← Older revision		Revision as of 16:51, 15 September 2026
(One intermediate revision by the same user not shown)
Line 59:		Line 59:
	\| 1		\| 1
	\| Provides readout and online display for the 1VM4 notch monitor (beamline 1V)		\| Provides readout and online display for the 1VM4 notch monitor (beamline 1V)
	\|		\| Blocked at perimeter firewall
	\|-		\|-
	\| exoelog.triumf.ca		\| exoelog.triumf.ca
Line 66:		Line 66:
	\| 1		\| 1
	\| Provides elog for EXO tests		\| Provides elog for EXO tests
	\| ~~not really used~~		\| Decommissioned 2026
	\|-		\|-
	\| scdms-srv0.triumf.ca		\| scdms-srv0.triumf.ca
Line 87:		Line 87:
	\| 1		\| 1
	\| Provides elog for M11 beamline		\| Provides elog for M11 beamline
	\|		\| Blocked at perimeter firewall
	\|-		\|-
	\| nd280elog-vm		\| nd280elog-vm
Line 143:		Line 143:
	\| 1		\| 1
	\| Hosts the FGD hardware database and webserver		\| Hosts the FGD hardware database and webserver
	\|		\| Decommissioned 2026
	\|		\|
	\|-		\|-
	\|}		\|}

DS-DM

Olchansk — Tue, 08 Sep 2026 23:50:53 GMT

DS20k block register map

← Older revision		Revision as of 23:50, 8 September 2026
(2 intermediate revisions by the same user not shown)
Line 2,372:		Line 2,372:
	52,53 \| 0x20240424 \| CDM \| RO \| VX serial link status, 4 bits per VX port		52,53 \| 0x20240424 \| CDM \| RO \| VX serial link status, 4 bits per VX port
	54 \| 0x20240424 \| CDM \| RO \| VX TX serial data monitor		54 \| 0x20240424 \| CDM \| RO \| VX TX serial data monitor
	55 \| 0x20240430 \| ALL \| RO \| QSFP, SFP and VX link loss counters		55 \| 0x20240430 \| ALL \| ROB \| QSFP, SFP and VX link loss counters, VX RX error counter
	56 \| 0x20240510 \| ALL \| RO \| sfp_rx_packet_counter		56 \| 0x20240510 \| ALL \| RO \| sfp_rx_packet_counter
	57 \| same \| ALL \| RO \| sfp_tx_packet_counter		57 \| same \| ALL \| RO \| sfp_tx_packet_counter
Line 2,410:		Line 2,410:
	87 \| 0x20250417 \| CDM \| ROLB \| vx_tx_veto_counter \| VX LVDS Veto counter (VX LVDS pair 13)		87 \| 0x20250417 \| CDM \| ROLB \| vx_tx_veto_counter \| VX LVDS Veto counter (VX LVDS pair 13)
	88 \| 0x20250422 \| GDM \| ROLB \| trg_in_lost_counter \| counter of TRG killed by gdm_busy		88 \| 0x20250422 \| GDM \| ROLB \| trg_in_lost_counter \| counter of TRG killed by gdm_busy
	89 \| 0x20250422 \| ALL \| RO \| fifo_from_fpga_lost_packet_counter \| counter of packets lost due to FIFO full		89 \| 0x20250422 \| ALL \| ROB \| fifo_from_fpga_lost_packet_counter \| counter of packets lost due to FIFO full
	90 \| 0x20250428 \| CDM \| ROL \| vx_bsy_status_latched \| status of VX busy, CDM busy, CDM veto		90 \| 0x20250428 \| CDM \| ROL \| vx_bsy_status_latched \| status of VX busy, CDM busy, CDM veto
	91 \| 0x20250428 \| CDM \| ROL \| vx_hitmap_status_latched \| status of VX hitmap		91 \| 0x20250428 \| CDM \| ROL \| vx_hitmap_status_latched \| status of VX hitmap
Line 3,201:		Line 3,201:
	8..15 - CDM SFP link loss counter, increments on sfp_link_rx_status 1->0 (reg15)		8..15 - CDM SFP link loss counter, increments on sfp_link_rx_status 1->0 (reg15)
	0...7 - CDM VX link loss counter, increments on vx_tx_link_rx_status 1->0 (reg10)		0...7 - CDM VX link loss counter, increments on vx_tx_link_rx_status 1->0 (reg10)
			</pre>

			<pre>
			vx_rx_error_counter counts vx_rx_error_bits of each/any of the enabled VX LVDS links:

			wire [11:0] vx_rx_error_bits = vx_rx_error \| vx_rx_deser_rdy \| vx_rx_code_err \| vx_rx_disp_err \| vx_link_error \| vx_rx_8to16_error;
	</pre>		</pre>

← Older revision		Revision as of 03:01, 18 September 2026
Line 2,428:		Line 2,428:
	109 \| 0x20260626 \| GDM \| ROL \| rtc_32khz_counter_latched \| counts RTC chip 32khz pulses		109 \| 0x20260626 \| GDM \| ROL \| rtc_32khz_counter_latched \| counts RTC chip 32khz pulses
	110 \| 0x20260626 \| GDM \| RO \| rtc_1pps_period \| RTC 1pps period, 125 MHz		110 \| 0x20260626 \| GDM \| RO \| rtc_1pps_period \| RTC 1pps period, 125 MHz
			111 \| 0x20260911 \| CDM \| ROLB \| cdm_hitmap_grand_or_counter_latched \| CDM hitmap grand_or counter
			112 \| 0x20260911 \| GDM \| ROLB \| gdm_hitmap_grand_or_counter_latched \| GDM hitmap grand_or counter
			113 \| 0x20260911 \| GDM \| RW \| conf_gdm_hitmap_trigger \| GDM hitmap trigger settings
	</pre>		</pre>

← Older revision		Revision as of 23:50, 8 September 2026
(2 intermediate revisions by the same user not shown)
Line 2,372:		Line 2,372:
	52,53 \| 0x20240424 \| CDM \| RO \| VX serial link status, 4 bits per VX port		52,53 \| 0x20240424 \| CDM \| RO \| VX serial link status, 4 bits per VX port
	54 \| 0x20240424 \| CDM \| RO \| VX TX serial data monitor		54 \| 0x20240424 \| CDM \| RO \| VX TX serial data monitor
	55 \| 0x20240430 \| ALL \| RO \| QSFP, SFP and VX link loss counters		55 \| 0x20240430 \| ALL \| ROB \| QSFP, SFP and VX link loss counters, VX RX error counter
	56 \| 0x20240510 \| ALL \| RO \| sfp_rx_packet_counter		56 \| 0x20240510 \| ALL \| RO \| sfp_rx_packet_counter
	57 \| same \| ALL \| RO \| sfp_tx_packet_counter		57 \| same \| ALL \| RO \| sfp_tx_packet_counter
Line 2,410:		Line 2,410:
	87 \| 0x20250417 \| CDM \| ROLB \| vx_tx_veto_counter \| VX LVDS Veto counter (VX LVDS pair 13)		87 \| 0x20250417 \| CDM \| ROLB \| vx_tx_veto_counter \| VX LVDS Veto counter (VX LVDS pair 13)
	88 \| 0x20250422 \| GDM \| ROLB \| trg_in_lost_counter \| counter of TRG killed by gdm_busy		88 \| 0x20250422 \| GDM \| ROLB \| trg_in_lost_counter \| counter of TRG killed by gdm_busy
	89 \| 0x20250422 \| ALL \| RO \| fifo_from_fpga_lost_packet_counter \| counter of packets lost due to FIFO full		89 \| 0x20250422 \| ALL \| ROB \| fifo_from_fpga_lost_packet_counter \| counter of packets lost due to FIFO full
	90 \| 0x20250428 \| CDM \| ROL \| vx_bsy_status_latched \| status of VX busy, CDM busy, CDM veto		90 \| 0x20250428 \| CDM \| ROL \| vx_bsy_status_latched \| status of VX busy, CDM busy, CDM veto
	91 \| 0x20250428 \| CDM \| ROL \| vx_hitmap_status_latched \| status of VX hitmap		91 \| 0x20250428 \| CDM \| ROL \| vx_hitmap_status_latched \| status of VX hitmap
Line 3,201:		Line 3,201:
	8..15 - CDM SFP link loss counter, increments on sfp_link_rx_status 1->0 (reg15)		8..15 - CDM SFP link loss counter, increments on sfp_link_rx_status 1->0 (reg15)
	0...7 - CDM VX link loss counter, increments on vx_tx_link_rx_status 1->0 (reg10)		0...7 - CDM VX link loss counter, increments on vx_tx_link_rx_status 1->0 (reg10)
			</pre>

			<pre>
			vx_rx_error_counter counts vx_rx_error_bits of each/any of the enabled VX LVDS links:

			wire [11:0] vx_rx_error_bits = vx_rx_error \| vx_rx_deser_rdy \| vx_rx_code_err \| vx_rx_disp_err \| vx_link_error \| vx_rx_8to16_error;
	</pre>		</pre>