Communication Protocols

Functions and Protocols

The BMENOR2200H module provides in-rack support for these functions and protocols in an M580 architecture:

RTU protocols	DNP3 NET (client or server) NOTE: When the module works as a DNP3 client, the number of connected servers affects the module performance (web page access, module start-up and data exchange through the backplane).
RTU protocols	Modbus TCP (client or server)
Main RTU protocol features	time synchronization through a protocol facility or SNTP
	data synchronization on demand of the SCADA
	balanced and unbalanced transmission mode
	event management with time stamping (Sequence of Events, SoE)
	event queue stored in RAM memory (up to 150,000 events)
	events data backfill to SCADA application via protocol facility
	event routing
	report by exception data exchanges
	unsolicited messaging data exchanges
	DNP3 secure authentication SAv2 and SAv5 with pre-shared key
	protocol setup via the DTM
Other built-in functionality	web server for security set-up and remote diagnostic
Other built-in functionality	advanced TCP/IP networking: SNTPv1 client, HTTPS server, and SNMP agent.

Limitations

NOTICE

UNINTENDED EQUIPMENT OPERATION

Use different address values for each session in a channel or for each section in a session.
Use successive DB mapping starting at 0 in the DNP3 protocol.
Do not configure the DNP3 client to control a point that is not configured in the DNP3 server point mapping.

Failure to follow these instructions can result in equipment damage.

The BMENOR2200H module does not support multiple RTU protocols instances. Only one instance at a time of the DNP3 RTU can be launched to work with Modbus TCP.