FiPy not attaching to Vodafone NB-IOT
-
Hi,
I'm having problems connecting my FiPy to the vodafone network.
I have upgraded the firmware to NB1-38729, that succeeded but still it's not connecting.
The sim card is activated so that should work also.
Please leave me suggestions so I can fix this problem.My code is:
When I run this it continuously prints the "not attached".
-
@nickb This is a standard AT command. the response tells:
"scanning with unsolicited response enabled" (first 2), and
"not registered, but MT is currently trying to attach or searching an operator to register to" (second 2)
https://www.etsi.org/deliver/etsi_ts/127000_127099/127007/12.07.00_60/ts_127007v120700p.pdf
or
https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIL0iGdl11z7Jos_jpX%2F-LKN7scqKKkb6TqB3uYO%2F-LKN82sqi_sHewyinxC5%2Fmonarch_4g-ez_lr5110_atcommands_referencemanual_rev3_noconfidential (2).pdf?generation=1534782114581269&alt=media
-
@robert-hh
The return from that command is 2,2.
I cant figure out what that means.I have the command executing a lot in a while loop ( while not lte.isattached()).
After 20 minutes it's still at +CEREG 2,2
And seen as it doesn't break out the loop I guess it's still not attached, or is that the wrong parsing you mentioned?Thanks a lot!
-
@nickb When you send after lte.attach() the command:
lte.send_at_cmd("AT+CEREG?")
what do you get? Please note, that attaching can take a while, up to 15 minutes, and you have to repeat the command a few times.
if you get somthing like.
+CEREG: 2,1,"xxxx","yyyyyyyy",7 or +CEREG: 2,1,"xxxx","yyyyyyyy",9
then the device is in fact attached, and it's just the parsing within lte.attach() which is wrong. @Xykon has provided a patched version which addreses this fault.
