You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soon as a downsampling factor is used, the scope does not trigger properly any more.
Known good configuration: Trigger only on CMD_BEAM_INJECTION, disable trigger on CMD_BEAM_EXTRACTION and CMD_START_ENERGY_RAMP
With downsampling mode, triggers are only received, if no events are disabled (Only CMD_BEAM_EXTRACTION) . As soon as any event is disabled, no data is received at all.
That strange behavior continues even if "downsampling_factor = 1" is picked.
(Doing downsampling in the same way than for dal025, which uses a factor of 8 .. seems to work fine there)
The text was updated successfully, but these errors were encountered:
In GitLab by @alexxcons on Apr 21, 2021, 16:23
As soon as a downsampling factor is used, the scope does not trigger properly any more.
Known good configuration: Trigger only on CMD_BEAM_INJECTION, disable trigger on CMD_BEAM_EXTRACTION and CMD_START_ENERGY_RAMP
With downsampling mode, triggers are only received, if no events are disabled (Only CMD_BEAM_EXTRACTION) . As soon as any event is disabled, no data is received at all.
That strange behavior continues even if "downsampling_factor = 1" is picked.
(Doing downsampling in the same way than for dal025, which uses a factor of 8 .. seems to work fine there)
The text was updated successfully, but these errors were encountered: