Kepware License Upgrade

[Jayme Bostic]

Thereshould be no problems with upgrading the .NET components. You will want to bank any licenses you may have deployed back to Kepware via the transfer process before completing the upgrade. Then reactivate the licenses after the upgrade is complete. There is always the chance that you can break the licenses when any of the machine components are changed.

I have recently been learned how to connect to kepware and pull in kepware tag data into Thingworx. I am wondering if I would be able to call a service based on a kepware tag reading value change without having to have a mashup open on a screen. Essentially, I would like to take advantage of how quickly Thingworx can trigger events without having to worry about hosting a mashup. Is there a piece of Thingworx functionality that I can look into for more detail about the possibilities of doing this?

So I'm tasked with resurrecting neglected OPC connections and I'm encountering a situation where i have to use a custom interface design XML file with KepServerEX 5.12.140.0 to specify tags from Sartorius AMBR systems.

I'm also encountering an issue where the OPC UA Configuration Manager that came with KepServerEX 5.12.140.0 seems to be creating a bad URI that can't be parsed by newer software because it puts whitespace in the URI string?

if there's a driver OOB for KepServerEX if i just get a different license type that will allow me to use drivers and not just a CID XML file. Or if I upgrade to KepServerEX 6 will I get driver support and not just manual CID XML capabilities

A lot to unpack here. Upgrading to the latest version of KEPServerEX (v6.15) will resolve your OPC UA issues you have mentioned. The "Unable to load plug-in DLL" Error is due to the installation of the Connection Sharing plugin with a driver that does not support it. The actual warning will not cause any issue with the server, but if you would like to remove that plug-in to remove the warning here are the steps:

Re-run the KEPServerEX setup that you used to install KEPServerEX. This will momentarily take your KEPServerEX instance offline, however it will not affect your license or project file. When you are able, select the Modify option. Once you reach the screen that lets you add or remove items, expand the Plug-ins selection and then click on the Connection sharing plug-in icon and select "Entire feature will be unavailable"

Click Next then modify then finish.

Now when you re-launch KEPServerEX you will no longer get the connection sharing plug-in warning.

What it means, one way or the other you are going to have to pay. It will be cheaper to go with Kepware rather than pay the Ignition upgrade price . Unless you can convince your customer to pay for the `upgrade.

Hopefully this can clear up some confusion. OPC is simply a communication protocol, like HTTP or RS232. It is the language Ignition speaks to communication drivers. Ignition also makes an OPC server that translates between the PLC and the OPC language.

Buy a newer version of Ignition. This will come with the newer Ignition OPC server that will communicate with the new firmware version Logix PLCs. If you have been paying a support contract that includes upgrade protection, this will be free. If not, you will have to purchase all your modules at the current price.

I installed ignition 64 bit v7.7.0 on 64-bit-linux machine

Installation is complete.But not able to launch project in gateway.

Attach is the image of file which opens on launching designer or project.

Java 1.8 which is pre-requisite for v7.7 is also installed.

What more settings are required? Please suggest.

Some external applications rely on the legacy drivers such as data logging database software interfaces. If the interface only supports the traditional TCP/IP ethernet communication for an S7 PLC for example, pressure should ideally be placed on the software vendor to update to a more secure medium. The work around here is to ensure the local network switch configuration only allows a specific device to interact with the PLC which minuses the risk through segregation.

Configuration changes can have highly negative impact if completed without sufficient thought. A concept survey report should always be completed to act as a forum for agreement when assessing the impact of change. The basics of defining what applications use data from each PLC is required and then what documents hold configuration detail for communication. The report should allow an approval of strategy which is then outlined in further detail in a validation plan. Design documentation updates and specific test installation and Qualification Protocols need to be created with multiple approvals. The core goal of a validation process in this upgrade is to focus on the important areas being considered so that the updates do not stop all systems from continuing to operate as expected.

The new server offers a split management configuration versus a run-time operation, enabling management at the user level and operation as a service, with the added bonus of Microsoft Terminal Services multi-user support.

Also featured is a new licensing and customer support model, designed to maximize end-user value and packaging flexibility, the company states. With the new release, KEPServerEX is now offered in the form of Vertical Suites. The new vertical suites are: IT and Infrastructure Suite, (SNMP, PING, System Monitor, Modbus and UCON drivers); Building Automation Suite (BACnet, Modbus, UCON drivers); Power Distribution Suite (DNP, Modbus, UCON drivers); Oil and Gas Suite (ROC, ROC Plus, Modbus and Modbus like RTU protocols, UCON drivers); and the Manufacturing Suite (a collection of more tan 100 protocols typically found in manufacturing environments). All protocols in an installation are supported by one instance of KEPServerEX, one OPC Interface and one Tag Namespace. Kepware also provides a new warranty, support and upgrade program; warranty now extends to 90 days. During the 90 days, customers are eligible for free technical support, access to the Kepware on-line knowledge base and product upgrades.

One way of "getting data out" could be to use Windows file sharing, which I think is what you're suggesting. Collecting information for a program like Proficy Historian on the other hand is a different matter.

If it doesn't, or if you're more concerned with supporting the maximum number of machines "out of the box", I'd recommend writing your own OPC client and machine data collection program using the THINC API version 1.9.1.0, and the Kepware OPC server you mentioned. You wouldn't need MT-Connect in that case, and it would give you lots of flexibility.

The Okuma MTConnect agent is available for free on the Okuma AppStore at -mtconnect-agent and there are many commercially available software packages that interface with the standard MTConnect agent (like 5ME and Memex)

Depending on the age of your machine (back to P100-II from 2004), you may or may not need an NC Software or THINC-API upgrade to use the MTConnect agent. These are also provided for free from Okuma but depending on your local distributor, there may be a charge to send a technician to perform the upgrade. At time of this writing (Nov, 2014) Okuma is still recommending the NC-Software and API upgrade be performed by an experienced technician.

The GCPL System Platform Upgrading Project consists of: The new System Platform 2017 will be installed on new SCADA Servers, which have different computer names from the existing production servers.Migrate SCADA HMI galaxy from the existing system to the new galaxy. Update the node addresses for platform instances.Integrate the new system with existing KepServerEX to get live data. Integrate the new system with ATMOS and Krohne LDS. GCPL to assembly new SCADA server rack.

Dow Chemical Operates over 4,000 miles of cross-country pipelines along the United States Gulf Coast. The pipeline systems stretch from Brownsville, Texas to New Orleans, Louisiana. The entire pipeline system is operated from the Control Center in Houston. The current SCADA System was developed over the past 10 years and requires to be upgraded to a single design and maintenance platform. TRC, under the guidance of Dows project management team will implement a completely new Pipeline Control and Management system, based on the Wonderware System Platform (ArchestrA), including upgrading all field interfaces. The project is slated for commissioning by the end of 2014.

Hi, we use FlexLM for license serving from a server but also via the HASP driver using USB keys. I've noticed on two occasions (and more coming I fear) that the upgrade from HASP 6.65 to HASP 7.103 is failing to install the Sentinel HL Key (it's literally not there). Yet, on other occasions (including my own test systems) it's perfectly fine.

However, if the customer upgrades (and we've had 2 possibly 3 now) they find that in Device Manager the Sentinel HL Key simply doesn't appear (even if I turn on visibility of hidden devices). This means that LMTools can see the HostID of the key (they are FLEX=9 versions with HW 3.25) but our software does not. But, like I said, only in specific instances not all the time.

3a8082e126