FBx Series DNP3 Driver Tag

FBx Series DNP3 driver uses the standard DNP3 communication protocol to retrieve history logs and audit information using file operations. It requires a child DNP3 driver to operate. This driver typically follows the following process:

  1. A read is requested by the user or triggered by another tag such as a polling tag. The request specifies the file type (such as history or alarm & event) and an instance number that corresponds to your Emerson specification tables.

  2. The FBx Series DNP3 driver references the most recent sequence read (the most recent point of relevant data retrieved) and compares it to the latest sequence available.

  3. The FBx Series DNP3 driver returns a file for each outstanding sequence containing the requested data in binary format

If "Reset Sequence" is selected, the driver will start from sequence 0 and read all available sequences up to the newest sequence available.

RPC Service

This FBx Series driver typically does not have its own dedicated RPC (Remote Procedure Call) service. Instead, it relies on a DNP3 driver (child). When configuring server lists for your FBx Series DNP3 driver communications the sever list must be based on the name of the child DNP3 tag.

Configure the flow computer to be compatible with VTScada's FBx Series DNP3 driver tag. Consider the following settings:
* Disable "Require Login" in the flow computer.
* When configuring FloBoss DNP3 objects for a meter in the flow computer, select components with matching numbers. ie. In the Emerson configuration field tool, if Tag = DP Mtr_1 then Station Assignment = Station_1 and so on.
For more information, refer to your Emerson manual and application.

Troubleshooting

  • Cannot write from the VTScada application to the RTU
    Double-check that your flow computer settings do not have "Require Login" enabled.

FBx Series DNP3 Tag Widgets