Hello Definity, Its not a normal 3g/4g setup. You cant just put a normal simcard in and have it work. Youll need an NB-IOT/CAT-M1 enabled sim. and your local network needs to support it. which isn't actually the case for most of the UK. Vodafone is our best bet. But even they don't have a full rollout yet.

Same problem with the latest 1.18.2.r2. An SPI device that normally worked with 1.18.1.r7 does not work after 1.18.2.

@paul-thornton @ChangedDaily this is now reset. go ahead and re flash the firmware.

@joselfesteves I tried using SMS about a month ago - just an experiment to see if it worked. It did, in both directions for standard and multi-line messages. But that is here in Oz, on the Telstra network. Maybe it is a service related issue? Does the service you are using support SMS? I did have to experiment a bit with the AT command set though before I had any success.

@aventri My guess is that you haven't installed the drivers to allow you PC to see the Expansion Board com port? When I was starting with GPY, I found this tutorial from Core Electronics in Australia, to be very helpful.. https://core-electronics.com.au/tutorials/pycom-gpy-getting-started.html It is Windows centric, but there are others to be found as well

@fedonman Depends on the sensors really. What bus (i2C, SPI, etc) or other port you need. Other factors are the power supply required and any other such factors. My practice is to extend the bus/es from the sockets Expansion/Pytrack board to a protoboard, so I am able to connect more than one device, power supply, level shifters, pull up/down resistors, capacitors etc if required. Makes it easier to work on and follows on with making a custom PCB later on..

Ideally the external headers if the pins match your usecase.

@smoochypea You can achieve 5 minuite send intervals easily enough by sleeping for 5minuites - however long execution took. (read the time at the start and end of executing. run time is end - start sleep for 5 minuites - runtime as long as recording and sending data takes < 5 minuites you'll end up with a nicely timed 5 minuite loop) That said. without knowing more about what the rest of the datacollection code does it's rather hard to make recommendations.

@robin Have you tried forcing the use of the internal antenna, either via the appropriate WiFi setting, or directly by controlling P12?

OK. So my GPy's hardware was to blame. (Link) Since I also have a more recent FiPy I upgraded that one to NB1 40343. Success! I can read the 'Hello World!' message on the T-Mobile Netherlands dashboard. If this code does not attach for you, check that the CAPS show that your band is supported. My GPy was missing band 8 and I have requested an RMA... Testing code: import os from network import LTE import usocket import time def send_at_cmd_pretty(cmd, delay=1000): response = lte.send_at_cmd(cmd, delay=delay).split('\r\n') print('Sent to modem: \'{}\', delay {} ms'.format(cmd, delay)) for line in response: if line.strip() != '': print(line) # Print module details un = os.uname() print('Sysname:', un.sysname) print('Release:', un.release) print('Version:', un.version) print('Machine:', un.machine) # Initialize LTE object lte = LTE() time.sleep(5) # Pre attaching debugging print('Query LTE modem imei...', lte.imei()[:5] + '*' * 10) print('Query SIM iccid...', lte.iccid()[:5] + '*' * 15) send_at_cmd_pretty('ATI1') send_at_cmd_pretty('AT!="showver"') send_at_cmd_pretty('AT!="RRC:setDbgPerm full"') send_at_cmd_pretty('AT!="RRC:showcaps"') time.sleep(5) send_at_cmd_pretty('AT+SQNCTM?') # Attach LTE print('LTE attaching...') lte.attach(band=8, apn="cdp.iot.t-mobile.nl") attempts = 0 while not lte.isattached(): time.sleep(5) attempts = attempts + 1 print('Attaching...', attempts) if attempts % 15 == 0: send_at_cmd_pretty('AT+SQNMONI=9') send_at_cmd_pretty('AT+CEREG?') send_at_cmd_pretty('AT+CFUN?') send_at_cmd_pretty('AT+CSQ') send_at_cmd_pretty('AT!="showphy"') send_at_cmd_pretty('AT!="fsm"') print('LTE attach succeeded!') # Debug attached state send_at_cmd_pretty('AT+CEREG?') send_at_cmd_pretty('AT+SQNMONI=9') send_at_cmd_pretty('AT+CSQ') send_at_cmd_pretty('AT!="showphy"') send_at_cmd_pretty('AT!="fsm"') send_at_cmd_pretty('AT+CGPADDR') send_at_cmd_pretty('AT+PING="172.27.131.100"', delay=5000) # Connect LTE lte.connect() attempts = 0 while not lte.isconnected(): time.sleep(5) attempts = attempts + 1 print('Connecting...', attempts) print('LTE connection succeeded!') # Test DNS try: usocket.dnsserver(0, '8.8.8.8') usocket.dnsserver(1, '1.1.1.1') usocket.dnsserver() print(usocket.getaddrinfo('www.google.com', 80)[0][-1]) except Exception: print('DNS over NB-IoT failed...') # Send message to dashboard s = usocket.socket(usocket.AF_INET, usocket.SOCK_DGRAM) s.setsockopt(usocket.SOL_SOCKET, usocket.SO_REUSEADDR, 1) # s.settimeout(5) # s.setblocking(False) s.sendto(bytearray('Hello World!'), ('172.27.131.100', 15683)) s.close() # Shutdown LTE print("Disonnecting LTE ... ") lte.disconnect() print("Detaching LTE ... ") lte.dettach() print("Shuttting down LTE...") lte.deinit() Output: Sysname: FiPy Release: 1.20.0.rc7 Version: v1.9.4-2833cf5 on 2019-02-08 Machine: FiPy with ESP32 Query LTE modem imei... 35434********** Query SIM iccid... 89882*************** Sent to modem: 'ATI1', delay 1000 ms UE6.0.0.0 LR6.0.0.0-40343 OK Sent to modem: 'AT!="showver"', delay 1000 ms SYSTEM VERSION ============== FIRMWARE VERSION Bootloader0 : 5.1.1.0 [39529] Bootloader1* : 6.0.0.0 [40343] Bootloader2 : NA NV Info : 1.1,0,0 Software : 6.0.0.0 [40343] by robot-soft at 2018-11-07 13:57:00 UE : 6.0.0.0 COMPONENTS ZSP0 : 1.0.99-3171 ZSP1 : 1.0.98-3170 OK Sent to modem: 'AT!="RRC:setDbgPerm full"', delay 1000 ms OK Sent to modem: 'AT!="RRC:showcaps"', delay 1000 ms == CAPS config ============================= .Lock UE on SRV band : false .MFBI support : true .TM8 TDD support : false ============================================ == CAPS ==================================== . access stratum: R13 . catM : 1 . nb-IoT : 1 -- EUTRA bands -- . supported : 28/20/13/12/8/5/4/3 . board : 3/4/5/8/12/13/20/28 . admin : . pending admin : -- EUTRA carriers -- . admin : . pending admin : ============================================ OK Sent to modem: 'AT+SQNCTM?', delay 1000 ms +SQNCTM: standard OK LTE attaching... Attaching... 1 Attaching... 2 LTE attach succeeded! Sent to modem: 'AT+CEREG?', delay 1000 ms +CEREG: 2,5,"04F5","00710C67",9 OK Sent to modem: 'AT+SQNMONI=9', delay 1000 ms +SQNMONI: 20416 Cc:204 Nc:16 RSRP:-78.30 CINR:5.60 RSRQ:-12.00 TAC:1269 Id:287 EARFCN:3747 PWR:-58.52 PAGING:1024 OK Sent to modem: 'AT+CSQ', delay 1000 ms +CSQ: 27,99 OK Sent to modem: 'AT!="showphy"', delay 1000 ms DL SYNCHRO STATISTICS ===================== Synchro state : CELL_ACQUIRED PPU SIB1 ACQ watchdog : 0 Frequency Hypothesis RF (Hz) : 0 RSRP (dBm) : -79.52 RSRQ (dB) : -12.22 Channel estimation state (Cell-spec.) : LOW CINR Channel estimation state (UE-spec.) : LOW CINR Channel estimation state (MBSFN) : LOW CINR Channel estimation CINR : 3.51 Channel length : SHORT AGC AGC RX gain (dB) : 42.49 RX PSD BO (dBFs) : -21.15 RX PSD (dBm) : -81.08 Noise level RS (dBm) : -83.83 Digital gain (dB) : 1.85 CINR RS (dB) : 4.31 NARROWBANDS Last DL NB : Central Last UL NB : 0 AFC Frequency offset RF (Hz) : -737 Frequency offset BB (Hz) : 0 PBCH MIB received quantity : 0 MIB timeout quantity : 0 OK Sent to modem: 'AT!="fsm"', delay 1000 ms SYSTEM FSM ========== +--------------------------+--------------------+ | FSM | STATE | +--------------------------+--------------------+ | RRC TOP FSM |CONNECTED | | RRC SEARCH FSM |CAMPED | | RRC ACTIVE FSM |CONNECTED | | PMM PLMN FSM |NORM_CAMPED | | EMM MAIN FSM |REGISTERED | | EMM AUTH FSM |KASME_DEFINED | | EMM CONN FSM |EMM_CONNECTED | | EMM TAU FSM |NULL | | EMM TEST FSM |NULL | | ESM BEARER FSM |BEARER_ACTIVE | | SMS MT FSM |IDLE | | SMS MO FSM |IDLE | | LPP FSM |IDLE | | HP MAIN FSM |IDLE | | HP USIM FSM |READY | | HP SMS MO FSM |IDLE | | HP SMS MT FSM |IDLE | | HP CAT FSM |IDLE | +--------------------------+--------------------+ OK Sent to modem: 'AT+CGPADDR', delay 1000 ms +CGPADDR: 1,"10.0.1.100" OK Sent to modem: 'AT+PING="172.27.131.100"', delay 5000 ms +PING: 1,172.27.131.100,360,253 LTE connection succeeded! DNS over NB-IoT failed... Disonnecting LTE ... Detaching LTE ... Shuttting down LTE... Pycom MicroPython 1.20.0.rc7 [v1.9.4-2833cf5] on 2019-02-08; FiPy with ESP32 Type "help()" for more information.

@shedaim I'd agree with @robert-hh. Such "test points" are often incorporated into a PCB for automatic testing during production. Most boards pass through an automatic testing stage during manufacture and at that time it can be "pressed down" onto a jig that makes contact with these test points and allows for full testing and quite often the loading of any boot code required. Here are some similar looking test points inside, of all things, and electric toothbrush. Note that they have helpfully labelled a lot of the test points on the silkscreen (Hint hint, Pycom)

@stevo52 Yes, from the distance, it sounds like a hardware problem with the board. Maybe a broken wire or a bad solder point at the P2 pin.

@elizar I wouldn't have expected it since the Putty output looked fine, but it does appear to be issues related to poor signal quality. I took the breadboard out of the loop and attached the FTDI headers directly to the board headers with Molex cables and the flash finally took! Thanks for the suggestion!

Hi, I am currently working on development board with ESP32-WROVER and Quectel BC66 NB-IoT module. BC66 module contains MTK2625 modem. Not sure if this might help you somehow. https://forum.micropython.org/viewtopic.php?f=18&t=5778

@robert-hh OK, I set up some code to try this out, several timers at different periods and several threads including one to start LTE, send an SMS and then deinit. From what I can see, the timers do NOT get interupted by the LTE device. It seems the timer counts are retained and dumped to REPL as soon as possible (buffered apparently). There is some corruption/mixup of REPL lines but all the timer flags are there I will investigate a bit further and see if I can use this to my advantage. One thread/timer I will need will be at 11uS preferably, so as it is too fast to capture by eye, I'll have to write to a file to a file to evaluate any impact by the LTE device. Biggest constraint might be the actual time to write to disk. A FIFO data buffer is probably a good solution - some work to do there. The test code was pretty rough and ready so its needs a lot of refinement to be truly useful as a valid test.

Hi Drop an email to sales@pycom.io with the details :)