Querying the availability of named pods – Achronix Bitporter User Manual
Page 40
Querying the Availability of Connected Pods (-q option)
Using the Achronix STAPL Player
PAGE 34
Bitporter User Guide
With this information, the user would subsequently connect to either usb12345 or net12347,
via the -p command‐line option.
Querying the Availability of Named Pods
There are two typical cases where a user would desire to query the state of specific pods by
name:
1.
The user wishes to query the availability of a non‐local pod (a Bitporter connected to a
different Ethernet subnet than the host running the STAPL Player).
2.
There are multiple pods visible from the host, but the user only wishes to query a sub‐
set of these pods for performance reasons.
Unlike other pod interaction modes (‐a and ‐i), pod status queries will check the status of all
named pods, and will not stop at the first successful connection.
Unlike Autodetection mode, when pods are specifically named with ‐p, the availability status
table will include a status entry for unavailable USB pods and non‐local Ethernet pods. It will
also include an error status for any pod names which could not be found.
Similar to Autodetection mode, the availability results are returned in tabular form, with the
first column containing the pod name, and the second column containing availability
information. If there were errors detecting the availability of a pod, the error information will
be included in the second column.
The availability results table will be sorted first by availability, then by the order of the names
given by the user. Available pods will always be listed before unavailable pods, which will in
turn be listed before pods which could not be found.
The following pod states can be expected:
USB pod names:
Named USB pods will be shown in one of two states.
•
If the pod is successfully found, this means it is available, and its detected availability
will be shown as ++AVAILABLE++.
•
Otherwise, when the pod is not found, this means it is either not connected to the
host, or it is in use by another instance of acx_stapl_player. In this case, the pod status
will be shown as --in use or not connected--.
Ethernet pod names:
There are several possible states that may be shown for named Ethernet pods.
•
If the pod is successfully detected and is available, the status shown will be
++AVAILABLE++
.
•
If the pod is successfully detected but is not available (it is already in use), the listed
status will be --in use, owner is
will be the address of the host that is currently utilizing the named Bitporter.
•
If the podname contains a serial number, and the pod is not detected, the status will
be --No available Achronix Bitporter products with matching
serial number found on local subnet.--
(Remember that podnames with
serial numbers only reach the local Ethernet subnet; pods on a different subnet from
the host must be named using their IP address.)
•
If the podname contained an IP address, and nothing was found at that address, the
status will be --No available Achronix Bitporter product found at
supplied network address.--
.