Experimental Physics and
Industrial Control System

Ralph Lange <[email protected]> · Thu, 29 Mar 2012 12:11:05 +0200

It's an opaque void pointer, used for the callback mechanisms.
Whenever your (user supplied) callback routines are being called,
Channel Access will provide them with the puser argument that you set
when you created the subscription.

Except for its size, there is no restriction on puser.
Usually, it is a pointer to an internal structure in the client, that
the callback routines can use to do their work.
Sometimes, it is an enum, or an array offset.

~Ralph

On 29.03.2012 12:01, Florian Feldbauer wrote:
> Dear all,
>
> I currently write a CA Client that should monitor all measured
> temperatures in my experiment
> to regulate the chillers.
> This is my first try to program a CA Client, and I have a question
> concerning this:
>
> The ca_create_channel and the ca_create_subscription methods both have
> a parameter void* puser. How does this parameter have to look like?
> Can I use a C-Struct with any member I want to have (even members
> which are not
> for the CA, but for another part of my program)? Are there any members
> which are mandatory? (like value or chid)
>
> In the camonitor.c example generated with makeBaseApp.pl this puser is
> just a pointer to a C-Struct containing
> a c-string value, the chid and evid of the channel.
>
> Best regards,
> Florian
>

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System