Device structure in a project
This sample code shows device structure as it appears in a project.
projectRoot │ ├───devices │ │ output2.device │ │ adapter1.device │ │ input2.device │ │ controller2.device │ │ controller1.device │ │ adapter5.device │ │ input1.device │ │ │ └───types │ AB__1756_DI__C__1.device │ AB__1756_DO__O__0.device │ AB__1756_DI__I__0.device │ AB__1756_ENET_SLOT__O__0.device │ AB__1756_DO__I__0.device │ AB__1756_ENET_SLOT__I__0.device │ AB__1756_ENET_7SLOT__O__0.device │ AB__1756_OF8_Float__C__0.device │ AB__1756_OF8_Float__I__0.device │ AB__1756_OF8_Float__O__0.device │ AB__1756_NIO_Struct__C__0.device │ AB__1756_ENET_7SLOT__I__0.device │ AB__1756_DO__C__0.device └───topologies topology.device
Devices
Each device is stored as a
.device
file. All .device
files are checked into the version control system (VCS).
NOTE:
Some devices receive a system-generated name. The system-generated name must be a valid filename and must adhere to syntax rules for identifiers.
Module-defined types
Types are defined by the Device Catalog and are created when the device is created. Comments in the file and in the help content instruct users not to manually modify this data.
Topologies
Each topology is represented by its own
.device
file.Provide Feedback