You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
Hello,
I observed that when the reset command is called upon a PN5180ISO15693 instance, if the module is not connected, the code falls into an infinite loop, concretely in the transceiveCommand function waiting for a HIGH value in the busy pin.
I was wondering if there's any way to detect if the device is not connected without falling into an infinite loop and, in the case of not being implemented, if that's a pull request that could interest this repository.
Thanks a lot for maintaining this library and make it open source.
Jordi
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I observed that when the reset command is called upon a PN5180ISO15693 instance, if the module is not connected, the code falls into an infinite loop, concretely in the transceiveCommand function waiting for a HIGH value in the busy pin.
I was wondering if there's any way to detect if the device is not connected without falling into an infinite loop and, in the case of not being implemented, if that's a pull request that could interest this repository.
Thanks a lot for maintaining this library and make it open source.
Jordi
The text was updated successfully, but these errors were encountered: