Hi everyone,
I write this post in order to ask if there is someone that encountered the same error as me. I have a .tt2pro project where my working model is more than ~130k nodes big, and when I try to export the XML of the model I get the error message saying that the output file is too big. I am currently trying smaller versions of the model with less nodes, so far I have been able to generate a XML file from a ~19k nodes model and I am slowly growing it to see what´s the limit.
Does anyone know if there is any configuration parameter that could be modified in order to allow this kind of generation? Or is just that the model is too big for the UAModeler to handle?
Info: I am running version 1.6.7
Kind regards.
Model too big to generate XML file.
Moderator: uamodeler
-
- Jr. Member
- Posts: 2
- Joined: 20 Nov 2024, 07:14
Model too big to generate XML file.
Last edited by justohdezromera on 20 Nov 2024, 11:33, edited 1 time in total.
- Support Team
- Hero Member
- Posts: 3208
- Joined: 18 Mar 2011, 15:09
Re: Model too big to generate XML file.
Hi,
the UaModeler has (if it is licensed correctly) no limit in terms of XML, other than the overall memory of the computer. That said, it is not limiting the "number" of nodes, and not the "size" of each of them. Therefore the assumption is that just the amount and size is just to much for the memory.
Keep in mind the XMLNodeSet2 format of OPC Foundation was "intended for type system only". Some people think it is good idear to put "instances" into the XML, and others even think it would be good to put "values" into the XML. This may work for very few nodes, but because the format is inefficient, will not scale. Of course this will not work with hundrets of thousands, nor with millions, nor with hundrets of millions of nodes. In fact, it will not even work if it is just few instances with very large value (string of several giga bytes).
You should have "types" in the XML only, and get yourself a different mechanizm for instances (and values).
the UaModeler has (if it is licensed correctly) no limit in terms of XML, other than the overall memory of the computer. That said, it is not limiting the "number" of nodes, and not the "size" of each of them. Therefore the assumption is that just the amount and size is just to much for the memory.
Keep in mind the XMLNodeSet2 format of OPC Foundation was "intended for type system only". Some people think it is good idear to put "instances" into the XML, and others even think it would be good to put "values" into the XML. This may work for very few nodes, but because the format is inefficient, will not scale. Of course this will not work with hundrets of thousands, nor with millions, nor with hundrets of millions of nodes. In fact, it will not even work if it is just few instances with very large value (string of several giga bytes).
You should have "types" in the XML only, and get yourself a different mechanizm for instances (and values).
Best regards
Unified Automation Support Team
Unified Automation Support Team
-
- Jr. Member
- Posts: 2
- Joined: 20 Nov 2024, 07:14
Re: Model too big to generate XML file.
Thank you for the reply, it was very useful insight.