IoT & Connectivity

I am currently testing Kepware Server 7 to connect to an OPC Server via OPC DA.The OPC Server, in production, is currently has working OPC DA Client. I have configured the DCOM configuration for the Kepware Server.Set the Launch and Access Permission default and limits with the user that is also in the OPC Server as well as Access Permission. I can browse the tags but when OPC Quick Client (OQC) is connected to the Kepware, data is Bad and not updating. Here are what I observe during the testing:Data is updating:            Kepware Runtime “Use DCOM configuration” = disabled Data is not updating:      Kepware Runtime “Use DCOM configuration” = enabled Data is updating:            “My Computer” authentication level = None and “Use DCOM remote security” is enabled (connected directly to OPC Server) Data is not updating:      “My Computer” authentication level = Default/Connect and “Use DCOM remote security” is enabled. (connected directly to OPC Server)However, I tried to set the authent

hi all,I’m trying to setup a Modbus TCP/IP connection on a thingworx Kepware server 6.18, to an energy meter from Circutor (CVM-E3-MINI-ITF-WiEth, manual can be found here M170F01-03.pdf). I’ve setup connections to other energy meters before using Modbus TCP/IP without issues, but with this device I keep getting unrealistic values.I’ve literally tried using all different combinations on Data access & encoding, but the output I’m seeing seems either extremely high or extremely low, sometimes more or less stable but often also varying a lot which can normal if the byte order was swapped.The manual doesn’t really tell much on the Modbus-TCP setup, like what device-id I need to be using. So far I’ve tested mostly with device-ID 1 which seems most logical in that case, but I’ve used other device-id’s like 2 or 7.I’m hoping anyone has some experience with these types of devices or recognizes this type of behaviour and has some ideas on how to solve it.Many thanks in advance.H.

Hi everyone,I am trying to configure an MQTT Thing in ThingWorx 10.0.1-b202 using MQTT Extension 4.0.0.I followed the steps documented in the ThingWorx Help Center:https://support.ptc.com/help/thingworx/platform/r9/en/index.html#page/ThingWorx/Help/Extensibility/MQTT.htmlEnvironment ThingWorx Version: 10.0.1-b202 MQTT Extension: 4.0.0 MQTT Broker: demo.thingsboard.io Steps Performed Installed the MQTT Extension. Created a Thing using the MQTT Thing template as described in the documentation. Configured the MQTT broker as demo.thingsboard.io. Created a property on the Thing and configured the corresponding mapping in the Mapping infotable under the Configuration section. Issues The MQTT Thing never connects to the broker. When I try to update the property value under the Properties tab, I receive the following error: "Error occurred: Unexpected error occurred on server." The Application Log shows the following messages: Unable to close client in MQTT Thing ITH.MQTT.Tes

I’ve had this same issue with the “Notifications” entities as well. As stated in this topic (https://community.ptc.com/thingworx-developers-185/email-notification-doesn-t-work-90553). Using the “SendMessage” service on my MailThing will work, but if I set up a Notification to trigger from an event, no email is sent.  I set up a subscription to log a message on the same event and it DOES log the message.  Our ThingWorx platform is configured as a HA cluster, currently running version 10.1.1, but this issue has been across multiple versions.Performing a rolling restart of my individual server nodes seems to resolve the problem and the Notifications ARE triggered for a while, but eventually they stop working again.  I’m curious to know if more people have experienced this issue.UPDATE: Performing the rolling restart (cycling nodes while platform remains up) is NOT working in today’s instance of this problem.  I believe it worked in the past but seemingly not today.  Maybe the problem has

We are facing an issue in our ThingWorx 9.3 Production environment where Timer Things and Schedulers are not executing, while the same configuration works correctly in other environments.EnvironmentThingWorx Version: 9.3 License: Valid until 2027 Issue specific to production environmentValidation PerformedVerified Timer Thing is enabled. Verified runAsUser is set to Administrator. Verified subscriptions are enabled. Compared Timer Thing XML/configuration between working (test) and non-working (production) environments; no significant differences found. Created a new test Timer Thing with a simple logging subscription; it did not trigger. Created a test Scheduler; it also did not execute. Restarted the ThingWorx server. Verified license status through Licensing Subsystem.

The ThingWorx mashup-vendor-shared.js file is using the jQuery scrollintoview plugin v1.8 (2011), which is vulnerable. We would like to upgrade this to the latest version, but since it is bundled within ThingWorx, please advise on the recommended approach for upgrading or replacing this plugin.Current environment:jQuery: 3.7.2 jQuery UI: 1.14 jQuery Migrate: 3.5.2

I am using ThingWorx Platform Release 9.2 and DatecodeSP12 C3P0PooledConnectionPoolManager[identityToken->2y7va1bjf5tzhngvxv49|58599b34]-HelperThread-#2] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@f2f0838 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. Here are the errors that I faced C3P0PooledConnectionPoolManager[identityToken->2y7va1bjf5tzhngvxv49|58599b34]-HelperThread-#2] Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@f2f0838 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.

Hi all, On version 10.0.0 and this is an issue I am just noticing as of recent (maybe just after updating our dev to 10.0.0). There is this dependency with an entity called 'open-tabs' but I don't see it used anywhere in the mashup and don't even know what the entity is (based on name seems like a default thingworx entity). Any ideas on what this is or how to resolve this dependency? 

Hi ThingWorx Community,I'm working on a ThingWorx Mashup and need to uniquely identify the client machine that is accessing the mashup. The goal is to know which specific PC/workstation is running the mashup at any given time.I've explored a few approaches but hit limitations due to the browser sandbox and the separation between client-side (mashup) and server-side (JavaScript services). I'm hoping someone has solved this or can suggest a better approach.What I've TriedClient IP Address (CurrentSessionInfo.GetCurrentUserSessionInfo()) — This works, but the IP address can change due to DHCP, VPN, or NAT/proxy, so it's not a reliable unique identifier. URLSearchParams / window.location in a server-side service — This doesn't work because ThingWorx JavaScript services run on the Rhino engine (server-side), which has no access to browser APIs.What I'd Like to Do (Any of These Would Work) Read an environment variable from the client machine (e.g., %COMPUTERNAME% on Windows) directly from th

Hi,I’m using ThingWorx 9.3.0-b20 with Analytics Manager, and I’m facing an issue where analytics jobs stay in “Waiting” state for a long time.This does not happen all the time, but occurs around 3–5 times per day.The jobs only start running after I manually trigger another job (e.g., test an analysis model or create a new job). Once I do that, the waiting jobs immediately execute.Expected: Jobs should start automatically without manual trigger.Actual: Jobs get stuck until another job “wakes them up”.Questions:Is this a known issue in 9.3? Any configuration related to scheduler/queue causing this? Any workaround or fix?Thanks in advance.

Hi Experts,I'm looking for guidance from Kepware, ThingWorx, and security experts regarding certificate handling between ThingWorx and Kepware, particularly around REST-based integrations and Java truststore behavior.BackgroundUsing Kepware IoT gateway I am downloading MES data.During troubleshooting of a Work Order (WO) download issue between ThingWorx and Kepware, observed that:In one environment, WO downloads failed and the issue appeared to be related to an expired Kepware REST server certificate. After addressing the certificate issue, WO downloads resumed successfully. However, in other environments, the Kepware REST server certificates were also expired, yet ThingWorx-to-Kepware communication and WO downloads continued to function normally.Initial investigation suggested that the difference may be related to the Java truststore (cacerts) contents on the ThingWorx servers. In some environments, the Kepware certificate appears to be trusted/imported into the JVM truststore, while

How to use the OPC UA → ThingWorx bridge (Python)Getting OPC UA data into ThingWorx usually means Kepware plus a Connection Server, and complex/structured tags are often the hardest part. This post shows a config-driven Python bridge that connects to any OPC UA server, including complex structures (structs, arrays, method arguments), maps the tags to ThingWorx Things and properties, and pushes live values through the thingworx-python wrapper. It even generates the matching ThingWorx entities for you, so you write no code — just YAML.What it doesThe bridge is a Python package (opcua_bridge) with a four-step workflow and a runtime pipeline:OPC UA server → reader (asyncua) → map/coerce → ThingWorx propertieswalks the OPC UA address space and writes a mapping skeleton for you; generates importable ThingWorx XML (Project, DataShapes, Things, Network); at runtime, decodes OPC UA values on an asyncio thread, coerces them, and pushes them up through the wrapper; turns complex OPC UA types (str

Running a machine-learning model right at the edge — next to the machine, without a round-trip to the cloud — is a common ask. This post shows a ready-made Python solution that reads live data from an OPC UA server, scores a PMML model locally, and pushes the predictions into ThingWorx as Thing properties. It builds on the thingworx-python wrapper, so the ThingWorx side is only a few lines of code and everything is driven by one config.json.What it doesThe service edge_inference.py wires up a small pipeline:OPC UA (asyncua) → assemble a feature row → PMML model → ThingWorx propertiessubscribes to / polls OPC UA nodes (e.g. temperature, pressure, humidity); optionally reads extra inputs from ThingWorx properties (setpoints, limits); runs the model when the trigger condition is met; writes each prediction back to a ThingWorx property.Where to get itThe Edge ML solution is on GitHub:https://github.com/thingworx-field-work/Python-Edge-Machine-LearningIt builds on the ThingWorx Python SDK w

Most ThingWorx edge agents are written in C, Java, or .NET. But a lot of edge logic today — data science, protocol bridges, quick prototypes — lives in Python. This post shows how to connect a Python program to ThingWorx using a thin Python wrapper around the ThingWorx C SDK, so you get the performance and protocol support of the native twCSdk library with a Pythonic API on top.What the wrapper isThe wrapper (thingworx-python) is a pure-Python package that talks to the native ThingWorx C SDK through Python's standard-library ctypes. It ships two layers:a high-level API — ThingWorxClient, Thing, DataShape, InfoTable, BaseType, plus decorators for properties/services/events; and a low-level 1:1 binding to the C SDK (twApi_*, twPrimitive_*, twInfoTable_*, …) for anything the high-level API doesn't expose.It has zero pip dependencies — only ctypes. The native library itself is not shipped; you provide the twCSdk build for your platform.Where to get itThe full project — wrapper, examples, a

I currently have a KEPServerEX 6.7.1054.0 instance running on a production server. The original application owner is no longer with the company, and unfortunately, the installer for this exact version is not available in our internal software repository.I do not see a way to obtain this exact legacy installer from PTC, so I am evaluating whether it is safe to proceed using a newer KEPServerEX installer within the 6.x major version.Before moving forward, I would like to confirm a few things to minimize risk in a production environment: License Compatibility Is licensing for KEPServerEX 6.7 generally forward-compatible within newer 6.x releases (e.g., 6.14 or later)? Specifically, will existing licenses (including licensed modules) remain valid after an in-place upgrade? Upgrade Risk / Downtime Considerations Has anyone performed an in-place upgrade from 6.7 to a newer 6.x version in production? Were there any licensing reactivation issues or unexpected service interruptions? Module

Hi,I am using Kepware Server v7.0.236 with FTView v16 on Windows Server 2025 in a Domain setup.  The Kepware Server is installed on the same server as the FTView application.  I have a FTView Client PC (Windows 11 24H2) which runs the FTView client.  The problem is when I run the FTView client on the W11 PC any tags on a graphic which directly address the Kepware server don’t read. I’ve gone through every step of the Kepware “Configuration Guide Remote OPC DA (DCOM)” and had a 2 hour Teams session with Kepware UK Tech support (MAC Solutions) while I’ve had remote desktop connection to the server. We went through the settings on both the Server and Client step by step and confirmed the recommended settings were in place and even uninstalled/reinstalled Kepware but nothing has worked.Anyone had similar issues and found solutions ?

I am using ThingWorx Platform Release 9.1 and DatecodeSP1 Users or Developers are not able to see the mashup Runtime, even though they are in the "Administrators" group. Sometimes, after restarting the laptop or incognito Runtime shows up, but most of the time, the dashboards won't come up. We tried in different ways:1. Different Browsers2. Restarted Laptops3. Incognito Windows4. Restarted the Thingworx with clearing cache When the Runtime Dashboard is opened, we get HTTP Status 403 – Forbidden Here are the errors that I faced HTTP Status 403 – Forbidden

Hi,We are getting frequent warning events in the Allen-Bradley ControlLogix Ethernet Driver even though there are no changes at the PLC end. Communication is mostly stable but warnings keep appearing.Has anyone faced this? Any insights on possible causes or troubleshooting steps would be helpful.Thanks!

Not able to read correct/exact data of siemens S7-300 PLC tags, datatype is TIME OF DAY/datetime/time.Thingworx Kepware Server v6.16.217.0

I have upgraded our Kepware system and I need to remove LinkMaster and the OPC server that is with it.  Since everything seems to break Kepware licenses, are there precautions that need to be taken in uninstalling LinkMaster or can you just use the Windows Uninstaller?

Hi,I have installed the IQNOX Thingworx Map widget from the website and I have Imported it to the Thingworx: But the Map is not showing up in the Widgtes:  There is no widgets of google showing up:   Thanks.

We have successfully migrated the existing PostgreSQL 15.3 database to a new PostgreSQL 15.3 server and established connectivity with the newly installed ThingWorx 9.4.0 environment on the new servers.As the next step, we need to upgrade ThingWorx from version 9.4.0 to 10.0.Could you please advise on the recommended approach and best practices for performing this upgrade?For your information, ThingWorx and PostgreSQL are hosted on separate servers.

Hello, Has any configured KEPServerEX to be able to run timers between a start and end trigger tags? I want to be able to setup Operation Cycle Time Logging from plcs tags and be able to calculate the time that it takes for the operation. Example: Timer between hit of a start button and final test saying that the test passed without having to create a timer in the plc itself to monitor this operation Thank you

As per the original post.   Hi,   I have the similar problem as NM_12850686. Could you please share the port issue solution?   Here is my setup: Cleco Controller mPro200 - Open Protocol - Port 9002 - Activated Cleco Controller mPro200 - TorqueNet- Port 12345 - Activated Cleco Controller mPro200 id : 192.168.50.20 KepServerEx - Channel:TorqueToolEthernet - Device:Cleco (Open Protocol - 192.168.50.20 - Port: 9002)   Both the controller and the port can be ping successfully from the PC.   However, none of the tags receives information from Cleco. Could you please look into this?   Thank you,LP

Hi, I have a customer that is using Kepware Server for OPC DA / OPC UA / OPC DA communication between two systems. At the moment we are having issues with certain slow updating tags (booleans and integers) that freezes and are not updated between the two systems. Continuous updating values are no issue... The issue seem to be that the tags gets timed out and are not correctly mirrored between the systems. If we create local subscriptions on the KepServer node on the actual tags the error seem to disappear. Is there a way to configure kepware to establish the subscription to the source tags regardless of the client status? We cant find any correlating error messages in kepware.