Help: ICE_NETWORK_ICENET
utility for communicating with ICE services macro from outside Midas
The ICENET routine in the $ICEROOT/test directory can be used to control and/or test ICE Network Appliances.
The public interface includes all control widgets exposed by the macro.
These controls are accessed by key=value pairs where the key is the label of the control.
The labels are listed in the page http://<host>:<port>/Controls or by the readout when a graphical widget has focus.
To set a control, use the key=value syntax and just the key or key= to perform a get.
To start or stop an appliance that has already been instantiated:
>ice net SET udp:192.168.0.199:7777/192.168.0.123:9000 ACTION=REC
>ice net SET udp:192.168.0.199:7777/192.168.0.123:9000 ACTION=STOP
where 192.168.0.199 is the address of the controller NIC card
and 192.168.0.123 is the address of the ICE Appliance.
To change the frequency of the 1st snapper case in the appliance:
>ice net SET udp:192.168.0.199:7777/192.168.0.123:9001 FREQ=10
By default, the SET and GET verbs address control widgets only. The routine can also be used
to access any other object in the macro registry or reslts table. For instance:
>ice net SET udp:192.168.0.199:7777/192.168.0.123:9001 "/Controls?FREQ=10"
sets the same control as the previous example, and
>ice net GET udp:192.168.0.199:7777/192.168.0.123:9001 "/Registry/SP?CYCLE"
gets the current cycle count of the sourcepic primitive SP.
The ICENET routine can also acquire a snapshot of packet data off a local NIC card.
By default, this routine checks for packet sequence errors and determines the aggregate data rate.
To test a packet stream coming from an ICE Appliance for rate and/or drops:
>ice net ACQ udp:192.168.0.199:7777/224.1.40.%d:7777 testfile ICE 40e6 10
The loop count can be used to run the command multiple times with a single call.
If the multicast address contains an %d, the loop count will be inserted to allow looping
through a series of channels as if from a tuner bank.
For a description of each parameter, type:
>ice net
with no arguments.
For more examples of icenet commands, see the HELP on ICE_NETWORK_SERVICE.