> No. Just use @init {readRegister;}
>
> Example:
> readRegister { out "\$1"; in "%i";}
> writeRegister { ... @init {readRegister;} }
This is interesting. It means that writeRegister and readRegister must
have the same parameters and in the same order. readRegister($1, $2) for
example would seem more intuitive, besides I could also do
readRegister($2,$1), or readRegister(23,$3), etc.
I looked at the aai record.
Why is the aai record not compiled in?
I suspect it is because R3.13 did not include it in its epics bases, is
this the case?
I noticed that my IN directive for a protocol is hitting a limit.
I did not investigate this problem in depth.
But I am faced with the situation where I have something like
in "%*x,%*f,%*i,%*X,%*f,%*f,%*f,%*f,%*f,%*f,%*f,%*f,%*f, (a few
more ;-),%*f,%*f" ;
If the IN directive is too long (or there are too many converter
matching), then the program complains and do not work.
Is there a "length" and/or "number" limit(s) on the directives?
I use a device with crc/checksum checking. the converter works very
well. But the communication is flaky. So I get crc errors for 20% of my
messages. As a result my IOC terminal is flooded with asyn/stream error
messages. Is there a way to disable those globally? or locally at the
protocol level?
Before implementing the aai record, I tried with several ai configured
as I/O intr scanned records.
1/ For one of my devices, I have the reply from the device broken in two
segments and the matching by the I/O intr ai is not working.
The matching would clearly work on the complete reply.
The situation I am facing is similar to
the value is in the first reply segment, but I need to check the crc
which is in the other segment of the reply.
What the pollTimeout parameter to control just that?
2/ I have another device with whom I can do 1 ai trigger record ( with
the OUT directive) and several ai records configured as I/O intr. I
noticed that the trigger record times out (STAT = TIMEOUT right after
all the @init complete) if too many I/O intr records are attached.
Is that expected? Do I/O intr record lock the asyn interface?
Finally (and this is on my wish list), I would like to have protocol
directives able to communicate on different asyn interfaces.
For example, I would like to OUT on an asyn file interface for debugging
purpose or IN on again a another asyn file interface for the init value.
Right now, I can do that but it requires each time rewriting the asyn
interface code. So allowing for the asyn port/interface to be set in the
protocol would be welcome.
Cheers,
--
Emmanuel
- Replies:
- Re: Stream protocol configuration Dirk Zimoch
- References:
- writing your own stream cronverter Emmanuel Mayssat
- Re: writing your own stream cronverter Emmanuel Mayssat
- Re: writing your own stream converter Emmanuel Mayssat
- Stream protocol configuration Emmanuel Mayssat
- Re: Stream protocol configuration Dirk Zimoch
- Re: Stream protocol configuration Emmanuel Mayssat
- Re: Stream protocol configuration Dirk Zimoch
- Navigate by Date:
- Prev:
Build of edm 1-11-0zi errors Margaret Smith
- Next:
First announcement on the next EPICS collaboration meeting /EPICS seminar SQLiu
- 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: Stream protocol configuration Dirk Zimoch
- Next:
Re: Stream protocol configuration Dirk Zimoch
- 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
|