Data not processed by the UA-Cloud-Twin

[digitaltwinconsortium]

Data not processed by the UA-Cloud-Twin

[barnstee]

Hi Steven, I can see from the discovered assets that the Munich production line is missing in UA Cloud Twin. it looks like there is a problem with the OPC UA certificate exchange that happens with the Azure Storage. I've seen this happen once since I switched to a slower VM (but a lot cheaper VM!). I will increase the pauses between starting the individual parts of the simulation. Please Stop and then Start the production line using the batch scripts on the VM one more time, that should fix it. Also, it is normal that the UA Cloud Twin no longer processes telemetry data, only metadata. This was another cost optimization I made, so telemetry is sent to ADX only now.

[Sdelausnay]

Hi, Thanks for the quick response.

Indeed the waiting time was the issue. I saw the waiting "press a key to continue" and didn't wanted to wait :)
Ok now I also understand better how the data flow is working so ADT is purely for modeling and all telemetry data is stored in ADX and quired in that way.

Sorry for the question, was a bit to unpetitioned to get everything up and running.

Very nice demo! Really interesting to see how quickly you can build these dashboards.

[barnstee]

Any time, my friend. Let me know what you think of the solution! :-) Also, if you really, really want to have ADT process the telemetry to get a digital twin per OPC UA node which is updated all the time, you can set the environment variable PROCESS_TELEMETRY_MESSAGES to 1 and the behavior will be as it was before.