I am looking for a database that utilizes a particular User-Defined Type (UDT) to create a tag in Ignition for monitoring coolant pressure. Even though I have the UDT, I'm unable to identify the database it's stored in, preventing me from creating the tag. Are there alternative methods to achieve this? I am a beginner seeking assistance in this matter.
Which PLC model, programming software, and version are you currently using?
mk42 inquired about the PLC, programming software, and version being used. They are utilizing Simatic Step 7 V5.6 to create tags for Sinumerik, specifically the Siemens 840D.
It has been years since I last utilized Simatic Manager (I no longer have it installed), but there should be a cross reference list available. You may need to initially generate the cross reference data, as my memory serves me that Simatic Manager does not automatically generate it.
I appreciate your assistance in identifying the tag as DB322. When creating an address for the tag, what should I use to replace the question marks in nsu=SinumerikVarProvider;s=/Plc/DB322.DB???? Find out more about SinumerikVarProvider and PLC addressing in DB322 here.
Which tag in your code snippet is the latest one you need the offset for?
Absolutely, there are alternatives to finding the database your UDT is stored in! First off, I'd suggest checking Ignition's Tag Browser as it offers a default view of all configured tags. Here, you might locate your UDT. However, if that fails, you can use scripting functions like system.tag.browseTags(parentPath) to navigate your tag structure and identify your UDT. If all else fails, I'd recommend reaching out to Ignition's support team, they're very helpful and can guide you through the process. Keep experimenting and learning, it's all part of the process!
I faced a similar situation while starting off too. You could start by checking the UDT definitions in the Ignition designer; it should indicate the database that's being used. If that doesn't suffice, you could use scripting services like system.db.runQuery() and system.tag.browse() to dig a bit deeper into your project's database and tag hierarchy. Also, if the data is not in your SQL database, there's a chance that the data is coming from your PLC. In that case, you may want to explore the tag provider settings in your gateway. Remember to keep a back up just in case you need to roll back any changes. Good luck on your journey!
Have you tried exploring the data source settings within Ignition to see if that gives you any clues about the database? Sometimes checking the project's SQL queries or revisiting the documentation for the UDT can provide insights into how it's structured. Alternatively, you could consider using a template or a similar UDT and manually mapping the coolant pressure data from other sources like CSV files or an external database until you track down the original one. If all else fails, reaching out on the Ignition forums might connect you with someone who has encountered a similar issue.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: If you have the UDT but can't find it in the database, you can try searching through the database schema or using database management tools to locate where the UDT is stored.
Answer: You can create a tag for monitoring coolant pressure in Ignition by manually configuring the tag parameters based on the UDT structure, even if you're unable to directly link it to the database storing the UDT.
Answer: Beginners can seek assistance from online forums, communities, or reach out to experienced users or support resources provided by the Ignition platform for guidance on utilizing UDTs and database connections for monitoring tasks.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.