Start Capture
The Start Capture command starts the capture of data between devices being tested. The Start Capture command should only be sent after a successful FTS Start command has been processed. For Bluetooth devices only, the Start Capture command does not start the sniffing processing, which is the case for all other devices supported by Frontline software. The following is an example of the command string for this command.
Start Capture
When you start Frontline software, the client side is responsible for keeping track of the connections, not the server. For example, Client A is first connected to the Frontline software application and Client B is connected to a second instance of Frontline software application. Then both are disconnected. If Client B is reconnected first, it will be connected to the first instance of ComProbe application, not the second as it was originally.
The client is also responsible for the Sniff, Capture, and Sync On states.
If an error occurs - which could be due to (1) a time out waiting for the Start Capture command to process or (2) the Frontline software has not been started, then a failure notification response is sent from the server. The form for the failure notification response is the following.
Start Capture;FAILED;Timestamp=14:25:00,10/05/2006;Reason=FTS not started
A successful attempt to start capturing will result in a successful notification response. The form for the successful notification response is the following.
Start Capture;SUCCEEDED;Timestsamp=14:26:00,10/05/2006