It looks like you may be starting iX Developer from a project that is stored on a network drive. iX Developer does not work when it is installed to a network drive. Nor does it work when you open a project that is stored on a network drive. iX projects must be stored on a local drive when you are ed...

When you installed iX Developer, did you run setup.exe or the "NeoSetup.msi" file? You need to run the setup.exe otherwise not all the iX Dev dependencies will be installed.

You can not print a screen that is not actually being shown on the HMI. Only the topmost, shown screen, can be printed.

You have the Modbus Master addressing set to use Decimal. Which means that the address range for the Holding resisters is 400000.0 - 465535.15. By using the 44106 address you are referencing the Coil status registers (000000 - 065535), which I do not think you want to do. The controller driver docum...

There is no built in Watchdog functionality in iX Developer. You will have to create a program in C# to monitor the tag. You could create a timer and have the timer monitor the tag. Pseudo code assuming a cyclical counter for the watchdog: Timer checks value of tag and records it. Timer checks value...

This code gets the active instance: this.InstanceName; Unfortunately I cannot provide you with C# programming consulting services. I can only help with iX Developer related C# questions. Writing if statements and the such are out of this forums scope. If you have never programmed in C# I suggest you...

You would have to somehow execute code that checks to see what instance you are on. You can execute via a button push or when a screen is opened. Then I would set a tag based on the instance.

The tag could then be used in the Dynamics of a on screen control to change the color.

The Modbus slave driver only supports Holding Registers in Decimal format. Which means that it will not allow you to use the 30000 or 10000 Modbus registers. The Modbus Master driver will allow you to read those other registers.

Take a look at the Controller documentation. Most likely you have the driver set to use HEX addressing and you are typing in Decimal addresses into the Controller Tag column.

As I already mentioned, you can associate actions with tags. When the comm error system tag goes higher than 0, then your action associated with the tag will fire. It does not matter what screen is open, as the action fires when the tag reaches a specific value.