Re: EPICS 'isegHAL' module

[Bruno Martins via Tech-talk <tech-talk@aps.anl.gov>]

Hi Florian,

Thanks for letting me know! That looks promising indeed.

Bruno

On Fri, Aug 23, 2019 at 11:12 AM Florian Feldbauer <florian@ep1.ruhr-uni-bochum.de> wrote:

Hey Bruno,

at least in the current master branch from isegHAL, I found the following in the readme:

Remote Access
=============

The library isegHAL-service allows accessing isegHAL running on a computer
or iseg Crate somewhere in the local network or in the internet.

Secure sockets are used to crypt the communication between the two end points.

The API is completely the same as for isegHAL, with some adjustments and some
extensions, which are described here.

iseg_connect
------------

The iseg_connect API call takes a special URL to connect to a remote server.

Example: iseg_connect("myEth", "hal://192.168.16.56:1454/can0,user,pass", NULL);

* The first parameter "myEth" is the session name, which must be unique for every
  client. A unique session name can be generated by the isegHAL API (see below).

* The second parameter "hal://192.168.16.56:1454/can0,user,pass" always starts
  with "hal://".

  Following, the remote hosts IP address or name, and, separated by a colon (:),
  the port are given. The remote server always uses port 1454, but it may be
  necessary to use an other port if the remote server is behind a network router.

  After the slash (/), further arguments are given: the used interface (can0),
  the login user name (user) and the password (pass).

* The third parameter is reserved at the moment and should always be NULL.

I'm not sure, if the the iseg-ioc currently supports this though. I will test it on Monday and maybe update the iseg-ioc accordingly.
By the way: the code of the device support package is now on github: https://github.com/ffeldbauer/devIsegHal.
Some additions from Bruce are merged there

Have a nice weekend!

Florian

On 8/9/19 4:52 PM, Bruno Martins wrote:

Hi Florian,

Thanks for the info, it makes more sense now. The cc24 manual mentions secure sockets (I assumed ssl), but maybe that's not available.

Maybe it would be possible to create a TCP bridge for this Unix socket so it can be exposed on a second machine.

Bruno

On Fri, Aug 9, 2019, 10:21 Florian Feldbauer via Tech-talk <tech-talk@aps.anl.gov> wrote:

Hey,

since we have a very old crate from iseg, which does not have the cc24 controller, I'm running the isegHAL-Daemon and my isegIOC on a BeagleBone Black, which is connected via CAN bus to our HV modules.
But for crates with CC24 controller the isegHAL and the corresponding IOC have to run on that controller. IIRC the isegioc connects via a local unix-socket to the isegHAL. So, the IOC connecting to the HAL cannot run on a different PC...

Cheers,
Florian

On 8/9/19 3:50 PM, Bruno Martins via Tech-talk wrote:

Hi Bruce,

I am working with Ethan on this project. Our goal is similar to yours: to use our standard tools and link some extra EPICS modules with the iseg IOC. Is it not possible at all to have a client to this isegHALservice that runs elsewhere? I am assuming such client would be just exchanging messages like "get voltage", "get status", "set voltage", etc.

Thanks!

Bruno

On Fri, Aug 9, 2019 at 1:24 AM Hill, Bruce via Tech-talk <tech-talk@aps.anl.gov> wrote:

Hi All,
The embedded IOC in these iSeg CC24 controllers is indeed the
fastest and easiest route to getting EPICS control of the modules.
If you only have a few crates you can hand customize and install
the iseg_epics.db and iseg_epics.sub files and you're good to go!

At SLAC we'll be deploying 6-10 of these mpod crates each w/ several
HV modules and may add some additional crates and/or LV modules
as we commission more LCLS2 chambers.

We wanted to be able to upgrade and version control our iSeg IOCs
w/ the same tools and EPICS 7 base releases as our other IOCs so we
found a way to do that and also add access security.

iSeg provided us w/ the arm-apalis gnu toolchain so we're cross-compiling
the iSegHAL module on our RHEL7 build server along w/ our EPICS base
and support modules and building IOC releases there on NFS.

The CC24 uses systemd services for startup, so we disable the isegioc
and install three slac systemd services.   One service does an NFS mount,
the next runs a startup script on the NFS mount that does other NFS
mounts, and a third that launches the IOC.

I've got this working on a demo unit and am looking forward to getting
our deployment crates and HV in so I can iron out any kinks in the scripts.
I"ve actually made a number of other changes to our demo system in the
course of this development so I need to make sure this all works from a
clean factory CC24.

If anyone's interested, contact me and I can provide more details re how
to get this working.

Cheers,
- Bruce

-- 
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA  94025

On 8/8/19 12:05 AM, laurent daudin via Tech-talk wrote:

Dear Ethan,

Why don't you use directly the CC24 embedded IOC ?

I am using the EPICS "isegHAL" which is already in the controler, so from the iCS controler WEB page in the EPICS section you just have to :

- download the "iseg_epics.db" and "iseg_epics.sub" files

- modify these files if needed

- Upload these new files

- reboot the EPICS IOC

and it should works !

regards,

Laurent.

Le 07/08/2019 à 22:47, Fulcher, Ethan via Tech-talk a écrit :

Hello all,

I am building an IOC for an iseg CC24 Master power supply, and need an EPICS module called 'isegHAL'. I wasn't able to find a download for it on the hardware support by manufacturer EPICS webpage (https://epics.anl.gov/modules/manufacturer.php#ISEG). Would anyone know about this module or where to get it?

Thank you,

Ethan Fulcher

Facility for Rare Isotope Beams

Michigan State University

640 South Shaw Lane

East Lansing, MI 48824, USA

Email: fulcher@frib.msu.edu

--

-- 
Dr. Florian Feldbauer

Ruhr-Universität Bochum
Experimentalphysik I AG
Universitätsstr. 150
Fach-Nr. 125
D-44801 Bochum

Office: NB 2/134
Phone:  (+49)234 / 32-23563
Fax:    (+49)234 / 32-14170
https://paluma.ruhr-uni-bochum.de

-- 
Dr. Florian Feldbauer

Ruhr-Universität Bochum
Experimentalphysik I AG
Universitätsstr. 150
Fach-Nr. 125
D-44801 Bochum

Office: NB 2/134
Phone:  (+49)234 / 32-23563
Fax:    (+49)234 / 32-14170
https://paluma.ruhr-uni-bochum.de