INNPM12 Precision control

1. Input Channels and Transducer Supply:

• Thirty-two scanned inputs designed for 24 V.
• All channels share a common signal return.
• Transducer supply is derived from a fused common source.
• External voltage supply and fusing for groups less than 32 channels are possible, but return sides must be connectable.
• Galvanic isolation exists between the 32 channels and internal electronics.

2. Communication in Distributed Control Systems:

• Communication between different computers results in a load shared between the communication link and main CPUs.
• Consideration is crucial in designing a distributed control system.
• A key rule is to limit the frequency of information transfer to what the application truly needs.
• Event-controlled transfer, if secure, is preferred over cyclic transfer.
• Main CPU load due to communication varies with design.
• In MasterBus 300, two implementations exist in Advant Controller 450: one uses the main CPU, the other employs a dedicated slave processor on the submodule carrier (lower CPU load but higher cost).
• Similar information applies to MasterBus 300E.

3. Communication Implementations for MasterBus 300:

• Implementation 1:
  • Designation: MasterBus 300 (executed in main CPU).
  • Submodule carrier: SC510 (no slave processor support).
• Implementation 2:
  • Designation: MasterBus 300 (executed in slave CPU).
  • Submodule carrier: SC520 (with slave processor support).
• Note:
  • Application is unaffected by the selection.
  • Mixing MasterBus 300 (main CPU) and MasterBus 300 (slave CPU) in the same controller is not allowed.

4. Submodule and Submodule Carrier Placement:

• No restrictions on submodule and submodule carrier location in the controller subrack.
• Use a leftover slot on a submodule carrier if the carrier is suitable for the actual submodule (refer to Table 3-7 and guidelines).
• Cost-wise, submodule carrier SC510 is preferable.
• Cannot mix MasterBus 300 (main CPU) and MasterBus 300 (slave CPU) within the same controller.

5. Submodule Carrier Types and Mixing:

• Submodule Carrier SC510:
  • Preferable from a cost viewpoint.
• Submodule Carrier SC520:
  • Can be used but cannot mix two MasterBus 300 (main CPU) on the same SC520 carrier.
  • Mixing MasterBus 300 (main CPU) and MasterBus 300 (slave CPU) within the same controller is not allowed.

6. Submodule Carrier Types for MasterBus 300E:

• Submodule Carrier SC510:
  • Preferable from a cost viewpoint.
• Submodule Carrier SC520:
  • Can be used but cannot mix two MasterBus 300E (main CPU) on the same SC520 carrier.
  • Mixing MasterBus 300E (main CPU) and MasterBus 300E (slave CPU) within the same controller is not allowed.

By structuring the information in this manner, the article provides a clear and organized understanding of input channels, transducer supply, and communication implementations in distributed control systems.

INNPM12 Precision control