• Orange attach time very big

    GPy attach time connectivity
    3
    0 Votes
    3 Posts
    50 Views
    C
    @Gijs I tried last pycom firware update 1.20.0.r7
  • attach() diagnosis?

    Discussion attach sequans provider diagnosis nb-iot
    1
    0 Votes
    1 Posts
    254 Views
    No one has replied
  • 0 Votes
    7 Posts
    629 Views
    K
    @reidfo I've put more time than I would like into the lte here in oz too Steve. Stumbled across some bizarre current draws after modem reset in my battery powered application. On the upside I can now finish an lte connection & get into micropower deepsleep in 3s whereas the disconnect/detach sequence used to take more like 7s. These gems are hard won by those of us who go down these rabbit holes & I'd be happy to share on a wiki. I also think pycom HQ could post some material too, like exactly what lte.init() does for instance.
  • 0 Votes
    20 Posts
    2k Views
    L
    @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
  • lte.attach() doesn't work, but modem is attached

    GPy gpy attach nb-iot
    9
    0 Votes
    9 Posts
    1k Views
    P
    @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.
  • NB-IoT in Austria

    FiPy nb-iot fipy attach
    12
    0 Votes
    12 Posts
    2k Views
    robert-hhR
    @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
  • 1 of 5 FiPys connect to NB-LTE

    FiPy fipy signal missing attach nb-iot
    4
    0 Votes
    4 Posts
    1k Views
    C
    After >18 hours of connecting the last device finally started working with the network. I have no idea what happened, because I made no changes to anything. The only thing I can say is that the commands I have in the first post should be enough and be patient with it as it can take >24 hours to find signal and connect.