@robert-hh It turns out the "periodic=False" attribute is all it needed. Works fine now.

@robert-hh Got it! Many thanks!

@le_wildfox I'm not very familiar with NB-IoT, but from what I understand, it is quite specifically designed to not offer great throughput or latency, as the priority is low power. The peak rate is between 20 and 250 kbits/s, and latency is counted in seconds... Not sure exactly what you expect to get...

Hey @timh , I have mentioned about the sensor, I am going to use for monitoring and I want to use cellular service, as wifi connection is not available here so not sure about which hardware will be better to use and if I try with GPY then need to know the better way to connect the Private network with GPY which help readings of sensor on AWS cloud And I am new comer to this area so please suggest the tools of AWS cloud which I should use to make this monitoring process display on my smart phone.

@ananda I suggest you check out https://pycom.io/where-to-buy/ and/or contact sales@pycom.io

@binux I haven't tried upip but support for uzlib should be available in the latest development firmware.

@seb it looks like the pytrack button wakes the board only if you enable the accel wake up. Since I disabled the accel wake up the button does not wake up anymore. Can anyone can confirm this ?

@torsi That's now fixed, thank you for your report

@xykon Thank you so much for the help; I believe you've rightly pointed out my error was assuming the board firmware was installed correctly and only the device firmware was the problem. Hopefully this can be useful to others: what I seem to have missed is the distinction between the Bootloader mode and the Application mode. Once I got my successful command line result from "dfu-util-static.exe", I didn't think the text from an immediately proceeding sentence beginning with "If, by mistake, the" would apply to me, so I likely skimmed over the crucial sentence: "If, by mistake, the libusbk driver was installed while the USB ID is the Application mode (0xF013 for Pytrack or 0xF012 for Pysense), then the Serial USB (CDC) driver has to be installed for application mode. This will allow Windows to allocate a COM port, which is required for REPL console." I recommend that the help page 4.2.1 (https://docs.pycom.io/chapter/pytrackpysense/installation/firmware.html) be rewritten to emphasize this point or at least put in a "Double-check Serial USB (CDC) driver is installed in Application mode" header right before the key sentence I missed. An additional element of confusion on that page is its direction regarding solely the "Pytrack/Pysense" boards, but it serves to document the steps for Expansion Board 3.0 firmware setup as well. Thanks again!

@xykon thanks for this note. In this case I didn't need to reflash the firmware, however I will remember your advice as I am sure to need it soon enough!

Sorry @jmarcelino for missing that bit in the documentation... it makes sense now. Thank you @MarcoBenini for the information about the defaults. That seems like a good solution.

Thank you @robert-hh and @jmarcelino! I will give it a go and report back. :-)

@jcaron I have two antennas which perform more robust. One, which looks similar, but is 22 cm long (18 cm up from the hinge). That one shows a nice current profile, peak in the middel of the "active" section and going down to almost zero towards bot sides. The other is a home-brew ground plane antenna, along a recipe from the ttn forum, which also work pretty well. Both are not very sensitive to touching the xxPy and moving. Compared to these the PyCom antenna performs between 6dB and 16 dB, depending on placement and touching. I have my xxPY built into a aluminium box with the antenna connector at the shorter side. The PyCom antenna shows some current at the connector, which explains the sensitivity to touching. Picture: GP antenna on FiPy in a box, built from a SMA connector an 1.5 mm wire. Tip wire it 82mm, the radial are 86 mm. [image: 1526903725057-gp-antenna-on-fipy.jpg]

@jcaron - thanks

@jmarcelino Oh. Yes I was using machine.deepsleep(). Now it works. Thank you for your help.