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: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms"
From: Mark Rivers <[email protected]>
To: "'Eric Norum'" <[email protected]>, epics Talk <[email protected]>
Cc: ??? <[email protected]>
Date: Thu, 24 May 2012 16:07:17 +0000
Yes, I agree, but he said he is running asyn R4-6, which is over 6 years old and does not support that :-)

Mark


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Eric Norum
Sent: Thursday, May 24, 2012 10:54 AM
To: epics Talk
Cc: ???
Subject: Re: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms"

On May 24, 2012, at 8:44 AM, Mark Rivers wrote:

>> asynSetTraceMask("MOXA1",0,255)
>> 2012/05/24 16:14:12.091 MOXA1 -1 exceptionOccurred calling exceptionUser
>> But when asynSetTraceMask("MOXA1",0,1),there is no the error message.
> 
> The message you see above about "exceptionOccurred" is not an error, it is just for information.  So setting asynTraceMask to 255 is fine.
> 
>> 2012/05/24 16:14:15.200 192.168.127.254:4001 write.
>> 2012/05/24 16:14:15.200 192.168.127.254:4001 write 11
>> 2012/05/24 16:14:15.200 MOXA1 write
> ...
>> 2012/05/24 16:14:15.201 192.168.127.254:4001 read.
>> 2012/05/24 16:14:16.200 MOXA1 MOXA1:getPosition: No reply from device within 1000 ms
> 
> These messages are telling you that you have sent 11 bytes to the device, but that you got no reply from the device.  If set asynTraceMask to 255 you will see exactly what characters you sent to the device, and can verify that they are correct.  For some reason the device is not answering you.  That could be a problem with cabling (pins 2&3) or with baud rate, parity, etc.
> 
> You can set the baud rate, parity, etc. on the Moxa through a Web interface.

Yes, but I think that it's preferable to set the serial port parameters from the st.cmd script since it makes it easier to swap LAN/serial adapters when one goes bad.
All the MOXA units which which I am familiar support RFC-2217.

-- 
Eric Norum
[email protected]




Replies:
Re: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" Eric Norum
References:
"@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" 洪春霞
RE: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" Mark Rivers
Re: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" Eric Norum

Navigate by Date:
Prev: Re: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" Eric Norum
Next: Re: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" Eric Norum
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: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" Eric Norum
Next: Re: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms" Eric Norum
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 ·