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 2021 2022 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 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | ASYN Connection feedback |
From: | Mathew Hicks <[email protected]> |
To: | [email protected] |
Date: | Tue, 9 Jun 2009 11:14:25 -0700 |
I am running into a problem with ASYN connection feedback I was wondering if anyone could help. Here's what I have set up:
Hardware: I have an IOC running on debian which communicates via ethernet to an Agilent E5801A LAN/GPIB Gateway which then communicates to several GPIB Power Supplies.
In st.cmd I set up asyn ports using
���� vxi11Configure("Portname",
"192.128.0.X", 0, 1000, "gpib0")
and also reboot the gateway using
���� E5810Reboot("192.168.0.64",0)
I then have databases running that do appropriate string formatting for GPIB commands and put them in the .AOUT field of an ASYN record configured as follows:
� DTYP= asynRecordDevice
� PORT=Portname
� ADDR=GPIB_ADR
� TMOD=READ/WRITE
The communication works fine and the device responds as commanded. The problem I am running into is when I physically unplug the Ethernet cable between the gateway and IOC, I get read/write errors in the ERRS field when the record processes but it still says �Connect� in the .CNCT field.
With other devices using
� drvAsynIPPortConfigure
� modbusInterposeConfig
� drvModbusAsynConfigure
The ASYN records .CNCT field changes when I unplug the Ethernet cable to Disconnect.
I tried setting up a drvAsynIPPortConfigure to talk with the gateway and to see if the connection is monitored that way, couldn't get that to work either. I don't think it ever establishes a valid communication link because it starts out as disconnect and I get timeout messages from traceError in the IOC shell.
I am wondering where I what to do next. Should I try creating device support for the devices connected to the gateway, would it even be possible through device support? Has anyone encounter this problem and came up with a solution? Any help is appreciated.
Thanks,
Mathew Hicks