I looked at this more closely.
drvAsynIPPortConfigure("MOXA_4", "172.24.192.29:4004", 0, 0, 0)
asynOctetConnect("KeithleyIO", "MOXA_4", "-1",2000)
drvAsynKeithley648x("6485", "MOXA_4","KeithleyIO",0)
asynSetTraceIOMask("MOXA_4", 0, 0x2)
asynSetTraceMask("MOXA_4", 0, 0x9)
dbLoadRecords("db/Keithley6485.db", "P=trARPES:, CA=Sample:, PORT=MOXA_4")
My comments are:
Your original message says that drvAsynKeithley6845 take 3 arguments. Your actual commands call drvAsynKeithey648x with 4 arguments. Why the difference? Does 648x take an initial argument with the exact model number, or is that the name of the new port?
I don't see the need for the asynOctetConnect line.
Maybe this will work:
drvAsynIPPortConfigure("MOXA_4", "172.24.192.29:4004", 0, 0, 0)
drvAsynKeithley648x("6485", "MOXA_4",0)
asynSetTraceIOMask("MOXA_4", 0, 0x2)
asynSetTraceMask("MOXA_4", 0, 0x9)
dbLoadRecords("db/Keithley6485.db", "P=trARPES:, CA=Sample:, "6845")
I deleted the asynOctetConnect, deleted the 3 argument to drvKeithley648x, and changed the port passed in dbLoadRecords.
Is this driver code on Github or somewhere else we can look at it?
Mark
________________________________
From: Mark Rivers
Sent: Wednesday, March 6, 2019 6:34 AM
To: Heinz Junkes
Subject: Re: epics-Keithley_648x, drvAsynKeithley648x
Hi Heinz,
I am not sure, but this line looks wrong to me:
> dbLoadRecords("db/Keithley6485.db", "P=trARPES:, CA=Sample:, PORT=MOXA_4")
It seems that should probably be:
dbLoadRecords("db/Keithley6485.db", "P=trARPES:, CA=Sample:, PORT=KeithleyIO")
The PORT that database talks to is the KeithleyIO, not the underlying TCP port?
Mark
________________________________
From: [email protected] <[email protected]> on behalf of Heinz Junkes via Tech-talk <[email protected]>
Sent: Wednesday, March 6, 2019 3:03 AM
To: tech-talk
Subject: epics-Keithley_648x, drvAsynKeithley648x
I want to use the ip-driver for the Keithley 6485:
/*
Description
This module provides support for a multiple device port driver. To
initialize the driver, the method drvAsynKeithley6485() is called from the
startup script with the following calling sequence.
drvAsynKeithley6485(myport,ioport,ioaddr)
Where:
myport - Keithley6485 Asyn interface port driver name (i.e. "EP0" )
ioport - Communication port driver name (i.e. "S0" )
ioaddr - Communication port device addr
The method dbior can be called from the IOC shell to display the current
status of the driver.
*/
Unfortunately I don't know how to configure the "ioport".
Right now, here's what I'm gonna try in the st.cmd:
drvAsynIPPortConfigure("MOXA_4", "172.24.192.29:4004", 0, 0, 0)
asynOctetConnect("KeithleyIO", "MOXA_4", "-1",2000)
drvAsynKeithley648x("6485", "MOXA_4","KeithleyIO",0)
asynSetTraceIOMask("MOXA_4", 0, 0x2)
asynSetTraceMask("MOXA_4", 0, 0x9)
dbLoadRecords("db/Keithley6485.db", "P=trARPES:, CA=Sample:, PORT=MOXA_4")
Unfortunately there is no communication with the device.
How do I configure this correctly?
Danke,
Heinz
- Replies:
- Re: epics-Keithley_648x, drvAsynKeithley648x Heinz Junkes via Tech-talk
- References:
- epics-Keithley_648x, drvAsynKeithley648x Heinz Junkes via Tech-talk
- Navigate by Date:
- Prev:
Fw: epics-Keithley_648x, drvAsynKeithley648x Mark Rivers via Tech-talk
- Next:
Re: epics-Keithley_648x, drvAsynKeithley648x Heinz Junkes via Tech-talk
- 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:
Fw: epics-Keithley_648x, drvAsynKeithley648x Mark Rivers via Tech-talk
- Next:
Re: epics-Keithley_648x, drvAsynKeithley648x Heinz Junkes via Tech-talk
- 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
|