You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has been a couple of weeks since we found our issue, but essentially it was a one liner fix...
Background: The Arduino MKR NB 1500 was running with no issue for quite some time during testing. After about a week or two, we were unable to connect to the Firebase server anymore. We found that the sockets were not being created, opened, or closed. Then, every new MKR we tested had the same issue. After not finding solutions online, we read through the SARA-R4 datasheet and enabled Modem debug AT commands.
Fix: Long story short, in the NBClient.cpp, (line 128ish) we change MODEM.send("AT+USECPRF=0,0,1"); to MODEM.send("AT+USECPRF=0,0,0"); and the sockets are now functioning correctly. We have GET/POST thousands of requests with <1% failure to connect rate.
During our troubleshooting and Googling, we realize many others have had this issue or at least, the same symptoms so we felt the need to post here for others. Hope this helps!
The text was updated successfully, but these errors were encountered:
cth000182
changed the title
AT+USOCO and AT+USOCL returning ERROR constantly when trying to connect to a server
AT+USOCO and AT+USOCL returning ERROR constantly when trying to connect to Firebase server
Oct 8, 2021
It has been a couple of weeks since we found our issue, but essentially it was a one liner fix...
Background: The Arduino MKR NB 1500 was running with no issue for quite some time during testing. After about a week or two, we were unable to connect to the Firebase server anymore. We found that the sockets were not being created, opened, or closed. Then, every new MKR we tested had the same issue. After not finding solutions online, we read through the SARA-R4 datasheet and enabled Modem debug AT commands.
Fix: Long story short, in the NBClient.cpp, (line 128ish) we change
MODEM.send("AT+USECPRF=0,0,1");
toMODEM.send("AT+USECPRF=0,0,0");
and the sockets are now functioning correctly. We have GET/POST thousands of requests with <1% failure to connect rate.During our troubleshooting and Googling, we realize many others have had this issue or at least, the same symptoms so we felt the need to post here for others. Hope this helps!
The text was updated successfully, but these errors were encountered: