Re: gateway won't set "busy" PV type properly

[Dennis Nicklaus <nicklaus@fnal.gov>]

Thanks everyone for your helpful explanations and comments. We'll give 
the CA gateway with base 3.14.11 a try, but it is nice to understand why 
its working this way.
Dennis

Dirk Zimoch wrote:
> Hi Dennis,
>
> I had similar problems with the motor record. Build the latest version 
> of ca gateway with base 3.14.11 or higher and the problem should be 
> fixed.
>
> Starting from 3.14.11, the portable ca server, which is used in the 
> gateway, is able to distinguish between put and put-callback requests. 
> Before, the gateway always did put-callbacks, even if the client (e.g. 
> medm) didn't. However, the motor record, the busy record and some 
> other record types from synApps related to long-term actions (i.e. 
> scans) don't sent the callback until the action they perform has 
> finished (not when the action has successfully started as all the 
> other records do). That blocked the gateway.
>
> Dirk
>
> Dennis Nicklaus wrote:
> > We've encountered an odd behavior the last couple days that has us 
> > pretty confused.
> > Can someone please explain this and/or suggest a fix?
> > When I set a certain PV going through an EPICS gateway, the setting 
> > doesn't "work*" entirely.
> > If set through a non-gateway-ed connection, everything works fine.