Skip to content

SOFB SyncBPMs command doesn't do everything necessary to sync BPMs, as done by TrigAcqConfig command. #1179

@ericonr

Description

@ericonr

The FOFB HLA uses the SI-Glob:AP-SOFB:SyncBPMs-Cmd PV to sync the FOFB network, but that doesn't always work. In many cases, it's necessary to sync the BPMs from the SOFB HLA, using the SI-Glob:AP-SOFB:TrigAcqConfig-Cmd PV.

There's some additional work done by TrigAcqConfig which makes the BPM synchronization succeed and allows us to close the FOFB network.

def acq_config_bpms(self, *args):
"""."""
_ = args
msg = "Configuring BPMs..."
self._update_log(msg)
_log.info(msg)
mask = self._get_mask()
for i, bpm in enumerate(self.bpms):
bpm.put_enable = mask[i]
if self.is_multiturn():
bpm.switching_mode = _CSBPM.SwModes.direct
bpm.configure()
self.timing.configure()
elif self.is_singlepass():
bpm.switching_mode = _CSBPM.SwModes.direct
bpm.configure()
self.timing.configure()
elif self.is_sloworb():
bpm.switching_mode = _CSBPM.SwModes.switching
self.sync_bpms(None)
msg = "Done configuring BPMs!"
self._update_log(msg)
_log.info(msg)
return True

Seems to be essentially the switching mode setting that's the difference (sync_bpms is the function called by the SyncBPMs PV). Will have to wait for an occasion where synchronization via the FOFB HLA fails, so we can check the switching mode of all BPMs... I'm not sure there's any other available option.

@fernandohds564 @anacso17 @augustofg @guilhermerc

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions