NSClientSearchNodeFlags (ENUM)

TYPE NSClientSearchNodeFlags :

Attributes:

qualified_only

InOut:

Name	Initial	Comment
SearchByType	16#1
SearchByVersion	16#2
SearchById	16#4
SearchByNodeName	16#8
SearchForDirectChildOfUsOnly	16#10
SearchForDirectChildOfAddressOnly	16#20
SearchForDirectChildOfUsOrAddressOnly	SearchForDirectChildOfUsOnly OR SearchForDirectChildOfAddressOnly
SearchIgnoreOurselfsIfTwoPlcs	16#40	If this flag is used, then the scan will succeed in the following ambiguity situation too and return the info of the second found plc: - We have exactly two matches - One of these matches is our own plc The rationale behing this is, that a scan is used while we have two plcs (due to the same name probably Windows) with the same identification info. For real work, this is probably not really a usecase. Nevertheless, this will happen quickly if somebody wants to test the dataserver. Then the most simple test is to start two plcs locally and thus we have exactly this situation. To allow this usecase without causing severe compatibilty problems, we simply return the other plc and go on. This flag is only relevant for scanning for a specific node. When searching all nodes, this flag will be ignored. It is up to the caller to do the according filtering.
SearchForFirstMatch	16#10000
SearchForNonAmbiguousMatch	16#20000