Module master_trigger

MasterTriggerBoard communications

The MTB (MasterTriggerBoard) is currently (Jan 2023) connected to the ethernet via UDP sockets and sends out its own datapackets per each triggered event.

The packet format contains the event id as well as number of hits and a mask which encodes the hit channels.

The data is encoded in IPBus packets. see docs here

Re-exports

• pub use crate::settings::MTBSettings;

Modules

• control
  Master trigger board control
• registers
  MasterTriggerBoard registers

Functions

• configure_mtb
  Configure the MTB according to lifot settings. If the settings have a non-zero prescale for any of the triggers, this will cause the MTB to start triggering (if it hasn’t been triggering before)
• get_event
  Read the complete event of the MTB
• get_mtbmonidata
  Gather monitoring data from the Mtb
• master_trigger
  Communications with the master trigger over Udp