#KEPSERVEREX V6 DOWNLOAD LICENSE#
Fixed an issue where a deadlock could occur during explicit reads.Resolved issue with the Rest Client Agent “Publish as Media Type” didn't match the option set in the Configuration.Fixed an issue where Boolean values reported to the server with underlying non-zero values except '-1' were reported as ‘false’ by agents.Fixed an issue where license status was incorrectly reported as “unlicensed” in the Agent properties.Updated Java third-party libraries to address security vulnerabilities.Fixed an issue where the ThingWorx Native Interface would silently drop updates.Fixed GET request filtering results by object type.Īdded the property “Static Tags” to channels and devices.This reports the total number of static tags defined for the object and everything under it.Fixed an issue where the configuration API could crash when under performance stress.Descriptions are no longer visible in the User Manager tab and can only be viewed by editing user or group properties.Fixed an issue that caused the Settings dialog to close if the language was changed.Fixed an issue introduced in 6.7 where importing users could cause the Server Configuration to crash.
#KEPSERVEREX V6 DOWNLOAD FULL#
One of the key advantages of KEPServerEX is the fact that its manufacturer, the company PTC, continuously improves it and provides full technical support for it. For download, please click the button at the end of this article.
Have you upgraded your KEPServerEX to the latest 6.9 version? Read on to learn about the main enhancements. Exchanging Data between Systems, Databases & SAP ERP.PROFIBUS Diagnostics, Repairs & Modernisation.Question (1): Can we use Labview 2013 to pass data to the KepServerEX V5 using OPC connectivity, but not have to add another module to Labview. Since we already have a working Labview application and product, option (b) is preferred.Ĭonsequently, our final aim is to have the ability to have OPC data which can be accessed by Kepware or any other OPC server/client for future installations. Option b) Using an existing Labview application and pass or access this data through the KepServerEX and an OPC client. Option a) Obtain data from instrument using KepServerEX and seperate data into required groups and tags, then pass or access this data through Labview. It appears there are a couple of Labview/Kepware connection architectures that could be used: The following is what I feel are my options:
I'm currently investigating the options to make this happen. We next need to have our instrument pass data from Labview to Kepwares (KepServerEX) using OPC. We have a Labview program application designed for our instrument and this works as intended on a singal PC. My question relates to Labview and Kepware. This is my 1st post requesting some guidance.