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.