When user measures MBR SNR, should they use Raw count change value(with touch – without touch) as signal value?
Or should they use Diff count itself as signal value?
I think that user should use Diff count itself when user calculates SNR.
Because max Diff count(button) is 255 even if Raw count change value is 1000.
But I think that EZ-Click uses raw count change value when EZ-Click calculates SNR.
If EZ-Click uses raw count even if it is correct to use diff count for SNR, calculated all SNR by EZ_Click may become incorrect.
Although max diff count is 255, calculated SNR by EZ_Click may exceed 255 depending on the timing.
For example. Please confirm attached pptx file.
- Noise: 3
- Raw count change value: 560(3560 – 3000)
- SNR: 190
Is it OK that diff count saturates(diff is 255)?
It is difficult to tune so that diff count does not become saturated.
Because MBR is smart sense and there is only few sensitivity setting.
How does MBR3 calculate diff count?
For example, if Raw count change value is 1000(5000 – 6000), does MBR3 compress 1000 and convert it to 1byte of diff count?
Does MBR3 compress 2byte data and calculate diff count as 1byte?
Or does MBR3 convert 1000 to 1byte of diff count by multiplying by some coefficient(multiply diff by 0.8 etc)?
Or is MBR3 simply subtracting Raw count when MBR3 calculates diff count?
Then is MBR3 always making diff count 255 when raw count change value exceeds 255?
About a graph of “Signal to noise ratio” in EZ_Click.
SNR from 2nd time becomes lower than 1st SNR.
Please confirm png file.
Could you please let us know this reason?
Does noise in “Signal to noise ratio” also include Raw count change value by finger-touch?