Wiki source code of RS485 Configure Tool
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | |||
| 47 | |||
| 48 | == 3.1 General Configure: == | ||
| 49 | |||
| 50 | |||
| 51 | * (% style="color:blue" %)**Port **(%%): COM port in PC to connect to RS485 End Node. | ||
| 52 | |||
| 53 | * (% style="color:blue" %)**Node Baud Rate **(%%): The Baud Rate for RS485 End Node. | ||
| 54 | |||
| 55 | * (% style="color:blue" %)**5VT **(%%): 5v Power_On_Duration for external RS485 Sensors. Unit: ms. | ||
| 56 | |||
| 57 | * (% style="color:blue" %)**Connect End Node **(%%): Connect to RS485 End Node. | ||
| 58 | |||
| 59 | * (% style="color:blue" %)**Disconnect End Node **(%%): Disconnect RS485 End Node. | ||
| 60 | |||
| 61 | * (% style="color:blue" %)**Sensor Baud Rate **(%%): Baud Rate of RS485 Sensors. | ||
| 62 | |||
| 63 | * (% style="color:blue" %)**Sensor Data Bit **(%%): Data Bit of RS485 Sensors | ||
| 64 | |||
| 65 | * (% style="color:blue" %)**Sensor Check Bit **(%%): Check Bit of RS485 Sensors. | ||
| 66 | |||
| 67 | * (% style="color:blue" %)**Sensor Stop Bit **(%%): Stop Bit of RS485 Sensors | ||
| 68 | |||
| 69 | * (% style="color:blue" %)**Configure Devices **(%%): Send General Configure Command to End Node. | ||
| 70 | |||
| 71 | == 3.2 Console Window: == | ||
| 72 | |||
| 73 | |||
| 74 | After **Connect End Node**. The Console Window will shows all the output from RS485 End Node. | ||
| 75 | |||
| 76 | User can also Send AT Commands to RS485 End Node in this window. | ||
| 77 | |||
| 78 | [[image:image-20230928233408-3.png||_mstalt="432289"]] | ||
| 79 | |||
| 80 | |||
| 81 | == 3.3 RS485 Commands to Sensor == | ||
| 82 | |||
| 83 | |||
| 84 | This area is used to configure what RS485 Commands the End Node should send to the RS485 sensors to get the sensor value. | ||
| 85 | |||
| 86 | * There are totally 15 commands max. | ||
| 87 | |||
| 88 | * Each command should be set according to the sensor manual. | ||
| 89 | |||
| 90 | * 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). | ||
| 91 | |||
| 92 | * User should calculate the CRC if needed | ||
| 93 | |||
| 94 | **Example**: | ||
| 95 | |||
| 96 | * 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. | ||
| 97 | |||
| 98 | **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. | ||
| 99 | |||
| 100 | |||
| 101 | == 3.4 Process Sensor Returns == | ||
| 102 | |||
| 103 | |||
| 104 | 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**. | ||
| 105 | |||
| 106 | **Example:** | ||
| 107 | |||
| 108 | User configure below commands : | ||
| 109 | |||
| 110 | * Poll Command 1: 04 03 00 00 00 02 C4 52 | ||
| 111 | |||
| 112 | * Poll Command 3: 08 03 00 00 00 02 C4 92 | ||
| 113 | |||
| 114 | * Poll Command 5: 11 03 00 00 00 02 C6 9B | ||
| 115 | |||
| 116 | Then Click "Test RS485 Commands". End Node will then send these three commands to RS485 sensors one by one and waiting for returns. | ||
| 117 | |||
| 118 | Their returnes will be shown in "RS485 Return Data" Area, such as below: | ||
| 119 | |||
| 120 | [[image:image-20230930193108-1.png||_mstalt="430235"]] | ||
| 121 | |||
| 122 | Use can choose to get "Discrete Data Bytes" or "Bytes Blocks": | ||
| 123 | |||
| 124 | [[image:image-20230930193257-2.png||_mstalt="432198"]] Select the 1st ~~ 3rd bytes from the return. | ||
| 125 | |||
| 126 | [[image:image-20230930193357-3.png||_mstalt="432874"]] Select the 3rd, 6th, 9th bytes from the return. | ||
| 127 | |||
| 128 | [[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. | ||
| 129 | |||
| 130 | |||
| 131 | Below is the full screen shot: | ||
| 132 | |||
| 133 | [[image:image-20230930193658-5.png||_mstalt="434876" height="735" width="1146"]] | ||
| 134 | |||
| 135 | |||
| 136 | (% 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. | ||
| 137 | |||
| 138 | (% 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. | ||
| 139 | |||
| 140 | |||
| 141 | == 3.5 Commands Previwe Window == | ||
| 142 | |||
| 143 | |||
| 144 | This window show the commands to be flash into the RS485 end node. | ||
| 145 | |||
| 146 | * (% style="color:blue" %)**Import Commands **(%%): Import commands from txt. | ||
| 147 | |||
| 148 | * (% style="color:blue" %)**Save Commands **(%%): Save commands to a txt. | ||
| 149 | |||
| 150 | * (% style="color:blue" %)**Write **(%%): Write Commands to End Node | ||
| 151 | |||
| 152 | * (% style="color:blue" %)**Erase All **(%%): Clear All Configured Commands in the RS485. It won't erase the commands shows in the preview window. | ||
| 153 | |||
| 154 | == Change Log: == | ||
| 155 | |||
| 156 | === v1.1: === | ||
| 157 | |||
| 158 | 1.No spaces are required between each byte of the inquiry frame | ||
| 159 | |||
| 160 | 2.Improve the prompt box | ||
| 161 | |||
| 162 | 3.AT instruction coverage function | ||
| 163 | |||
| 164 | 4.Button function prompt | ||
| 165 | |||
| 166 | === V1.2: === | ||
| 167 | |||
| 168 | 1.Fixed overwrite failure when AT instruction has multiple parameters | ||
| 169 | |||
| 170 | 2.Add Payload Structure Window | ||
| 171 | |||
| 172 | = TODO: = | ||
| 173 | |||
| 174 | ~1. Add Payload Structure Window(Done at v1.2) | ||
| 175 | |||
| 176 | 2. Modify Chars to looks nicer ( Done at v1.1) | ||
| 177 | |||
| 178 |