ESP Crash when downloading template

[brianrho]

ESP Crash when downloading template

[brianrho]

Any reason why you think the protocol is different? As far as I can tell, the module is basically the same as the one I used. Try the new modules with an Uno; if everything works as expected, then this is an ESP related issue, most likely caused by the absence of yield() calls in the loop where readRaw() grabs the template.

[danbicks]

Brian, Great Idea, I will try this with an Uno and also try adding yield() statements. With ESP the standard finger print reader works perfect so their must be something slightly different between the 2 types I would have thought. The reason I thought it could be protocol related is the byte's that are received using an old routine of mine differ between the 2 reader types I will look in to this further and give you the output and old function if this helps. I was looking to implement instead of spiffs Google firebase storage of finger templates have you looked at firebase? Big thanks Dans

…

On Tue, Jun 13, 2017 at 10:05 PM, Brian Ejike ***@***.***> wrote: Any reason why you think the protocol is different? As far as I can tell, the module is basically the same as the one I used. Try the new modules with an Uno; if everything works as expected, then this is an ESP related issue, most likely caused by the absence of yield() calls in the loop where readRaw() grabs the template. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALsWl3qnQ0hW2uoBM1dY08dcUjNARnxnks5sDvl9gaJpZM4N2a1R> .

[brianrho]

No I haven't used Firebase nor do I have much experience with ESPs really. The debug option in the library isn't well implemented yet else that would've been the way to go so I can see the bytes coming from the new reader. But you say everything works for both reader types except for the process of reading in the templates (I assume you don't mean the getTemplate() call itself) which causes problems both with the new and old readers when used with an ESP; that's why I think the issue is ESP-related. I guess we'll know for sure after you've tested with an Uno and inserted the yield()s.

[danbicks]

Hi Brian,

Big thanks for getting back so soon, yes the getTemplate() routine works fine with the older reader type as long as wifi has no connectivity on the ESP, with the new reader type the routine causes a stack dump crash. Could be lacking of yield statements however the data output using one of my routines looks different. I will do some further tests over this weekend and beginning of next week and report back the results of my tests.

Keep you posted, thanks again for all your efforts.

Dans