Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
<== Date ==> <== Thread ==>

Subject: Re: pvput JSON syntax
From: Mark Rivers via Core-talk <core-talk@aps.anl.gov>
To: Ralph Lange <ralph.lange@gmx.de>
Cc: "core-talk@aps.anl.gov" <core-talk@aps.anl.gov>
Date: Thu, 16 Jan 2020 12:05:53 +0000
Ralph,


When the bug reporter ran "pvput-h" they did not specify a path for pvput.  That version reported "JSON support is present".  When they actually tried to use the JSON support they specified the path as /usr/bin/pvput.  Is it possibly they have 2 different verions of pvput on their system?


Mark



________________________________
From: Core-talk <core-talk-bounces@aps.anl.gov> on behalf of Ralph Lange via Core-talk <core-talk@aps.anl.gov>
Sent: Thursday, January 16, 2020 4:35 AM
To: EPICS Core Talk
Subject: pvput JSON syntax

Dear Core colleagues,

I have a new CODAC Core System (CCS) bug on my desk, saying:

New: pvput does not support anymore JSON field assignment
The command line help does not mention this removal of functionality.
$ pvput -h
Usage: pvput [options] <PV name> <value>
       pvput [options] <PV name> <size/ignored> <value> [<value> ...]
       pvput [options] <PV name> <field>=<value> ...
       pvput [options] <PV name> <json_array>
       pvput [options] <PV name> <json_map>
options:
  -h: Help: Print this message
  -V: Print version and exit
  -r <pv request>:   Request, specifies what fields to return and options,
default is ''
  -w <sec>:          Wait time, specifies timeout, default is 5.000000
second(s)
  -p <provider>:     Set default provider name, default is 'pva'
  -M <raw|nt|json>:  Output mode.  default is 'nt'
  -v:                Show entire structure (implies Raw mode)
  -q:                Quiet mode, print only error messages
  -d:                Enable debug output
 Deprecated options:
  default: Auto - try value as enum string, then as index number
  -n, -s, -F, -t: ignored
  -f <input file>: error
 JSON support is present
Examples:
  pvput double01 1.234       # shorthand
  pvput double01 value=1.234
  pvput arr:pv X 1.0 2.0  # shorthand  (X is arbitrary and ignored)
  pvput arr:pv "[1.0, 2.0]"            # shorthand
  pvput arr:pv value="[1.0, 2.0]"
Field values may be given with JSON syntax.
Complete structure
  pvput double01 '{"value":1.234}'
Sub-structure(s)
  pvput group:pv some='{"value":1.234}' other='{"value":"a string"}'
$ /usr/bin/pvput PVA-SRV-TESTS:INTEGER '{"value":4321}'
JSON syntax not supported by this build.

The previous CCS version was using EPICS 7.0.2 (libpvAccess 6.1.0), the one we're preparing for uses EPICS 7.0.3.1 (libpvAccess 7.1.0). I don't see any mention of this in the release notes of pvAccess [1].

Any suggestions?

Cheers,
~Ralph

[1] https://docs.epics-controls.org/projects/pvaccess-cpp/en/latest/doxygen/pvarelease_notes.html

References:
pvput JSON syntax Ralph Lange via Core-talk

Navigate by Date:
Prev: Re: pvput JSON syntax Timo Korhonen via Core-talk
Next: Re: pvput JSON syntax Ralph Lange via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
Navigate by Thread:
Prev: Re: pvput JSON syntax Michael Davidsaver via Core-talk
Next: RE: Arithmetic calculations before sending a command Mark Rivers via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
ANJ, 20 Jan 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·