Optimizing Data Integration with Kepware v6 and FTSE v10: Troubleshooting Derived Tags in RSL Enterprise In our implementation of Kepware v6 and FTSE v10, we successfully utilize Kepware tags within RSL Enterprise for effective data visualization on display screens. However, we’ve encountered an unusual issue: attempts to create a derived tag from a Kepware tag or utilize an HMI tag linked to a Kepware tag result in failure. The error message indicates that the expression is incorrect, despite it being accurate. I've experimented with various data types, including Floats, Words, and Boolean values, but to no avail. After spending an hour on the phone with tech support yesterday without a resolution, I’m reaching out to see if anyone else has faced this issue and discovered a workaround. Any insights or solutions would be greatly appreciated!
Is the Kepware server successfully installed on your FTView PC? Have you confirmed that the Kepware server appears in the FTView directory with the appropriate OPC Server Name?
User 'rdrast' inquired: "Is the Kepware server set up on the FTView PC? Additionally, is the Kepware server correctly integrated within the FTView configuration tree, using the appropriate OPC Server Name?" To elaborate, my response is affirmative on both counts. I am successfully able to read all tags from Kepware, but unfortunately, FTView is unable to write these tags to either an HMI tag or a Derived tag.
Are the Kepware tags configured to be Read-Only?
While I'm exclusively referencing Kepware, it's important to note that FTSE is self-generating the content along with the CLX. This situation has left me puzzled for the last two days!
The FTSE system seems to be generating its own data, along with the CLX. However, this situation is confusing to me. It’s essential for the FTSE to read the tag directly from the Kepware server. If you haven't done so yet, consider reinitializing the Kepware server. Please provide an example of a specific IO tag as it is defined in your Tag Database for better clarity.
I totally understand your frustration; these integration issues can be a real headache! One thing to check is whether the Kepware tags you're trying to use as a basis for your derived tags have their read permissions configured correctly. Sometimes, it’s something as simple as access rights or a mismatch in data type expectations between the two systems. Also, I’ve found that experimenting with more explicit typecasting in your expressions can help clarify any confusion. If you've already checked those, it might be worth reaching out on forums dedicated to Kepware or RSL—a fresh set of eyes might offer a unique perspective!
I’ve run into similar issues when working with derived tags in RSL Enterprise, especially when it comes to type mismatches that can be tricky to spot. One thing you might want to check is the data type compatibility between the Kepware tags and what RSL Enterprise expects for derived tags. Also, ensure that the expressions you’re using don’t have any superfluous spaces or syntax errors—even tiny details can throw a wrench in the works. If you haven't already, try simplifying your derived tag expressions to see if that helps. Another tip is to look into any updates or patches for both Kepware and FTSE, as sometimes bugs are resolved in newer versions. Good luck, and I hope you find a solution soon!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.