Experimental Physics and Industrial Control System
|
Hi all,
Unfortunately, Emma is wrong. Because of the way how %(myRecord.fieldName) is
implemented, myRecord is never processed when the read does not succeed. I just
don't get to the point to find out about myRecord when there is no input to parse.
Also forwarding connection problems to I/O Intr records is not don in
StreamDevice yet. Because it is not supported by asyn, I would have to add a yet
another hack and have my own list of I/O Intr connected to any particular asyn
port/address. That is something I can probably do.
Dirk
Shepherd, EL (Emma) wrote:
Hi Stephen,
One thing you could do is to change your implementation slightly. Make
your I/O interrupt records Passive, and change your protocol to
explicitly map each part of the message to the required records using
the "%(myRecord.fieldName)" syntax of format converters.
I'm fairly sure this should make the records go invalid if communication
fails... but someone correct me if I'm wrong.
Emma
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Schuh, Stephen
Sent: 18 March 2008 20:27
To: [email protected]
Subject: Severity of I/O interrupt records
I am using streamdevice to communicate with a VME crate
controller. One record sends a query string to the crate and
receives a string as a reply. The reply string contains a
lot of information and needs to be mapped to several records.
The records that receive this information are all
streamdevice records with I/O interrupt processing. This all works.
My problem is that I want the severity of all the I/O
interrupt records to be set to invalid if there is a problem
with the communication to the crate. The record that sends
the query string has invalid severity in this case. Can
anyone suggest a nice way to propagate that invalid severity
to all the I/O interrupt records? I thought about disabling
the records, but I think I would need to process the records
to make this work, and I don't know how to cause I/O
interrupt records to process. Is there an asyn option that
will cause I/O interrupt records to process after a
connection problem?
thank you,
Stephen
<DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
</FONT></DIV>
--
Dr. Dirk Zimoch
Paul Scherrer Institut, WBGB/006
5232 Villigen PSI, Switzerland
Phone +41 56 310 5182
- References:
- RE: Severity of I/O interrupt records Shepherd, EL (Emma)
- Navigate by Date:
- Prev:
Re: EPICS: Selecting a Text Error Message Emmanuel Mayssat
- Next:
CALC expression feature request Benjamin Franksen
- 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:
RE: Severity of I/O interrupt records Shepherd, EL (Emma)
- Next:
Re: Severity of I/O interrupt records Tim Mooney
- 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
|
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|