Experimental Physics and Industrial Control System
Hi all,
I have a soft IOC running on Linux PC, connected to a modbus TCP server using Asyn (v4.19) ModbusTCP (v2.4) driver,
EPICS R3.14.2.
in my IOC I run the two following records:
record(longin, tstRB) {
field(SCAN, "I/O Intr")
field(DTYP, "asynInt32")
field(INP, "@asyn($(EQPT):Read_All 2)MODBUS_DATA")
field(TPRO, "1")
}
record(longin, tstRB2) {
field(SCAN, "I/O Intr")
field(DTYP, "asynUInt32Digital")
field(INP, "@asynMask($(EQPT):Read_All 2 0 0xFFFF )MODBUS_DATA")
field(TPRO, "1")
}
Both records read the same register in the modbus table which I know is a constant value.
At execution time, I have the following messages for the record tstRB using asynInt32 but no messages related to tstRB2
using asynUInt32Digital:
cbLow: Process tstRB
cbLow: Process tstRB
cbLow: Process tstRB
cbLow: Process tstRB
cbLow: Process tstRB
If I use asynFloat64 iso asynInt32 I also have the messages,
I expected no messages in all cases since the read value is not changing, I didn't expected the behaviour to be DTYP
dependent ... Am I wrong ?
Regards
begin:vcard
fn:Christophe Haquin
n:Haquin;Christophe
email;internet:[email protected]
tel;work:02 31 45 46 61
x-mozilla-html:FALSE
version:2.1
end:vcard
- Replies:
- RE: Unexpected Processing Trace (TPRO) Mark Rivers
- Navigate by Date:
- Prev:
RE: TPG261 : "message too small=0" for EPICS Mark Rivers
- Next:
CS-Studio Census Eric Berryman
- 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: TPG261 : "message too small=0" for EPICS Sanguk Won
- Next:
RE: Unexpected Processing Trace (TPRO) Mark Rivers
- 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