RFID_STATUS WINAPI RFID_SetTagStorageSettings ( RFID_HANDLE32  readerHandle,
LPTAG_STORAGE_SETTINGS  lpTagStorageSettings 
)

This function allows configuring the maximum Tag-storage capacity of the DLL and the storage to be allocated in the Tag data-structure (TAG_DATA) for the Memory-Bank data.

Parameters:
[in] readerHandle 
Handle to the RFID device.
[in] lpTagStorageSettings 
Pointer to TAG_STORAGE_SETTINGS.
Returns:
If the function succeeds the return value is RFID_API_SUCCESS. If the function fails the return value is one of the following:
  • RFID_API_INVALID_HANDLE Handle provided is invalid
  • RFID_API_PARAM_ERROR Invalid parameter given
Remarks:
If the application does not call this function, default settings will be used, maxTagCount is 4096, maxMemoryBankByteCount is 64 bytes (512 bits) and maxTagIDByteCount is 12 bytes (96 bits). All the fields of TAG_DATA will be enabled for use by default. The field tagFields which is a member of TAG_STORAGE_SETTINGS can be used to enable/disable fields of TAG_DATA. Tags reported from the Reader as part of Inventory or Access operations will be temporarily queued in the DLL, till the user fetches them using RFID_GetReadTag. When the number of tags queued in the DLL exceeds 90% of maxTagCount, the event registered for BUFFER_FULL_WARNING_EVENT will be signaled once. When the number of tags queued in the DLL exceeds maxTagCount, the event registered for BUFFER_FULL_EVENT will be signaled for each tag that is discarded. Each TAG_DATA structure holds a memory-bank in it, the size of which can be configured so as to optimize the memory. The application can use this API to customize the Tag-size based on requirements.
See also:
RFID_PerformInventory, RFID_StopInventory, RFID_AddPreFilter, RFID_DeletePreFilter, RFID_SetSingulationControl, RFID_AllocateTag
Remarks:
Example: See


Generated on Fri Mar 4 02:25:29 2016 for RFIDAPI3 1.1 C API Documentation by  doxygen 1.5.6