Hi,
It should also work for that specific case, see:
https://paulscherrerinstitute.github.io/StreamDevice/processing.html#init
Another way to handle this is to not use PINI, and instead have some record logic that processes all the records (that did use PINI=Yes) when the Asyn port becomes connected. And you can detect this by using
an asynRecord via the CNCT field. So when CNCT changes state, trigger the record processing.
Cheers,
Matt
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Friederich, Dr. Simon via Tech-talk
Sent: Friday, May 16, 2025 2:57 PM
To: ralph.lange at gmx.de
Cc: tech-talk at aps.anl.gov
Subject: [EXTERNAL] Re: Process PINI-Record again as soon as device is reconnected
Dear Ralph, But does @init except handle the case if the ioc is already running before a device is available? I think I've tested both (@ init,
PINI) and that did not help with this issue. Best regards Am 16. Mai 2025, 19: 34, um 19: 34,
Ralph
But does @init except handle the case if the ioc is already running before a device is available? I think I've tested both (@init, PINI) and that did not help with this issue.
>On Fri, 16 May 2025 at 16:05, Dr. Simon Friederich via Tech-talk
>In most cases I use asyn + streamdevice to talk to my devices so I
>guess might be some kind of signal comming from asyn "hey, the device
>is back online, now you can (re)process your PINI-records"?
>That's what StreamDevice's @init exception handler does.