Controller Fieldbus
ToolsTalk 2 version 2.24 introduces Controller Fieldbus, which differs from a Fieldbus in one way: Controller Fieldbus is intended for controller-wide use and is shared by all Virtual Stations in a controller.
Controller Fieldbus provides a built-in signal-mapping feature by using Virtual Fieldbus. The purpose of Virtual Fieldbus is to map individual signal configurations into logical groups of signal configurations by using references. Virtual Fieldbus provides a point from where Virtual Stations are mapped to signal configurations. A signal configuration can be mapped to many Virtual Fieldbuses, which lets Virtual Stations share the same signal configurations.
Controller Fieldbus lets many Virtual Stations use the same incoming signal. This reduces the amount of required bandwidth, when compared with Fieldbus.
- Prerequisites to Using Controller Fieldbus
- Creating a Controller Fieldbus Configuration
- Creating a Signal Configuration in the Controller Fieldbus
- Creating a Virtual Fieldbus
- Mapping a Signal Configuration to One or More Virtual Fieldbuses
- Mapping a Virtual Station to a Virtual Fieldbus
- Changing the Controller Offset