Wiki source code of SDI-12-LB -- SDI-12 to LoRaWAN Converter User Manual

Version 41.10 by Xiaoling on 2023/02/01 16:26

version	line-number	content
40.7	1	(% style="text-align:center" %)
	2	[[image:image-20230131183542-1.jpeg\|\|height="694" width="694"]]
2.2	3
	4	Table of Contents：
	5
40.7	6	{{toc/}}
2.2	7
	8
	9
	10
	11
	12
	13
	14
	15
	16
	17
	18
	19
9.2	20	= 1. Introduction =
2.2	21
9.2	22	== 1.1 What is SDI-12 to LoRaWAN Converter ==
2.2	23
	24
40.2	25	The Dragino (% style="color:blue" %)SDI-12-LB(%%) is a (% style="color:blue" %)SDI-12 to LoRaWAN Converter (%%)designed for Smart Agriculture solution.
9.2	26
2.2	27	SDI-12 (Serial Digital Interface at 1200 baud) is an asynchronous [[serial communications>>url:https://en.wikipedia.org/wiki/Serial_communication]] protocol for intelligent sensors that monitor environment data. SDI-12 protocol is widely used in Agriculture sensor and Weather Station sensors.
	28
37.8	29	SDI-12-LB has SDI-12 interface and support 12v output to power external SDI-12 sensor. It can get the environment data from SDI-12 sensor and sends out the data via LoRaWAN wireless protocol.
2.2	30
37.8	31	The LoRa wireless technology used in SDI-12-LB allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
2.2	32
40.2	33	SDI-12-LB is powered by (% style="color:blue" %)8500mAh Li-SOCI2 battery(%%), it is designed for long term use up to 5 years.
2.2	34
37.8	35	Each SDI-12-LB is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
2.2	36
	37
40.7	38	[[image:image-20230201084414-1.png\|\|height="464" width="1108"]]
2.2	39
	40
	41
	42
9.2	43	== 1.2 Features ==
	44
	45
2.2	46	* LoRaWAN 1.0.3 Class A
	47	* Ultra-low power consumption
	48	* Controllable 5v and 12v output to power external sensor
	49	* SDI-12 Protocol to connect to SDI-12 Sensor
	50	* Monitor Battery Level
	51	* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
	52	* Support Bluetooth v5.1 and LoRaWAN remote configure.
	53	* Support wireless OTA update firmware
	54	* Uplink on periodically
	55	* Downlink to change configure
	56	* 8500mAh Battery for long term use
	57
9.2	58	== 1.3 Specification ==
2.2	59
	60
40.2	61	(% style="color:#037691" %)Micro Controller:
2.2	62
	63	* MCU: 48Mhz ARM
	64	* Flash: 256KB
	65	* RAM: 64KB
	66
40.2	67	(% style="color:#037691" %)Common DC Characteristics:
2.2	68
	69	* Supply Voltage: 2.5v ~~ 3.6v
	70	* Operating Temperature: -40 ~~ 85°C
	71
40.2	72	(% style="color:#037691" %)LoRa Spec:
2.2	73
	74	* Frequency Range, Band 1 (HF): 862 ~~ 1020 Mhz
	75	* Max +22 dBm constant RF output vs.
	76	* RX sensitivity: down to -139 dBm.
	77	* Excellent blocking immunity
	78
40.2	79	(% style="color:#037691" %)Current Input Measuring :
2.2	80
	81	* Range: 0 ~~ 20mA
	82	* Accuracy: 0.02mA
	83	* Resolution: 0.001mA
	84
40.2	85	(% style="color:#037691" %)Voltage Input Measuring:
2.2	86
	87	* Range: 0 ~~ 30v
	88	* Accuracy: 0.02v
	89	* Resolution: 0.001v
	90
40.2	91	(% style="color:#037691" %)Battery:
2.2	92
	93	* Li/SOCI2 un-chargeable battery
	94	* Capacity: 8500mAh
	95	* Self-Discharge: <1% / Year @ 25°C
	96	* Max continuously current: 130mA
	97	* Max boost current: 2A, 1 second
	98
40.2	99	(% style="color:#037691" %)Power Consumption
2.2	100
	101	* Sleep Mode: 5uA @ 3.3v
	102	* LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm
	103
9.2	104	== 1.4 Connect to SDI-12 Sensor ==
2.2	105
	106
	107
40.7	108	[[image:1675212538524-889.png]]
2.2	109
	110
9.2	111	== 1.5 Sleep mode and working mode ==
2.2	112
	113
40.2	114	(% style="color:blue" %)Deep Sleep Mode: (%%)Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life.
2.2	115
40.2	116	(% style="color:blue" %)Working Mode: (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN 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.
2.2	117
	118
9.2	119	== 1.6 Button & LEDs ==
2.2	120
	121
40.7	122	[[image:1675212633011-651.png]]
2.2	123
	124
	125
9.2	126	(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
	127	\|=(% style="width: 167px;" %)Behavior on ACT\|=(% style="width: 117px;" %)Function\|=(% style="width: 225px;" %)Action
	128	\|(% style="width:167px" %)Pressing ACT between 1s < time < 3s\|(% style="width:117px" %)Send an uplink\|(% style="width:225px" %)(((
	129	If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)blue led (%%)will blink once.
2.2	130	Meanwhile, BLE module will be active and user can connect via BLE to configure device.
	131	)))
9.2	132	\|(% style="width:167px" %)Pressing ACT for more than 3s\|(% style="width:117px" %)Active Device\|(% style="width:225px" %)(((
	133	(% 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 JOIN LoRaWAN network.
	134	(% style="color:green" %)Green led(%%) will solidly turn on for 5 seconds after joined in network.
2.2	135	Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network.
	136	)))
9.2	137	\|(% style="width:167px" %)Fast press ACT 5 times.\|(% style="width:117px" %)Deactivate Device\|(% style="width:225px" %)(% style="color:red" %)Red led(%%) will solid on for 5 seconds. Means PS-LB is in Deep Sleep Mode.
2.2	138
9.2	139	== 1.7 Pin Mapping ==
2.2	140
	141
40.7	142	[[image:1675213198663-754.png]]
2.2	143
	144
9.2	145	== 1.8 BLE connection ==
2.2	146
9.2	147
2.2	148	SDI-12-LB support BLE remote configure.
	149
	150	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:
	151
	152	* Press button to send an uplink
	153	* Press button to active device.
	154	* Device Power on or reset.
	155
	156	If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
	157
	158
9.2	159	== 1.9 Mechanical ==
2.2	160
	161
40.7	162	[[image:image-20230201090139-2.png]]
2.2	163
40.7	164	[[image:image-20230201090139-3.png]]
2.2	165
40.7	166	[[image:image-20230201090139-4.png]]
2.2	167
	168
19.2	169	= 2. Configure SDI-12 to connect to LoRaWAN network =
9.2	170
19.2	171	== 2.1 How it works ==
9.2	172
	173
40.2	174	The SDI-12-LB is configured as (% style="color:#037691" %)LoRaWAN OTAA Class A(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and activate the SDI-12-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
9.2	175
2.2	176
19.2	177	== 2.2 Quick guide to connect to LoRaWAN server (OTAA) ==
2.2	178
	179
	180	Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example.
	181
	182
40.7	183	[[image:image-20230201090528-5.png\|\|height="465" width="1111"]]
2.2	184
	185
	186	The LPS8V2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
	187
	188
40.2	189	(% style="color:blue" %)Step 1(%%): Create a device in TTN with the OTAA keys from SDI-12-LB.
2.2	190
	191	Each SDI-12-LB is shipped with a sticker with the default device EUI as below:
	192
	193
41.2	194	[[image:image-20230201152430-20.jpeg]]
2.2	195
	196
	197	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
	198
	199
40.2	200	(% style="color:blue" %)Register the device
2.2	201
40.7	202	[[image:1675213652444-622.png]]
2.2	203
	204
40.2	205	(% style="color:blue" %)Add APP EUI and DEV EUI
2.2	206
	207
40.7	208	[[image:1675213661769-223.png]]
2.2	209
	210
40.2	211	(% style="color:blue" %)Add APP EUI in the application
2.2	212
	213
40.7	214	[[image:1675213675852-577.png]]
2.2	215
	216
40.2	217	(% style="color:blue" %)Add APP KEY
2.2	218
40.7	219	[[image:1675213686734-883.png]]
2.2	220
	221
40.2	222	(% style="color:blue" %)Step 2(%%): Activate on SDI-12-LB
2.2	223
	224
	225	Press the button for 5 seconds to activate the SDI-12-LB.
	226
40.2	227	(% style="color:green" %)Green led(%%) will fast blink 5 times, device will enter (% style="color:blue" %)OTA mode (%%)for 3 seconds. And then start to JOIN LoRaWAN network. (% style="color:green" %)Green led(%%) will solidly turn on for 5 seconds after joined in network.
2.2	228
	229
40.7	230	[[image:1675213704414-644.png]]
2.2	231
	232
19.2	233	== 2.3 SDI-12 Related Commands ==
2.2	234
	235
19.2	236	User need to configure SDI-12-LB to communicate with SDI-12 sensors otherwise the uplink payload will only include a few bytes.
2.2	237
	238
29.2	239	=== 2.3.1 Basic SDI-12 debug command ===
2.2	240
	241
	242	User can run some basic SDI-12 command to debug the connection to the SDI-12 sensor. These commands can be sent via AT Command or LoRaWAN downlink command.
	243
	244	If SDI-12 sensor return value after get these commands, //SDI-12-LB// will uplink the return on FPORT=100, otherwise, if there is no response from SDI-12 sensor. //SDI-12-LB// will uplink NULL (0x 4E 55 4C 4C) to server.
	245
	246	The following is the display information on the serial port and the server.
	247
	248
40.7	249	[[image:image-20230201091027-6.png]]
2.2	250
19.2	251
40.7	252	[[image:image-20230201091027-7.png\|\|height="261" width="1179"]]
19.2	253
	254
41.4	255
40.2	256	==== (% style="color:blue" %)al! ~-~- Get SDI-12 sensor Identification(%%) ====
19.2	257
	258
2.2	259	* AT Command: AT+ADDRI=aa
	260	* LoRaWAN Downlink(prefix 0xAA00): AA 00 aa
	261
40.2	262	(% style="color:#037691" %)Parameter: (%%)aa: ASCII value of SDI-12 sensor address in downlink or HEX value in AT Command)
2.2	263
41.4	264	(% style="color:blue" %)Example : (%%)AT+ADDRI=0 ( Equal to downlink: 0x AA 00 30)
2.2	265
	266
	267	The following is the display information on the serial port and the server.
	268
	269
40.7	270	[[image:image-20230201091257-8.png]]
2.2	271
	272
40.7	273	[[image:image-20230201091257-9.png\|\|height="225" width="1242"]]
19.2	274
	275
40.2	276	==== (% style="color:blue" %)aM!,aMC!, aM1!- aM9!, aMC1!- aMC9!(%%) ====
2.2	277
	278
40.2	279	(% style="color:red" %)aM! (%%): Start Non-Concurrent Measurement
2.2	280
40.2	281	(% style="color:red" %)aMC! (%%): Start Non-Concurrent Measurement – Request CRC
2.2	282
40.2	283	(% style="color:red" %)aM1!- aM9! (%%): Additional Measurements
2.2	284
40.2	285	(% style="color:red" %)aMC1!- aMC9!(%%) : Additional Measurements – Request CRC
2.2	286
27.2	287
2.2	288	* AT Command : AT+ADDRM=0,1,0,1
37.10	289
2.2	290	* LoRaWAN Downlink(prefix 0xAA01): 0xAA 01 30 01 00 01
	291
	292	Downlink：AA 01 aa bb cc dd
	293
40.2	294	(% style="color:#037691" %)aa(%%): SDI-12 sensor address.
2.2	295
40.2	296	(% style="color:#037691" %)bb(%%): 0: no CRC, 1: request CRC
2.2	297
40.2	298	(% style="color:#037691" %)cc(%%): 1-9: Additional Measurement, 0: no additional measurement
2.2	299
41.5	300	(% style="color:#037691" %)dd(%%): delay (in second) to send (% style="color:#037691" %)__aD0!__(%%) to get return.
2.2	301
	302
	303	The following is the display information on the serial port and the server.
	304
	305
40.7	306	[[image:image-20230201091630-10.png]]
2.2	307
	308
40.7	309	[[image:image-20230201091630-11.png\|\|height="247" width="1165"]]
2.2	310
	311
	312
40.2	313	==== (% style="color:blue" %)aC!, aCC!, aC1!- aC9!, aCC1!- aCC9! (%%) ====
2.2	314
	315
40.2	316	(% style="color:red" %)aC!(%%) : Start Concurrent Measurement
2.2	317
40.2	318	(% style="color:red" %)aCC! (%%): Start Concurrent Measurement – Request CRC
2.2	319
40.2	320	(% style="color:red" %)aC1!- aC9!(%%) : Start Additional Concurrent Measurements
27.2	321
40.2	322	(% style="color:red" %)aCC1!- aCC9!(%%) : Start Additional Concurrent Measurements – Request CRC
27.2	323
	324
2.2	325	* AT Command : AT+ADDRC=0,1,0,1
	326
	327	* LoRaWAN Downlink(0xAA02): 0xAA 02 30 01 00 01
	328
	329	Downlink: AA 02 aa bb cc dd
	330
40.2	331	(% style="color:#037691" %)aa(%%): SDI-12 sensor address.
2.2	332
40.2	333	(% style="color:#037691" %)bb(%%): 0: no CRC, 1: request CRC
2.2	334
40.2	335	(% style="color:#037691" %)cc(%%): 1-9: Additional Measurement, 0: no additional measurement
2.2	336
41.5	337	(% style="color:#037691" %)dd(%%): delay (in second) to send (% style="color:#037691" %)__aD0!__(%%)__ __to get return.
2.2	338
	339
	340	The following is the display information on the serial port and the server.
	341
	342
40.7	343	[[image:image-20230201091954-12.png]]
2.2	344
	345
40.7	346	[[image:image-20230201091954-13.png\|\|height="203" width="1117"]]
2.2	347
27.2	348
	349
	350
40.2	351	==== (% style="color:blue" %)aR0!- aR9!, aRC0!- aRC9!(%%) ====
27.2	352
37.10	353
2.2	354	Start Continuous Measurement
	355
	356	Start Continuous Measurement – Request CRC
	357
	358
	359	* AT Command : AT+ADDRR=0,1,0,1
	360	* LoRaWAN Downlink (0xAA 03): 0xAA 03 30 01 00 01
	361
	362	Downlink: AA 03 aa bb cc dd
	363
40.2	364	(% style="color:#037691" %)aa(%%): SDI-12 sensor address.
2.2	365
40.2	366	(% style="color:#037691" %)bb(%%): 0: no CRC, 1: request CRC
2.2	367
40.2	368	(% style="color:#037691" %)cc(%%): 1-9: Additional Measurement, 0: no additional measurement
2.2	369
41.5	370	(% style="color:#037691" %)dd(%%): delay (in second) to send (% style="color:#037691" %)__aD0!__(%%) to get return.
2.2	371
	372
	373	The following is the display information on the serial port and the server.
	374
	375
40.7	376	[[image:image-20230201092208-14.png]]
2.2	377
27.2	378
40.7	379	[[image:image-20230201092208-15.png\|\|height="214" width="1140"]]
27.2	380
	381
37.2	382	=== 2.3.2 Advance SDI-12 Debug command ===
27.2	383
	384
2.2	385	This command can be used to debug all SDI-12 command.
	386
	387
	388	LoRaWAN Downlink: A8 aa xx xx xx xx bb cc
	389
40.2	390	(% style="color:#037691" %)aa (%%): total SDI-12 command length
2.2	391
40.2	392	(% style="color:#037691" %)xx (%%): SDI-12 command
2.2	393
40.2	394	(% style="color:#037691" %)bb (%%): Delay to wait for return
2.2	395
40.2	396	(% style="color:#037691" %)cc (%%): 0: don't uplink return to LoRaWAN, 1: Uplink return to LoRaWAN on FPORT=100
2.2	397
	398
40.2	399	(% style="color:blue" %)Example: (%%) AT+CFGDEV =0RC0!,1
2.2	400
40.2	401	(% style="color:#037691" %)0RC0! (%%): SDI-12 Command,
2.2	402
40.2	403	(% style="color:#037691" %)1 (%%): Delay 1 second. ( 0: 810 mini-second)
2.2	404
	405	Equal Downlink: 0xA8 05 30 52 43 30 21 01 01
	406
	407
	408	The following is the display information on the serial port and the server.
	409
	410
40.7	411	[[image:image-20230201092355-16.png]]
2.2	412
	413
40.7	414	[[image:image-20230201092355-17.png\|\|height="426" width="1135"]]
27.2	415
29.2	416
	417	=== 2.3.3 Convert ASCII to String ===
	418
	419
2.2	420	This command is used to convert between ASCII and String format.
	421
	422	AT+CONVFORM ( Max length: 80 bytes)
	423
	424
40.2	425	(% style="color:blue" %)Example:
2.2	426
29.2	427	1) AT+CONVFORM=0, string Convert String from String to ASCII
2.2	428
40.7	429	[[image:1675214845056-885.png]]
2.2	430
	431
29.2	432	2) AT+CONVFORM=1, ASCII Convert ASCII to String.
2.2	433
40.7	434	[[image:1675214856590-846.png]]
2.2	435
29.2	436
	437	=== 2.3.4 Define periodically SDI-12 commands and uplink. ===
	438
	439
2.2	440	AT+COMMANDx & AT+DATACUTx
	441
	442	User can define max 15 SDI-12 Commands (AT+COMMAND1 ~~ AT+COMMANDF). On each uplink period (TDC time, default 20 minutes), SDI-12-LB will send these SDI-12 commands and wait for return from SDI-12 sensors. SDI-12-LB will then combine these returns and uplink via LoRaWAN.
	443
	444
40.2	445	* (% style="color:blue" %)AT Command:
2.2	446
40.2	447	(% style="color:#037691" %)AT+COMMANDx=var1,var2,var3,var4.
2.2	448
40.2	449	(% style="color:red" %)var1(%%): SDI-12 command , for example: 0RC0!
2.2	450
40.2	451	(% style="color:red" %)var2(%%): Wait timeout for return. (unit: second)
2.2	452
40.2	453	(% style="color:red" %)var3(%%): Whether to send //addrD0!// to get return after var2 timeout. 0: Don't Send //addrD0! //; 1: Send //addrD0!//.
2.2	454
40.2	455	(% style="color:red" %)var4(%%): validation check for return. If return invalid, SDI-12-LB will resend this command. Max 2 retries.
2.2	456
40.2	457	(% style="color:red" %)0 (%%) No validation check;
2.2	458
40.2	459	(% style="color:red" %)1 (%%) Check if return chars are printable char(0x20 ~~ 0x7E);
2.2	460
41.5	461	(% style="color:red" %)2(%%) Check if there is return from SDI-12 sensor
2.2	462
40.2	463	(% style="color:red" %)3 (%%) Check if return pass CRC check ( SDI-12 command var1 must include CRC request);
2.2	464
	465
40.2	466	Each AT+COMMANDx is followed by a (% style="color:blue" %)AT+DATACUT(%%) command. AT+DATACUT command is used to take the useful string from the SDI-12 sensor so the final payload will have the minimum length to uplink.
2.2	467
	468
40.2	469	(% style="color:blue" %)AT+DATACUTx(%%) : This command defines how to handle the return from AT+COMMANDx, max return length is 100 bytes.
2.2	470
29.2	471	(% border="1" style="background-color:#f7faff; width:436px" %)
	472	\|(% style="width:433px" %)(((
35.2	473	AT+DATACUTx=a,b,c
2.2	474
29.2	475	a: length for the return of AT+COMMAND
2.2	476
37.11	477	b: 1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.
2.2	478
29.2	479	c: define the position for valid value.
2.2	480	)))
	481
35.2	482	For example, if return from AT+COMMAND1 is “013METER TER12 112T12-00024895” , Below AT+DATACUT1 will get different result to combine payload:
2.2	483
	484
35.2	485	(% border="1" cellspacing="4" style="background-color:#f7faff; width:510px" %)
	486	\|(% style="width:170px" %)AT+DATACUT1 value\|(% style="width:338px" %)Final Result to combine Payload
	487	\|(% style="width:170px" %)34,1,1+2+3\|(% style="width:338px" %)0D 00 01 30 31 33
	488	\|(% style="width:170px" %)34,2,1~~8+12~~16\|(% style="width:338px" %)0D 00 01 30 31 33 4D 45 54 45 52 54 45 52 31 32
	489	\|(% style="width:170px" %)34,2,1~~34\|(% style="width:338px" %)0D 00 01 30 31 33 4D 45 54 45 52 20 20 20 54 45 52 31 32 20 31 31 32 54 31 32 2D 30 30 30 32 34 38 39 35 0D 0A
2.2	490
40.2	491	* (% style="color:blue" %) Downlink Payload:
2.2	492
40.2	493	(% style="color:blue" %)0xAF(%%) downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
2.2	494
	495
40.2	496	(% style="color:red" %)Note : if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
2.2	497
	498
40.2	499	Format: (% style="color:#037691" %)AF MM NN LL XX XX XX XX YY(%%)
2.2	500
	501	Where:
	502
40.2	503	* (% style="color:#037691" %)MM (%%): the AT+COMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
	504	* (% style="color:#037691" %)NN (%%): 1: set the AT+DATACUT value ; 2: set the AT+DATACUT value.
	505	* (% style="color:#037691" %)LL (%%): The length of AT+COMMAND or AT+DATACUT command
	506	* (% style="color:#037691" %)XX XX XX XX (%%): AT+COMMAND or AT+DATACUT command
	507	* (% style="color:#037691" %)YY (%%): If YY=0, RS485-LN will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
2.2	508
40.2	509	(% style="color:blue" %)Example:
2.2	510
40.7	511	[[image:image-20230201094129-18.png]]
2.2	512
	513
40.2	514	(% style="color:blue" %)Clear SDI12 Command
2.2	515
	516	The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
	517
	518
40.2	519	* (% style="color:#037691" %)AT Command:
2.2	520
40.2	521	(% style="color:#4f81bd" %)AT+CMDEAR=mm,nn (%%) mm: start position of erase ,nn: stop position of erase
2.2	522
	523
	524	Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
	525
	526
40.2	527	* (% style="color:#037691" %) Downlink Payload:
2.2	528
40.2	529	(% style="color:#4f81bd" %)0x09 aa bb(%%) same as AT+CMDEAR=aa,bb
2.2	530
	531
	532
40.2	533	(% style="color:blue" %)command combination
2.2	534
	535	Below shows a screen shot how the results combines together to a uplink payload.
	536
40.7	537	[[image:1675215745275-920.png]]
2.2	538
	539
35.2	540	If user don't want to use DATACUT for some command, he simply want to uplink all returns. AT+ALLDATAMOD can be set to 1.
2.2	541
40.2	542	(% style="color:blue" %)AT+ALLDATAMOD(%%) will simply get all return and don't do CRC check as result for SDI-12 command. AT+DATACUTx command has higher priority, if AT+DATACUTx has been set, AT+ALLDATAMOD will be ignore for this SDI-12 command.
2.2	543
	544
41.7	545	(% style="color:#4f81bd" %)For example: (%%) as below photo, AT+ALLDATAMOD=1, but AT+DATACUT1 has been set, AT+DATACUT1 will be still effect the result.
2.2	546
	547
40.7	548	[[image:1675215782925-448.png]]
2.2	549
	550
40.2	551	If AT+ALLDATAMOD=1, (% style="color:#4f81bd" %)FX,X(%%) will be added in the payload, FX specify which command is used and X specify the length of return. for example in above screen, F1 05 means the return is from AT+COMMAND1 and the return is 5 bytes.
2.2	552
	553
	554
40.2	555	(% style="color:blue" %)Compose Uplink
2.2	556
37.2	557
40.2	558	(% style="color:#4f81bd" %)AT+DATAUP=0
2.2	559
41.8	560	Compose the uplink payload with value returns in sequence and send with __A SIGNLE UPLINK__.
2.2	561
41.8	562	Final Payload is __Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx__
2.2	563
	564	Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
	565
	566
40.7	567	[[image:1675215828102-844.png]]
2.2	568
	569
40.2	570	(% style="color:#4f81bd" %)AT+DATAUP=1
2.2	571
41.8	572	Compose the uplink payload with value returns in sequence and send with __Multiply UPLINKs__.
2.2	573
41.8	574	Final Payload is __Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA__
2.2	575
	576	1. Battery Info (2 bytes): Battery voltage
	577	1. PAYVER (1 byte): Defined by AT+PAYVER
	578	1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
	579	1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
	580	1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
	581
40.7	582	[[image:1675215848113-696.png]]
2.2	583
	584
40.2	585	(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
2.2	586
35.2	587	* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
	588	* For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	589	* For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
	590	* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date).
2.2	591
40.2	592	(% style="color:red" %)When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;
2.2	593
40.2	594	(% style="color:red" %)When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value.
2.2	595
	596
40.7	597	== 2.4 Uplink Payload ==
2.2	598
	599
	600	Uplink payloads have two types:
	601
	602	* Distance Value: Use FPORT=2
	603	* Other control commands: Use other FPORT fields.
	604
	605	The application server should parse the correct value based on FPORT settings.
	606
	607
37.2	608	=== 2.4.1 Device Payload, FPORT~=5 ===
2.2	609
37.2	610
2.2	611	Include device configure status. Once SDI-12-LB Joined the network, it will uplink this message to the server.
	612
	613	Users can also use the downlink command(0x26 01) to ask SDI-12-LB to resend this uplink.
	614
35.2	615	(% border="1" cellspacing="4" style="background-color:#f7faff; width:437px" %)
	616	\|(% colspan="6" style="width:434px" %)Device Status (FPORT=5)
	617	\|(% style="width:102px" %)Size (bytes)\|(% style="width:67px" %)1\|(% style="width:80px" %)2\|(% style="width:89px" %)1\|(% style="width:52px" %)1\|(% style="width:44px" %)2
	618	\|(% style="width:102px" %)Value\|(% style="width:67px" %)Sensor Model\|(% style="width:80px" %)Firmware Version\|(% style="width:89px" %)Frequency Band\|(% style="width:52px" %)Sub-band\|(% style="width:44px" %)BAT
2.2	619
	620	Example parse in TTNv3
	621
40.7	622	[[image:1675215946738-635.png]]
2.2	623
37.2	624
40.2	625	(% style="color:#037691" %)Sensor Model(%%): For SDI-12-LB, this value is 0x17
2.2	626
40.2	627	(% style="color:#037691" %)Firmware Version(%%): 0x0100, Means: v1.0.0 version
2.2	628
40.2	629	(% style="color:#037691" %)Frequency Band:
2.2	630
	631	*0x01: EU868
	632
	633	*0x02: US915
	634
	635	*0x03: IN865
	636
	637	*0x04: AU915
	638
	639	*0x05: KZ865
	640
	641	*0x06: RU864
	642
	643	*0x07: AS923
	644
	645	*0x08: AS923-1
	646
	647	*0x09: AS923-2
	648
	649	*0x0a: AS923-3
	650
	651	*0x0b: CN470
	652
	653	*0x0c: EU433
	654
	655	*0x0d: KR920
	656
	657	*0x0e: MA869
	658
	659
40.2	660	(% style="color:#037691" %)Sub-Band:
2.2	661
	662	AU915 and US915:value 0x00 ~~ 0x08
	663
	664	CN470: value 0x0B ~~ 0x0C
	665
	666	Other Bands: Always 0x00
	667
	668
40.2	669	(% style="color:#037691" %)Battery Info:
2.2	670
	671	Check the battery voltage.
	672
	673	Ex1: 0x0B45 = 2885mV
	674
	675	Ex2: 0x0B49 = 2889mV
	676
	677
37.2	678	=== 2.4.2 Uplink Payload, FPORT~=2 ===
2.2	679
37.2	680
2.2	681	There are different cases for uplink. See below
	682
	683	* SDI-12 Debug Command return: FPORT=100
	684
	685	* Periodically Uplink: FPORT=2
	686
37.2	687	(% border="1" cellspacing="4" style="background-color:#f7faff; width:510px" %)
	688	\|(% style="width:93px" %)(((
	689	Size(bytes)
	690	)))\|(% style="width:83px" %)2\|(% style="width:70px" %)1\|(% style="width:234px" %)Length depends on the return from the commands
	691	\|(% style="width:93px" %)Value\|(% style="width:83px" %)(((
2.2	692	Battery(mV)
	693	&
	694	Interrupt_Flag
37.12	695	)))\|(% style="width:70px" %)[[PAYLOAD_VER>>\|\|anchor="H3.6Setthepayloadversion"]]\|(% style="width:234px" %)(((
37.2	696	If the valid payload is too long and exceed the maximum support.
2.2	697	Payload length in server,server will show payload not provided in the LoRaWAN server.
	698	)))
	699
40.7	700	[[image:1675216282284-923.png]]
2.2	701
	702
37.2	703	=== 2.4.3 Battery Info ===
2.2	704
	705
	706	Check the battery voltage for SDI-12-LB.
	707
	708	Ex1: 0x0B45 = 2885mV
	709
	710	Ex2: 0x0B49 = 2889mV
	711
	712
37.2	713	=== 2.4.4 Interrupt Pin ===
2.2	714
37.2	715
40.2	716	This data field shows if this packet is generated by (% style="color:#037691" %)Interrupt Pin(%%) or not. [[Click here>>\|\|anchor="H3.2SetInterruptMode"]] for the hardware and software set up. Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>\|\|anchor="H1.7PinMapping"]].
2.2	717
37.2	718	Example:
2.2	719
	720	Ex1: 0x0B45:0x0B&0x80= 0x00 Normal uplink packet.
	721
	722	Ex2: 0x8B49:0x8B&0x80= 0x80 Interrupt Uplink Packet.
	723
	724
37.2	725	=== 2.4.5 Payload version ===
2.2	726
	727
	728
37.2	729	=== 2.4.6 Decode payload in The Things Network ===
2.2	730
	731
	732	While using TTN network, you can add the payload format to decode the payload.
	733
40.7	734	[[image:1675216779406-595.png]]
2.2	735
	736
	737	There is no fix payload decoder in LoRaWAN server because the SDI-12 sensors returns are different. User need to write the decoder themselves for their case.
	738
37.2	739	SDI-12-LB TTN Payload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]]
2.2	740
	741
37.3	742	== 2.5 Uplink Interval ==
2.2	743
	744
	745	The SDI-12-LB by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link:
	746
40.2	747	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.1ChangeUplinkInterval>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.1ChangeUplinkInterval]]]]
2.2	748
	749
37.3	750	== 2.6 Frequency Plans ==
2.2	751
	752
37.3	753	The SDI-12-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
2.2	754
37.3	755	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
2.2	756
	757
37.3	758	== 2.7 Firmware Change Log ==
	759
	760
2.2	761	Firmware download link:
	762
41.9	763	[[https:~~/~~/www.dropbox.com/sh/qrbgbikb109lkiv/AACBR-v_ZhZAMengcY7Nsa1ja?dl=0>>https://www.dropbox.com/sh/qrbgbikb109lkiv/AACBR-v_ZhZAMengcY7Nsa1ja?dl=0]]
2.2	764
41.9	765
2.2	766
37.3	767	= 3. Configure SDI-12-LB via AT Command or LoRaWAN Downlink =
2.2	768
	769
	770	Use can configure SDI-12-LB via AT Command or LoRaWAN Downlink.
	771
40.8	772	* AT Command Connection: See [[FAQ>>\|\|anchor="H7.FAQ"]].
37.3	773	* LoRaWAN Downlink instruction for different platforms: See [[IoT LoRaWAN Server>>http://wiki.dragino.com/xwiki/bin/view/Main/]] section.
2.2	774
	775	There are two kinds of commands to configure SDI-12-LB, they are:
	776
40.7	777	* (% style="color:blue" %)General Commands.
2.2	778
	779	These commands are to configure:
	780
	781	* General system settings like: uplink interval.
	782	* LoRaWAN protocol & radio related command.
	783
	784	They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki:
	785
40.2	786	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
2.2	787
	788
40.7	789	* (% style="color:blue" %)Commands special design for SDI-12-LB
2.2	790
	791	These commands only valid for SDI-12-LB, as below:
	792
	793
37.3	794	== 3.1 Set Transmit Interval Time ==
2.2	795
	796
	797	Feature: Change LoRaWAN End Node Transmit Interval.
	798
37.3	799	(% style="color:blue" %)AT Command: AT+TDC
2.2	800
37.3	801	(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
	802	\|=(% style="width: 156px;" %)Command Example\|=(% style="width: 137px;" %)Function\|=Response
	803	\|(% style="width:156px" %)AT+TDC=?\|(% style="width:137px" %)Show current transmit Interval\|(((
2.2	804	30000
	805	OK
	806	the interval is 30000ms = 30s
	807	)))
37.3	808	\|(% style="width:156px" %)AT+TDC=60000\|(% style="width:137px" %)Set Transmit Interval\|(((
2.2	809	OK
	810	Set transmit interval to 60000ms = 60 seconds
	811	)))
	812
37.3	813	(% style="color:blue" %)Downlink Command: 0x01
2.2	814
37.3	815
2.2	816	Format: Command Code (0x01) followed by 3 bytes time value.
	817
37.6	818	If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
2.2	819
37.6	820	* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	821	* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
2.2	822
37.3	823	== 3.2 Set Interrupt Mode ==
2.2	824
37.6	825
2.2	826	Feature, Set Interrupt mode for GPIO_EXIT.
	827
37.3	828	(% style="color:blue" %)AT Command: AT+INTMOD
2.2	829
37.3	830	(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:510px" %)
37.6	831	\|=(% style="width: 156px;" %)Command Example\|=(% style="width: 187px;" %)Function\|=(% style="width: 165px;" %)Response
	832	\|(% style="width:156px" %)AT+INTMOD=?\|(% style="width:187px" %)Show current interrupt mode\|(% style="width:165px" %)(((
2.2	833	0
	834	OK
	835	the mode is 0 = No interruption
	836	)))
37.6	837	\|(% style="width:156px" %)AT+INTMOD=2\|(% style="width:187px" %)(((
2.2	838	Set Transmit Interval
37.3	839	~1. (Disable Interrupt),
	840	2. (Trigger by rising and falling edge)
	841	3. (Trigger by falling edge)
	842	4. (Trigger by rising edge)
37.6	843	)))\|(% style="width:165px" %)OK
2.2	844
37.3	845	(% style="color:blue" %)Downlink Command: 0x06
2.2	846
	847	Format: Command Code (0x06) followed by 3 bytes.
	848
	849	This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	850
37.6	851	* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	852	* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
2.2	853
37.3	854	== 3.3 Set the output time ==
	855
	856
2.2	857	Feature, Control the output 3V3 , 5V or 12V.
	858
37.3	859	(% style="color:blue" %)AT Command: AT+3V3T
2.2	860
37.3	861	(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:474px" %)
	862	\|=(% style="width: 154px;" %)Command Example\|=(% style="width: 201px;" %)Function\|=(% style="width: 116px;" %)Response
	863	\|(% style="width:154px" %)AT+3V3T=?\|(% style="width:201px" %)Show 3V3 open time.\|(% style="width:116px" %)(((
2.2	864	0
	865	OK
	866	)))
37.3	867	\|(% style="width:154px" %)AT+3V3T=0\|(% style="width:201px" %)Normally open 3V3 power supply.\|(% style="width:116px" %)(((
2.2	868	OK
	869	default setting
	870	)))
37.3	871	\|(% style="width:154px" %)AT+3V3T=1000\|(% style="width:201px" %)Close after a delay of 1000 milliseconds.\|(% style="width:116px" %)(((
2.2	872	OK
	873	)))
37.3	874	\|(% style="width:154px" %)AT+3V3T=65535\|(% style="width:201px" %)Normally closed 3V3 power supply.\|(% style="width:116px" %)(((
2.2	875	OK
	876	)))
	877
37.3	878	(% style="color:blue" %)AT Command: AT+5VT
2.2	879
37.3	880	(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:470px" %)
	881	\|=(% style="width: 155px;" %)Command Example\|=(% style="width: 196px;" %)Function\|=(% style="width: 114px;" %)Response
	882	\|(% style="width:155px" %)AT+5VT=?\|(% style="width:196px" %)Show 5V open time.\|(% style="width:114px" %)(((
2.2	883	0
	884	OK
	885	)))
37.3	886	\|(% style="width:155px" %)AT+5VT=0\|(% style="width:196px" %)Normally closed 5V power supply.\|(% style="width:114px" %)(((
2.2	887	OK
	888	default setting
	889	)))
37.3	890	\|(% style="width:155px" %)AT+5VT=1000\|(% style="width:196px" %)Close after a delay of 1000 milliseconds.\|(% style="width:114px" %)(((
2.2	891	OK
	892	)))
37.3	893	\|(% style="width:155px" %)AT+5VT=65535\|(% style="width:196px" %)Normally open 5V power supply.\|(% style="width:114px" %)(((
2.2	894	OK
	895	)))
	896
37.3	897	(% style="color:blue" %)AT Command: AT+12VT
2.2	898
37.3	899	(% border="1" cellspacing="4" style="background-color:#f7faff; color:black; width:443px" %)
	900	\|=(% style="width: 156px;" %)Command Example\|=(% style="width: 199px;" %)Function\|=(% style="width: 83px;" %)Response
	901	\|(% style="width:156px" %)AT+12VT=?\|(% style="width:199px" %)Show 12V open time.\|(% style="width:83px" %)(((
2.2	902	0
	903	OK
	904	)))
37.3	905	\|(% style="width:156px" %)AT+12VT=0\|(% style="width:199px" %)Normally closed 12V power supply.\|(% style="width:83px" %)OK
	906	\|(% style="width:156px" %)AT+12VT=500\|(% style="width:199px" %)Close after a delay of 500 milliseconds.\|(% style="width:83px" %)(((
2.2	907	OK
	908	)))
	909
37.3	910	(% style="color:blue" %)Downlink Command: 0x07
2.2	911
	912	Format: Command Code (0x07) followed by 3 bytes.
	913
	914	The first byte is which power, the second and third bytes are the time to turn on.
	915
37.3	916	* Example 1: Downlink Payload: 070101F4 ~-~--> AT+3V3T=500
	917	* Example 2: Downlink Payload: 0701FFFF ~-~--> AT+3V3T=65535
	918	* Example 3: Downlink Payload: 070203E8 ~-~--> AT+5VT=1000
	919	* Example 4: Downlink Payload: 07020000 ~-~--> AT+5VT=0
	920	* Example 5: Downlink Payload: 070301F4 ~-~--> AT+12VT=500
	921	* Example 6: Downlink Payload: 07030000 ~-~--> AT+12VT=0
2.2	922
37.3	923	== 3.4 Set the all data mode ==
	924
37.5	925
2.2	926	Feature, Set the all data mode.
	927
37.5	928	(% style="color:blue" %)AT Command: AT+ALLDATAMOD
2.2	929
37.5	930	(% border="1" cellspacing="4" style="background-color:#f7faff; width:437px" %)
	931	\|=Command Example\|=Function\|=Response
2.2	932	\|AT+ALLDATAMOD=?\|Show current all data mode\|(((
	933	0
	934	OK
	935	)))
	936	\|AT+ALLDATAMOD=1\|Set all data mode is 1.\|OK
	937
37.5	938	(% style="color:blue" %)Downlink Command: 0xAB
2.2	939
	940	Format: Command Code (0xAB) followed by 1 bytes.
	941
37.5	942	* Example 1: Downlink Payload: AB 00 ~/~/ AT+ALLDATAMOD=0
	943	* Example 2: Downlink Payload: AB 01 ~/~/ AT+ALLDATAMOD=1
2.2	944
37.3	945	== 3.5 Set the splicing payload for uplink ==
	946
37.5	947
2.2	948	Feature, splicing payload for uplink.
	949
37.5	950	(% style="color:blue" %)AT Command: AT+DATAUP
2.2	951
37.5	952	(% border="1" cellspacing="4" style="background-color:#f7faff; width:510px" %)
	953	\|=(% style="width: 154px;" %)Command Example\|=(% style="width: 266px;" %)Function\|=Response
	954	\|(% style="width:154px" %)AT+DATAUP =?\|(% style="width:266px" %)Show current splicing payload for uplink mode\|(((
2.2	955	0
	956	OK
	957	)))
37.5	958	\|(% style="width:154px" %)AT+DATAUP =0\|(% style="width:266px" %)(((
2.2	959	Set splicing payload for uplink mode is 0.
	960	)))\|(((
	961	OK
	962	)))
37.5	963	\|(% style="width:154px" %)AT+DATAUP =1\|(% style="width:266px" %)Set splicing payload for uplink mode is 1 , and the each splice uplink is sent sequentially.\|OK
	964	\|(% style="width:154px" %)AT+DATAUP =1,20000\|(% style="width:266px" %)(((
37.3	965	Set splicing payload for uplink mode is 1, and the uplink interval of each splice to 20000 milliseconds.
2.2	966	)))\|OK
	967
37.5	968	(% style="color:blue" %)Downlink Command: 0xAD
2.2	969
	970	Format: Command Code (0xAD) followed by 1 bytes or 5 bytes.
	971
37.6	972	* Example 1: Downlink Payload: AD 00 ~/~/ AT+DATAUP=0
	973	* Example 2: Downlink Payload: AD 01 ~/~/ AT+DATAUP =1
	974	* Example 3: Downlink Payload: AD 01 00 00 14 ~/~/ AT+DATAUP =1,20000
2.2	975
	976	This means that the interval is set to 0x000014=20S
	977
	978
37.3	979	== 3.6 Set the payload version ==
2.2	980
	981	Feature, Set the payload version.
	982
37.5	983	(% style="color:blue" %)AT Command: AT+PAYVER
2.2	984
37.6	985	(% border="1" cellspacing="4" style="background-color:#f7faff; width:437px" %)
	986	\|=(% style="width: 158px;" %)Command Example\|=(% style="width: 192px;" %)Function\|=Response
	987	\|(% style="width:158px" %)AT+PAYVER=?\|(% style="width:192px" %)Show current payload version\|(((
2.2	988	1
	989	OK
	990	)))
37.6	991	\|(% style="width:158px" %)AT+PAYVER=5\|(% style="width:192px" %)Set payload version is 5.\|OK
2.2	992
37.5	993	(% style="color:blue" %)Downlink Command: 0xAE
2.2	994
	995	Format: Command Code (0xAE) followed by 1 bytes.
	996
37.6	997	* Example 1: Downlink Payload: AE 01 ~/~/ AT+PAYVER=1
	998	* Example 2: Downlink Payload: AE 05 ~/~/ AT+PAYVER=5
2.2	999
37.3	1000	= 4. Battery & how to replace =
2.2	1001
37.3	1002	== 4.1 Battery Type ==
2.2	1003
	1004
37.5	1005	SDI-12-LB is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>https://www.dropbox.com/sh/w9l2oa3ytpculph/AAAPtt-apH4lYfCj-2Y6lHvQa?dl=0]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
37.3	1006
	1007
2.2	1008	The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
	1009
40.7	1010	[[image:1675234124233-857.png]]
2.2	1011
	1012
37.5	1013	Minimum Working Voltage for the SDI-12-LB:
2.2	1014
37.5	1015	SDI-12-LB: 2.45v ~~ 3.6v
2.2	1016
	1017
37.3	1018	== 4.2 Replace Battery ==
2.2	1019
37.3	1020
2.2	1021	Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
	1022
	1023	And make sure the positive and negative pins match.
	1024
	1025
37.3	1026	== 4.3 Power Consumption Analyze ==
2.2	1027
	1028
	1029	Dragino Battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
	1030
	1031	Instruction to use as below:
	1032
37.3	1033	(% style="color:blue" %)Step 1:(%%) Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dropbox.com/sh/zwex6i331j5oeq2/AACIMf9f_v2qsJ39CuMQ5Py_a?dl=0>>https://www.dropbox.com/sh/zwex6i331j5oeq2/AACIMf9f_v2qsJ39CuMQ5Py_a?dl=0]]
2.2	1034
37.3	1035	(% style="color:blue" %)Step 2:(%%) Open it and choose
2.2	1036
	1037	* Product Model
	1038	* Uplink Interval
	1039	* Working Mode
	1040
	1041	And the Life expectation in difference case will be shown on the right.
	1042
	1043
40.7	1044	[[image:1675234155374-163.png]]
2.2	1045
40.2	1046
2.2	1047	The battery related documents as below:
	1048
37.3	1049	* [[Battery Dimension>>https://www.dropbox.com/s/ox5g9njwjle7aw3/LSN50-Battery-Dimension.pdf?dl=0]],
	1050	* [[Lithium-Thionyl Chloride Battery datasheet, Tech Spec>>https://www.dropbox.com/sh/d4oyfnp8o94180o/AABQewCNSh5GPeQH86UxRgQQa?dl=0]]
	1051	* [[Lithium-ion Battery-Capacitor datasheet>>https://www.dropbox.com/s/791gjes2lcbfi1p/SPC_1520_datasheet.jpg?dl=0]], [[Tech Spec>>https://www.dropbox.com/s/4pkepr9qqqvtzf2/SPC1520%20Technical%20Specification20171123.pdf?dl=0]]
2.2	1052
40.7	1053	[[image:image-20230201145019-19.png]]
2.2	1054
	1055
37.3	1056	=== 4.3.1 Battery Note ===
2.2	1057
	1058
	1059	The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
	1060
	1061
37.3	1062	=== 4.3.2 Replace the battery ===
2.2	1063
	1064
37.5	1065	You can change the battery in the SDI-12-LB.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
2.2	1066
37.5	1067	The default battery pack of SDI-12-LB includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
2.2	1068
	1069
37.3	1070	= 5. Remote Configure device =
2.2	1071
37.3	1072	== 5.1 Connect via BLE ==
2.2	1073
	1074
37.3	1075	Please see this instruction for how to configure via BLE: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]
2.2	1076
	1077
37.3	1078	== 5.2 AT Command Set ==
2.2	1079
	1080
	1081
37.3	1082	= 6. OTA firmware update =
	1083
	1084
2.2	1085	Please see this link for how to do OTA firmware update.
	1086
	1087	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]
	1088
	1089
40.2	1090	= 7. FAQ =
2.2	1091
40.2	1092	== 7.1 How to use AT Command to access device? ==
2.2	1093
	1094
40.2	1095	See: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]
	1096
	1097
	1098	== 7.2 How to update firmware via UART port? ==
	1099
	1100
	1101	See: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]
	1102
	1103
	1104	== 7.3 How to change the LoRa Frequency Bands/Region? ==
	1105
	1106
	1107	You can follow the instructions for [[how to upgrade image>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]].
	1108	When downloading the images, choose the required image file for download.
	1109
	1110
	1111	= 8. Order Info =
	1112
	1113
40.7	1114	(% style="color:blue" %)Part Number: SDI-12-LB-XXX
	1115
37.4	1116	XXX: The default frequency band
2.2	1117
40.7	1118	(% style="color:red" %)AS923(%%): LoRaWAN AS923 band
	1119	(% style="color:red" %)AU915(%%): LoRaWAN AU915 band
	1120	(% style="color:red" %)EU433(%%): LoRaWAN EU433 band
	1121	(% style="color:red" %)EU868(%%): LoRaWAN EU868 band
	1122	(% style="color:red" %)KR920(%%): LoRaWAN KR920 band
	1123	(% style="color:red" %)US915(%%): LoRaWAN US915 band
	1124	(% style="color:red" %)IN865(%%): LoRaWAN IN865 band
	1125	(% style="color:red" %)CN470(%%): LoRaWAN CN470 band
2.2	1126
	1127
	1128
	1129
	1130
	1131
37.4	1132
40.2	1133	= 9. Packing Info =
37.3	1134
	1135
40.7	1136	(% style="color:#037691" %)Package Includes:
2.2	1137
37.3	1138	* SDI-12-LB SDI-12 to LoRaWAN Converter x 1
2.2	1139
40.7	1140	(% style="color:#037691" %)Dimension and weight:
2.2	1141
	1142	* Device Size: cm
	1143	* Device Weight: g
	1144	* Package Size / pcs : cm
	1145	* Weight / pcs : g
	1146
40.2	1147	= 10. Support =
37.3	1148
	1149
2.2	1150	* 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.
	1151
37.3	1152	* 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.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
2.2	1153
40.8	1154

Wiki source code of SDI-12-LB -- SDI-12 to LoRaWAN Converter User Manual

Applications

Navigation