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  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Proposed support for additional Modbus data types
From: haquin <[email protected]>
To: Eric Norum <[email protected]>
Cc: tech-talk <[email protected]>
Date: Fri, 6 Apr 2012 09:01:13 +0200
if I change the mode to I/O Intr after the IOC has started,
data in the waveform are equal to zero, no crash.

I will run this under gdb and send you the trace.



Le 05/04/2012 17:25, Eric Norum a écrit :
On Apr 5, 2012, at 7:19 AM, haquin wrote:

Hi Mark,

I started to test the new release R2-4 of your modbus driver,

1/ I have a regression problem:
in case of "intarray_in" when scan mode is I/O Intr:
Linux IOC crashes with segmentation error message
Could you run this again under GDB and send a stack trace?

VxWorks IOC doesn't crash but data in the waveform are equal to zero

On Linux if I start with the scan mode set to none there is no crash.
What happens if you change the mode to I/O Intr after the IOC has started?

In both cases linux and VxWorks,
if I change the scanning mode to any periodic scan (with a caput in the SCAN field), I do retreive correct data.

here is my drvModbusAsynConfigure
drvModbusAsynConfigure("AR-GT7-PC3:Read_All",    "AR-GT7-PC3", 255,  4 , 0 , 46 , 0 ,  2000 , "InterfaceIocaste")

here is my waveform:
record(waveform, "$(EQPT):ReceiveModbusTable") {
  field(DTYP, "asynInt32ArrayIn")
  field(FLNK, "$(EQPT):TrigModbusTableProcessing")
  field(INP, "@asyn($(EQPT):Read_All 0)MODBUS_DATA")
  field(NELM, "46")
  field(FTVL, "LONG")
  field(SCAN, "I/O Intr")
}

2/ I have tested the retreival of float32_LE with ai record, this is ok

tomorrow I'll test retreival of int32 and also he writting.

best 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


References:
Proposed support for additional Modbus data types Mark Rivers
RE: Proposed support for additional Modbus data types Mark Rivers
Re: Proposed support for additional Modbus data types haquin
RE: Proposed support for additional Modbus data types Mark Rivers
Re: Proposed support for additional Modbus data types haquin
Re: Proposed support for additional Modbus data types Eric Norum

Navigate by Date:
Prev: a question about sequencer wux
Next: RE: a question about sequencer Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Proposed support for additional Modbus data types Eric Norum
Next: Re: Proposed support for additional Modbus data types haquin
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·