RE: asynPortDriver callParamCallbacks(); not working but callParamCallbacks(0); working

[Mark Rivers via Tech-talk <tech-talk@aps.anl.gov>]

Hi Hugo,

 

If I understand what you are saying correctly, you see a different behavior when you call

 

callParamCallbacks();

 

vs

 

callParamCallbacks(0);

 

That does not make sense to me.  This is the code in asynPortDriver:

 

/** Calls callParamCallbacks(0, 0) i.e. with both list and asyn address. */

asynStatus asynPortDriver::callParamCallbacks()

{

    return this->callParamCallbacks(0, 0);

}

 

/** Calls callParamCallbacks(addr, addr) i.e. with list=addr, which is normal. */

asynStatus asynPortDriver::callParamCallbacks(int addr)

{

    return this->callParamCallbacks(addr, addr);

}

 

/** Calls paramList::callCallbacks(addr) for a specific parameter list.

  * \param[in] list The parameter list number.  Must be < maxAddr passed to asynPortDriver::asynPortDriver.

  * \param[in] addr The asyn address to be used in the callback.  Typically the same value as list. */

asynStatus asynPortDriver::callParamCallbacks(int list, int addr)

{

    return this->params[list]->callCallbacks(addr);

}

 

Note that:

callParamCallbacks simply calls callParamCallbacks(0,0)

callParamCallbacks(0) also simple calls callParamCallbacks(0,0)

 

Ultimately both call this->params[list]->callCallbacks(addr);

 

So I don’t see how they can behave differently.

 

Please send more evidence for your claim that they behave differently.

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> On Behalf Of Hugot Sebastien via Tech-talk
Sent: Monday, February 18, 2019 10:19 AM
To: tech-talk@aps.anl.gov
Subject: asynPortDriver callParamCallbacks(); not working but callParamCallbacks(0); working

 

Hello,

 

I was relieved to find the solution of an asyn problem I had (behavior change from 4-26 to 4-27).

(https://epics.anl.gov/tech-talk/2015/msg01713.php)

 

Now, when I use the code,

   setParamStatus(param, ASYN_SUCCESS);  /* If it might previously have been an error code */

   setXXXParam(param, value);

   callParamCallbacks();

   setParamStatus(param, ASYN_ERROR);  /* Or other error */

  callParamCallbacks();

does not update the value of my parameter,

 

but with this version (using callParamCallbacks(0); instead of callParamCallbacks();)

   setParamStatus(param, ASYN_SUCCESS);  /* If it might previously have been an error code */

   setXXXParam(param, value);

   callParamCallbacks(0);

   setParamStatus(param, ASYN_ERROR);  /* Or other error */

  callParamCallbacks(0);

the parameter value is updated.

 

Do you have any idea for such a behavior ?

 

I am using asyn4-32.

 

Sébastien.

---

Préservons notre environnement, n’imprimez ce mail que si nécessaire.
Preserve our environment, print this email only if necessary.