RSView Supervisory Edition Installation Guide

More documents

Recommendations

Info

• • • • •RSVIEW SUPERVISORY EDITION USER’S GUIDEThresholdvaluesThresholdsAlarmseveritylevels5,0006*1Increasing4,0005*43,000482,00038Safe zoneDecreasing1,00026114TimeThresholds must be set upin ascending order* These alarms are triggered only if Generate alarms whenapproaching normal operating range is selected in the AlarmSetup dialog box.If the motor speedIt triggers an alarm of this severityexceeds 3,000 rpm 8exceeds 4,000 rpm 4exceeds 5,000 rpm 1falls below 5,000 rpm* 4falls below 4,000 rpm* 8falls below 2,000 rpm 8falls below 1,000 rpm 6falls below 1 rpm 4In the illustration, an X shows when the tag goes into alarm and an O shows when the taggoes out of alarm.Alarms occur when the motor speed falls below 5,000 rpm and 4,000 rpm, and when itrises above 1 rpm and 1,000 rpm. These alarms would not occur if Generate alarms whenapproaching normal operating range was cleared in the Alarm Setup dialog box11-4
11 • CREATING ALARMS• • • • •Variable thresholdsThreshold values can be constant or variable. The previous example uses constantthresholds. To define a variable threshold, specify a tag name in the Threshold box whensetting up the thresholds for an analog alarm tag. As the value of the specified tagchanges, the threshold changes.Variable thresholds require more system resources than constant thresholds because of thecontinuous scanning of threshold values, and the processing necessary to detect alarmfaults.11 • PlaceholderAlarm faultsA variable threshold must not become higher than the threshold above it or lower than thethreshold below it. If this happens, an alarm fault is generated for the monitored tag. Tocorrect an alarm fault, change the variable threshold so it does not overlap either of itsneighbors. This can be complex when the neighboring thresholds are also variable,because these boundaries are determined dynamically at run time.When an alarm fault is generated, the following actions occur:• The tag’s alarm status stays as it was before the fault was generated.• An alarm fault is reported to all alarm reporting devices you have set up, such as thealarm log file and the printer.• The alarm fault status bit for the tag is set in the value table. This notifies otherapplications that an alarm fault has been generated.• The Alarm Type column in the alarm summary states that the tag is in ‘Alarm Fault’.When the faulty thresholds return to their normal operating range, the alarm faultcondition is cleared, the out-of-alarm-fault status is generated and logged, and alarms forthe tag resume normal operation.DeadbandWith some measured values, such as line pressure, tag values can fluctuate rapidly aboveand below a critical threshold. Where such conditions exist, you can create a deadband asa buffer to prevent the fluctuations from triggering unnecessary alarms.If the threshold is increasing—monitoring rising values—the deadband range lies belowthe threshold. If the threshold is decreasing—monitoring falling values—the deadbandlies above it.11-5
Page 1 and 2:
User’s GuideVolume 1Publication V
Page 3 and 4:
ContentsPrefaceAbout the documentat
Page 5:
CONTENTS• • • • •Plan how
Page 8 and 9:
• • • • •RSVIEW SUPERVISO
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 29 and 30:
1Getting startedThis chapter descri
Page 31 and 32:
1 • GETTING STARTED• • •
Page 33 and 34:
Page 35 and 36:
Page 37:
Page 40 and 41:
Page 42 and 43:
Page 45 and 46:
2Exploring RSView StudioThis chapte
Page 47 and 48:
2 • EXPLORING RSVIEW STUDIO•
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 75 and 76:
4Setting up FactoryTalk DirectoryTh
Page 77 and 78:
4 • SETTING UP FACTORYTALK DIRECT
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
5Working with distributed applicati
Page 85 and 86:
5 • WORKING WITH DISTRIBUTED APPL
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109: • • • • •RSVIEW SUPERVISO
Page 111 and 112: 7Setting up communicationsThis chap
Page 113 and 114: 7 • SETTING UP COMMUNICATIONS•
Page 123: 7 • SETTING UP COMMUNICATIONS•
Page 149 and 150: 10Creating derived tagsThis chapter
Page 151 and 152: 10 • CREATING DERIVED TAGS• •
Page 153 and 154: 10 • CREATING DERIVED TAGS• •
Page 155 and 156: 11Creating alarmsThis chapter descr
Page 157: 11 • CREATING ALARMS• • •
Page 161 and 162: 11 • CREATING ALARMS• • •
Page 195 and 196: 12Logging system activityThis chapt
Page 197 and 198: 12 • LOGGING SYSTEM ACTIVITY•
Page 205: 12 • LOGGING SYSTEM ACTIVITY•
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 223 and 224:
14Using eventsThis chapter describe
Page 225 and 226:
14 • USING EVENTS• • • •
Page 227:
14 • USING EVENTS• • • •
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 263 and 264:
INDEX• • • • •IndexSymbol
Page 265 and 266:
INDEX• • • • •Object Smar
Page 267 and 268:
INDEX• • • • •redundancyS
Page 269 and 270:
INDEX• • • • •Embedded va
Page 271 and 272:
INDEX• • • • •caching •
Page 273 and 274:
INDEX• • • • •stopping au
Page 275 and 276:
INDEX• • • • •MMacros •
Page 277 and 278:
INDEX• • • • •QQuestion m
Page 279 and 280:
INDEX• • • • •to RSView c
Page 281 and 282:
INDEX• • • • •Tags • 8-
Page 283:
INDEX• • • • •Procedures
show all

RSView Supervisory Edition Installation Guide

Create successful ePaper yourself

Delete template?

Save as template?