Skip to content

Commit a17585d

Browse files
authored
Merge pull request #2283 from ControlSystemStudio/pvtree_doc
PV Tree doc
2 parents d321d45 + 03401ea commit a17585d

File tree

1 file changed

+24
-7
lines changed

1 file changed

+24
-7
lines changed

app/pvtree/doc/index.rst

Lines changed: 24 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -56,12 +56,29 @@ Tool Bar Buttons
5656
Limitations
5757
-----------
5858

59-
This tool uses the EPICS network protocol, Channel Access, to read PVs.
60-
There is no way to query EPICS V3 IOCs for their database information
59+
This tool uses the EPICS Channel Access or PV Access network protocols to read PVs.
60+
Note that there is a difference between EPICS records in an IOC and
61+
channels on the network.
62+
There is no way to query EPICS IOCs for their database information
6163
to determine the available "input" links.
6264

63-
The knowledge of which links to follow for each record type is therefore
64-
configured into the EPICS PV Tree application. It is at this time not
65-
configurable by end users, but people with access to the
66-
source code can determine the syntax from the Settings.java file
67-
and override the site-specific settings.
65+
Given a PV name ``x``, the PV tree attempts to read the channel ``x.RTYP``.
66+
If the channel is indeed based on a record, it will report the record type.
67+
The knowledge of which links to follow for each record type is
68+
configured into the EPICS PV Tree application via the ``org.phoebus.applications.pvtree/fields``
69+
preference setting.
70+
This allows maintainers of site-specific settings to add support
71+
for locally developed record types, or add certain output links to the
72+
list of links that the PV tree should trace and display.
73+
74+
The Channel Access protocol adds another limitation to the PV tree operation,
75+
because Channel Access strings are restricted to a length of 40 characters.
76+
The PV tree can therefore not read the complete value of links when they exceed
77+
40 characters. This results in long record names being truncated and then failing to
78+
resolve. As a workaround, the PV tree can read a link ``x.INP`` as ``x.INP$`` with a trailing dollar sign,
79+
which causes the IOC to return the value as a byte waveform without length limitations.
80+
This mode, however, is not supported by older IOCs and older CA gateways.
81+
If your site only runs IOCs and gateways that support the ``x.INP$`` channel name syntax,
82+
you can enable the ``org.phoebus.applications.pvtree/read_long_fields=true`` option in the PV tree preferences.
83+
If your site still runs older IOCs, you won't be able to use the PV tree with them unless you
84+
set ``org.phoebus.applications.pvtree/read_long_fields=false``.

0 commit comments

Comments
 (0)