Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
W
White Rabbit Trigger Distribution
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
White Rabbit Trigger Distribution
Commits
da3f42d9
Commit
da3f42d9
authored
Jul 23, 2019
by
Dimitris Lampridis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[doc] minor doc updates
parent
e3f72058
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
6 additions
and
6 deletions
+6
-6
basic_concepts.rst
doc/basic_concepts.rst
+3
-4
devel.rst
doc/devel.rst
+2
-1
introduction.rst
doc/introduction.rst
+1
-1
No files found.
doc/basic_concepts.rst
View file @
da3f42d9
...
...
@@ -113,12 +113,11 @@ Local Channels represent the connections of a :ref:`node` to its environment. Th
inputs or outputs.
A Local Channel input delivers input Events to the :ref:`node`. Typical examples include the
external trigger
out
put of a digitiser, a Time to Digital Converter (TDC) or a TTL input channel on
external trigger
in
put of a digitiser, a Time to Digital Converter (TDC) or a TTL input channel on
a digital I/O board.
A Local Channel output receives output Events from the :ref:`node`. Typical examples include the
external trigger input of a digitiser, a Fine Delay generator or a TTL output channel on a digital
I/O board.
A Local Channel output transmits output Events from the :ref:`node`. Typical examples include a Fine
Delay generator or a TTL output channel on a digital I/O board.
All Local Channels use reserved :ref:`Event IDs <event_id>`.
...
...
doc/devel.rst
View file @
da3f42d9
...
...
@@ -12,7 +12,8 @@ an existing WRTD Node, please refer to :numref:`usage` instead.
It should be noted that a new Node does not necessarily need to use the resources provided by the
WRTD project itself. In fact, the only hard requirement is that the Node must be able to send and/or
receive :ref:`Event Messages <message>` over an Ethernet-based LAN, using multicast UDP on address
``224.0.23.159``, port ``5044``.
``224.0.23.159``, port ``5044``. It should also respect the :ref:`event_id` naming conventions of
WRTD.
Of course, the above is the absolute minimum requirement, which is already fullfilled by any LXI
device supporting the relevant LXI extended functions (see also :ref:`lxi`).
...
...
doc/introduction.rst
View file @
da3f42d9
...
...
@@ -64,7 +64,7 @@ Relation to IVI and LXI
`LAN eXtensions for Instrumentation (LXI) <http://www.lxistandard.org>`_ is a standard, defining a
communication protocol for the remote control of instrumentation over an Ethernet-based LAN.
Version 1.5 of the LXI splits the specification in two parts:
Version 1.5 of the LXI s
tandard s
plits the specification in two parts:
#. The `LXI Core Specification`_, to which all LXI Devices must conform.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment