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.

Sign up for GitHub

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

Jump to bottom

firmware upload timer is changed, probably by ublox or carrier #66

Open
ravelab opened this issue Oct 7, 2019 · 2 comments
Open

firmware upload timer is changed, probably by ublox or carrier #66

ravelab opened this issue Oct 7, 2019 · 2 comments

Comments

@ravelab
Copy link
Contributor

ravelab commented Oct 7, 2019

{2019-10-07T18:45:35Z INFO src/Cellular.cpp:35 connect , carrier : Verizon Wireless Sierra Wireless , initTime :13899, signal :15}
{2019-10-07T18:45:35Z INFO src/Mqtt.cpp:100 connect , broker : a2ink9r2yi1ntl-ats.iot.us-east-2.amazonaws.com }
AT+USOCR=6
+USOCR: 0

OK
AT+USOCO=0,"a2ink9r2yi1ntl-ats.iot.us-east-2.amazonaws.com",8883

stuck for 1 minute then watchdog reset
@ravelab
Copy link
Contributor Author

ravelab commented Oct 7, 2019

and after that, cellular model.debug does not output any AT commands, unless the power is cycled.

@ravelab
Copy link
Contributor Author

ravelab commented Oct 7, 2019

it turned out firmware update time is changed by maybe the carrier:
AT
OK
AT+UFOTACONF=2
+UFOTACONF: 2, 86400

I'm adding a function disableModemFirmwareUpdate() in Cellular.cpp

@ravelab ravelab changed the title cannot connect to aws mqtt with verizon, but at&t OK firmware upload timer is changed, probably by ublox or carrier Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ravelab