Campaign Scan and Send Time Settings

Campaign Scan and Send Time Settings

The default campaign timeout and scan frequency settings are usually good enough for the majority of cases and these controls are only included for advanced users.

1. Scan query length is how long the scanning Bluetooth radio should spend looking for new devices. When a scan takes place it is carried out for this set period of time which once elapsed all the results are returned from the Bluetooth driver to Unicast Lite for processing. Results do not come in as they are found, rather they are totalled up in the Bluetooth device driver over a predetermined period of time.

   
   
   

   This field should be left with the value 0 if you want to let the Bluetooth driver optimise this scan time automatically.

   
   
   

2. Ignore query length toggles between two different searching algorithms.

   
   
   

   When not selected a faster algorithm is used which is capable of optimising its scan query length (1) or have one set.

   
   
   

   When selected a slower but much more thorough algorithm is used, this performs several scans checking for various criteria and returns a larger result set. This can perform quite well in low footfall areas but we would still not recommend using this unless absolutely necessary. In higher footfall areas this scan could take several minutes to return its results and is therefore undesirable unless the dwell time of target devices is extremely long.

   
   
   

   Generally this option should be left unselected.

   
   
   

3. Scan interval is the amount of time to wait between scans, this is measured from the time that the last scan finished. A general rule of thumb for setting this value is:

   
   
   

   short for low footfall and short dwell time

   
   
   

   long for high footfall and long dwell time

   
   
   

4. Send time out is the time out for each action performed during a Bluetooth OBEX send to the target device. It is the time out when establishing Bluetooth connection, opening the OBEX connection and for each message pair which sends the OBEX file packets. This is not a timeout for the total time of the send to the device.

   
   
   

For more information on Unicast please refer to the BlueAd Unicast FAQ.