at cmds Vs the alternative
Does anybody know why at cmds are 50% quicker than the alternative?
_getlte() start=time.time(); lte.disconnect(); print('modem at cmd reset', end=' '); lte.send_at_cmd('AT^RESET'); end=time.time(); print(end-start) _getlte() start=time.time(); print('modem reset', end=' '); lte.reset(); end=time.time(); print(end-start) _endlte() lte attaching 0 1 2 3 4 5 6 7 8 OK read ss -86 lte connecting OK modem at cmd reset 7 lte attaching 0 1 2 3 4 OK read ss -86 lte connecting 0 OK modem reset 11
robert-hh last edited by robert-hh
@kjm That value is #defined in esp32/lte/lteppp.h, and the constant is used e.g. in esp32/mods/modlte.c.
@robert-hh I've not come across LTE_RX_TIMEOUT_MAX_MS = 9500 ms in my readings Rob, can you link me to any docs that explain this further please?
robert-hh last edited by
@kjm The implementation of lte.reset() send the command AT^RESET too, but then waits for the string +SYSSTART as a confirmation for the reset. The maximum wait time is 19 seconds (two times LTE_RX_TIMEOUT_MAX_MS = 9500 ms)