Topic: DMD0249 I/O Configuration |
|
I/O ConfigurationThe Top level of the I/O Configuration dialog displays a graphical view of the I/O Bases that are currently configured.
The top-most graphic will always be the base that contains the Do-more CPU and the I/O modules that are in that PLC system. Additional graphics for any Ethernet I/O Slaves will follow in the order they were added during the Ethernet I/O Master configuration.
|
|
I/O MastersExpanding the I/O Configuration will display the list of the I/O Masters that are currently in use to interface to the local and remote I/O bases in the system.
This list will contain one or more of the following depending on the PLC system in use and the CPU type in that system: BRX Local I/O Master is the backplane driver on BRX series CPUs.
DL205 Local I/O Master is the backplane driver for the Do-more H2 series CPUs.
Terminator Local I/O Master is the backplane driver for the Do-more Terminator series CPUs.
Ethernet I/O Master will be usable on Ethernet-equipped Do-more CPUs.
Modbus I/O Scanner will be usable on all Do-more CPUs.
EtherNet/IP Scanner will be available on Ethernet-equipped BRX CPUs.
|
|
I/O Configuration ModeSelecting any Local I/O Master from the list shows the following configuration parameter for the I/O Configuration Mode:
Auto (default) means that on power-up the CPU will scan the backplane for on-board I/O and I/O modules and automatically create an I/O configuration that matches the modules detected at that time.
Manual - Must Match mode means that on power-up the CPU will scan the backplane for on-board I/O and I/O modules and create an I/O configuration, then compare that with the I/O configuration in the currently open project. The I/O configurations must match before the CPU can go into Run mode.
Manual - Modules Optional mode means that on power-up the CPU will scan the backplane for on-board I/O and I/O modules and create an I/O configuration, then compare that with the I/O configuration in the currently open project. Any I/O modules that are detected must match the project's I/O configuration before the CPU can go into Run mode. BUT, having I/O modules in the project's configuration that ARE NOT detected in the PLC system will still allow the CPU to go into RUN mode.
|
|
CPU and Module Configuration OptionsExpanding any of I/O Master entries and selecting one of the PLC system items will display a graphical view of the PLC system including the CPU, the on-board I/O (if present), any installed I/O modules, and if the Ethernet I/O Master is enabled, each expansion I/O Slave is shown with the I/O they have installed.
Hovering the mouse cursor over the graphic will cause an orange outline to appear over important areas of the CPU, the on-board I/O, and the I/O Modules. Hovering the mouse cursor over any of the highlighted areas will generate a pop-up tool tip that will display the current configuration of the highlighted object. Left-clicking on any of the highlighted objects will display a pop-up menu of selections for configuring the selected object.
While the cursor is hovering over an I/O Module the pop-up tool tip will display the module's part number, where it's currently mapped, and its power budget consumption.
Right-clicking on the module will display a list of operations that can be performed on that module.
Depending on the PLC family that list will contain one or more of the following:
|
|
Manual I/O Configuration OptionsIf the I/O Master's Configuration Mode is set to Manual you can perform the following actions: (DL205 Systems Only) Manually Scan for Base Contents
How to Delete the Configuration for an Installed ModuleIf the I/O Master's Configuration Mode is set to "manual", right-clicking on the installed module's graphic and select Delete Module from the pop-up menu will remove the current I/O module definition from the I/O configuration.
(DL205 Systems Only) How to Mark a Module as OptionalIf the I/O Master's Configuration Mode is set to "manual", right-clicking on the installed module's graphic and select Optional from the pop-up menu will mark this module as Optional meaning that it will not be considered when the manual I/O configuration is compared to the I/O configuration read from the system during a Program-mode to Run-mode transition. The I/O space consumed by a module configured as optional is retained so that the I/O mapping does not change.
Note: I/O modules that are configured to be optional will be marked with the word "* Optional *" in yellow on the graphical view.
Note: The instruction HWINFO - Get Hardware Information can be used to detect the presence of I/O modules marked as 'Optional' as a way to programmatically control optional execution schemes.
How to Manually Add a Module in a BRX SystemBecause most of the BRX PLCs have some amount of on-board I/O, the exact model number of the PLC is required to present the correct amount and type of I/O in the system configuration. If you are online with the BRX PLC, the correct model number is select by Do-more Designer when the communication session was first initiated. But if you are offline, you must select the proper model number as part of the New Project definition. If for any reason you need to change the PLC type that was initially selected, you can right-click anywhere on the PLC graphic and the popup menu will contain an entry for Select CPU Subtype. Doing so will open the following dialog where you can select a different PLC model number:
I/O modules are physically added to the BRX PLC by connecting them to the expansion I/O connector on the right side of the base in the desired order.
Do-more Designer allows I/O Modules to be manually added to the I/O configuration by inserting a new I/O module between existing I/O modules or by adding a new I/O module at the end. This is done by hovering the mouse cursor over the left or right edge of the I/O Module where the new module will be inserted. This action will draw a pale-blue rectangle with an orange outline. Right-clicking on that rectangle will display the Insert Module dialog; follow on to display a selection of I/O Module classes; follow on from there to display a list of the I/O modules in that class. Select the desired module part number in the resulting list and the selected I/O module will be inserted at that point.
How to Manually Add a Module in a DL205 BaseThe DL205 system uses bases that have a fixed number of I/O slots. Right-clicking on an Empty Slot will display the Add Module dialog, which will then display a selection of I/O Module classes. Select the appropriate class, and follow on to display a list of the I/O modules in that class. Select the desired module by part number in that list and that module will be added to the I/O Configuration.
How to Manually Add a Module in a Terminator I/O SystemUnlike the DL205 system, a Terminator I/O system (using either a T1H-DM1/E CPU or a T1H-EBC100 as an Ethernet I/O Slave) does not have a backplane with a fixed number of slots where I/O modules are inserted. I/O modules are physically added to the system by connecting their base pieces together in the desired order.
Do-more Designer allows I/O Modules to be manually added to the I/O configuration by inserting a new I/O module between existing I/O modules or by adding a new I/O module at the end. This is done by hovering the mouse cursor over the left or right edge of the I/O Module where the new module will be inserted. This action will draw an empty rectangle with a blue outline. Right-clicking on that rectangle will display the Insert Module dialog; follow on to display a selection of I/O Module classes; follow on from there to display a list of the I/O modules in that class. Select the desired module part number in the resulting list and that I/O module will be inserted at that point.
How to Manually Change the GS Drive TypeRight-clicking on the GS Drive picture will display the Select Drive Type dialog, follow on to display a list of the valid GS Drive types. Select the desired GS Drive type from the list and the drive picture will change to reflect the drive selected type.
|
|
Handling Runtime Errors from I/O ModulesDo-more Designer provides the I/O System View to monitor errors from I/O modules when it is connected to the Do-more CPU. This section details what the Do-more CPU provides to programmers that need to handle runtime reporting of errors from the I/O Masters, and the I/O modules that are under the control of any of the I/O Masters. There is a three tiered reporting scheme that reports I/O Master and I/O module errors at increasing levels of definition. This allows the programmer to handle these error condition at whatever level is deemed appropriate. First Tier ReportingThe highest level of reporting is done through the System Bit $IOError (ST152), which is a single location that will be ON any time any of the I/O Masters in the system is reporting an error from one or more of its I/O Slaves or I/O modules. The Warning indicator will also be visible on the Status Bar, and the text "One or more IO masters are indicating a problem with a module - $IOError (ST152)" will be logged in the Warning Message section of the System Information dialog.
Second Tier ReportingThe middle tier of reporting is done through
the System structure $IOMasterErrors
(DST28), which is a DWord (32-bit) location that has one bit assigned
to each I/O Master in the system. The individual bit for an I/O Master
will be ON if any I/O module controlled by that I/O Master is reporting
an error. Bit 0 is assigned to the Local I/O Master.
Bit 1 is assigned to the Ethernet I/O Master.
Additional Bits are assigned to additional I/O Masters in the order that they appear in the I/O Configuration list.
Third Tier ReportingThe third tier of error reporting is done through a System structure for each I/O Master.
The Local I/O Master can manage up to 128 slots of I/O modules; its structure has the following four DWord (32-bit) locations, with one bit assigned to each slot:
The following Data View shows these elements reporting the following error conditions:
There is an I/O Error ($IOError is ON). The I/O Master that is reporting the error
is the Local I/O Master (bit 0 of $IOMasterErrors is ON). The I/O Module that is reporting the error is in slot 5 (bit 5 of LocalIOMaster.Slot0_31 is ON).
Additional Error ReportingThe final error reporting is the error information from the I/O module itself. The amount of this data, the type of data, and how that data is presented to the Do-more CPU depends on the I/O subsystem the module is part of, and the individual I/O modules.
For modules that report error information through status bits and / or alarm bits (for example the analog input modules), those bits are automatically placed in the Discrete Input range (X) at the same time the values for the actual I/O channels are placed in their proper memory locations - refer to the chart for Analog I/O Module Mapping and Discrete I/O Module Mapping for details on the number of alarm and status bits that are allocated for a particular module.
Details on what each of those bits indicates is module-specific; that information must be referenced from the Analog and Discrete I/O Module chapters of the Do-more H2 Series PLC Hardware User Manual (Automationdirect.com Part #: H2-DM-M) or the Do-more Terminator Series PLC Hardware User Manual (Automationdirect.com Part #: T1H-DM-M).
For debugging purposes, the I/O System View provides detailed error and warning information from I/O modules in the local base and from Ethernet I/O Slave devices and their I/O Modules.
|
|
See Also:
I/O Configuration
|
|