Sync Status
The Sync Status command directs Frontline software to send the status of the Bluetooth devices being tested every time it changes. This command can also tell Frontline software to stop sending the status of the Bluetooth devices being tested. This command can only be used when testing Classic Bluetooth.
Note: Once you turn on Sync Status, it sets a flag in Frontline software to export the state. If the state of any device changes, you are notified.
The following table identifies what each status color means.
| Color Code | Sync Status Description |
|---|---|
| Red | Unknown, Pending, Halted (State=0-2) |
| Green | Waiting for master to connect to the slave (State=4) |
| Blue | Synchronized with the master clock – link active (State=5) |
| Gray | Synchronized with the master clock – link inactive (State=6) |
| Yellow | Waiting for the master to resume transmission (State=7) |
The following is an example of the command string for this command. The ON parameter for the command tells Frontline software to send the status; the OFF parameter tells Frontline software to stop sending the status. This command is not supported by the ComProbe low energy product.
| Sync Status;On | (returns and turns on the subscription for all links) |
| Sync Status;On;1 | (returns and turns on the subscription for link 1) |
| Sync Status;On;1,2 | (returns and turns on the subscription for links 1 & 2) |
| Sync Status;Off | (turns off the subscription for all) |
You can only subscribe once at a time. You must unsubscribe before subscribing again.
For Frontline BPA 500 only, the status is never returned for the gray state (6) which is synchronized with the master clock - link inactive. State 5 which is blue is only returned when the link initially goes in sync.
For Frontline FTS4BT all the states are returned.
If you have 2 links up and you subscribe for the first one, you will only get status for that link.
An error can occur if the devices under test are (1) not Bluetooth devices, (2) an invalid command is sent, or (3) an invalid synchronization state is passed back from Frontline software, etc. If a failure occurs, a failure notification response is sent. The form for the failure notification response is the following.
Sync Status;FAILED;Timestamp=10:43:00,10/05/2006;Reason=Invalid synchronization state
A successful attempt to sync the status results in a successful notification response. The form for the successful notification response is the following.
Sync Status;SUCCEEDED;Timestamp=5/18/2007 10:44:00 AM;State=1