Hello,
I am trying to communicate over linux-gpib with asyn.
My asyn interface is configured with
GpibBoardDriverConfig("L0",1,0,3,0)
(At this point, that's the ONLY COMMAND I have in my stcmd file)
But when I start the ioc ... BOOM !
2007/08/03 17:54:53.352 L0 addr -1 : EDVR 0: OS error.
2007/08/03 17:54:53.353 asynManager::asynConnectCallback, port L0 error
calling
asynCommon->connect
2007/08/03 17:54:53.353 L0 addr -1 : EDVR 0: OS error.
2007/08/03 17:54:53.353 136742344 autoConnect could not connect
2007/08/03 17:54:53.353 L0 addr -1 : EDVR 0: OS error.
2007/08/03 17:54:53.353 asynManager::asynConnectCallback, port L0 error
calling
asynCommon->connect
The error seesm to be coming from my gpib libraries.
What does EDVR mean? Where does it get this -1 address?
Is my computer smoking?
My primary of interface is set to 0 in gpib.conf...
Am I missing gpib options in my stcmd? Probably...
What are common linux-gpib/drvLinuxGpib options?
Have a great weekend !
--
E
- Replies:
- Re: Enabling drvLinuxGpib (linux-gpib) Gasper Jansa
- Navigate by Date:
- Prev:
RE: asyn float64array interrupt problem Mark Rivers
- Next:
problem in communicating to the gpib device with asyn4-6 zhangdemin99
- 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: Channel Archiver | Matlab Kay-Uwe Kasemir
- Next:
Re: Enabling drvLinuxGpib (linux-gpib) Gasper Jansa
- 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
|