it's a shame we can not generate templates but it will be useful to be able to generate instances.

Probably in a future version (it is never too late) we will be able to generate a template with generic import and why not from a right click on the variable selector!!! :woohoo: :woohoo: :woohoo:

Hello,
Where can I find a document updated that explains the AA structure of Tpl_Instances.xml.?

Thank you.

Hi Manu,

This is not documented but, normally, nobody have to use it.
What's your need?

Nico

Hi Nico,
I have a CPP customer (AMICS) who is using is own application generator in order to generate the PLC progam & scada application.
He spend 3 days in Lyon with Raph to have demo / explanation and specific things in PcVue for developpers such as : Webservices in PcVue 12.0, implementation of .Net components, XMLImporter.exe, run AA genereation with command lines, etc...

No he tries to implement all those stuffs but he finds no helpfull documentations in PcVue help / pdf or in the KB.
Many of his needs are not officially documented yet (internal use)

I found the document from Gilles below. but it a 2013 document and AA has changed from 2013. But it's a document I can share to the customer
. So is there an update of this document?

This is the message from the customer :

"Salut Manuel,
Je pense que la réponse est classé secret défense mais je pose quand même la question.
L’application Architect contient la liste des instances dans le fichier Tpl_Instances.xml. Est-ce qu’on a une doc sur la structure de ce fichier ?
Le but pour nous maintenant est d’utiliser l’application Architect mais de générer automatiquement la liste des instances car c’est une image de la modélisation objet que nous avons déjà dans l’automate.
Donc avec notre soft, j’aimerais modifier ce ficher et lancer la génération. "
Manu

Hello,

As Nicolas said, the format of the file Tpl_Instances.xml is not described and is internal. But reading your last message I think there is a small misunderstanding.

What your customer wants is the Generic Import format for the Application Explorer. The "official" documentation can be found in the directory: "PcVue 12Development kitsImport Toolkit" (when installed), but unfortunately not everything is described there and in particular the Architect items (which is a shame).

I'll try to get some samples and eventually the format description.

Hi Florent,
Thnks for you answer
maybe it's that Generic Import with the xml format for Architect that he needs.

I had a call with Benoit this morning. We will see what is the best way to exchange with Amics about his technical & specifics needs.

Manu

Hello,
...
What your customer wants is the Generic Import format for the Application Explorer.
...

Yes, I was obviously talking about the Architect, not the Explorer...

Here are some details, with the main3 types of Collection/Items.

Topology Elements

<Collection type="TopologyElements" id="(default).ParentFullName">
<Item id="ElementName">
ElementBranch
ElementDescription

Instances

<Collection type="Instances" id="(default).ParentFullName">
<Item id="InstanceName">
TemplateNameWithLib
InstanceBranch
InstanceDescription

Parameters in Instances

<Collection type="InstanceParameterInputValues" id="(default).InstanceFullName">
<Item id="ParameterNameWithLib">
ParameterValue

Few things:
- (default) corresponds to the root element
- ParentFullName corresponds to the concatenation of the upper Names (eg: level0.level1.level2)
- xxxName property corresponds to the name displayed in the treeview
- xxxNameWithLib corresponds to the full name of th template/parameter, it does not include the category (eg: /Lib/TemplateName)

There are other collections/items(input values, select/deselect, but I need to dig a little bit more if toy need them.

Hi all
Here a little trick since Pcvue 12 if you don't know it (Thanks Nico Kuntzer !) Sorry it 's in french