Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 129.3 >
edited by Xiaoling
on 2024/09/14 10:54
To version < 134.1 >
edited by Mengting Qiu
on 2024/10/18 15:41
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 2.2 Speed Up Network Attach time ==
57 57  
58 +
58 58  **BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**.
59 59  
60 60  **Note:**Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power.
... ... @@ -73,7 +73,7 @@
73 73  
74 74  See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
75 75  
76 -=== **1.Configure Frequency Band** ===
77 +=== **1. Configure Frequency Band** ===
77 77  
78 78  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
79 79  
... ... @@ -143,7 +143,7 @@
143 143  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
144 144  
145 145  
146 -=== **2.Configure search network sequence** ===
147 +=== **2. Configure search network sequence** ===
147 147  
148 148  AT+QCFG="nwscanseq",<scanseq>,1
149 149  
... ... @@ -156,8 +156,9 @@
156 156  
157 157  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
158 158  
159 -=== **3.Configure Network Category to be Searched for under LTE RAT** ===
160 160  
161 +=== **3. Configure Network Category to be Searched for under LTE RAT** ===
162 +
161 161  AT+QCFG="iotopmode",mode,1
162 162  
163 163  0 eMTC 
... ... @@ -164,8 +164,9 @@
164 164  1 NB-IoT 
165 165  2 eMTC and NB-IoT
166 166  
167 -=== **4.AT command to set frequency band and network category** ===
168 168  
170 +=== **4. AT command to set frequency band and network category** ===
171 +
169 169  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
170 170  
171 171  AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
... ... @@ -187,6 +187,7 @@
187 187  
188 188  == 3.1 General UDP Connection ==
189 189  
193 +
190 190  The NB-IoT Sensor can send packet to server use UDP protocol.
191 191  
192 192  
... ... @@ -231,7 +231,7 @@
231 231  
232 232  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
233 233  
234 -* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
238 +* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
235 235  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
236 236  
237 237  [[image:image-20240819103212-2.png]]
... ... @@ -305,7 +305,6 @@
305 305  
306 306  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
307 307  
308 -
309 309  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
310 310  
311 311  
... ... @@ -345,7 +345,6 @@
345 345  
346 346  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
347 347  
348 -
349 349  ==== 3.3.3.2 Uplink Examples ====
350 350  
351 351  
... ... @@ -417,7 +417,6 @@
417 417  
418 418  * (% style="color:blue" %)**S31B-CB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
419 419  
420 -
421 421  === 3.4.1 For device Already has template ===
422 422  
423 423  ==== 3.4.1.1 Create Device ====
... ... @@ -577,7 +577,6 @@
577 577  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
578 578  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
579 579  
580 -
581 581  == 3.6 ThingsBoard.Cloud (via MQTT) ==
582 582  
583 583  === 3.6.1 Configure ThingsBoard ===
... ... @@ -665,11 +665,82 @@
665 665  [[image:image-20240820112426-40.png]]
666 666  
667 667  
668 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
669 669  
670 -=== 3.7.1 Create device & Get Credentials ===
669 +== 3.7 ThingsBoard.Cloud (via COAP) ==
671 671  
671 +=== 3.7.1 Configure ThingsBoard ===
672 672  
673 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
674 +
675 +
676 +(% style="color:blue" %)**Uplink Converter**
677 +
678 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
679 +
680 +To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
681 +
682 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729141300-1.png?width=1115&height=552&rev=1.1||alt="image-20240729141300-1.png" height="579" width="1168"]]
683 +
684 +
685 +(% style="color:blue" %)**Downlink Converter**
686 +
687 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
688 +
689 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729142505-3.png?width=1023&height=507&rev=1.1||alt="image-20240729142505-3.png" height="579" width="1168"]]
690 +
691 +
692 +==== 3.7.1.2 COAP Integration Setup ====
693 +
694 +
695 +Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
696 +
697 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729144058-4.png?width=1021&height=506&rev=1.1||alt="image-20240729144058-4.png" height="583" width="1176"]]
698 +
699 +
700 +The next steps is to add the recently created uplink converters;
701 +
702 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729150142-5.png?width=1023&height=507&rev=1.1||alt="image-20240729150142-5.png" height="591" width="1193"]]
703 +
704 +
705 +==== 3.7.1.3 Add COAP Integration ====
706 +
707 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729161543-9.png?width=1009&height=500&rev=1.1||alt="image-20240729161543-9.png" height="590" width="1191"]]
708 +
709 +
710 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
711 +
712 +==== 3.7.2.1 Instruction Description ====
713 +
714 +
715 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
716 +* AT+SERVADDR=COAP Server Address,5683
717 +
718 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
719 +
720 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172305-12.png?width=624&height=361&rev=1.1||alt="image-20240729172305-12.png" height="417" width="721"]]
721 +
722 +Note:The port for the COAP protocol has been fixed to 5683
723 +
724 +
725 +* AT+URL1=11,"i"
726 +* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
727 +*
728 +
729 +-CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
730 +
731 +e.g.
732 +
733 +* AT+URL1=11, "i"
734 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
735 +
736 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172500-14.png?width=700&height=403&rev=1.1||alt="image-20240729172500-14.png" height="413" width="718"]]
737 +
738 +
739 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
740 +
741 +=== 3.8.1 Create device & Get Credentials ===
742 +
743 +
673 673  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
674 674  
675 675  [[image:image-20240820112516-41.png]]
... ... @@ -716,10 +716,9 @@
716 716  
717 717  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
718 718  
790 +=== 3.8.2 Simulate with MQTT.fx ===
719 719  
720 -=== 3.7.2 Simulate with MQTT.fx ===
721 721  
722 -
723 723  [[image:image-20240820112552-44.png]]
724 724  
725 725  [[image:image-20240820112604-45.png]]
... ... @@ -731,7 +731,7 @@
731 731  [[image:image-20240820112626-47.png]]
732 732  
733 733  
734 -=== 3.7.3 tago data ===
804 +=== 3.8.3 tago data ===
735 735  
736 736  
737 737  [[image:image-20240820112637-48.png]]
... ... @@ -739,7 +739,7 @@
739 739  [[image:image-20240820112647-49.png]]
740 740  
741 741  
742 -== 3.8 TCP Connection ==
812 +== 3.9 TCP Connection ==
743 743  
744 744  
745 745  (% style="color:blue" %)**AT command:**
... ... @@ -759,7 +759,7 @@
759 759  [[image:image-20240820112716-51.png]]
760 760  
761 761  
762 -== 3.9 AWS Connection ==
832 +== 3.10 AWS Connection ==
763 763  
764 764  
765 765  Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
... ... @@ -881,7 +881,6 @@
881 881  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
882 882  1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
883 883  
884 -
885 885  == 6.2 Why the uplink JSON format is not standard? ==
886 886  
887 887  

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0