RS-485 User's Manual MEH448d - Fuji Electric America

More documents

Recommendations

Info

Character format 3-3 3-1 Messages Each byte of a message is transmitted as a character. Character formats are described on the following page. A character comprises a start bit (logical value 0), 8-bit data, an additional (optional) parity bit, and a stop bit (logical value 1). A character always consists of eleven bits, and the number of stop bits varies depending on whether parity exists. Without parity LSB MSB 0 1 2 3 4 5 6 7 8 9 10 Start Data Stop With parity LSB MSB 0 1 2 3 4 5 6 7 8 9 10 Start Data Parity (optional) Stop - Modbus RTU protocol has the above character format as specified by the rule. But, some devices use the format "No parity + Stop bit: 1 bit." For connection with these devices, FRENIC- Multi/MEGA support the parity bit selection: y06, y16=3. When y06, y16=3 are selected, the protocol is given the following character format. LSB MSB 0 1 2 3 4 5 6 7 8 9 Start Data Stop Chap. 3 Modbus RTU PROTOCOL
3.1.4 Message categories There are eight RTU message categories; read holding registers, preset single register, preset multiple registers, diagnostics, read coil status, force single coil, force multiple coils and error response. Each category is described below: [1] Read holding registers Query 1 byte 1 byte 2 bytes 2 bytes 2 bytes Station 03H Function code Number of read Error check address data Hi Lo Hi Lo Normal response 1 byte 1 byte 1 byte 2 to 100 bytes*1 2 bytes Station address 03H Byte count Read data Hi, Lo (data 0); Hi, Lo (data 1); ····· Error check *1 From 2 to 200 bytes for FRENIC-MEGA How to set a query - This request is not available for broadcast transactions. Station address 0 will become invalid (no response). - 'FC' = 3 (03H) - The function code is two bytes long. The Hi byte indicates the function code group (see Table 3.2), and the Lo byte represents a function code identification number (0 to 99). (Example) When the function code is E15, the Hi byte is 01H and the Lo byte is 0FH. Table 3.2 Function code group/code conversion table Group Code Name Group Code Name F 0 00H Fundamental function o 6 06 H Operational function E 1 01H Extension terminal function M 8 08H Monitor data C 2 02H Control function of frequency J 13 0DH Application function 1 P 3 03H Motor1 parameter H 4 04H High performance function d 19 13H Application function 2 A 5 05H Motor2 parameter y 14 0EH Link function b 18 12H Motor3 parameter W 15 0FH Monitor 2 r 10 0AH Motor4 parameter X 16 10H Alarm 1 S 7 07H Command/ Function data 3-4 Z 17 11H Alarm 2 - The length of the read data is up to 50 words (2 byte each) (100 words for FRENIC-MEGA). - If the read data contains an unused function code, 0 will be read, which will not result in an error. - Data does not extend over two or more function code groups. If, for example, reading of 40 words is specified from F40 but only function codes up to F40 are available, the data of F40 will be set at the first word, and the other 49 words will be 0.
Page 1 and 2: MEH448d
Page 3 and 4: Copyright © 2002-2009 Fuji Electri
Page 5 and 6: FRENIC-Multi Name Document number D
Page 7 and 8: CHAPTER 1 OVERVIEW1 Table of Conten
Page 9 and 10: CHAPTER 7 Metasys N2 (N2 PROTOCOL)1
Page 12 and 13: 1.1 Features The functions listed b
Page 14 and 15: CHAPTER 2 COMMON SPECIFICATIONS Thi
Page 16 and 17: 2.1 Specifications of RS-485 Commun
Page 18 and 19: 2.1.1 Specification of the RJ-45 co
Page 20 and 21: 2-5 2.1 Specifications 2.1.3 RJ-45
Page 22 and 23: 2.1.4 Specification of connection c
Page 24 and 25: 2-9 2.2 Connections (2) Connection
Page 26 and 27: 2-11 2.2 Connections (4) Multidrop
Page 28 and 29: (a ) RS-485 communications card (fo
Page 30 and 31: 2.2.3 Devices for connection 2-15 2
Page 32 and 33: Separating the grounding 2-17 2.2 C
Page 34 and 35: 2.3.2 Link functions (operation sel
Page 36 and 37: 2-21 2.3 Switching to Communication
Page 38 and 39: Baud rate (y04, y14) Set a baud rat
Page 40 and 41: 2.5 Selecting the Method of Storing
Page 42: CHAPTER 3 Modbus RTU PROTOCOL This
Page 45: 3.1.3 Message frames As shown below
Page 49 and 50: How to set a query - When the stati
Page 51 and 52: Interpretation of normal response -
Page 53 and 54: Interpretation of normal response -
Page 55 and 56: 3.2 Host Side Procedures 3.2.1 Inve
Page 57 and 58: 3.2.3 Receiving preparation complet
Page 59 and 60: 3.3.2 Operations in case of errors
Page 61 and 62: When y02 = 3 (mode in which the inv
Page 63 and 64: START Initial setting Remainder R
Page 65 and 66: Table 3.13 CRC data calculation tab
Page 68 and 69: 4.1 Messages 4.1.1 Message formats
Page 70 and 71: Byte Field ASCII format Value Table
Page 72 and 73: Table 4.3 ACK frame 4-5 4.1 Message
Page 74 and 75: [2] Optional frame This section des
Page 76 and 77: Byte Polling response frame [invert
Page 78 and 79: 4.1.3 Descriptions of fields [1] Co
Page 80 and 81: 4.1.4 Communications examples 4-13
Page 82 and 83: 4.2 Host Side Procedures 4.2.1 Inve
Page 84 and 85: 4.3 Communications Errors 4.3.1 Cat
Page 86: CHAPTER 5 FUNCTION CODES AND DATA F
Page 89 and 90: 5.1.2 Command data [1] List of comm
Page 91 and 92: [3] Operation command data Table 5.
Page 93 and 94: Table 5.5 Relation between operatio
Page 95 and 96: [5] Universal DO and universal AO (
Page 97 and 98:
Table 5.9 Monitor data 1 function c
Page 99 and 100:
Table 5.11 Monitor data 1 function
Page 101 and 102:
Table 5.13 Monitor data 1 function
Page 103 and 104:
Table 5.14 Keypad-related function
Page 105 and 106:
*1 Operation command source code In
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
5.2 Data Formats 5.2.1 List of data
Page 115 and 116:
Table 5.18 List of data format numb
Page 117 and 118:
Code Table 5.19 List of data format
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Data format [7] Decimal data (posit
Page 137 and 138:
Data format [11] Capacity code (uni
Page 139 and 140:
Data format [17] Model code 15 14 1
Page 141 and 142:
Data format [23] Polarity + decimal
Page 143 and 144:
Data format [40] Alarm factor 15 14
Page 145 and 146:
Data format [68] Frequency command
Page 148 and 149:
===Appendix=== CHAPTER 6 FLOOR LEVE
Page 150 and 151:
6.1 Messages 6.1.1 polling/selectin
Page 152 and 153:
6.5 Strategies 6.5.1 Monitoring 6-3
Page 154 and 155:
6.6.5 Analog Inputs monitor 6-5 6.6
Page 156 and 157:
Point Number Point Type Table 6.3 P
Page 158 and 159:
Table 6.4 Point Database for FLN. P
Page 160:
It is similar for the lower limit v
Page 164 and 165:
7.1 Messages 7.1.1 Transmission Spe
Page 166 and 167:
7.4 Read / Write Parameter Read Par
Page 168 and 169:
Support Command List 2 Message Comm
Page 170:
Support Command List 4 Message Comm
Page 173:
Fuji Electric Systems Co., Ltd. Sta
show all

RS-485 User's Manual MEH448d - Fuji Electric America

Create successful ePaper yourself

Delete template?

Save as template?