EMMA: Migrate to IBEX

[kjwoodsISIS]

As an instrument scientist, I would like to migrate EMMA to use the IBEX instrument control system.

Acceptance Criteria

1. IBEX is installed on EMMA
2. Configuration files are created (see EMMA: Create Configs and Synoptics #2387)
3. IBEX is configured for the devices on EMMA.
4. EMMA scripts are converted to genie_python
5. EMMA scientists are trained in how to use IBEX
6. IBEX is tested on EMMA

Notes

1. The devices on EMMA are listed on the EMMA Instrument Details list
2. The following tickets should be implemented prior to deploying IBEX on EMMA
   • EMMA: Fermi Chopper Lift IOC and OPI #2365
     • In progress
   • EMMA: Y-Z and Rotation Stages #2366
     • EMMA and others: Generic Sample Stack OPI #1197 awaiting review complete
   • EMMA: Create Configs and Synoptics #2387
   • EMMA: Create Setup Scripts #2388
   • EMMA: Fermi Chopper #2397
     • Impeded awaiting Asyn: add a "break on every write" option. #2768
3. Use the Migrate-an-Instrument-Control-PC page to guide you through the migration process. The following activities need to be completed as part of the migration process:
   • Ask Facilities IT (Anthony Shuttle) to create a private network for EMMA. This is required so that we can use TCP/IP to communicate with the Galils. Facilities IT will need notice of about 4-6 weeks.
     • Emailed Anthony 15/11/17
   • Check that NDXEMMA has sufficient disk space to install IBEX
   • Check whether EMMA uses 5- or 8- digit run-numbers
     • If it uses 5-digit run-numbers, upgrade the ICP program (to permit 8-digit run-numbers)
   • Create a virtual instrument for testing purposes
     • Set up a test system, say, NDXEMM-ATEST.
     • create IBEX configurations to correspond to their SECI equivalents
     • create genie-python scripts to correspond to their Open-Genie equivalents
     • test these configurations & scripts
     • check that all the devices previously supported by SECI (on EMMA) are supported by IBEX
   • arrange one or more training sessions with the scientists to help them understand how to use IBEX
     • demonstrate the configurations & scripts (created above) to the instrument scientists and check that they are happy with the migrated configurations & scripts

[ChrisM-S]

Sent a note to EMMA instrument scientists to say that EMMA will not be migrated for next cycle.

[Tom-Willemsen]

Note the machine is actually called NDXEMMA-A not NDXEMMA.

[AdrianPotter]

I've done the majority of the setup. I'm setting impeded until the Fermi chopper and lift are in so I can add them.

I've migrated some scripts I found on EMMA. They seem to have been stolen from GEM but customised for EMMA. I've migrated them to genie_python. Tom is going to ask whether that's sufficient or whether they want more as part of #2388.

The configurations have been migrated but currently don't contain the chopper or lift.

Training has been organised for 23rd/24th January. We'll make sure Jeff is encouraged to attend

[AdrianPotter]

Jeff is signed up on the training. Waiting for outstanding tickets to be reviewed. I've asked Jeff for a time we can do a preliminary migration to confirm everything is set up to his liking

[AdrianPotter]

The migration is mostly complete. There are a few outstanding tasks:

• The shutter status is currently listed as "UNKNOWN". I'm told that's because the shutter status is contained in a PV with instrument name "HET" rather than "EMMA-A". We need to see if we can create a new PV.
• I can't talk to the Eurotherm at the moment. Neither can LabView. I suspect it's unplugged. It has the same COM port listed as the Galil though which is weird. I need to ask Jeff
• I've burnt the standard IP address to the Galil. It just needs plugging in to the network now, which needs to be done by one of the controls team
• I want to double check what Jeff expects with regard to the CAENs.

[kjwoodsISIS]

@FreddieAkeroyd - do we need to retain the legacy name, "HET"? Is it likely that there is some other process (perhaps something owned by the Accelerator Controls team) that still uses "HET"? Can it be eliminated?

[FreddieAkeroyd]

There was already a PV for the EMMA shutter, but it was called "EMMA" rather than "EMMA-A" - I've added an "EMMA-A" alias which should now be active. I haven't removed the HET alias yet, but it is not causing any problems. All instrument shutter PVs are actually aliases for an underlying port PV which is named something like N9 for "north 9"

[AdrianPotter]

Super, thanks. Moving to impeded awaiting connection of the Galil via ethernet

[AdrianPotter]

I've done the final setup on Emma. Waiting for Jeff to get back to me so we can organise a time to look at it together

[AdrianPotter]

Meeting on EMMA today 1:30 with Mark Brind from the chopper group to finish and test the setup

[AdrianPotter]

Jeff's happy with the current setup. We haven't been able to test the chopper lift or chopper because the chopper is broken. Mike Brind has scheduled maintenance

[kjwoodsISIS]

If we are waiting for the chopper to be fixed, we should not leave this ticket in an impeded state (because it might take some time to fix the chopper). It would be better to create a new ticket to address the outstanding chopper tasks, rather than hold up the review & completion of this ticket.

[Tom-Willemsen]

IBEX is deployed on EMMA.

Reviewed:
• I've had a look at their configs, synoptics, DAE tables. They seem plausible.
• I had a look at the scripts - they seem ok, a bit more advanced than most instrument scripts in terms of python knowledge but they seem ok.
• I had a look at the logs that have been generated so far, nothing jumps out as being wrong since they were last updated on 2/2/2018. Before that date the ARACCESS IOC was spewing some logs but it looks like that has been fixed since the new deployment.

There is some outstanding work for this e.g. test the Fermi Chopper but this is captured in separate tickets so I will mark this as complete.