Agathe LeeHi Lonny,
Here’s the result:
at+cmee=2
OK
at+cgdcont=3,”IP”
+CME ERROR: operation not supported
Agathe LeeThe command AT#SGACT=3,”IP” returns ERROR. I tried modifying the PDP context with AT+CGDCONT=3,”IP”,”VZWINTERNET”,””,0,0. This also returns ERROR.
Agathe LeeAlas, I was asking because these documents, which I have, do not shed much light on the differences between sleep modes (So, one means that ST Micro is stopped, while the other means it’s in standby, for a user, what does that mean? In terms of what do I need to save, what do I need to restore, how long does it take to wake up from each type of sleep, and what is the idle current draw of each, the manual, page 21, offers two conflicting answers)
Thanks,
Agathe
Agathe LeeThanks, Jason. Does this mean that at+sleep now enables a “deeper” sleep than what was possible on 0.1.4 firmware? I am trying to understand the differences between the two, and what there is to gain with the new firmware.
What are the differences in sleep modes? which one is the default? Any differences in power consumption between them?
Agathe LeeIt helps sometimes. I found that it helped best when sent shortly after a hardware reset.
Agathe LeeOkay, that’s a workaround, although I would still like to know the actual timing.
I am now noticing a lot of “failed to join network” and unacknowledged transmissions when operating with sleep mode.
Basically, I have the mDot in sleep mode by default, wake it up by interrupt when i have something to transmit, wait for OK and attempt to join network, then when successfully joined send a 43-byte packet at SF9. The Conduit is in an adjoining room and RSSI hovers at -65.
Agathe LeeHi Brandon,
Thanks for your answer. I had seen the warning about the two receive windows online but decided to try the command anyway just to see what happened. This seems to imply that serial data mode would have the same conflict between what the command is supposed to do and what LoRa Class A allows. Is that correct?
-Agathe
