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
Unable to connect to AWS following example #224
Comments
Hi there, and sorry you're having trouble with this.
The latter could happen if you are entering the AT commands manually and have not entered the Here is an example of a working sequence run against a SARA-R510M8S module (taken from a
|
Thanks for the quick response. In m-center it is showing the Profile as an external PSD profile. I am not sure how the AT_UPSD=0,100,1 knows how to map an external vs internal profile.
|
I think you want |
Same 'error' with UPSDA.
|
Could you post the entire AT sequence, from power-on? If |
From M-Center
|
As far as I can tell you have context 0 activated, which is the default context that kind of "comes with" an LTE registration. The
...and then wait for the You say at the start of your original issue "I am trying to follow the example from this document..."; which document are you referring to? This site is about the |
I am trying to follow the example from this document and using the M-Center to send AT commands to the SARA-R510M8S dev board connected to a Windows PC.
I am using an ATT SIM card and am able to send SMS messages, and the ATT control center shows it is connected.
I've gone over the certs and keys and they seem to be correct. I am not sure what 'operation not allowed' means. Is that coming from AWS or from the modem?
Everything is accepted until I get to the command to log in:
At some point the Monitor on the AWS IoT Core dashboard showed that there was a connection made, but I have never had the AT+MQTTC=1 command succeed.
Any thoughts on what else to try?
The text was updated successfully, but these errors were encountered: