| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: asynDriver/asynGpib |
| From: | "LYNCH, Damien" <[email protected]> |
| To: | [email protected] |
| Date: | Mon, 13 Mar 2006 09:45:02 +1100 |
It may be useful to say that this question is related to a posting around January 7 with the subject "A couple of drvAsyn/devGpib questions". Just to re-cap I'm trying to write some support for a serial device connected to a local serial port.
> First I agree with Mark's comment about trying to upgrade to a later
> verson of asyn.
>
Me too. When I get some time I'm going to upgrade the base and I'll upgrade asynDriver then as well.
> I suspect that you are implementing a devGpib module and have
> specified
> one of the following commands:
>
> GPIBACMD|GPIBREADW|GPIBEFASTIW|GPIBIFC
> |GPIBREN|GPIBDCL|GPIBLLO|GPIBSDC|GPIBGTL|GPIBSRQHANDLER
That's right. GPIBSRQHANDLER.
> But you have connected to a port driver that is not a gpib controller.
> Perhaps just a serial port driver?
>
Yep, that's right as well. In my st.cmd file is a drvAsynSerialPortConfigure() line.
I'll go back to a snipet the earlier "A couple of drvAsyn/devGpib questions" reply from Marty and ask the question I probably should have asked to begin with.
> I will describe two possibilities: 1) a devGpib implementation and 2) a
> devEpics implementation.
> I would suggest the devEpics for reasons given below.
>
> But first the devGpib implementation
>
> Have your port Driver implement interface asynGpibPort.
How do I do this?
Thanks,
Damien.