RIKEN Front End: Control of the DG535

[KathrynBaker]

As a scientist on the RIKEN Front End I want to able to control the Stanford DG535 remotely.

Acceptance Criteria

1. There is an IOC to control the DG535
2. There is an OPI for interactions

Notes

1. Standard Driver
2. Details of specific interactions will follow

[kjwoodsISIS]

May be required for RIKEN refurbishment project. See RIKENFE user specification after upgrade - clarifications.docx - specifically the section on Kicker timing. Choice may be between a DG535 or a DG645.

[JamesKingWork]

Also required for EMU RF Kit

[ChrisM-S]

There is currently a DG535 down in the kicker rack for the Riken FE, it needs to be communicated with through a serial to GPIB converter - which doesn't appear to be there anymore - not sure why. I will investigate, we could potentially use an NI GPIB/Enet converter if the current one has died but GPIB/serial is probably simpler/cheaper to maintain.

[ChrisM-S]

If the converter is lost or broken, there seems to be quite a cheap Enet/GPIB converter here which just takes network commands and looks like it can be set up with ~GPIB~DHCP - didn't have much luck in finding R232/GPIB although NI do do a somewhat more pricey box. @davidkeymer or @KathrynBaker what was the connection for the the other DG535?

[DominicOram]

There is an IOC for this already at https://epics.anl.gov/bcda/synApps/delaygen/delaygen.html

[FreddieAkeroyd]

Using https://github.com/NSLS-II-CSX/stanfordDG645 may work better than delaygen see #5154

[davidkeymer]

Decision announced on 08/12/2021 to use DG645 instead of DG535. Additional units will be purchased as part of the RIKEN refurbishment project.

The DG535 may still be required at some point, so leaving ticket open and placing in main IBEX backlog.