Wiki source code of PF52 LoRaWAN Crowd Recognition Sensor User Manual
Last modified by Karry Zhuang on 2025/08/07 15:49
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | |||
2 | |||
3 | [[image:image-20241127145539-2.png||data-xwiki-image-style-alignment="center" height="284" width="370"]] | ||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
9 | |||
10 | |||
11 | |||
12 | |||
13 | |||
14 | (% _mstvisible="1" %) | ||
15 | (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:** | ||
16 | |||
17 | {{toc/}} | ||
18 | |||
19 | |||
20 | |||
21 | |||
22 | |||
23 | |||
24 | |||
25 | |||
26 | = 1. Introduction = | ||
27 | |||
28 | == 1.1 What is PF52 pedestrian recognition Sensor == | ||
29 | |||
30 | |||
31 | ((( | ||
32 | The Dragino PF52 pedestrian recognition sensor is a long-range LoRaWAN sensor. It includes a built-in AI camera sensor and has a USB Type-C. | ||
33 | ))) | ||
34 | |||
35 | ((( | ||
36 | PF52 (% style="color:blue" %)**senses the movement of people and makes identification judgments.**(%%) and send these values via long-range wireless LoRaWAN protocol. It targets professional wireless sensor network applications such as smart metering, smart cities, building automation, and so on. | ||
37 | ))) | ||
38 | |||
39 | ((( | ||
40 | PF52 uses an external power supply and can work for a long time. | ||
41 | ))) | ||
42 | |||
43 | ((( | ||
44 | PF52 is fully compatible with LoRaWAN v1.0.3 protocol, it can work with standard LoRaWAN gateway. | ||
45 | ))) | ||
46 | |||
47 | ((( | ||
48 | PF52 supports(% style="color:blue" %)** Datalog feature** (%%)to make sure users won't miss sensor data. It records sensor value for every uplink. These values can be retrieved by LoRaWAN server via downlink command. | ||
49 | ))) | ||
50 | |||
51 | ((( | ||
52 | |||
53 | ))) | ||
54 | |||
55 | [[image:1754549173539-713.png||height="301" width="763"]] | ||
56 | |||
57 | |||
58 | == 1.2 Features == | ||
59 | |||
60 | |||
61 | * LoRaWAN v1.0.3 Class A protocol. | ||
62 | * Low power consumption | ||
63 | * AI Image Sensor. | ||
64 | * Send image to IoT server | ||
65 | * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915 | ||
66 | * Support Interrupt uplink | ||
67 | * Support Bluetooth v5.1 and LoRaWAN remote configure | ||
68 | * Support wireless OTA update firmware | ||
69 | * AT Commands to change parameters | ||
70 | * Uplink on periodically | ||
71 | * Downlink to change configure | ||
72 | * IP Rating: IP52 | ||
73 | |||
74 | == 1.3 Specification == | ||
75 | |||
76 | |||
77 | **Common DC Characteristics:** | ||
78 | |||
79 | * DC power supply 5v | ||
80 | * Operating Temperature: -40 ~~ 85°C | ||
81 | |||
82 | **Camera:** | ||
83 | |||
84 | * Angle: 110° | ||
85 | * Image size:64kb | ||
86 | * Image resolution:640x480 | ||
87 | * Power Consumption: 206.1mW | ||
88 | * Supply Voltage: DC5V | ||
89 | * Idel Mode: 6uA | ||
90 | * Take Photo: 41.22 mA and 3171 ms | ||
91 | * Cable Length:150cm | ||
92 | * Dimension:46.2x29x13.8 mm | ||
93 | * Waterproof level:IP52 | ||
94 | |||
95 | **LoRa Spec:** | ||
96 | |||
97 | * Frequency Range, Band 1 (HF): 862 ~~ 1020 Mhz | ||
98 | * Max +22 dBm constant RF output vs. | ||
99 | * RX sensitivity: down to -139 dBm. | ||
100 | * Excellent blocking immunity | ||
101 | |||
102 | == 1.5 Storage & Operation Temperature == | ||
103 | |||
104 | |||
105 | -10 ~~ 50 °C or -40 ~~ 60 °C | ||
106 | |||
107 | |||
108 | == 1.6 Applications == | ||
109 | |||
110 | |||
111 | * Smart Buildings & Home Automation | ||
112 | * Logistics and Supply Chain Management | ||
113 | * Smart Metering | ||
114 | * Smart Agriculture | ||
115 | * Smart Cities | ||
116 | * Smart Factory | ||
117 | |||
118 | = 2. Configure PF52 to connect to LoRaWAN network = | ||
119 | |||
120 | == 2.1 How it works == | ||
121 | |||
122 | |||
123 | The PF52 is configured as **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 press the button to activate thePF52. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes. | ||
124 | |||
125 | The LED light is at the upper left for a positive viewing angle.When the character crosses the horizontal line in the middle, the count increases by one. | ||
126 | |||
127 | For details, please see the case. | ||
128 | |||
129 | [[image:image-20241128111021-4.jpeg||height="319" width="239"]][[image:1754549756659-849.png||height="321" width="427"]] | ||
130 | |||
131 | |||
132 | == 2.2 Example to join LoRaWAN network == | ||
133 | |||
134 | |||
135 | This section shows an example for how to join the [[TheThingsNetwork>>url:https://www.thethingsnetwork.org/]] LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure. | ||
136 | |||
137 | (% class="wikigeneratedid" _mstvisible="1" %) | ||
138 | [[image:1754549182417-132.png||height="306" width="777"]] | ||
139 | |||
140 | Assume the DLOS8 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the PF52 device in TTN V3 portal. | ||
141 | |||
142 | |||
143 | (% style="color:blue" %)**Step 1**(%%): Create a device in TTN V3 with the OTAA keys from PF52. | ||
144 | |||
145 | Each PF52 is shipped with a sticker with the default DEV EUI as below: | ||
146 | |||
147 | [[image:image-20230426083617-1.png||height="294" width="633"]] | ||
148 | |||
149 | |||
150 | Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot: | ||
151 | |||
152 | **Create the application.** | ||
153 | |||
154 | [[image:image-20250423093843-1.png||height="264" width="756"]](% style="display:none" %) | ||
155 | |||
156 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1||alt="image-20240907111305-2.png"]] | ||
157 | |||
158 | |||
159 | **Add devices to the created Application.** | ||
160 | |||
161 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111659-3.png?width=977&height=185&rev=1.1||alt="image-20240907111659-3.png"]] | ||
162 | |||
163 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1||alt="image-20240907111820-5.png"]] | ||
164 | |||
165 | |||
166 | **Enter end device specifics manually.** | ||
167 | |||
168 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1||alt="image-20240907112136-6.png"]] | ||
169 | |||
170 | |||
171 | **Add DevEUI and AppKey.** | ||
172 | |||
173 | **Customize a platform ID for the device.** | ||
174 | |||
175 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1||alt="image-20240907112427-7.png"]] | ||
176 | |||
177 | |||
178 | (% style="color:blue" %)**Step 2**(%%): Add decoder. | ||
179 | |||
180 | In TTN, user can add a custom payload so it shows friendly reading. | ||
181 | |||
182 | Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/]] | ||
183 | |||
184 | Below is TTN screen shot: | ||
185 | |||
186 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140556-1.png?width=1184&height=488&rev=1.1||alt="image-20241009140556-1.png"]] | ||
187 | |||
188 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140603-2.png?width=1168&height=562&rev=1.1||alt="image-20241009140603-2.png"]] | ||
189 | |||
190 | |||
191 | (% style="color:blue" %)**Step 3**(%%): Activate on PF52 | ||
192 | |||
193 | Press the ACT button for more than 3 seconds to activate PF52. | ||
194 | |||
195 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter **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. | ||
196 | |||
197 | After join success, it will start to upload messages to TTN V3 and you can see the messages in the panel. | ||
198 | |||
199 | [[image:image-20241128101717-1.png]] | ||
200 | |||
201 | |||
202 | == 2.3 Uplink Payload == | ||
203 | |||
204 | |||
205 | Uplink payloads include two types: Valid Sensor Value and other status / control command. | ||
206 | |||
207 | * Valid Sensor Value: Use FPORT=2 | ||
208 | * Other control command: Use FPORT other than 2. | ||
209 | |||
210 | === 2.3.1 Uplink FPORT~=5, Device Status === | ||
211 | |||
212 | |||
213 | Uplink the device configures with FPORT=5. Once PF52 Joined the network, it will uplink this message to the server. After first uplink, PF52 will uplink Device Status every 12 hours. | ||
214 | |||
215 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:370px" %) | ||
216 | |=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bytes)(% style="display:none" %) (%%)**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2** | ||
217 | |(% style="width:99px" %)Value|(% style="width:62px" %)Sensor Model|(% style="width:80px" %)Firmware Version|(% style="width:82px" %)Frequency Band|(% style="width:85px" %)Sub-band|(% style="width:46px" %)BAT | ||
218 | |||
219 | [[image:image-20241127165422-5.png]](% style="display:none" %) | ||
220 | |||
221 | |||
222 | Example Payload (FPort=5): 38 0A 00 01 FF 0C D2 | ||
223 | |||
224 | |||
225 | (% style="color:#4472c4" %)**Sensor Model**(%%): For PF52, this value is 0x38. | ||
226 | |||
227 | (% style="color:#4472c4" %)**Firmware Version**(%%): 0x0A00, Means: v1.0.0 version. | ||
228 | |||
229 | (% style="color:#4472c4" %)**Frequency Band**: | ||
230 | |||
231 | *0x01: EU868 | ||
232 | |||
233 | *0x02: US915 | ||
234 | |||
235 | *0x03: IN865 | ||
236 | |||
237 | *0x04: AU915 | ||
238 | |||
239 | *0x05: KZ865 | ||
240 | |||
241 | *0x06: RU864 | ||
242 | |||
243 | *0x07: AS923 | ||
244 | |||
245 | *0x08: AS923-1 | ||
246 | |||
247 | *0x09: AS923-2 | ||
248 | |||
249 | *0x0a: AS923-3 | ||
250 | |||
251 | |||
252 | (% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00) | ||
253 | |||
254 | (% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PF52. | ||
255 | |||
256 | (% style="color:#4472c4" %)**Ex1**(%%): 0x0CD2 = 3282mV | ||
257 | |||
258 | |||
259 | Use can also get the Device Status uplink through the downlink command: | ||
260 | |||
261 | (% style="color:#4472c4" %)**Downlink: **(%%)0x2601 | ||
262 | |||
263 | |||
264 | === 2.3.2 Uplink FPORT~=2, Real time sensor value === | ||
265 | |||
266 | |||
267 | PF52 will send this uplink after Device Status uplink once join LoRaWAN network successfully. And it will periodically send this uplink. Default interval is 20 minutes and [[can be changed>>||anchor="H3.1A0DownlinkCommandSet"]]. | ||
268 | |||
269 | Uplink uses FPORT=2 and every 20 minutes send one uplink by default. | ||
270 | |||
271 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:390px" %) | ||
272 | |=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( | ||
273 | **Size(bytes)** | ||
274 | )))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( | ||
275 | **2** | ||
276 | )))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( | ||
277 | **1** | ||
278 | )))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)((( | ||
279 | 4 | ||
280 | )))|=(% style="width: 60px; background-color: rgb(79, 129, 189); color: white;" %)((( | ||
281 | 4 | ||
282 | )))|=(% style="width: 60px; background-color: rgb(79, 129, 189); color: white;" %)((( | ||
283 | **4** | ||
284 | ))) | ||
285 | |(% style="width:97px" %)((( | ||
286 | Value | ||
287 | )))|(% style="width:39px" %)((( | ||
288 | BAT | ||
289 | )))|(% style="width:100px" %)((( | ||
290 | ((( | ||
291 | MOD | ||
292 | ))) | ||
293 | )))|(% style="width:77px" %)sysTimeCurrent|(% style="width:46px" %)OUT|(% style="width:34px" %)((( | ||
294 | INT | ||
295 | ))) | ||
296 | |||
297 | [[image:image-20241127162828-3.png||height="432" width="1144"]] | ||
298 | |||
299 | Example Payload (FPort=2): (% style="background-color:yellow" %)**0C D2 01 00 00 00 04 00 00 00 02** | ||
300 | |||
301 | |||
302 | ==== (% style="color:blue" %)**BAT:**(%%) ==== | ||
303 | |||
304 | * Example1: 0x0CD2/100=3.282 | ||
305 | * Example2: 0xCD8/100=3.288 | ||
306 | |||
307 | ==== (% style="color:blue" %)**MOD:**(%%) ==== | ||
308 | |||
309 | * MOD: 0x01=1 | ||
310 | |||
311 | ==== (% style="color:blue" %)**sysTimeCurrent:**(%%) ==== | ||
312 | |||
313 | PF52 use Unix TimeStamp format based on: | ||
314 | |||
315 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/AIS01-LB--LoRaWAN_AI_Image_End_Node_User_Manual/WebHome/1715151333259-453.png?rev=1.1||alt="1715151333259-453.png"]] | ||
316 | |||
317 | Users can get this time from the link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] : | ||
318 | |||
319 | Below is the converter example. | ||
320 | |||
321 | **Ex**:66B5C1B0=2024-08-09 07:13:52 | ||
322 | |||
323 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/AIS01-LB--LoRaWAN_AI_Image_End_Node_User_Manual/WebHome/image-20240809152956-5.png?width=788&height=402&rev=1.1||alt="image-20240809152956-5.png" height="402" width="788"]] | ||
324 | |||
325 | So, we can use AT+TIMESTAMP=1723187632 or downlink 66B5C1B0 to set the current time 2024 – August ~-~- 9 Friday 07:13:52 | ||
326 | |||
327 | |||
328 | ==== (% style="color:blue" %)**OUT**(%%) ==== | ||
329 | |||
330 | * Example1: 0x00000004=4 | ||
331 | |||
332 | ==== (% style="color:blue" %)**INT**(%%) ==== | ||
333 | |||
334 | * Example1: 0x00000002=2 | ||
335 | |||
336 | INT and OUT can be customized according to the situation, just swap the positions of INT and OUT in the decoder. | ||
337 | |||
338 | |||
339 | === 2.3.3 Decoder in TTN V3 === | ||
340 | |||
341 | |||
342 | In LoRaWAN protocol, the uplink payload is HEX format, user need to add a payload formatter/decoder in LoRaWAN Server to get human friendly string. | ||
343 | |||
344 | In TTN , add formatter as below: | ||
345 | |||
346 | [[image:image-20220621102026-10.png]] | ||
347 | |||
348 | ((( | ||
349 | Please check the decoder from this link: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/blob/main/PF52>>https://github.com/dragino/dragino-end-node-decoder/blob/main/PF52/PF52.txt]] | ||
350 | ))) | ||
351 | |||
352 | |||
353 | |||
354 | == 2.4 LED Indicator == | ||
355 | |||
356 | |||
357 | ((( | ||
358 | The PF52 has a triple color LED which for easy showing different stage. | ||
359 | ))) | ||
360 | |||
361 | |||
362 | ((( | ||
363 | (% style="color:#037691" %)**In a normal working state**: | ||
364 | ))) | ||
365 | |||
366 | * When the node is restarted, (% style="color:blue" %)**BLUE**(%%)** **are sequentially lit. | ||
367 | |||
368 | * During OTAA Join: | ||
369 | ** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once. | ||
370 | ** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds. | ||
371 | |||
372 | * After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once. | ||
373 | ** (% style="color:blue" %)**BLUE LED**(%%) when external sensor is connected | ||
374 | ** (% style="color:green" %)**GREEN LED**(%%) when external sensor is not connected | ||
375 | |||
376 | (% style="display:none" %) (%%) | ||
377 | |||
378 | == 2.5 Button == | ||
379 | |||
380 | |||
381 | Press the button PF52 will reset and join network again. | ||
382 | |||
383 | |||
384 | == 2.6 Bluetooth Transfer Screen == | ||
385 | |||
386 | |||
387 | To better manage and monitor PF52 devices, users can remotely control and manage the devices by downloading a specially designed mobile application. | ||
388 | |||
389 | Once the application is installed, the next step is to establish a Bluetooth connection between your smart device and PF52. | ||
390 | |||
391 | Please make sure that the Bluetooth function of your mobile phone is turned on and within the search range of the device (usually within 10 meters). | ||
392 | |||
393 | After opening the application, follow the on-screen prompts to complete the simple pairing process. | ||
394 | |||
395 | After a successful connection, the application will automatically detect the PF52 and start synchronizing the device status. | ||
396 | |||
397 | Once the connection is established, users can obtain high-definition real-time images captured by PF52 through the application. | ||
398 | |||
399 | [[image:image-20250109175450-1.jpeg||height="270" width="360"]] [[image:image-20250114113302-5.gif||height="271" width="236"]] | ||
400 | |||
401 | From the example, we can see that when a mobile phone is connected to PF52, it can observe the direction of a person and record data in real time. | ||
402 | |||
403 | |||
404 | = 3. Configure PF52 via AT command or LoRaWAN downlink = | ||
405 | |||
406 | |||
407 | Use can configure PF52 via AT Command or LoRaWAN Downlink. | ||
408 | |||
409 | * AT Command Connection: See [[FAQ>>||anchor="H4.FAQ"]]. | ||
410 | |||
411 | * LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] | ||
412 | |||
413 | There are two kinds of commands to configure PF52, they are: | ||
414 | |||
415 | * (% style="color:#4f81bd" %)**General Commands:** | ||
416 | |||
417 | These commands are to configure: | ||
418 | |||
419 | * General system settings like: uplink interval. | ||
420 | |||
421 | * LoRaWAN protocol & radio-related commands. | ||
422 | |||
423 | They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] | ||
424 | |||
425 | |||
426 | * (% style="color:#4f81bd" %)**Commands special design for PF52** | ||
427 | |||
428 | These commands are only valid for PF52, as below: | ||
429 | |||
430 | |||
431 | == 3.1 Downlink Command Set == | ||
432 | |||
433 | |||
434 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %) | ||
435 | |=(% style="width: 100px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 100px;background-color:#4F81BD;color:white" %)**Response**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**Downlink** | ||
436 | |(% style="width:161px" %)AT+TDC=?|(% style="width:138px" %)View current TDC time|(% style="width:243px" %)((( | ||
437 | 1200000 | ||
438 | OK | ||
439 | )))|(% style="width:1001px" %)Default 1200000(ms) | ||
440 | |(% style="width:161px" %)AT+TDC=300000|(% style="width:138px" %)Set TDC time|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
441 | 0X0100012C: | ||
442 | 01: fixed command | ||
443 | 00012C: 0X00012C=300(seconds) | ||
444 | ))) | ||
445 | |(% style="width:161px" %)ATZ|(% style="width:138px" %)Reset node|(% style="width:243px" %) |(% style="width:1001px" %)0x04FF | ||
446 | |(% style="width:161px" %)AT+FDR|(% style="width:138px" %)Restore factory settings|(% style="width:243px" %) |(% style="width:1001px" %)0X04FE | ||
447 | |(% style="width:161px" %)AT+CFM=?|(% style="width:138px" %)View the current confirmation mode status|(% style="width:243px" %)((( | ||
448 | 0 | ||
449 | OK | ||
450 | )))|(% style="width:1001px" %)Default 0 | ||
451 | |(% style="width:161px" %)AT+CFM=1|(% style="width:138px" %)Turn on confirmation mode|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
452 | 0x0500: close | ||
453 | 0x0501: open | ||
454 | 05: fixed command | ||
455 | ))) | ||
456 | |(% style="width:161px" %)AT+CHE=?|(% style="width:138px" %)View the current sub-band select 0-7, the default is 0|(% style="width:243px" %)((( | ||
457 | 0 | ||
458 | OK | ||
459 | )))|(% style="width:1001px" %)Default 0 | ||
460 | |(% style="width:161px" %)AT+CHE=2|(% style="width:138px" %)((( | ||
461 | Set subband to 2 | ||
462 | (CN470,US915,AU915) | ||
463 | )))|(% style="width:243px" %)((( | ||
464 | Attention:Take effect after ATZ | ||
465 | OK | ||
466 | )))|(% style="width:1001px" %)((( | ||
467 | 0X0702: | ||
468 | 07: fixed command | ||
469 | 02: Select subband 2 | ||
470 | ))) | ||
471 | |(% style="width:161px" %)AT+WMOD=?|(% style="width:138px" %)View the current alarm mode status|(% style="width:243px" %)((( | ||
472 | 0 | ||
473 | OK | ||
474 | )))|(% style="width:1001px" %)Default 0 | ||
475 | |(% style="width:161px" %)AT+WMOD=1|(% style="width:138px" %)Turn on alarm mode|(% style="width:243px" %)((( | ||
476 | Attention:Take effect after ATZ | ||
477 | OK | ||
478 | )))|(% style="width:1001px" %)((( | ||
479 | 0xA501: open | ||
480 | 0XA500: close | ||
481 | A5: fixed command | ||
482 | ))) | ||
483 | |(% style="width:161px" %)AT+CITEMP=?|(% style="width:138px" %)View the current temperature detection time interval|(% style="width:243px" %)((( | ||
484 | 1 | ||
485 | OK | ||
486 | )))|(% style="width:1001px" %)Default 1(min) | ||
487 | |(% style="width:161px" %)AT+CITEMP=2|(% style="width:138px" %)Set the temperature detection time interval to 2min|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
488 | 0XA70002 | ||
489 | A7: fixed command | ||
490 | 0002: 0X0002=2(min) | ||
491 | ))) | ||
492 | |(% style="width:161px" %)AT+NJM=?|(% style="width:138px" %)Check the current network connection method|(% style="width:243px" %)((( | ||
493 | 1 | ||
494 | OK | ||
495 | )))|(% style="width:1001px" %)Default 1 | ||
496 | |(% style="width:161px" %)AT+NJM=0|(% style="width:138px" %)Change the network connection method to ABP|(% style="width:243px" %)((( | ||
497 | Attention:Take effect after ATZ | ||
498 | OK | ||
499 | )))|(% style="width:1001px" %)((( | ||
500 | 0X2000: ABP | ||
501 | 0x2001: OTAA | ||
502 | 20: fixed command | ||
503 | ))) | ||
504 | |(% style="width:161px" %)AT+RPL=?|(% style="width:138px" %)View current RPL settings|(% style="width:243px" %)((( | ||
505 | 0 | ||
506 | OK | ||
507 | )))|(% style="width:1001px" %)Default 0 | ||
508 | |(% style="width:161px" %)AT+RPL=1|(% style="width:138px" %)set RPL=1|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
509 | 0x2101: | ||
510 | 21: fixed command | ||
511 | 01: for details, check wiki | ||
512 | ))) | ||
513 | |(% style="width:161px" %)AT+ADR=?|(% style="width:138px" %)View current ADR status|(% style="width:243px" %)((( | ||
514 | 1 | ||
515 | OK | ||
516 | )))|(% style="width:1001px" %)Default 0 | ||
517 | |(% style="width:161px" %)AT+ADR=0|(% style="width:138px" %)Set the ADR state to off|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
518 | 0x2200: close | ||
519 | 0x2201: open | ||
520 | 22: fixed command | ||
521 | ))) | ||
522 | |(% style="width:161px" %)AT+DR=?|(% style="width:138px" %)View the current DR settings|(% style="width:243px" %)OK|(% style="width:1001px" %) | ||
523 | |(% style="width:161px" %)AT+DR=1|(% style="width:138px" %)((( | ||
524 | set DR to 1 | ||
525 | It takes effect only when ADR=0 | ||
526 | )))|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
527 | 0X22000100: | ||
528 | 00: ADR=0 | ||
529 | 01: DR=1 | ||
530 | 00: TXP=0 | ||
531 | 22: fixed command | ||
532 | ))) | ||
533 | |(% style="width:161px" %)AT+TXP=?|(% style="width:138px" %)View the current TXP|(% style="width:243px" %)OK|(% style="width:1001px" %) | ||
534 | |(% style="width:161px" %)AT+TXP=0|(% style="width:138px" %)((( | ||
535 | set TXP to 0 | ||
536 | It takes effect only when ADR=0 | ||
537 | )))|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
538 | 0X22000100: | ||
539 | 00: ADR=0 | ||
540 | 01: DR=1 | ||
541 | 00: TXP=0 | ||
542 | 22: fixed command | ||
543 | ))) | ||
544 | |(% style="width:161px" %) |(% style="width:138px" %)Upload node configuration or DS18B20 ID|(% style="width:243px" %) |(% style="width:1001px" %)((( | ||
545 | 0X2301:Upload node configuration | ||
546 | 0x2302: Upload DS18B20 ID | ||
547 | 23: fixed command | ||
548 | ))) | ||
549 | |(% style="width:161px" %)AT+DWELL=?|(% style="width:138px" %)Check the high-rate upload settings|(% style="width:243px" %)((( | ||
550 | 1 | ||
551 | OK | ||
552 | )))|(% style="width:1001px" %)Default 1 | ||
553 | |(% style="width:161px" %)AT+DWELL=1|(% style="width:138px" %)((( | ||
554 | Set high rate upload | ||
555 | (AS923,AU915) | ||
556 | )))|(% style="width:243px" %)((( | ||
557 | Attention:Take effect after ATZ | ||
558 | OK | ||
559 | )))|(% style="width:1001px" %)((( | ||
560 | 0x2501: close | ||
561 | 0x2500: open | ||
562 | 25: fixed command | ||
563 | for details, check wiki | ||
564 | ))) | ||
565 | |(% style="width:161px" %)AT+RJTDC=?|(% style="width:138px" %)View current RJTDC set time|(% style="width:243px" %)((( | ||
566 | 20 | ||
567 | OK | ||
568 | )))|(% style="width:1001px" %)Default 20(min) | ||
569 | |(% style="width:161px" %)AT+RJTDC=10|(% style="width:138px" %)Set RJTDC time interval|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
570 | 0X26000A: | ||
571 | 26: fixed command | ||
572 | 000A: 0X000A=10(min) | ||
573 | for details, check wiki | ||
574 | ))) | ||
575 | |(% style="width:161px" %) |(% style="width:138px" %)Retrieve stored data for a specified period of time|(% style="width:243px" %) |(% style="width:1001px" %)((( | ||
576 | 0X3161DE7C7061DE8A800A: | ||
577 | 31: fixed command | ||
578 | 61DE7C70:0X61DE7C70=2022/1/12 15:00:00 | ||
579 | 61DE8A80:0X61DE8A80=2022/1/12 16:00:00 | ||
580 | 0A: 0X0A=10(second) | ||
581 | View details 2.6.2 | ||
582 | ))) | ||
583 | |(% style="width:161px" %)AT+DDETECT=?|(% style="width:138px" %)View the current DDETECT setting status and time|(% style="width:243px" %)((( | ||
584 | 0,1440 | ||
585 | OK | ||
586 | )))|(% style="width:1001px" %)Default 0,1440(min) | ||
587 | |(% style="width:161px" %)AT+DDETECT=1,1440,2880|(% style="width:138px" %)((( | ||
588 | Set DDETECT setting status and time | ||
589 | ((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%)) | ||
590 | )))|(% style="width:243px" %)OK|(% style="width:1001px" %)((( | ||
591 | 0X320005A0: close | ||
592 | 0X320105A0: open | ||
593 | 32: fixed command | ||
594 | 05A0: 0X05A0=1440(min) | ||
595 | ))) | ||
596 | |(% style="width:161px" %) |(% style="width:138px" %)((( | ||
597 | Downlink Modification Alarm Mode | ||
598 | (AT+WMOD,AT+CITEMP,AT+ARTEMP) | ||
599 | )))|(% style="width:243px" %) |(% style="width:1001px" %)((( | ||
600 | 0XAA010002000F00032: | ||
601 | AA: fixed command | ||
602 | 01: 0X01=1(AT+MOD) | ||
603 | 0002: 0X0002=2(AT+CITEMP) | ||
604 | 000F: 0X000F=15(AT+ARTEMP) | ||
605 | 0032: 0X0032=50(AT+ARTEMP) | ||
606 | ))) | ||
607 | |||
608 | == 3.2 Set Password == | ||
609 | |||
610 | |||
611 | Feature: Set device password, max 9 digits. | ||
612 | |||
613 | (% style="color:#4f81bd" %)**AT Command: AT+PWORD** | ||
614 | |||
615 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %) | ||
616 | |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response** | ||
617 | |(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)((( | ||
618 | 123456 | ||
619 | OK | ||
620 | ))) | ||
621 | |(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK | ||
622 | |||
623 | (% style="color:#4f81bd" %)**Downlink Command:** | ||
624 | |||
625 | No downlink command for this feature. | ||
626 | |||
627 | |||
628 | = 4. FAQ = | ||
629 | |||
630 | == 4.1 AT Command and Downlink == | ||
631 | |||
632 | |||
633 | ((( | ||
634 | Sending ATZ will reboot the node | ||
635 | ))) | ||
636 | |||
637 | ((( | ||
638 | Sending AT+FDR will restore the node to factory settings | ||
639 | ))) | ||
640 | |||
641 | ((( | ||
642 | Get the node's AT command setting by sending AT+CFG | ||
643 | ))) | ||
644 | |||
645 | ((( | ||
646 | |||
647 | ))) | ||
648 | |||
649 | ((( | ||
650 | **Example:** | ||
651 | ))) | ||
652 | |||
653 | ((( | ||
654 | AT+VER=EU868 v1.0 | ||
655 | ))) | ||
656 | |||
657 | ((( | ||
658 | AT+NJM=1 | ||
659 | ))) | ||
660 | |||
661 | ((( | ||
662 | AT+DEUI=25 32 12 45 65 26 12 35 | ||
663 | ))) | ||
664 | |||
665 | ((( | ||
666 | AT+APPEUI=25 32 12 45 65 26 32 16 | ||
667 | ))) | ||
668 | |||
669 | ((( | ||
670 | AT+APPKEY=25 32 12 45 65 26 32 16 89 48 85 65 45 87 89 55 | ||
671 | ))) | ||
672 | |||
673 | ((( | ||
674 | AT+DADDR=00 00 00 00 | ||
675 | ))) | ||
676 | |||
677 | ((( | ||
678 | AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ||
679 | ))) | ||
680 | |||
681 | ((( | ||
682 | AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ||
683 | ))) | ||
684 | |||
685 | ((( | ||
686 | AT+NWKID=00 00 00 13 | ||
687 | ))) | ||
688 | |||
689 | ((( | ||
690 | AT+ADR=1 | ||
691 | ))) | ||
692 | |||
693 | ((( | ||
694 | AT+DR=5 | ||
695 | ))) | ||
696 | |||
697 | ((( | ||
698 | AT+TXP=0 | ||
699 | ))) | ||
700 | |||
701 | ((( | ||
702 | AT+CHS=0 | ||
703 | ))) | ||
704 | |||
705 | ((( | ||
706 | AT+CLASS=A | ||
707 | ))) | ||
708 | |||
709 | ((( | ||
710 | AT+CFM=0 | ||
711 | ))) | ||
712 | |||
713 | ((( | ||
714 | AT+JN1DL=5000 | ||
715 | ))) | ||
716 | |||
717 | ((( | ||
718 | AT+JN2DL=6000 | ||
719 | ))) | ||
720 | |||
721 | ((( | ||
722 | AT+RX1DL=5000 | ||
723 | ))) | ||
724 | |||
725 | ((( | ||
726 | AT+RX2DL=6000 | ||
727 | ))) | ||
728 | |||
729 | ((( | ||
730 | AT+RX1WTO=24 | ||
731 | ))) | ||
732 | |||
733 | ((( | ||
734 | AT+RX2WTO=6 | ||
735 | ))) | ||
736 | |||
737 | ((( | ||
738 | AT+RX2FQ=869525000 | ||
739 | ))) | ||
740 | |||
741 | ((( | ||
742 | AT+RX2DR=0 | ||
743 | ))) | ||
744 | |||
745 | ((( | ||
746 | AT+RPL=0 | ||
747 | ))) | ||
748 | |||
749 | ((( | ||
750 | AT+FCU=6 | ||
751 | ))) | ||
752 | |||
753 | ((( | ||
754 | AT+FCD=0 | ||
755 | ))) | ||
756 | |||
757 | ((( | ||
758 | AT+CFS=0 | ||
759 | ))) | ||
760 | |||
761 | ((( | ||
762 | AT+NJS=1 | ||
763 | ))) | ||
764 | |||
765 | ((( | ||
766 | AT+DCS=0 | ||
767 | ))) | ||
768 | |||
769 | ((( | ||
770 | AT+PNM=1 | ||
771 | ))) | ||
772 | |||
773 | ((( | ||
774 | AT+PWORD=123456 | ||
775 | ))) | ||
776 | |||
777 | ((( | ||
778 | AT+EXT=1 | ||
779 | ))) | ||
780 | |||
781 | ((( | ||
782 | AT+TDC=120000 | ||
783 | ))) | ||
784 | |||
785 | ((( | ||
786 | AT+TIMESTAMP=1640851037 2021 12 30 7 57 17 | ||
787 | ))) | ||
788 | |||
789 | ((( | ||
790 | AT+RJTDC=20 | ||
791 | ))) | ||
792 | |||
793 | ((( | ||
794 | AT+DDETECT=0,1440 | ||
795 | ))) | ||
796 | |||
797 | ((( | ||
798 | AT+WMOD=0 | ||
799 | ))) | ||
800 | |||
801 | ((( | ||
802 | AT+CITEMP=1 | ||
803 | ))) | ||
804 | |||
805 | ((( | ||
806 | AT+ARTEMP=-40,125 | ||
807 | |||
808 | |||
809 | ))) | ||
810 | |||
811 | == 4.2 How to upgrade the firmware? == | ||
812 | |||
813 | |||
814 | PF52 requires a program converter to upload images to PF52, which is used to upload image to PF52 for: | ||
815 | |||
816 | * Support new features | ||
817 | * For bug fix | ||
818 | * Change LoRaWAN bands. | ||
819 | |||
820 | ((( | ||
821 | User can check this link for the detail of operation of firmware upgrade: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction.WebHome||anchor="H2.3LHT52"]] | ||
822 | ))) | ||
823 | |||
824 | |||
825 | |||
826 | |||
827 | |||
828 | |||
829 | |||
830 | |||
831 | |||
832 | |||
833 | |||
834 | |||
835 | |||
836 | = 5. Order Info = | ||
837 | |||
838 | == 5.1 Main Device == | ||
839 | |||
840 | |||
841 | ((( | ||
842 | Part Number: (% style="color:#4472c4" %)**SCA01L-XX** | ||
843 | ))) | ||
844 | |||
845 | ((( | ||
846 | (% style="color:#4472c4" %)**XX **(%%): The default frequency band | ||
847 | ))) | ||
848 | |||
849 | * (% style="color:red" %)**AS923**(%%)**: **LoRaWAN AS923 band | ||
850 | * (% style="color:red" %)**AU915**(%%)**: **LoRaWAN AU915 band | ||
851 | * (% style="color:red" %)**EU433**(%%)**: **LoRaWAN EU433 band | ||
852 | * (% style="color:red" %)**EU868**(%%)**:** LoRaWAN EU868 band | ||
853 | * (% style="color:red" %)**KR920**(%%)**: **LoRaWAN KR920 band | ||
854 | * (% style="color:red" %)**US915**(%%)**: **LoRaWAN US915 band | ||
855 | * (% style="color:red" %)**IN865**(%%)**: **LoRaWAN IN865 band | ||
856 | * (% style="color:red" %)**CN470**(%%)**: **LoRaWAN CN470 band | ||
857 | |||
858 | = 6. Packing Info = | ||
859 | |||
860 | |||
861 | **Package Includes**: | ||
862 | |||
863 | * PF52 x 1 | ||
864 | |||
865 | = 7. Support = | ||
866 | |||
867 | |||
868 | * 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. | ||
869 | * 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:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. | ||
870 | |||
871 | = 8. FCC Warning = | ||
872 | |||
873 | |||
874 | This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions: | ||
875 | |||
876 | (1) This device may not cause harmful interference; | ||
877 | |||
878 | (2) this device must accept any interference received,including interference that may cause undesired operation. | ||
879 | |||
880 | |||
881 | = 9. Appendix I:According to the use = | ||
882 | |||
883 | |||
884 | Installed in the middle of the aisle threshold, it can detect the entire aisle to avoid omissions. | ||
885 | |||
886 | Installation height limit 2.2m-2.5m. | ||
887 | |||
888 | [[image:image-20241128113808-6.png||height="627" width="416"]] | ||
889 | |||
890 | When pedestrians pass by, the image can be viewed through the BLE app. | ||
891 | |||
892 | [[image:1753432832193-208.png||height="392" width="346"]][[image:1753432851170-761.png||height="393" width="346"]] |