Print statements can be extremely helpful in troubleshooting tricky pieces of scripting. Print statements that you add to your Gateway Event Scripts are also output to the wrapper.log file. Gateway Event Script errors are not the only handy bits of information logged to the wrapper file. It is recommended that you download a tool like Wintail that will allow you to view the tail-end (hence the name) of the changing wrapper.log without having to constantly reopen the file.
This file is in constant use by the Ignition system and is being modified in realtime. If you have just started Ignition for the first time you will see something like this: When you open this file, scroll to the bottom to see the newest messages. Version 7.2- \Inductive Automation\Ignition\wrapper.log Version 7.3+ \Inductive Automation\Ignition\logs\wrapper.log You can find this file in the install directory under These errors are indeed logged and there are a couple places where you can go to find inspect these error messages.Īll of the error messages from your Gateway Event Scripts are logged to one file: wrapper.log. One might think that these errors would be generated and logged in the Ignition Gateway Console utility, but unfortunately due to how logging works internally this is not the case. In a Gateway Event Script the errors still appear, but because there is no GUI associated with it, they don't show up for the user to see. Writing an event script that runs on a client (through a client event Script or on a component) allows for easy debugging because a red error message pops up when something goes wrong.
0 kommentar(er)
