User Guide - Eurotherm Ltda

More documents

Recommendations

Info

nanodac RECORDER/CONTROLLER: USER GUIDE4.9.1 Slave Main Menu (Cont.)PRIORITY LEVELSThree levels of update rate can be entered for use in data configuration (Section 4.9.3), to define how oftena value is read or written. In order to optimise performance, it is recommended that the slowest rate consistentwith requirements be selected. The intervals are selected from a scroll list see figure 4.9.1 above.4.9.2 Slave Diagnostics menuModbus Master.Slave.1.DiagnosticsActual HighActual MediumActual LowDevice StatusLoopback TestTotalSuccessfulFailuresRetriesTimeoutsIllegal Functionillegal AddressIlegal DataSlave FailureNo Gateway PathReset0.1251.0002.000SuccessNo154281542800000000NoFigure 4.9.2 Diagnostics menuNote: Diagnostic values are reset on power upActual HighActual MediumActual LowDevice StatusThe high priority rate that this slave is actually running at. This can never be faster thanthe high priority rate that was configured for this device (Slave Main menu, above), butif the master is heavily loaded the rate may be lower than that specified.The medium priority rate that this slave is running at. This can never be faster than themedium priority rate that was configured for this device (Slave Main menu, above), butif the master is heavily loaded the rate may be lower than that specified.The actual low priority rate that this slave is running at. This can never be faster than thelow priority rate that was configured for this device (Slave Main menu, above), but if themaster is heavily loaded the rate may be lower than that specified.The status of the last transaction to this slaveSuccess: The transaction was successfully actioned by the slave deviceTimeout: There was no response from the slave device to a given request within theconfigured timeIllegal Address: The request to the slave device contained an invalid modbus address.The address may be for a read only parameterIllegal Value: The request to the slave device contained invalid data for the specifiedparameterBad Sub: The sub function code in the request was invalidPage 138HA030554Issue 7 Nov 12
nanodac RECORDER/CONTROLLER: USER GUIDE4.9.2 Slave Diagnostics Menu (Cont.)DEVICE STATUS (Cont.)Idle: This data item is currently idle and not communicating with the slave deviceIllegal Code: The slave does not support the function code transmitted by the master.Pending: The request is waiting to be sent, the most likely cause being that the slavedevice has not been set to onlineLoopback Test If set to ‘Yes’, Sends a function code 8 transaction to the slave, and waits for a response.TotalA count of all the transactions sent to the slave including reads, writes both good andfailed transactions.Successful A count of all the successful transactions sent to the slave.FailuresA count of all the unsuccessful (failed) transactions sent to the slave. May be caused byIllegal Function, Illegal Address etc. failures, as detailed belowRetriesThe number of transactions that were re-sent because of timed out responses from theslave devices.TimeoutsA count of all the transactions sent to the slave for which no response was received withinthe configured timeout period.Illegal Function A count of all the transactions sent to the slave that the slave claimed contained aninvalid function code. Exception code (1).Illegal Address A count of all the transactions sent to the slave that the slave claimed contained aninvalid Modbus register address. Exception code (2).Illegal Data A count of all the transactions sent to the slave that the slave claimed contained aninvalid value. Exception code (3)Slave Failure A count of all the times this slave device has failed to communicate. Exception code (4)No Gateway Path A count of all the times it has not been possible to access the slave device as it is on anothernetwork that requires a gateway for accessMaster Rejects A count of all the transactions that the Modbus Master has refused to send to the slavedue to invalid configuration dataResetA one shot action that immediately resets all diagnostics counts.4.9.3 Modbus master data configurationThis is the area of configuration in which the individual data items are selected for transmission across theModbus master communications link. The configuration fields that appear depends on the parameter selected,so the examples given here will probably not match those that appear to the user. The parametersthat appear in the ‘parameter List’ scroll menu depends on the slave model.EXAMPLE 1: TARGET SP1 WITH NANODAC SLAVESelect configuration menuModbus Master.1.DataProgrammerDataDescriptorData Item 1Modbus MasterPV0.00EtherNet/IPStatusSuccessDigital I/OSlave Devicenanodac<strong>User</strong> LinParameter ListTarget SPCustom MessageNumber1ZirconiaPriorityMediumFigure 4.9.3a Target SetpointHA030554Issue 7 Nov 12Page 139
Page 1 and 2:
nanodacUser Guidenanodac recorder/c
Page 3:
Declaration of ConformityManufactur
Page 6 and 7:
nanodac RECORDER/CONTROLLER: USER G
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
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:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101: nanodac RECORDER/CONTROLLER: USER G
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
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:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
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:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
NANODAC RECORDER/CONTROLLER: USER G
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392:
show all

User Guide - Eurotherm Ltda

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

Delete template?

Save as template?