So I have a tag that occasionally will be NAN in the PLC. This could be for a number of reasons, most of which involve a bad comm or a Divide by 0. Ignition will then read the tag as a bad quality and putting a try() function on the expression does not seem to help hide the bad data. When this tag is being divided by 0, the equipment has not been run yet so its efficiency really should show NAN or something equivalent. Other HMIs will show some kind of letter value for these kinds of conditions. Is there a way that Ignition can deal with this condition? Why does a try statement seem to fail?