In this blog, I have mentioned some of the issues faced during OPCUA setup and possible solution.
Lets get into the topic.
The reason could be that address space of the OPCUA server is huge and there could be possible frequent timeouts happening while scanning. To find out that run the OPCUA agent by adding the following to log.xml file.
<logger name="com.cumulocity.opcua.client" level="TRACE" />
<logger name="com.prosysopc.ua.client" level="TRACE" />
Check if the datapoint is sending the data and its interval.
Check the variables path if it is correct. If any one variable’s path to the data-point is incorrect, then the device creation gets affected.
Path can be validated by creating operation. Check OPC UA - Cumulocity IoT Guides for more info.
Check the file extension if the file is csv or csv UTF-8 encoded. If it is csv UTF-8 encoded then change it to plain csv extension.
Check if all mandatory headers are filled.