|
<< Click to Display Table of Contents >>
[B] Parameters for Block Tag Addressing |
B1 |
Mode 1 (one) |
RP570: RTU address, between 1 (one) and 255 or RP571: RTU router, between 1 (one) and 255 |
Mode 2 (two) |
RP570: RTU address, between 1 (one) and 255 or RP571: Partitioned value in RRPP format, where RR: RTU router, between 1 (one) and 255 (high byte of B1) and PP: RTU address, between 1 (one) and 255 (low byte of B1) |
|
B2 |
Command number. For more information, please check table Commands for Block Tags |
|
B3 |
Parameter, if necessary |
|
B4 |
Parameter, if necessary |
|
Use the Block Tags from the next table to perform a reading of data and events received via polling by PLC Tag requests with the N2 parameter equal to 0 (zero, RA: Request, priority level 1) and the N2 parameter equal to 8 (eight, RB: Request, priority level 2) or without polling by PLC Tag requests with the N2 parameter equal to 4 (four, RX: Request X).
B1 |
B2 |
B3 |
B4 |
Mode |
|
|---|---|---|---|---|---|
Mode 2 |
320 (AVM - AVS) |
Block number |
Not used |
Read-only |
|
•Element 0: Polling request. Possible values are •0: RA (Request A) •4: RX (Request X) •8: RB (Request B) •Element 1: Type of reply. Possible values are: •20: AVM_P1 (Analog Value Message, Priority 1) •21: AVM_P2 (Analog Value Message, Priority 2, 3) •22: AVS_P1 (Analog Value Message with Status, Priority 1) •23: AVS_P2 (Analog Value Message with Status, Priority 2, 3) •64: AVM_P1_CCR (Analog Value Message, Priority 1, CCR Included) •65: AVM_P2_CCR (Analog Value Message, Priority 2, 3, CCR Included) •66: AVS_P1_CCR (Analog Value Message with Status, Priority 1, CCR Included) •67: AVS_P2_CCR (Analog Value Message with Status, Priority 2, 3, CCR Included) •Element 2: LIM_CHK. Possible value is 1 (Local Limit Supervision is active) •Element 3: Status. Possible values are: •0: Normal •1: Low Alarm zone (not supported by RTU 110) •2: High Alarme zone (not supported by RTU 110) •3: Low Warning zone (not supported by RTU 110) •6: High Warning zone (not supported by RTU 110) •7: Faulty or Blocked Value •Element 4: 12-bit signed integer |
|||||
Mode 2 |
324 (IDM - IDS) |
Block number |
Not used |
Read-only |
|
•Element 0: Polling request. Possible values are: •0: RA (Request A) •4: RX (Request X) •8: RB (Request B) •Element 1: Type of reply. Possible values are: •24: IDM_P1 (Indication Message, Priority 1) •25: IDM_P2 (Indication Message, Priority 2, 3) •26: IDS_P1 (Indication Message with Status, Priority 1) •27: IDS_P2 (Indication Message with Status, Priority 2, 3) •68: IDM_P1_CCR (Indication Message, Priority 1, CCR Included) •69: IDM_P2_CCR (Indication Message, Priority 2, 3, CCR Included) •70: IDS_P1_CCR (Indication Message with Status, Priority 1, CCR Included) •71: IDS_P2_CCR (Indication Message with Status, Priority 2, 3, CCR Included) •Element 2: Status •Element 3: 16-bit unsigned integer |
|||||
Mode 2 |
328 (DVM: Buffer Event) |
Block number |
Not used |
Read-only |
|
•Element 0: Polling request. Possible values are: •0: RA (Request A) •4: RX (Request X) •8: RB (Request B) •Element 1: Type of reply. Possible values are: •28: DVM_P1 (Digital Value Message, Priority 1) •29: DVM_P2 (Digital Value Message, Priority 2, 3) •72: DVM_P1_CCR (Digital Value Message, Priority 1, CCR Included) •73: DVM_P2_CCR (Digital Value Message, Priority 2, 3, CCR Included) •Element 2: LIM_CHK. Possible value is 1 (Local Limit Supervision is active, not supported by RTUs 200 and 201) •Element 3: Status. Possible values are: •0: Normal •1: Low Alarme zone (not supported by RTUs 110, 200, and 201) •2: High Alarme zone (not supported by RTUs 110, 200, and 201) •3: Low Warning zone (not supported by RTUs 110, 200, and 201) •4: High Warning zone (not supported by RTUs 110, 200, and 201) •7: Faulty or Blocked Value •Element 4: 16-bit signed integer |
|||||
Mode 2 |
330 (PCM: Buffer Event) |
Block number |
Not used |
Read-only |
|
•Element 0: Polling request. Possible values are: •0: RA (Request A) •4: RX (Request X) •8: RB (Request B) •Element 1: Type of reply. Possible values are: •30: PCM_P1 (Pulse Counter Message, Priority 1) •31: PCM_P2 (Pulse Counter Message, Priority 2, 3) •74: PCM_P1_CCR (Pulse Counter Message, Priority 1, CCR Included) •75: PCM_P2_CCR (Pulse Counter Message, Priority 2, 3, CCR Included) •Element 2: RC. Possible value is 1 (Restarted counter) •Element 3: IV. Possible value is 1 (Invalid value) •Element 4: CT. Possible value is 1 (Changed time) •Element 5: IT. Possible value is 1 (Invalid time) •Element 6: LS. Possible value is 1 (Local storage of pulse counter values) •Element 7: IR. Possible value is 1 (Value is the result of an intermediate reading) •Element 8: EPR. Possible value is 1 (Value is the result of an end of period) •Element 9: 32-bit signed integer |
|||||
Mode 2 |
337 (DVL: Buffer Event) |
Block number |
Not used |
Read-only |
|
•Element 0: Polling request. Possible values are: •0: RA (Request A) •4: RX (Request X) •8: RB (Request B) •Element 1: Type of reply. Possible values are: •37: DVL_P1 (Digital Value Long, Priority 1) •38: DVL_P2 (Digital Value Long, Priority 2, 3) •76: DVL_P1_CCR (Digital Value Long, Priority 1, CCR Included) •77: DVL_P2_CCR (Digital Value Long, Priority 2, 3, CCR Included) •Element 2: LIM_CHK. Possible value is 1 (Local Limit Supervision is active, not supported by RTUs 200 and 201) •Element 3: Status. Possible values are: •0: Normal •1: Low Alarm zone (not supported by RTUs 200 and 201) •2: High Alarm zone (not supported by RTUs 200 and 201) •3: Low Warning zone (not supported by RTUs 200 and 201) •4: High Warning zone (not supported by RTUs 200 and 201) •7: Faulty or Blocked Value •Element 4: 32-bit signed integer |
|||||
Mode 2 |
339 (PCT: Buffer Event) |
Block number |
Not used |
Read-only |
|
|
|
•Element 0: Polling request. Possible values are: •0: RA (Request A) •4: RX (Request X) •8: RB (Request B) •Element 1: Type of reply. Possible values are: •39: PCT_P1 (Pulse Counter Telegram, Priority 1) •40: PCT_P2 (Pulse Counter Telegram, Priority 2, 3) •78: PCT_P1_CCR (Pulse Counter Telegram, Priority 1, CCR Included) •79: PCT_P2_CCR (Pulse Counter Telegram, Priority 2, 3, CCR Included) •Element 2: RC. Possible value is 1 (Restarted counter) •Element 3: IV. Possible value is 1 (Invalid value) •Element 4: CT. Possible value is 1 (Changed time) •Element 5: IT. Possible value is 1 (Invalid time) •Element 6: LS. Possible value is 1 (Local storage of pulse counter values) •Element 7: IR. Possible value is 1 (Value is the result of an intermediate reading) •Element 8: EPR. Possible value is 1 (Value is the result of an end of period reading) •Element 9: 32-bit signed integer |
|
||
Mode 2 |
305 (TSTA: Buffer Event) |
Not used |
Not used |
Read-only |
|
Values for Elements are 0: Terminal Status identity and 1: Status Flags for RTU |
|||||
Mode 2 |
306 (TSTS: Buffer Event) |
Not used |
Not used |
Read-only |
|
Values for Elements are 0: Terminal Status identity, 1: RTU Status Flags for satellite RTU, 2: Satellite line number, and 3: Satellite RTU number |
|||||
Mode 2 |
307 (TEV: Buffer Event) |
Not used |
Not used |
Read-only |
|
Values for Elements are 0: Terminal event number, 1: Info 1, 2: Info 2, 3: Info 3, 4: Info 4, 5: Info 5, and 6: Info 6 |
|||||
Mode 2 |
308 (TEVS: Buffer Event) |
Not used |
Not used |
Read-only |
|
Values for Elements are 0: Terminal event number, 1: Info 1, 2: Info 2, 3: Info 3, 4: Info 4, 5: Info 5, 6: Info 6, 7: Satellite line number, and 8: Satellite RTU number |
|||||
Mode 2 |
332 (ERMI: Buffer Event) |
Block number |
Bit number |
Read-only |
|
•Element 0: Sequence •Element 1: TYP. Possible values are 0: Single Indication or 1: Double Indication •Element 2: VAL. Possible values for single Indications are 1: ON or 2: OFF and for double Indications are 0: Intermediate position, 1: ON, 2: OFF, or 3: Intermediate position •Element 3: QUALITY. Possible values are: •0: Time is valid •1: Milliseconds. Below this value is not valid •2: Milliseconds × 10. Below this value is not valid •3: Milliseconds × 100. Below this value is not valid •4: Seconds. Below this value is not valid •5: Seconds × 10. Below this value is not valid •Element 4: NS. Possible value is 1 (RTU clock is not synchronized) •Element 5: OF. Possible value is 1 (an overflow occurred) NOTE: Use this Block Tag's OnRead event to receive a list of all ERMI events captured by this Driver |
|||||
Mode 2 |
333 (ERMA: Buffer Event) |
Block number |
Not used |
Read-only |
|
•Element 0: Sequence •Element 1: LLP. Possible value is 1 (Level Limit Passed) •Element 2: LLD (Level Limit Direction). Possible values are 0: Level limit passed in direction to normal zone or 1: Level limit passed in direction from normal zone •Element 3: Status. Possible values are: •0: Normal status •1: Low Alarm Zone •2: High Alarm Zone •3: Low Warning Zone •4: High Warning Zone •Element 4: Time quality. Possible values are: •0: Time is valid •1: Milliseconds. Below this value is not valid •2: Milliseconds × 10. Below this value is not valid •3: Milliseconds × 100. Below this value is not valid •4: Seconds. Below this value is not valid •5: Seconds × 10. Below this value is not valid •Element 5: NS. Possible value is 1 (RTU clock is not synchronized) •Element 6: OF. Possible value is 1 (an overflow occurred) NOTE: Use this Block Tag's OnRead event to receive a list of all ERMA events captured by this Driver |
|||||
Mode 2 |
334 (ERMD: Buffer Event) |
Block number |
Not used |
Read-only |
|
•Element 0: Sequence •Element 1: LLP. Possible value is 1 (Level Limit Passed) •Element 2: LLD (Level Limit Direction). Possible values are 0: Level limit passed in direction to normal zone or 1: Level limit passed in direction from normal zone •Element 3: Status. Possible values are: •0: Normal status •1: Low Alarm Zone •2: High Alarm Zone •3: Low Warning Zone •4: High Warning Zone •Element 4: Time quality. Possible values are: •0: Time is valid •1: Milliseconds. Below this value is not valid •2: Milliseconds × 10. Below this value is not valid •3: Milliseconds × 100. Below this value is not valid •4: Seconds. Below this value is not valid •5: Seconds × 10. Below this value is not valid •Element 5: NS. Possible value is 1 (RTU clock is not synchronized) •Element 6: OF. Possible value is 1 (an overflow occurred) NOTE: Use this Block Tag's OnRead event to receive a list of all ERMD events captured by this Driver |
|||||
Mode 2 |
341 (ERMIR: Buffer Event) |
Block number |
Bit number |
Read-only |
|
•Element 0: Sequence •Element 1: TYP. Possible values are 0: Single bit event or 1: Double bit event •Element 2: VAL. Possible values for single Indications are 1: ON or 2: OFF and for double Indications are 0: Intermediate position, 1: ON, 2: OFF, or 3: Intermediate position •Element 3: QUALITY. Possible values are: •0: Time is valid •1: Milliseconds. Below this value is not valid •2: Milliseconds × 10. Below this value is not valid •3: Milliseconds × 100. Below this value is not valid •4: Seconds. Below this value is not valid •5: Seconds × 10. Below this value is not valid •Element 4: NS. Possible value is 1 (RTU clock is not synchronized) •Element 5: OF. Possible value is 1 (an overflow in SER message queue occurred) •Element 6: Relative Time since start event in date and time format •Element 7: Number of corresponding start event, incremented with each new start event •Element 8: Cause of Transmission. Possible values are 1: Spontaneous event, 2: Test mode, or 3: Event caused by local operation NOTE: Use this Block Tag's OnRead event to receive a list of all ERMIR events captured by this Driver |
|||||
Mode 2 |
343 (ERMFD: Buffer Event) |
Block number |
Not used |
Read-only |
|
•Element 0: Sequence •Element 1: Value •Element 2: QUALITY. Possible values are: •0: Time is valid •1: Milliseconds. Below this value is not valid •2: Milliseconds × 10. Below this value is not valid •3: Milliseconds × 100. Below this value is not valid •4: Seconds. Below this value is not valid •5: Seconds × 10. Below this value is not valid •Element 3: NS. Possible value is 1 (RTU clock is not synchronized) •Element 4: OF. Possible value is 1 (an overflow in SER message queue occurred) •Element 5: Relative Time since start event in date and time format •Element 6: Number of corresponding start event, incremented with each new start event •Element 7: Cause of Transmission. Possible values are 1: Spontaneous event, 2: Test mode, or 3: Event caused by local operation NOTE: Use this Block Tag's OnRead event to receive a list of all ERMFD events captured by this Driver |
|||||
Mode 2 |
344 (ERMC: Buffer Event) |
Block number |
Bit number |
Read-only |
|
•Element 0: Sequence •Element 1: TYP. Possible values are 0: Single bit event or 1: Double bit event •Element 2: VAL. Possible values for single Indications are 1: ON or 2: OFF and for double Indications are 0: Intermediate position, 1: ON, 2: OFF, or 3: Intermediate position •Element 3: QUALITY. Possible values are: •0: Time is valid •1: Milliseconds. Below this value is not valid •2: Milliseconds × 10. Below this value is not valid •3: Milliseconds × 100. Below this value is not valid •4: Seconds. Below this value is not valid •5: Seconds × 10. Below this value is not valid •Element 4: NS. Possible value is 1 (RTU clock is not synchronized) •Element 5: OF. Possible value is 1 (an overflow occurred) •Element 6: Object number NOTE: Use this Block Tag's OnRead event to receive a list of all ERMC events captured by this Driver |
|||||
Mode 2 |
610 (FCOM 10: Generate MCM telegram. Please check the N2 parameter equal to 710) |
The number of bytes returned by MCM corresponds to the number of Elements declared for this Block Tag, counted from the initial address defined by the N2 parameter equal to 710. Not supported for RTUs 200 and 210 |
Not used |
Read-only |
|