Investigate approach for talking to updated Instron stress rig on Engin-X [Timebox: 2.5 days] [Engineers on site 30 August to 2 September]

[KathrynBaker]

As someone supporting the Instron on IBEX I want to keep using it after the controller is updated to the ethernet version

Acceptance Criteria

• The cmd file uses etherent as opposed to GPIB
• Each rig has been tested for still working

Notes

• Be wary of the controllers for each rig (50kN and 100kN)
• Don't forget the need for cooling water to test the stress and strain modes

[Tom-Willemsen]

I had an initial conversation with Instron engineers is that they were unaware we were using the GPIB interface for remote control and they are not aware of any equivalent in the new system (which is a PC running their manufacturer software).

I then had a follow-up call with a software developer at instron who suggested that the only approach we might be able to use is:

• Use a manufacturer dll called arby.dll to send commands to the rig
• Before we can call into arby.dll the rig and system will need to be configured using the instron console application, which is a GUI application. I enquired about command line but it sounds like this is not available.
• We are "likely to need support from Instron" in order to implement this approach as the DLL has little/no documentation

I have suggested that we need a proper follow-up meeting between Instron, the Engin-X scientists, and ourselves in order to fully understand the suggested approach. Probably at least 2 people from our group should be in this meeting so that knowledge of the approach is shared.

Suggest that this ticket becomes "investigate approach for controlling updated instron" rather than "switch control", as there is significant complexity here.

[Tom-Willemsen]

Also note: only the 100kN rig is being updated. The 50kN rig stays on it's existing GPIB control, so drivers for both need to remain available.

[Tom-Willemsen]

Contact details for useful instron contacts are at \\isis\shares\ISIS_Experiment_Controls\data for tickets\Ticket7296, along with various other documentation received from them.

[FreddieAkeroyd]

Basis of IOC using arby.dll at https://github.com/ISISComputingGroup/EPICS-InstronArby

[Tom-Willemsen]

I've now exhausted the timebox for the initial investigation. We have had some success talking to the rig via the new Arby.dll mechanism, so I'm adding an IOC for this. Currently I have added this as a separate IOC (INSTRONA) rather than as a macro of the existing IOC - I think this makes more sense because you can never switch between the two comms modes (due to 32/64bit issues). But happy to be persuaded otherwise if others feel strongly that it should be the same IOC.

There are a number of outstanding issues with this approach that need to be solved before ENGIN-X can use the rig in cycle. These are documented in the follow-on issues below.

PRs:

• Ticket7296 instron arby EPICS-ioc#722
• Move DBs to instron sup. module EPICS-instron#6
• Ticket7296 instron arby EPICS-InstronArby#1
  • Unfortunately some work was done on main in this repo, so need to review main as well as the PR.
• Ticket7296 instron arby ibex_gui#1470
• https://github.com/ISISComputingGroup/ibex_developers_manual/wiki/Instron-stress-rig---MiniTower
• Add tests for INSTRONA EPICS-IOC_Test_Framework#562
• Ticket7296 #7331

Follow-on issues:

• Instron MiniTower - decide details of how to support host computer #7326
• Instron MiniTower - run test with scientists [Timebox: 2.5 days] #7327

To review:

• Check code looks reasonable
• If you want to see new IOC communicating, ask Tom to take you down to ENGIN-X, where this can be set up.
• Check docs are understandable and manuals are in usual share etc
• Check follow-on issues represent remaining work to be done on this

Note:

• You won't be able to run this IOC locally as you won't have Arby.dll on your system. You should be able to build it, however.
• In it's deployed configuration this IOC uses a 32-bit EPICS build.