Re: "@init handler failed" , "Record initialization failed" and "No reply from device within 1000 ms"

[Eric Norum <wenorum@lbl.gov>]

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
wenorum@lbl.gov