@daniel I understand Telstra connectivity issue should be resolved. I don't see how to test it myself, Sequans firmware being unavailable at the moment. Did you get positive feedback in this forum?

@amket Thanks for the feedback, I'll look into adding some output such as "Connecting to Wifi network..." to make it more clear what is happening.

@pas We have KiCad footprints available on GitHub https://github.com/pycom/footprints All our development modules have the same footprint so if you have one for a WiPy2, LoPy or SiPy etc (NOT WiPy/WiPy1) then that will also work with the FiPy. We also have Altium design files for the Universal Expansion Board https://docs.pycom.io/chapter/datasheets/oem/universal_reference.html which for the headers uses the same footprint as the FiPy (it fits into the expansion board the same way).

@dmnk Sorry dominik, i have emergency on other projet and cannot do some test with my lopy4. In fact, as i previously said i work with sigfox on my company product. We send setting via downlink on our device to start them when necessary. For a 10K fleet device, 95% of them have receive downlink after 3 downlink (and aprox 50% one first downlink), so definitly for me downlink is more weak than uplink. As i understood the ohter post from xorlover and answer from seb, it's sigfox FSK ptp that is not yet present in firmware.

@nicolac Yes, you have to update to the lastest firmware, which is like 1.17.3.b1 or later. You can tell the firmware version by the commands: import uos uos.uname()

@dan, how did you fix this problem? Would you please post the code on both devices that you used? I am running in to the same issue. Thanks

Later I realized I needed to download the pycom libraries in https://github.com/pycom/pycom-libraries. There was the mqtt lib and now it works. Isn't this supposed to be in the online documentation? Thank you.

I've got an update. Today, I tried updating to the latest Sequans firmware and experienced strange issues. I tried updating to the latest firmware, downgrading to earlier release firmware, still problematic. Leaving the modem at 1.17, I unplugged and left it alone for a while. A few hours later, reconnected and tried running the exact code in this thread. So, at this point, the FiPy firmware and modem firmware are identical to when I first experienced these issues. This time, everything worked. I could successfully open sockets, send receive data, etc. This allows me to close out my evaluation of the FiPy modem. It seems there are still some major functional and reliability issues to be resolved from all parties, Monarch/Sequans, Pycom, and Verizon. I'll revisit this in the future and in the interim, drop in on the forums from time to time to see what current user experience has been.

Hi @turbolego Power consumption will vary with usage, you can find all the details on the datasheet: https://docs.pycom.io/chapter/datasheets/downloads/fipy-specsheet.pdf

Figured out the issue. Looks like the FiPy was consuming more current that my USB was able to deliver even though it was just running the sample PyMakr code of changing LED color. I connected a LiPo battery to it and didn't have an issue since. For those interested in figuring out how I got to this: I removed the FiPy module from the PySense Connected through USB to the computer and checked device manager for a new COM port If present, then PySense is fine. Without removing the USB to the PySense, I connected the FiPy and was able to program it. With the above basic steps you can determine if the board is actually bricked or just requires power.

@jcaron Thanks a lot for the explanation! That solved the question for me.

@grantosw Glad I could help. ;o)

I spoke too soon! >.< From a fresh wipe and firmware upgrade, I was able to run the I2C library. However, once I loaded my own modules onto the device and used them to connect to my network, calling "init" on an I2C instance caused the WiPy to freeze (connected over serial, but I could no longer type into the console). I built a bit-banged version of I2C yesterday and am able to use it on the same pins ("P8", "P9") without issue.

@akshayjames I think the problem is the button on the Pysense goes low when pressed, not high, so you want to wake up on low.

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