• Troubleshooting lte connections

    GPy gpy lte nb-iot
    4
    0 Votes
    4 Posts
    785 Views
    robert-hhR
    @shedaim There is a problem in the lte.attach() API concerning parsing the response from the network. @xykon adresses this in a trial firmware build at [LINK NO LONGER AVAILABLE] Please download and install that (install from file). It may fix you problem. See also this thread around https://forum.pycom.io/topic/3549/important-update-regarding-lte-modem-updates/83
  • 2 Votes
    7 Posts
    1k Views
    R
    @robert-hh Many thanks. :)
  • NB-IoT configuration for USA

    FiPy fipy nb-iot nb-iot coverage t-mobile
    1
    0 Votes
    1 Posts
    437 Views
    No one has replied
  • 0 Votes
    1 Posts
    475 Views
    No one has replied
  • 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.
  • nb-iot on t-mobile NL

    Discussion nb-iot t-mobile
    2
    2 Votes
    2 Posts
    541 Views
    A
    @eric-waai We have successfully connected to our Huawei eNodeB based NB-IoT network in Norway with modem firmware revision 37781. For some reason the 38729 firmware revision is not working. Our NB-IoT network is deployed in guard band.
  • NB-IoT attach issue

    GPy gpy nb-iot pytrack
    1
    0 Votes
    1 Posts
    634 Views
    No one has replied
  • 0 Votes
    18 Posts
    3k Views
    danD
    Hi @agotsis, Please check this post for more info about this issue. Hope this helps!
  • 0 Votes
    4 Posts
    745 Views
    J
    @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...
  • NB-IoT limitations with Huawei base station.

    GPy gpy fipy nb-iot huawei
    2
    3 Votes
    2 Posts
    733 Views
    le_wildfoxL
    Hi! "Full support for Huawei is planned for early Q2 2018" --> is there any update for this? Is it now supported? Thanks!
  • PSM & eDRX

    Enhancements nb-iot deep sleep
    2
    3 Votes
    2 Posts
    871 Views
    A
    Is there any release date for the support of PSM and eDRX features? If you cant keep up with the amount of work you have to deliver, maybe you should think something like bounties for most requested features by your community.
  • NB-IoT for Azure or AWS? No UDP protocol

    GPy nb-iot tcp
    6
    0 Votes
    6 Posts
    2k Views
    J
    @electronic CoAP is the protocol of choice in NB-IOT and used where the carrier offers a “connected device platform” (sometimes the only option, as some operators don’t even give UDP access)
  • NB-IoT on fipy

    Comments & Feedback nb-iot fipy amarisoft
    7
    0 Votes
    7 Posts
    2k Views
    N
    @jmarcelino I am still in need of a way to use NB-IoT on fipy. Is there a way to achive it? As I can see others have the same problem as me, so can we have some update on the state of the matter?
  • 0 Votes
    2 Posts
    955 Views
    T
    @bettina Hi Bettina, I am based in Australia and developing a remote flood monitoring solution using LoPy4 (soon to be FiPy). I have plans to work with Vodafone locally and wish to get a proof of concept together using NB-IoT. Can you share information about the outcomes of the NB-IoT workshop to help get me started. I have systems working with Sigfox and LoRaWAN. Now just want to adapt to test with NB-IoT. Cheers Peter.
  • 0 Votes
    10 Posts
    2k Views
    M
    @paul-thornton said in FiPy NB-IOT Example Codes for beta network testing: @mfa2214 We can support Huawei, but it depends what feature set the network operators enable to how well this will work :) Hi all, I'm trying to attach the "webe aka unifi" as network operators in Malaysia using band 5. unfortunately, modem still cannot attached and fipy also cannot listening the base station (Huawei e-nobe-b). below is the error i got: lte.connect() Traceback (most recent call last): File "<stdin>", line 1, in <module> OSError: LTE modem version not read lte.connect() Traceback (most recent call last): File "<stdin>", line 1, in <module> OSError: modem not attached Currently using FiPy-1.18.1.r7 as the modem f/w. Still do not know what happend. Hopefully someone could help. Many thanks
  • LTE support for Telia and Telenor (Norway)

    GPy lte nb-iot cat-m telia telenor
    18
    0 Votes
    18 Posts
    1k Views
    S
    @Gijs @Yoann-Baud any luck here? I'm in Norway and using the same setup. We've had some discussions before but haven't been able to get around this either and any updates on this case you have here that you could share would be very helpful! Scott
  • GPy NB-IoT connectivity with AMARI LTE 100

    GPy gpy nbiot sim nb-iot
    7
    1 Votes
    7 Posts
    1k Views
    I
    I saw your updated NB-IoT section in the documentation and would like to clarify one thing. Does below mean that an NB-IoT connection between GPy and my AMRI LTE 100 is not possible as of this moment? Current NB-IoT limitations At the moment the NB-IoT firmware supplied by Sequans only support Ericsson base stations configured for In-Band mode. Standalone and guard-band modes will be supported in a later release. Support for Huawei base stations is also limited and only lab testing with Huawei eNodeB is recommended at the moment. Full support for Huawei is planned for early Q2 2018.
  • SIM slot and G01 on custom board

    Comments & Feedback sim g01 nb-iot lte-m
    1
    0 Votes
    1 Posts
    639 Views
    No one has replied
  • LTE NB-IoT DNS

    FiPy nb-iot fipy firmware dns
    14
    1 Votes
    14 Posts
    3k Views
    L
    @combaindeft I finally found the time to test this and it works indeed! Just a heads up, Google DNS is 8.8.8.8 and 8.8.4.4, not 4.4.4.4 :)