ABB SACE Division: PR122/VF Modbus System Interface

ABB SACE Division
Project
Emax VF
Subproject
PR122/VF
Title
Modbus System Interface
The aim of this document is to show the addresses of all the information available in PR122/VF.
Moreover, it expalins the procedures to read information and program the parameters of the above mentioned protection units.
Author Title EN
Autore LB-DTEA Titolo PR122/VF + PR120/D-M
Modbus™ System Interface
Doc. No
ABB L4618 N. Doc. 1SDH000922R0001 Tot. Pag.
1/40
Index Page
1. REVISION HISTORY..................................................................................................................................................................5
1.1 REV 01, 11/01/2011 .................................................................................................................................................................5
2. AIM .................................................................................................................................................................................................5
3. ACRONYMS AND DEFINITIONS ............................................................................................................................................5
3.1 ACRONYMS...............................................................................................................................................................................5
4. COMMUNICATION PARAMETERS.......................................................................................................................................6
5. UNIT IDENTIFICATION............................................................................................................................................................6
6. AVAILABLE MODBUS FUNCTIONS......................................................................................................................................6
6.1 FUNCTION 03 (03H) READ HOLDING REGISTERS .....................................................................................................................7
6.2 FUNCTION 04 (04H) READ INPUT REGISTERS ..........................................................................................................................7
6.3 FUNCTION 06 (06H) WRITE SINGLE REGISTER ........................................................................................................................7
6.4 FUNCTION 08 (08H) DIAGNOSTIC.............................................................................................................................................7
6.5 FUNCTION 16 (10H) WRITE MULTIPLE REGISTERS ..................................................................................................................8
6.6 FUNCTION 17 (11H) REPORT SLAVE ID....................................................................................................................................8
6.7 FUNCTION 70 (46H) READ EXTENDED REGISTERS ..................................................................................................................8
6.8 EXCEPTION RESPONSES ............................................................................................................................................................9
6.8.1 Illegal function.................................................................................................................................................................9
6.8.2 Illegal data address .........................................................................................................................................................9
6.8.3 Illegal data value.............................................................................................................................................................9
6.8.4 Slave device failure .........................................................................................................................................................9
6.8.5 Slave device busy.............................................................................................................................................................9
6.8.6 Exception occurrences ....................................................................................................................................................9
7. MODBUS MAP............................................................................................................................................................................10
7.1 MEASURES..........................................................................................................................................................................10
7.2 PROTECTIONS ....................................................................................................................................................................10
7.3 REGISTER MAP...................................................................................................................................................................11
7.3.1 SYSTEM BUS MAP .......................................................................................................................................................11
7.4 DATALOGGER MAP (EXTENDED REGISTERS) ...................................................................................................................12
8. DESCRIPTION OF REGISTERS.............................................................................................................................................14
8.1 COMMANDS........................................................................................................................................................................14
8.2 STATISTICAL DATA..........................................................................................................................................................15
8.3 PROGR FAIL ERROR CODE ..............................................................................................................................................15
8.4 STATE ...................................................................................................................................................................................17
8.5 TIME......................................................................................................................................................................................20
8.6 RUN-TIME MEASURES .....................................................................................................................................................20
8.7 INFORMATION ...................................................................................................................................................................20
8.8 PARAMETERS CONFIGURATION 1................................................................................................................................21
8.11 PARAMETERS PROTECTION SET1.................................................................................................................................23
8.12 TRIP HISTORY ....................................................................................................................................................................24
8.13 MEASURES HISTORY........................................................................................................................................................25
8.14 LOG EVENTS.......................................................................................................................................................................25
Author Title EN
Doc. No
2/40
9. TABLES........................................................................................................................................................................................26
10. CHECK OF PARAMETERS ACCURACY ........................................................................................................................27
11. OPERATION DESCRIPTION..............................................................................................................................................27
11.1 PARAMETER PROGRAMMING .......................................................................................................................................27
11.2 DATALOGGER....................................................................................................................................................................28
11.2.1 Recorded data................................................................................................................................................................29
11.2.2 Trigger state information ..............................................................................................................................................29
11.2.3 Datalogger settings .......................................................................................................................................................30
11.2.4 Available commands for the datalogger.......................................................................................................................31
11.2.5 Functioning description ................................................................................................................................................32
11.3 MEASURE HISTORY DATA STRUCTURE .....................................................................................................................33
11.4 RELAY FUNCTIONALITY.................................................................................................................................................34
11.4.1 Settings of relay fucntionality of the signaling module ................................................................................................35
11.5 SIGNALLING MODULE INPUT FUNCTIONALITY ......................................................................................................36
11.5.1 Settings of input signalling module...............................................................................................................................37
11.6 CB STATE INFORMATION ...............................................................................................................................................37
11.7 STATISTICAL DATA..........................................................................................................................................................38
11.8 RELAYS YO AND YC .........................................................................................................................................................39
11.9 COMAMND EXECUTION CONDITIONS ........................................................................................................................40
11.9.1 Command execution conditions:...................................................................................................................................40
11.10 MEASURE LIMITS AND REPRESENTATION............................................................................................................40
11.11 CONTACT WEAR............................................................................................................................................................40
Author Title EN
Doc. No
3/40
Index of figures Page
FIGURE 1 PROGRAMMING SESSION CORRECTLY HANDLED ....................................................................................................................27
FIGURE 2 PROGRAMMING FAILED ..........................................................................................................................................................27
FIGURE 3 PROGRAMMING ABORTED .......................................................................................................................................................28
FIGURE 5 THREE SITUATIONS OF RECORDING........................................................................................................................................28
FIGURE 6 RECORDING TIME LOWER THAN MAXIMUM ............................................................................................................................29
FIGURE 7 EXAMPLE OF STOP DATALOGGER FOR TRIGGER OR FOR STOP COMMAND AND RESTART TRIGGER COMMAND ....................32
FIGURE 8 RELAY FUNCTIONALITY ..........................................................................................................................................................34
FIGURE 9 EFFECT OF MINIMUM TIME OF RELAY ACTIVATION ................................................................................................................34
FIGURE 10 SIGNALLING MODULE INPUT FUNCTIONALITY ......................................................................................................................36
Index of tables Page

TABLE 1 TAB_INPUT_OUTPUT .........................................................................................................................................................13
TABLE 2 TAB_TRIP ..............................................................................................................................................................................13
TABLE 3 TAB_ALARM_1 ....................................................................................................................................................................13
TABLE 4 TAB_ALARM_2 ....................................................................................................................................................................13
TABLE 5 TAB_COMMANDS ...............................................................................................................................................................14
TABLE 6 TAB_PAR_ERR_CODE ........................................................................................................................................................16
TABLE 7 TAB_TRIP_TYPE ..................................................................................................................................................................24
TABLE 8 TAB_RELAYS_FUNCTION.................................................................................................................................................26
TABLE 9 TAB_P_RELE_CONFIG .......................................................................................................................................................26
TABLE 10 TAB_CB_TYPE ...................................................................................................................................................................26
TABLE 11 TAB_LOG_EVENTS ...........................................................................................................................................................26
TABLE 12 TAB DLOG RECORDING TIME........................................................................................................................................30
TABLE 13 COMMAND EXECUTION CONDITIONS........................................................................................................................40
Author Title EN
Doc. No
4/40
1. REVISION HISTORY
1.1 Rev 01, 11/01/2011
First release.
2. AIM
The aim of this document is to indicate the addresses of all the information available with PR122/VF.
Moreover, it explains the procedures to read information and to program the parameters of the above mentioned protection units.
3. ACRONYMS AND DEFINITIONS

3.1 Acronyms
AI Analog Input
AO Analog Output
CB Circuit Breaker
LSb Least Significant Bit
MSb Most Significant Bit
LSB Least Significant Byte
MSB Most Significant Byte
BOOL Bit or Boolean (IEC 61131-3)

BYTE Byte (IEC 61131-3)
WORD Word (IEC 61131-3)
DWORD Double word (IEC 61131-3)
LWORD Long Word (IEC 61131-3)
SINT Short Integer (IEC 61131-3)
USINT Unsigned Short Integer (IEC 61131-3)
INT Single Integer (IEC 61131-3)
UINT Unsigned Integer (IEC 61131-3)
DINT Double Integer (IEC 61131-3)
UDINT Unsigned Double Integer (IEC 61131-3)
LINT Long Integer (IEC 61131-3)
ULINT Unsigned Long Integer (IEC 61131-3)
STRING Text String (IEC 61131-3)
UNICODE Unicode (IEC 61131-3)
Author Title EN
Doc. No
5/40
4. Communication parameters
Serial type Baud rate Address Addressing type Physical protocol
SSI 500 KHz 3 Standard E, 8, 1
E, 8, 1
O, 8, 1
Bus EXT 9600/19200 bit/s 1 ÷ 247 Standard / ABB
N, 8, 2
N, 8, 1
Bus INT 19200 bit/s 3 Standard E, 8, 1
Bus Test 19200 bit/s 3 Standard E, 8, 1
5. Unit identification
Unit Slave ID
PR122/VF 0x11
6. Available Modbus functions

Function Code Name Applicable to
03 (03h) Read Holding Registers AO
04 (04h) Read Input Registers AI
06 (06h) Write Single Register AO
Funct Code Subf Code Name Applicable to
08 (08h) 00 (00H) Diagnostic Loopback ---
Function Code Name Applicable to
16 (10h) Write Multiple Registers AO
17 (11h) Report Slave ID ---
70 (46h) Read Extended Registers Extended Reg
Nota 1. All queries must respect the limitation of the maximum modbus message length of 256 byte
Legend:
AA = slave address (1 247)
cl = byte low of CRC
ch = byte high of CRC
Author Title EN
Doc. No
6/40
6.1 Function 03 (03h) Read Holding Registers
Query
Addr Function Starting address Number of registers Crc
AA 03h High Low High Low ch cl
Nota 1. Number of registers ≤ 125
Response
Addr Function Byte count Register value … Register value Crc
AA 03h nn High Low … High Low ch cl
6.2 Function 04 (04h) Read Input Registers

Query
Addr Function Starting address Nr of input registers Crc
Response
Addr Function Byte count Input register … Input register Crc
AA 04h nn High Low … High Low ch cl
6.3 Function 06 (06h) Write Single Register

Query
Addr Function Register address Register value Crc
Response (echo della query)

Addr Function Register address Register value Crc
6.4 Function 08 (08h) Diagnostic

Query
Addr Function Subfunction Data … Crc
Aa 08h 00h 00h yy … ch cl
Nota 1. 0 ≤ Number of data bytes ≤ 250, any value
Response (echo della query)

Addr Function Subfunction Data … Crc
Aa 08h 00h 00h yy … ch cl
Author Title EN
Doc. No
7/40
6.5 Function 16 (10h) Write Multiple Registers
Query
Addr Funct Starting addr Num of registers Byte count Reg value … Reg value Crc
Aa 10h High Low High Low Nn High Low … High Low ch cl
Response
Addr Function Starting address Number of register Crc
Aa 10h High Low High Low ch cl
6.6 Function 17 (11h) Report slave ID

Query
Addr Function Crc
AA 11h Ch cl
Response
Addr Function Byte count Slave ID Run indicator Sw Version Addr event Device Ser Nr Crc
AA 11h 16h ID 0FFh High Low High Low 16 byte (ASCII) ch cl
6.7 Function 70 (46h) Read Extended Registers

Query
Addr Function Byte count Ref type File number Starting address Number of registers Crc
AA 46h 07h 06h High Low High Low High Low ch Cl
Nota 1. File number ≤ 3
Nota 2. Starting address ≤ 65535
Response
Addr Funct Byte count Ref type Reg value … Reg value Crc
AA 46h Nn 06h High Low … High Low ch Cl
Author Title EN
Doc. No
8/40
6.8 Exception responses
6.8.1 Illegal function
Addr Function Exception code Crc
AA Function + 80h 01h ch cl
6.8.2 Illegal data address

6.8.3 Illegal data value

6.8.4 Slave device failure

6.8.5 Slave device busy

6.8.6 Exception occurrences

EXCEPTIONS
01 02 03 04 06
Illegal function Illegal data address Illegal data value Slave device failure Slave device busy
• Starting address not • Invalid query length
valid • Requested no. of register too
03
large
• Address out of modbus map
• Starting address not • Invalid query length • Reading attempt in flash with
valid • Requested no. Of register too flash busy
04
large
• Address out of modbus map
• Starting address not • Invalid query length • Reading from ext bus in local
valid mode
• Write of a time • Programming session already
06
information not open on the other bus
QUERY FUNCTIONS
allowed with this • Programming session not open

function
• Subfunction ≠ 00 00
08
• Invalid query length
• Invalid query length • Parameters error • Reading from ext bus in local
• Starting address not
• Requested no. of register too check after a stop mode
valid
programming
large • Programming session not open
session command
16 • Address out of modbus map • Programmins session already
• Not provided command open on other bus
• Invalid command parameter • Command acceptance conditions
• Wrong time not verified
17 • Invalid query length
• Starting address not • Invalid query length • Reading attempt of busy
valid datalogger
• No. of registers too large
70 • Invalid Address out of map
Field Ref Type
• Invalid Field Byte count
Author Title EN
Doc. No
9/40
7. MODBUS MAP
Data format LINT (4 byte = 2 word = 2 registers) is transferred with low significant part at lower modbus address (LOW-HIGH)
Register i LS word
Register i + 1 MS word
Instead within WORD data the most significant byte is transferred first (as in MODBUS RTU standard)
MS byte LS byte
7.1 MEASURES
The following table shows the available measures for each type of device and possible necessary conditions:
PR122/VF
Line currents `
Trip history `
Log event history `
Measure history `
Contact wear `
Datalogger `
Legend `: Available without further conditions
7.2 PROTECTIONS
The following table shows the different available protections for each type of device and possible necessary conditions:
PR122/VF
L `
I `
OT `
LC `(1)
Hw prot. `
Legend `: Available without further conditions

(1): Load control always enabled on state bits but feasible only if present signaling module or output unit on system bus (ex:
PR120/K)
Author Title EN
Doc. No
10/40
7.3 REGISTER MAP
7.3.1 SYSTEM BUS MAP
AI [30001] AO [40001]
Ind
rel Function 4 16 3 6
Function:
(6.2) (6.5) (6.1) (6.3)
0 STATISTICAL DATA (8.2) COMMANDS(8.1)
50 PROGR FAIL ERROR CODE (8.3)
100 STAT(8.4) TIME(8.5) (*)
200 RUN TIME MEASURES (8.5)
600 (8.7)
700 INFORMATION(8.7)
1000 PAR. CONFIG1 ACTUAL(8.8)

1020 PAR. CONFIG2 ACTUAL(8.9)
1050 PAR. CONFIG3 ACTUAL(8.10) PAR. CONFIG3 NEW (*)
1100 PAR. PROT. SET1 ACTUAL (8.11) PAR. PROT SET1 NEW (*)
2000 TRIP HISTORY (8.12)
2500 MEASURE HISTORY (8.13)
3300 LOG EVENT (0)
6000
________________________________________________________________________________________________________
U *FLASH : could be busy (busy exception response)
(*) Parameters that can be written only during an open programming session
________________________________________________________________________________________________________
Example of table reading:
RUN-TIME MEASURES analog input absolute address: 30001+offset (200) = 30201
The relative address is offset (200) = 200
Author Title EN
Doc. No
11/40
7.4 DATALOGGER MAP (extended registers)
________________________________________________________________________________________________________
U Addressing type “ABB” cannot be used for these registers, therefore the address field will be always included between 1
and 65536 for all addressing methods.
________________________________________________________________________________________________________
Extended Reg (600000)

File Number Sample Number Function 70
Rel. address Description Note
0 Current sample I1 note 1
3 ---
4 ---
5 ---
6 ---
Samples 0 (Old) 7 ---
8 ---
File 0 (Old) 9 ---
10 ---
11 ---
12 Input/Output status TAB_INPUT_OUTPUT
13 Alarm 1 status TAB_ALARM_1
14 Alarm 2 status TAB_ALARM_2
15 Trip 1 status TAB_TRIP
Samples 1 16 ÷ 31 “ “
… … “ “
Samples 4095 (New) 65519 ÷ 65535 “ “
File 1 Samples 0 ÷ Samples 4095 0 ÷ 65535 “ “
File 2 Samples 0 ÷ Samples 4095 0 ÷ 65535 “ “
File 3 (New) Samples 0 ÷ Samples 4095 0 ÷ 65535 “ “
note 1: Signal sample with 910 → 1 In
Author Title EN
Doc. No
12/40
Table 1 TAB_INPUT_OUTPUT
Table 3 TAB_ALARM_1
Bit Input type
0 --- Bit Input type
1 --- 0 ---
2 --- 1 Contact Wear Pre-alarm
3 --- 2 Contact Wear Alarm
4 --- 3 L Pre-alarm
5 --- 4 L Timing
6 --- 5 ---
7 --- 6 ---
8 Relay P1 contact 7 ---
12 --- 11 OT Pre-alarm
13 --- 12 OT Alarm
14 --- 13 OT Alarm (Blocked Trip)
15 --- 14 ---
15 ---
Table 2 TAB_TRIP
Table 4 TAB_ALARM_2
Bit Input type
0 L tripped Bit Input type
1 -- 0 ---
2 -- 1 ---
3 I tripped 2 ---
4 -- 3 ---
5 -- 4 ---
6 --- 5 ---
7 OT tripped 6 ---
8 --- 7 ---
9 -- 8 ---
10 -- 9 ---
11 -- 10 ---
12 --- 11 ---
13 -- 12 ---
14 --- 13 ---
15 --- 14 Iw Warning
15 LC1 Alarm
Author Title EN
Doc. No
13/40
8. DESCRIPTION OF REGISTERS
8.1 COMMANDS
Rel # of
Name Notes Bus
addr item
0 1 COMMAND TYPE TAB_COMMANDS SLTI
1 1 COMMAND PARAMETER TAB_COMMANDS SLTI
To execute a command it is requested to write to COMMAND TYPE field the number desired and in the following address the
possible parameter related to the command.
To send a command it is requested to use function 16 and write both the command registers and the parameter also if this one is
not necessary.
Example 1:to send the command “Trip test”, write 19 at the address of the register COMMAND TYPE and each value at
the address of the PARAMETER address (parameter not necessary for this command).
Following the command list table with pertinent command parameters.
Table 5 TAB_COMMANDS
Value Command type Parameter
0 Dummy command don’t care
1 Trip reset don’t care
2 Signaling Reset don’t care
3 Communication statistics reset don’t care
4 Log event reset don’t care
5 Start programming session don’t care
6 Abort programming session don’t care
7 Stop programming session don’t care
8 CB Open don’t care
9 CB Close don’t care
10 CB Reset don’t care
11 Wink toggle command don’t care
12 History measure reset don’t care
13 --- don’t care
14 Datalogger trigger restart don’t care
15 Datalogger stop don’t care
Author Title EN
Doc. No
14/40
8.2 STATISTICAL DATA
Rel # of
Name Representation Notes
addr item
Received msg no. =
Received msg no. with crc error +
0 1 Received message number 0 ÷ 65535
Sent msg no. +
Received broadcast msg no.
Received message number
1 1 0 ÷ 65535
with crc error
2 1 Sent message number 0 ÷ 65535 Total exception response number included
Slave Busy exception number
3 1 0 ÷ 65535
responses
Total exception response
4 1 0 ÷ 65535 Slave Busy exception number response included
number
0 ÷ 65000
5 1 Contact wear (100% = 65000)
CW > 100% → 65000
6 1 Total trip protection number 0 ÷ 65535 Protection trip fail number included
Total operation no. =
Manual operation no. +
7 1 Total operation number 0 ÷ 65535 protection trip no. +
protection trip fail no. +
N° trip test no.
8 1 Manual operation number 0 ÷ 65535
9 1 Total trip protection number 0 ÷ 65535 Protection trip fail number not included
10 1 Trip protection fail number 0 ÷ 65535
11 1 Trip test number 0 ÷ 65535
________________________________________________________________________________________________________
U Registers from address 0 to 4 compose the communication statistics, registers from address 6 to 11 compose CB
operation statistics.
8.3 PROGR FAIL ERROR CODE

Rel # of
Name Notes
addr item
0: No error
1 ÷ 999: See table TAB_PAR_ERR_CODE

50 1 Programming Fail Error Code
Common:
3001: Error on the change language
Author Title EN
Doc. No
15/40
Table 6 TAB_PAR_ERR_CODE
Par error code Parameters Par error code Parameters Par error code Parameters Par error code Parameters
< min > max Step err address < min > max Step err address < min > max Step err address < min > max Step err address
0 1 2 Not used 183 184 185 1072 366 367 368 1142 549 550 551 1221
3 4 5 1020 186 187 188 1073 369 370 371 1143 552 553 554 1222
6 7 8 1050 189 190 191 1074 372 373 374 1145 555 556 557 1225
9 10 11 1301 192 193 194 1075 375 376 377 1147 558 559 560 1223
12 13 14 1021 195 196 197 1076 378 379 380 1144 561 562 563 1224
15 16 17 1022 198 199 200 1077 381 382 383 1146 564 565 566 1226
18 19 20 1023 201 202 203 1078 384 385 386 1148 567 568 569 1227
21 22 23 1024 204 205 206 1079 387 388 389 1149 570 571 572 1228
24 25 26 1025 207 208 209 1080 390 391 392 1176 573 574 575 1229
27 28 29 1026 210 211 212 1081 393 394 395 1177 576 577 578 1230
30 31 32 1051 213 214 215 1082 396 397 398 1178 579 580 581 1231
33 34 35 1083 216 217 218 1300 399 400 401 1150 582 583 584 1232
36 37 38 1302 219 220 221 1314 402 403 404 1151 585 586 587 1233
39 40 41 1303 222 223 224 1310 405 406 407 1152 588 589 590 1234
42 43 44 1304 225 226 227 Not used 408 409 410 1153 591 592 593 1236
45 46 47 1305 228 229 230 Not used 411 412 413 1154 594 595 596 1238
48 49 50 1306 231 232 233 1311 414 415 416 1155 597 598 599 1235
51 52 53 1307 234 235 236 1312 417 418 419 1156 600 601 602 1237
54 55 56 1308 237 238 239 1313 420 421 422 1157 603 604 605 1239
57 58 59 1309 240 241 242 1100 423 424 425 1158 606 607 608 1240
60 61 62 1028 243 244 245 1101 426 427 428 1159 609 610 611 1241
63 64 65 1029 246 247 248 1102 429 430 431 1160 612 613 614 1242
66 67 68 1030 249 250 251 1104 432 433 434 1161 615 616 617 1243
69 70 71 1031 252 253 254 1103 435 436 437 1162 618 619 620 1245
255 256 257 1105 438 439 440 1163 621 622 623 1247
72 73 74 1095
258 259 260 1106 441 442 443 1164 624 625 626 1244
75 76 77 1096
261 262 263 1107 444 445 446 1165 627 628 629 1246
78 79 80 1084
264 265 266 1108 447 448 449 1166 630 631 632 1248
81 82 83 1085
267 268 269 1110 450 451 452 1167 633 634 635 1249
84 85 86 1086
270 271 272 1112 453 454 455 1168 636 637 638 1276
87 88 89 1087
273 274 275 1109 456 457 458 1169 639 640 641 1277
90 91 92 1088 276 277 278 1111 459 460 461 1170 642 643 644 1278
93 94 95 1089
279 280 281 1113 462 463 464 1171 645 646 647 1250
96 97 98 1090 282 283 284 1114 465 466 467 1172 648 649 650 1251
99 100 101 1091 285 286 287 1115 468 469 470 1173 651 652 653 1252
102 103 104 1092 288 289 290 1116 471 472 473 1174 654 655 656 1253
105 106 107 1093 291 292 293 1118 474 475 476 1175 657 658 659 1254
108 109 110 1027 294 295 296 1117 477 478 479 1179 660 661 662 1255
111 112 113 1094 297 298 299 1119 480 481 482 1180 663 664 665 1256
114 115 116 1032 300 301 302 1120 483 484 485 1181 666 667 668 1257
117 118 119 1097 303 304 305 1121 486 487 488 1200 669 670 671 1258
120 121 122 1098 306 307 308 1122 489 490 491 1201 672 673 674 1259
123 124 125 1052 309 310 311 1125 492 493 494 1202 675 676 677 1260
126 127 128 1067 312 313 314 1123 495 496 497 1204 678 679 680 1261
129 130 131 1053 315 316 317 1124 498 499 500 1203 681 682 683 1262
132 133 134 1054 318 319 320 1126 501 502 503 1205 684 685 686 1263
135 136 137 1055 321 322 323 1127 504 505 506 1206 687 688 689 1264
138 139 140 1056 324 325 326 1128 507 508 509 1207 690 691 692 1265
141 142 143 1057 327 328 329 1129 510 511 512 1208 693 694 695 1266
144 145 146 1058 330 331 332 1130 513 514 515 1210 696 697 698 1267
147 148 149 1059 333 334 335 1131 516 517 518 1212 699 700 701 1268
150 151 152 1060 336 337 338 1132 519 520 521 1209 702 703 704 1269
153 154 155 1061 339 340 341 1133 522 523 524 1211 705 706 707 1270
156 157 158 1062 342 343 344 1134 525 526 527 1213 708 709 710 1271
159 160 161 1063 345 346 347 1136 528 529 530 1214 711 712 713 1272
162 163 164 1064 348 349 350 1138 531 532 533 1215 714 715 716 1273
165 166 167 1065 351 352 353 1135 534 535 536 1216 717 718 719 1274
168 169 170 1066 354 355 356 1137 537 538 539 1218 720 721 722 1275
171 172 173 1068 357 358 359 1139 540 541 542 1217 723 724 725 1279
174 175 176 1069 360 361 362 1140 543 544 545 1219 726 727 728 1280
177 178 179 1070 363 364 365 1141 546 547 548 1220 729 730 731 1281
180 181 182 1071
Author Title EN
Doc. No
16/40
8.4 STATE
N Symbols (↑) and (↕) marks state bits whose variation are traced in the events log; (↑) means that variation from o to 1 is
traced, instead (↕) means that variations from 0 to 1 and from 1 to 0 are traced too.
Rel # of
Name Bit Descrption Notes
addr item
BIT 0 (↑) Parameter changed 1 = Parameter(s) changed
BIT 1 Historical Measure Update 1 = Histor meas updated
BIT 2 --- ---
BIT 3 (↑) Signalling Reset 1 = Signalling resetted
BIT 4 Trip Reset 1 = Trip Reset Command executed
BIT 5 CB Reset 1 = CB Reset Command executed
BIT 6 Dummy Command 1 = Dummy Command executed
STATE 1
GLITCH BIT 7 --- ---
100 1
note 2 BIT 8 --- ---
BIT 9 --- ---
BIT 10 --- ---
BIT 11 --- ---
BIT 12 --- ---
BIT 13 --- ---
BIT 14 --- ---
BIT 15 --- ---
BIT 0 Any Alarm / Timing / Warning OR of alarms
BIT 1 Any Trip OR of Trips (latched)
BIT 2 CB tripped 1 = CB tripped
BIT 3 (↕) CB connected / isolated 0 = Isolated, 1 = Connected
BIT 4 (↕) CB open/closed 0 = Open, 1 = Closed
BIT 5 (↕) CB undefined 1 = Undefined
BIT 6 (↕) No communic on Local Bus 1 = No communication on LB
STATE 2 BIT 7 Springs charged/discharged 0 = Discharged, 1 = Charged
101 1
FLAGS BIT 8 (↑) Trip command fail 1 = Trip command failed
BIT 9 (↕) Local / Remote Operating Mode 0 = Local, 1 = Remote
BIT 10 Programming OK 1 = Programming OK
BIT 11 Programming Fail 1 = Programming Failed
BIT 12 Internal Bus programming session 1 = Bus SSI session opened
BIT 13 Test Bus programming session 1 = Bus Test session opened
BIT 14 --- ---
BIT 15 System Bus programming session 1 = Bus Ext session opened
BIT 0 (↕) Test Session 1 = Test session opened
BIT 1 (↕) Test Unit connected 1 = Test unit connected
BIT 2 --- ---
BIT 3 Signalling module present 1 = Signalling module present
BIT 4 Dialog unit present 1 = Dialog unit present
BIT 5 --- ---
BIT 6 Display Off for high temp 1 = Display Off
STATE 3 BIT 7 Waiting Trigger 1 =Waiting trigger
102 1
FLAGS BIT 8 Datalogger Triggered 1 = Triggered
BIT 9 Datalogger stopped 1 = Stopped
BIT 10 (↕) --- ---
BIT 11 Wink ON 0 = OFF, 1 = ON
BIT 12 Signalling Module Input Status 0 = Not active, 1 = Active
BIT 13 KK function 0 = OFF, 1 = ON
BIT 14 --- ---
BIT 15 Local Bus Digital Input 0 = OFF, 1 = ON
Author Title EN
Doc. No
17/40
Rel # of
Name Bit Description Notes
addr item
BIT 0 Vaux Required
BIT 1 (↕) Contact Wear Pre-alarm
BIT 2 (↕) Contact Wear Alarm
BIT 3 (↕) L Pre-alarm
BIT 4 (↕) L Timing
BIT 5 (↕) --- ---
BIT 6 (↕) --- ---
STATE 4 BIT 7 (↕) --- ---
103 1
ALARM BIT 8 (↕) --- ---
BIT 9 --- ---
BIT 10 --- ---
BIT 11 (↕) OT Pre-alarm
BIT 12 (↕) OT Alarm
BIT 13 (↕) OT Alarm (Blocked Trip)
BIT 12 --- ---
BIT 15 (↕) --- ---
BIT 0 (↕) --- ---
BIT 1 (↕) --- ---
BIT 2 (↕) --- ---
BIT 3 (↕) --- ---
BIT 4 (↕) --- ---
BIT 5 --- ---
BIT 6 --- ---
STATE 5 BIT 7 (↕) --- ---
104 1
ALARM BIT 8 (↕) --- ---
BIT 9 --- ---
BIT 10 --- ---
BIT 11 --- ---
BIT 12 --- ---
BIT 13 (↕) --- ---
BIT 14 (↕) Iw Warning
BIT 15 (↕) LC1 Alarm
BIT 0 (↕) LC2 Alarm
BIT 1 (↕) --- ---
BIT 2 (↕) --- ---
BIT 3 (↕) --- ---
BIT 4 (↕) --- ---
BIT 5 (↕) CB Device error ---
BIT 6 (↕) TC Error
STATE 6 BIT 7 (↕) Rating Plug Error
105 1
ALARM BIT 8 (↕) Key Plug Error
BIT 9 Internal Error
BIT 10 --- ---
BIT 11 --- ---
BIT 12 Invalid Date
BIT 13 (↕) Configuration Error
BIT 14 (↕) CB Status Error
BIT 15 --- ---
Author Title EN
Doc. No
18/40
Rel # of
Name Bit Description Notes
addr item
BIT 0 --- ---
BIT 1 --- ---
BIT 2 --- ---
BIT 3 --- ---
BIT 4 --- ---
BIT 5 --- ---
BIT 6 --- ---
STATE 7
INPUTS BIT 7 --- ---
106 1
/OUTPUTS BIT 8 Relay P1 contact 0 = open, 1 = closed
BIT 9 Relay P2 contact 0 = open, 1 = closed
BIT 12 --- ---
BIT 13 --- ---
BIT 14 --- ---
BIT 15 --- ---
BIT 0 (↑) L tripped 1 = L trip
BIT 1 (↑) --- ---
BIT 2 (↑) --- ---
BIT 3 (↑) I tripped 1 = I trip
BIT 4 (↑) --- ---
BIT 5 (↑) --- ---
STATE 8 BIT 6 --- ---
107 1 LATCHED BIT 7 (↑) OT tripped 1 = OT trip
note 3 BIT 8 --- ---
BIT 9 (↑) --- ---
BIT 10 (↑) --- ---
BIT 11 (↑) --- ---
BIT 12 --- ---
BIT 13 (↑) --- ---
BIT 14 --- ---
BIT 15 --- ---
BIT 0 (↑) Electronic Trip Test ---
BIT 1 (↑) Simulated Trip from Test Unit ---
BIT 2 (↑) External Input Trip ---
BIT 3 (↑) Hardware Error Trip ---
BIT 4 --- ---
BIT 5 --- ---
STATE 9 BIT 6 --- ---
LATCHED BIT 7 --- ---
108 1
BIT 8 --- ---
note 3
BIT 9 --- ---
BIT 10 --- ---
BIT 11 --- ---
BIT 12 --- ---
BIT 13 --- ---
BIT 14 --- ---
BIT 15 TRIP command fail 1= TRIP command failed
note 2: GLITCH registers are automatically cleared after reading.
note 3: LATCHED registers are set when the associated event happens; they are seret only by “CB RESET” or “TRIP RESET”commands.
Author Title EN
Doc. No
19/40
8.5 TIME
Rel # of
Name Description
addr item
100 1 Day Number of days from 31/12/1999
101 1 Hour & minute MSB = Hour, LSB = minute
102 1 Second 0 – 59
103 1 Millisecond 0 -999
________________________________________________________________________________________________________
U As shown in REGISTER MAP (3.2), the TIME update could be done only using modbus function 16. In order to modify
the Time it is necessary to open the programming session, the data come immediately modified and not at the end of the
programming session as it happens for the normal parameters, therefore the abandonment (abort) of the programming
session do not cancel the carried out modification.
It’s recommended to update simultaneously all four TIME registers.
________________________________________________________________________________________________________
8.6 RUN-TIME MEASURES

The measure limits shown in column “Notes” are depicted in MEASURE LIMITS AND REPRESENTATIONS.
Rel # of
Name Description Notes
addr item
Not available → 232-1
200 2 Maximum current (rms) [A] I < IMIN → 0
I > IMAX → IMAX
0→ Not available,
1→ I1
202 1 Maximum current phase Not available → 0
2→ I2
3→ I3
203 2 I1 phase current (rms) Not available → 232-1
205 2 I2 phase current (rms) [A] I < IMIN → 0
207 2 I3 phase current (rms) I > IMAX → IMAX
8.7 INFORMATION
Rel # of
Name Range Description
addr item
700 1 Slave ID 0x11 PR122/VF
701 1 SW version Major + minor
702 1 Product Standard Reference 0 0→IEC
703 1 ---
704 1 In (nominal current) 800 ÷ 2500 [A]
705 1 CB type TAB_CB_TYPE TAB_CB_TYPE
706 8 CB Serial Number ASCII format characters ASCII format characters
714 1 Datalogger max file 0÷3 0÷3
715 1 Datalogger max address 0 ÷ 65535 0 ÷ 65535
0 = None (free running)
1 = Any Alarm
716 1 Datalogger Trigger 0÷4 2 = L Timing
3= Any Trip
4 = Custom
717 1 Day of Dlogger trigger Number of days from 31/12/1999
718 1 Hour & minute of Dlog trigger Hour & minute MSB = Hour, LSB = minute
719 1 Second of Dlog trigger Seconds
720 1 Millisecond of Dlog trigger Milliseconds
721 2 --- --- ---
723 6 CB name ASCII format characters
Author Title EN
Doc. No
20/40
8.8 PARAMETERS CONFIGURATION 1
Rel # of
Name Range Description
addr item
1000 1 Product execution 1 0ÆLI
1001 8 Relay Serial Number ASCII format characters ---

Rel addr # of item Name Range Description
Bit Bit = 0 Bit = 1
0 --- ---
1 --- ---
0x0000
1020 1 Unit configuration ÷ 2 --- ---
0x003F 3 --- ---
4 --- ---
5 --- ---
6 Operating mode = Local Operating mode = Remote
0 = ENG
1 = ITA
1021 1 Language 0÷4 2 = FRA
3 = GER
4 = SPA
0 = 6.6 Hz
1 = 16.6 Hz
1022 1 Nominal Frequency 0÷3
2 = 25 Hz
3 = 50 Hz
Slave Address
1028 1 1 ÷ 247 1 ÷ 247
(external bus only)
Addressing Type 0 = standard
1029 1 0÷1
(external bus only) 1 = ABB
Baud rate 0 = 9600
1030 1 0÷1
(external bus only) 1 = 19200
0 = “E,8,1”
Protocol Type 1 = “O,8,1”
1031 1 0÷3
(external bus only) 2 = “N,8,2”
3 = “N,8,1”
Author Title EN
Doc. No
21/40
Rel
# of item Name Range Description
addr
1051 1 Measurement store time 5 ÷ 120 step 5 [min] 5 ÷ 120 min
1067 1 P Relays Contact config TAB_P_RELE_CONFIG TAB_P_RELE_CONFIG
1068 1 P1 Function 0 ÷ 65535 TAB_RELAYS_FUNCTION
1069 1 P1 Delay 0.00 ÷ 100.00 step 0.01 [s] 0 ÷ 10000 [s*10-2]
1071 1 P2 Delay 0.00 ÷ 100.00 step 0.01 [s] 0 ÷ 10000 [s*10-2]
1073 1 P3 Delay 0.00 ÷ 100.00 step 0.01 [s] 0 ÷ 10000 [s*10-2]
1075 1 P4 Delay 0.00 ÷ 100.00 step 0.01 [s] 0 ÷ 10000 [s*10-2]
Programmable Input 0 = Active low
1076 1 0x0000 ÷ 0x0001
config 1 = Active high
0 = Generic
1 = External TRIP
Programmable Input 2 = Trip reset
1077 1 0÷5
Function 3 = ---
4 = Dial Local
5 = Reset Signalling Module
1078 1 Programmable Input Delay 0.00 ÷ 100.00 step 0.01 [s] 0 ÷ 10000 [s*10-2]
0 = Data Logger = OFF
1079 1 Data Logger Config 0x0000 ÷ 0x0001
1 = Data Logger = ON
Standard:
Standard: 0 ÷ 3 0 = None (free running)
1080 1 Data Logger Trigger Type Custom 256 ÷ 65535 1 = Any Alarm
(see Trigger setting) 2 = L Timing
3 = Any Trip
1081 1 Data Logger Stop Delay 0.00 ÷ 10.00 step 0.01 [s] 0 ÷ 1000 [s*10-2]
0 = 600 Hz
1 = 1200 Hz
1082 1 Data Logger Frequency 0÷3
2 = 2400 Hz
3 = 4800 Hz
1083 --- ---
1084 5 CB TAG name Characters in format ASCII
1089 5 User data Characters in format ASCII
1094 1 ---
Number of days from
1095 1 Date of installation CB
31/12/1999
Number of days from
1096 1 Date of last maint CB
31/12/1999
1097 1 ---
Startup current activation
1098 1 0.10 ÷ 10.00 step 0.10 [In] 10 ÷ 1000 [In*10-2]
threshold
Author Title EN
Doc. No
22/40
8.11 PARAMETERS PROTECTION SET1
The following table shows parameters included in protections.
Rel addr # of item Name Range Description

Bit Bit = 0 Bit = 1
0 --- ---
1 --- ---
1100 1 Prot L configuration
2 --- ---
3 --- ---
4 --- ---
1101 --- ---
1102 --- ---
1103 --- ---
1104 1 Prot L threshold 0.40 ÷ 1.00 step 0.01 [In] 40 ÷ 100 [In*10-2]
1105 1 Prot L time 3 ÷ 102 step 3 [s] 300 ÷ 10200 [s*10-2]
Bit Bit = 0 Bit = 1
0 Prot disable Prot enable
1 --- ---
1128 1 Prot I configuration Start Up Th Start Up Th
2
= OFF = ON
3 --- ---
4 --- ---
1129 1 Prot I threshold 1,5 ÷ 10 step 0.1 [In] 150 ÷ 1000 [In*10-2]
1130 1 Prot I start up threshold 1,5 ÷ 10 step 0.1 [In] 150 ÷ 1000 [In*10-2]
1131 1 Prot I start up time 0.10 ÷ 30.00 step 0.01 [s] 10 ÷ 3000 [s*10-2]
1165 --- --- --- ---
Bit Bit = 0 Bit = 1
0 --- ---
1171 1 Prot OT configuration 1 Trip disable Trip enable

2 --- ---
3 --- ---
4 --- ---
Bit Bit = 0 Bit = 1
1172 1 Load control configuration 0x0000 ÷ 0x0007 0 Iw Th disabled Iw Th enabled
1 LC1 Th disabled LC1 Th enabled
2 LC2 Th disabled LC2 Th enabled
1173 1 Warning current Iw 0.30 ÷ 10.00 step 0.05 [In] 30 ÷ 1000 [In*10-2]
1174 1 LC1 threshold 50 ÷ 100 step 1 [%I1] 50 ÷ 100 [%I1]
1175 1 LC2 threshold 50 ÷ 100 step 1 [%I1] 50 ÷ 100 [%I1]
Author Title EN
Doc. No
23/40
8.12 TRIP HISTORY
Rel # of
Name Description
addr item
0 MARKER (0 = valid)
Trip Type
1
TAB_TRIP_TYPE
2 N° trip
3 Date (day)
4 Date (MSB = hours, LSB = min)
5 Date (seconds)
2000 19 Trip history no. 1 (new) 6 Date (ms)
7÷8 Current I1
9÷10 Current I2
11÷12 Current I3
13÷14 ---
15 Contact wear
16 TAB_TRIP_TYPE
17 TAB_TRIP_TYPE
18 TAB_TRIP_TYPE
2019 19 Trip history N° 2 “
… 19 Trip history N° 3 “
… … …. “
2361 19 Trip history N° 20 (old) “
Table 7 TAB_TRIP_TYPE
Trip type word 1 word 16 word 17 word 18
L 1 In Active threshold = value / 512 See addr. 1100 ---
I 7 0x0000 In Active threshold = value / 512 See addr. 1128
OT 10 Temperature °C = value * 0,073855 See addr. 705 See addr. 704
EXT 18 See addr. 1078 See addr. 1076 See addr. 1077
Hw Trip 21 See addr. 105 See addr. 1401 See addr. 1500
Author Title EN
Doc. No
24/40
8.13 MEASURES HISTORY
Rel # of
Name Description
addr item
0 MARKER (0 = valid)
History code:
0 = NORMAL_HISTORY
1
1 = POWER_UP
2 = NEW_PERIOD
2 Period from last save (minutes)
3 Number of days from 31/12/1999
4 MSB = Hour, LSB = minute
Measure history 5
2500 24
n° 1 (new) 6
7
8
9 Phase with max. current (1 = I1, 2 = I2, 3 = I3)
10 Maximum current LOW
11 Maximum current HIGH
12 ---
13 ---
2524 24 Measure history n°2 “
… 24 … “
3076 24 Measure history n°25 (old) “
8.14 LOG EVENTS

Rel # of
Name Description
addr item
MARKER (0 = valid)
Event type
TAB_LOG_EVENTS
Number of days from 31/12/1999
3300 6 Log event n° 1 (new)
MSB = Hour, LSB = minute
Seconds
Milliseconds
3306 6 Log event n° 2 “
3312 6 Log event n° 3 “
… 6 … “
3768 6 Log event n° 79 “
3774 6 Log event n° 80 (old) “
Author Title EN
Doc. No
25/40
9. TABLES
Table 8 TAB_RELAYS_FUNCTION Table 11 TAB_LOG_EVENTS
Value Description Value Event type
0 None 0 Parameters changed
1 L prealarm 1 Signalling reset
2 L timing 2 CB isolated
3 --- 3 CB connected
4 CB open
4 L trip
5 CB closed
5 --- 6 CB status defined
6 I trip 7 CB status undefined
7 --- 8 ---
8 Any trip 9 ---
9 Any Alarm 10 Trip command fail
10 LC1 11 ---
12 Remote mode operating mode
11 LC2
13 Test session closed
Custom 14 Test session opened
256 ÷ 65535
Setting of the activation relay function 15 Test unit not connected
16 Test unit connected
17 ---
Table 9 TAB_P_RELE_CONFIG 18 ---
19 ---
Bit = 0 Bit = 1 20 ---
Bit 0 Relay P1 not latched Relay P1 Latched 21 Cw Preal OFF
Bit 1 Relay P2 not latched Relay P2 Latched 22 Cw Preal ON
Bit 2 Relay P3 not latched Relay P3 Latched 23 Cw Alarm OFF
Bit 3 Relay P4 not latched Relay P4 Latched 24 Cw Alarm ON
25 L Preal OFF
Bit 4 Contact P1 NO Contact P1 NC
26 L Preal ON
Bit 5 Contact P2 NO Contact P2 NC 27 L Timing OFF
Bit 6 Contact P3 NO Contact P3 NC 28 L Timing ON
Bit 7 Contact P4 NO Contact P4 NC 41 OT Warning OFF
42 OT Warning ON
43 OT Alarm OFF
Table 10 TAB_CB_TYPE 44 OT Alarm ON
45 OT Alarm Block OFF
CB Valore 46 OT Alarm Block ON
E2VF800 0 79 Iw Alarm OFF
1 80 Iw Alarm ON
E2VF1000 2 81 Lc1 OFF
3 82 Lc1 ON
E2VF1250 4 83 Lc2 OFF
84 Lc2 ON
5
93 CB Device Alarm OFF
E2VF1600 6
94 CB Device Alarm ON
7 95 TC Alarm OFF
E2VF1600 8 96 TC Alarm ON
9 97 Rating Plug Alarm OFF
E3VF800 10 98 Rating Plug Alarm ON
11 99 Key Plug error OFF
E3VF1000 12 100 Key Plug error ON
13 107 CB status error OFF
108 CB status error ON
E3VF1250 14
109 L tripped
15 110 ---
E3VF1600 16 111 ---
17 112 I tripped
E3VF2000 18 113 ---
19 114 ---
E3VF2500 20 115 ---
21 116 OT tripped
E3VF1600 22 125 Electronic trip test
126 Simulated trip from test unit
23 127 External input trip
E3VF2000 24 128 Hardware Error Trip
25 129 Aux On
E3VF2500 26 130 Trip Reset Ev
27 131 History Trip Reset
E2VF1200 28 132 History Measure Reset
29 133 Energy Reset
134 Aux Voltage On
E3VF1200 30
135 Aux Ext On
31
Author Title EN
Doc. No
ABB Lxxxx N. Doc. 1SDHxxxxxxR0001 Tot. Pag.
26/40
10. CHECK OF PARAMETERS ACCURACY
During the programming the accuracy checks of new parameters set are carried out, in particular:
1. All parameter values are in the admitted ranges (also if relevant to protection in off)
In case one of these checks failed the reply of exception ‘ILLEGAL DATA ERROR’ is done supplying in the ‘Programming Fail
Error Code’ the relevant error code.
11. OPERATION DESCRIPTION

11.1 PARAMETER PROGRAMMING
_______________________________________________________________________________________________________
U There is a validity programming session timeout of 5 minutes once empire the session is aborted; to extend it of 5
minutes more it is sufficient to re-send an open programming session command.
U Through the system bus it is allowed to open a programming session only in REMOTE functioning mode.
________________________________________________________________________________________________________
Open Stop
session Send session
parameters
Check parameters Mem in flash
Progr.ok = 1
Progr.ok = 1 Progr.fail = 0
Progr.fail = 1 Programming session open
Figure 1 Programming session correctly handled
________________________________________________________________________________________________________
Open Stop
Send
session session
parameters
i i
Check parameters Reload device

internal parameters
Progr.ok = 1 Progr.ok = 0
Progr.fail = 1 Progr.fail = 1
Programming session open
Figure 2 Programming failed
Author Title EN
Doc. No
27/40
Open Send Abort
session sessione
parameters
Reload flash
parameters
Progr.ok = 1 Progr.ok = 0
Progr.fail = 1 Progr.fail = 0
Programming session open
Figure 3 Programming aborted
11.2 DATALOGGER
Through the datalogger functionality is possible to execute the recording of some analogic and digital writings for a temporal
window of definable duration and synchronized by a setteble event.
The following figure shows in yellow the temporal window, the trigger and the available samples.
Stop Delay
Measures available
Samples
Pre-trigger
Trigger
1/Freq Recording time
Figure 4 Datalogger example
The user can select the sampling frequency, the trigger event type and the stop delay for obtaining the pre-trigger expected
towards the selected event.
According to the stop delay set there will be 3 situations:
Stop delay = 0 Stop delay < recording time Stop delay > recording time
Trigger Trigger Trigger

Figure 5 Three situations of recording
Author Title EN
Doc. No
28/40
The maximum length of recording is defined exclusively by the sample frequency set as described in table TAB DLOG
RECORDING TIME, in the case the sum of the stop delay and the time elapsed between a restart trigger is lower than the
maximum recording time, there will be a recording time lower than the maximum one as shown in the following figure:
Recording time
Stop delay
Restart Trigger Trigger

Max recording time
Figure 6 Recording time lower than maximum
11.2.1 Recorded data

When the trigger event happens or at the reception of the stop command, the following data are recorded in the box
INFORMATION:
• Datalogger Trigger that shows the trigger type that has caused the datalogger stop.
• Time-stamp of the trigger event (day/hour+minutes/seconds/milliseconds) (4 word)
• Datalogger max file that shows which is the max file with importante data that can be apply by function 70
• Datalogger max address that shows which is the max address with important data that can be apply by function 70
For each sampling period 16 word are recorded with, in order, the following information:
1. current sample I1 (1 word) 13. digital inputs (1 word)
2. current sample I2 (1 word) 14. alarms1 (1 word)
3. current sample I3 (1 word) 15. alarms2 (1 word)
From 4. to 12. dummy 16. trip (1 word)
The data recorded may be read (only when the datalogger is stopped) in the MODBUS MAP.
11.2.2 Trigger state information

In STATE the following information of datalogger state are supplied:
• Waiting trigger: shows that the datalogger is suitable and is waiting for the happening of the event chosen as trigger
• Datalogger triggered: shows that the trigger event happened and the datalogger is under recording
• Datalogger stopped: shows that the recording was completed because it finished or completed or by a stop datalogger
command
The datalogger recordings may be read in the MODBUS MAP only when the datalogger is not in phase of recording, that is when
the datalogger stopped is signaled.
Author Title EN
Doc. No
29/40
11.2.3 Datalogger settings
In PARAMETERS CONFIGURATION the configuration parameters of datalogger, described below, are present.
Note: following any modification of datalogger parameters this is stopped, to restart it is necessary to reset the trigger with the
restart trigger
11.2.3.1 Datalogger activation

To function datalogger it is necessary to activate it by HMI or by the system with datalogger config. parameter
11.2.3.2 Datalogger activation

It’s necessary to send a command of restart trigger (by HMI or by system) to activate the datalogger
11.2.3.3 Saving frequency setting

Both by HMI and by system it is possible, through the datalogger frequency parameter, the frequency by which the measures
among 4 fixed frequencies 600Hz, 1200Hz, 2400Hz or 4800Hz are saved.
The memory used by datalogger is 512Kbyte therefore memorizing 16 word (32 byte) the maximum number (theoretic) of
recordings is 16384, therefore, according to the frequency set different recording times are obtained as shown in the following
table:
Frequency Recording time
600 Hz 27,307 s
1200 Hz 13,653 s
2400 Hz 6,827 s
4800 Hz 3,413 s
Table 12 TAB DLOG RECORDING TIME
11.2.3.4 Trigger setting
11.2.3.4.1 Trigger standard

By HMI it is possible to select, through the datalogger trigger type parameter, one of the following trigger:
0. None (free running)
1. Any alarm
2. L timing
3. Any Trip
In case 1. None (free running) no trigger is setted and the datalogger may be stopped only with a stop command by HMI or by
system.
11.2.3.4.2 Trigger custom

Writing in “Data logger Trigger Type” (inserted on PARAMETERS CONFIGURATION a value on range 0-3, will set up one
of the three standard trigger (0 = None, 1 = Any alarm, 2 = L timing, 3 = Any Trip); writing a value greater than list values, it’s
possible to configure custom functionality as described in the following table.
Bit di Datalogger Trigger Type

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
OR Byte placement (offset from 0x100
Not Used Bits mask to be monitored in the byte
AND address) in the STATE
Bit 7 ÷ 0: bit mask used by trigger.

Bit 12 ÷ 8: byte offset in the device STATE (numeration starts from 1).
Bit 14 ÷ 13: Not Used.
Bit 15: if 0 means OR function among selected bits (mask), if 1 means AND function.
Author Title EN
Doc. No
30/40
Example 1:
To configure data logger trigger type to stop when at least one of the listed conditions occur ( L tripped, S tripped, I
tripped and G tripped) the value to write is:
Bit 7 ÷ 0 = 00101011 (1 in correspondence of desired bits).

Bit 14 ÷ 8 = 00001111 = 15 ( byte containing conditions is the 15th of STATE).
Bit 15 = 0 (OR function).
Therefore Data logger Trigger Type = 0x0F2B
Example 2:
To configure data logger trigger type to stop when all the listed conditions occur (UV Timing, RV Timing) the value to
write is:
Bit 7 ÷ 0 = 10000010 (1 in correspondence of desired bits).

Bit 14 ÷ 8 = 0001001 = 9 ( byte containing conditions is the 15th of STATE).
Bit 15 = 1 (AND function).
Therefore Data logger Trigger Type = 0x8982
11.2.3.5 Stop delay setting

Both by HMI and by the system it is possible to set, through a datalogger stop delay parameter, the stop delay in the range 0.00
[s] at 10.00 [s] with step of 0.01 [s].
11.2.4 Available commands for the datalogger

It is possible to send the following commands to the datalogger activation/disactivation
• Restart trigger: after this command the dataloger trigger is reset.
• Stop acquisition: after this command the possible recording of the datalogger is stopped
In case there is an opening these commands are not accepted and will be reply exception BUSY
Author Title EN
Doc. No
31/40
11.2.5 Functioning description
When the functionality is activate, the measures are continuously recorded and with a frequency set in a FIFO memory.
The recording will end after a stop delay setted according to the trigger event.
________________________________________________________________________________________________________
U The recording will end 10 ms after a trip.
________________________________________________________________________________________________________
The following recording will be activated after a Restart trigger command.
The recording will end also after a Stop Datalogger command.
If the parameters relevant to the datalogger are changed while it is active, the recording will be cleared and a new recording will
start according to the new parameters.
Available samples Available

samples
Samples
Trigger
Waiting Trigger
Datalogger Triggered
Datalogger Stopped Rit stop
Modbus Commands
Restart Stop Restart

Datalogger activation
Figure 7 Example of stop datalogger for trigger or for stop command and restart trigger command
Author Title EN
Doc. No
32/40
11.3 MEASURE HISTORY DATA STRUCTURE
The measure history log (8.13) contains the following information:
• Marker
• History code
• Saving period
• Day
• Hour + minute
• Total mean active power
• Maximum current
• Phase of Maximum current (I1, I2, I3)
The Marker (word length) is a general code for all non-volatile memory structure used to distinguish valid data (marker = 0x0000)
from not valid data (marker ≠ 0x0000)
The history code has 3 types of recorded data:

Nr. 0 = Normal record.
Nr. 1 = First record after a supply power-up.
Nr. 2 = First record after a saving period change.
Saving period mean, in the case nr.0 and nr.2, the elapsed time in minutes from previous record.
In case nr.1 an almost empty structure is recorded only to show power supply returns; only Marker and History code have mean.
Day, hour and minutes are the time-stamp of structure recording time.
Could take place the following situations:
1. Normal situation (history code 0) with saving period = 1hour:
1h 1h 1h
2. For e.g. after 27minutes from last recording time the Saving period is changed to 10minutes (history code 2):
1h 27m 10m
3. For e.g. after 14minutes from last recording time there is an auxiliary power supply failure and then a new power-up
(history code 1):
1h 14m … 1h
Time gap Power-up

considered
NULL
The striped histograms are those that match with historical code different from “normal”
Author Title EN
Doc. No
33/40
11.4 RELAY FUNCTIONALITY
In PARAMETERS CONFIGURATION some parameters are present that must be opportunely programmed to carry out the
activation funtions of P1 ÷ P4 relay (PR120/K).
In presence of the contact module (4 relay) the relevant relays can be managed as shown: it is possible an event (a specific state
situation) following up to activate with the desired relay, the desired relays in an independent way. Following the functionality is
shown.
Times lower than activation delay
Activation delay
Relay state Relay activation
Event
A B C
Figure 8 Relay functionality
In figure 3 situations A, B, C are shown with the activation condition occurred, in situations A and B this doesn’t last for a time
higher than the activation delay, therefore the relay is not activated: in situation C the relay is activated after a delay set and
disactivated immediately (with a minimum selectable activation time) at the lacking of the condition of valid activation.
In the following figure the situation of the operation of the minimum time of relay activation is shown when the activation event
becomes not checked before the expiring of this time.
Note: the minimum activation time is selectable only for activation functions CUSTOM
Activation delay T min activation
Relay state Relay activation
Event
A B C
Figure 9 Effect of minimum time of relay activation
Time lower than min. time

activation
Author Title EN
Doc. No
34/40
11.4.1 Settings of relay fucntionality of the signaling module
In PARAMETERS CONFIGURATION the configuration parameters, described below, of the relay are present.
11.4.1.1 Settings of the configuration of relay contacts

In PARAMETERS CONFIGURATION in the record P relays Contact Config it is possible to choose for each relay if the contact
may be normally open or normally close and if it may have the latched.
11.4.1.2 Setting of the activation relay function

By HMI the relevant activation function for each relay may be programmed choosing it among a list of standard functions while
by the system other more complex functions said custom may be programmed.
11.4.1.2.1 Standard function of relay activation

By HMI one of the following standard functions can be programmed:
0. None (no activation)

1. L prealarm
2. L timing
3. L trip
4. I trip
5. Any trip
that clearly define which event determines the relay activation (or the disactivation if the relay is defined as normally close)
11.4.1.2.2 Custom function of relay activation

By the system, it is possible, besides the limits shown above, select the activation function more sophisticated in the following
way:
Writing in the record ‘namerelay Function’ in PARAMETERS CONFIGURATION a value included between 0 and 8, one of
the 9 types of the above standard functions will be set, writing a higher value the function will be considered custom type and
explained as follows:
Bit of function relay
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
OR Minimum
Byte placement in STATE Bits mask to be monitored in the trigger
AND activation T
Bit 7 ÷ 0: bit mask used in the activation relay function.

Bit 12 ÷ 8: byte offset in the device STATE (numbering starts from 1).
Bit 14 ÷ 13: minimum activation time of the relay (00 = none, 01 = 50ms, 10 = 100ms, 11 = 200ms).
Bit 15: if 0 it means OR function among the selected bits, if 1 it means AND function among the selected bits.
Example 1:
To configure the activation function in order that the relay will activate when even one of the listed conditions occur : L
tripped, S tripped, I tripped e G tripped, the value to write is:
Bit 7 ÷ 0 = 00101011 (1 in correspondence of the desired bit).

Bit 14 ÷ 8 = 00001111 = 15 ( byte containing conditions is the 15th of STATE (numbering starts from 1).
Bit 15 = 0 (OR function).
Therefore relay function = 0x0F2B
Author Title EN
Doc. No
35/40
Example 2:
To configure the trigger in order that the datalogger will stop when simultaneously the listed conditions occur: UV
Timing, RP timing, the value to write is:
Bit 7 ÷ 0 = 10000010 (1 in correspondence of desired bit).

Bit 14 ÷ 8 = 0001001 = 9(byte containing conditions is the 9th of STATE (numbering starts from 1).
Bit 15 = 1 (AND function).
Therefore Datalogger Trigger Type = 0x8982
11.4.1.3 Setting of activation delay

Both by HMI and by system it is possible to set, through parameter ‘namerelay Delay’ the activation delay in range 0.00 [s] to
100.00 [s] with step of 0.01 [s].
11.4.1.4 Reset of signallings

As shown in para. COMMANDS, it is provided the reset signalling command following up the contacts are placed to their rest
state (open or closed according to the programming); if the function of the relay activation is still valid, the reset command
causes no changes of the same relay state.
11.5 SIGNALLING MODULE INPUT FUNCTIONALITY

In the signalling module there i also the input with configurable functionality.
Activation delay
Action Action
Input validity A B C
Figure 10 Signalling module input functionality
In figure are shown 3 situations (A, B, C) with the input state valid.
In situations A and B the input is not valid for a time higher than the activation delay therefore the action associated has not
occurred; instead in situation C the action begins after the set delay.
Author Title EN
Doc. No
36/40
11.5.1 Settings of input signalling module
In PARAMETERS CONFIGURATION the parameters configurations of this input are present.
11.5.1.1 Settings of input configuration

In Programmable Input Config of PARAMETERS CONFIGURATION it is possible to select the level at which to consider active
the input:
1. low active input
2. high active input
11.5.1.2 Settings of input function (ACTION)

In Programmable Input Function of PARAMETERS CONFIGURATION it is possible to select the action associated to the input,
that is the action that after the programmed delay occurs after the activation (high or low) of the input.
It’s possible to select one of the following actions:
1. Generic : No specific action is associated to the input that can be read in the state as generic input
2. Trip test: when the input is active for the specified delay a trip test is carried out
3. Trip reset: when the input is active for the specified delay a trip reset is carried out
4. Dial Local: when the input is active for the specified delay the local mode of the dialogue is forced
5. Signalling Module Reset: when the input is active for the speficied delay the relay state is reset
11.5.1.3 Setting of input activation delay

It’ s possible to set, by the parameter ‘Programmable Input Delay’ the activation delay in the range 0.00 [s] to 100.00 [s] with step
of 0.01 [s].
11.6 CB STATE INFORMATION

The device using the following dedicated input reports CB state:
• CB open
• CB close
• CB connected/withdrawn
• Springs charged
The device filters and checks CB state producing the following information:
• CB open/close
• CB state undefined
• CB state error
• CB connected/withdrawn
• Springs charged/discharged
The following table shows the information on CB:

Value
State Notes
0 = Open 1 = Close
Input CB open = 1 The state of inputs open and
Input CB open = 0
CB open/close Input CB close = 0 close has to remain steady for
Input CB close = 1
NO flowing current at least 30 ms
Author Title EN
Doc. No
37/40
Value
State Notes
0 = Defined 1 = Undefined
Input CB open = 1
Input CB close = 0
Input CB open The state of inputs open and
NO flowing current
CB undefined = close has to remain steady for
Or
Input CB close at least 30 ms
Input CB open = 0
Input CB close = 1
Value
State Notes
0 = No error 1 = CB error
Input CB open = 1 The state of inputs open and
CB error Other chases Input CB close = 0 close has to remain steady for
Current flowing at least 30 ms
Value
State Notes
0 = withdrawn 1 = connected
CB The input has to remain steady
Input CB connected = 0 Input CB connected = 1
withdrawin/connected for at least 1000 ms
Value
State Notes
0 = discharged springs 1 = charged springs
Springs The input has to remain steady
Input charged springs = 0 Input charged springs = 1
charged/discharged for at least 200 ms
11.7 STATISTICAL DATA

Devices produces some statistical data relevant to system bus communication and to CB operations, in particular:
1. communication statistical data
a. received messages nr.
b. Received messages ns. with crc error
c. Set messages nr.
d. Slave Busy exception responses nr.
e. Total exception responses nr.
Must be: a = b + c + nr. Broadcast messages

Data described above are NOT updated in self-supply device mode.
________________________________________________________________________________________________________
U There is a copy of each bus for the statistic communication data in order that the cancelling of the same will not compromise the reading by
other bus.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
2. CB operation statistical data
a. Contact wear
b. Total protection trip number
3. CB operation statistical data NOT updated in self-supply device mode
c. Total operation nr.
d. Manual operation nr.
e. Protection trip nr.
f. Protection trip fail nr.
g. Trip test nr.
Author Title EN
Doc. No
38/40
The relationship between them: c=d + e + f + g , b ≥ e + f.
The following diagram shows the CB statistical data calculation method:
No
Trip open?
(d)manual oper.+=1
No New open? Vaux
present?
No
(c)Total operation += 1
Protection No
(g)Trip test += 1
No Protection open?
open?
No Trip
(b)Total protection trip nr. += 1 (e)Protection trip += 1 (f)Trip fail += 1
Failed?
Save statistical data in

non-volatile memory
END
11.8 RELAYS YO AND YC

By proper commands (CB Open and CB Close) it is possible to operate on relays YO and YC present on dialogue unit.
In case of command acceptance, the interested relay is closed for 120 ms. The following table shows the checks carried out for the
acceptance of the commands and the relevant activation.
Command Acceptance conditions Relay YO RelayYC Notes

CB connected In case the acceptance
CB Open It is excited for 120 ms
Test Unit not connected conditions are not
CB connected verified the exception
CB Close CB not undefined It is excited for 120 ms ILLEGAL FUNCTION
Test Unit not connected will be give back
The relay YO is controlled also after a back up protection (the CB is closed also after an open command); in this case the relay
YO is controlled with an excitation (120 ms)–idle (50 ms) up to the CB is not open.
Author Title EN
Doc. No
39/40
11.9 COMAMND EXECUTION CONDITIONS
11.9.1 Command execution conditions:
To the condition below reported must be appended:
1. By external bus the commands are accepted only in remote operation device mode.
2. With Test unit connected only CB OPEN command is accepted
Command type Action Acceptance conditions Notes

Dummy command No action Always accepted
This is the only command
CB connected and opening or closing not
CB Open Active for 200 ms output YO accepted when the unit test is
executing
connected.
CB connected, CB open, state CB not
CB Close Active for 200 ms output YC undefined and open and close command
not executing
Reset CB Reset trip state bits Always accepted
Start Autotest Display Led Carry out display and led tests Always accepted
Start Autotest Module Contacts Carry out module contact tests Always accepted
Trip test Carry out a trip test I > 0,05 In
Trip reset Abort trip state bits Always accepted
Commute wink state of the unit
Wink toggle command Always accepted
(backlight wink)
Reset the signalling module and unit
Reset signalling Always accepted
master on local bus
Table 13 COMMAND EXECUTION CONDITIONS
11.10 MEASURE LIMITS AND REPRESENTATION

Measure Special value Description Modbus Local Display
CB state Inaccuracy / current
Not available 0xFFFFFFFF
presence
Currents
Too low I < Imin 0 •••
Saturation I > Imax Imax I > xxx A
CB state Inaccuracy / current
Max current polarity Not available 0 (listed)
presence, all I < Imin
Contact wear Saturation CW > 100% 65000 100%
Legend: min = 0,05 In

Imax = 10 In
Note: It is advisable to use the visualization shown in column “local Display” also on remote visualization devices.
11.11 CONTACT WEAR

The contact wear is calculated as the usury sum owed at every single CB open and it’s explicit in % (0 ÷ 100[%]):
I’s available in format 0 ÷ 65000 (0 = 0%, 65000 = 100%), therefore to obtain the percentage is necessary to divide the value for
650.
Author Title EN
Doc. No
40/40

ABB SACE Division: PR122/VF Modbus System Interface

Uploaded by

Copyright:

Available Formats

ABB SACE Division: PR122/VF Modbus System Interface

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ABB SACE Division: PR122/VF Modbus System Interface

Uploaded by

Copyright:

Available Formats

ABB SACE Division

Modbus System Interface

Index of tables Page

3. ACRONYMS AND DEFINITIONS

BOOL Bit or Boolean (IEC 61131-3)

6. Available Modbus functions

6.2 Function 04 (04h) Read Input Registers

6.3 Function 06 (06h) Write Single Register

Response (echo della query)

6.4 Function 08 (08h) Diagnostic

Response (echo della query)

6.6 Function 17 (11h) Report slave ID

6.7 Function 70 (46h) Read Extended Registers

6.8.2 Illegal data address

6.8.3 Illegal data value

6.8.4 Slave device failure

6.8.5 Slave device busy

6.8.6 Exception occurrences

allowed with this • Programming session not open

Legend `: Available without further conditions

Legend `: Available without further conditions

50 PROGR FAIL ERROR CODE (8.3)

100 STAT(8.4) TIME(8.5) (*)

200 RUN TIME MEASURES (8.5)

1000 PAR. CONFIG1 ACTUAL(8.8)

2000 TRIP HISTORY (8.12)

2500 MEASURE HISTORY (8.13)

3300 LOG EVENT (0)

Extended Reg (600000)

File 2 Samples 0 ÷ Samples 4095 0 ÷ 65535 “ “

File 3 (New) Samples 0 ÷ Samples 4095 0 ÷ 65535 “ “

note 1: Signal sample with 910 → 1 In

Following the command list table with pertinent command parameters.

8.3 PROGR FAIL ERROR CODE

1 ÷ 999: See table TAB_PAR_ERR_CODE

8.6 RUN-TIME MEASURES

8.9 PARAMETERS CONFIGURATION 2

Rel addr # of item Name Range Description

1171 1 Prot OT configuration 1 Trip disable Trip enable

8.14 LOG EVENTS

11. OPERATION DESCRIPTION

Check parameters Mem in flash

Figure 1 Programming session correctly handled

Check parameters Reload device

Figure 2 Programming failed

Figure 3 Programming aborted

1/Freq Recording time

Figure 4 Datalogger example

According to the stop delay set there will be 3 situations:

Trigger Trigger Trigger

Restart Trigger Trigger

Figure 6 Recording time lower than maximum

11.2.1 Recorded data

11.2.2 Trigger state information

11.2.3.1 Datalogger activation

11.2.3.2 Datalogger activation

11.2.3.3 Saving frequency setting

11.2.3.4 Trigger setting

11.2.3.4.1 Trigger standard