As you can see, the communication between the CLP and the Ignition is working just fine, when I’m looking at the OPC Quick Client.
But inside my application, this Uncertain_InitialValue appears.
Have you tried binding Low_level_T1 to a component on screen? I’ve seen that before on new tags, granted it was with a Leased tag group and not the Default (Direct) tag group.
Edited to add: Another thing to check is the tag group of the uncertain tags. If the tag group does not exist, the tag will never be polled. I stumble into this occasionally when importing tags with custom tag groups.
Yes, I have, but the problem kept appearing.
Although, I have already solved the problem.
Solution: Just waited until the next day and all those problems related to uncertain values of tags were gone.
Adding info here, to help anyone in the future, since my search lead to this page.
In our version of this error the issue was the tag group rate was set to 0. (It had previously not been set to 0, someone had made an over the weekend change) The fix was to return the rate back to the non-zero value.
This error occurred in concert with server OS patching, adding confusion.
Also, no log pointed to this, it was found by chance while looking for last resorts on things to check.
I also Experienced something similar. I had a Tank level that would send out Clear notifications any time the Gateway was restarted even though the tag alarm never went active. I tried binding to the one of the tags 4 alarms to disable it if communications were down thinking it would be disabled when the gateway started back up initially.
This didnt really work, so I ended up binding to the overall alarm enable disable property. This seemed to also not help, but it didnt seem to be hurting anything so I left it.
After upgrading to a later version of ignition and updating the project a time or two, all of a sudden the tank level tag had an "Uncertain Initial Value" and would nut update. I could create a new tag with the same OPC tag and it would update fine though.
Once I removed the binding on the overall alarm enable property, the tag went back to normal. I also found the fix to the initial problem I was having of alarm notifications going out for cleared status on start up from another post. I needed to check the box for acknowledged drop out condition on the alarm pipeline.
It seems like if there is an incorrect parameter set on the tag, it just defaults to "Uncertain Initial Value". If any one else has this problem in the future, try reducing the complexity of the tag property bindings or eliminating them until it starts working.