Experimental Physics and
Industrial Control System

"Szalata, Zenon M." <[email protected]> · Wed, 26 Jan 2011 17:26:25 -0800

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/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
...

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
> 
> 
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System