search

ThiagoFerrao / solum

APIs for OEMs to Create Standalone Applications
https://www.clarius.com
BSD 3-Clause "New" or "Revised" License
1 stars 0 forks source link

`CusStatusInfo` occasionally reports the wrong `CusFanStatus` #4

Open ujrm opened 3 months ago

ujrm commented 3 months ago

Describe the bug CusStatusInfo occasionally reports the wrong CusFanStatus. It reports NoFan when a fan is connected. It's very occasional, sometimes you have to wait a long time for it to happen. Quite often it only happens for a couple of seconds and then it corrects itself.

To Reproduce Steps to reproduce the behavior:

  1. Tap Download scanner info
  2. Enable Bluetooth searching
  3. Select probe
  4. Tap Load Selected Scanner Details
  5. Connect to probe's WiFi
  6. Tap Connect
  7. Change Application to "msk"
  8. Tap Load Application
  9. Wait - The console will print out the fan status every second

It might take a while (several minutes), but the fan status will incorrectly report as NoFan (_CusFanStatus(rawValue: 0)). See attached image of this log.

Environment:

Screenshot 2024-06-26 at 10 25 26
clariusk commented 3 months ago

We've seen this from previous software versions and made some fixes in 11.3. Looks like it may not be completely resolved, though our test team spent quite a bit of time doing regression tests with good success, so we may suggest checking with another device or fan attachment to see if you catch the issue still - note these are magnets that trigger the detection, so small variability is root cause of this, with 11.3 implementing some filtering on the detection signal.

ujrm commented 3 months ago

We've seen this issue with 6 probes and fans. It appears to be an issue regardless of which probe and fan are used.