EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20212022  2023  2024  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Question about "error calling writeRead" in modbus
From: "Wang, SuYin Grass via Tech-talk" <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 1 Jul 2021 15:21:44 +0000
Hi Everyone, 

I have a question about asyn and modbus
I am running the soft IOC with a modbus simulator. Since I don't have permission on the workstation running simulator, I am using port 4502 instead 502
The IOC and simulator run fine, according to "trace_debug.txt" the reading and writing are reasonable.
It is just when the IOC boot up, there is always one line of error about "error calling writeRead" right after the drvModbusAsynConfigure for the writing function.
Any advice? 

Thanks!
Grass

===========st.cmd=================================================
##this line is for simulator; this is Modbus TCP, but for this device we must set noProcessEos to 0
drvAsynIPPortConfigure("RKamp","xxx.xxx.xxx.xxx:4502",0,0,0)

modbusInterposeConfig("RKamp",0,2000,0)

drvModbusAsynConfigure("ctrl",      "RKamp",1,6,1, 3,0,100,"RKamp")
2021/07/01 09:55:26.074 drvModbusAsyn::doModbusIO port ctrl error calling writeRead, error=xxx.xxx.xxx.xxx:4502 timeout: Resource temporarily unavailable, nwrite=6/6, nread=0
drvModbusAsynConfigure("UINT32",    "RKamp",1,3,1,70,0,2000,"RKamp")
drvModbusAsynConfigure("INT32",     "RKamp",1,3,1,70,4,2000,"RKamp")
=============================================================================


========the  trace_debug.txt===================
2021/06/30 18:21:30.574 xxx.xxx.xxx.xxx:4502 write 12

00 09 00 00 00 06 01 03 00 01 00 46
2021/06/30 18:21:30.575 xxx.xxx.xxx.xxx:4502 read 149

00 09 00 00 00 8f 01 03 8c 00 00 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 00 00 c9 00 ca 00 cb 00 00 00 00 00 00 00
0b 00 0b 00 0b 00 0b 00 0b 00 0b 00 0b 00 0b 00 0b 00 0b 00
0b 00 0b 00 16 00 16 00 16 00 16 00 16 00 16 00 16 00 32 00
2021/06/30 18:21:31.511 xxx.xxx.xxx.xxx:4502 write 12

00 0a 00 00 00 06 01 03 00 01 00 01
2021/06/30 18:21:31.512 xxx.xxx.xxx.xxx:4502 read 11

00 0a 00 00 00 05 01 03 02 00 00
2021/06/30 18:21:31.513xxx.xxx.xxx.xxx:4502 write 12

00 0b 00 00 00 06 01 06 00 01 00 01
2021/06/30 18:21:31.513 xxx.xxx.xxx.xxx:4502 read 12

00 0b 00 00 00 06 01 06 00 01 00 01
=================================================

Replies:
Re: Question about "error calling writeRead" in modbus Mark Rivers via Tech-talk

Navigate by Date:
Prev: Re: EPICS compilation Torsten Bögershausen via Tech-talk
Next: Re: Using CALC value to set NELM in subArray Johnson, Andrew N. via Tech-talk
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  <20212022  2023  2024 
Navigate by Thread:
Prev: Re: EPICS compilation Mark Rivers via Tech-talk
Next: Re: Question about "error calling writeRead" in modbus Mark Rivers via Tech-talk
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  <20212022  2023  2024 
ANJ, 05 Jul 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·