BB2-7030 User Guide – Rev. 1.0
Page 40
11.
Using
the
BB2
7030
02
as
an
SNMP
Server
(Agent)
The BB2-7030-02 can act as an SNMP agent or server. You select which BACnet objects are to
show up in the MIB, and the MIB is created dynamically as you fill out the list of objects. Once
the MIB is created, any standard v1 or v2 SNMP manager can access the data. Integer data is
most universally recognized by SNMP. Floating point support is available in the BB2-7030;
however, floating point is not standardized and you should test compatibility.
IMPORTANT:
The definition of Input versus Output object is from the perspective of
the BACnet network. Therefore your SNMP client should Write to Input objects to provide input
to BACnet, and Read from Output objects to receive output from BACnet. Attempting to write a
BACnet Output object from SNMP will not work properly. You must think of your SNMP
manager as the physical I/O being accessed from BACnet. If you want to make your
SNMP manager write to an Output object on another BACnet device, use the BACnet client
mapping to translate a local Input to remote Output on the BACnet side.
Rule number simply tells you where you're at on the list of the local SNMP Agent's OID maps.
Click "next" and "prev" to scroll through the list. To advance directly to a specific map, enter the
desired number in the "Showing" box, then click Update.
This page enables SNMP Get/Set to objects indicated on the above map list. The available local
OID's are assigned automatically. You may select which local BACnet objects are mapped to
these OID's. The only data type supported via the internal SNMP Agent is signed integer,
therefore you must use scaling to provide real data as integers. This is an inherent limitation of
SNMP which does not have any universally accepted method of transmitting floating point data.
Internal data is multiplied by the scale factor when read by your remote SNMP manager (client).
Data written by your SNMP client is divided by the scale factor before being stored internally.
