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  <20102011  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  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: asyn port question
From: Eric Norum <[email protected]>
To: Michael Davidsaver <[email protected]>
Cc: EPICS tech-talk <[email protected]>
Date: Fri, 9 Apr 2010 11:39:39 -0700
On Apr 9, 2010, at 11:12 AM, Mark Rivers wrote:

> Hi Michael,
> 
> You should be able to do what you propose fairly easily.  You may even
> be able to do it with the asyn "Interpose Interface" mechanism, which
> will just add the header.

Yep.
For simple command/reply transactions an asynOctet interface interposed on top of an asynIPPort and below StreamDevice or devGpib might be all that's needed.
For SRQ handling and such you may need to write the equivalent of drvVxi11.

> 
> However, that may or may not be the best way to do it.  I just looked at
> the Lecroy manual, and I see that they do not seem to even document what
> IP port number one uses when communicating with the scope?  What they do
> document is their ActiveDSO interface, which uses ActiveX.  That is
> another route you could use.  I have EPICS asyn drivers that use ActiveX
> (Microsoft COM) for controlling Windows objects.  In my case it is the
> Roper Scientific WinView program for CCD cameras.  
> 
> It's a choice: you can talk to the device with the lower-level commands
> (if you can get enough documentation from them), or with the higher
> level functionality of the ActiveDSO interface.

The advantage of the low-level approach, of course, is that your IOC isn't tied to windows.  The disadvantage is that prying the required information out of a vendor might be difficult or impossible (I'm looking at you, Tektronix).

<rant>
It is incredibly annoying that manufacturers seem unable to utilize well-established standards (VXI-11 in this case) and instead run off and develop their own protocols! And then tie these protocols to windows.
</rant>

-- 
Eric Norum
[email protected]






References:
asyn port question Davidsaver, Michael
RE: asyn port question Mark Rivers

Navigate by Date:
Prev: RE: asyn port question Mark Rivers
Next: RE: asyn port question Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: asyn port question Mark Rivers
Next: RE: asyn port question Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·