2021-10-01 03:10 AM
Hi,
Can we use ST25RU3993 Eval kit in Device mode directly(instead of Host driven), without using the GUI application.
Need to use it directly without using GUI Application for making configuration for detecting the TAGs.
Please let me know if such setting are present or not in the available firmware SDK or any change are required to make it working.
All the supports are highly appreciated.
Thanks
SS
Solved! Go to Solution.
2021-11-10 06:43 AM
Hello,
when using the device mode the FW must be compiled with the STUHFL_DEVICE_MODE define set to 1. Either in the project settings or direct in the code.
Optional the STUHFL_HOST_COMMUNICATION=1 settings must be removed if no host communication is needed.
Code stubs for the usage of the define mode can then found in main.c as starting point for the development.
The code is surrounded with the preprocessor statement #if STUHFL_DEVICE_MODE .. #endif in main.c
Independent of the mode (device or host) the implementation gets notified when TAGs are available with the same callback
static STUHFL_T_RET_CODE cbInventoryCycle(STUHFL_T_InventoryData *cycleData)
The cycleData pointer has some statistic information and provides a list of recent found TAGs.
Howto access this information can be found in the host mode demo code STUHFL_demo.
In general the usage of the STUHFL API is independent of the mode, but a simple print TAGs info to screen is not possible in device mode, only the callback stub is implemented.
BR
Nick
2021-10-11 01:36 AM
Dear SSing.10,
a device mode is possible.
Please check our latest documentation of the SDK which describes this use case.
Cheers,
B
2021-10-27 01:18 AM
Hi Bart Herse,
I gone through the document but could not find actual configuration need to be done for the device mode configuration.
And even there is no further steps available to store the detected tags, if tags detects in device mode configurations.
I kindly request to share steps for the same.
Thanks & Regards
SS
2021-11-10 06:43 AM
Hello,
when using the device mode the FW must be compiled with the STUHFL_DEVICE_MODE define set to 1. Either in the project settings or direct in the code.
Optional the STUHFL_HOST_COMMUNICATION=1 settings must be removed if no host communication is needed.
Code stubs for the usage of the define mode can then found in main.c as starting point for the development.
The code is surrounded with the preprocessor statement #if STUHFL_DEVICE_MODE .. #endif in main.c
Independent of the mode (device or host) the implementation gets notified when TAGs are available with the same callback
static STUHFL_T_RET_CODE cbInventoryCycle(STUHFL_T_InventoryData *cycleData)
The cycleData pointer has some statistic information and provides a list of recent found TAGs.
Howto access this information can be found in the host mode demo code STUHFL_demo.
In general the usage of the STUHFL API is independent of the mode, but a simple print TAGs info to screen is not possible in device mode, only the callback stub is implemented.
BR
Nick