Modbus and Bacnet websettings : Rename variables and functions to avoid name collisions.
Websettings for modbus and bacnet are now passed to runtime as python files loaded (execfile) at init of PLCObject with the same globals.
Because if this, same names used in previously different modules now colide.
<?xml version='1.0' encoding='utf-8'?>
<project xmlns:ns1="http://www.plcopen.org/xml/tc6_0201" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.plcopen.org/xml/tc6_0201">
<fileHeader companyName="Unknown" productName="Unnamed" productVersion="1" creationDateTime="2014-01-19T11:14:47" contentDescription="This example shows how you can customize build process by using 'make'. "/>
<contentHeader name="Makefile Example" modificationDateTime="2018-08-24T13:12:10">
<coordinateInfo>
<fbd>
<scaling x="0" y="0"/>
</fbd>
<ld>
<scaling x="0" y="0"/>
</ld>
<sfc>
<scaling x="0" y="0"/>
</sfc>
</coordinateInfo>
</contentHeader>
<types>
<dataTypes/>
<pous>
<pou name="program0" pouType="program">
<interface>
<localVars>
<variable name="LocalVara">
<type>
<INT/>
</type>
</variable>
<variable name="LocalVarb">
<type>
<INT/>
</type>
</variable>
</localVars>
</interface>
<body>
<FBD>
<inVariable localId="1" executionOrderId="0" height="30" width="77" negated="false">
<position x="52" y="424"/>
<connectionPointOut>
<relPosition x="77" y="15"/>
</connectionPointOut>
<expression>LocalVara</expression>
</inVariable>
<outVariable localId="2" executionOrderId="0" height="30" width="77" negated="false">
<position x="167" y="424"/>
<connectionPointIn>
<relPosition x="0" y="15"/>
<connection refLocalId="1">
<position x="167" y="439"/>
<position x="129" y="439"/>
</connection>
</connectionPointIn>
<expression>LocalVarb</expression>
</outVariable>
<comment localId="3" height="385" width="760">
<position x="32" y="23"/>
<content>
<xhtml:p><![CDATA[This example shows how you can customize build process by using 'make'.
Sometimes special steps need to be done to build entire project.
But it's not necessary to create another target in Beremiz every time you need to customize something in build process. Just use for that 'Generic' target and describe all necessary steps in Makefile.
For example, you can
- preprocess generated by Beremiz C source files,
- do some fancy source code transformation using any tools you want,
- use any compiler you want,
- call static analyzers,
- run integration tests on the project,
- upload source code to external build server,
- upload to the target and compile it there,
- flash/transfer your compiled binary to the target,
and much much more.
]]></xhtml:p>
</content>
</comment>
</FBD>
</body>
</pou>
</pous>
</types>
<instances>
<configurations>
<configuration name="config">
<resource name="resource1">
<task name="Tsk" priority="0" interval="T#100ms">
<pouInstance name="Inst" typeName="program0"/>
</task>
</resource>
</configuration>
</configurations>
</instances>
</project>