Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.

Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.

@afzal_m said in Add subscriptions via api: Thanks a lot @JeroenD. Maybe you are not aware of it but last month with did a major update on the document library after two years. But we only focused on the devices part. In August we will update the API part as well @Roalnd-Baldin is already working on it. Nice @afzal_m

Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.

@afzal_m Bedankt !!

Cool, still happy to receive your logs (as Eric requested)

I have been looking to this post: https://forum.iot.t-mobile.nl/topic/310/sim7000e-accepteert-de-genoemde-commandos-niet?_=1591271570193 I like to have it work with T-mobile NB IoT on a combination of the SparkFun SAMD21 Mini Breakout connection and the SIM7000E break out board. Is there anybody who has succeeded to do so with Arduino code? Thanks in advance for your answer.

@trick2011 I use the following sequence: AT+UDCONF=1,0 AT+USOCR=17,7000 <rx socket number> AT+USOCO=<socket>,“172.127.131.100”,<udp port> AT+USOWR=<socket>,<data length> <wait for @> <send user data> AT+USORF=<socket>,127 #127 is max rx length, depends on yr buffers +USORF: <socket>,“172.27.131.100”,15683,17,“downstream data” AT+USOCL=<socket> # close socket

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

I found the problem, I use an arduino leonardo with a dragino nbiot shield. For incomming/outgoing messages i use SoftwareSerial.h, to change the tx/rx pins to pins 10/11. I fixed the problem by using the normal rx/tx pins and it works. Hence the library seems to be my problem. Hope this helps anyone.

@Eric-Barten I still get the extra messages delivered even after deleting all but one subscriptions. Any thoughts on how to tackle this? Could it have something to do with downlinks not arriving? for example how lomg should I wait after sending before receiving?

There is no option to query the status of a downlink message. Buffering of downlink messages may occur on different places in our solution it is hard to give an clear response to such a request due to the asynchronous nature of the protocols. Note: after sending an uplink message we will try to downlink all buffered messages.

@Martijn-Kooijman I solved it by checking the return message after sending “AT+USOCR=17,7000”. Once it is contains “+USOCR: 0” in the returning string I know it is ok: (it takes about 5 s after a reset) added code: String check_sara=cmd("AT+USOCR=17,7000"); while ((check_sara.indexOf("+USOCR: 0",1)<0)) { delay(500); check_sara=cmd("AT+USOCR=17,7000"); Serial.println(check_sara);//just for checking }

@Crowdsourcer If you see 15 mA it means there is a problem. I measured an average of 6.7 uA in PSM

@sopwafel You could, but be aware of using PSM and expected latency. Your device might be sleeping again before it had the chance to receive a downlink message. I don’t know if it’s possible to use in combination with the T-Mobile CDP but you might want to take a look at LWM2M and CoAP. These protocols have acknowledgements build in.

I received this question a lot these days. I still need to understand why. Is our document library (getting) too complex maybe? Please let me know However, if you ordered your NB-IoT simcard at iot.t-mobile.nl, I can assure you that your simcard is already active. We want to save you from the simcard hassle as much as possible. All our NB-IoT simcards have the same configuration. To make sure that you can simply keep one single stock for all your different use cases/projects, Just register the IMEI number of your module in one of your projects. Configure your module with the right settings, put your simcard in it and it should work right away.

Okay, my problem is fixed. I flashed the sequans modem again and I tested my code again. But it was still not working. I wiggled the cable of the antenna a bit and it connected to the network! I think the antenna of my gpy wasn’t connected properly or the antenna cable is broken or something.

@eric-barten I didn’t register the device in the att assets. I’ve received some messages in the debug tab, but it has a delay of a day?? Now I have registered the device with the IMEI in the assets tab and I sent some test messages but I’m currently not receiving any.

@eric-barten That would be nice. But what channel to use for this PM then ?

Currently, data packet buffering works only in combination with PSM, in the nearest future it should also work with eDRX. So once you activated this feature on your module, packets will be buffered automatically.