https://opcfoundation.org/forum/opc-ua-standard/create-monitoreditem-with-node-statuscode-badnodeidunknown/

Redefine “the StatusCode of the ProcessDataOutput shall become a bad code”.
Adjust related test case Device.ProcessData.Write: ERR-001.

A possible bad statuscode could be Bad_OutOfRange.
@AlexanderAllmendinger, what is your opion? Is there a more suitable cad statuscode available/defined?

grafik.png (935 bytes)   

grafik.png (935 bytes)   

Bit 6: PD status
This bit indicates whether the Device can provide valid Process Data or not. Defined values for the parameter are listed in Table A.5.
This PD status flag shall be used for Devices with input Process Data. Devices with output Process Data shall always indicate "Process Data valid".
If the PD status flag is set to “Process Data invalid” within a message, all the input Process Data of the complete Process Data cycle are invalid.

AA via Email:
UA Part 8: DataAccess - 6.3 Data Access status codes
https://reference.opcfoundation.org/Core/Part8/v105/docs/6.3

Bad_DeviceFailure There has been a failure in the device/data source that generates the value that has affected the value.

WG approved. Incoporate it into CS V1.00 and V1.01.

Martin will update 1.00, Deepak should update 1.01.

WG meeting: Deepak already incorporate this issue in his local version. WG waiting for next review version.

Updated the working version of the document with the Status code : "Bad_DeviceFailure "

V1.01 spec has been updated

WG approved changes.