version 20: trigger IDs are not the same for different DUT modes operated at the same time
The TriggerID of mode 01 and the TriggerID of mode 00 (EUDET mode) externally clocked-out on line "TRIGGER" are not the same. This is probably connected to the reset issue#1, additionally the TriggerID of mode 00 is also not reset at the moment. Both are individually incrementing if they are active. Also after a power cycle, there is already a mismatch by +1, which was observed in looking into the NiProducer and TluProducer data stream, see attached screenshot. --> Having the the same triggerID for both modes is crucial synchronization between different devices and event building.
From "Summary of testing the AIDA-TriggerID mode (DUTMaskMode: b01) fw-v20 with EUDAQ2 (master) and MimosaDAQ/NiProducer from 16th April 2019"