Mappings

Creating mappings is the most relevant activity to use the Bridge Generator.

• Each <mapping> node defines the matching rules and can have one or more child tag nodes (<dynsim>, <mwpl>, <rules>).

• Each tag node encloses the contents associated to the mapping rule.

For information on typical mappings to connect virtual items to their counterpart on the process simulator, see Sample mappings for ChannelSIM4ME.

Code example

This is a code example for mappings.

<?xml version="1.0" encoding="utf-8" ?>

<mappings>

<!-- .. -->

<mapping type="ItemValve" name="$1600-RF108A" outputEnabled="true">

<shares>

<share field="{name}.rotationSpeed" direction="in" />

</shares>

<dynsim>

<analog name="{name:5:2}{name:0:4}_{name:7:3}.POS" direction="in" mode="router" uom="%"/>

<analog name="{name:5:2}{name:0:4}_{name:7:3}.OP" direction="out" mode="direct" uom="%"/>

<analog name="{name:5:2}{name:0:4}_{name:7:3}.TIMEOP" direction="in" mode="router" uom="sec"/>

</dynsim>

<mwpl>

<sfloat name="{name}.value" capture="false"/>

<sfloat name="{name}.op" capture="false"/>

<sfloat name="{name}.rotationSpeed" capture="false"/>

</mwpl>

<rules>

<trigger from="dynsim:{name:5:2}{name:0:4}_{name:7:3}.POS" to="mwpl:{name}.value" value="[*'{0:0.000}',n:#@dynsim:{name:5:2}{name:0:4}_{name:7:3}.POS@/100#]"/>

<trigger from="mwpl:{name}.op" to="dynsim:{name:5:2}{name:0:4}_{name:7:3}.OP" value="#@mwpl:{name}.op@*100#"/>

<trigger from="dynsim:{name:5:2}{name:0:4}_{name:7:3}.TIMEOP" to="mwpl:{name}.rotationSpeed" value="#(1/@dynsim:{name:5:2}{name:0:4}_{name:7:3}.TIMEOP@)*(@dynsim:SIMSPD@/100)#"/>

</rules>

</mapping>

<mapping type="ItemValve" name="" outputEnabled="true">

<patches>

<item key="{name}.value" value="0" />

</patches>

</mapping>

<!-- .. -->

</mappings>