Wiki source code of RS485 Configure Tool

Last modified by Herong Lu on 2024/03/11 17:31
Show last authors
1 = **Table of Contents：** =
2
3 {{toc/}}
4
5
6
7 = 1. What is Dragino RS485 Configure Tool? =
8
9
10 Dragino RS485 tool is designed to provide a friendly way to user to configure Dragino RS485 Wireless Sensor such as : **RS485-LN**, **RS485-LB**, **RS485-BL**, **RS485-NB**.
11
12 The RS485 tool provide below features:
13
14 * A Console window which use can do debug via AT Commands.
15
16 * Test the poll command to RS485 sensors.
17
18 * See return from RS485 sensors and preview process command for returns.
19
20 * Generate the AT Commands after debuging.
21
22 * Write the AT Commands to end node in batch.
23
24 * Import / Export commands
25
26 = 2. Hardware Connection =
27
28
29 To use Dragino RS485 Configure Tool. User need to run the tool in PC and use the TTL connection to Dragino End Node, and RS485 end node should connect to the RS485 Sensors for debug or configure.
30
31 **[[Download RS485 Configure Tool>>https://www.dropbox.com/sh/us9qecn39fwt8n1/AABREdqUCzEmJMRrfuWuXasoa?dl=0]]**.
32
33 [[image:image-20230928230446-1.png||_mstalt="431288" height="275" width="471"]]
34
35 = 3. Use the tool =
36
37 == Overview ==
38
39
40 Below is the block diagram of the RS485 Tool:
41
42 [[image:image-20230928235259-4.png||_mstalt="434590" height="681" width="915"]]
43
44 Below is the block diagram of the RS485 Tool V1.2:
45
46 [[image:image-20231010145454-2.png||_mstalt="428597" height="689" width="921"]]
47
48
49 == 3.1 General Configure: ==
50
51
52 * (% style="color:blue" %)**Port **(%%): COM port in PC to connect to RS485 End Node.
53
54 * (% style="color:blue" %)**Node Baud Rate **(%%): The Baud Rate for RS485 End Node.
55
56 * (% style="color:blue" %)**5VT **(%%): 5v Power_On_Duration for external RS485 Sensors. Unit: ms.
57
58 * (% style="color:blue" %)**Connect End Node **(%%): Connect to RS485 End Node.
59
60 * (% style="color:blue" %)**Disconnect End Node **(%%): Disconnect RS485 End Node.
61
62 * (% style="color:blue" %)**Sensor Baud Rate **(%%): Baud Rate of RS485 Sensors.
63
64 * (% style="color:blue" %)**Sensor Data Bit **(%%): Data Bit of RS485 Sensors
65
66 * (% style="color:blue" %)**Sensor Check Bit **(%%): Check Bit of RS485 Sensors.
67
68 * (% style="color:blue" %)**Sensor Stop Bit **(%%): Stop Bit of RS485 Sensors
69
70 * (% style="color:blue" %)**Configure Devices **(%%): Send General Configure Command to End Node.
71
72 == 3.2 Console Window: ==
73
74
75 After **Connect End Node**. The Console Window will shows all the output from RS485 End Node.
76
77 User can also Send AT Commands to RS485 End Node in this window.
78
79 [[image:image-20230928233408-3.png||_mstalt="432289"]]
80
81
82 == 3.3 RS485 Commands to Sensor ==
83
84
85 This area is used to configure what RS485 Commands the End Node should send to the RS485 sensors to get the sensor value.
86
87 * There are totally 15 commands max.
88
89 * Each command should be set according to the sensor manual.
90
91 * It is HEX format and no need 0x. Each byte should have a space in between (will be fix in next version so no need space).
92
93 * User should calculate the CRC if needed
94
95 **Example**:
96
97 * Sensor Command: FE 03 00 00 00 03 11 C4  (11 C4 is CRC). User need to input: FE 03 00 00 00 03 11 C4 as poll command.
98
99 **Test RS485 Commands**: After configure poll commands. Click this button then the tool will generate related AT+COMMANDS and send to the End node to test and get return.
100
101
102 == 3.4 Process Sensor Returns ==
103
104
105 RS485 sensors will return a string, to make it more efficient to process via LoRaWAN packets, we can fetch the valid chars from the returns in the **process sensor returns area**.
106
107 **Example:**
108
109 User configure below commands :
110
111 * Poll Command 1: 04 03 00 00 00 02 C4 52
112
113 * Poll Command 3: 08 03 00 00 00 02 C4 92
114
115 * Poll Command 5: 11 03 00 00 00 02 C6 9B
116
117 Then Click "Test RS485 Commands". End Node will then send these three commands to RS485 sensors one by one and waiting for returns.
118
119 Their returnes will be shown in "RS485 Return Data" Area, such as below:
120
121 [[image:image-20230930193108-1.png||_mstalt="430235"]]
122
123 Use can choose to get "Discrete Data Bytes" or "Bytes Blocks":
124
125 [[image:image-20230930193257-2.png||_mstalt="432198"]] Select the 1st ~~ 3rd bytes from the return.
126
127 [[image:image-20230930193357-3.png||_mstalt="432874"]] Select the 3rd, 6th, 9th bytes from the return.
128
129 [[image:image-20230930193456-4.png||_mstalt="433212"]] After select the byte fetch method. User can see preview the result. This photo shows to fetch the Block 1~~3 from the first return.
130
131 [[image:image-20231010150227-4.png||_mstalt="427531"]] Based on the AT command in the preview window, the node will upload data in the format of the left image
132
133 Below is the full screen shot:
134
135 [[image:image-20231010150054-3.png||_mstalt="426504"]]
136
137
138 (% style="color:blue" %)**AT+CMDDL**(%%): This specify the delay for RS485 End Node to wait for the RS485 sensors return. If RS485 sensors doesn't reply in this time. End Node will consider there is no reply.
139
140 (% style="color:blue" %)**Generate AT Instructions**(%%): After All testing goes fine with Poll Command & Return Process. User can press this button to generate the AT Commands which is for the Ene Node.
141
142
143 == 3.5 Commands Previwe Window ==
144
145
146 This window show the commands to be flash into the RS485 end node.
147
148 * (% style="color:blue" %)**Import Commands **(%%): Import commands from txt.
149
150 * (% style="color:blue" %)**Save Commands **(%%): Save commands to a txt.
151
152 * (% style="color:blue" %)**Write **(%%): Write Commands to End Node
153
154 * (% style="color:blue" %)**Erase All **(%%): Clear All Configured Commands in the RS485. It won't erase the commands shows in the preview window.
155
156 == 3.6 Reference video ==
157
158 link:[[https:~~/~~/youtu.be/l9fLE3ekY4I>>https://youtu.be/l9fLE3ekY4I]]
159
160 == Change Log: ==
161
162 === v1.1: ===
163
164 1.No spaces are required between each byte of the inquiry frame
165
166 2.Improve the prompt box
167
168 3.AT instruction coverage function
169
170 4.Button function prompt
171
172 === V1.2: ===
173
174 1.Fixed overwrite failure when AT instruction has multiple parameters
175
176 2.Add Payload Structure Window
177
178 === V1.3: ===
179
180 Fixed bug in V1.2
181
182 1.When the input cut value exceeds the number of bytes returned, an incorrect AT instruction will be generated
183
184 New:
185
186 1.Control the inquiry time input box between inquiry frames
187
188 2.The inquiry frame does not require CRC verification input
189
190 [[image:image-20240311144211-2.png]]
191
192 = TODO: =
193
194 ~1. Add Payload Structure Window(Done at v1.2)
195
196 2. Modify Chars to looks nicer  ( Done at v1.1)

Applications

Navigation

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