Changes for page 08 Communication
Last modified by Iris on 2025/07/24 15:23
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Servo. 1 UserManual.02 VD2 SA Series.WebHome1 +Servo.Manual.02 VD2 SA Series.WebHome - Content
-
... ... @@ -11,7 +11,7 @@ 11 11 12 12 Figure 8-1 The position of RS485 communication port of VD2B drive 13 13 14 -For the position of the RS485 communication port of other models, see __[[4.5 Communication signal wiring>>https://docs.we-con.com.cn/bin/view/Servo/ 2.%20User%20Manual/06%20VD2%20SA%20Series%20Servo%20Drives%20Manual%20%28Full%20V1.1%29/04%20Wiring/#HCommunicationsignalwiring]]__.14 +For the position of the RS485 communication port of other models, see __[[4.5 Communication signal wiring>>https://docs.we-con.com.cn/bin/view/Servo/Manual/02%20VD2%20SA%20Series/04%20Wiring/#HCommunicationsignalwiring]]__. 15 15 16 16 The servo drive adopts RS485 half-duplex communication mode. The 485 bus should adopt the hand-in-hand structure instead of the star structure or the bifurcated structure. The star structure or bifurcation structure will produce reflected signals, which will affect the 485 communication. 17 17 ... ... @@ -45,7 +45,7 @@ 45 45 The VD2 series servo drives currently support the RTU communication format. The typical data frame format is shown in the table. 46 46 47 47 (% class="table-bordered" %) 48 -|(% rowspan="2" style="text-align:center; vertical-align:middle; width:425px" %)**There should be a message interval not less than 3.5 characters at the beginning**|(% style="text-align:center; vertical-align:middle; width:166px" %)**Address**|(% style="text-align:center; vertical-align:middle; width:189px" %)**Function code**|(% style="text-align:center; vertical-align:middle; width:155px" %)**Data**|(% style="text-align:center; vertical-align:middle; width:158px" %)**CRC check code** 48 +|=(% rowspan="2" scope="row" style="text-align: center; vertical-align: middle; width: 425px;" %)**There should be a message interval not less than 3.5 characters at the beginning**|=(% style="text-align: center; vertical-align: middle; width: 166px;" %)**Address**|=(% style="text-align: center; vertical-align: middle; width: 189px;" %)**Function code**|=(% style="text-align: center; vertical-align: middle; width: 155px;" %)**Data**|=(% style="text-align: center; vertical-align: middle; width: 158px;" %)**CRC check code** 49 49 |(% style="text-align:center; vertical-align:middle; width:166px" %)1 byte|(% style="text-align:center; vertical-align:middle; width:189px" %)1 byte|(% style="text-align:center; vertical-align:middle; width:155px" %)N bytes|(% style="text-align:center; vertical-align:middle; width:158px" %)2 bytes 50 50 51 51 == **Description of supported function codes** == ... ... @@ -53,7 +53,7 @@ 53 53 The host reads and writes data to the servo through Modbus RTU format (03, 06 function codes). The corresponding Modbus function codes are as follows: 54 54 55 55 (% class="table-bordered" %) 56 -|(% style="text-align:center; vertical-align:middle" %)**Operate**|(% style="text-align:center; vertical-align:middle" %)**Command code** 56 +|=(% style="text-align: center; vertical-align: middle;" %)**Operate**|=(% style="text-align: center; vertical-align: middle;" %)**Command code** 57 57 |(% style="text-align:center; vertical-align:middle" %)Read 16-bit/32-bit function code|(% style="text-align:center; vertical-align:middle" %)0x03 58 58 |(% style="text-align:center; vertical-align:middle" %)Write 16-bit function code|(% style="text-align:center; vertical-align:middle" %)0x06 59 59 |(% style="text-align:center; vertical-align:middle" %)Write 32-bit function code|(% style="text-align:center; vertical-align:middle" %)0x10 ... ... @@ -68,9 +68,10 @@ 68 68 69 69 Correct response format: 70 70 71 -|(% rowspan="2" %)**Address**|(% rowspan="2" %)**Function code**|(% rowspan="2" %)**Number of bytes of returned data**|(% colspan="2" %)**Register 1**|(% rowspan="2" %)**…**|(% rowspan="2" %)**CRC check code** 72 -|**high byte**|**low byte** 73 -|1 byte|03|1 byte|1 byte|1 byte|…|2 bytes 71 +(% style="width:1055px" %) 72 +|(% rowspan="2" %)**Address**|(% rowspan="2" %)**Function code**|(% rowspan="2" style="width:279px" %)**Number of bytes of returned data**|(% colspan="2" style="width:274px" %)**Register 1**|(% rowspan="2" style="width:98px" %)**…**|(% rowspan="2" %)**CRC check code** 73 +|(% style="width:160px" %)**high byte**|(% style="width:114px" %)**low byte** 74 +|1 byte|03|(% style="width:279px" %)1 byte|(% style="width:160px" %)1 byte|(% style="width:114px" %)1 byte|(% style="width:98px" %)…|2 bytes 74 74 75 75 **Write function code: 0x06** 76 76 ... ... @@ -90,8 +90,8 @@ 90 90 91 91 If the setting is successful, the original is returned 92 92 93 -|(% rowspan="2" %)**There should be a message interval not less than 3.5 characters at the beginning**|**Address**|**Function code**|**Data**|**CRC check code** 94 -|1 byte|1 byte|N bytes|2 bytes 94 +|(% rowspan="2" style="width:551px" %)**There should be a message interval not less than 3.5 characters at the beginning**|(% style="width:114px" %)**Address**|(% style="width:127px" %)**Function code**|(% style="width:104px" %)**Data**|(% style="width:180px" %)**CRC check code** 95 +|(% style="width:114px" %)1 byte|(% style="width:127px" %)1 byte|(% style="width:104px" %)N bytes|(% style="width:180px" %)2 bytes 95 95 96 96 (% style="color:inherit; font-family:inherit; font-size:26px" %)**CRC check** 97 97 ... ... @@ -150,13 +150,13 @@ 150 150 == **Error response frame** == 151 151 152 152 (% class="table-bordered" %) 153 -|(% style="text-align:center; vertical-align:middle" %)**Address**|(% style="text-align:center; vertical-align:middle" %)**Function code**|(% style="text-align:center; vertical-align:middle" %)**Error code**|(% style="text-align:center; vertical-align:middle" %)**CRC check code** 154 +|=(% style="text-align: center; vertical-align: middle;" %)**Address**|=(% style="text-align: center; vertical-align: middle;" %)**Function code**|=(% style="text-align: center; vertical-align: middle;" %)**Error code**|=(% style="text-align: center; vertical-align: middle;" %)**CRC check code** 154 154 |(% style="text-align:center; vertical-align:middle" %)1 byte|(% style="text-align:center; vertical-align:middle" %)Command code+0x80|(% style="text-align:center; vertical-align:middle" %)Error code|(% style="text-align:center; vertical-align:middle" %)2 bytes 155 155 156 156 When an error occurs, set the function code bit7 issued by the host to 1, and return (for example, 0x03 returns 0x83, 0x06 returns 0x86); the description of the error code are as follows. 157 157 158 158 (% class="table-bordered" %) 159 -|(% style="text-align:center; vertical-align:middle" %)**Error code**|(% style="text-align:center; vertical-align:middle" %)**Coding description** 160 +|=(% style="text-align: center; vertical-align: middle;" %)**Error code**|=(% style="text-align: center; vertical-align: middle;" %)**Coding description** 160 160 |(% style="text-align:center; vertical-align:middle" %)0x0001|(% style="text-align:center; vertical-align:middle" %)Illegal command code 161 161 |(% style="text-align:center; vertical-align:middle" %)0x0002|(% style="text-align:center; vertical-align:middle" %)Illegal data address 162 162 |(% style="text-align:center; vertical-align:middle" %)0x0003|(% style="text-align:center; vertical-align:middle" %)Illegal data ... ... @@ -202,8 +202,6 @@ 202 202 |**high byte**|**low byte**|**high byte**|**low byte** 203 203 |01|06|01|0A|0B|B8|AF, 76 204 204 205 - 206 - 207 207 **10 Function code write** 208 208 209 209 P07-09 set the 1st segment position to 2000, and this variable corresponds to the Modbus address: 1801 (0x0709). ... ... @@ -227,15 +227,15 @@ 227 227 228 228 Figure 8-3 Modbus communication parameter setting process 229 229 230 -** (1)Set the servo address P12-1**229 +**Set the servo address P12-1** 231 231 232 232 When multiple servos are in network communication, each servo can only have a unique address, otherwise it will cause abnormal communication and fail to communicate. 233 233 234 -** (2)Set the serial port baud rate P12-2**233 +**Set the serial port baud rate P12-2** 235 235 236 236 The communication rate of the servo and the communication rate of the host computer must be set consistently, otherwise the communication cannot be carried out. 237 237 238 -** (3)Set the serial port data format P12-3**237 +**Set the serial port data format P12-3** 239 239 240 240 The data bit check methods of servo communication are: 241 241 ... ... @@ -246,7 +246,7 @@ 246 246 247 247 The data frame format of the servo and the host computer must be consistent, otherwise the communication cannot be carried out. 248 248 249 -** (4)Set that whether the function code changed by Modbus communication is written into EEPROM in real time [P12-4]**248 +**Set that whether the function code changed by Modbus communication is written into EEPROM in real time [P12-4]** 250 250 251 251 When the host computer modifies the servo function code through communication, it can choose to store it in EEPROM in real time, which has the function of power-off storage. 252 252 ... ... @@ -258,7 +258,7 @@ 258 258 |(% style="text-align:center; vertical-align:middle" %)[[image:image-20220611153214-3.png]] 259 259 |After the EEPROM is damaged, the servo will have an non resettable fault! 260 260 261 -** (5)Set the high and low order of the 32-bit monitoring data**260 +**Set the high and low order of the 32-bit monitoring data** 262 262 263 263 Part of the monitoring volume is 32-bit length and occupies 2 consecutive bias numbers. The user needs to set the order of the data high bit and low bit correctly, otherwise it will cause data reading and writing errors! 264 264 ... ... @@ -267,51 +267,42 @@ 267 267 The description of related function codes are as follows. 268 268 269 269 (% class="table-bordered" %) 270 -|(% style="text-align:center; vertical-align:middle; width:121px" %)**Function code**|(% style="text-align:center; vertical-align:middle; width: 205px" %)**Name**|(% style="text-align:center; vertical-align:middle; width:187px" %)(((269 +|=(% style="text-align: center; vertical-align: middle; width: 121px;" %)**Function code**|=(% style="text-align: center; vertical-align: middle; width: 165px;" %)**Name**|=(% style="text-align: center; vertical-align: middle; width: 148px;" %)((( 271 271 **Setting method** 272 -)))|(% style="text-align:center; vertical-align:middle; width:1 86px" %)(((271 +)))|=(% style="text-align: center; vertical-align: middle; width: 165px;" %)((( 273 273 **Effective time** 274 -)))|(% style="text-align:center; vertical-align:middle; width:1 30px" %)**Default value**|(% style="text-align:center; vertical-align:middle; width:132px" %)**Range**|(% style="text-align:center; vertical-align:middle; width:252px" %)**Definition**|(% style="text-align:center; vertical-align:middle; width:85px" %)**Unit**275 -|(% style="text-align:center; vertical-align:middle; width:121px" %)P12-02|(% style="text-align:center; vertical-align:middle; width: 205px" %)Baud rate|(% style="text-align:center; vertical-align:middle; width:187px" %)(((273 +)))|=(% style="text-align: center; vertical-align: middle; width: 109px;" %)**Default value**|=(% style="text-align: center; vertical-align: middle; width: 85px;" %)**Range**|=(% style="text-align: center; vertical-align: middle; width: 224px;" %)**Definition**|=(% style="text-align: center; vertical-align: middle; width: 69px;" %)**Unit** 274 +|(% style="text-align:center; vertical-align:middle; width:121px" %)P12-02|(% style="text-align:center; vertical-align:middle; width:165px" %)Baud rate|(% style="text-align:center; vertical-align:middle; width:148px" %)((( 276 276 Operation setting 277 -)))|(% style="text-align:center; vertical-align:middle; width:1 86px" %)(((276 +)))|(% style="text-align:center; vertical-align:middle; width:165px" %)((( 278 278 Effective immediately 279 -)))|(% style="text-align:center; vertical-align:middle; width:130px" %)2|(% style="text-align:center; vertical-align:middle; width:132px" %)0 to 5|(% style="width:252px" %)((( 280 -0-2400bps 281 - 282 -1-4800bps 283 - 284 -2-9600bps 285 - 286 -3-19200bps 287 - 288 -4-38400bps 289 - 290 -5-57600bp 291 -)))|(% style="text-align:center; vertical-align:middle; width:85px" %)- 292 -|(% style="text-align:center; vertical-align:middle; width:121px" %)P12-03|(% style="text-align:center; vertical-align:middle; width:205px" %)Serial data format|(% style="text-align:center; vertical-align:middle; width:187px" %)((( 278 +)))|(% style="text-align:center; vertical-align:middle; width:109px" %)2|(% style="text-align:center; vertical-align:middle; width:85px" %)0 to 5|(% style="width:224px" %)((( 279 +* 0: 2400bps 280 +* 1: 4800bps 281 +* 2: 9600bps 282 +* 3: 19200bps 283 +* 4: 38400bps 284 +* 5: 57600bp 285 +)))|(% style="text-align:center; vertical-align:middle; width:69px" %)- 286 +|(% style="text-align:center; vertical-align:middle; width:121px" %)P12-03|(% style="text-align:center; vertical-align:middle; width:165px" %)Serial data format|(% style="text-align:center; vertical-align:middle; width:148px" %)((( 293 293 Operation setting 294 -)))|(% style="text-align:center; vertical-align:middle; width:1 86px" %)(((288 +)))|(% style="text-align:center; vertical-align:middle; width:165px" %)((( 295 295 Effective immediately 296 -)))|(% style="text-align:center; vertical-align:middle; width:130px" %)0|(% style="text-align:center; vertical-align:middle; width:132px" %)0 to 3|(% style="width:252px" %)((( 297 -0: 1 stop bit, no parity 298 - 299 -1: 1 stop bit, odd parity 300 - 301 -2: 1 stop bit, even parity 302 - 303 -3: 2 stop bits, no parity 304 -)))|(% style="text-align:center; vertical-align:middle; width:85px" %)- 305 -|(% style="text-align:center; vertical-align:middle; width:121px" %)P12-04|(% style="text-align:center; vertical-align:middle; width:205px" %)Modbus communication data is written into EEPROM|(% style="text-align:center; vertical-align:middle; width:187px" %)((( 290 +)))|(% style="text-align:center; vertical-align:middle; width:109px" %)0|(% style="text-align:center; vertical-align:middle; width:85px" %)0 to 3|(% style="width:224px" %)((( 291 +* 0: 1 stop bit, no parity 292 +* 1: 1 stop bit, odd parity 293 +* 2: 1 stop bit, even parity 294 +* 3: 2 stop bits, no parity 295 +)))|(% style="text-align:center; vertical-align:middle; width:69px" %)- 296 +|(% style="text-align:center; vertical-align:middle; width:121px" %)P12-04|(% style="text-align:center; vertical-align:middle; width:165px" %)Modbus communication data is written into EEPROM|(% style="text-align:center; vertical-align:middle; width:148px" %)((( 306 306 Operation setting 307 -)))|(% style="text-align:center; vertical-align:middle; width:1 86px" %)(((298 +)))|(% style="text-align:center; vertical-align:middle; width:165px" %)((( 308 308 Effective immediately 309 -)))|(% style="text-align:center; vertical-align:middle; width:130px" %)0|(% style="text-align:center; vertical-align:middle; width:132px" %)0 to 1|(% style="width:252px" %)((( 310 -0: Do not write to EEPROM, and do not store after power failure; 300 +)))|(% style="text-align:center; vertical-align:middle; width:109px" %)0|(% style="text-align:center; vertical-align:middle; width:85px" %)0 to 1|(% style="width:224px" %)((( 301 +* 0: Do not write to EEPROM, and do not store after power failure; 302 +* 1: Write to EEPROM, power-down storage. 303 +)))|(% style="text-align:center; vertical-align:middle; width:69px" %)- 311 311 312 -1: Write to EEPROM, power-down storage. 313 -)))|(% style="text-align:center; vertical-align:middle; width:85px" %)- 314 - 315 315 = **Modbus communication variable address and value** = 316 316 317 317 == **Variable address description** == ... ... @@ -340,19 +340,15 @@ 340 340 In order to facilitate actual use, this manual provides both decimal and hexadecimal address identification, it is shown in the following table: 341 341 342 342 (% class="table-bordered" %) 343 -|(% style="text-align:center; vertical-align:middle" %)**Function code**|(% style="text-align:center; vertical-align:middle" %)((( 344 -**Modbus address** 333 +|=(% style="text-align: center; vertical-align: middle; width: 162px;" %)**Function code**|=(% style="text-align: center; vertical-align: middle; width: 302px;" %)((( 334 +**Modbus address (Hexadecimal)** 335 +)))|=(% style="text-align: center; vertical-align: middle; width: 278px;" %)((( 336 +**Modbus address (Decimal)** 337 +)))|=(% style="text-align: center; vertical-align: middle; width: 192px;" %)**Category**|=(% style="text-align: center; vertical-align: middle; width: 142px;" %)**Name** 338 +|(% style="text-align:center; vertical-align:middle; width:162px" %)P0-1|(% style="text-align:center; vertical-align:middle; width:302px" %)0x0001|(% style="text-align:center; vertical-align:middle; width:278px" %)1|(% style="text-align:center; vertical-align:middle; width:192px" %)Basic settings|(% style="text-align:center; vertical-align:middle; width:142px" %)Control mode 345 345 346 -**(Hexadecimal)** 347 -)))|(% style="text-align:center; vertical-align:middle" %)((( 348 -**Modbus address** 340 +For detailed parameter addresses, please refer to __[["11.1 Lists of parameters".>>https://docs.we-con.com.cn/bin/view/Servo/Manual/02%20VD2%20SA%20Series/11%20Appendix/#HListsofparameters]]__ 349 349 350 -**(Decimal)** 351 -)))|(% style="text-align:center; vertical-align:middle" %)**Category**|(% style="text-align:center; vertical-align:middle" %)**Name** 352 -|(% style="text-align:center; vertical-align:middle" %)P0-1|(% style="text-align:center; vertical-align:middle" %)0x0001|(% style="text-align:center; vertical-align:middle" %)1|(% style="text-align:center; vertical-align:middle" %)Basic settings|(% style="text-align:center; vertical-align:middle" %)Control mode 353 - 354 -For detailed parameter addresses, please refer to __[["11.1 Lists of parameters".>>https://docs.we-con.com.cn/bin/view/Servo/2.%20User%20Manual/06%20VD2%20SA%20Series%20Servo%20Drives%20Manual%20%28Full%20V1.1%29/11%20Appendix/#HListsofparameters]]__ 355 - 356 356 == **Variable value type description** == 357 357 358 358 When writing function codes with signed numbers, you need to convert the pre-written data into hexadecimal complements. The conversion rules are as follows: