You also can manually write to the audit log to track events. The Audit Log will automatically log write operations such as tag writes and SQL updates, inserts, or deletes.īecause this tool logs includes timestamps, users, and events, it’s helpful in identifying how a tag got deleted or why it’s not functioning in the way you expect. You will also need to check “enable auditing” in the Project Properties and select your profile for the audit log to record. The Audit Log needs to be set up on the Gateway web page by navigating to Configure > Security > Auditing. If errors are coming from unexpected issues such as missing tags or incorrect data, another handy tool is the Audit Log. Examples of client-scoped scripts are Client Startup scripts and user events such as a button press. Only client-scoped scripts will be visible from either the Output Console or the client Diagnostic Console. If the Help menu item is not visible, the Control+Shift+F7 hotkey combination will open it up. When debugging from a client, the Diagnostics tool in the client will display the print statements in the Console tab. If you use the print function in the Ignition Designer, print statements can be viewed with the Output Console. The print function in Python scripts is the most common method for finding and logging bugs. Client-scoped events will not be sent to the logger, these instead will be sent to the diagnostic tool in the client. This includes scripts like a Gateway Timer script or a script on a Tag Change event. However, only Gateway-scope scripts and events will be sent here. You can send your own custom messages here with their own priority level from trace all the way to fatal. If you navigate to the Ignition Logger by going to Status > Diagnostics > Logs, you will see all the logged messages that are coming from Ignition modules. If Java isn’t causing the problem, here are some ways to help you troubleshoot your issue. To clear out the Java cache, go to Java Control Panel, select Settings under Temporary Internet Files followed by the Delete Files button. Once enabled, the Java console will launch with every client and designer instance opened and will display Java-related messages.Īnother thing to try within the Java settings is clearing the cache, especially if problems have started that haven’t happened before. By default, the Java Console is not enabled, so you’ll first need to go in to the Java settings and enable it. Because Ignition is built on Java, if problems arise with Ignition – for example, if the Ignition Designer fails to launch – the Java Console is a good place to check for answers. This post provides a few tips on the different tools available for troubleshooting issues both within your application and with the Ignition software.Ī good starting place for debugging Ignition issues themselves is the Java Console. Before the final product hits the plant floor, however, developers must configure and program the platform. Inductive Automation’s Ignition platform is a powerful, flexible, and highly customizable SCADA platform enabling data-driven decision making for industrial enterprises.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |