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

Missing handler for socket error/dead caused by weak signal strength #82

Closed
CptHolzschnauz opened this issue Aug 1, 2021 · 1 comment

Comments

@CptHolzschnauz
Copy link
Contributor

CptHolzschnauz commented Aug 1, 2021

What:
A created socket can 'die' out of a sudden when the server does simply not answer anymore without closing the socket.
Then a +USOWR command can stop in the middle of the write process and the modem answer with +CME Error 3 (Operation not allowed). A error readout with +USOER says "65 EEOF - End of file."

The client wants to write data into a dead socket, the bytestream is blocked because the server does simple not read anymore.

Result: The board freezes because the NbClient can't handle that error.

Remedy: these processes take place on the baseband and cannot be influenced or predicted. however, the nbclient must be able to handle the error message of the modem cleanly.

@CptHolzschnauz
Copy link
Contributor Author

closed with #84

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