GPY loss of attachment ability
kjm last edited by kjm
I've managed to get 2 GPY lte modems into a state where they can no longer attach, presumably because of an AT cmd sequence
I was evaluating. Since I'm now down to only one working GPY I've been trying to get them working again. So far I've tried;
AT+SQNSFACTORYRESET followed by AT^RESET
and reflashing the modems firmware
to no avail. Can anybody suggest something I haven't thought of? I guess I'm after something to erase the modem flash where it keeps the persistent results of changes wrought by AT cmds
Is there anybody with a surplus of GPYs willing to risk
so I can see what the default modem should be?
kjm last edited by
I maybe got a clue to what's going on https://forum.pycom.io/topic/4915/gpy-pytrack-modem-won-t-attach-after-firmware-upgrade/7 with responses to print(lte.send_at_cmd("ATI"))
My one working GPY responds SEQUANS Communications VZM20Q UE220.127.116.11d whereas the dead ones reply PYCOM FiPy UE18.104.22.168d God knows how a cereg cmd makes the lte modem think its FiPy?!