![]() |
RFID API Documentation
1.0
Reference guide for RFID API
|
This struct is used to specify the storage settings related to Tags using RFID_SetTagStorageSettings. More...
Data Fields | |
| UINT32 | maxTagCount |
| Maximum Tag Count maintained in the API internal Queue. More... | |
| UINT32 | maxMemoryBankByteCount |
| Maximum Size of Memory Bank in Bytes (Should be WORD aligned, i.e. More... | |
| UINT32 | maxTagIDByteCount |
| Maximum size of EPC Data in Bytes (Should be WORD aligned, i.e. More... | |
| UINT16 | tagFields |
| Bit field indicating contents of TAG_DATA. More... | |
| BOOLEAN | enableAccessReports |
| Indicates whether Dll should enable reporting of TAG_DATA for access operations like Write, Lock, Kill, etc. More... | |
| BOOLEAN | discardTagsOnInventoryStop |
| Option to discard the tags which are reported by the reader when inventory/access-sequence operation has been stopped by a call to RFID_StopInventory or RFID_StopAccessSequence. More... | |
| UINT32 | reserved32 |
| for future expansions other than pointers types More... | |
| LPVOID | lpReserved [4-2] |
| Reserved for future. More... | |
This struct is used to specify the storage settings related to Tags using RFID_SetTagStorageSettings.
Maximum size of the settings are not retricted and could be adjusted as per requirements/constraints of the machine (device/host) on which the application is executed.
| UINT32 TAG_STORAGE_SETTINGS::maxTagCount |
Maximum Tag Count maintained in the API internal Queue.
| UINT32 TAG_STORAGE_SETTINGS::maxMemoryBankByteCount |
Maximum Size of Memory Bank in Bytes (Should be WORD aligned, i.e.
double bytes).
| UINT32 TAG_STORAGE_SETTINGS::maxTagIDByteCount |
Maximum size of EPC Data in Bytes (Should be WORD aligned, i.e.
double bytes).
| UINT16 TAG_STORAGE_SETTINGS::tagFields |
Bit field indicating contents of TAG_DATA.
It inturn specifies whether certain fields are required to be processed by the Reader/Dll. Absence of certain fields can improve performance of the Reader/Dll or result in specific behavior. For e.g. disabling Antenna Id can result in application receiving as single unique tag even though there were multiple entries of the same tag reported from different Antennas
| BOOLEAN TAG_STORAGE_SETTINGS::enableAccessReports |
Indicates whether Dll should enable reporting of TAG_DATA for access operations like Write, Lock, Kill, etc.
By default, this will be false, which implies reports will be enabled only for Inventory, Read and Block-permalock Access operations.
| BOOLEAN TAG_STORAGE_SETTINGS::discardTagsOnInventoryStop |
Option to discard the tags which are reported by the reader when inventory/access-sequence operation has been stopped by a call to RFID_StopInventory or RFID_StopAccessSequence.
Choosing this option will not purge the tags which are already queued by the Dll. This option will be ignored if tagReportTrigger of TRIGGER_INFO is not equal to 1.
| UINT32 TAG_STORAGE_SETTINGS::reserved32 |
for future expansions other than pointers types
| LPVOID TAG_STORAGE_SETTINGS::lpReserved[4-2] |
Reserved for future.