Re: Pure Python IOC (CAProcess issue)

["Cobb, Tom \(DLSLtd,RAL,LSCI\) via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Ralph,

I asked this question of Michael and Michael the other week, so I'll try and summarize:

• pyDevSup provides Python device support within an existing IOC build (along with Makefile rules to do it). It follows the same style as writing device support in C, and includes a parameter table implementation to reduce some boilerplate. You build an IOC using the standard EPICS build system each time you want to use it, which means you can mix it with other non-Python support modules.
  
• pythonIoc (formerly pythonSoftIoc) provides an IOC binary with Python device support built in. You create a Python script that instantiates Python classes with a supplied on_update callback, and that is what you use as your IOC. It is currently tied to Diamond's cothread module for concurrency and putting other PVs in response to a caput of its PVs, but we have plans to provide an asyncio option too. We have ambitions to make it installable via pip, but don't know if this is possible yet.
  

Both options make a full soft IOC with the standard set of EPICS records.

Thanks,

Tom

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>
Sent: 17 July 2020 17:17
To: EPICS Tech Talk <tech-talk at aps.anl.gov>
Subject: Re: Pure Python IOC (CAProcess issue)

 

Question:

What is the difference between pyDevSup [1] and pythonIoc [2]?

To the untrained eye, their concepts seem pretty similar. Is the divide between C and Python on a different layer? Or just the ecosystem they're running in?

Thanks,

~Ralph

[1] https://github.com/mdavidsaver/pyDevSup

[2] http://controls.diamond.ac.uk/downloads/python/pythonIoc/

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom