Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!
Modicon PAC Forum
A forum for topics related to the scope of Modicon PAC offers and ecosystem along the whole lifecycle: Modicon M580 and 340, EcoStruxure Control Expert, EcoStruxure Process Expert (Unity Pro) and more.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-29 07:48 AM
I have configured a BMENOR2200H with a server channel for receiving DNP3 binary input commands from an SEL RTAC.
Within control expert these DNP3 binary inputs from the remote client are defined as bytes within control expert. I want to be able to use the correct bit within the binary input DNP3 byte to indicate on/off from a pulsed command from the automation controller. Which bit within the byte do I use to indicate on/off status? Or which bit within the byte is going to change, and how, if the remote client sends a binary input high command (ex. TRIP bkr).
I currently have the DNP3 remote client byte going to a BYTE TO BOOL function block within control expert but have no way to test this expect during the installation. Is the use of the BYTE TO BOOL function block to use the DNP binary input from the remote client the correct use of this data? If not, how am I supposed to utilize the DNP3 binary input command from the remote client within the PLC logic in control expert?
Below is an example of how i currently have the DNP3 pulsed binary input commands from the remote client being used in the program.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-09-03 06:14 AM
Hi @Owen_Woodard,
Check my comments below:
The BMENOR module is configured as a DNP3 server and will receive the DNP3 Binary output commands from the DNP3 Client, which is SEL RTAC.
On the BMENOR server configuration, you have to choose DNP3 binary output points (BO) instead of DNP3 binary input points (BI) to receive the commands from the DNP3 Client, as mentioned below:
There are three possibilities for operating CROB (Control Relay Output Block using DNP3 Binary output points:
By default, the Latch ON/OFF and Pulse_ON are selected when you declare the Binary Output DNP3 point in BMENOR configuration. For Trip functionality, you have to choose the Pulse_Trip_Close option, as shown below:
Double Point Mode is selected by default for the Pulse Trip Close function in the BMENOR module, as shown below:
NOTE: The following snapshots show the DNP3 Server parameter.
For the Double Point Mode, you have to declare two DNP3 Binary Output points in the BMENOR module, which are grouped for the Pulse Trip Close functionality.
Two DNP3 BO points are declared as shown below:
Note: Two DNP3 points are declared, with point 0 acting as a closed function and point 1 acting as a trip function.
I did the test with the following setup:
The BO structure inside the ECE DDT is in byte format (by default, and this is fixed, and cannot be changed); we are interested in only the first bit of the byte.
It depends on the programmer how it's going to use this bit; you can also use the BYTE_TO_BOOL converter to extract this first bit. I also used BYTE_TO_BOOL for both points and mapped them into two digital points, such as Command for point 0 and Trip for point 1, as shown below.
Latch_ON:
Before triggering any command from the Client side:
Triggered the Latch_ON command from the Client, and it's reflected inside the ECE as shown below:
Latch_OFF:
Pulse_ON:
NOTE: The pulse duration depends on how you configured it during the point configuration.
I created the trending tool inside the ECE to show you the events when the value changes from 0 to 1 and then remains at 1 for the time duration that is configured in pulse duration. Once the timer expires, it reverts 1 to 0 as shown below:
Pulse_Close:
Pulse_Trip:
The snapshots below show the pulse for ON/Close and Trip as I issued these commands multiple times:
I hope the above explanation provides a fundamental understanding and guidance on using the BMENOR module to use DNP3 BO points with Trip and Close functionality.
I suggest you read the BMENOR user manual and the DNP3 standard to get more detailed information.
Best Regards,
MWS
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.