Need for speed: Run multiple instances of equipment generator (EquipGen.exe) in parallel.

Please note there were some improvements in 2020R2 which you might not have included in your projects yet (they have to be implemented on the equipment template xml files) and could be worth a try.

Typically the xml version for older templates is (based on the Meter_MEO from the ExampleSA):
<?xml version="1.0" encoding="UTF-8"?>
for newer versions you will see the 2nd line:
<?xml version="1.0" encoding="utf-8"?>
<template version="2.0" desc="">

The newer template for Meter_MEO has:
<input name="equipment" file="equip.dbf" desc="Equipment Database">
<field name="NAME" />
<field name="CLUSTER" />
<field name="TYPE" load="true">{type.name}</field>

the last line makes the difference and was not possible in older versions (ie dynamic referring to the equip type, hard coded was possible), but it makes the generations quite a bit more effective (especially if you have loads of equipment with a fair amount of different types).

Please note there were some improvements in 2020R2 which you might not have included in your projects yet (they have to be implemented on the equipment template xml files) and could be worth a try.

Typically the xml version for older templates is (based on the Meter_MEO from the ExampleSA):
<?xml version="1.0" encoding="UTF-8"?>
for newer versions you will see the 2nd line:
<?xml version="1.0" encoding="utf-8"?>
<template version="2.0" desc="">

The newer template for Meter_MEO has:
<input name="equipment" file="equip.dbf" desc="Equipment Database">
<field name="NAME" />
<field name="CLUSTER" />
<field name="TYPE" load="true">{type.name}</field>

the last line makes the difference and was not possible in older versions (ie dynamic referring to the equip type, hard coded was possible), but it makes the generations quite a bit more effective (especially if you have loads of equipment with a fair amount of different types).

Hi Erik, thanks for the tips.

I tried that but now equipgen.exe fail and I can't see anymore my types in EquipmentEditor. My xml files looks like that (I added the line 2 and updated the line 13)

<?xml version="1.0" encoding="utf-8"?>
<template version="2.0" desc="">
<!-- E_ANAVALVE - Vanne analogique -->
	<template desc="Vanne analogique">
	<param name="type">
		<string name="name">E_ANAVALVE</string>
		<string name="parameter-definitions">
		</string>
	</param>
	<input name="equipment" file="equip.dbf" desc="Equipment Database">
		<field name="NAME"/>
		<field name="CLUSTER"/>
		<field name="TYPE" load="true">{type.name}</field>
		<field name="COMMENT"/>
		<field name="CUSTOM1"/>
		<field name="CUSTOM2"/>
		<field name="CUSTOM3"/>
		<field name="CUSTOM4"/>
		<field name="CUSTOM5"/>
		<field name="CUSTOM6"/>
		<field name="CUSTOM7"/>
		<field name="CUSTOM8"/>
		<field name="IODEVICE"/>
		<field name="PAGE"/>
		<field name="TAGPREFIX"/>
		<field name="PARAM"/>
		<array name="param_list">{ToProperty('{param}','=',';')}</array>
	</input>

Is this improvement exist in 2020R2? The Meter_MEO in my ExempleSA don't have this modification.

Thank you,

Hi Geoffrey,

good to read from you :).

In that case I would try:
- delete line 2
it might be introduced for 2023 version - configuration parameters.

If that doesn't work , replace in line 13 {type.name} with the actual name of the type template (E_ANAVALVE)

Yes, removing the line 2 make the build works again but without any observable amelioration.

Thank you,