Unibrain API-810, User Manual

Page: 54 / 77

ubCore™ 3.1 User Guide
br | busreset | reset [long|short]
Initiates a bus reset on the local bus. Enter the parameter long or short to
specify the type of the bus reset.
br
and
busreset
display the new physical ID that the current adapter
obtained after the bus reset. reset does not display it so that it is more
convienient to use in automated command scripts.
NOTE : Adapters that comply only with IEEE 1394-1995, but not with
P1394A, do not support short bus resets. In such a case, the request will
fail with a status code of STATUS_1394_INVALID_REQUEST
.
brcount
Displays the bus-reset count for the current adapter. This can be used to
verify the number of bus resets that a test operation caused.
cls | c
Clears the contents of the command window.
delay msec
Creates a delay for the given number of msec. Useful when a sequence of
commands is executed from a file (see command file) and an artificial delay
period must be created.
dir, cd, del, copy, a:, b:, …, z:
These commands are passed directly to the system command shell
(cmd.exe or other). This way you can run these common commands
without leaving the 1394 command interpreter window.
file infile [outfile]
Reads and executes a series of commands from the file specified by
infile
. If
outfile
is provided as well, then the output of all commands
that will be executed will be redirected to that file. Otherwise the output will
be displayed on screen.
file commands cannot be nested; a script file with 1394 commands cannot
contain another file command.
A line in a script file that starts with either ‘;’ or ‘#’ is considered as a
comment and is ignored by the interpreter.
gap [gap_count]
Without an argument, the command prints the gap_count value of the
current adapter. With a number between 1 and 63 as argument, the
command transmits a PHY configuration packet that sets the gap_count of
all the stations on the local bus to this number.
Remember that selfID packets contain the value of a node’s gap_count at
the time of the bus reset. If you run the gap command and then the
topology command without an intervening bus reset, you will still see the
old values in the selfID packets.
However a PHY configuration packet is immediately effective. If you run
gap 31 on node A, and then run gap on node B, you will see that the
gap_count of node B has become 31.
The 1394 protocol mandates that after two bus resets the gap_count of a
node is reset to 63.
54