<!-- Copyright 2016 CERN and GSI This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. -->
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see http://www.gnu.org/licenses/.-->
<xs:documentation>A SILECS configuration contains the class designs, the memory mapping and the hardware distribution for a given set of PLCs.</xs:documentation>
<xs:documentation>A SILECS configuration contains the class designs,
the memory mapping and the hardware distribution for a given set of
PLCs.
</xs:documentation>
<xs:appinfo>
<xs:appinfo>
<doc>
<doc>
The SILECS configuration defines the data structure and the communication parameters required for the interconnection of the PLCs and the Front-End clients. It consists of 3 parts:
The SILECS configuration defines the data structure and the
<ol>
communication parameters required for the interconnection of the
<li> Design: to define the structure of the exchanged data
PLCs and the Front-End clients. It consists of 3 parts:
<li> Mapping: to define the PLC memory mapping and the protocol parameters
<ol>
<li> Generation: to define the hardware on which we will deployed the different Mapping
<li> Design: to define the structure of the exchanged data
</ol>
<li> Mapping: to define the PLC memory mapping and the
Generally under the responsability of a unique expert entity, an SILECS configuration is done for a set of classes and PLCs in the scope of a particular project or set of equipment.
protocol
parameters
<li> Generation: to define the hardware on
which we will deployed the
different Mapping
</ol>
Generally
under the responsability of a unique expert entity, an SILECS
configuration is done for a set of classes and PLCs in the scope of
a particular project or set of equipment.
</doc>
</doc>
</xs:appinfo>
</xs:appinfo>
</xs:annotation>
</xs:annotation>
...
@@ -38,12 +38,12 @@ along with this program. If not, see http://www.gnu.org/licenses/.-->
...
@@ -38,12 +38,12 @@ along with this program. If not, see http://www.gnu.org/licenses/.-->
<!-- No support for this type in CERN codegen so far<xs:element name="Beckhoff-RIO" type="BeckhoffRIOType">
<xs:annotation>
<xs:annotation>
<xs:documentation>A Beckhoff-Mapping defines a particular Mapping
<xs:documentation>A Beckhoff-RIO deployment defines the physical Mapping of TwinCAT Remote IO modules.</xs:documentation>
of classes intended to TwinCat PLCs
</xs:annotation>
</xs:documentation>
</xs:element>-->
</xs:annotation>
<xs:elementname="Rabbit-uC"type="RabbituCType">
</xs:element>
<xs:annotation>
<!-- No support for this type in CERN codegen so far<xs:element name="Beckhoff-RIO" type="BeckhoffRIOType"> <xs:annotation> <xs:documentation>A Beckhoff-RIO deployment defines the physical Mapping of TwinCAT Remote IO modules.</xs:documentation> </xs:annotation> </xs:element> -->
<xs:documentation>A Rabbit-Mapping defines a particular Mapping of classes intended for Rabbit microcontrollers</xs:documentation>
<xs:elementname="Rabbit-uC"type="RabbituCType">
</xs:annotation>
<xs:annotation>
</xs:element>
<xs:documentation>A Rabbit-Mapping defines a particular Mapping of
<xs:documentation>Number of the diagnostic DB that is the first one of the global configuration (corresponds to the common SilecsHeader data-block).</xs:documentation>
DEVICE_MODE: One S7-DB per class/device
<xs:appinfo>
([class-name]_[device-label|id]),
<doc>
<br>containing the
Number of the diagnostic DB that is the first one of the global configuration ( >=1)
<xs:documentation>Start address of the SILECS configuration (corresponds to the common SilecsHeader block address). Attention: 16bit address value is expected independently from the HW model (16 or 32 bit).</xs:documentation>
<doc>
<xs:appinfo>
BLOCK_MODE: One data-segment per class/block
<doc>
([class-name]_[block-name]),
Start address of the SILECS configuration (corresponds to the common SilecsHeader block address).
<br>containing array of
<br>Attention: 16bit address value is expected independently from the HW model (16 or 32 bit)
<xs:documentation>Start address of the SILECS configuration (corresponds to the common SilecsHeader block address). Attention: 16bit address value is expected independently from the HW model (16 or 32 bit).</xs:documentation>
<doc>
<xs:appinfo>
BLOCK_MODE: One data-segment per class/block
<doc>
([class-name]_[block-name]),
Start address of the SILECS configuration (corresponds to the common SilecsHeader block address).
<br>containing array of
<br>Attention: 16bit address value is expected independently from the HW model (16 or 32 bit)
<xs:documentation>Start address of the SILECS configuration
(corresponds to the common SilecsHeader block address). Attention:
16bit address value is expected independently from the HW model (16
or 32 bit).
</xs:documentation>
<xs:appinfo>
<doc>
Start address of the SILECS configuration (corresponds to the
common
SilecsHeader block address).
<br>Attention: 16bit
address value is expected independently from the HW model
(16 or 32
bit)
</doc>
</xs:appinfo>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- No support for this type in CERN codegen so far <xs:complexType name="BeckhoffRIOType">
<!-- No support for this type in CERN codegen so far <xs:complexType name="BeckhoffRIOType"> <xs:attribute name="system" type="BeckhoffSystemType" use="required"> <xs:annotation> <xs:documentation>System infrastructure used to develop and/or configure the controller software.</xs:documentation> <xs:appinfo> <doc> System infrastructure used to develop and/or configure the Controller software. </doc> </xs:appinfo> </xs:annotation> </xs:attribute> <xs:attribute name="model" use="required"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="BK9000"/> <xs:enumeration value="BK9050"/> <xs:enumeration value="BK9100"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="io-base-address" type="xs:unsignedInt" use="required"> <xs:annotation> <xs:documentation>Start address of the Remote IO modules (can be 0 if not required). Attention: 16bit address value is expected independently from the HW model (16 or 32 bit).</xs:documentation> <xs:appinfo> <doc> Start
address of the Remote IO modules (can be 0 if not required). <br>Attention: 16bit address value is expected independently from the HW model (16 or 32 bit). </doc> </xs:appinfo> </xs:annotation> </xs:attribute> </xs:complexType> -->
<xs:annotation>
<xs:documentation>System infrastructure used to develop and/or configure the controller software.</xs:documentation>
<xs:appinfo>
<doc>
System infrastructure used to develop and/or configure the Controller software.
<xs:documentation>Start address of the Remote IO modules (can be 0 if not required). Attention: 16bit address value is expected independently from the HW model (16 or 32 bit).</xs:documentation>
<xs:appinfo>
<doc>
Start address of the Remote IO modules (can be 0 if not required).
<br>Attention: 16bit address value is expected independently from the HW model (16 or 32 bit).
<xs:documentation>Data access mode is defined at PLC level for all the classes</xs:documentation>
<xs:appinfo>
<doc>
DEVICE_MODE: One C struct field per class/device ([class-name]_[device-label|id]), <br>containing the corresponding ordered list of Blocks
<br>BLOCK_MODE: One C struct field per class/block ([class-name]_[block-name]), <br>containing array of corresponding Block, one element per device
<xs:documentation>Data access mode is defined at PLC level for all the classes</xs:documentation>
<xs:enumerationvalue="Rabbit_RCM_4010"/>
<xs:appinfo>
<xs:enumerationvalue="Rabbit_RCM_2000"/>
<doc>
</xs:restriction>
DEVICE_MODE: One C struct field per class/device ([class-name]_[device-label|id]), <br>containing the corresponding ordered list of Blocks
</xs:simpleType>
<br>BLOCK_MODE: One C struct field per class/block ([class-name]_[block-name]), <br>containing array of corresponding Block, one element per device
<xs:documentation>Number of the diagnostic DB that is the first one of the global configuration (corresponds to the common SilecsHeader data-block).</xs:documentation>
<doc>
<xs:appinfo>
DEVICE_MODE: One C struct field per class/device
<doc>
([class-name]_[device-label|id]), <br>containing the
Number of the diagnostic DB that is the first one of the global configuration ( >=1)
corresponding ordered list of Blocks
</doc>
<br>BLOCK_MODE: One C
</xs:appinfo>
struct field per class/block ([class-name]_[block-name]),
</xs:annotation>
<br>containing array of corresponding Block, one element per
<xs:documentation>Data access mode is defined at PLC level for all the classes</xs:documentation>
<xs:annotation>
<xs:appinfo>
<xs:documentation>System infrastructure used to develop and/or
<doc>
configure the controller software.
DEVICE_MODE: One shared variable per class/device (//class-name//controllerName//device-label), <br>containing the corresponding ordered list of Blocks.
</xs:documentation>
</doc>
<xs:appinfo>
</xs:appinfo>
<doc>
</xs:annotation>
System infrastructure used to develop and/or configure the
