Introduction ............................................................................................................................................... 2
Assumptions ............................................................................................................................................. 2
Assumptions
1. Your firmware has B023, B021, B015, and B013 loaded.
2. You have taken DNP 3.0 configuration training.
3. You understand the basic architecture of the GE product.
The data processing application (DPA) in general reports data from the system point database memory
registers to a master. It can sort and filter data going back to the master by configuring point mapping
tables. A few examples of the many DPAs available are DNP 3.0, MODBUS, or IEC protocols.
Filtering: Selecting points you want to return to the master and skip the others.
Sorting: Grouping the points to be reported.
Remember: DPAs cannot own points; they are merely mapped to a DCA or DTA-owned point.
The data collection application (DCA) collects data from external devices and writes it to the system point
database memory registers. It can pass controls, time-synchronize devices, and poll as many devices as
connected for that protocol (you do not need a DCA per device). A few examples of the many DCAs
available are DNP 3.0, MODBUS, or IEC protocols.
The data translation application (DTA) does not communicate to devices or respond to master requests. It
be mapped to read points in the system point database memory registers and write to other points in the
system point database memory registers. Some examples of DTAs are Calculator, Mailbox, and
LogicLinx.
The system point database allows you to reserve the 16-bit memory registers in NVRAM on the D2X
platform and assign them to DCAs.
The system point database allows you to enter the number of points required by the device in the field, as
well as the points required by the B023-0 application (known as pseudo points).
Golden Rule #1
Each DNP 3.0 DCA (B023-0) version requires a different number of pseudo points. Please refer to your
version-specific configuration guide appendix on pseudo point configuration. If you enter an incorrect
number of pseudo points, you may encounter the following error in the wesmaint error log: Insufficient
wesdac <x> points expected <n>.
One real point (referring to figure 1 DNP 3.0 device number one)
Five per device pseudo points (referring to the configuration guide)
One real point (referring to figure 1 DNP 3.0 device number two)
Five per device pseudo points (referring to the configuration guide)
Golden Rule #2
Always configure your data link (B013) application before you configure the DPA and DCA applications
(B023-0 and B021-0) and finally your Bridgeman (B015) application.
The data link (B013) application is used to configure your RS232 / 485 communications ports with specific
parameters, and give that configuration a data link channel number.
The tables available to be configured in the data link are displayed below.
For the example in figure 1, we configure the Port Configuration table to have three ports (COM 1, 2, and
5). This reflects the physical hardware ports we want to use in our system. The end configuration looks
similar to the following screen:
Golden Rule #3
The numbers in the Config column are used as the data link channels in the Bridgeman (B015)
application LAT and RAT tables. For example, config 0 in the B013 Port Configuration table is the same
as data link channel 0 in the B015 LAT and RAT tables.
The DNP 3.0 DCA (B023-0) has three tables that can be configured to mirror your device in the field and
set up the desired polling scheme. This example focuses on the device setup including points and
addresses.
The first table to configure is the Device Point Map table. In the system point database memory registers,
we have set up four digital inputs and one analog input for both devices. Because both devices have
identical point counts and types, we only have to account for them once in the table. We map them twice
in the next step to allow for all points to be collected from both devices.
For information about the other fields in this table, please refer to your configuration guide and functional
specification.
This example focuses on setting the address and linking the Device Point Map table. For information
about the other fields in this table, please refer to your configuration guide and functional specification.
The following example shows how to configure the DNP 3.0 DCA (B023-0) application for the desired
addresses of the two devices in figure 1.
After the addresses are set, we link the Device Point Map table to this Device Configuration table using
the device configuration map at the end of this table.
Double-click the Device Configuration cell, and a mapping window opens. The mapping window allows
you to select the desired point configuration from the Device Point Map table in the First Point Record
cell.
Double-click the First Point Record cell, and select the points desired. In this case, we select both point
types to reflect the desired points in figure 1 of the first device.
Now that you have mapped the points for device 1, repeat the steps to map the points for device 2.
The last table in the DNP 3.0 DCA (B023-0) you need to configure is the DCA Configuration table. This
example focuses on the DNP 3.0 DCA addressing and linking the two logical devices (devices 1 and 2 in
figure 1) we created to that address.
To set the address to which the devices will report, in the case in figure 1, you enter address 10. This
gives the DNP 3.0 DCA an identifiable unique address.
To link the two logical devices we configured, navigate to theFirst Device Entry cell at the end of the DCA
Configuration table.
Opening Bridgeman
Configuring Bridgeman for the example in figure 1 requires that you set up the Local Application table
(LAT) and the Remote Application table (RAT). Think of these tables as one-way streets for information.
The LAT is the one-way street for information coming from your external device, through the
communication port data link channels defined in the data link (B013) to the DNP 3.0 application
addresses you configured.
The Application Address column contains the address you configure in your DNP 3.0 DCA and
DPA application.
The Data Link Name column contains the application number of the data link you are using. In
this example we are using RS232, which is the B013 application. For Ethernet, you use B052.
The Data Link Channel column links the config number from the B013 application. Refer to
golden rule # 3.
The LAN Address (hex) column contains the hexadecimal equivalent of the decimal number in
the Application Address column.
If you must configure any other cells in the table, please refer to your configuration guide.
The RAT is the one-way street for information coming from your DNP 3.0 application (B023-0, B021-0)
addresses, through the communication port data link channels defined in the data link (B013) to the
external devices.
The Application Address column contains the addresses of the external devices.
The Data Link Name column contains the application numbers of the data links you are using. In
this example we are using RS232, which is the B013 application. For Ethernet, you use B052.
The Data Link Channel column links the config number from the B013 application. Refer to
Golden rule # 3.
The LAN Address (hex) column contains the hexadecimal equivalent of the decimal number in
the Application Address column.
If you must configure any other cells in the table, please refer to your configuration guide.