daqcontrol [-c start | stop] [-t TARGETIP:PORT] ?-t TARGETIP2:PORT2?... [-e ECCSERVER:PORT] ?-p on | off?
-h, --helpOutputs program help text and exits.
-V, --versionOutputs the program version and exits.
-c, --command start | stop
Start or stop the target(s) specified by -t option.
-t, --targets TARGETIP:PORT
CoBo Target IP address and port to execute the command given. Multiple CoBos can be specified by adding multiple -t
-t, --ecc ECCSERVERIP:PORTECC server IP and its port to transmit command to target(s).
-p, --pulser on | offDefault option is off. By setting it on with start command, the internal pulser configured in the configuration file is activated and starts to emit pulses.
With stop command, this option is set off always.
This program is written to replace existing daqstart and daqstop. Additional features on this program is supporting start and stop commands and multiple CoBos in a single binary.
Description below is copied from the old documentation. GET Run control (old way)
These programs initiate (daqstart) and terminate (daqstop) data taking in a CoBo. The assumption they make is that some outside agency, such as GetController has prepared the CoBo for data taking with the desired configuration.
hwnode describes the service on which
the desired CoBo is accepting connections. This is given in
ip-address:service-number format
where ip-address is the dotted
IP address of the CoBo and service-number
is normally 46001.
eccserver describes the service on which the
GET eccserver is accepting connections. This should be given in
ip-address:service-number where
the ip-address is the address of the host
system (spdaq) on the 10Gbit private subnet that connects the
host to the microTCA crate. The service-number
is normally 46002.
You can determine the proper IP addresses for a CoBo by examining the /etc/dhcp/dhcpd.conf which determines which physical ethernet addresses are given which IP addresses. You can determine the proper IP address for the Ecc Server by issuing the command
And examining the IP address of the last ehternet interface. For example; in spdaq08, the command above will give the following output:
eth4 Link encap:Ethernet HWaddr 90:e2:ba:86:7e:bc
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth5 Link encap:Ethernet HWaddr 90:e2:ba:86:7e:bd
inet addr:10.50.200.2 Bcast:10.50.255.255 Mask:255.255.0.0
inet6 addr: fe80::92e2:baff:fe86:7ebd/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1422015 errors:0 dropped:0 overruns:0 frame:0
TX packets:282885 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:563624233 (537.5 MiB) TX bytes:65826892 (62.7 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:7224717 errors:0 dropped:0 overruns:0 frame:0
TX packets:7224717 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:119555197682 (111.3 GiB) TX bytes:119555197682 (111.3 GiB)
See the emphasized part of the eth5 output. The IP address is 10.50.200.2.
The final, optional, parameter for daqstart controls whether or not the internal pulser is started. For pulser tests, this must be 1 (the default). For ordinary data taking (e.g. with external triggers), this should be 0. This is required because GetController e.g. does not turn on the test pulser until its button is clicked.
Note that daqstop unconditionally turns off the test pulser so that if the next run does not explicitly turn it back on, the pulser will remain off.