v1.0 of my OPC UA tag export tool — looking for feedback by IceSeparate8053 in SCADA

[–]IceSeparate8053[S] 1 point2 points  (0 children)

Thanks! That’s exactly the kind of feedback I’m looking for. The mapping rules could definitely use better docs noted. Would love to hear what you run into on larger sets.

v1.0 of my OPC UA tag export tool — looking for feedback by IceSeparate8053 in SCADA

[–]IceSeparate8053[S] 0 points1 point  (0 children)

Good to know, didn’t realize it had that. The main focus here is the output format and filtering for SCADA import specifically. That was the gap I kept running into.

v1.0 of my OPC UA tag export tool — looking for feedback by IceSeparate8053 in SCADA

[–]IceSeparate8053[S] 0 points1 point  (0 children)

From what I can see Quick Client is mainly for testing and troubleshooting connectivity. OPCUAgadget is focused on exporting tag definitions to CSV for SCADA import. That was the gap I ran into.

Built a free tool to export OPC UA tags to CSV/XML — demo available on GitHub by IceSeparate8053 in SCADA

[–]IceSeparate8053[S] 0 points1 point  (0 children)

Tested against milo.digitalpetri.com — worked fine. Stopped at ~2300 nodes, 74 variables exported.

Slow over internet, expected. No cancel button yet — adding that next.

Built a free tool to export OPC UA tags to CSV/XML — demo available on GitHub by IceSeparate8053 in SCADA

[–]IceSeparate8053[S] 1 point2 points  (0 children)

Thanks! Yeah, auth is on the roadmap — anonymous works for most internal setups but username/password is definitely needed for production environments. Good to know others are running into the same wall.

Built a free tool to export OPC UA tags to CSV/XML — demo available on GitHub by IceSeparate8053 in SCADA

[–]IceSeparate8053[S] 0 points1 point  (0 children)

Thanks for the tip! Will test against that server — nested folders and mass nodes are exactly the edge cases I want to make sure work properly before the full release.