Experimental Physics and
Industrial Control System

Folks,

 

I’m trying to understand the –q option to pvMonitor.  This is the help output:

 

TahoeU18:/corvette/home/epics/scratch> /corvette/usr/local/epics-devel/base-7.0.5/bin/linux-x86_64-ub18/pvmonitor -h

 

  -q:                Quiet mode, print only error messages

  -d:                Enable debug output

deprecated options:

  -q, -t, -i, -n, -F: ignored

 

It appears to have contradictory information.  It says that –q is quite mode and prints only error messages, and then it says that –q is deprecated.

oops, my mistake.  I don't recall if '-q' did anything prior to #129.  Currently it is a no-op.

https://github.com/epics-base/pvAccessCPP/pull/129

 

...

It would be really nice to be able to limit the output of pvmonitor, similar to the -# option in camonitor. ...

The PVXS utilities (pvxget and pvxmonitor) have '-#'.

Although at this stage these aren't so friendly as they don't yet do special case formatting for eg. NTScalar like the pvAccessCPP tools do.

 

Can someone also explain what the –Mraw flag to pvget and pvmonitor does?  I don’t see any difference in the output with and without that option:

There is no special case handling for your example case in pvAccessCPP, so "raw" is the default.  Try with NTScalar, NTScalarArray, NTEnum, or NTTable to see a difference.

 

TahoeU18:/corvette/home/epics/scratch> /corvette/usr/local/epics-devel/base-7.0.5/bin/linux-x86_64-ub18/pvget -r "value" 13SIM1:Pva1:Image | more

13SIM1:Pva1:Image structure

    union value

        float[]  [912445,912446,912447,912448,912449,912450,912451,912452,912453,912454,912455

 

TahoeU18:/corvette/home/epics/scratch> /corvette/usr/local/epics-devel/base-7.0.5/bin/linux-x86_64-ub18/pvget -r "value" -Mraw 13SIM1:Pva1:Image | more

13SIM1:Pva1:Image structure

    union value

        float[]  [912445,912446,912447,912448,912449,912450,912451,912452,912453,912454,912455,

 

Thanks,

Mark

 

References:

pvMonitor questions Mark L Rivers via Core-talk

Navigate by Date:

Prev: epics-base-7.0-win64s-test - Build # 358 - Fixed! APS Jenkins via Core-talk

Next: epics-7.0 » mac - Build # 370 - Failure! APS Jenkins via Core-talk

Index: 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: pvMonitor questions Mark L Rivers via Core-talk

Next: epics-7.0 » mac - Build # 370 - Failure! APS Jenkins via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <2021>  2022  2023  2024