Having SCAN="I/O Intr" is somewhat unusual for output records. Are you sure this is what you want? I ask this because it is the reason that you don't see the record process when you write to it -- 'process on write' occurs only if SCAN="Passive".
On Oct 4, 2011, at 6:20 AM, PELLE Sébastien wrote:
> Hello,
>
> I am currently writing an EPICS device support using the asyn framework.
>
> I have an issue : when writing the PV, It does not fall into the write function whereas the write function is called during iocInit (PINI = 1).
>
> Here is my record (I have some other like this) :
>
> record(bo, "$(P)$(R)boDevice_Status_ColdReset")
> {
> field(PINI, "1")
> field(DTYP, "asynUInt32Digital")
> field(OUT, "@asynMask($(PORT),$(ADDRESS),0x00000001,$(TIMEOUT))BODEVICE_STATUS_COLDRESET")
> field(SCAN, "I/O Intr")
> field(ONAM, "Device Cold Reset")
> field(ZNAM, "Nothing will happen")
> }
>
> When writing to it (dbpf <portName>: boDevice_Status_ColdReset 1) the my writeUInt32Digital is not called. No idea why.
>
> I tried with the SCAN field = 1 second : the write function is called every second. However, this is not the behavior I want.
>
> Does anyone have any idea why this write function is not called ?
>
> Thanks a lot,
>
> Best Regards,
> Sébastien PELLÉ
> Tel : +33 (0)4 76 61 87 09
> Fax : +33 (0)4 76 41 47 47
> [email protected]
> 36, chemin du vieux chêne
> BP 104
> 38243 Meylan Cedex
>
> ________________________________
>
>
> Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
>
>
--
Eric Norum
[email protected]
- Replies:
- RE: asynUInt32Digital write callback function not called PELLE Sébastien
- References:
- asynUInt32Digital write callback function not called PELLE Sébastien
- Navigate by Date:
- Prev:
RE: the seq that launched a thousand seqs Laznovsky Michael
- Next:
Re: Sequence monitor not getting callback Shankar, Murali
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
asynUInt32Digital write callback function not called PELLE Sébastien
- Next:
RE: asynUInt32Digital write callback function not called PELLE Sébastien
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|