Experimental Physics and Industrial Control System
|
Mark, Thanks for such a quick response! Yeah, I forgot to include that dbd. I have recompiled and here what I've got: drvAsynIPPortConfigure("L0", "172.20.92.3", 0, 0, 0)
drvAsynIPPortConfigure: "172.20.92.3" is not of the form "<host>:<port> [protocol]"
Port L0 connectDevice failed: asynManager:connectDevice port L0 not found asynOctetSetOutputEos("L0",0,"\n") Port L0 connectDevice failed: asynManager:connectDevice port L0 not found
Which port should I use: 172.20.92.3:80? The 80th? I don't know actually, but in the Tektronix's prefs (Instrument Setup) I see the option Http Port: 80. Though, I don't know this is the correct port. I presume, it's just for the simple http access via the internet browser. I'm stuck. Please, help!
PAvelOn Mon, Mar 5, 2012 at 6:38 PM, Mark Rivers <[email protected]> wrote:
Hi Pavel,
This error
ERROR: vxi11Configure is not supported on WIN32
is expected because there is no support for VXI-11 on win32-x86, because we don't have an implementation of Sun RPC for win32-x86, which the VXI-11 support requires.
However, this error:
drvAsynIPPortConfigure("L0", "172.20.92.3", 0, 0, 0)
st.cmd -- Line 50 -- Command drvAsynIPPortConfigure not found.
is not expected. The drvAsynIPPortConfigure command works fine on win32-x86. You must have a mistake in building your application, perhaps you forgot to include "drvAsynIPPort.dbd" in your dbd file.
Mark
________________________________
From: [email protected] [[email protected]] on behalf of Pavel Masloff [[email protected]]
Sent: Monday, March 05, 2012 8:31 AM
To: EPICS Tech Talk; Nicholas P. DiMonte
Subject: TDS 3000 on win32-x86
Hi Nick et al. :
I am trying to use your Tektronix TDS-3000 support on win32-x86. And I have found that it neither works via "Direct network connection" nor "GPIB/LAN connection":
ERROR: vxi11Configure is not supported on WIN32
Is there a possibility to talk to the TDS 3054C device any other way on win32? If so, could you give me a hint?
If using "Remote serial port", the following errors occur:
drvAsynIPPortConfigure("L0", "172.20.92.3", 0, 0, 0)
st.cmd -- Line 50 -- Command drvAsynIPPortConfigure not found.
asynOctetSetInputEos("L0",0,"\n")
Port L0 connectDevice failed: asynManager:connectDevice port L0 not found
asynOctetSetOutputEos("L0",0,"\n")
Port L0 connectDevice failed: asynManager:connectDevice port L0 not found
--
Best regards,
Pavel Maslov, MS
Controls Engineer at Pulsed power Lab
Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia
Mobile: +7 (951) 672 22 19
Phone: +7 (812) 461 01 01
-- Best regards,
Pavel Maslov, MS Controls Engineer at Pulsed power Lab Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia
Mobile: +7 (951) 672 22 19
Phone: +7 (812) 461 01 01
-- Best regards,
Pavel Maslov, MS Controls Engineer at Pulsed power Lab Efremov Institute for Electro-Physical Apparatus St. Petersburg, Russia
Mobile: +7 (951) 672 22 19
Phone: +7 (812) 461 01 01
- Replies:
- RE: TDS 3000 on win32-x86 Mark Rivers
- References:
- TDS 3000 on win32-x86 Pavel Masloff
- RE: TDS 3000 on win32-x86 Mark Rivers
- Navigate by Date:
- Prev:
RE: BOY FAQ Chen, Xihui
- Next:
RE: TDS 3000 on win32-x86 Mark Rivers
- 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
- Navigate by Thread:
- Prev:
RE: TDS 3000 on win32-x86 Mark Rivers
- Next:
RE: TDS 3000 on win32-x86 Mark Rivers
- 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
|
ANJ, 18 Nov 2013 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|