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

Sprint updates are soft-bricking nodes #54

Open
mdbartos opened this issue Aug 26, 2017 · 0 comments
Open

Sprint updates are soft-bricking nodes #54

mdbartos opened this issue Aug 26, 2017 · 0 comments
Labels

Comments

@mdbartos
Copy link
Member

Sprint updates are causing nodes to stop reporting in the field. When Sprint initiates an update, the updater starts writing strings of the form '#9XX' to the cell module's RX buffer. This is causing the parser to fail, and thus the node can't communicate with the server (modem_send_recv returns 0).

In general, AT commands shouldn't be issued during the update process, as it can cause activation/updates to fail. The proper way to deal with this problem should be to put the module in standby when '#900' is detected and then not send any AT commands until another '#900' is detected. We can also tell Sprint to not send updates to these cell modules.

@mdbartos mdbartos added the bug label Aug 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant