Hi, I'm running a gPy device on LTE against pybytes.pycom.io. The device has never been connected via wifi and is working fine. Things I have done: attached an external antenna replaced the LTE-controller firmware with one suitable for my region / provider

Someone found a workaround - check out this github here: https://github.com/pycom/pycom-micropython-sigfox/issues/424

@hayesey I am looking for a SIM card NB-IoT enabled in the UK. Could you let me know how you get your SIM card, or where I can find one please?

@naveen No clue. When it did not work for me, I could not get a hand on debugging. I only purchased another LTE NBIoT module to verify, that the service was available and the SIM worked. It did. Module type SIM7020.

@nadvorvo said in T-Mobile NB-IoT in the Netherlands? [SOLVED]: Could you comment, please [AT] 939910, [AT-OK] +9509 I do not know meaning. [AT] 939910 means an AT command was submitted at timestamp 939910 [AT-OK] +9509 means an OK response was received after elapsed time 9509 both values are in milliseconds

@eric-waai These settings should be fine then.

@robert-hh said in no can connect to vodafone spain NB-IOT with FIPY: The second number is the bit error rate (ber), whic is not know beforehand. So it means now the device detects is a proper signal. then. then, now I understand that it had a good signal, but the fipy was trying to attach herself all night, and she did not succeed. it's just waiting, or we should give it the command to attach repeatedly ... On the other hand, I'll check the commands you indicate

@robert-hh Can you give an example how to send data using 1nce sim card?

@danielm Did you ever get an answer to WHY 'AT+CESQ' fails to return: RECEIVED SIGNAL STRENGTH LEVEL CHANNEL BIT ERROR RATE RECEIVED SINGAL CODE POWER RATIO OF RECEIVED ENERGY i.e. the first 4 parameters in the command?

@combaindeft Hej! I have just started to play with he Telia IoT using fipy. But I guess I am having similar problem with the socket creation as you experienced. I got such an error OSError: [Errno 113] EHOSTUNREACH while connecting to sockets. So how is it working for you now? Thanks.

@elizar said in Weird issue when pinging an external server: @shedaim Ping'ing takes time. Maybe the successful reply to the second ping is in fact the answer to the first ping? Using the newly added "delay" option should have fixed that, so I don't believe that's what's happening. This is what I managed to find out untill now: Trying a single ping message: Ping request UE --> Server Success Ping reply Server --> EPG Success Ping reply EPG --> MME Success Ping reply MME --> eNodeB Success Ping reply eNodeB --> UE Unknown (Doesn't show in Atom, but MME states that message has been sent) Trying two pings in rapid succession: Ping request UE --> Server Success Ping reply Server --> EPG Success Ping reply EPG --> MME Success Ping reply MME --> eNodeB Success ping reply eNodeB --> UE Unknown (Doesn't show in Atom, but MME states that message has been sent) Ping request UE --> Server Success ping reply Server --> UE Success (Arrives after 150 - 500 ms) Pinging from server to UE is successful continuously. eDRX is in state "NOT_CONFIGURED" - same as network. Tried to disable sleep of the modem using AT!="EE::disable" Additional information for the Pros: First Ping message is sent over S1AP/NAS-EPS in the initial message to the MME, which contains a Control Plane Service Request. Second ping message is sent over the same interface as an UplinkNasTransport message. Wireshark of MME messages - Download

@wtrocel As @robert-hh has suggested using the pycom firmware update tool and selecting include development versions + development instead of stable is likely the easiest way to get the new Release candidate.

@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

@dommei That's means: "not registered, MT is not currently searching an operator to register to". At my device, it toggles between 2,0 and 2,2. The response you need is 2,1 or 2,5. The AT command set document is here: https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIL0iGdl11z7Jos_jpX%2F-LKN7scqKKkb6TqB3uYO%2F-LKN866sBhZY7wCqpQPA%2Fmonarch_4g-ez_lr5110_atcommands_referencemanual_rev3_noconfidential.pdf?generation=1534782117167775&alt=media

@elizar Thank you for confirming this!