| 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: | RE: Agilent E8257D Device Support? |
| From: | "Mark Rivers" <[email protected]> |
| To: | "Gaul, Robert" <[email protected]>, <[email protected]> |
| Date: | Fri, 29 May 2009 16:08:20 -0500 |
|
Hi Robert, If you can’t find existing support
then I would recommend streamDevice. streamDevice is independent of the
underlying transport mechanism (RS-232, GPIB, Ethernet). It provides the
device support for standard EPICS records, building the strings to send to the
device and parsing the responses. You don’t need to write any C code,
just a protocol file. The Agilent E8257D implements the “SCPI”
protocol, which is a nice industry standard ASCII protocol for controlling
devices. Mark From:
[email protected] [mailto:[email protected]] On Behalf Of Hello, I
was wondering if anyone had device drivers directly for the Agilent E8257D
microwave signal generator? If
drivers do not exist directly then I figure that you can connect it via GPIB to
a LAN/GPIB gateway (Agilent E5810) and that this gateway has EPICS device
drivers that include asynDriver and StreamDevice. My questions, if this is the
route we have to go, is as follows: -
Does anyone have support written
for the 8257D using the gateway? -
Would StreamDevice be needed? I
want to say no because the 8257 is not RS-232 but I may be wrong in how I look
at the architecture of everything Any
help from the community is helpful and I want to thank everyone in advance! Robert
Gaul III Student Assistant NSLS II |