Merge projects

1) Merge modules with different names directly;

2) If the parameters of same named module are different, rename it and merge it;

3) Modules with the same name have the same parameters and do not need to be merged.

1) Merge arrays with different names directly;

2) Arrays with the same name and parameters, and whose module names have not been changed in the previous step, will not be merged; Parameters of "Create pile" in the order of merging, with the first one with parameters as the reference;

3) For those with the same name but not meeting the conditions in 2), merge them after renaming.

1) When the coordinates of transformers from different SKPs coincide and have same code, merge the combiner equipment and string to which these two transformers belong into one power block;

2) Except for 1), all power blocks will be merged. When there is an overlap in coding, priority will be given to retaining them in the order of merging;

3) After the merge is completed, when saving the SKP, it will check whether the imported arrays overlap with the main project. If so, the imported arrays will be deleted.

1) There are transformers with 3 or 4 of the electrical connection method in the project to be merged, and MPPT has been set up;

2) If there are electrical parameters with the same electrical connection method and consistent capacity, skip them, otherwise merge them.

1) Directly merge inverters with different names;

2) If the parameters of the inverter with same name are different, rename it and merge it;

3) Inverters with same name have same parameters and will not be merged.

1) All flexible brackets are unconditionally merged;

2) The columns and foundation of the flexible bracket are defined and created by corresponding components; When merging projects, components in different SKPs will be automatically renamed by SU, even if the content is the same. Therefore, after the merger is completed, the default columns and foundation components need to be re associated with a unique default component definition, and then excess definitions need to be cleared;

3) For flexible brackets that is using templates, the component names of their columns and foundations correspond one-to-one with the template names. After merging, automatic renaming by SU maybe cause confusion, so it is necessary to update the name of template, template names in the foundation and properties, and corresponding component definition names.