Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for R503 FPS and watchdog #18

Closed
unseemlycoder opened this issue Oct 25, 2022 · 4 comments
Closed

Support for R503 FPS and watchdog #18

unseemlycoder opened this issue Oct 25, 2022 · 4 comments

Comments

@unseemlycoder
Copy link
Contributor

The adafruit fingerprint library supports FPM10A (optical) and R30x/R50x (Capacitive) Fingerprint sensors. However, the Capacitive fingerprint sensors (FPS) do not support the following function:

finger.fingerFastSearch();

The above line throws "Unknown Error" on Serial Monitor via switch-case logic.
but instead use

finger.fingerSearch();

The R-series FPS have an LED ring around the sensor that can be used to indicate various states via

finger.LEDcontrol(uint8_t control, uint8_t speed, uint8_t coloridx, uint8_t count=0)

I have also noticed that certain microcontrollers (ESP32xx family) get stuck and do not publish mqtt messages, even though broker and wifi are available. I am yet to ascertain the issue via logs as this bug appears only when microcontroller is on power (for an extended period of time - days) and not connected to a system for serial monitor. Currently using a watchdog to raise a hardware interrupt and reboot the device on such a scenario.

Hardware WatchDog Timer - ESP32xx Stuck WiFi

unseemlycoder added a commit to unseemlycoder/fingerprint-mqtt that referenced this issue Oct 25, 2022
@unseemlycoder
Copy link
Contributor Author

#19 Pull request created.

@unseemlycoder
Copy link
Contributor Author

#20 Pull request created (Updated an if condition).

@unseemlycoder
Copy link
Contributor Author

Turns out when the WiFi access point switches channels or the microcontroller loses connection to the AP, there isn't a reconnection strategy in the code for WiFi. Only MQTT reconnect is implemented. The current watchdog solution works as a reconnection strategy but can be done using the native WiFi library. Will take a look into this.

Reference:
knolleary/pubsubclient#629

@unseemlycoder
Copy link
Contributor Author

IMG_3631.-.Trim.mp4

Been stable for the last month. Closing this issue.

EverythingSmartHome added a commit that referenced this issue Jan 6, 2023
Issue #18: R503 FPS LED WDT ESP32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant