Support
Søg i ofte stillede spørgsmål
FA231756
Hvordan kan vi hjælpe dig i dag?

PlantStruxure PES [V3.1 + SP1]: Update Operation Software

Goals and Symptoms

How to keep Planstruxure PES Operation Software Updated.

Facts and Changes

PES still uses SCADA Expert Vijeo Citect SCADA as the associated supervision software to run the supervision projects which are generated by PES. In the PES, installation ISO file and the corresponding installation guide, it instructs the user how to install the supervision software.
However, except for the regular upgrade of PES software, user need to keep an eye on the upgrade of supervision software. The upgrade of supervision software mainly includes three parts:
- Vijeo Citect SCADA
- OFS
- SCADA OFSOPC driver.

Causes and Fixes

Introduction of the sites to check and download the latest update of Supervision Software.

1. Update the Vijeo Citect SCADA with the latest Service Pack:

PES V3.1 integrates VJC SCADA 7.30. The latest SCADA Service Pack could be referred to from the SCADA website,

or on the corporate website.

Currently the latest Service pack version for SCADA 7.30 is SP1.

2.Update the OFS with the Latest Service Pack

PES V3.1 integrates OFS V3.40. The latest OFS V3.40 Service Pack could be referred to from the OFS website.

Currently the latest Service pack version for OFS 3.40 is SP4

3. Update the OFSOPC Driver with the Latest One:

With the complete of SCADA installation, the OFSOPC driver would be installed into the PC by default.
However, SCADA software developing team would release the new OFSOPC driver regularly to fix all up-to-date found bugs and supply better compatibility to the latest software and operating system.
To have a better performance and working condition of OFS, it’s suggested to update OFSOPC driver timely.
The latest OFSOPC driver could be referred to from the SCADA Driver website.

Currently the latest SCADA OFSOPC driver version is 2.15.05.001.

Appendix: Configure OFS properly

After generating the supervision project in PES project explorer and build the executable, the SCADA projects, SCADA included projects and OFS configuration xml file are created. In PES V3.1, the user needs to save these SCADA projects and OFS configuration to local hard disc in real machine and open them on the supervision server to run.

kb1

kb2

The SCADA projects could be used directly if all the settings have been configured properly in PES.
However, the OFS configuration xml file, which is generated by PES automatically, is not properly managed and needs to be configured manually by the user.
Now let’s introduce how to configure the OFS server before running on operation server.

First let’s open the OFS Configuration Tool and open the OFS Archive file, which was exported from PES before.

kb3

In the above window, we could see three IO devices included in the xml file. “DevExample_1” and “DevExample_2” are two device configuration examples supplied by OFS. Here we do not need them and can delete them immediately. “Alias_IODevice_1” is the IO device to be used. Let’s refine its parameter.

Device name – It’s created by PES and it should be same as the IO device name inside the supervision generated by PES.
Device address – It’s automatically assigned by PES if the IP address is configured in the PES Topological Explorer and is mapped in PES Project Explorer.
PLC Embedded Data – As PES is using unlocated variable to manage the logic, “Using Data Dictionary” has already been checked. Here we suggest to tick “No Communication Break” as it will help to avoid the communication break following a modification of the PLC application.
Dynamic consistency – We suggest to tick “New Symbol Detection” as for Unity PLC alias this option allows to browse newly created variable in the application.


kb4

Then let’s scroll down to the see “Adjustment information” setting.

Max channels – This is the maximum number of TCP/IP connections that OFS will open with the controller. This parameter has a very important impact on performance.
Max Pending – This is the number of requests that are allowed to be sent in parallel to the controller.
Device timeout (ms) - This parameter has to be increased mainly when you use rate adapt parameter. In this case, it’s recommended to set this parameter from 2 to 5 times greater than “main” group period.
Frame timeout (ms) – This is the permissible delay between request and answer. In all cases the quality depends on the frame time out. If you want to read more items than possible the frame time out has to be longer than the group’s period.


For Modicon controller programmed with Unity there are 3 different devices that can be present and their configuration has to be done in relation with their communication capabilities: Quantum, Premium, M340. Regarding how to proper set above four parameters, it’s suggested to refer to two TVDAs, “How can I Assess SCADA software performance” and “How can I Assess PAC to SCADA Communication”.

kb5

For example, if the communication is done over a Quantum NOE module which limits bandwidth to 12 requests, the max channels is set to 12 to enable parallel sending mechanism and the max pending request is set to 12 in order to get the full NOE bandwidth.
Device timeout is set to 12000ms while frame time is set to 3000ms.

kb6

After we finish configuration in “Device - Device overview”, let’s click “OFS Server settings - Communication” folder and modify the communication parameters.

Communication overrun:

1. Items to bad Quality - Items have to be read in the group’s update rate (default setting); otherwise the quality of the items which have not been refreshed is set to bad.
2. Rate Adapt - Items have to be updated even if an overrun occurs. In this case the update rate is no guarantied and the client will be notified at the server-polling rate. The frame time-out of the affected devices must tune to allow the complete refresh of the items. The group’s update rate remains the same but you allow reading group’s item into the time out frame period. Over this time the quality will be switched to bad.


Advanced feature:

Quick item validation - In OPC Standard, there is a method that enables the client to ask to the server if an item is valid; this method is used at start up by OFSOPC Client. Without checking this option, OFS validate the item into the controller, so every validate need a request to check into the controller is the item exist and can be read. By checking this option, only the syntax string of the item is checked without sending any request to the controller so the startup time is much faster as no communication is done with the controller.
Quick Set Active State - This option should be checked when using OFSOPC Client to speed up page change and to refresh faster the values on the page. This enables to read data from the PLC straight away they have been added into the group without waiting for the notification period time.

kb7

After finishing all these configurations, let’s save it and then OFS server could be running with the parameters refined before.

Udgivet til: Schneider Electric Danmark
Se mere
Område:
EcoStruxure™ Process Expert
Se mere
Område:
EcoStruxure™ Process Expert

Brug for hjælp?

Brug for hjælp?

Produktvælger

Produktvælger

Find hurtigt og nemt de rette produkter og det rette tilbehør til dine anvendelser.

Få et tilbud

Få et tilbud

Start din salgsforespørgsel online, så vil du blive kontaktet af en ekspert.

Find forhandler

Find forhandler

Find den nærmeste Schneider Electric-distributør.

Hjælpecenter

Hjælpecenter

Find supportressourcer til alle dine behov på ét sted.

  • Produktdokumentation
  • Download af software
  • Produktvælger
  • Udskiftning og erstatning af produkter
  • Hjælp og kontaktcenter
  • Find forhandler
  • Projektrådgivning
  • Find vores kontorer
  • Schneider Electric Community
  • Karriere
  • Virksomhedsprofil
  • Rapportér en forseelse
  • Tilgængelighed
  • Presserum
  • Investorer
  • EcoStruxure
  • Jobsøgning
  • Blog
  • Privatlivspolitik
  • Cookiemeddelelse
  • Vilkår for anvendelse
  • Rediger dine cookieindstillinger