During integration, the same macros as in Axxon One are created in Axxon PSIM; however, they lack any preset conditions for triggering, that is, they are "empty" by default.
The integration operates as follows: if a macro triggers in Axxon One, a macro with the same name also triggers in Axxon PSIM, even if no conditions are set in it. The reverse process is also possible: after you start a macro in Axxon PSIM, the corresponding macro is also started in Axxon One.
If necessary, you can set any conditions for triggering the macro in Axxon PSIM (see Creating and using macros). Note that triggering according to the specified conditions will occur only in Axxon PSIM, while in Axxon One, the macro will trigger based on the conditions set in Axxon One.
You can transfer macros from Axxon One to Axxon PSIM. You cannot transfer macros in the opposite way.
You can monitor and handle events received in Axxon PSIM from Axxon One using the following interface objects:
You can handle events received from Axxon One in the same way as Axxon PSIM events. For more details, see Events control and processing.
To enable the ability to use the F12 key to open DevTools in the Axxon One archive browser that you can open from Axxon PSIM when working with the NGP manager module, use the ChromiumWebBrowserDevToolsEnable =1 parameter of the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AxxonSoft\PSIM registry (see Axxon PSIM base version. For the information on working with the registry, see Working with Windows OS registry).