• RE: Roaming - local network partners

    @JakubT , in addition to @Ronan-Lacroix last post, he also checked the simcard numbers that you sent to me by email and he did not see any attempts to attach to the network so far…

    posted in Network & Coverage
  • RE: Collegial roaming?

    @magnatron yes it is correct

    But it still possible that in some places there is no network available at all.
    Some operators only activated part of their networks.

    posted in Network & Coverage
  • RE: The message never arrives from the device

    Hi Peter,

    I just contacted you via our support channel so I can do some additional tests to your connection.

    Can you please send my your IMEIs as a response to the email which you just got.

    Many thanks!

    Regards, Roland

    posted in Network & Coverage
  • RE: Solution Guidelines for successful IoT deployments

    Btw: our goal is also to minimize signaling storms from inefficient IoT devices not supporting the TS.34 Radio Policy Manager (RPM) feature. What’s your experience with TS.34 RPM so far?

    posted in Announcements
  • Solution Guidelines for successful IoT deployments

    Do you know that you can save a lot of time in your IoT development and deployment activities by following our IoT solution guidelines? 💡
    Deutsche Telekom has a team dedicated to continuously improving the network, upgrading it with new features and testing and certifying of modules of all manufacturers to make sure they work well with our networks.

    If you additionally respect our simple rules like:

    • avoid synchronous device behavior - add randomization to your cloud app and firmware

    • only send wake-up messages to devices that you know are attached to the network (make sure you know the device status)

    • and some more

    you’ll end up with an amazing IoT application and successful business case. We’re here to help you, feel free to add your question as a comment here or contact me via uta@iotcreators.com.

    posted in Announcements
  • Infos about downlink API and binary data

    Currently the API supports the following for functions/URLs to send downlink messages to the device

    • downlinkMsg/0/data
      Sends regular queued downlink messages to device when uplink is received.

    • downlinkMsgBase64/0/data
      Sends queued binary data blob message to device when an uplink is received. The function expects base64 encoded payload from the applaction as input into this function. Before the message is sent to the device it is decoded back to binary and sent to the device.

    • downlinkMsgDrx/0/data
      Same like downlinkMsg/0/data but without queuing.

    • downlinkMsgBase64Drx/0/data
      Same like downlinkMsgBase64/0/data but without queuing.

    posted in The Thing For IoT Creators
  • RE: Downlink API dataformat

    @Lauwie007 said in Downlink API dataformat:

    Downlink data received: 00 (but this is ASCII, which translates to 3030 in HEX)

    Your assumption here is wrong @Lauwie007 this is binary the device visualizes the received data for you in HEX so it received 0x00 binary 2 bytes which is what you want to achieve.

    +CSONMI: 0,2,00 means I received 2 bytes both all zeros.

    Regards,
    Eric

    posted in The Thing For IoT Creators
  • RE: LTE-M Connection Problem with BG96

    @Kurosh

    I don’t see the URCs arriving at your screen. As described in my last message, please configure your URC port.
    If it is configured correctly you should see something like this:

    ate0 
    ate0
    
    OK
    
    at+cfun=0 
    
    OK
    
    at+qcscon=1 
    
    OK
    
    at+cereg=2 
    
    OK
    
    at+cfun=1 
    
    OK
    
    +CPIN: READY
    
    +QUSIM: 1
    
    +QIND: SMS DONE
    
    at+cops=1,2,"26201",8 
    
    OK
    
    +QCSCON: 1,1
    
    +CEREG: 5,"6F55","18CB40E",8
    
    +QCSCON: 1,0
    
    +CEREG: 5,"6F55","18CB404",8
    

    Notice that the +QCSCON: 1,1 and +CEREG: 5,“6F55”,“18CB40E”,8 pop up automatically.
    Also right after turning on the radio with AT+CFUN=1 you can see

    +CPIN: READY
    
    +QUSIM: 1
    
    +QIND: SMS DONE
    

    popping up automatically. I dont see that in your logs. Please configure your URC port and issue the commands as I’ve shown in the example here.

    Best
    Yassine

    posted in The Thing For IoT Creators
  • RE: LTE-M Connection Problem with BG96

    Hi Kurosh,

    In an earlier message when you changed the APN it was working fine. Is there anything you changed since than? In general your AT commands seem fine.

    Can you please do the following:

    Turn off the radio with AT+CFUN=0. Do a AT+CEREG=3 and AT+QCSCON=1 (or if that doesn’t work use AT+CSCON=1). This will automatically print URC messages giving us an indication about what the module is doing. You should see automatic +CEREG and +CSCON messages arriving on your screen when you try to attach. If that doesn’t happen, your URC Indication configuration is not correct. Try using the command AT+QURCCFG=“urcport”,[“usbat” or “usbmodem” or “uart1”]. This depends on which serial port you are using so just try out one after the other, reboot the module and see if you get the URCs (an indication that it’s configured correctly is that you get a +CPIN: READY automatically printed on the screen when the module boots up.)

    After that please send the logs so we can try to figure out what is going wrong.

    Best
    Yassine

    posted in The Thing For IoT Creators
  • RE: LTE-M Connection Problem with BG96

    @Kurosh said in LTE-M Connection Problem with BG96:

    08:08:07.346 -> at+cops=1,2,“26201”,8

    why does it show “8”?

    posted in The Thing For IoT Creators