Hi Phil,
Do you see your driver output if you don't send the asynTrace output to a file, but rather just to the default of stdout?
Are you sure that you set the mask for the correct asyn port, i.e. the port for your driver and not the port for an underlying TCP driver or a plugin? It should work, you don't need to initialize anything. You are seeing the messages from asynPortDriver and asynManager, but just not the ones from your driver.
You can see the current setting of the trace masks with the asynReport function. Look at the sixth output line below.
epics> asynReport 1 PS1
PS1 multiDevice:No canBlock:Yes autoConnect:No
enabled:Yes connected:Yes numberConnects 3
nDevices 0 nQueued 0 blocked:No
asynManagerLock:No synchronousLock:No
exceptionActive:No exceptionUsers 1 exceptionNotifys 0
traceMask:0x1 traceIOMask:0x2 traceInfoMask:0x1
Prosilica camera PS1 Unique ID=101271
PvAPI version: 1.26
ID: 101271
IP address: 164.54.160.58
Serial number: 02-2142A-06178
Camera name: GC1380H
Model: GC1380H
Firmware version: 00.01.42.02
Access flags: 6
Sensor type: Mono
Sensor bits: 12
Sensor width: 1360
Sensor height: 1024
Frame buffer size: 2785280
Time stamp freq: 54687500
maxPvAPIFrames: 2
Since you are directing the output to a file the problem could also be file flushing. If you set the trace file back to "" then it will flush and close your log file and direct the output back to stdout.
Mark
________________________________
From: [email protected] [[email protected]] on behalf of Phil Atkin [[email protected]]
Sent: Tuesday, April 26, 2016 3:40 AM
To: [email protected] list
Subject: Generating log output from areaDetector IOC
Hi,
I can't see my output from asynPrint.
I turn on debugging using the asynRecord.opi (masks are 0x1F and 0x7, and I set the filename), and the log file is created and contains 'other' messages. But messages I try to generate are absent. I am seeing lots of events such as these:
2016/04/26 09:34:08.344 Camera1 addr -1 queueRequest priority 0 not lockHolder
2016/04/26 09:34:08.344 asynManager::portThread port=Camera1 callback
2016/04/26 09:34:08.344 asynPortDriver:readFloat64: function=44, value=2.872490
2016/04/26 09:34:08.344 RIXSCam1:Camera1:PoolUsedMem devAsynFloat64 process value=2.872490
My code looks (e.g.) like this:
asynPrint(this->pasynUserSelf, ASYN_TRACE_FLOW,
"%s:%s: New CCD power setting detected\n", _driverName, functionName);
What might cause this to fail to output anything? Do I need to call some initialization function?
Thanks,
Phil
--
[cid:[email protected]]Pixel Analytics is a limited company registered in England. Company number: 7747526; Registered office: 93A New Road, Haslingfield, Cambridge CB23 1LP
- Replies:
- Re: Generating log output from areaDetector IOC Phil Atkin
- References:
- Generating log output from areaDetector IOC Phil Atkin
- Navigate by Date:
- Prev:
Generating log output from areaDetector IOC Phil Atkin
- Next:
Re: EPICS_TIMEZONE and TZ on RTEMS Michael Davidsaver
- 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:
Generating log output from areaDetector IOC Phil Atkin
- Next:
Re: Generating log output from areaDetector IOC Phil Atkin
- 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
|