User's Manual
Datalogic Scanning, Inc
959 Terry Street
Eugene, Oregon 97402
Page 17 10/23/2009
Revision X2
PSKEY_AGC_HYST_LEVELS 0x003d agc_hyst_config 0x8, 0x6, 0xb, 0x9
BlueCore contains an automatic gain control algorithm which attempts to maintain a reasonable signal level
by adding and removing various sources of attenuation. This key controls the signal strength at which these
sources are added and removed. It should not be altered except on advice from CSR.
Key Name Key Number Type Default Setting
PSKEY_NO_CAL_ON_BOOT 0x0042 bool FALSE
Setting this key to TRUE causes the LC not to calibrate the radio at boot time. This means that the radio
will not work until the key is set to false and the chip is rebooted. This key is intend to allow the use of a
bootmode where the radio is disabled. (For details on bootmodes, see the document "Understanding and
Using Bootmodes", document number CS-101528-AN (previously numbered as bcore-an-019P) on the
CSR support website).
(Type bool is fundamentally a uint16 with values 0 and 1 mapping to FALSE and TRUE.)
Key Name Key Number Type Default Setting
PSKEY_RSSI_HI_TARGET 0x0043 uint8 80
This key controls a parameter used by BlueCore's automatic gain control (AGC) algorithm. It should not be
changed except on advice from CSR.
Key Name Key
Number
Type Default Setting
PSKEY_PREFERRED_MIN_ATTENUATION 0x0044 uint8 4
See the description of PSKEY_LC_RSSI_GOLDEN_RANGE for 21.x builds.
Key Name Key
Number
Type Default Setting
PSKEY_LC_COMBO_DOT11_PRIORITY_OVERRIDE 0x0045 bool FALSE
If this key is set to TRUE then all Bluetooth activity will be treated as high priority.
See also PSKEY_LC_COMBO_PRIORITY_PIO_MASK
.
Key Name Key Number Type Default Setting
PSKEY_LC_MULTISLOT_HOLDOFF 0x0047 TIME 300 * MILLISECOND
The BT 1.2 specification recommends that in low power modes the master should use single slot packets to
help the slave resynchronise. This would be at the sniff instant or at the end of a hold.
However, a too literal following of this rule can cause bandwidth problems with short sniff intervals as the
master will use single slot packets frequently.
Clearly, for really short sniff intervals, the slave should find it not signficantly harder to resynchronise than
it does in active mode and in active mode multi-slot packet are encouraged.
So, a more lax interpretation, but still within the spirit of the spec, would be to use the single slot behaviour
only when the sniff interval or hold period has been long enough that the slave might need some help