Liebert® IntelliSlot® Modbus 485, Modbus IP and BACnet IP

More documents

Recommendations

Info

2.3.2 Function Code 4 Modbus Communications - Modbus Packet Format The function code field tells the addressed slaves what function to perform. Function codes are designed to invoke a specific action by the slave device. The function code ranges from 1 to 127. Liebert IntelliSlot Modbus server supports the following Modbus function codes. Table 3 Supported Modbus function codes Code Function Description 01 Read Coils 02 Read Discrete Inputs 03 Read Holding Registers 2.3.3 Data Fields The data field length varies, depending on whether the message is a request or a response to a packet. This field typically contains information required by the slave device to perform the command specified or to the response to a data request from the master device. 2.3.4 Error Check Field Read from 1 to 2000 contiguous status of coils managed by the server. Coils in the response message are packed as one per bit of a byte, 1=On and 0=Off. If the requested quantity of coils is not a multiple of 8, zeros are padded in the final byte. Read from 1 to 2000 contiguous input status managed by the server. Discrete inputs in the response message are packed as one per bit of a byte, 1=On and 0=Off. If the requested number of inputs is not a multiple of 8, zeros are padded in the final byte. Read the contents of contiguous block of 1 to 127 holding registers. Data are packed as two bytes per register; the first byte contains the high order bits. 04 Read Input Registers Read the contents of contiguous block of 1 to 127 Input registers. Data are packed as two bytes per register; the first byte contains the high order bits. 05 Write Single Coil Write a single output to either On (1) or Off (0) mapped in coil section. 06 Write Single Register Write a value into a single holding register; 15 Write Multiple Coils Force each coil in a sequence of coils to either On or Off. 16 Write Multiple Registers Write values into a block of contiguous registers (1 to 120) The Error Check Field consists of a 16-bit (2 byte) Cyclical Redundancy Check (CRC16). It allows the receiving device to detect a packet that has been corrupted by transmission errors.
2.4 RTU Framing 5 Modbus Communications - RTU Framing The example below shows a typical query and response from a Liebert IntelliSlot interface card. The master device initiates a query asking Slave Device, with address 2, for holding registers starting at holding register 40051 (offset 50) and including next two registers (three total). Table 4 Query sample Slave Function Starting Register Number of Registers CRC16 Address Code Hi Byte Lo Byte Hi Byte Lo Byte Hi Byte Lo Byte 02 03 00 32 00 03 E5 FA Table 5 Response sample Register CRC16 Slave Function Count: Bytes of 40051 Data 40052 Data 40053 Data Address Code Data Hi Lo Hi Lo Hi Lo Hi Byte Lo Byte 02 03 6 1 58 00 FA 00 54 1B 0D Slave Device, with address 2, responds to Function Code 3 with 6 bytes of hexadecimal data and ends with CRC16 checksum. Register values: 40051 = 158 (hex) = 344 (decimal) 40052 = FA (hex) = 250 (decimal) 40053 = 54 (hex) = 84 (decimal)
Page 1: Infrastructure Management & Monitor
Page 4 and 5: 3.0 MODBUS 485 AND MODBUS IP PROTOC
Page 6 and 7: 3.4 Battery Monitoring Products . .
Page 8 and 9: MODBUS 485 & MODBUS IP PROTOCOLS (c
Page 12 and 13: 3.0 MODBUS 485 AND MODBUS IP PROTOC
Page 14 and 15: Modbus 485 and Modbus IP Protocols
Page 22 and 23: Shutdown - Loss Of Power - Event Ty
Page 36 and 37: Remote Sensor System Average Over T
Page 40 and 41: Table 10 Liebert CRV - Input and Ho
Page 46 and 47: Table 11 Liebert CRV - Glossary (co
Page 48 and 49: Table 11 Liebert CRV - Glossary (co
Page 50 and 51: Table 12 Liebert HPC (Chiller) - S
Page 52 and 53: Table 13 Liebert HPC (Chiller) - In
Page 54 and 55: Table 13 Liebert HPC (Chiller) - In
Page 56 and 57: Table 14 Liebert HPC (Chiller) - Gl
Page 58 and 59: Table 14 Liebert HPC (Chiller) - Gl
Page 60 and 61:
Table 15 Liebert XDC - Status and
Page 62 and 63:
Table 16 Liebert XDC - Input and Ho
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Table 17 Liebert XDC - Glossary (co
Page 74 and 75:
Table 17 Liebert XDC - Glossary (co
Page 76 and 77:
Modbus 485 and Modbus IP Protocols
Page 78 and 79:
Table 19 Liebert XDP - Input and Ho
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Table 20 Liebert XDP - Glossary (co
Page 94 and 95:
Table 20 Liebert XDP - Glossary (co
Page 96 and 97:
Table 22 Liebert XDWP (XDP-W) - Inp
Page 98 and 99:
Table 23 Liebert DS and Liebert Pe
Page 100 and 101:
Table 24 Liebert DS and Liebert PeX
Page 102 and 103:
Table 24 Liebert DS and Liebert PeX
Page 104 and 105:
Table 26 Liebert XDF - Input and Ho
Page 106 and 107:
Page 108 and 109:
Table 29 Liebert DataMate, Liebert
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Table 40 Liebert APM - Status and
Page 142 and 143:
Table 41 Liebert APM - Input and Ho
Page 144 and 145:
Table 42 Liebert APM - Glossary (co
Page 146 and 147:
140 Modbus 485 and Modbus IP Protoc
Page 148 and 149:
Table 44 Liebert GXT2 and Liebert G
Page 150 and 151:
Table 47 Liebert Nfinity ® - Statu
Page 152 and 153:
Table 49 Liebert NX - Status and C
Page 154 and 155:
Table 50 Liebert NX - Input and Hol
Page 156 and 157:
Table 51 Liebert NXL SA, SR, SN, M
Page 158 and 159:
Table 52 Liebert NXL SA, SR, SN, MM
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Table 57 Liebert PowerSure Interact
Page 184 and 185:
Table 59 Liebert Series 300 UPS - I
Page 186 and 187:
Table 61 Liebert Series 600 UPS - I
Page 188 and 189:
Table 63 Liebert Series 610 SCC UPS
Page 190 and 191:
Page 192 and 193:
Table 65 Liebert SICE 7200 - Input
Page 194 and 195:
Table 66 Liebert NPower - Input an
Page 196 and 197:
Table 67 Liebert BDSU - Status and
Page 198 and 199:
Table 68 Liebert BDSU - Input and H
Page 200 and 201:
4.0 BACNET COMMUNICATIONS BACnet Co
Page 202 and 203:
4.1.3 Standard Object Types Support
Page 204 and 205:
BACnet Communications - BACnet Prot
Page 206 and 207:
4.2 Precision Cooling Products 200
Page 208 and 209:
202 BACnet Communications - Precisi
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Ext Standby Glycol Pump On - Event
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Table 73 Liebert CRV - Binary Data
Page 230 and 231:
Table 74 Liebert CRV - Analog Data
Page 232 and 233:
Table 74 Liebert CRV - Analog Data
Page 234 and 235:
Table 75 Liebert CRV - Multistate D
Page 236 and 237:
Table 76 Liebert CRV - Glossary (co
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Table 77 Liebert HPC - Binary Data
Page 244 and 245:
Table 77 Liebert HPC - Binary Data
Page 246 and 247:
Table 78 Liebert HPC - Analog Data
Page 248 and 249:
Table 79 Liebert HPC - Multistate D
Page 250 and 251:
Table 80 Liebert HPC - Glossary (co
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Table 82 Liebert XDP, Liebert XDWP
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Table 86 Liebert Mini-Mate2 8 Ton -
Page 274 and 275:
Table 87 Liebert APM - Binary Data
Page 276 and 277:
Table 88 Liebert APM - Analog Data
Page 278 and 279:
Table 90 Liebert APM - Glossary Dat
Page 280:
Ensuring The High Availability Of M
show all

Liebert® IntelliSlot® Modbus 485, Modbus IP and BACnet IP

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?