RSView Supervisory Edition Installation Guide

More documents

Recommendations

Info

• • • • •RSVIEW SUPERVISORY EDITION USER’S GUIDEPlanning the layout of the networkIt is important to pay careful attention to the layout of the network, when designing adistributed application.The Windows ® domain or workgroupDistributed applications that contain more than 10 computers require a domain controller.Do not run FactoryTalk® Directory, or any other application software, on the same computer asa Windows domain controller.Applications that contain that 10 computers or fewer, can be run in a Windows workgroupenvironment. In that case, all computers participating in a single application must bemembers of the same Windows workgroup, and all must have administrative rights.The computers you’ll needYou can develop a distributed application on a single computer, and you can run it on asingle computer for testing purposes. However, depending on needs, a distributedapplication deployed for production typically involves the following computers:One computer running FactoryTalk Network Directory serverFactoryTalk Directory is software that works like a telephone directory or electronicaddress book, allowing the parts of an application to find each other on a computer, oracross a network.FactoryTalk Network Directory manages distributed applications, which can consist ofmultiple clients and servers distributed across a network. All of the computersparticipating in a distributed application must point at the same FactoryTalk NetworkDirectory. For details, see Chapter 4, Setting up FactoryTalk Directory.One or more redundant pairs of computers with RSView SE Server softwareinstalled on themThe RSView ® SE Server software is required to create and run HMI servers. The HMIserver stores HMI project components (for example, graphic displays), and serves thosecomponents to clients. The server also performs alarm detection, and historical datamanagement (logging), and might contain a database of tags.More than 2 HMI servers can be located on a single computer for development purposes only.When deploying an application, ensure that there are no more than 2 HMI servers per computer.If the servers are set up for redundancy, only 1 HMI server per computer is permitted.3-2
3 • PLANNING AN APPLICATION• • • • •One or more redundant pairs of computers running data serversData servers allow clients access to information in programmable controllers, devices, andother data servers that comply with the OPC-DA 2.0 specification.If an application requires more than 10,000 tags and you are not using RSLinx ® Enterprise forcommunications, install the OPC data server on its own, dedicated host computer for bestperformance.If you are using RSLinx Enterprise this is not necessary. RSLinx Enterprise is optimized toprovide best performance for large numbers of clients (more than 10) and a large number of tags(more than 10,000) even if it is located on the same computer as the HMI server.3 • PlaceholderFor details about data servers, see Chapter 7, Setting up communications.One or more development computers, running RSView StudioRSView Studio is configuration software for developing and testing machine- andsupervisory-level human-machine interface (HMI) applications.This manual provides information about developing supervisory-level applications. Forinformation about developing machine-level applications, see the RSView MachineEdition User’s Guide.One or more operator client computers, running RSView SE ClientRSView SE Client is software for viewing and interacting with supervisory-levelapplications developed using RSView Studio.For details about setting up RSView SE Clients, see page 27-13.One or more administration computers, running RSView AdministrationConsoleThe RSView Administration Console is software for administering RSView SupervisoryEdition applications after they have been deployed. The RSView Administration Consolecontains a sub-set of the RSView Studio editors so you can make minor changes to anapplication without installing RSView Studio.For more information, “Administering deployed applications” on page 27-16System requirements and installationFor details about system requirements and installing the RSView Enterprise software, seethe RSView Supervisory Edition Installation Guide.3-3
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: • • • • •RSVIEW SUPERVISO
Page 29 and 30: 1Getting startedThis chapter descri
Page 31 and 32: 1 • GETTING STARTED• • •
Page 37: 1 • GETTING STARTED• • •
Page 45 and 46: 2Exploring RSView StudioThis chapte
Page 47 and 48: 2 • EXPLORING RSVIEW STUDIO•
Page 61: 2 • EXPLORING RSVIEW STUDIO•
Page 75 and 76: 4Setting up FactoryTalk DirectoryTh
Page 77 and 78: 4 • SETTING UP FACTORYTALK DIRECT
Page 83 and 84: 5Working with distributed applicati
Page 85 and 86: 5 • WORKING WITH DISTRIBUTED APPL
Page 101: 5 • WORKING WITH DISTRIBUTED APPL
Page 111 and 112: 7Setting up communicationsThis chap
Page 113 and 114: 7 • SETTING UP COMMUNICATIONS•
Page 115 and 116:
7 • SETTING UP COMMUNICATIONS•
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
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 and 158:
11 • CREATING ALARMS• • •
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
12Logging system activityThis chapt
Page 197 and 198:
12 • LOGGING SYSTEM ACTIVITY•
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205:
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

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

Delete template?

Save as template?