How to set tag quality (sub?) codes like Bad_WaitingForInitialData?

Simon.de.Kraa · May 7, 2022, 7:03am

I guess you are right. Unfortunately we do need more control over the OPC UA implementation i.e. the status code. Really hope the the exposed tags feature can be extended in the future so at least the status code Uncertain will be emitted as well.

Great product, but for now we will look elsewhere. Thank you all for your support!

Kevin.Herron · May 7, 2022, 1:21pm

I mentioned this in the middle of other posts, but this is on its way for probably Ignition 8.1.18.

Simon.de.Kraa · May 7, 2022, 1:53pm

Nice!

Would be great if you could do this for the unique mappings between quality and status codes(*) that can be found here:

github.com

OPCFoundation/UA-.NETStandard-Samples/blob/c7b99a583ee3407ca2e174fda6e032190bd32eec/ComIOP/Common/Common/ComUtils.cs#L2489

      
        
            		/// <summary>
            		/// Converts a DA quality code to a status code.
            		/// </summary>
            		public static StatusCode GetQualityCode(short quality)
            		{
            			StatusCode code = 0;
            
            
			// convert quality status.
            			switch ((short)(quality & 0x00FC))
            			{			
                            case OpcRcw.Da.Qualities.OPC_QUALITY_GOOD:                     { code = StatusCodes.Good;                              break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_LOCAL_OVERRIDE:           { code = StatusCodes.GoodLocalOverride;                 break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_UNCERTAIN:                { code = StatusCodes.Uncertain;                         break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_SUB_NORMAL:               { code = StatusCodes.UncertainSubNormal;                break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_SENSOR_CAL:               { code = StatusCodes.UncertainSensorNotAccurate;        break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_EGU_EXCEEDED:             { code = StatusCodes.UncertainEngineeringUnitsExceeded; break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_LAST_USABLE:              { code = StatusCodes.UncertainLastUsableValue;          break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_BAD:                      { code = StatusCodes.Bad;                               break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_CONFIG_ERROR:             { code = StatusCodes.BadConfigurationError;             break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_NOT_CONNECTED:            { code = StatusCodes.BadNotConnected;                   break; }
                            case OpcRcw.Da.Qualities.OPC_QUALITY_COMM_FAILURE:             { code = StatusCodes.BadNoCommunication;                break; }

(*) I am aware that the Ignition quality codes are no longer a 100% match but still you could do a mapping where possible and add Ignition quality codes where needed. Imho a great enhancement to the exposed tags feature.

My post on the OPC foundation forum:
https://opcfoundation.org/forum/opc-ua-standard/quality-codes-vs-status-codes/

Thanks Kevin.

Simon.de.Kraa · May 9, 2022, 4:18pm

Any idea when this version will be available for testing?

And if you would consider adding additional Ignition quality codes and quality / status code mappings? As described in my previous post.

Thanks. Appreciate your input.

Kevin.Herron · May 9, 2022, 4:27pm

I'm mapping the ones that make sense, but no we won't just be adding a bunch of arbitrary codes copied from OPC Classic. As I said previously, we call it a QualityCode, and there is still some remaining influence from OPC Classic in that we have an additional good code that has a value of 192, in addition to the default good code of 0 (for the purposes of backwards compatibility), but it is not an enumeration of OPC Classic/DA quality codes.

The final release of 8.1.18 is scheduled for June 14, but the changes will be available in a nightly release as soon as they're finished and have gone through QA.

Simon.de.Kraa · May 9, 2022, 4:47pm

Thanks.

Last question…

What is the best way to check what mapping is actually implemented and when (and where) the Ignition nightly will be available? I really would like to give it atry it once it is available. Anything I can subscribe to?

Kevin.Herron · May 9, 2022, 4:55pm

The nightly releases are available on our downloads page and we update this thread regularly with the changes being merged in.

As for the actual mapping… I think that’ll have to get added to the user manual as part of this ticket work.