1. UAB Development Status
18/07/2016

2. UAB Development Status
Summary
Multi Package
Migration of Specs File to XLSX
Default Values Treatment in Templates
TIA Portal Integration
Beta Releases
UAB Development Status
18/07/2016

3. Multi Package Implementation
Allow the selection of CPC libraries from CPC Wizard:
Independent resource packages with independent releases
Sub-package defined by groupId
<groupId>cern.uab.resources.cpc.cryo</groupId>
<artifactId>cryo-resources-package</artifactId>
<version>1.9.2</version>
<name>CRYO Resources</name>
<description>CRYO Resources</description>
<groupId>cern.uab.resources.cpc</groupId>
<artifactId>cpc-resources-package</artifactId>
<version>1.9.0</version>
Bootstrap will detect and download the compatible sub-packages
UAB Development Status
18/07/2016

4. Multi Package Implementation
Resources Package Implementation
Unique placeholder for the package name (‘CPC’, ‘Vacuum’ …)
Using a pom.xml property (devicePackageName)
Inject the package name in:
Device type definitions
UAB Development Status
18/07/2016

5. Multi Package Implementation
Resources Package Implementation
Unique placeholder for the package name (‘CPC’, ‘Vacuum’ …)
Using a pom.xml property (devicePackageName)
Inject the package name in:
Device type definitions
ResourcesPackageConfiguration.xml
<Resources Version="${project.version}" xmlns="
<DeviceTypes>
<!-- WARNING: The device types order in this list is the right order for the Unity instance files! -->
<DeviceType Name="DigitalInput" Description="The Digital Input object type" Package="${devicePackageName}"/>
<DeviceType Name="AnalogInput" Description="The Analog Input object type" Package="${devicePackageName}"/>
UAB Development Status
18/07/2016

6. Multi Package Implementation
Resources Package Implementation
Unique placeholder for the package name (‘CPC’, ‘Vacuum’ …)
Using a pom.xml property (devicePackageName)
Inject the package name in:
Device type definitions
ResourcesPackageConfiguration.xml
PlcParams/Siemens.xml (Additional parameters for addressing calculation)
<SiemensPLC Name="PLC1" Description="PLC1 declaration" xmlns="
<ParameterList Name="SiemensSpecificParameters" Description="Specific parameters for Siemens manufacturer" isExpertField="false">
<ParameterList Name="PLCMemory" Description="">
<PositiveIntegerParameter DefaultValue="6000" Description="UAB will create the ${devicePackageName} …" Value="6000" Name="${devicePackageName}"/>
</ParameterList>
</SiemensPLC>
UAB Development Status
18/07/2016

7. Multi Package Implementation
Resources Package Implementation
Unique placeholder for the package name (‘CPC’, ‘Vacuum’ …)
Using a pom.xml property (devicePackageName)
Inject the package name in:
Device type definitions
ResourcesPackageConfiguration.xml
PlcParams/Siemens.xml (Additional parameters for addressing calculation)
Specs will contain the package name for each device
UAB Development Status
18/07/2016

8. Multi Package Implementation
Resources Package Implementation
SiemensDeviceOrder.xml
Added an Index attribute to merge types
<Resources Version="${project.version}" >
<DeviceTypes>
<DeviceType Name="DigitalInput" Description=“…" Index="100"/>
<DeviceType Name="AnalogInput" Description=“…" Index="200"/>
<DeviceType Name="AnalogInputReal" Description=“…" Index="300"/>
<DeviceType Name="Encoder" Description=“…" Index="400"/>
<DeviceType Name="DigitalOutput" Description=“…" Index="500"/> …
<Resources Version="${project.version}" >
<DeviceTypes>
<DeviceType Name="VG_PT" Description=“…" Index="310"/>
<DeviceType Name="VR_GT" Description=“…" Index="320"/>
<DeviceType Name="VP_TP" Description=“…" Index="330"/>
</DeviceTypes>
</Resources>
<Resources Version= "1.9.0" >
<DeviceTypes>
<DeviceType Name="DigitalInput" Description=“…" Index="100"/>
<DeviceType Name="AnalogInput" Description=“…" Index="200"/>
<DeviceType Name="AnalogInputReal" Description=“…" Index="300"/>
<DeviceType Name="VG_PT" Description=“…" Index="310"/>
<DeviceType Name="VR_GT" Description=“…" Index="320"/>
<DeviceType Name="VP_TP" Description=“…" Index="330"/>
<DeviceType Name="Encoder" Description=“…" Index="400"/>
<DeviceType Name="DigitalOutput" Description=“…" Index="500"/> …
UAB Development Status
18/07/2016

9. Multi Package Implementation
New Application / Upgrade
Select the additional packages
Merge the resource packages:
Add the resources from additional packages
Merge ResourcesPackageConfiguration.xml
Merge PlcParams/Siemens.xml
Merge PlcParams/SiemensDeviceAddressOrder.xml
Merge Spec files including devices from additional packages
Upgrade an application with additional packages
Select by default the additional packages if not selected by the user i.e. additional packages cannot be removed during an upgrade
Cannot downgrade additional packages
UAB Development Status
18/07/2016

10. Multi Package Implementation
TODO
Define Siemens.xml for sub-packages
Memory address calculation for sub-package devices
Restore unit tests in memory address calculation
UAB Development Status
18/07/2016

11. Resources Package Modifications
New parent pom for CPC resource packages
Profiles for generation of documentation
Website
Pdf
Images from device definitions
Specs generation in XLSX from maven-plugin
Vacuum resources package created (from Ben implementation)
Sources for site generation missing
TODO
Fix test errors in RP (cannot release from Jenkins)
UAB Development Status
18/07/2016

12. Migration of Spec file to XLSX
Specs generation
Generate the new specs from the device type definitions
Maven plug-in to generate the new specs
UAB Core
New java classes to handle specs in the new format [under testing]
New factory class to create specs
Use the factory class to get the specs: SpecFactory.getSpec(..)
CPC
Others …
Upgrades
New plug-in for FlexExtractor to handle XLSX files
Modify FlexExtractor API to use a unique spec upgrade config file
Modify the spec file upgrade to handle XML and XLSX files
Upgrade the Siemens user resource files (static, dynamic)
Type Builder
Generate XLSX instead of XML
UAB Development Status
18/07/2016

13. Default Values Treatment in Templates
Device Type Definitions
Add the default values for the specification attributes
Specs
Add a new row for the default values
The user can modify the default values
UAB Core
Modify spec API to return the default value if no value is specified
Jython Templates
Remove the hardcoded default values
UAB Development Status
18/07/2016

14. TIA Portal Integration
Wizard
New target platform: TIA Portal
Rename others? (Step-7, Schneider)
Bootstrap back compatibility! New Bootstrap version (?)
Integrate plug-ins & panels in CPC Wizard
Define PLC types for TIA Portal (S7-1200… ???)
Plug-ins
Code Refactoring: Avoid duplications (Siemens / TIA plug-ins)
Resources Package
New PLC params (TIAPlc)
New templates
UAB Development Status
18/07/2016

15. UAB Development Status
Beta Releases
UAB Core v1.6.2-beta-08
CPC Wizard v1.9.0-beta-05
CPC Resources Package v1.9.0-beta-01
Vacuum Resources Package v1.9.0-beta-01
Bootstrap v1.2.6-beta-04
Type Creation Tool v1.3.2-beta-02
uab-specs-generator v0.0.1-beta-01
UAB Development Status
18/07/2016