Re: pC_->doCallbacksEnum() coming too early

["Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov>]

Hi Torsten,

 

I assume this an Asyn port driver; what is triggering the I/O that results in your code doing that callback? The callback shouldn't happen until after the EPICS global interruptAccept is non-zero, any earlier than that and the IOC and records won't be ready for device support to call it. The asynPortDriver code looks like it ignores all such calls before then. If the code needs something to trigger that processing it could register an initHook and wait for the value initHookAfterInterruptAccept, which is only sent once (i.e. it doesn't get repeated if the IOC is paused), or for initHookAfterDatabaseRunning which is repeated after an IOC pause is rescinded.

 

HTH,

 

- Andrew

 

-- 

Complexity comes for free, Simplicity you have to work for.

 

 

On 2/27/24, 10:38 AM, "Core-talk" <core-talk-bounces at aps.anl.gov> wrote:

 

Hej experts, I have an IOC that talks to a PLC-ish system. The PLC gives us some names for enmums, resulting in a call to pC_->doCallbacksEnum() However, most often the response from the PLC comes back to the IOC before the record has registered

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

 

ZjQcmQRYFpfptBannerEnd

Hej experts,

I have an IOC that talks to a PLC-ish system.

The PLC gives us some names for enmums, resulting in a call to

pC_->doCallbacksEnum()

However,  most often the response from the PLC comes back

to the IOC before the record has registered for the callback.

And the enums in the mbbi record are not updated.

Delaying the polling does work around this problem -

but is there a better solution ?