Navigation

    iotcreators.com web
    • Login
    • Search
    • forum.iotcreators.com
    • Tags
    • Popular
    • Recent
    • Register
    1. Home
    2. Roalnd Baldin
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Roalnd Baldin

    @Roalnd Baldin

    Deutsche Telekom IoT

    15
    Reputation
    52
    Posts
    63
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online
    Location Pascalstr. 11, 10587 Berlin, Germany Age 53

    Roalnd Baldin Follow
    ScS PoC Deutsche Telekom IoT Global Moderator Admin

    Best posts made by Roalnd Baldin

    • Does roaming works in Spain with Vodafone?

      Hi,

      today we took a nice comort sensor (CO2/Temp/Humidity/BodySense) in Barcelona into operation.

      We configured

      • 21401 as PLMN ID for Vodafone Spain
      • and used 20 for the frequencyband (800Mhz).
      • cdp.iot.t-mobile.nl as APN for IoT Creators

      It worked immediately without any problems.

      Regards, Roland

      posted in Network & Coverage
      Roalnd Baldin
      Roalnd Baldin
    • RE: Quectel BC66, UDP, T-Mobile SIM in Germany: DNS parse failed

      Hi Stefan,

      you are a cool guy!! This solved the problem. It was the whitespace.

      Many many thanks for your support!!

      Regards, Roland

      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • RE: Quectel BC66, UDP, T-Mobile SIM in Germany: DNS parse failed

      Hi Stefan,

      again many thanks. It works now. I can send data to my App. The following sequence works for Quectel BC66:

      Deactivate auto sleep mode

      AT+QSCLK=0
      

      Persistent network and APN setup

      AT+QBAND=1,8
      AT+CFUN=0
      AT*MCGDEFCONT="IP","cdp.iot.t-mobile.nl"
      

      Restart the module as some configurations only take place after a reboot.

      AT+QRST=1
      

      After reboot wakup from sleep, deactivate auto sleep mode again and wait for network connect

      AT+QSCLK=0
      
      +IP: 10.128.0.134
      

      Create a UDP socket and for UDP server

      AT+QIOPEN=1,1,"UDP","172.27.131.100",15683,1001,0,0
      

      Send message “Hello World”

      AT+QISEND=1,11,48656c6c6f20576f726c64
      
      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • RE: Would it be possible to add the Grove - Base Shield for Arduino V2 to the tuino 096

      Hi Mario,

      Tuino 096 is an Arduino Zero (M0) compatible board. Grove Base Shield V2.0 doesn’t support this explicitity.

      I recommand to try"ARDUINO MKR CONNECTOR CARRIER (GROVE COMPATIBLE)" instead. With this shield you can bridge from Zero/M0 to sensors with Grove connectors.

      Regards, Roland

      posted in Network & Coverage
      Roalnd Baldin
      Roalnd Baldin
    • RE: Oeps

      Hi Joop,

      I will fix this.

      Could you please give me your IMEI?

      Regards, Roland

      posted in General discussion / Other topics
      Roalnd Baldin
      Roalnd Baldin
    • RE: API access does not work

      @paulvha This URL and headers work for me:

      To get the list of all devices:
      URL:
      GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1

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

      This should work with your credentials:
      curl -X GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1 -H 'Authorization:Basic base(<USERNAME>:<PASSWORD>)

      As you can see the request works also without Content-Type and Accept.

      To get the details of a single device:
      URL:
      GET https://iot.netwerk.t-mobile.nl:443/rest/device/<ID>

      Headers:
      Content-Type:application/json
      Authorization:Basic base64(USERNAME:PASSWORD)
      Accept:application/json

      To get the details of the device don’t use the deviceId!

      Regards, Roland

      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • RE: NB IoT in Czech Rep.

      Hi Petr,

      if I understood you right I see the following challenges:

      1. find a location with NB IoT coverage.
      2. attach your device to the NB-IoT network of T-Mobile Czech.
      3. send messages via UDP to Cloud of Things
      4. decode the payload of your UDP message and integrate it with Cloud of Things

      Please let us get directly in contact, that we can speak about it (roland.baldin@t-systems.com).

      Regards, Roland

      posted in Network & Coverage
      Roalnd Baldin
      Roalnd Baldin
    • 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
      Roalnd Baldin
      Roalnd Baldin
    • RE: eDRX in Germany for NB-IoT

      @Stefan-de-Lange Hi Stefan, nezwork specialists developed a simulation tool for NB-IoT devices with which it is possible to understand the power consumption and battery live time by simulating different protocolls and NB-IoT features.

      Let me try ro access to it. We can have a conf-call and play a little bit with it. Maybe it is interesting for us.
      I guess my colleagues are interested in our feedback about it.

      Regards, Roland

      posted in Network & Coverage
      Roalnd Baldin
      Roalnd Baldin
    • RE: Is there any way for my device to know if a packet it has sent has been received?

      @afzal_m said in Is there any way for my device to know if a packet it has sent has been received?:

      https://docs.iotcreators.com/docs/ii-network-attach

      The link to the documentation has changed to https://docs.iotcreators.com/docs/sodaq-sara-aff-n211-1

      posted in Network & Coverage
      Roalnd Baldin
      Roalnd Baldin

    Latest posts made by Roalnd Baldin

    • RE: Message forwarded multiple times.

      @Gijs-Mos
      I checked the UDP logs for your device and I agree. Your device doesn’t send the messages twice.

      If your application end-point doesn’t return to our platform within 1 second we go into a re-try loop to re-deliver the message. We re-try max. 5 times. Every minute ones. If within the period of re-trieng additional messages from other devices arrive they are put into the same post request and delivered as an additional element of the “reports” array. But in this case you would see different serialNumbers and timestamps.

      Is it possible that your callback returns sometimes slower than 1 second. In this case our platform would re-deliver the message a second time.

      I saw cases where the application end-point didn’t publish the message into a queue for asynchronous processing. It processed the message directly and stored it away into a DB. Sometimes the DB blocked. By the this the response time was bad and the messages have been delivered a second time.

      Regards, Roland

      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • Via which IP IoT Creators SCS webhook forwards uplink messages to application callback URL?

      Hi,

      many users ask via which IP address IoT Creators SCS forwards received uplink messages to the registered application callback URL:

      IoT Creators SCS forwards the uplink messages to your application callback URL via one of the two IPs

      • 18.195.119.162
      • 18.195.17.174

      Hope this helps you to configure the IP whitelists of your application.

      Regards, Roland

      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • RE: Quectel BC66, How to improve very-first-attachment time
      • Before activating radio module Set APN with AT+QCGDEFCONT rather than **AT+CGDCONT
      • Set frequency band explicity with AT+QBAND
      • Configure first APN, fequency band and mobile operator ID before switching on automatic attachment
      posted in Hardware
      Roalnd Baldin
      Roalnd Baldin
    • Quectel BC66, How to improve very-first-attachment time

      As you know the very-first-attachment to the network can take multiple minutes. Sometimes this creates problems in the production process.

      Out of this reasons we are looking for possible measures to improve the very-first-attachment time.

      Regards, Roland

      posted in Hardware
      Roalnd Baldin
      Roalnd Baldin
    • RE: Quectel BG96, Error while trying to ping the UDP Server

      @Rasyid Do you have a valid network connection ?

      For Quectel BG96 you can verify the network connection with the following AT commands

      AT+CGPADDR                    //check IP address
      AT+CGATT?                     //check if attached to network
      AT+COPS?                      //check current set MNO
      AT+COPS=?                     //scan network for mobile operators
      AT+CGDCONT?                   //check APN
      AT+QPING=1,"172.27.131.100"   //ping UDP server
      

      Regards, Roland

      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • RE: Ack message from server

      @David-Netten

      Hi David,

      you are right, that the UDP server of IoT Creators doesn’t send back an acknowledgment for a received messages.

      BUT: The CoAP/Leul server of IoT Creators acknowledges a received messages with a “2.05 Content” acknowlegment.

      Be aware that CoAP/Leul is the Huawei flavor of CoAP and it is supported by Huawei chipset such as HiSilicon which are used in moduls such ublox N211 or Quectel BC95.

      For many customers it is not enough to have an acknowledgment between the device and the IoT middleware. The implement an asynchronous acknowledgment between the application and the device on the basis of a downlink message. If you would need the asynchnronous application acknowledgment it wouldn’t make a difference between CoAP/Leul and pure UDP.

      Regards, Roland

      ​

      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • RE: Ack message from server

      @David-Netten be aware the both the CoAP/Leul server and the UDP server are hosted on the same IP 172.27.131.100. But the port of the CoAP/Leul server is 5683 and the port of the UDP server is 15683.

      CoAP/Leul is special CoAP flaviour from Huawei. Some of the Huawei chipset such as HiSilicon which are used e.g. in ublox N211 or Quectel BC95 support it.

      The AT commands for the Quectel BC95 to send and receive messages via CoAP/Leul looks like the following:

      # Read current configuration
      AT+UCOAP?
      
      # Set OceanConnect CoAP server and port   
      AT+NCDP="172.27.131.100",5683
      
      # Activate send message indicator
      AT+NSMI=1
      
      # Send Hello World message
      AT+NMGS=11,"48656c6c6f20576f726c64"
      
      +NSMI: SENT                                                                      
      
      # Activate receive message indicator 
      # and display received message 
      AT+NNMI=1 
                                                                                       
      # Receive downlink message
      +NNMI: 16,"48616C6C6F20766F6E20536572766572"                                     
      
      # Activate receive message indicator with message display 
      AT+NNMI=2
      +NNMI     
                                                                             
      AT+NMGR
      16,"48616C6C6F20766F6E20536572766572"                                   
      
      

      Regards, Roland

      posted in The Thing For IoT Creators
      Roalnd Baldin
      Roalnd Baldin
    • Tutorial available: How to integrate IoT Creators with AWS Lambda, AWS Timestream DB and Grafana

      Hi,

      just published the first version of a tutorial how to integrate a “real” comfort sensor with IoT Creators, AWS Lambda, AWS Timestream DB and Grafana in our documentation library.

      7b0454a7-ded6-45c1-b00f-6ccac65a9a79-image.png

      • Step 1: Register and activate sensor device
        • Register device in IoT Creators
        • Activate IMBUILDING comfort sensor
      • Step 2: Create AWS user and role with IAM
        • Create Role for Lambda Function
        • Create User for Grafana Client
      • Step 3: Create AWS Timestream DB
        • Create IoT DB
        • Create IoT Table

      • Step4: Create AWS Lambda function for data decoding and injection
        • Create Lambda function
        • Create up-to-date boto3 library Layer and bind it to Lambda function
          • Create updated boto3 library with Timestream support
          • Create Lambda Layer for updated boto3 library
          • Assign updated boto3 library Layer to Lambda function
      • Step 5: Make Lambda function accessable from the internet
        • Create API Gateway
        • Bind Lambda function to API Gateway
        • Test Lambda function and verify if data is written to Timestream DB
      • Step 6: Add static authentication token to Lambda function
        • Create Lambda authorizer function
        • Bind Lambda authorizer to API Gateway
        • Test the authorization
      • Step 7: Integrate IoT Creators with AWS Timestream DB
        • Register your AWS Lambda function as application callback in your IoT Creators project
        • Test the integration
      • Step 8: Integrate Grafana with AWS Timestream
        • Add Amazon Timestream Plugin to your Grafana
        • Add Amazon Timestream Data Soruce to your Grafana
      • Step 9: Create an IoT Dashboard in Grafana
      • Step 10: Integrate AWS Simple Queue Service
      posted in Announcements
      Roalnd Baldin
      Roalnd Baldin
    • 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
      Roalnd Baldin
      Roalnd Baldin
    • 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
      Roalnd Baldin
      Roalnd Baldin