@evekites Ik gebruik de volgende commando’s:
op deze manier zie ik Hello World op de portal binnenkomen! firmware in de SIM7020E = 1752B06SIM7020E
Ik ben nieuw met IoT en ik heb een SIM7020E met dezelfde firmware. Als ik de bovenstaande commando’s uitvoer, krijg ik na AT+CSOSEND=0,0,“Hello World”, gelijk ERROR.
Ik snap (nog) niet wat ik fout doe. Kan iemand mij hier mee helpen?
Het werkt met het volgende:
8 = hoeveelheid characters
74657374 = ‘test’ in hex
@eric-barten dank voor je reactie. UDP heb ik al langere tijd werkend. De officiële informatie over CoAP, ook de link die je geeft, is heel beperkt. Als ik CoAP initieer op mijn device verwacht ik dat ik per UDP frame een JSON van CDP krijg op mijn applicatieserver, omdat UDP onder CoAP ligt. Echter, CoAP is een connectie, en verwacht dus data terug. Dat lijkt mij onmogelijk op deze manier. Toch is dat wat ik zoek: een full duplex stream naar mijn applicatieserver. Kan dat met CoAP? Of is er een andere manier? Zo ja welke?
In 1 van onze nieuwe apparaten in van product lijn RAE Systems (Honeywell global) hebben wij een BN-ioT modem.
Hierin heb ik een starterpack simkaart geplaats, inmiddels zie ik data in de portal komen.
Om deze data naar mijn pakket te krijgen moet ik het naar een url of ip sturen op de specifiek poort 50018.
Als ik bij de application server een :50018 toevoeg om het naar de juist poort te sturen krijg ik een error hoe kan ik dit toch voor elkaar krijgen?
Thank you very much for your request. The MQTT-SN CONNECT packet looks right so far and since you get an answer from the gateway, the communication works well. It seems that the registration in the cloud of things is not quite correct, especially the field ICCID. Quote from the user manual:
ICCID: The ICCID of the device (equal to the ID of the device)
Important here is the addition in brackets “equal to ID of the device”. In this case, the ID of the device is the IMSI and must also be specified when registering the device. Please try the registration of the device again with the IMSI in the field ICCID, then it should work.
unfortunately our UI is sometimes not working the way we have wished to.
You can fold the menu by using the toggle button or use zoom in/out option of your browser to view full content. In this case, however, it seems to me that there is no additional incoming message, but the UI falsely suggests that there is additional message.
A “pin” can only appear if the Device has sent a position. This ability is related to the functions of the device. Whether this was the case is not clear from the question.
For devices that are connected to the CoT via NB-IoT or MQTT-SN, the IMSI is the identifier to which the respective password is linked. If you use a different IMSI for the same device, you also need separate credentials for this identifier, i.e. you must register a second device in the CoT. The IMSI must be unique.
When registering, it is sufficient to first create only the credentials based on the IMSI. An IMEI does not necessarily have to be specified. In this case, no devices need to be deleted from the CoT either, since you then have two different devices in the CoT which are either online or offline depending on the SIM card used. It is only important that the device also uses the credentials coupled with the respective IMSI.
unfortunately, IMEI alone is not enough for the registration of NB-IOT devices but must be created with credentials. In the attached manual you will find the exact instructions for the registration of the NB-IoT devices.
You are right. This is exactly how it is currently implemented. The NB-IoT CoT access is currently only a test product and thus the behavior of the alarm is not scheduled to change anytime soon. I will forward your request to our internal team for further discussions.
Release announcement: Activation of NB-IoT network features
Dear IoT Community,
please note that we will soon be activating new features, as well as will update the configuration of already available features in the NB-IoT network. With the transition, you’ll be able to manage your NB-IoT devices even more flexibly and efficiently. The activation is currently planned for beginning of November and will affect our networks in Austria, Czech Republic, Germany and the Netherlands.
The changes at a glance:
• Switch to dynamic Power Saving Mode (PSM) - the network will now accept the values suggested by devices
• Switch to dynamic (long-periodic) Tracking Area Update (TAU/LP-TAU) - the network will now accept the values suggested by devices
• Introduction of Data Packet Buffering - the network will buffer up to 10 data packets for the sleeping devices in the PSM
If you already use PSM and / or TAU / LP-TAU, then please note that your devices may behave differently than usual after activating the network functions. We recommend checking the settings on your devices.
If you have questions, don’t hesitate to ask in our IoT Forum!
It works in the publish/subscribe manner. A device which wants to send data to CoT, needs to have implemented this protocol. The easiest way to implement is to use the Open Source Paho Client from von Eclipse.
CoT can only be addressed over the REST interface and therefore the connector is needed to convert incoming MQTT-SN messages to CoT messages.
There is a second important function of the connector. It interprets data, so for example temperature can be identified as such. Prerequisite for that is that MQTT-SN messages are being formatted according a predefined convention. How this is to be accomplished is described in the NBIOT-Protocol-Developerguide.
If MQTT-SN messages are correctly formatted and compliant to the convention described in the developerguide, then data is transferred into the Cloud of Things.
The mentioned IP address belongs to a private network, since it is the tunnel endpoint of the IPSec-tunnel from private APN of the CoT. This server is only acceible via the private APN.
For sending UDP packets to a server residing in the Internet, you need to have SIM cards with public APN (internet.nbiot.telekom.de). Since you have ordered only SIM cards for CoT, you are only able to send data to the CoT with IP 172.25.102.151:1883
There are a few ground rules for participation in our forum. Please respect these rules, and each other.
The forum language is English. This is an international community, with members from all over the globe. To share the knowledge between all of us, we use English as primary language.
For specific topics according your country like Netherlands, please use the relating section. There are appropriate specialists to support you in your question.
All-important guides you can find in our IoT Documentation - that might help you at the beginning.
Be creative and have fun!
If you have a question but don’t want to place it publicly, you are more than welcome to write directly to us. Please use this e-mail address: email@example.com
Looks like your connection to Internet of Things was lost, please wait while we try to reconnect.