-
Notifications
You must be signed in to change notification settings - Fork 41
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
[+]Response timeout #24
Comments
What command gives this error? What's your baud rate? Post a minimal example of the code that yields this behaviour (with Pastebin.com) |
When Client connected to ESP8266 and it makes some requests like call a URL like 192.168.4.1/count then timeout error appears in Serial monitor... This is the minimal code: https://pastebin.com/zMZpqzkU Sometimes it also give error like this with different values: While simple timeout error is very frequent: Note: Timeout Error occurs no matters WiFi is ON or OFF. But timeout error + Packet too long error occurs more frequently when Client is communicating with ESP8266 using its WiFi Access Point. |
First, fix the return type of |
Okay I changed the data type.
Yes I'm using most recent version. I just downloaded the library from here at github. And Debug level is default (Errors Only) in FPM.h
No, timeout error occurred no matters I count the fingerprints, Enroll a new Fingerprint or Search. Timeout occurs each time randomly (mostly when WiFi is ON). Important: See this is the latest results: |
You're powering the circuit through your Wemos USB port, right? Do you have anything else connected to the Wemos besides the R301T? Since the timeouts only happen when you turn on the Wi-Fi (soft AP?), it's possible that you're simply not providing enough power for the ESP8266 and R301T. So try powering the R301 with some other source (maybe another USB port). Also try increasing |
1. Yes I was powering Wemos with its MicroUSB port. There is a Buzzer Module and an LED in my circuit along with Wemos D1 Mini and Fingerprint Sensor. 2. I changes I noted that when Timeout error occurs fingerprint module stop searching (stuck) for FPM_DEFAULT_TIMEOUT seconds. I mean after error appear fingerprint sensor stops working and then start working again after the timeout value seconds set for I think there are some sort of compatibility issues of this FPM Library with ESP8266 Modules. |
Can't add compatibility if the problem's cause is unknown, and that's assuming the issue is even with the library. This is the first time I've seen an R301 in use, so there's no precedence here. I'd recommend you try the Adafruit library and see if it works for you without timeouts. Then we could conclude that this library is likely the problem. |
Okay but I see that this timeout error is discussed by someone else too. |
That was for a different MCU and sensor. And in that case, it turned out the high speed search command wasn't supported by the module and so it was replaced with the regular search command, as well as increasing the timeout to a more reasonable 2 seconds. Yours is more general and seems more like a case of poor power supply or the module simply doesn't support these commands as documented. If you have a different sensor model, you can try it to see if the problem goes away. Or try a different library, like I already suggested. |
Okay... |
I am using Wemos D1 Mini, ESP8266-12E based development board. ESP8266 is controlling R301T Fingerprint sensor using Serial Monitor commands. I am also using ESP8266's WiFi as Access Point to do some configurations and communications with local clients. Everything is working as expected BUT only one problem is there...!!!
The Serial Monitor showing this error randomly even when WiFi is disabled (No AP mode).
[+]Response timeout
Some times, when AP mode is enabled, the error looks like this:
or this:
This timeout error becomes more frequent when ESP8266 is working in Access Point Mode and communicating with Clients.
Does this timeout occurs due to some Timer issues???
I can not understand the reason of this error and how to solve it. Please help me to solve this issue. Thanks!
The text was updated successfully, but these errors were encountered: