Baracoda IDBlue 补充手册
IDBlue – Communication Protocol v2.4.1
- 12 -
Data Capture
for Workforce
in Motion
Device Configuration
The IDBlue™ device supports a number of configuration properties. These properties are either
persistent properties (saved to the on-board EEPROM, and “remembered” when the device is shut
down), or session properties (active until the next device shutdown).
In firmware versions prior to 2.4, the IDBlue™ was configured through two sets of discrete
configuration commands; one for default/persistent properties, and one for session properties. That
configuration model has been replaced by these four commands, providing a streamlined and more
extensible method for device configuration:
persistent properties (saved to the on-board EEPROM, and “remembered” when the device is shut
down), or session properties (active until the next device shutdown).
In firmware versions prior to 2.4, the IDBlue™ was configured through two sets of discrete
configuration commands; one for default/persistent properties, and one for session properties. That
configuration model has been replaced by these four commands, providing a streamlined and more
extensible method for device configuration:
• LOAD_DEFAULT_AS_SESSION. Overrides the current session properties of the device with
the saved persistent settings. This is the same operation performed by the IDBlue™ during
power-up.
• SAVE_SESSION_AS_DEFAULT. Writes the current session properties of the device to the
EEPROM, persisting these values between shutdowns.
• GET_PROPERTY. Retrieves the current value of a session property.
• SET_PROPERTY. Sets the current value of a session property.
the saved persistent settings. This is the same operation performed by the IDBlue™ during
power-up.
• SAVE_SESSION_AS_DEFAULT. Writes the current session properties of the device to the
EEPROM, persisting these values between shutdowns.
• GET_PROPERTY. Retrieves the current value of a session property.
• SET_PROPERTY. Sets the current value of a session property.
These four commands allow for the configuration of every IDBlue™ parameter, except for the
Bluetooth® name and PIN code. Developer-focused information on certain ky properties is presented
below, with the full table of properties is listed in Appendix A – Properties.
Bluetooth® name and PIN code. Developer-focused information on certain ky properties is presented
below, with the full table of properties is listed in Appendix A – Properties.
Continuous Scanning Flag
One of the powerful new features introduced in the 2.4 firmware release is the continuous scanning
flag. This mode enables each of the connected and disconnected asynchronous operations (note:
except for the REACTIVE / Button Press mode) to “continuously” scan for tags without requiring the
user to repeatedly push the IDBlue™ hardware button.
This is ideal for scenarios involving bulk scanning, reading or writing of tags. To enable this feature
set the CONTINUOUSSCANNING property to true. With this flag active, a hardware button press will
enable the asynchronous mode; for example, in Normal (or Tag Scan) mode, the device will:
flag. This mode enables each of the connected and disconnected asynchronous operations (note:
except for the REACTIVE / Button Press mode) to “continuously” scan for tags without requiring the
user to repeatedly push the IDBlue™ hardware button.
This is ideal for scenarios involving bulk scanning, reading or writing of tags. To enable this feature
set the CONTINUOUSSCANNING property to true. With this flag active, a hardware button press will
enable the asynchronous mode; for example, in Normal (or Tag Scan) mode, the device will:
• Start scanning for tags when the hardware button is pressed
• Stop scanning for tags when the hardware button is pressed again
• Stop scanning for tags when the hardware button is pressed again
The continuous scan will time out after a certain period of time if no tags are found; this timeout
period is controlled by the CONTINUOUSSCANNINGTIMEOUT property.
In addition, in disconnected Tag Store mode, a duplicate tag filter may be enabled by configuring the
DUPLICATEELIMINATIONTIMEOUT property to a value greater than zero (0).
This filter will cause the not scan or store the same tag ID for a certain period of time.
Note: this filter only applies to the last tag scanned.
Also, in cases where the usage scenario does not require valid timestamps for tags stored in Tag
Store mode, the REQUIRETIMESTAMP property may be set to false. This will configure the IDBlue™
device not to check for a valid timestamp before storing a tag ID, invalid timestamp (all 0’s) and
contents of byte 0.
Note: this filter only applies to the last tag scanned.
Also, in cases where the usage scenario does not require valid timestamps for tags stored in Tag
Store mode, the REQUIRETIMESTAMP property may be set to false. This will configure the IDBlue™
device not to check for a valid timestamp before storing a tag ID, invalid timestamp (all 0’s) and
contents of byte 0.