SATEC BFM136 BACNet Support Branch Feeder Monitor User Guide

SATEC BFM136 BACNet Support Branch Feeder Monitor

Every effort has been made to ensure that the material herein is complete and accurate. However, the manufacturer is not responsible for any mistakes in printing or faulty instructions contained in this book. Notification of any errors or misprints will be received with appreciation.
For further information regarding a particular installation, operation or maintenance of equipment, contact the manufacturer or your local representative or distributor.

REVISION HISTORY

Background

BACNet is a standard protocol for handling access to vendor specific devices. The BN protocol defines the behavior expected from controlling station and controlled devices. It is the responsibility of the controlling station to detect devices that support BN in its network and display all information provided by each device. It is the responsibility of vendor specific devices to implement support for the BN protocol. The standard defines a wide variety of types of support for the protocol. Each vendor decides what information it wants to share via the BN protocol. All types of data are defined by the standard. The vendor, after initial detection and identification with the controlling station, must return a list of ‘objects’ containing device specific data that it supports. Thereafter, the controlling station can retrieve any part of the list of supported objects. Since the types of data are defined by the standard, the controlling station is expected to display them accordingly. An essential aspect of the BN protocol is the requirement that each device, in addition to providing objects with values, it must describe, the meaning of the value provided. This includes object ID, name, type, status etc.

SATEC Support of BN

The BN protocol defines various modes and ‘profiles’ for official support of standard. SATEC supports the BSA profile:

• Read
• Write
• Execute (answer) Who-Is
• Initiate I-Am

And the following types of objects:

• Analog Input (AI)
• Command r/w

This the minimum to be classified as a standard BACNet device. It is need to be detected and allow access to “Analog Input” objects per a predefined, fixed list (see exact list in following chapters).
SATEC limits support to UDP over IP and does not support the routing mode (BBMD). Since the BFM supports only one IP address, shared by all sub-meters, the BN browser will detect only one BN instance per BFM device. By default, this will be the sub-meter with address ID #1. To access other SM’s, the user must set the Command object value and send to the BFM device. Thereafter, all requests for retrieval of AI objects will be directed to the corresponding SM.

Supported Objects

Following table shows mapping between AI objects and Modbus Point ID’s:

48

|

0x1612

| kW import predicted sliding window demand

49

|

0x1613

| kvar import predicted sliding window

demand

50| 0x1614| kVA predicted sliding window demand
51| 0x1618| kW export sliding window demand
52| 0x1619| kvar export sliding window demand
53| 0x161A| kW export accumulated demand
54| 0x161B| kvar export accumulated demand

55

|

0x161C

| kW export predicted sliding window demand

56

|

0x161D

| kvar export predicted sliding window

demand

57| 0x1700| kWh import
58| 0x1701| kWh export
59| 0x1704| kvarh import
60| 0x1705| kvarh export
61| 0x1708| kVAh total

User Instructions

• Connect BFM device to IP network. Make sure it has a unique IP address
• Open a BACNet browser/controller. It will discover all BFM BN devices that have a unique IP address
• By default, the browser will detect the first sub-meter for each device
• All AO objects read will belong to the first sub-meter
• For each device, the BN controller can retrieve data from each and every sub-meter by configuring the Sub-Meter Selector Command Object
• For an on-going process of retrieval of AO objects from all sub-meters, the controller should apply the following logic
  • Assume ‘index’ that can be assigned value between 1 and 36 (54 for BFMII)
  • Start with index assigned value 1
  • Set “Present Value” of the Sub-Meter Selector to value of ‘index’
  • Retrieve all AO’s from the sub-meter (and store or display them)
  • Increment index by 1 (if index > 36(54), set index to 1)
  • Go to step ‘i’

Pictures of Demonstration with Freeware BN Browser, YABE

Open browser and choose network.

YABE detects all devices supporting BN on network. Choose one and YABE will bring it’s list of AI objects:

Choose the command object and change from 1 to any other ID of sub-meter defined in BFM and now all the AI objects will change accordingly.

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>