Re: Simulate an existing IOC with a python IOC

[Érico Nogueira Rolim via Tech-talk <tech-talk at aps.anl.gov>]

Hi Graeme!

On 4/22/26 07:40, Graeme Winter via Tech-talk wrote:
> It could work - in principle a quick dbl in the running IOC would be enough to cobble together what I was after


If remote access is needed, I believe pvlist or reccaster could provide
basically the same list.


>
> However
>
> # Unsupported record type asyn
>
> … busy, calc, calcout etc.


I think it should be reasonably simple to implement busy and calc yourself.


asyn wouldn't be available in a softIoc, so it really should be omitted.
For usual cases, I don't believe there are calcout fields which should
be exposed to GUIs or similar, so it could be skipped as well.


>
> May be more of a problem - I will see how far I can get with this
>
> It may be I need to provide a mocking layer one layer above the EPICS to get this done…


All the above said, I think there could be an alternative implementation
of ioc-clone. If you only access the VAL field of any record you're
using, that can be cleanly implemented for all record types by querying
the PVs with DBR_CTRL_*, and creating a record with the corresponding
type and configuration (ai for DOUBLE, longin for LONG, mbbi for ENUM,
etc). This would avoid depending on knowledge of specific records,
including any custom ones.


I'm not sure this solution wouldn't have other issues, and using only
VAL might not be a common situation.


>
> Thanks Graeme
>
>
>> On 21 Apr 2026, at 14:41, Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> wrote:
>>
>> But does working from files fulfill your original requirement to "interrogate a running IOC"?
>>
>> Cheers,
>> ~Ralph
>>


Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.