Wiki source code of PS-CB-NA -- NB-IoT/LTE-M Analog Sensor User Manual
Last modified by Xiaoling on 2025/06/10 09:31
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | (% aria-label="image-20230830100139-1.png image widget" contenteditable="false" role="region" tabindex="-1" %) | ||
| 4 | ((( | ||
| 5 | (% data-widget="image" style="text-align:center;" %) | ||
| 6 | [[image:image-20230830100139-1.png||height="496" width="315"]](% title="Click and drag to resize" %) | ||
| 7 | |||
| 8 | (% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
| 9 | ))) | ||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | |||
| 17 | **Table of Contents:** | ||
| 18 | |||
| 19 | (% aria-label="macro:toc widget" contenteditable="false" role="region" tabindex="-1" %) | ||
| 20 | ((( | ||
| 21 | {{toc/}} | ||
| 22 | |||
| 23 | (% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
| 24 | ))) | ||
| 25 | |||
| 26 | |||
| 27 | |||
| 28 | |||
| 29 | |||
| 30 | |||
| 31 | = 1. Introduction = | ||
| 32 | |||
| 33 | == 1.1 What is NB-IoT/LTE-M Analog Sensor == | ||
| 34 | |||
| 35 | |||
| 36 | The Dragino PS-CB-NA is a (% style="color:blue" %)**NB-IoT/LTE-M Analog Sensor**(%%) for Internet of Things solution. PS-CB-NA has 5v and 12v output, 4~~20mA, 0~~30v input interface to power and get value from Analog Sensor. PS-CB-NA will convert the Analog Value to NB-IoT wireless data and send to IoT platform via NB-IoT network. | ||
| 37 | |||
| 38 | PS-CB-NA supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP, TCP or CoAP**(%%) for different application requirement, and support uplinks to various IoT Servers. | ||
| 39 | |||
| 40 | PS-CB-NA (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use. | ||
| 41 | |||
| 42 | PS-CB-NA is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years. | ||
| 43 | |||
| 44 | PS-CB-NA has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. | ||
| 45 | |||
| 46 | |||
| 47 | == 1.2 Features == | ||
| 48 | |||
| 49 | |||
| 50 | * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 | ||
| 51 | * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85 | ||
| 52 | * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 | ||
| 53 | * Ultra-low power consumption | ||
| 54 | * 1 x 0~~20mA input , 1 x 0~~30v input | ||
| 55 | * 5v and 12v output to power external sensor | ||
| 56 | * Multiply Sampling and one uplink | ||
| 57 | * GNSS for Location Report | ||
| 58 | * Support Bluetooth v5.1 remote configure and update firmware | ||
| 59 | * Uplink on periodically | ||
| 60 | * Downlink to change configure | ||
| 61 | * 8500mAh Battery for long term use | ||
| 62 | * IP66 Waterproof Enclosure | ||
| 63 | * Uplink via MQTT, MQTTs, TCP, or UDP | ||
| 64 | * Nano SIM card slot for NB-IoT SIM | ||
| 65 | |||
| 66 | == 1.3 Specification == | ||
| 67 | |||
| 68 | |||
| 69 | (% style="color:blue" %)**Common DC Characteristics:** | ||
| 70 | |||
| 71 | * Supply Voltage: 2.6v ~~ 3.6v | ||
| 72 | * Operating Temperature: -40 ~~ 85°C | ||
| 73 | |||
| 74 | (% style="color:blue" %)**Current Input (DC) Measuring :** | ||
| 75 | |||
| 76 | * Range: 0 ~~ 20mA | ||
| 77 | * Accuracy: 0.02mA | ||
| 78 | * Resolution: 0.001mA | ||
| 79 | |||
| 80 | (% style="color:blue" %)**Voltage Input Measuring:** | ||
| 81 | |||
| 82 | * Range: 0 ~~ 30v | ||
| 83 | * Accuracy: 0.02v | ||
| 84 | * Resolution: 0.001v | ||
| 85 | |||
| 86 | (% style="color:blue" %)**NB-IoT Spec:** | ||
| 87 | |||
| 88 | (% style="color:#037691" %)**NB-IoT Module: BG95-NGFF** | ||
| 89 | |||
| 90 | (% style="color:#037691" %)**Support Bands:** | ||
| 91 | |||
| 92 | * B1 @H-FDD: 2100MHz | ||
| 93 | * B2 @H-FDD: 1900MHz | ||
| 94 | * B3 @H-FDD: 1800MHz | ||
| 95 | * B4 @H-FDD: 2100MHz | ||
| 96 | * B5 @H-FDD: 860MHz | ||
| 97 | * B8 @H-FDD: 900MHz | ||
| 98 | * B12 @H-FDD: 720MHz | ||
| 99 | * B13 @H-FDD: 740MHz | ||
| 100 | * B17 @H-FDD: 730MHz | ||
| 101 | * B18 @H-FDD: 870MHz | ||
| 102 | * B19 @H-FDD: 870MHz | ||
| 103 | * B20 @H-FDD: 790MHz | ||
| 104 | * B25 @H-FDD: 1900MHz | ||
| 105 | * B28 @H-FDD: 750MHz | ||
| 106 | * B66 @H-FDD: 2000MHz | ||
| 107 | * B70 @H-FDD: 2000MHz | ||
| 108 | * B85 @H-FDD: 700MHz | ||
| 109 | |||
| 110 | (% style="color:blue" %)**Battery:** | ||
| 111 | |||
| 112 | * Li/SOCI2 un-chargeable battery | ||
| 113 | * Capacity: 8500mAh | ||
| 114 | * Self Discharge: <1% / Year @ 25°C | ||
| 115 | * Max continuously current: 130mA | ||
| 116 | * Max boost current: 2A, 1 second | ||
| 117 | |||
| 118 | (% style="color:blue" %)**Power Consumption** | ||
| 119 | |||
| 120 | * STOP Mode: 10uA @ 3.3v | ||
| 121 | * Max transmit power: 350mA@3.3v | ||
| 122 | |||
| 123 | == 1.4 Applications == | ||
| 124 | |||
| 125 | |||
| 126 | * Smart Buildings & Home Automation | ||
| 127 | * Logistics and Supply Chain Management | ||
| 128 | * Smart Metering | ||
| 129 | * Smart Agriculture | ||
| 130 | * Smart Cities | ||
| 131 | * Smart Factory | ||
| 132 | |||
| 133 | == 1.5 Sleep mode and working mode == | ||
| 134 | |||
| 135 | |||
| 136 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life. | ||
| 137 | |||
| 138 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode. | ||
| 139 | |||
| 140 | |||
| 141 | == 1.6 Button & LEDs == | ||
| 142 | |||
| 143 | |||
| 144 | (% aria-label="1675071855856-879.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]](% title="Click and drag to resize" %) | ||
| 145 | |||
| 146 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 147 | |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:226px;background-color:#4F81BD;color:white" %)**Action** | ||
| 148 | |[[image:1749519094236-908.png]] 1~~3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
| 149 | If sensor has already attached to NB-IoT/CAT-M1 network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
| 150 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
| 151 | ))) | ||
| 152 | |[[image:1749519099973-281.png]] >3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
| 153 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT/CAT-M1 network. | ||
| 154 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT/CAT-M1 network or not. | ||
| 155 | ))) | ||
| 156 | |[[image:1749519064321-472.png]] x5|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode. | ||
| 157 | |||
| 158 | (% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.** | ||
| 159 | |||
| 160 | |||
| 161 | == 1.7 BLE connection == | ||
| 162 | |||
| 163 | |||
| 164 | PS-CB-NA support BLE remote configure and firmware update. | ||
| 165 | |||
| 166 | |||
| 167 | BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case: | ||
| 168 | |||
| 169 | * Press button to send an uplink | ||
| 170 | * Press button to active device. | ||
| 171 | * Device Power on or reset. | ||
| 172 | |||
| 173 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
| 174 | |||
| 175 | |||
| 176 | == 1.8 Pin Definitions , Switch & SIM Direction == | ||
| 177 | |||
| 178 | |||
| 179 | PS-CB-NA use the mother board which as below. | ||
| 180 | |||
| 181 | (% aria-label="image-20240730143319-1.jpeg image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240730143319-1.jpeg||height="451" width="686"]](% style="background:url(~"https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png~") rgba(220, 220, 220, 0.5); left:0px; top:-15px" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 182 | |||
| 183 | |||
| 184 | === 1.8.1 Jumper JP2 === | ||
| 185 | |||
| 186 | |||
| 187 | Power on Device when put this jumper. | ||
| 188 | |||
| 189 | |||
| 190 | === 1.8.2 BOOT MODE / SW1 === | ||
| 191 | |||
| 192 | |||
| 193 | **1)** (% style="color:blue" %)**ISP**(%%): upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. | ||
| 194 | |||
| 195 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
| 196 | |||
| 197 | |||
| 198 | === 1.8.3 Reset Button === | ||
| 199 | |||
| 200 | |||
| 201 | Press to reboot the device. | ||
| 202 | |||
| 203 | |||
| 204 | === 1.8.4 SIM Card Direction === | ||
| 205 | |||
| 206 | |||
| 207 | See this link. [[How to insert SIM Card>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]]. | ||
| 208 | |||
| 209 | |||
| 210 | == 1.9 Mechanical == | ||
| 211 | |||
| 212 | |||
| 213 | [[image:image-20250415140025-1.jpeg]] | ||
| 214 | |||
| 215 | |||
| 216 | = 2. Use PS-CB-NA to communicate with IoT Server = | ||
| 217 | |||
| 218 | == 2.1 Send data to IoT server via NB-IoT/CAT-M1 network == | ||
| 219 | |||
| 220 | |||
| 221 | The PS-CB-NA is equipped with a NB-IoT module, the pre-loaded firmware in PS-CB-NA will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by PS-CB-NA. | ||
| 222 | |||
| 223 | Below shows the network structure: | ||
| 224 | |||
| 225 | [[image:image-20250117165220-1.png]](% title="Click and drag to resize" %) | ||
| 226 | |||
| 227 | |||
| 228 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of PS-CB-NA. | ||
| 229 | |||
| 230 | (% style="color:blue" %)**GE Version**(%%): This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set PS-CB-NA send data to IoT server. | ||
| 231 | |||
| 232 | * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H2.AttachNetwork]]. | ||
| 233 | |||
| 234 | * Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H3.Configuretoconnecttodifferentservers]]. | ||
| 235 | |||
| 236 | Below shows result of different server as a glance. | ||
| 237 | |||
| 238 | (% border="1" cellspacing="3" style="width:515px" %) | ||
| 239 | |(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments** | ||
| 240 | |(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
| 241 | (% aria-label="image-20230819113244-8.png image widget" contenteditable="false" role="region" tabindex="-1" %) | ||
| 242 | ((( | ||
| 243 | (% data-widget="image" style="text-align:center;" %) | ||
| 244 | [[image:image-20230819113244-8.png||height="183" width="367"]](% title="Click and drag to resize" %) | ||
| 245 | |||
| 246 | (% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
| 247 | ))) | ||
| 248 | )))|(% style="width:170px" %) | ||
| 249 | |(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)((( | ||
| 250 | (% aria-label="image-20230819113244-9.png image widget" contenteditable="false" role="region" tabindex="-1" %) | ||
| 251 | ((( | ||
| 252 | (% data-widget="image" style="text-align:center;" %) | ||
| 253 | [[image:image-20230819113244-9.png||height="119" width="367"]](% title="Click and drag to resize" %) | ||
| 254 | |||
| 255 | (% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
| 256 | ))) | ||
| 257 | )))|(% style="width:170px" %) | ||
| 258 | |(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %) | ||
| 259 | |(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
| 260 | |(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %) | ||
| 261 | |(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
| 262 | (% aria-label="image-20230819113244-10.png image widget" contenteditable="false" role="region" tabindex="-1" %) | ||
| 263 | ((( | ||
| 264 | (% data-widget="image" style="text-align:center;" %) | ||
| 265 | [[image:image-20230819113244-10.png||height="104" width="367"]](% title="Click and drag to resize" %) | ||
| 266 | |||
| 267 | (% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
| 268 | ))) | ||
| 269 | )))|(% style="width:170px" %) | ||
| 270 | |(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)((( | ||
| 271 | (% aria-label="image-20230819113244-11.png image widget" contenteditable="false" role="region" tabindex="-1" %) | ||
| 272 | ((( | ||
| 273 | (% data-widget="image" style="text-align:center;" %) | ||
| 274 | [[image:image-20230819113244-11.png||height="141" width="367"]](% title="Click and drag to resize" %) | ||
| 275 | |||
| 276 | (% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
| 277 | ))) | ||
| 278 | )))|(% style="width:170px" %) | ||
| 279 | |||
| 280 | (% style="color:blue" %)**1T Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate PS-CB-NA and user will be able to see data in ThingsEye. See here for [[ThingsEye Config Instruction>>url:https://wiki.thingseye.io/xwiki/bin/view/Main/]]. | ||
| 281 | |||
| 282 | |||
| 283 | == 2.2 Payload Types == | ||
| 284 | |||
| 285 | |||
| 286 | To meet different server requirement, PS-CB-NA supports different payload type. | ||
| 287 | |||
| 288 | **Includes:** | ||
| 289 | |||
| 290 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
| 291 | |||
| 292 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
| 293 | |||
| 294 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
| 295 | |||
| 296 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
| 297 | |||
| 298 | User can specify the payload type when choose the connection protocol. Example: | ||
| 299 | |||
| 300 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
| 301 | |||
| 302 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
| 303 | |||
| 304 | (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Use MQTT Connection & hex Payload | ||
| 305 | |||
| 306 | (% style="color:#037691" %)**AT+PRO=3,1 **(%%)~/~/ Use MQTT Connection & ThingSpeak | ||
| 307 | |||
| 308 | (% style="color:#037691" %)**AT+PRO=3,3 **(%%)~/~/ Use MQTT Connection & ThingsBoard | ||
| 309 | |||
| 310 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
| 311 | |||
| 312 | (% style="color:#037691" %)**AT+PRO=4,0** (%%) ~/~/ Use TCP Connection & hex Payload | ||
| 313 | |||
| 314 | (% style="color:#037691" %)**AT+PRO=4,5** (%%) ~/~/ Use TCP Connection & Json Payload | ||
| 315 | |||
| 316 | |||
| 317 | === 2.2.1 General Json Format(Type~=5) === | ||
| 318 | |||
| 319 | |||
| 320 | This is the General Json Format. As below: | ||
| 321 | |||
| 322 | (% style="color:#4472c4" %)**{"IMEI":"864370064394515","Model":"PS-CB","idc_intput":3.896,"vdc_intput":0.000,"battery":3.649,"signal":24,"latitude":22.706230,"longitude":114.242650,"gps_time":"2024-07-26T03:10:15Z","1":[3.895,0.000,"2024-07-26T02:55:34Z"],"2":[2.509,3.639,"2024-07-25T07:50:36Z"],"3":[2.509,3.639,"2024-07-25T07:49:36Z"],"4":[2.509,3.640,"2024-07-25T07:48:36Z"],"5":[2.509,3.639,"2024-07-25T07:47:36Z"],"6":[2.509,3.640,"2024-07-25T07:46:36Z"],"7":[2.509,3.640,"2024-07-25T07:45:36Z"],"8":[2.509,3.640,"2024-07-25T07:44:36Z"]}** | ||
| 323 | |||
| 324 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CB sensor uplink data. | ||
| 325 | |||
| 326 | (% aria-label="image-20240726111821-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726111821-1.png||height="769" width="922"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 327 | |||
| 328 | (% style="color:red" %)**Notice, from above payload:** | ||
| 329 | |||
| 330 | * Idc_input , Vdc_input , Battery & Signal are the value at uplink time. | ||
| 331 | |||
| 332 | * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+CLOCKLOG=1,65535,15,8 ** (%%)Command. Each entry includes (from left to right): Idc_input , Vdc_input, Sampling time. | ||
| 333 | |||
| 334 | === 2.2.2 HEX format Payload(Type~=0) === | ||
| 335 | |||
| 336 | |||
| 337 | This is the HEX Format. As below: | ||
| 338 | |||
| 339 | (% style="color:#4472c4" %)**f86437006439451546660e1719000000000000000000000000000066a316940f38000066a316940f37000066a3102609cd0e3766a203cc09cd0e3766a2039009cd0e3866a2035409cd0e3766a2031809cd0e3866a202dc09cd0e3866a202a009cd0e3866a20264** | ||
| 340 | |||
| 341 | (% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]][[image:image-20250117155304-1.png]](% title="Click and drag to resize" %)[[image:image-20250117155406-1.png]] | ||
| 342 | |||
| 343 | If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CB sensor uplink data. | ||
| 344 | |||
| 345 | (% aria-label="image-20240726112727-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726112727-2.png||height="801" width="956"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 346 | |||
| 347 | |||
| 348 | (% style="color:blue" %)**Version:** | ||
| 349 | |||
| 350 | These bytes include the hardware and software version. | ||
| 351 | |||
| 352 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x46 for PS-CB-NA | ||
| 353 | |||
| 354 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x66=102, means firmware version 1.0.2 | ||
| 355 | |||
| 356 | |||
| 357 | (% style="color:blue" %)**BAT (Battery Info):** | ||
| 358 | |||
| 359 | Check the battery voltage for PS-CB-NA. | ||
| 360 | |||
| 361 | Ex1: 0x0dde = 3550mV | ||
| 362 | |||
| 363 | Ex2: 0x0B49 = 2889mV | ||
| 364 | |||
| 365 | |||
| 366 | (% style="color:blue" %)**Signal Strength:** | ||
| 367 | |||
| 368 | NB-IoT Network signal Strength. | ||
| 369 | |||
| 370 | **Ex1: 0x13 = 19** | ||
| 371 | |||
| 372 | **0** -113dBm or less | ||
| 373 | |||
| 374 | **1** -111dBm | ||
| 375 | |||
| 376 | **2...30** -109dBm... -53dBm | ||
| 377 | |||
| 378 | **31** -51dBm or greater | ||
| 379 | |||
| 380 | **99** Not known or not detectable | ||
| 381 | |||
| 382 | |||
| 383 | (% style="color:blue" %)**Probe Model:** | ||
| 384 | |||
| 385 | PS-CB-NA might connect to different kind of probes, 4~~20mA represent the full scale of the measuring range. So a 12mA output means different meaning for different probe. | ||
| 386 | |||
| 387 | **For example.** | ||
| 388 | |||
| 389 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %) | ||
| 390 | |(% style="background-color:#4f81bd; color:white; width:150px" %)**Probe Type**|(% style="background-color:#4f81bd; color:white; width:150px" %)**4~~20mA scale for this probe**|(% style="background-color:#4f81bd; color:white; width:200px" %)**Example: 12mA actually meaning for this probe** | ||
| 391 | |(% style="background-color:#f2f2f2; width:206px" %)PH Combination Electrodes|(% style="background-color:#f2f2f2; width:222px" %)0 ~~ 14 pH|(% style="background-color:#f2f2f2; width:356px" %)PH Value: 7 | ||
| 392 | |(% style="background-color:#f2f2f2; width:206px" %)Water Pressure Sensor|(% style="background-color:#f2f2f2; width:222px" %)0~~5 meters|(% style="background-color:#f2f2f2; width:356px" %)2.5 meters pure water | ||
| 393 | |(% style="background-color:#f2f2f2; width:206px" %)Pressure transmitter probe|(% style="background-color:#f2f2f2; width:222px" %)0~~1MPa|(% style="background-color:#f2f2f2; width:356px" %)0.5MPa air / gas or water pressure | ||
| 394 | |||
| 395 | User can set different probe model for above probes. So IoT server is able to se identical how it should parse the 4~~20mA or 0~~30v sensor value and get the correct value. | ||
| 396 | |||
| 397 | |||
| 398 | (% style="color:blue" %)**IN1 & IN2: ** | ||
| 399 | |||
| 400 | IN1 and IN2 are used as Digital input pins. | ||
| 401 | |||
| 402 | (% style="color:#037691" %)**Example**: | ||
| 403 | |||
| 404 | 01 (H): IN1 or IN2 pin is high level. | ||
| 405 | |||
| 406 | 00 (L): IN1 or IN2 pin is low level.(% style="color:blue" %)** ** | ||
| 407 | |||
| 408 | |||
| 409 | (% style="color:blue" %)**GPIO_EXTI Level:** | ||
| 410 | |||
| 411 | GPIO_EXTI is used as Interrupt Pin. | ||
| 412 | |||
| 413 | (% style="color:#037691" %)**Example**: | ||
| 414 | |||
| 415 | 01 (H): GPIO_EXTI pin is high level. | ||
| 416 | |||
| 417 | 00 (L): GPIO_EXTI pin is low level. | ||
| 418 | |||
| 419 | |||
| 420 | (% style="color:blue" %)**GPIO_EXTI Flag:** | ||
| 421 | |||
| 422 | This data field shows if this packet is generated by (% style="color:blue" %)**Interrupt Pin** (%%)or not. | ||
| 423 | |||
| 424 | Note: The Interrupt Pin is a separate pin in the screw terminal. | ||
| 425 | |||
| 426 | (% style="color:#037691" %)**Example:** | ||
| 427 | |||
| 428 | 0x00: Normal uplink packet. | ||
| 429 | |||
| 430 | 0x01: Interrupt Uplink Packet. | ||
| 431 | |||
| 432 | |||
| 433 | (% style="color:blue" %)**Latitude:** | ||
| 434 | |||
| 435 | EX1:** **0x00000000 ~/~/ Locating fails or is not enabled. | ||
| 436 | |||
| 437 | EX2:** **0x015a771e(H)=22705950(D)=22.705950 | ||
| 438 | |||
| 439 | |||
| 440 | (% style="color:blue" %)**Longitude:** | ||
| 441 | |||
| 442 | EX1:** **0x00000000 ~/~/ Locating fails or is not enabled. | ||
| 443 | |||
| 444 | EX2:** **0x114242500(H)=114242500(D)=114.242500 | ||
| 445 | |||
| 446 | |||
| 447 | (% style="color:blue" %)**GPS_Timestamp:** | ||
| 448 | |||
| 449 | EX1: 0x00000000 ~/~/ The value is "1970-01-01T00:00:00Z" in JSON format. The initial GPS time is not refreshed if GPS positioning is disabled or fails. | ||
| 450 | |||
| 451 | EX2: 0x6682595d =1719818589 = 2024-07-01 15:23:09 | ||
| 452 | |||
| 453 | |||
| 454 | (% style="color:blue" %)**0~~20mA:** | ||
| 455 | |||
| 456 | (% style="color:#037691" %)**Example**: | ||
| 457 | |||
| 458 | 27AE(H) = 10158 (D)/1000 = 10.158mA. | ||
| 459 | |||
| 460 | (% aria-label="image-20230904112121-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20230904112121-3.png||height="219" width="552"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 461 | |||
| 462 | **Connect to a 2 wire 4~~20mA sensor.** | ||
| 463 | |||
| 464 | (% aria-label="image-20240730150222-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240730150222-2.png||height="307" width="563"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 465 | |||
| 466 | |||
| 467 | (% style="color:blue" %)**0~~30V:** | ||
| 468 | |||
| 469 | Measure the voltage value. The range is 0 to 30V. | ||
| 470 | |||
| 471 | (% style="color:#037691" %)**Example**: | ||
| 472 | |||
| 473 | 138E(H) = 5006(D)/1000= 5.006V | ||
| 474 | |||
| 475 | |||
| 476 | (% style="color:blue" %)**TimeStamp:** | ||
| 477 | |||
| 478 | Unit TimeStamp Example: 66A31694(H) = 1721964180(D) | ||
| 479 | |||
| 480 | Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]])to get the time. | ||
| 481 | |||
| 482 | |||
| 483 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
| 484 | |||
| 485 | |||
| 486 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
| 487 | |||
| 488 | (% style="color:blue" %)**{ | ||
| 489 | "topic": "CB_PUB", | ||
| 490 | "payload": { | ||
| 491 | "IMEI": "864370064394515", | ||
| 492 | "Model": "PS-CB", | ||
| 493 | "idc_intput": 3.895, | ||
| 494 | "vdc_intput": 0.0, | ||
| 495 | "battery": 3.529, | ||
| 496 | "signal": 26, | ||
| 497 | "latitude": 0.0, | ||
| 498 | "longitude": 0.0, | ||
| 499 | "gps_time": "1970-01-01T00:00:00Z", | ||
| 500 | "1": [3.895, 0.0, "2024-07-26T03:40:43Z"], | ||
| 501 | "2": [3.895, 0.0, "2024-07-26T03:39:43Z"], | ||
| 502 | "3": [3.895, 0.0, "2024-07-26T03:38:43Z"], | ||
| 503 | "4": [3.894, 0.0, "2024-07-26T03:34:32Z"], | ||
| 504 | "5": [3.895, 0.0, "2024-07-26T02:55:34Z"], | ||
| 505 | "6": [2.509, 3.639, "2024-07-25T07:50:36Z"], | ||
| 506 | "7": [2.509, 3.639, "2024-07-25T07:49:36Z"], | ||
| 507 | "8": [2.509, 3.64, "2024-07-25T07:48:36Z"] | ||
| 508 | } | ||
| 509 | }** | ||
| 510 | |||
| 511 | (% aria-label="image-20240726114549-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726114549-3.png||height="610" width="1222"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 512 | |||
| 513 | |||
| 514 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
| 515 | |||
| 516 | |||
| 517 | This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~6 are: | ||
| 518 | |||
| 519 | Idc_input , Vdc_input , Battery, Signal, Interrupt & Interrupt level. This payload type only valid for ThingsSpeak Platform | ||
| 520 | |||
| 521 | As below: | ||
| 522 | |||
| 523 | (% style="color:blue" %)**field1=idc_intput value&field2=vdc_intput value&field3=battery value&field4=signal value&field5=Interrupt value&field6=Interrupt_level value** | ||
| 524 | |||
| 525 | (% aria-label="image-20240726140736-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726140736-4.png||height="872" width="900"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 526 | |||
| 527 | |||
| 528 | = 3. Configure PS-CB-NA = | ||
| 529 | |||
| 530 | == 3.1 Configure Methods == | ||
| 531 | |||
| 532 | |||
| 533 | PS-CB-NA supports below configure method: | ||
| 534 | |||
| 535 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
| 536 | |||
| 537 | * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]. | ||
| 538 | |||
| 539 | == 3.2 Serial Access Password == | ||
| 540 | |||
| 541 | |||
| 542 | After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window. | ||
| 543 | |||
| 544 | The label on the box of the node will print the initial password: AT+PIN=**xxxxxx**, and directly use the six-digit password to access the AT instruction window. | ||
| 545 | |||
| 546 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-NB%2C-NS_RS485%2CUART_to_NB-IoT_Converter_User_Manual/WebHome/image-20250226165815-1.png?rev=1.1||alt="image-20250226165815-1.png"]](% title="Click and drag to resize" %) | ||
| 547 | |||
| 548 | |||
| 549 | If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), CB nodes only support lowercase letters. | ||
| 550 | |||
| 551 | (% aria-label="image-20240826180612-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240826180612-2.png]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 552 | |||
| 553 | |||
| 554 | (% style="color:red" %)**Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.** | ||
| 555 | |||
| 556 | (% aria-label="image-20240826180617-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240826180617-3.png]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 557 | |||
| 558 | |||
| 559 | == 3.3 AT Commands Set == | ||
| 560 | |||
| 561 | |||
| 562 | AT+<CMD>? : Help on <CMD> | ||
| 563 | |||
| 564 | AT+<CMD> : Run <CMD> | ||
| 565 | |||
| 566 | AT+<CMD>=<value> : Set the value | ||
| 567 | |||
| 568 | AT+<CMD>=? : Get the value | ||
| 569 | |||
| 570 | |||
| 571 | (% style="color:blue" %)**General Commands** | ||
| 572 | |||
| 573 | AT : Attention | ||
| 574 | |||
| 575 | AT? : Short Help | ||
| 576 | |||
| 577 | AT+MODEL : Get module information | ||
| 578 | |||
| 579 | ATZ : Trig a reset of the MCU | ||
| 580 | |||
| 581 | AT+DEUI : Get or set the Device ID | ||
| 582 | |||
| 583 | AT+SLEEP : Get or set the sleep status | ||
| 584 | |||
| 585 | AT+DEBUG : Set more info output | ||
| 586 | |||
| 587 | AT+CFG : Print all settings | ||
| 588 | |||
| 589 | AT+SERVADDR: Get or Set the Server address | ||
| 590 | |||
| 591 | AT+TDC : Get or set the application data transmission interval in s | ||
| 592 | |||
| 593 | AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising) | ||
| 594 | |||
| 595 | AT+APN : Get or set the APN | ||
| 596 | |||
| 597 | AT+3V3T : Get or Set extend the time of 3V3 power | ||
| 598 | |||
| 599 | AT+5VT : Get or Set extend the time of 5V power | ||
| 600 | |||
| 601 | AT+12VT : Get or Set extend the time of 12V power | ||
| 602 | |||
| 603 | AT+PROBE : Get or Set the probe model | ||
| 604 | |||
| 605 | AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP) | ||
| 606 | |||
| 607 | AT+RXDL : Get or Set the receiving time | ||
| 608 | |||
| 609 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
| 610 | |||
| 611 | AT+DNSCFG : Get or Set DNS Server | ||
| 612 | |||
| 613 | AT+CSQTIME : Get or Set the time to join the network | ||
| 614 | |||
| 615 | AT+GDNS : Get or Set the DNS | ||
| 616 | |||
| 617 | AT+TLSMOD : Get or Set the TLS mode | ||
| 618 | |||
| 619 | AT+IPTYPE : Set the IPv4 or IPv6 | ||
| 620 | |||
| 621 | AT+QSW : Power on and power off BG95 module | ||
| 622 | |||
| 623 | AT+CLOCKLOG: Enable or Disable Clock Logging | ||
| 624 | |||
| 625 | AT+TIMESTAMP : Get or Set UNIX timestamp in second | ||
| 626 | |||
| 627 | AT+GETLOG : Print serial port logs | ||
| 628 | |||
| 629 | |||
| 630 | (% style="color:blue" %)**MQTT Management** | ||
| 631 | |||
| 632 | AT+CLIENT : Get or Set the MQTT clientID | ||
| 633 | |||
| 634 | AT+UNAME : Get or Set the MQTT Username | ||
| 635 | |||
| 636 | AT+PWD : Get or Set the MQTT password | ||
| 637 | |||
| 638 | AT+PUBTOPIC: Get or set MQTT publishing topic | ||
| 639 | |||
| 640 | AT+SUBTOPIC: Get or set MQTT subscription topic | ||
| 641 | |||
| 642 | AT+MQOS : Set the QoS level of MQTT | ||
| 643 | |||
| 644 | |||
| 645 | (% style="color:blue" %)**Coap Management** | ||
| 646 | |||
| 647 | AT+URI1: Get or set CoAP option 1 | ||
| 648 | |||
| 649 | AT+URI2: Get or set CoAP option 2 | ||
| 650 | |||
| 651 | AT+URI3: Get or set CoAP option 3 | ||
| 652 | |||
| 653 | AT+URI4: Get or set CoAP option 4 | ||
| 654 | |||
| 655 | AT+URI5: Get or set CoAP option 5 | ||
| 656 | |||
| 657 | AT+URI6: Get or set CoAP option 6 | ||
| 658 | |||
| 659 | AT+URI7: Get or set CoAP option 7 | ||
| 660 | |||
| 661 | AT+URI8: Get or set CoAP option 8 | ||
| 662 | |||
| 663 | |||
| 664 | (% style="color:blue" %)**GPS** | ||
| 665 | |||
| 666 | AT+GNSST : Extend the time to turn on GNSS | ||
| 667 | |||
| 668 | AT+GPS : Turn off and on GPS | ||
| 669 | |||
| 670 | AT+GTDC : Get or set GPS positioning interval in units of h | ||
| 671 | |||
| 672 | |||
| 673 | (% style="color:blue" %)**Information** | ||
| 674 | |||
| 675 | AT+FDR1 : Reset parameters to factory default values except for passwords | ||
| 676 | |||
| 677 | AT+FDR : Reset Parameters to Factory Default | ||
| 678 | |||
| 679 | AT+PWORD : Get or set the System password | ||
| 680 | |||
| 681 | AT+CDP : Read or Clear cached data | ||
| 682 | |||
| 683 | AT+LDATA : Get the last upload data | ||
| 684 | |||
| 685 | |||
| 686 | == 3.4 Trggier an uplink by external interrupt == | ||
| 687 | |||
| 688 | |||
| 689 | PS-CB-NA has an external trigger interrupt function. Users can use the GPIO_EXTI pin to trigger the upload of data packets. | ||
| 690 | |||
| 691 | (% style="color:blue" %)**AT command:** | ||
| 692 | |||
| 693 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
| 694 | |||
| 695 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt,as a digital input pin | ||
| 696 | |||
| 697 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
| 698 | |||
| 699 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
| 700 | |||
| 701 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
| 702 | |||
| 703 | (% style="color:blue" %)**Downlink Command: 0x06** | ||
| 704 | |||
| 705 | Format: Command Code (0x06) followed by 3 bytes. | ||
| 706 | |||
| 707 | This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. | ||
| 708 | |||
| 709 | * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode | ||
| 710 | * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger | ||
| 711 | |||
| 712 | == 3.5 Set Power Output Duration == | ||
| 713 | |||
| 714 | |||
| 715 | Control the output duration 3V3 , 5V or 12V. Before each sampling, device will | ||
| 716 | |||
| 717 | ~1. first enable the power output to external sensor, | ||
| 718 | |||
| 719 | 2. keep it on as per duration, read sensor value and construct uplink payload | ||
| 720 | |||
| 721 | 3. final, close the power output. | ||
| 722 | |||
| 723 | |||
| 724 | (% style="color:blue" %)**AT Command: AT+3V3T** | ||
| 725 | |||
| 726 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:471px" %) | ||
| 727 | |=(% style="width: 154px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 201px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 116px;background-color:#4F81BD;color:white" %)**Response** | ||
| 728 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=?|(% style="background-color:#f2f2f2; width:201px" %)Show 3V3 open time.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 729 | 0 | ||
| 730 | OK | ||
| 731 | ))) | ||
| 732 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=0|(% style="background-color:#f2f2f2; width:201px" %)Normally open 3V3 power supply.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 733 | OK | ||
| 734 | default setting | ||
| 735 | ))) | ||
| 736 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=1000|(% style="background-color:#f2f2f2; width:201px" %)Close after a delay of 1000 milliseconds.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 737 | OK | ||
| 738 | ))) | ||
| 739 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=65535|(% style="background-color:#f2f2f2; width:201px" %)Normally closed 3V3 power supply.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 740 | OK | ||
| 741 | ))) | ||
| 742 | |||
| 743 | (% style="color:blue" %)**AT Command: AT+5VT** | ||
| 744 | |||
| 745 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:465px" %) | ||
| 746 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 196px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 114px;background-color:#4F81BD;color:white" %)**Response** | ||
| 747 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=?|(% style="background-color:#f2f2f2; width:196px" %)Show 5V open time.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 748 | 0 | ||
| 749 | OK | ||
| 750 | ))) | ||
| 751 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=0|(% style="background-color:#f2f2f2; width:196px" %)Normally closed 5V power supply.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 752 | OK | ||
| 753 | default setting | ||
| 754 | ))) | ||
| 755 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=1000|(% style="background-color:#f2f2f2; width:196px" %)Close after a delay of 1000 milliseconds.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 756 | OK | ||
| 757 | ))) | ||
| 758 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=65535|(% style="background-color:#f2f2f2; width:196px" %)Normally open 5V power supply.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 759 | OK | ||
| 760 | ))) | ||
| 761 | |||
| 762 | (% style="color:blue" %)**AT Command: AT+12VT** | ||
| 763 | |||
| 764 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:438px" %) | ||
| 765 | |=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 199px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 83px;background-color:#4F81BD;color:white" %)**Response** | ||
| 766 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=?|(% style="background-color:#f2f2f2; width:199px" %)Show 12V open time.|(% style="background-color:#f2f2f2; width:83px" %)((( | ||
| 767 | 0 | ||
| 768 | OK | ||
| 769 | ))) | ||
| 770 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=0|(% style="background-color:#f2f2f2; width:199px" %)Normally closed 12V power supply.|(% style="background-color:#f2f2f2; width:83px" %)OK | ||
| 771 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=500|(% style="background-color:#f2f2f2; width:199px" %)Close after a delay of 500 milliseconds.|(% style="background-color:#f2f2f2; width:83px" %)((( | ||
| 772 | OK | ||
| 773 | ))) | ||
| 774 | |||
| 775 | (% style="color:blue" %)**Downlink Command: 0x07** | ||
| 776 | |||
| 777 | Format: Command Code (0x07) followed by 3 bytes. | ||
| 778 | |||
| 779 | The first byte is which power, the second and third bytes are the time to turn on. | ||
| 780 | |||
| 781 | * Example 1: Downlink Payload: 070101F4 **~-~-->** AT+3V3T=500 | ||
| 782 | * Example 2: Downlink Payload: 0701FFFF **~-~-->** AT+3V3T=65535 | ||
| 783 | * Example 3: Downlink Payload: 070203E8 **~-~-->** AT+5VT=1000 | ||
| 784 | * Example 4: Downlink Payload: 07020000 **~-~-->** AT+5VT=0 | ||
| 785 | * Example 5: Downlink Payload: 070301F4 **~-~-->** AT+12VT=500 | ||
| 786 | * Example 6: Downlink Payload: 07030000 **~-~-->** AT+12VT=0 | ||
| 787 | |||
| 788 | == 3.6 Set the Probe Model == | ||
| 789 | |||
| 790 | |||
| 791 | Users need to configure this parameter according to the type of external probe. In this way, the server can decode according to this value, and convert the current value output by the sensor into water depth or pressure value. | ||
| 792 | |||
| 793 | (% style="color:blue" %)**AT Command: AT** **+PROBE** | ||
| 794 | |||
| 795 | AT+PROBE=aabb | ||
| 796 | |||
| 797 | When aa=00, it is the water depth mode, and the current is converted into the water depth value; bb is the probe at a depth of several meters. | ||
| 798 | |||
| 799 | When aa=01, it is the pressure mode, which converts the current into a pressure value; | ||
| 800 | |||
| 801 | bb represents which type of pressure sensor it is. | ||
| 802 | |||
| 803 | (A->01,B->02,C->03,D->04,E->05,F->06,G->07,H->08,I->09,J->0A,K->0B,L->0C) | ||
| 804 | |||
| 805 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 806 | |(% style="background-color:#4f81bd; color:white; width:154px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:269px" %)**Function**|(% style="background-color:#4f81bd; color:white" %)**Response** | ||
| 807 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =?|(% style="background-color:#f2f2f2; width:269px" %)Get or Set the probe model.|(% style="background-color:#f2f2f2" %)0 | ||
| 808 | OK | ||
| 809 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0003|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 3m type.|(% style="background-color:#f2f2f2" %)OK | ||
| 810 | |(% style="background-color:#f2f2f2; width:154px" %)((( | ||
| 811 | AT +PROBE =000A | ||
| 812 | |||
| 813 | |||
| 814 | )))|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 10m type.|(% style="background-color:#f2f2f2" %)OK | ||
| 815 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0101|(% style="background-color:#f2f2f2; width:269px" %)Set pressure transmitters mode, first type(A).|(% style="background-color:#f2f2f2" %)OK | ||
| 816 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0000|(% style="background-color:#f2f2f2; width:269px" %)Initial state, no settings.|(% style="background-color:#f2f2f2" %)OK | ||
| 817 | |||
| 818 | (% style="color:blue" %)**Downlink Command: 0x08** | ||
| 819 | |||
| 820 | Format: Command Code (0x08) followed by 2 bytes. | ||
| 821 | |||
| 822 | * Example 1: Downlink Payload: 080003 **~-~-->** AT+PROBE=0003 | ||
| 823 | * Example 2: Downlink Payload: 080101 **~-~-->** AT+PROBE=0101 | ||
| 824 | |||
| 825 | == 3.7 Multiple VDC /IDC collections in one uplink == | ||
| 826 | |||
| 827 | |||
| 828 | Added AT+STDC command to collect the voltage of **VDC_INPUT/IDC_INPUT** multiple times and upload it at one time. | ||
| 829 | |||
| 830 | (% style="color:blue" %)**AT Command: AT** **+STDC** | ||
| 831 | |||
| 832 | AT+STDC=aa,bb,bb | ||
| 833 | |||
| 834 | (% style="color:#037691" %)**aa:**(%%) | ||
| 835 | **0:** means disable this function and use TDC to send packets. | ||
| 836 | **1:** means that the function is enabled to send packets by collecting VDC data for multiple times | ||
| 837 | **2:** means that the function is enabled to send packets by collecting IDC data for multiple times | ||
| 838 | (% style="color:#037691" %)**bb:**(%%) Each collection interval (s), the value is 1~~65535 | ||
| 839 | (% style="color:#037691" %)**cc:**(%%)** **the number of collection times, the value is 1~~120 | ||
| 840 | |||
| 841 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
| 842 | |(% style="background-color:#4f81bd; color:white; width:160px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:215px" %)**Function**|(% style="background-color:#4f81bd; color:white" %)**Response** | ||
| 843 | |(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=?|(% style="background-color:#f2f2f2; width:215px" %)Get the mode of multiple acquisitions and one uplink.|(% style="background-color:#f2f2f2" %)1,10,18 | ||
| 844 | OK | ||
| 845 | |(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=1,10,18|(% style="background-color:#f2f2f2; width:215px" %)Set the mode of multiple acquisitions and one uplink, collect once every 10 seconds, and report after 18 times.|(% style="background-color:#f2f2f2" %)((( | ||
| 846 | Attention:Take effect after ATZ | ||
| 847 | |||
| 848 | OK | ||
| 849 | ))) | ||
| 850 | |(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=0, 0,0|(% style="background-color:#f2f2f2; width:215px" %)((( | ||
| 851 | Use the TDC interval to send packets.(default) | ||
| 852 | |||
| 853 | |||
| 854 | )))|(% style="background-color:#f2f2f2" %)((( | ||
| 855 | Attention:Take effect after ATZ | ||
| 856 | |||
| 857 | OK | ||
| 858 | ))) | ||
| 859 | |||
| 860 | (% style="color:blue" %)**Downlink Command: 0xAE** | ||
| 861 | |||
| 862 | Format: Command Code (0xAE) followed by 4 bytes. | ||
| 863 | |||
| 864 | * Example 1: Downlink Payload: AE 01 02 58 12** ~-~-->** AT+STDC=1,600,18 | ||
| 865 | |||
| 866 | == 3.8 Clock logging == | ||
| 867 | |||
| 868 | |||
| 869 | Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature. | ||
| 870 | |||
| 871 | We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data. | ||
| 872 | |||
| 873 | * (% style="color:blue" %)**AT Command: AT** **+CLOCKLOG=a,b,c,d** | ||
| 874 | |||
| 875 | (% style="color:blue" %)**a:**(%%)** 0:** Disable Clock logging. ** 1: **Enable Clock Logging | ||
| 876 | |||
| 877 | (% style="color:blue" %)**b:**(%%)** **Specify First sampling start second: range **(0 ~~ 3599, 65535) ** ~/~/ (% style="color:red" %)**Note:**(%%)** **If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets. | ||
| 878 | |||
| 879 | (% style="color:blue" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)** | ||
| 880 | |||
| 881 | (% style="color:blue" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)** | ||
| 882 | |||
| 883 | (% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0** | ||
| 884 | |||
| 885 | (% aria-label="image-20240408084118-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240408084118-1.png]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 886 | |||
| 887 | **Example:** | ||
| 888 | |||
| 889 | **AT+CLOCKLOG=1,65535,1,3** | ||
| 890 | |||
| 891 | After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 3 memory records (payload + timestamp). | ||
| 892 | |||
| 893 | (% class="wikigeneratedid" %) | ||
| 894 | (% aria-label="image-20240726141453-5.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726141453-5.png||height="571" width="1065"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 895 | |||
| 896 | (% class="wikigeneratedid" %) | ||
| 897 | (% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.** | ||
| 898 | |||
| 899 | |||
| 900 | == 3.9 Power on / power off BG95 module == | ||
| 901 | |||
| 902 | |||
| 903 | This command is used to power on and power off BG95 module. | ||
| 904 | |||
| 905 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+QSW(%%)** | ||
| 906 | |||
| 907 | The module is powered on after the command is sent for the first time, and powered off after the command is sent again. | ||
| 908 | |||
| 909 | (% aria-label="image-20240726141704-8.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726141704-8.png||height="612" width="809"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 910 | |||
| 911 | |||
| 912 | == 3.10 Example Query saved historical records == | ||
| 913 | |||
| 914 | |||
| 915 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)** | ||
| 916 | |||
| 917 | This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes. | ||
| 918 | |||
| 919 | (% aria-label="image-20240726141523-6.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726141523-6.png||height="608" width="808"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 920 | |||
| 921 | |||
| 922 | == 3.11 Uplink log query == | ||
| 923 | |||
| 924 | |||
| 925 | * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)** | ||
| 926 | |||
| 927 | This command can be used to query upstream logs of data packets. | ||
| 928 | |||
| 929 | (% aria-label="image-20240726141548-7.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20240726141548-7.png||height="602" width="804"]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]] | ||
| 930 | |||
| 931 | |||
| 932 | == 3.12 Set CoAP option == | ||
| 933 | |||
| 934 | |||
| 935 | Feature: Set CoAP option, follow this link to set up the CoaP protocol. | ||
| 936 | |||
| 937 | (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8** | ||
| 938 | |||
| 939 | (% style="color:#037691; font-weight:bold" %)**AT+URI1=11,"i" **(%%)~/~/ "i/" indicates that the endpoint supports observation mode. In -CB products, fixed setting AT+URI1=11,"i" | ||
| 940 | |||
| 941 | (% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl" **(%%)~/~/ 11 is a fixed parameter. | ||
| 942 | |||
| 943 | **Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86 | ||
| 944 | |||
| 945 | AT+URI1=11,"i" | ||
| 946 | |||
| 947 | AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86" | ||
| 948 | |||
| 949 | ~-~-> If multiple groups of CoAP endpoint urls: | ||
| 950 | |||
| 951 | AT+URI3=11,"i" | ||
| 952 | |||
| 953 | AT+URI4=11,"CoAP endpoint URl" | ||
| 954 | |||
| 955 | |||
| 956 | = 4. Battery & Power Consumption = | ||
| 957 | |||
| 958 | |||
| 959 | PS-CB-NA use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
| 960 | |||
| 961 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
| 962 | |||
| 963 | |||
| 964 | = 5. Firmware update = | ||
| 965 | |||
| 966 | |||
| 967 | User can change device firmware to: | ||
| 968 | |||
| 969 | * Update with new features. | ||
| 970 | |||
| 971 | * Fix bugs. | ||
| 972 | |||
| 973 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/ALRWIZMmoxsEv4fHra6o1vw/PS-CB?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]]** | ||
| 974 | |||
| 975 | Methods to Update Firmware: | ||
| 976 | |||
| 977 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
| 978 | |||
| 979 | * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**. | ||
| 980 | |||
| 981 | = 6. FAQ = | ||
| 982 | |||
| 983 | == 6.1 How can I access the BG95-NGFF AT Commands? == | ||
| 984 | |||
| 985 | |||
| 986 | User can access to BG95-NGFF directly and send AT Commands. | ||
| 987 | |||
| 988 | [[See BG95-NGFF AT Command set>>https://www.dropbox.com/scl/fo/1mzflb9p9kx15btnc11gr/ALDWTvDjuVoXvDJuYWCRh5U/Vendor%20Datasheet/BG95?dl=0&rlkey=ku98jt8u30coqy66saebai2co&subfolder_nav_tracking=1]] | ||
| 989 | |||
| 990 | |||
| 991 | == 6.2 How to configure the device through the MQTT subscription function? == | ||
| 992 | |||
| 993 | |||
| 994 | Subscription content: {AT COMMAND} | ||
| 995 | |||
| 996 | (% style="color:#037691" %)**Example:** | ||
| 997 | |||
| 998 | Setting AT+5VT=500 through Node-RED requires MQTT to send the content {AT+5VT=500}. | ||
| 999 | |||
| 1000 | (% aria-label="image-20231025162946-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20231025162946-2.png]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 1001 | |||
| 1002 | The serial port displays: | ||
| 1003 | |||
| 1004 | (% aria-label="image-20231025162958-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20231025162958-3.png]](% style="background-image:url(https://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) | ||
| 1005 | |||
| 1006 | |||
| 1007 | = 7. Order Info = | ||
| 1008 | |||
| 1009 | |||
| 1010 | Part Number: (% style="color:blue" %)**PS-CB-NA-XX-YY** | ||
| 1011 | |||
| 1012 | (% style="color:red" %)**XX:** | ||
| 1013 | |||
| 1014 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
| 1015 | |||
| 1016 | * (% style="color:#037691" %)**1T**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to ThingsEye server | ||
| 1017 | |||
| 1018 | (% style="color:blue" %)**YY: The grand connector hole size** | ||
| 1019 | |||
| 1020 | * M12: M12 hole | ||
| 1021 | |||
| 1022 | * M16: M16 hole | ||
| 1023 | |||
| 1024 | * M20: M20 hole | ||
| 1025 | |||
| 1026 | = 8. Packing Info = | ||
| 1027 | |||
| 1028 | |||
| 1029 | (% style="color:#037691" %)**Package Includes**: | ||
| 1030 | |||
| 1031 | * PS-CB-NA NB-IoT/LTE-M Analog Sensor x 1 | ||
| 1032 | |||
| 1033 | * External antenna x 1 | ||
| 1034 | |||
| 1035 | (% style="color:#037691" %)**Dimension and weight**: | ||
| 1036 | |||
| 1037 | (% style="color:blue" %)**Package Size / pcs :** | ||
| 1038 | |||
| 1039 | * For PS-CB-NA: 170*80*55 mm | ||
| 1040 | * For PS-CS-NA: 160*105*45 mm | ||
| 1041 | |||
| 1042 | (% style="color:blue" %)**Weight / pcs :**(%%)** ** | ||
| 1043 | |||
| 1044 | * For PS-CB-NA: 250 g | ||
| 1045 | * For PS-CS-NA: 285 g | ||
| 1046 | |||
| 1047 | = 9. Support = | ||
| 1048 | |||
| 1049 | |||
| 1050 | * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. | ||
| 1051 | |||
| 1052 | * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]. | ||
| 1053 | |||
| 1054 | (% style="display:none" %) (%%) |