Scribd
Upload
97 views4 pages

KEPServer Enterprise v5.x Does Not Use Default - Pfe File Like v4.5 and Earlier

Uploaded by

Sharad Adelkar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
97 views4 pages

KEPServer Enterprise v5.x Does Not Use Default - Pfe File Like v4.5 and Earlier

Uploaded by

Sharad Adelkar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

ID: QA18888 | Access Levels: TechConnect

KEPServer Enterprise v5.x does not use default.pfe file like


v4.5 and earlier

Document ID QA18888

Published Date 02/14/2020

Summary
KEPServer Enterprise v5.x does not use default.pfe file like v4.5 and earlier

Question
Why does KEPServer Enterprise v5.x not use the default.pfe file like v4.5 and earlier?

Answer
In KEPServer Enterprise v5.x, when a project is opened in the Configuration Tool AND
when the user selects Yes to upload the project into the Runtime, the default.pfe file is
overwritten with the data from the file that was opened in the Configuration Tool. The
Runtime process ALWAYS loads its configuration from default.pfe the Configuration
Tool simply changes (edits/overwrites) default.pfe when changes are made in the
Configuration Tool or project files are opened and uploaded.

You will see a file path in the Configuration Tool’s menu bar when you have not closed the
Configuration Tool after opening a file and uploading it into the Runtime. The
Configuration Tool still has a record of where the configuration data came from. If you
closed the Configuration Tool and opened it again, making sure it’s connected to the
Runtime, you’ll see your same configuration data in the Configuration Tool as you did after
opening the file, but the top of the menu bar will show Runtime. This is because the
Configuration Tool sourced the configuration data from the Runtime itself, meaning
default.pfe, not an external file.

Think of KEPServer Enterprise in this manner:

1. The Configuration Tool is PLC programming software


2. The Runtime process as the PLC
3. The file default.pfe is the PLC’s memory

You can connect and disconnect the Configuration Tool from the Runtime, you can make
changes to the Runtime’s configuration data in real-time, and you can choose to
completely overwrite the existing configuration data by uploading a new configuration
from a separate PFE file.
Here is a link for videos demonstrations of KEPServer v5:
http://www.kepware.com/Support_Center/support_demonstration.asp

We recommend reviewing the KEPServerEX v5 Feature Tour because it notes the


differences between KEPServer v4 and v5.

Recently Viewed

Kepware KEPServer Enterprise


FactoryTalk View SE and Sending ASCII commands to an
Drivers for the PanelView Plus
Kepware Guides Ethernet printer
family of terminals

DISCLAIMER
This knowledge base web site is intended to provide general technical information on a particular subject or subjects and is not an exhaustive
treatment of such subjects. Accordingly, the information in this web site is not intended to constitute application, design, software or other
professional engineering advice or services. Before making any decision or taking any action, which might affect your equipment, you should consult
a qualified professional advisor.

ROCKWELL AUTOMATION DOES NOT WARRANT THE COMPLETENESS, TIMELINESS OR ACCURACY OF ANY OF THE DATA CONTAINED
IN THIS WEB SITE AND MAY MAKE CHANGES THERETO AT ANY TIME IN ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL
INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS "AS IS." IN NO EVENT SHALL ROCKWELL BE LIABLE FOR ANY DAMAGES
OF ANY KIND INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT OR DAMAGE, EVEN IF ROCKWELL
AUTOMATION HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

ROCKWELL AUTOMATION DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED IN RESPECT OF THE INFORMATION
(INCLUDING SOFTWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE,
MERCHANTABILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not countenance the exclusion of implied warranties; thus, this
disclaimer may not apply to you.

You might also like