ccorrads:
@zbelding Do you have exactly the implementation of pulsing the pwr_on pin in Arduino?From code examples....I'm guessing...
pinMode(SARA_PWR_ON, OUTPUT);
digitalWrite(SARA_PWR_ON, HIGH);
delay(150); // Datasheet says power-on pulse should be >=150ms, <=3200ms
digitalWrite(SARA_PWR_ON, LOW);I'm noticing (as you and others have pointed out) that after random times, the SARA chip goes into an unresponsive state and my sketch basically infinitely loops in trying to reconnect via "nbAccess.begin()". I thought that the begin method in the NB class of the MKRNB library would pulse the pwr_on pin correctly...but maybe I am mistaken?
I'm using the latest master branch of the MKRNB library since the fixes aren't in a release yet:
MKRNB/src/NB.cpp at master · arduino-libraries/MKRNB · GitHub
then...
MKRNB/src/Modem.cpp at master · arduino-libraries/MKRNB · GitHubI'm thinking maybe the V_INT pin check after some time in Arduino is out of sync with the Modem's actual state and it infinitely hangs because it never actually sends the power on pulse when it gets into this unresponsive state.
Your pwr_on code looks right to me. I usually use 500ms, but anything between the range you found in the manual should work. I would keep it less than 1.5s, that way you don't accidentally turn the modem off if it's already on. V_INT is not connected on this board. It doesn't really need to be. You can pulse the pwr_on pin at any time to confirm the modem is on.
Sorry, I can't help you too much with arduino library specific questions. I only used these libraries in the very beginning.
With regard to the modem seeming to be unresponsive, in my experience this was completely fixed with the new version of the modem firmware. I believe this was a specific AT&T issue. You can find more details in my other threads.