• RE: QUECTEL BC95-B8 not connecting to Network

    @jonasled You can enable more verbose error reporting with AT+CMEE=2. That will tell you what kind of error you have.

    Quectel usually has their own version for every command so SARA N211 commands will not work.

    What I can think of:

    • Make sure you have the latest firmware
    • Make sure the SIM works (try with a different module?)
    • Make sure the antenna is properly connected
    • Make sure you are in range of a network (scan with AT+COPS=?)
    • Make sure you have a proper powersupply/cable (especially some USB supplies can be bad)
    • Make sure you have the correct LTE bands enabled
    • It should autoconnect to an available network but if it doesn’t you can force it with AT+COPS
    posted in The Thing For IoT Creators
  • RE: QUECTEL BC95-B8 not connecting to Network

    @jonasled Can you check if you have a working SIM card? Try AT+CPIN?

    It should return OK

    posted in The Thing For IoT Creators
  • LwM2M v1.2 is out!

    Awesome news ahead: LwM2M v1.2 specification is finally released! One of the headlining features of LwM2M v1.2 is LwM2M over MQTT! This is a good opportunity for LwM2M to get way more visibility, as MQTT (arguably the most popular IoT protocol) is currently missing any real data model.

    LwM2M 1.2 feature highlights: [1]

    • State-of-the-art energy-efficient security—Leveraging (D)TLS 1.3 and Connection ID enhances security while reducing the challenges and energy losses of connecting devices over LPWAs like NB-IoT.

    • MQTT as a transport protocol—MQTT users can now add LwM2M device management functionality. Inversely, using MQTT as a transport mechanism for LwM2M simplifies connecting to the cloud in some scenarios.

    • Single-step device commissioning—Now, bootstrapping a device requires just a single bi-directional session instead of the previous five exchanges, saving time, energy, and other resources.

    • Optimized data reporting—LwM2M data-format optimizations shave bytes from each message, increasing energy-efficiency, device lifespan, and return-on-investment (ROI).

    More details: [2]

    • New transports for LwM2M; this allows LwM2M messaging to be conveyed over MQTT and over HTTP.
    • Optimizations for the bootstrapping interface; this reduces the amount of data and the number of messages transmitted during the bootstrapping exchange.
    • Optimizations for the registration interface; this reduces the amount of data transmitted during registration exchanges.
    • Optimizations for the information reporting interface; observation attributes may now be included in an Observe operation.
    • Support for LwM2M gateway functionality; this allows non-LwM2M IoT devices as well as LwM2M devices behind a gateway to be connected to the LwM2M ecosystem and to manage those devices remotely.
    • New, highly optimized encoding format based on CBOR called LwM2M CBOR.
    • Enhanced functionality for firmware updates.
    • Definition of new notification attributes (edge, confirmable notification, and maximum historical queue). Edge allows notifications to be triggered on rising and falling edges. Confirmable notifications allow the control of reliable transmissions of notifications.
    • Maximum historical queue allows the control of time-series data usage. Clarifications of object versioning rules.
    • Updates to use the latest communication security protocols based on TLS and DTLS 1.3 (as well as the use of the Connection ID).
    • Flexibility to control the use of TLS and DTLS 1.3 through configuration information.
      Untangling the relationship of security credentials and their server configuration.

    [1] https://ioterop.com/lightweight-m2m-1-2-iot-device-management/
    [2] http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf
    [3] http://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Transport-V1_2-20201110-A.pdf

    posted in Announcements
  • How to create a second application URL?

    To add a seconde application URL you can perform the following …

    With the username and password from the projects API credentials

    Bildschirmfoto vom 2020-11-25 14-00-22.png

    Put the following HTTP request:

    PUT:
    https://iot.netwerk.t-mobile.nl:443/m2m/applications/registration

    HEADERS:
    Content-Type: application/json
    Authorization: Basic base64(<USERNAME>:<PASSWORD>)
    Accept’: 'application/json

    BODY:
    {
    ‘url’: ‘<YOUR APPLICATION URL>’,
    ‘headers’: { <YOUR HEADER FIELDS>}
    }

    If everything works fine you should get returned from the API
    {
    “msg”: “Success”,
    “code”: 1000
    }

    posted in The Thing For IoT Creators
  • RE: NB-IoT & location tracking

    Hi All,

    We would like:

    • Accuracy of 3 to 5 meters latitude / longitude
    • Correct altitude measurement(up to 1 meter, for certain use cases even more important than lat and longitude). This is for height measurements in building so that floor levels can be determined accurately
    • We would like secured connections to the service, preferably a VPN
    • A process that clients can be checked if they are to be trusted(we don’t want to deliver this sensitiedata to bad people with sinister plans)
    • Adjustable frequency of positioning, higher frequency means paying more. High frequency is refresh every second(for emergencies for instance)
    • Possibility to cross reference/compare the data with GPS data out of the field
    • A way to determine which radio’s on which cell towers are used, this will be important if the target is moving.
    • A service which checks the availability of the positioning service and availability of data

    Questions

    • Is the data available on all networks(2G, 3G, 4G - NB-IoT/LTE-M enabled devices). My / Our assumption is that it is, as long as three cell towers/radio’s can be connected to.
    • Are changes necessary in the firmware of cellular modules to use the service?
    • Is the data available as a service, so do we receive aggregated data. Or do we receive lang, long and altitude plus data where the data is retrieved from(cell towers and radio’s plus the signal strength data which comes with it?
    • Is the service strictly available on the network of T-Mobile? Or is the data still available when roaming takes place to other networks?
    • How reliable is the service, especially on moving targets, when roaming is necessary?
    • How accurate is the service? Or how accurate can you get?
    • To which height is the service still available(we have gone up to 2,5 kilometers on NB-IoT). Ewout Karel has done about 300 - 500 meters on a relatively fast moving target
    posted in Network & Coverage
  • RE: Quectel BC95-G problem with receive the "Hello Device" downlink message

    @lbr hi, if you still have problems please contact me via support@iotcreators.com and provide me your imei. I will help you.

    Regards, Roland

    posted in The Thing For IoT Creators
  • RE: NB-IoT network and DNS

    Hi @Artur-S ,

    @Stefan-de-Lange is correct public DNS is not reachable from the IoT creators sim cards. I didn’t see and DNS option available in NB-IOT only capable modems I must say. Indeed LTE-M gives access to public DNS and internet. You could try one of the prepaid cards some of the T-Mobile operators are offering for IoT.

    posted in Network & Coverage
  • RE: NB-IoT network and DNS

    @Artur-S As far as I am aware all NB-IoT connections are limited to the internal network only. The only reachable endpoint is the CDP so reaching your API endpoint directly is not possible. Maybe that LTE-M does offer this option. Someone from T-Mobile can comment on this 🙂

    posted in Network & Coverage
  • RE: NB-IoT network and DNS

    @Artur-S I don’t think so. And since your device can’t access open internet anyway it doesn’t make much sense to do it. Interested to hear why you need DNS 🤔

    posted in Network & Coverage
  • RE: How to get your nuSIM dev-kit online?

    @rogierlodewijks and @afzal_m
    Thanks for the honors and the devkit.
    First of all; indeed you cannot turn on the echo using the standardised commands also I have found no alternative.
    So sharing logs is more difficult.

    I think the example above has a small error in the order of things.
    Due to AT+CFUN=0 (which is switch off phone functionality)
    You cannot issue at+cops and at+cgdcont commands

    So the correct order is;
    AT+CMEE=1;+CSCON=1;+CEREG=5 (turn on some informative feedback)
    AT+CFUN=1
    AT+COPS=1,2,“20416”
    AT+CGDCONT=1,“IP”,“cdp.iot.t-mobile.nl”

    See if we are searching for a network
    AT+COPS? (If answer is 2 we are still searching)
    AT+CSQ (if first number is unequal to 99 we have a radiosignal)

    And then wait for:
    +CSCON:1 (RRC Connected)
    +CEREG:5,5,###### (Registered roaming)

    (I have updated the example above)

    posted in The Thing For IoT Creators