There is a bug in SmartSense2X UM code. But there is a workaround for this. In wizard use manual threshold.And in your main code after smartsense initialization use the global variables that stores the threshold for each sensor as shown below.
Can you expand on what exact issue you are facing?
If you want to set the threshold manually, you need to select either "Autotune based on sensitivity" or "Manual" under Threshold setting and modify the <Instance_Name>_baBtnFThreshold[Sensor_No] array to set the finger threshold after you call <Instance_Name>_Start() API and before calling the <Instance_Name>_UpdateSensorBaseline() API or <Instance_Name>_bIsSensorActive() API.
In case, you want to set the threshold setting you have entered in the wizard (when selecting "Manual" threshold), you have to call <Instance_Name>_SetDefaultFingerThresholds() API. Here <Instance_Name> = The name you have selected for the UM.
If you are facing any other issues, do let us know. We will help out.
there is option of setting the manual threshold in Wizard. I am setting it there.
Do i still need to do modifications that you are telling.
If yes can you elaborate with an example
In case you are setting the Threhold in wizard, you need to call <Instance_Name>_SetDefaultFingerThresholds() after you have called <Instance_Name>_Start() API for the threshold setting to take effect.
On another note, there is a known glitch with 'Manual' Setting in SmartSense2X UM.
In this setting, sensors are tuned to a fixed sensitivity rather than the user selected sensitivity. We have already implemented a fix which is scheduled for the next Designer release.
Meanwhile an workaround for the issue is as below -
1. Use 'Autotune based on sensitivity' setting in the wizard.
2. As TEJU mentioned, initialize the <Instance_Name>_baBtnFThreshold[Sensor_No] array as per your Finger threshold requirement.