Hi Tom,
Here is a complete console output:
zms@ar-esaux1 $ ./st.cmd
#!../../bin/linux-x86/example
< envPaths
epicsEnvSet("ARCH","linux-x86")
epicsEnvSet("IOC","iocexample")
epicsEnvSet("TOP","/afs/slac/g/testfac/workspace/zms/rhel5/R3.14.11/ioc/aravisnew/aravisGigE-0-1-2/iocs/example")
epicsEnvSet("EPICS_SITE_TOP","/afs/slac/g/testfac/rhel5/epics/R3.14.11")
epicsEnvSet("EPICS_BASE","/afs/slac/g/testfac/rhel5/epics/R3.14.11/base")
cd "/afs/slac/g/testfac/workspace/zms/rhel5/R3.14.11/ioc/aravisnew/aravisGigE-0-1-2/iocs/example"
epicsEnvSet "EPICS_TS_MIN_WEST", '0'
# Loading libraries
# -----------------
# Device initialisation
# ---------------------
cd "/afs/slac/g/testfac/workspace/zms/rhel5/R3.14.11/ioc/aravisnew/aravisGigE-0-1-2/iocs/example"
dbLoadDatabase "dbd/example.dbd"
example_registerRecordDeviceDriver(pdbbase)
# aravisCameraConfig(portName, cameraName, maxBuffers, maxMemory)
#aravisCameraConfig("CAM1", "Prosilica-02-2166A-06844", 50, -1)
aravisCameraConfig("CAM1", "Basler-20913924", 50, -1)
Looking for camera 'Basler-20913924'... Found 0x8f23500
# NDStdArraysConfigure(portName, queueSize, blockingCallbacks, NDArrayPort, NDArrayAddr, maxMemory)
NDStdArraysConfigure("ARR1", 2, 0, "CAM1", 0, -1)
# Final ioc initialisation
# ------------------------
cd "/afs/slac/g/testfac/workspace/zms/rhel5/R3.14.11/ioc/aravisnew/aravisGigE-0-1-2/iocs/example"
dbLoadRecords 'db/example_expanded.db'
iocInit
Starting iocInit
############################################################################
## EPICS R3.14.11 $R3-14-11$ $2009/08/28 18:47:36$
## EPICS Base built Dec 10 2010
############################################################################
2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_EXPAUTOTARGET
ARAVISCAM1:CAM:ExpAutoTarget_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_GAINAUTOTARGET
ARAVISCAM1:CAM:GainAutoTarget_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_IRISAUTOTARGET
ARAVISCAM1:CAM:IrisAutoTarget_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_IRISVIDEOLEVELMAX
ARAVISCAM1:CAM:IrisVideoLevelMax_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_IRISVIDEOLEVELMIN
ARAVISCAM1:CAM:IrisVideoLevelMin_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_IRISVIDEOLEVEL
ARAVISCAM1:CAM:IrisVideoLevel_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_EXPAUTOTARGET
ARAVISCAM1:CAM:ExpAutoTarget devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_GAINAUTOTARGET
ARAVISCAM1:CAM:GainAutoTarget devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_IRISAUTOTARGET
ARAVISCAM1:CAM:IrisAutoTarget devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_EXPAUTOALG
ARAVISCAM1:CAM:ExpAutoAlg_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.727 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_IRISAUTO
ARAVISCAM1:CAM:IrisAuto_RBV devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.727 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_EXPAUTOALG
ARAVISCAM1:CAM:ExpAutoAlg devAsynInt32::initCommon drvUserCreate
2011/01/26 17:18:55.727 asynPortDriver:drvUserCreate: addr=0, cannot find parameter ARAVIS_IRISAUTO
ARAVISCAM1:CAM:IrisAuto devAsynInt32::initCommon drvUserCreate
cas warning: Configured TCP port was unavailable.
cas warning: Using dynamically assigned TCP port 41779,
cas warning: but now two or more servers share the same UDP port.
cas warning: Depending on your IP kernel this server may not be
cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)
iocRun: All initialization complete
epics>
Thanks again,
Zen
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Thursday, January 27, 2011 12:52 AM
> To: Szalata, Zenon M.; [email protected]; [email protected]
> Cc: [email protected]
> Subject: RE: GigE driver for Area Detector
>
> Hi,
>
> Could you attach the complete list of errors at startup please? The ones
> that I see so far are because the camera doesn't support the same
> feature set as the prosilica. From your XML file, the following are
> supported:
> Gain
> Gain Mode
> Exposure
> White Balance (manual mode may not work properly as the camera also
> allows setting of the green channel)
> All the standard areaDetector parameters supported by aravis
>
> The following won't work:
> Iris
> Exposure algorithm
> Any "Auto target" values
>
> If you copy aravisProsilica.template to aravisBasler.template and remove
> the offending records then it won't print the messages. It looks like
> aravis can talk to your camera, just not some of the features.
>
> Thanks,
>
> Tom Cobb,
> Diamond Light Source Ltd.
> Diamond House
> Harwell Science and Innovation Campus
> Didcot
> Oxfordshire
> OX11 0DE
> Tel +44 (0) 1235 778582
>
> > -----Original Message-----
> > From: Szalata, Zenon M. [mailto:[email protected]]
> > Sent: 27 January 2011 01:26
> > To: Cobb, Tom (DLSLtd,RAL,DIA); [email protected]; Rees, Nick
> > (DLSLtd,RAL,DIA)
> > Cc: [email protected]
> > Subject: RE: GigE driver for Area Detector
> >
> > I have kludged a st.cmd file and when I run example with my st.cmd the
> camera
> > is found. However, then I get many messages which I interpret as
> error
> > messages. Here are some of them:
> >
> > # aravisCameraConfig(portName, cameraName, maxBuffers, maxMemory)
> > #aravisCameraConfig("CAM1", "Prosilica-02-2166A-06844", 50, -1)
> > aravisCameraConfig("CAM1", "Basler-20913924", 50, -1)
> > Looking for camera 'Basler-20913924'... Found 0x8f23500
> > # NDStdArraysConfigure(portName, queueSize, blockingCallbacks,
> NDArrayPort,
> > NDArrayAddr, maxMemory)
> > NDStdArraysConfigure("ARR1", 2, 0, "CAM1", 0, -1)
> > # Final ioc initialisation
> > # ------------------------
> > cd
> "/afs/slac/g/testfac/workspace/zms/rhel5/R3.14.11/ioc/aravisnew/aravisGi
> gE-
> > 0-1-2/iocs/example"
> > dbLoadRecords 'db/example_expanded.db'
> > iocInit
> > Starting iocInit
> >
> #############################################################
> ###########
> ####
> > ## EPICS R3.14.11 $R3-14-11$ $2009/08/28 18:47:36$
> > ## EPICS Base built Dec 10 2010
> >
> #############################################################
> ###########
> ####
> > 2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_EXPAUTOTARGET
> > ARAVISCAM1:CAM:ExpAutoTarget_RBV devAsynInt32::initCommon
> drvUserCreate
> > 2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_GAINAUTOTARGET
> > ARAVISCAM1:CAM:GainAutoTarget_RBV devAsynInt32::initCommon
> drvUserCreate
> > 2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_IRISAUTOTARGET
> > ARAVISCAM1:CAM:IrisAutoTarget_RBV devAsynInt32::initCommon
> drvUserCreate
> > 2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_IRISVIDEOLEVELMAX
> > ARAVISCAM1:CAM:IrisVideoLevelMax_RBV devAsynInt32::initCommon
> drvUserCreate
> > 2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_IRISVIDEOLEVELMIN
> > ARAVISCAM1:CAM:IrisVideoLevelMin_RBV devAsynInt32::initCommon
> drvUserCreate
> > 2011/01/26 17:18:55.725 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_IRISVIDEOLEVEL
> > ARAVISCAM1:CAM:IrisVideoLevel_RBV devAsynInt32::initCommon
> drvUserCreate
> > 2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_EXPAUTOTARGET
> > ARAVISCAM1:CAM:ExpAutoTarget devAsynInt32::initCommon drvUserCreate
> > 2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_GAINAUTOTARGET
> > ARAVISCAM1:CAM:GainAutoTarget devAsynInt32::initCommon
> drvUserCreate
> > 2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_IRISAUTOTARGET
> > ARAVISCAM1:CAM:IrisAutoTarget devAsynInt32::initCommon drvUserCreate
> > 2011/01/26 17:18:55.726 asynPortDriver:drvUserCreate: addr=0, cannot
> find
> > parameter ARAVIS_EXPAUTOALG
> > ...
> >
> > Is it fair to say that aravis as it now is, can't communicate with the
> camera?
> >
> > I have attached an xml dump from the camera.
> >
> > Thanks,
> > Zen
> >
> >
> > > -----Original Message-----
> > > From: [email protected] [mailto: [email protected]]
> > > Sent: Wednesday, January 26, 2011 12:45 PM
> > > To: [email protected]; Szalata, Zenon M.;
> [email protected];
> > > [email protected]
> > > Subject: RE: GigE driver for Area Detector
> > >
> > > Mark is right. We pass the .cmd file through MSI to generate the
> boot
> > > file. The rule is:
> > >
> > > %.boot: ../%.cmd
> > > $(MSI) $(SYS_BOOT_FLAGS) $(USR_BOOT_FLAGS) $< > $@
> > >
> > > This is so we can have identical startup scripts for different
> > > architectures.
> > >
> > > However, in this one off case, it should be easy enough to edit the
> .cmd
> > > file and manually substitute the macros.
> > >
> > > Cheers
> > >
> > > Nick Rees
> > > Principal Software Engineer Phone: +44 (0)1235-778430
> > > Diamond Light Source Fax: +44 (0)1235-446713
> > >
> > >
> > > > -----Original Message-----
> > > > From: [email protected] [mailto:tech-talk-
> > > > [email protected]] On Behalf Of Mark Rivers
> > > > Sent: 26 January 2011 19:35
> > > > To: Szalata, Zenon M.; Cobb, Tom (DLSLtd,RAL,DIA); tech-
> > > > [email protected]
> > > > Subject: RE: GigE driver for Area Detector
> > > >
> > > > I think they generate their startup files from a script. You
> probably
> > > > need to manually create an st.cmd file based on their template.
> > > >
> > > > -----Original Message-----
> > > > From: [email protected]
> > > > [mailto:[email protected]] On Behalf Of Szalata, Zenon
> M.
> > > > Sent: Wednesday, January 26, 2011 1:33 PM
> > > > To: [email protected]; [email protected]
> > > > Subject: RE: GigE driver for Area Detector
> > > >
> > > > Hi Tom,
> > > > I downloaded the tar file from the link below.
> > > > I am having trouble building the examples. I get this error:
> > > >
> > > > make[4]: Entering directory
> > > >
> > >
> `/afs/slac.stanford.edu/g/testfac/vol4/workspace/zms/rhel5/R3.14.11/ioc
> > > > /
> > > >
> > >
> aravisnew/aravisGigE-0-1-2/iocs/example/iocBoot/iocexample/O.linux-x86'
> > > > Installing created file ../../../bin/linux-x86/../stexample.sh
> > > > make[4]: *** No rule to make target
> > > > `../../../bin/linux-x86/stexample.boot', needed by `buildInstall'.
> > > > Stop.
> > > >
> > > > I can't find stexample.boot file. Is it perchance stexample.src?
> > > > Anyway, the file tree structure you are using is different from
> what I
> > > > am used to and right now I feel a bit at a loss.
> > > >
> > > > Thank you,
> > > > Zen
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: [email protected] [mailto:[email protected]]
> > > > > Sent: Monday, January 17, 2011 9:53 AM
> > > > > To: [email protected]
> > > > > Cc: [email protected]; Szalata, Zenon M.
> > > > > Subject: GigE driver for Area Detector
> > > > >
> > > > > Hi all,
> > > > >
> > > > > As a couple of people have asked for it, I've made a preliminary
> > > > release
> > > > > of the my areaDetector driver for GigE cameras on Linux based on
> the
> > > > > aravis library. It is only tested on Prosilica/AVT cameras,
> although
> > > > it
> > > > > should work with all GigE vision compliant cameras but, as
> always,
> > > > some
> > > > > cameras are more compliant than others...
> > > > >
> > > > > http://controls.diamond.ac.uk/downloads/support/aravisGigE
> > > > >
> > > > > Once you have built the module, there are 2 helper programs in
> the
> > > > > bin/linux-x86 directory, arv-show-devices will list all the GigE
> > > > vision
> > > > > cameras visible on the network, and dumpXml will dump their
> Genicam
> > > > xml
> > > > > files to disk. Please email me the outputs of these 2 programs
> if
> > > > your
> > > > > camera doesn't work properly.
> > > > >
> > > > > Thanks,
> > > > > Tom Cobb,
> > > > > Diamond Light Source Ltd.
> > > > > Diamond House
> > > > > Harwell Science and Innovation Campus
> > > > > Didcot
> > > > > Oxfordshire
> > > > > OX11 0DE
> > > > > Tel +44 (0) 1235 778582
> > > > >
> > > > >
> > > > > --
> > > > > This e-mail and any attachments may contain confidential,
> copyright
> > > > and or
> > > > > privileged material, and are for the use of the intended
> addressee
> > > > only. If you
> > > > > are not the intended addressee or an authorised recipient of the
> > > > addressee
> > > > > please notify us of receipt by returning the e-mail and do not
> use,
> > > > copy, retain,
> > > > > distribute or disclose the information in or attached to the
> e-mail.
> > > > > Any opinions expressed within this e-mail are those of the
> > > individual
> > > > and not
> > > > > necessarily of Diamond Light Source Ltd.
> > > > > Diamond Light Source Ltd. cannot guarantee that this e-mail or
> any
> > > > attachments
> > > > > are free from viruses and we cannot accept liability for any
> damage
> > > > which you
> > > > > may sustain as a result of software viruses which may be
> transmitted
> > > > in or with
> > > > > the message.
> > > > > Diamond Light Source Limited (company no. 4375679). Registered
> in
> > > > England
> > > > > and Wales with its registered office at Diamond House, Harwell
> > > > Science
> > > > and
> > > > > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > This e-mail and any attachments may contain confidential, copyright
> and or
> > > privileged material, and are for the use of the intended addressee
> only. If
> > you
> > > are not the intended addressee or an authorised recipient of the
> addressee
> > > please notify us of receipt by returning the e-mail and do not use,
> copy,
> > retain,
> > > distribute or disclose the information in or attached to the e-mail.
> > > Any opinions expressed within this e-mail are those of the
> individual and
> > not
> > > necessarily of Diamond Light Source Ltd.
> > > Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> > attachments
> > > are free from viruses and we cannot accept liability for any damage
> which
> > you
> > > may sustain as a result of software viruses which may be transmitted
> in or
> > with
> > > the message.
> > > Diamond Light Source Limited (company no. 4375679). Registered in
> England
> > > and Wales with its registered office at Diamond House, Harwell
> Science and
> > > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
> > >
> > >
> > >
>
>
> --
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only. If you
> are not the intended addressee or an authorised recipient of the addressee
> please notify us of receipt by returning the e-mail and do not use, copy, retain,
> distribute or disclose the information in or attached to the e-mail.
> Any opinions expressed within this e-mail are those of the individual and not
> necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments
> are free from viruses and we cannot accept liability for any damage which you
> may sustain as a result of software viruses which may be transmitted in or with
> the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England
> and Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
>
- Replies:
- RE: GigE driver for Area Detector Mark Rivers
- References:
- GigE driver for Area Detector tom.cobb
- RE: GigE driver for Area Detector Szalata, Zenon M.
- RE: GigE driver for Area Detector Mark Rivers
- RE: GigE driver for Area Detector nick.rees
- RE: GigE driver for Area Detector Szalata, Zenon M.
- RE: GigE driver for Area Detector tom.cobb
- Navigate by Date:
- Prev:
RE: GigE driver for Area Detector tom.cobb
- Next:
RE: GigE driver for Area Detector 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: GigE driver for Area Detector tom.cobb
- Next:
RE: GigE driver for Area Detector 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
|
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·