ISISComputingGroup / ISISComputingGroup/IBEX

LOQ: IOC and OPI for Ordela detector control and diagnostics & H/W testing

Open
#8,829 0 comments 0 reactions 0 assignees View on GitHub
8 Core training
Dominant language
No language data
Stars
6
Forks
2
Avg merge
16h 40m
Merged PRs (30d)
2

Description

# Feature Description

As a SANS instrument scientist, I would like to be able to control the LOQ Ordela detector (i.e. turn it on and off) as well as monitor its behaviour remotely.

## Explanation

Currently this is done via an obsolete, and soon to be disconnected, WIndows 10 PC using proprietary software. Please see [this ticket](https://github.com/ISISComputingGroup/IBEX/issues/3544) for the whole story. This ticket aims to replace this method with an IOC and OPI on the IBEX control machine.

### Additional Information

The detector's voltages and temperature are monitored using channels on MOXA IOLogik modules. IOCs already exist for these, and IBEX blocks on the three relevant PVs are used for run-control (See 'base component' on LOQ for details). These three values should also be displayed on the new detector OPI. Reading the HV is the only way to (remotely) determine whether or not the detector is on and functioning (i.e. ready to collect data).

See [this comment](https://github.com/ISISComputingGroup/IBEX/issues/3544#issuecomment-3257563692) in the ticket mentioned above for the actual commands and their format.

Is is envisaged that the serial communications cable from the detector to the LOQ cabin will be moved from the W10 PC to the nearby MOXA NPort. It will still be necessary to use the existing RS232<->RS485 convertor until such time as the NPort is replaced with an equivalent with RS485 capability.

**NB** This ticket does _NOT_ include the (independent) work to support the original NI PCI DIO card used for detector diagnostics (model `NI PCI-DIO-32HS` for reference).

See our [Git Workflow](https://isiscomputinggroup.github.io/ibex_developers_manual/processes/git_and_github/Git-workflow.html).

# Acceptance Criteria

- [ ] An IOC is written to control the detector (i.e. send ON and OFF commands, as well as query the firmware periodically to verify connection to trigger an alarm accordingly)
- [ ] An OPI is created to provide this control, display the firmware and show values from the relevant IOLogik channels mentioned above
- [ ] Appropriate tests are written for the new functionality
- [ ] A page is written for the [Developers' Manual](https://isiscomputinggroup.github.io/ibex_developers_manual/Specific-IOCs.html) with more information on the detector and new control method. May also include a summary of its history with our group, or at least a link to the original ticket
- [ ] Testing is performed with the principal LOQ instrument scientist (LC) in a convenient and imminent shutdown (may be more appropriate in its own ticket unless time allows). However, it would make sense to test with hardware as part of this work.

# How to Review

- Check code complies with all standards
- Test functionality with hardware

**To the reviewer: Make sure to [update submodules](https://isiscomputinggroup.github.io/ibex_developers_manual/processes/git_and_github/Git-workflow.html)!**

Discussed 00:42:10 - in planning 02/10/25

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.