Is there any way for my device to know if a packet it has sent has been received?
@rgb93 No worries, the IMEI is gone. Have you tried to change it to CoAP via the portal’s interface?
Can you provide me the ‘adaptationLayerName’?
@afzal_m I registered the device as CoAP with the command you provided. This seems to go wright. When I try to send with AT+NMGS I receive an error and that error seems to come because my module is not registered on the Huawei platform. I disabled this because Huawei registration was not needed with UDP. I tried to reregister and read out the registration process with AT+NMSTATUS but the outcome is ‘Registration Failed’. Without registration on the Huawei platform AT+NMGS can’t be used. Do get me wrong, Huawei registration is not establishing a connection with the CDP.
The link to the documentation has changed to https://docs.iotcreators.com/docs/sodaq-sara-aff-n211-1
@Roalnd-Baldin the module is registered to the CDP (AT+CGATT = 1 and AT+CSQ = 23), this is not the problem. The problem is the registration to the Huawei part of the CDP.
With UDP we disable the auto connect to Huawei platform because of the energy consumption (AT+QREGSWT=0). For Neul Messaging this connection needs to be set up first. But this is not working. Correct me if i’m wrong.
Can someone provide me more information and AT commands for Neul messaging?
magnatron last edited by
This what you looking for? (pseudo)
AT+CGDCONT=1,"IP","cdp.iot.t-mobile.nl" AT+NCDP="172.27.131.100" AT+NSMI=0 AT+NNMI=0 AT+CFUN=1 AT+NBAND=8 AT+COPS=1,2,"20416" // Check for CSQ: AT+CSQ // until lower than 99.99 // Then wait for attach: AT+CGATT // until 1 // Then send message: AT+NMGS=<message-size>,"<message>" // And read response to check for OK
@magnatron Thank you for your response!
These commands are exactly what I tested with. But I keep receiving CME Error: 4 at AT-NMGS.
I understand that there needs to be a connection to the Huawei part of the platform. Is this correct?
I found the commands here: https://support.sodaq.com/Shields_and_Bees/NB-IoT%20Shield/passthrough/#t-mobile-coap
Sorry I replied with a different account.
@rgb93 before april 2018 the Neul Messaging Protocol was a Huawei Ocean Connect propietary protocol.
But later the later on they made the source code available to us. We used the same source code to create the Neul Messaging Adapter in our Service Capability Server.
So if the error says that there is no connection to the Huawei platform, it simply means that there is no connection with our Neul Messaging adapter. Pls send me your IMEI number and group name (CON_00000xxx) by e-mail or DM and I will check it.
@afzal_m Proprietary sucks I hope more open protocols are added, UDP is pretty limiting