Subsection: Demand

This subsection of IOMapping allows the module IOs to specify properties (example: 24V and not 230V), which should be offered by the device IOs for proper connection. The demanded properties can be assigned as "offering" properties to the devices IOs during generation. The assignment is stored attached to the device description file.

For the automatic IO-connection of the device generator, this means that each module IO with "demanding" properties will scan the generated devices or wildcards of its parent modules until the a device and IO channel is found, which "offering" properties meets the demands

SEC IOMapping : <target>                           //optional: yes, modifier: [UPDATE]
    Parent := <target ID>;                           //optional: yes, type: ID
    SEC Demand                                          //optional: yes, modifier: [UPDATE]
            Desc := <description>;                       //optional: no, type: text
            Properties := [<property1>,<property2>,...]; //optional: no, type: IDList
    END_SEC
END_SEC

. Specification:

The subsections Demand and Connect cannot be defined simultaneously.
Desc defines a (localized) description of the required connection (in a text list).
Properties defines a list of properties which describe the properties required by the module IO (example: [Input24V, Digital]) It is possible to define several properties which allow to qualify the module IOs (example: module IOs which required only "Property1" and module IOs which required "Property1", "Property2", etc.).
Parent defines the Id of the device under which the channel should be connected. For "demanding" IOs, wildcard devices are also allowed as possible connection devices.

SEC std.DeviceGenerator
    SEC IOMapping : xOn
            SEC Demand
                    Desc := TL_Rooms.Role_RoomStandard_Lights;
                    Properties := [V24Output];
            END_SEC
    END_SEC
END_SEC