warning about the rpc port (trbnetd) for old designs is added

diff --git a/trb3/GbEGettingStarted.tex b/trb3/GbEGettingStarted.tex
index 71de81fff8783abdff098e4cbccd81a3513440b1..8ca5e172fc7cafb631aa7e6fb60df3d81386ff29 100644 (file)
--- a/trb3/GbEGettingStarted.tex
+++ b/trb3/GbEGettingStarted.tex
@@ -1,9 +1,17 @@
 \label{sec:GbeGettingStarted}
-In order to control TRB3 or a larger system with TRB3 as slow control client via Ethernet link, one needs to properly install and compile the trbcmd server, load a correct FPGA design and configure DHCP deamon on the server PC.Follow the instructions described in the next points.
+In order to control TRB3 or a larger system with TRB3 as slow control client
+via Ethernet link, one needs to properly install and compile the trbcmd
+server, load a correct FPGA design and configure DHCP deamon on the server
+PC.Follow the instructions described in the next points.
 
 \subsubsection{FPGA design}
-The optical link, activated for the Slow Control over GbE is the one labelled SFP8.
-After loading the design, TRB3 will automatically start to send control packets once per second. With any network monitoring tools (ex. Wireshark) one have to capture such packet and check the source MAC address. This address has to be added to the DHCP configuration on Slow Control server PC. MAC address is generated basing on the unique ID assigned to each FPGA and a constant part: 02:00:BE:UNIQUE$\_$ID(31 downto 8)
+The optical link, activated for the Slow Control over GbE is the one labelled
+SFP8. After loading the design, TRB3 will automatically start to send control
+packets once per second. With any network monitoring tools (ex. Wireshark) one
+have to capture such packet and check the source MAC address. This address has
+to be added to the DHCP configuration on Slow Control server PC. MAC address
+is generated basing on the unique ID assigned to each FPGA and a constant
+part: 02:00:BE:UNIQUE$\_$ID(31 downto 8) 
 
 \begin{itemize*}
 \item Open /etc/dhcpd.conf and add an entry specifing hostname and MAC address
@@ -11,24 +19,24 @@ After loading the design, TRB3 will automatically start to send control packets
 \item Restart DHCP daemon
 \end{itemize*}
 
-Now you can reload the central FPGA and it should automatically aquire the IP address from the server. One can verify that by monitoring the network traffic or system log file.
+Now you can reload the central FPGA and it should automatically aquire the IP
+address from the server. One can verify that by monitoring the network traffic
+or system log file.
 
 \subsubsection{Trbnetd}
 To access the TRB3 you can access it directly with trbcmd (the local version
-found in ``trbsoft/trbnettools/libtrbnet'', but this is
-not recommended and only meant to be used by experts for debugging.
-To find out which version of trbcmd one uses you can type "trbcmd -V"
-and in the output you will either find "Local TRB3" (local version) or "RPC"
-for the RPC version.
-The correct way is to use a trbnetd running on any machine in the
-network, which has direct UDP access to the TRB3 to be controlled. This daemon
-then collects all requests from many different clients and takes care of the
-correct arbritration (doesn't work for non atomic accesses, like SPI-interface
-which needs to access several registers one after the other).
-The trbnetd needs to know the ip-address of the TRB3 and *can* additionally be
-identified via a 8 bit number.
-So, to start the trbnetd which connects to the TRB3 with the ip-name trb30 one
-has to start the trbnetd in the following way:
+found in ``trbsoft/trbnettools/libtrbnet'', but this is not recommended and
+only meant to be used by experts for debugging. To find out which version of
+trbcmd one uses you can type "trbcmd -V" and in the output you will either
+find "Local TRB3" (local version) or "RPC" for the RPC version. The correct
+way is to use a trbnetd running on any machine in the network, which has
+direct UDP access to the TRB3 to be controlled. This daemon then collects all
+requests from many different clients and takes care of the correct
+arbritration (doesn't work for non atomic accesses, like SPI-interface which
+needs to access several registers one after the other). The trbnetd needs to
+know the ip-address of the TRB3 and *can* additionally be identified via a 8
+bit number. So, to start the trbnetd which connects to the TRB3 with the
+ip-name trb30 one has to start the trbnetd in the following way:
 \begin{verbatim}
  TRB3_SERVER=trb030 trbnetd
 \end{verbatim}
@@ -39,6 +47,14 @@ It is recommended to write down explicitly the RPC-id-number when starting the d
 \end{verbatim}
 to start the trbnetd with the id 9.
 
+\begin{warning}
+  For GbE designs older than August 2013 the correct port number for RPC
+  communication has to be given, e.g:
+  \begin{verbatim}
+    TRB3_SERVER=trb030:25000 trbnetd -i 9
+  \end{verbatim}
+\end{warning}
+
 To access this trbnetd one uses trbcmd with the address of the daemon given in
 the environment variable DAQOPSERVER, e.g.:
 \begin{verbatim}

diff --git a/trb3/trb3qs_configuration.tex b/trb3/trb3qs_configuration.tex
index 7300543f65d9b3ed8c06f3919256cd78bbf1dcf2..698c399032d45c0b418f7d676d98c2b032bb8274 100644 (file)
--- a/trb3/trb3qs_configuration.tex
+++ b/trb3/trb3qs_configuration.tex
@@ -181,6 +181,14 @@ DAQOPSERVER=localhost:1 trbcmd i 0xffff
 0xf306  0xfc00000390225628  0x02
 0xf306  0xb600000390225b28  0x03
 \end{lstlisting}
+\begin{warning}
+  For GbE designs older than August 2013 the correct port number for RPC
+  communication has to be given, e.g:
+  \begin{verbatim}
+    TRB3_SERVER=trb033:25000 trbnetd -i 1
+  \end{verbatim}
+\end{warning}
+
 
 If we have several TRB3 and we don't know which TRBnets are assigned to them, we
 can easily find them with following commands

diff --git a/trb3/trb3qs_software.tex b/trb3/trb3qs_software.tex
index 7d26f422fbd4bf09c5e83d03325f33705041ea86..6986a2b6d25e45f7cc388b60a7c362a7e6d13b22 100644 (file)
--- a/trb3/trb3qs_software.tex
+++ b/trb3/trb3qs_software.tex
@@ -62,6 +62,16 @@ $HOME/trbnettools/trbnetd/server/trbnetd -i 11
 
 \end{lstlisting}
 
+\begin{warning}
+  For GbE designs older than August 2013 the correct port number for RPC
+  communication has to be given, e.g:
+  \begin{verbatim}
+    export TRB3_SERVER=trb046:25000
+    pkill -f "trbnetd -i 11"
+    $HOME/trbnettools/trbnetd/server/trbnetd -i 11
+  \end{verbatim}
+\end{warning}
+
 This script only has to be started if the server you are using to communicate
 with the TRB3 has been rebooted.