Kepware

Warning OPC UA Client OPCUA_Hydraulic_Shop | Reconnecting server due to connection loss.

I am developing an application using OPC DA, but my client wants us to upgrade to OPC UA. The problem is that when the HMI reads the tag structure, it is different. With OPC DA my structure uses dots (.) to separate the path, and in OPC UA it uses backslashes (\) to separate the path. This has never happened to me before. Could you help me?

Hi,How would you use an Emergency ID in a disaster recovery scenario? For example, let's say you lose access to the server where Kepware was installed but have backups of the project available and have re-installed it on another server... seeking clarification on how you would handle the Emergency ID and Activation ID in this scenario.Also, is the Emergency ID available for re-use an unlimited number of times so long as it is reset and the original Activation ID is still active?

Hello, We have a PC which is running KEPServer EX6, but having issues connecting to the OPC server date.Errors I'm getting are as follows:Date Time Level Source Event11/12/2025 16:52:55 Error KEPServerEX\Runtime Attempt to add item 'Channel3.BottleMC3.Global.SCADA_CurrentHalfHour' failed.

Dear Members, I am new to KEPServerEX 6 and request expert guidance to configure Modbus RTU (RS-232) data in KEPServer, which I have been unable to achieve so far. Current Challenge At present, to bring RS-232 data into Modbus TCP/IP, I am using a protocol converter. However, this setup works only after running a Python script on the historian server that continuously sends ASCII commands (video attached) to read serial data and then pushes it back to the historian. Only then does the converter provide usable values for our Digital Data Visualization. Pain Points This approach is becoming unsustainable due to the following reasons: The Python script must run 24×7 Any script failure results in complete data loss Maintenance and troubleshooting are time-consuming The solution is not reliable for long-term plant operations What I Am Looking For I want to directly configure the RS-232 / Modbus RTU device in KEPServerEX and expose the data as Modbus TCP/IP (or directly to the hist

Hello,I am experiencing an issue when browsing/importing OPC UA server tags into Kepware. Several tags that are present on the OPC UA server do not appear in Kepware after the browse/import process.Details:The missing tags are not visible in the Kepware browse tree, so I cannot import/add them to my datalogger.I have verified the tags exist and are accessible from the OPC UA server side.I also confirmed using UAExpert that the missing tags are readable, and their data type is Float (so they do not appear to be unsupported types).Could you please advise what could cause Kepware to omit certain OPC UA nodes during browsing/import, and which Kepware settings or troubleshooting steps I should review to ensure all tags are discovered and available for import?Thank you. However, when running Tag Generation, it gives warning message of data type unknownWhen try to import, the tags are shown in imported itemsOPC-UA Server has tags under folder AHU/01 such as RA_RH, RA_T, SA_RH, etc.The fi

In the data logger feature, by default "Name" column is being considered as "Item ID" making difficult in database. How can i change this to "Log item Name" instead of default "Item ID"

Hi everyone,I’m sending MQTT data from Kepware IoT Gateway to ThingsBoard. Everything works fine when I publish around 250 tags in a single JSON payload. But when I increase it to 500 tags, the MQTT client in Kepware starts connecting and disconnecting repeatedly, and the message never publishes.I’m trying to figure out whether this limitation is coming from:Kepware IoT Gateway’s MQTT Client Agent, orThingsBoard’s MQTT broker / MQTT transport,or simply an MQTT payload size limit on either side.What I’m seeing:~250 tags → OK~500 tags → Kepware repeatedly connects/disconnectsNo clear error in Kepware UIThingsBoard logs show only connect/disconnectBehavior suggests a payload or packet size limitMy questions:Does ThingsBoard MQTT have a max payload or packet size limit?Does Kepware IoT Gateway restrict MQTT message size?Is this connect/disconnect loop typical when the payload is too large?Is splitting tags into smaller groups the recommended approach?Any insight from users who have handled

Is there any updates on when the License Transfer functionality will be fixed on my.kepware.com? We're currently unable to Transfer Licenses due to the error and all the Support Engineer can do is tell me to reach out to sales@kepware.com ?

I need to set up an external REST client to read AuditLog and EventLog over API hopefylly anonymouslyIs it possible?

Hello everyone, I’m trying to configure a tag of type LLong (Signed 64-bit Integer) in KEPServerEX 6.18 for a Modbus TCP/IP device, but I’m running into an addressing issue. My setup:Channel: Modbus TCP/IP EthernetDevice: Custom Modbus server running on Raspberry Pi (C#)The server exposes a 64-bit signed integer, stored correctly on the Modbus side.When I attempt to add a tag with data type LLong, KEPServerEX refuses any register address I enter. I’ve tried:4000740000730007300007But I always get the same error:“Data type 'LLong' is not valid for address '400007'.” It looks like KEPServerEX does not accept any Modbus register address for this data type, and I’m not sure whether the issue is related to:register type selection (3x/4x),addressing mode (1-based / 0-based),strict syntax rules,or a limitation of the Modbus TCP driver regarding 64-bit values. My questions.1) Has anyone successfully configured an LLong (64-bit) tag in a Modbus TCP/IP channel?2) What is the c

Hi,  Are advance tags only in read only mode or can we write to them from the OPC client ..? 

I am trying to add 2 separate SLC 5/05 plc's in our Kepware server using Allen Bradley Ethernet driver because both of the PLCs is networked. We have also used the DF1 driver with the ethernet encp. but that did not work either. Nothing sees the PLC. We then tried adding a test SCL 5/05 PLC in our training room with a small network for a controlled environment and it still will not see the PLC. Kepware EX6-6.16.203.0

The KepServerEx is configured as OPC DA Client to connect the OPC DA Server on another machine. It get callback failure and bad data. While using OPC Quick Client connected the OPC DA Server to get data directly. It get good data. Two servers are on the same domain but running with different Log On account.

We copied the virtual machine from old physical host to new one. The kepware licenses are broken. All the operation system is same as before. Why the license don't work? This issue can be fixed?Thanks.

Hello, We run Kewpare 6.16 on a VM Hyper-V for long time. The old system was Windows 2012 R2 and we use Kepware to feed our own Software using OPC DA communication. This system was running quite fine. After we migrate the VM to New Hardware our software is dying on resources on the system. After troubleshouting we found out that the request from our Software (Multi Clients) via Kepware to the Data Server are not responded in time. But looking at the Task manager of the system we could not find any issues. Processors, Memory, Disk and Network are showing no issues. the new hardware is comparable to the old hardware.When we disable the Kepware Service on the computer the system is running fine and is responding timely, but starting the communication with Kepware let the system dying of resources. It seem the requested are not answered timely. When starting only one or two clients the system is reacting correctly but with more clients started on the system the system getting slo

I have used Modbus Device Simulator (PyModbus) to run 200 Battery, 90 PCS and 10 FIP Modbus devices on localhost each with 1000+ registers.The simulator created devices sequentially from a port you specify, e.g. 300 devices starting on port 6001 will occupy the ports 6001-6300 with specified number of registers. Refer the attached test screenshots.All simulator devices are working correctly and can see values update with open ModScan client software, but all the values are zeroed in the OPC Quick client and in FT View Live Data Test Client even though the comms quality is Good. Refer the ModScan Output image.Unfortunately, I cannot set the ports for the channels independently. As soon as I change the port on one channel, same port gets assigned for all channels. I tried using FactoryTalk Live Data Test Client, with static registers (no random values) and I was able to read and write values from OPC and FT test client. The KepServer Enterprise 6.18 and the monitoring

I can't seem to consistently get the Read/Write Default User Account when I need it.  Any thoughts on what is grabbing it or how to find out what User has it?  Much less a way to boot them off and wrest control.

Thingworx: 9.3 KepWare 6.18Some Industrail Things can not connect to KepWare. The Industrial Gateway is set. All other Things are receiving data and everything is fine. Only 5 assets won't connect again. 

Hi ! Does anybody read tags from GE Quickpanel+ ?Which drivers we should use ? GE Ethernet ? What model ? PAC Systems ? We have downloaded runtime HMI project (Proficy Machine Edition 10) on GE Quickanel+ 755xxx. But we have no source project. We can read OPC tags from panel via Proficy View OPC server.  Used fromat is STATION IP\NameTagIs it possible to read tags via Kepserver OPC ?

Hello, I am a new user to Kepware, I setting up a flow of SQL data -> Kepware (querry to json) -> IoT gateway (REST server).Although the data in the OPC quick view look fine (attatch picture), the output from iot gateway contain un wanted character, how do I clean that ? { "readResults": [ { "id": "SQL2JSON.SQL2JSON.JsonData", "s": true, "r": "", "v": "[{\"id\": 1, \"pressure\": \"10\", \"temperature\": \"1\"}, {\"id\": 2, \"pressure\": \"190\", \"temperature\": \"1\"}, {\"id\": 3, \"pressure\": \"170\", \"temperature\": \"1\"}, {\"id\": 4, \"pressure\": \"0\", \"temperature\": \"0\"}, {\"id\": 5, \"pressure\": \"0\", \"temperature\": \"0\"}, {\"id\": 6, \"pressure\": \"118\", \"temperature\": \"70\"}, {\"id\": 7, \"pressure\": \"118\", \"temperature\": \"70\"}, {\"id\": 8, \"pressure\": \"118\", \"temperature\": \"70\"}, {\"id\": 9, \"pressure\": \"118\", \"temperature\": \"70\"}, {\"id\": 10, \"pressure\": \"118\", \"temperature\": \"70\"}, {\"id\": 11, \"pressure\":

I'm looking into utilizing the Universal Device Driver (UDD) for getting data from a REST API, however the API I need to communicate with is on a secure port requiring https.  I've found two articles that specifically say TLS is not currently supported by UDD:https://www.ptc.com/en/support/article/CS446447?source=searchhttps://www.ptc.com/en/support/article/CS442775?source=searchSince the UDD profile is user-defined, I'm still curious if there's a way to implement TLS into the connection via the Javascript profile.  Here are my questions I'm looking to get answered: Has anyone successfully implemented TLS/HTTPS calls via UDD?How does the back-end Script Engine make the calls to the remote host? Does the Script Engine use a particular library for the calls? Is TLS support on the UDD roadmap?

When using drivers with HMI applications like InTouch or Ignition, the tag in its database could have address modifiers or simply the tag type to let the Modbus driver know that you're looking for a floating point that is using more than one register. It appears that there's no way to accomplish the same thing when using KEPServerEX. Instead of a Modbus driver specifically written for Intouch or Ignition HMI applications.The only option is to manually create tags inside of KEPServerEX and then read those from the HMI? 

Getting below Error   IoT Gateway                 Failed to connect to server: '127.0.0.1:57212'. Please verify this connection information is correct and that the host can be reached.

I have attempted to connect to the Siemens TP900 OPCUA server with kepserverEx and am unable to do so, but I have no issues with the Unified Automation UaExpert application:    With keptserverEx, I follow these steps but am unable to succeed.   As it was not functioning in the certificates, I used the one I had imported Unified for OPCUASERVER, but nothing happened. I restarted the runtime and the server, but it still does not work.