Kepware

I am trying to connect the new omni 7000 flow computers to the Kepware omniflow driver, but these computers have a different and larger modbus map than the omni 6000 computers. Some of the registers are kept but there are others that when I try to enter them to the kepserver, I get an error message indicating that the number of registers cannot be added because it is out of range.How can I add the new registers from the omni 7000 to the omni flow driver?

Currently I am using the Torque Tool Ethernet driver, in KEPServerEX 6.The device I am testing for, is a PowerFocus 6000 that is communicating via Revision 2.0 of OpenProtocol. There are a number of things I need to test and simulate, and this means I need to also set ReadOnly values. This is so that I can bug test my code, and confirm it can retrieve correct values at the correct time. For example, when LTR_NEWDATA is set to 1 by the device, or when LTR_TORQUE_STATUS outputs a NG status value.  The problem is as follows:  LTR_TORQUE_STATUS is a ReadOnly tag. So I am under the impression that I cannot manually set the value for testing. This appears to be the same for other TORQUE tags like LTR_TORQUE_VALUE.I tried to set the data address to something like "901.00001" or "1202.00001", while keeping the tag name the same. My program only looks for tag names. So I was hoping that I could set a different address for testing. (I understand both 901 and 1202 are int

I'm setting up an Atlas Copco IXB controller using the KEPServerEX release 6.9.572.0 and I'm having an issue activating the two Boolean values for “PVT Comp” and “PVT_MON”. They are reporting false (0) causing Kepware to report null values for these readings (See Below). However, in the web GUI on the Atlas Copco controller tool, I received an accurate Prevailing Torque Compensate reading. In the Kepware manual, these Boolean values are tied to the “LTR_STRAT_OPT” item, which falls under the last tightening results command set. Specifically, bits 3 (PVT_MON) and 4 (PVT_COMP) need to be turned on. Here is a screenshot from the Kepware manual (page 15): We believe these bits in Kepware are connected to the mid-values (0060-0063) for the last tightening results from the tool. Below is a screenshot of these mid values from the OP manual (page 5): Is there a quick fix for turning on these bits that we might have missed?

Kepware OPC UA User Manager: What encyption is used when passwords for user accounts are saved? Addtionaly, is there a way to force the user to have to input the old password before entering new? Currenlty its is greyed out 

Hello community,I am reading via OPCUA a variable LLONG. on the OPC Client simulation the variable is visible. when I try to add this variable to the DATA LOGGER , and create a dedicate table for this type of data, there is no way to be able to write on SQL table and start the LOG. the alarm is  Date Time Level Source Event11/11/2024 4:59:19 PM Warning Data Logger Plug-in Failed to register log item 'LogItem1' for log group 'LOG_SCADA_LLONG'. apparently there is no other messages. I setup a LONG value, from a similar or identical OPC device and there was clear indication of the issue.     if anyone has an idea , appreciate. Thanks   

I have 3 PC's, have installed the product, but when I run the license utility it does not Launch on two of them

It appears empty and even when I tried manually adding the tags it gave me an error message. I tried stopping the runtime and restarting since it is the trial version to see if it would fix the issue but it did not. Any help would be greatly appreciated. I am trying to connect FACTORY IO to CODESYS. 

My system consists of two Control Logix L83 CPUs and one OPCDA server.I use advanced tags between these systems with both reads and writes to all of the devices.The issue I am encountering is this:When we first start up the system, the links do not synchronize between the systems.I have groups of boolean values in the PLC that have a value of 1 but in the OPCDA server, they remain 0.  If i manually change the state in the PLC from 1 to 0 and then back to 1, the OPCDA server will then show the change.I have tried opening the quick client and performing an async refresh of the cache and device but this does not seem to help. Is there a way to tell the whole system to sync up and ensure the linked tag destination matches the source?

Hi, has anyone had an issue with setting up KepserverEX to read the Modbus kWh address 45100 which is a 32bit float on a IEM3255 energy meter?  KepserverEX reads all the other registers such as Voltage & Current registers which are also 32bit float and returns the correct values.  It won't read the kWh value and just returns a Zero, I've tried toggling Modbus Byte Order, First Word Low, Zero-based addressing and all sorts of combinations. I've even set up a dedicated channel just to read kWh in case there are different settings for different registers but no good.I've tried other SCADA platforms such as Ignition and this reads it fine, so I know I've got the right address.Any help appreciated

Is there any way KepserverEx can pull tag from FT Historian?

Hello Everyone,  You know if Modbus Suite has compatibility with Windows server 2022? Regards

Hello everyone, I’m working with KepServerEX and need some help with a tag-based counter setup. I have a single tag, and I want to monitor its value every second. Specifically, whenever the tag’s value exceeds a certain threshold, I want to increase a counter that starts at 0 by +1.Here's a summary of what I'm trying to achieve:Monitor the tag value every second.If the tag value is above a certain threshold, increment a counter by 1.Counter should start at 0 and increase by 1 each time the condition is met.Could someone guide me on how to set this up? Any tips on scripting or configuration within KepServerEX would be greatly appreciated.Thanks in advance!

We have a OPC UA channel created to retrieve tags values from a Fette OPC UA Server. It was working fine until the certificated located in the OPC UA Configuration Manager in Trusted Servers for the Fette OPC UA Server expired. Even if I remove that certificate and create again the OPC UA channel it add again the certificate but with the same expired date.

Based on below document, it seems only Windows Server 2016 ?https://www.ptc.com/store/-/media/kepware-store/en/datasheets/opc-connectivity-datasheet.pdfHow about windows 2019 or 2022 ?  Supported Operating Systems• Windows Server 2016• Windows 10• Windows Server 2012 R2 and 2012• Windows 8• Windows Server 2008 R2• Windows 7 Ultimate, Enterprise, and Professional Thanks 

Looking for a better way to do  bulk import into KEPServerEX. I currently have an Excel  workbook with all the points in the system.I use VBA to create a JSON KEPServerEX application file. This works well for the initial setup and testing.The issue now is that when the customer makes a large number of changes or adds a new block of thousands points to an application we have to restart the KEPServerEX application when loading a new JSON application file. So all the existing points may miss some updates while KEPServerEX is restarting the app. If the CSV import is not very helpful as you would still need to manually create all the channels and devices, then do a manual import on maybe hundreds of devices.  I've not tried using the KEPServerEX API yet but looking at a demo it mostly seemed to give you the same functionality as the normal KEPServerEX client.

Hi everyone,I'm having trouble setting up Kepware OPC Server to read data from my PLCs. My Setup:- PLCs: Use Modbus RTU communication protocol as masters (initiate communication).- Kepware OPC Server: Used to acquire data from PLCs.- USR-TCP232-304 Module: Converts RS-485 communication from PLCs to Ethernet for Kepware to access. (Link to user manual: https://www.pusr.com/download/M0/USR-TCP232-304-User-Manual_V1.0.3.01.pdf)  The Problem:I can successfully receive data using a "Modbus slave" emulator software.However, Kepware OPC Server fails to receive data from the PLCs.My Kepware Configuration:Driver: Modbus RTU Server SerialPhysical Medium: Ethernet Encap.Port: 1123Device 1: ID 1 (matching PLC master write address)  What I Need Help With:Can someone advise on the correct Kepware driver for my setup?Are there any additional configuration steps required for Kepware or the USR module to establish communication?Any troubleshooting tips for Kepware's diagnostic tools to

I have multiple csv files each tied to a different advanced simulator channel. Within each of those channels I have one device tied to one csv file.Each of the csv files is different, meaning they have different number of columns and rows. Each file has approximately 32,000 rows.The record selection interval for all devices is 19200 ms. I noticed after a few days that the programs were on different lines of each csv file even though they have the same record selection interval. I was expecting that they would all be on the same row number because the record selection intervals were all the same. How can I counteract this and what is causing the problem?

Issue Description:Environment:Operating System: Windows Server 2022 Datacenter 64-bit (Build 20348)Instance Type: Amazon EC2 - t3.largeProcessor: Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz (2 CPUs)Memory: 8192MB RAM (8GB)Available Memory: 5999MBDirectX Version: DirectX 12BIOS: Default System BIOSDatabase: AWS RDS Aurora PostgreSQLInstance Type: Serverless v2Minimum Capacity: 0.5 ACUs (1 GiB)Maximum Capacity: 4 ACUs (8 GiB)Software: KEPServerEX v6.16 (6.16.217.0) - Data Logger Plug-inLog Group: 'TH_SF_BBO_1M'Logger Group Trigger: Static Every 1 minuteNumber of Items: 236 itemsIssue Details:The issue occurred after the OPC network connection was lost. When the connection was restored, the logger group attempted to resume recording to the existing table, but encountered the following error:{"timestamp":"2024-10-16T03:03:07.401","event":"Error","source":"Data Logger Plug-in","message":"Unable to open recordset on log group 'TH_SF_BBO_1M'. Reason: Out of memory while reading tuples.;mem

Hi Experts,I'm a beginner with Kepware and i've now encountered an issue i would really appreciate some help with solving: In my Siemens PLC i got an REAL variable that has the value "25.999".When i added the tag to Kepware (Float) and launched quick client the value is now shown as 1.10415E+09.How do i get Kepware to show the actual/same value as i can see in the PLC? Thanks in advance! 

In kepware there are energy meters tags showing tag quality good but values are shown as zero. All of changes in setting like reducing block size, recreated channel and devices, restarted kepware number of times we got bad address in block error. kepware error guide saying below reason,Possible Cause:The driver attempted to read a location in a PLC that does not exist, perhaps out of range. For example, in aPLC that only has holding registers 40001 to 41400, requesting address 41405 would generate this error.Once this error is generated, the driver does not request the specified block of data from the PLC again. Anyother addresses being requested from this same block are considered invalid.Kindly anyone post a solutions for the above problem.

Q-series Mitsubishi PLC connected to two Kepservers. One is KEPServerEX v6.14.263.0 and another one is Thingworx Kepware Server v6.14.263.0.I am receiving data from PLC in KEPServerEX v6.14.263.0 but not in Thingworx Kepware Server v6.14.263.0. all the channel and device configuration is same.Communication is having TCP connection and port number is 10000 in mitsubishi PLC and same at server side.earlier I was able to receive the data in both the servers.How can it be resolved?

We are getting "Request pending" from Kepware IoT Gateway REST Server.We have configured almost  - 10000+ tags for each site. We have CPU utilization remaining below 30%, indicating sufficient processing capacity for additional tasks. Network bandwidth is available, confirming that communication delays are not related to data congestion. We have only a single Kepware for all the sites. Does it going to impact our solutions?

In kepware there are energy meters tags showing tag quality good but values are shown as zero. All of changes in setting like reducing block size, recreated channel and devices, restarted kepware number of times we got bad address in block error. kepware error guide saying below reason,Possible Cause:The driver attempted to read a location in a PLC that does not exist, perhaps out of range. For example, in aPLC that only has holding registers 40001 to 41400, requesting address 41405 would generate this error.Once this error is generated, the driver does not request the specified block of data from the PLC again. Anyother addresses being requested from this same block are considered invalid.Kindly anyone post a solutions for the above problem.

Hi all, I am trying to import some OPC UA tags into Kepware via CSV. I have an address that looks like the below which is the address value in my CSV file: ns=3;s="DB31 Data Fixture"."CurrentMoldType" But when I import it the address ends up like this in Kepware:I can't seem to figure out why it is ending up with "" in Kepware when it isn't like that in my CSV

I am using KepwareEx6.15 with Mitsubishi iQ-R32 PLC + RJ71EN71 module.Kepware Channel and Device configuration point out to the RJ71EN71 module (SLMP TCP/IP port)I have created SLMP TCP/IP 40 ports for connecting the same PLC+RJ71EN71 module with KepwareEx6.15 multiple channel and devices for limit the tags in each devices for quick poll. I have active client connections with KepwareEx is 120 and Active tags more than 3000 with scan rate 100ms. I am facing the challenge to write back 200tags values from kepwareEx to PLC it took more than 40 secs.  the below information were my testing observations. Scenario 1: When i restart the Kepware and disconnect the active client connections and maintain one channel & device with 200 tags the write back time is 6secs. Scenario 2: When i restart the Kepware and loaded the active clients connections and maintain the one channel and device with 4000 tags and write back time of 200 tags is 60secs Scenario 3: Whe