Add Module (Generic 1756 Module): In the I/O Configuration, add a new 1756-MODULE.
Set connection parameters:
Name: Name the module, for example "MVI56PDPMV1".
Comm Format: Select "Data INT".
Slot: The actual slot where the input module is located.
Input Assembly Instance: 1; Output Assembly Instance: 2; Configuration Assembly Instance: 4。
Input/Output Size: Fill in the correct I/O block size based on the selected mode (LEGACY or FLEX) and the configuration in the PCB.
RPI (Requested Packet Interval): Set the RPI time according to the application scenario. For local racks, if using FLEX mode, it can be set to 750ms (as IOT commands will take over control). For other situations, a value between 5-750ms can be set.
6.2 Import AOI (applicable to ControlLogix v16 and above)
After configuring in the PCB, export L5X file.
In RSLogix, create a new program or open an existing program.
Right click on "Routines" under "MainProgram", select "New Routine", and create a new routine.
In the new routine, right-click on a blank step, select "Import Rung", and then choose the previously exported one L5X file.
RSLogix automatically imports all necessary user-defined data types, controller labels, and cascade logic for calling AOI.
Adjust communication path: Check the imported AOI cascade to ensure that the I/O connection variables it references (such as Local: 1: I.Data and Local: 1: O.Data) match the module names and slots defined in your "I/O Configuration".
7. Data exchange and email messaging
The data exchanged between modules and processors is divided into three categories: process data, status data, and email messages.
7.1 Process Data Exchange
LEGACY mode: Process data is directly exchanged through fixed input/output data blocks. Input block IDs 1-4 contain PROFIBUS input data, while output block IDs 1-4 contain PROFIBUS output data.
FLEX mode: Process data is transmitted through variable backplane I/O blocks. The number of data blocks depends on the total data volume of PROFIBUS and the size of each backplate. The module will automatically divide the data into multiple blocks and distinguish them based on block IDs.
7.2 Email Messaging
Email messages are a mechanism used to exchange non cyclic data (such as diagnostics, parameter configuration, control commands) between processors and modules. It supports MSAC1 and MSAC2 services for PROFIBUS DPV1.
Email message in FLEX mode: The processor uses the MSG instruction to send a "Set Attribute Single" request to the module to trigger a mailbox function. After the module is processed, it will lock a bit in the input block to notify the processor that the response can be read. The processor then sends the 'Get Attribute Single' instruction to retrieve the response. Example commands include: Get Slave Diagnostics, Get Live List, Perform Acyclic Read/Write, etc.
Email messages in LEGACY mode: Use a special output block (ID 100-109) to send requests, and the module responds with an input block of the same ID, coordinated with status and control words.
7.3 Diagnosis and Status Data
The module provides rich diagnostic information, which can be viewed in the following ways:
LED indicator lights: The OK, BP ACT, APP STOP and other LED indicator lights on the front panel of the module provide a visual display of the basic operating status of the module. The PROFIBUS status LEDs (TKN HLD, DBASE STAT, MSTR STAT, COM STAT) reflect the status of the PROFIBUS network.
PCB diagnostic window: Connect to the module via serial port or CIPconnect to enter the online diagnostic menu of the PCB. This menu provides functions such as viewing module status, input/output databases, and PROFIBUS slave status lists (SLAVE CFG LIST, TRANSFER LIST), making it a powerful tool for network debugging.
RSLogix Controller Label: The imported AOI contains status data labels (such as MVI56PDPMV1. Status), which can be viewed directly in the RSLogix Controller Label Monitor. Among them, arrays such as FB_Slave_Cfg_List and FB_Slave_xfer can accurately display which slave has been configured and which slave is exchanging data with the master.
8. PROFIBUS comDTM
In addition to PCB, ProSoft also provides PROFIBUS comDTM (Device Type Manager). This is a software component based on FDT (Field Device Tool) technology, allowing users to configure, monitor, and diagnose modules in a unified framework application (such as PACTware, FieldCare). ComDTM communicates with modules through serial ports or Ethernet (CIPconnect), providing users with a more graphical and intuitive configuration environment.
9. Fault diagnosis and troubleshooting
When there is a problem with the system, a systematic diagnostic process is crucial.
Preliminary inspection: Confirm that all hardware connections are secure and cables are intact. Especially for PROFIBUS cables, whether the installation of shielding layers and terminal resistors complies with regulations.
Observing LED status: As mentioned earlier, LED status is the first-hand information for quickly locating problems. For example:
COM STAT LED is green but flashing: This indicates that the master station is communicating with at least one slave station, but not all configured slave stations.