Log In
Home
10/18/2019
Offline
I have implemented a prototype for OPC 40451-1 UA CS for Tightening Systems. When I connect to the server, I am able to read the complex types defined in the specification, but I see the following warnings in the Log window of the UA Client:
DataType ResultDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType TighteningResultDataType not found in dictionary with NamespaceUri . Ignoring DataType.
...
I am not able to understand why I see this warning when the data types are available in the address space -> Types. The problem with this error is when i develop a Javascript Client and trying to read a complex structure, it is not working and throwing this error.
The desktop based UA client just logged this as warning and able to read/subscribe the data.
Can someone suggest what is missing the nodeset and any suggestion on fix?
05/30/2017
Offline
Without more content for those warnings it is impossible to know why they are produced. They sound like they are processing the DataType of a Variable that references the types and can't resolve them so it is necessary to know what Variable had the issue.
10/18/2019
Offline
These warnings are shows in the UA Client Log Window as soon as I connect to the OPC UA Server. I can get data content in those variables and Read Attributes shows the correct Type Definition and Data Type in the Attributes Window.
The nodeset is https://github.com/OPCFoundati.....Tightening
I tried to paste the error. Basically, there are around 10 complex structures defined and there are variables for few of those in the IJT Tightening Nodeset file.
I get these warnings in the Log Window as per attached image (Not sure if insert image worked properly as it shows nothing on my side).
The warnings are listed below. But these data types are available in the address space and there is ONLY one variable in the address space of Variable type ResultType which is of data type ResultDataType.
DataType ErrorInformationDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType ProcessingTimesDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType ResultDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType ResultValueDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType StepResultDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType StepTraceDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType TagDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType TighteningResultDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType TraceContentDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType TraceDataType not found in dictionary with NamespaceUri . Ignoring DataType.
DataType TighteningTraceDataType not found in dictionary with NamespaceUri . Ignoring DataType.
It looks something in the nodeset or some link which I could NOT troubleshoot. What is the way to troubleshoot this issue? I mean from the OPC UA Client side, it reads the data as expected but these warnings occur only with this specific nodeset file implementation.
05/30/2017
Offline
I think your client has a bug.
If you look at the NodeSet it defines several Aliases that need to be resolved:
<Alias Alias="ProcessingTimesDataType">ns=1;i=3002</Alias>
<Alias Alias="TagDataType">ns=1;i=3003</Alias>
<Alias Alias="ResultDataType">ns=1;i=3004</Alias>
<Alias Alias="ErrorInformationDataType">ns=1;i=3006</Alias>
<Alias Alias="ResultValueDataType">ns=1;i=3007</Alias>
<Alias Alias="ResultEvaluation">ns=1;i=3008</Alias>
<Alias Alias="StepResultDataType">ns=1;i=3009</Alias>
<Alias Alias="TraceDataType">ns=1;i=3011</Alias>
<Alias Alias="TighteningTraceDataType">ns=1;i=3012</Alias>
<Alias Alias="StepTraceDataType">ns=1;i=3013</Alias>
<Alias Alias="TraceContentDataType">ns=1;i=3014</Alias>
They match the errors exactly which says the client is not trying to resolve the aliases and treating them as bad NodeIds (or it can't resolve Aliases for NodeIds defined within the NodeSet).
I would manually replace the Aliases with a search and replace in your local copy of the NodeSet and try again.
Please tell us if that works.
10/18/2019
Offline
Thanks for the response Randy, I tried your suggestion with one data type which is TraceContentDataType where I replaced the alias name with actual node Id in places where DataType="TraceContentDataType" was given, but when I connect to the OPC UA Server, it shows the same warning.I get the same warnings for few types defined in DI as shown below:rnDataType FetchResultDataType not found in dictionary with NamespaceUri . Ignoring DataType.DataType TransferResultErrorDataType not found in dictionary with NamespaceUri . Ignoring DataType.DataType TransferResultDataDataType not found in dictionary with NamespaceUri . Ignoring DataType.DataType ParameterResultDataType not found in dictionary with NamespaceUri . Ignoring DataType.rnWith respect to UA Client, I am using UA Expert and that works in regular demo servers and other applications.rnI thought initially, maybe it is due to namespace resolution but when I check the namespaces of the data type they are shown correctly from the OPC UA Client view, all Tightening nodes shows the correct namespace and DI related types also shows the correct namespace.rnThis looks some where some meta data is missing or conflicting. Not sure of the root cause yet.
10/18/2019
Offline
While troubleshooting, noticed that there are around 14 structures mentioned above for which i see that warning from UA Expert Log Window..
I have noticed also same number following warning Logs:
[uastack] UaStructureField::setDataTypeId: not able to get BuiltInType for valueType
What i am unable to understand is, the UA Expert client is able to read the values of the structure type and data types are correctly mapped in the Types in the address space.
05/30/2017
Offline
The errors indicate errors in the NodeSet that may affect a Node that uses the types rather than the type itself. So you can't infer anything from the fact that the types loaded correctly.
The most likely source of error: aliases or wrong namespace index.
That said, I suspect alias issues because I see they are using Aliases for the DataTypes of fields which is yet another way to break existing parsers who do not expect aliases for types defined in the current NodeSet.
10/18/2019
Offline
Hi Randy,
The following errors got resolved by Delesecting "Add JSON Nodes" and "Add Datatype Dictionary" from the UaModeler settings.
It seems, DatatypeDictionary is DEPRECATED and few clients like UA Expert support both newer schema and older type of schema.
I need to still check what should be the final option to be selected while generating the NodeSet if few older clients does NOT support DataType Attribute schema and if we need JSON encodings too.
Wolfgang suggested the above option in UaModeler.
1 Guest(s)
Usage Policy