Skip to content

Conversation

@JohanEThomsen
Copy link
Contributor

No description provided.

@JohanEThomsen
Copy link
Contributor Author

Inspired by this article:
https://onomondo.com/blog/at-command-attach-detach-modems-tips/

// with reset attempts.
if (attempts_ > CELLULAR_FAILS_UNTIL_SCAN) and (attempts_ % 3 == 0):
logger.info "scanning for operators" --tags={"attempt": attempts_}
operators := driver.scan_for_operators
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we ignore the returned operators, but we believe that doing the scan will somehow have a side-effect on the next automatic attempt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that's the idea. It's not clearly described in the documentation, but our tests suggests that the scan updates the internal caches of modem's list of available operators, which then affects how it decides on a given operator in the subsequent automatic connect.

We have seen a device, which consistently kept re-choosing a network, where registration succeeded but the following PDP context activation failed, such that it never achieved a proper connection. After a couple of scans, it chose another operator and thus automatically achieved proper connection again.

However, it would be better to keep a flashed-back list of the used operators in the driver so we can prevent the situation completely (like the TODO comment suggests).

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

Successfully merging this pull request may close these issues.

2 participants