Skip to content
Real Time Automation, Inc.Real Time Automation, Inc.
  • Menu
  • Login / Register
    • No products in the cart.

  • Cart

    No products in the cart.

  • Products
    • Accessories
    • Allen-Bradley Solutions
    • Books
    • Data Historian
    • Gateways
    • Barcode to A-B PLC
    • Legacy A-B Solutions
    • Security
    • Software
    • Training
  • Support
    • 435NBX / 490NBX Tools
    • 460 Tools
    • 515RTAENI Tools
    • ScanDr. Tools
    • Support Request Form
    • Data Mapping Templates
    • Hardware Drawings
    • Certifications
  • Technologies
    • AS-INTERFACE
    • BACnet® Overview
    • CANopen
    • CC-link
    • CIP Security
    • DeviceNet
    • EtherCAT
    • EtherNet/IP
    • IEC 61131-3
    • IEEE 1588
    • IO-Link
    • Modbus
    • Modbus TCP/IP
    • Modbus RTU
    • LonWorks
    • OPC UA
    • PROFINET IO
    • PROFIBUS
    • Single Pair Ethernet (SPE)
    • USB
    • XML
  • Learn
  • About
    • Real Time Automation
    • Our Promise To You
    • Testimonials
    • Our Founder
    • Highlighting Wisconsin’s Best Employees
    • Events
    • Careers
    • Press
    • Newsletter
  • Buy
    • Buy Direct
    • Distributors
  • Contact Us
    • 1-800-249-1612

  PRODUCT SELECTOR:

Connect Your:

To:

view
BACnet, Industrial Networking, RTA's Blog

BACnet Data Representation

Posted on March 4, 2015November 30, 2018 by John S Rinaldi
04
Mar

BA-data copyTo understand a standard what you have to do is to focus on the data representation. How a protocol represents data is key to its functionality. Once you understand the data representation, then it’s simply a matter of figuring out how that data is moved from Point A to Point B over whatever physical layer it uses.

In BACnet, the basic construct to organize data is an Object. An Object is really key to the operation of BACnet. Objects contain the physical data – temperatures, counts, rates and everything else captured by our automated devices. Groups of Objects represent the devices themselves. A flow meter can be represented by a group of Analog Input Objects and some Binary Objects. Objects are really at the center of BACnet technology.

BACnet has eighteen different objects in its specification. That list includes the most common objects, objects you’ll find in most BACnet devices: the Analog Input Object, the Analog Output Object, the Binary Input Object, the Binary Output Object and the Binary Value Object. It also includes some objects you might never run into in an entire career, like the Notification Class Object and the Loop Object.

Every BACnet Object is composed of a set of properties. The properties of an Object describe the Object to the network. BACnet properties include items like identification strings, configuration information, status values and diagnostic status. It is only through an Object’s properties that an Object is monitored and controlled.

Properties are very valuable to BACnet users. They provide information called meta-data. Meta-data defines and explains a data point. For example, you may have a temperature value of 25. Without meta-data, you won’t know if the refrigeration system is properly cold (25 Fahrenheit) or if the building roof is really hot (25 Celsius). Properties (meta-data) help to explain the characteristics of a value, what we call “present value” in BACnet.

Properties can tell you things like the scale, where the sensor is located, what kind of sensor is being used, or what kind of device is doing the measuring. Properties can be either Read only or Read-Write. The BACnet specification details what level of access an external device has to a BACnet property.

Properties are either required or optional. Required properties are properties that must be included in the Object. Network queries to the Object can always find and read those properties in an Object because, be definition, they have to be present. Optional properties are properties that CAN be included in the Object. It’s the choice of the device vendor to include or exclude an optional property.

Three properties, Object-identifier, Object-name, and Object-type are required to be present in every BACnet Object. Every Object must have these three objects plus any other Objects that are required for that Object’s Object-type. The type of Object and the type of device in which that Object resides determine which properties are required.

An Analog Input Object, for example, has the three objects required of every BACnet object, five other required objects plus seventeen optional objects:

Object_IdentifierRequiredAnalog Input #1
Object_NameRequired“AI 01”
Object_TypeRequiredAnalog Input
Present_ValueRequired68.0
Status_FlagsRequiredIn_Alarm Fault Overridden Out_Of_Service flags
Event_StateRequiredNormal (plus various problem-reporting states)
Out_Of_ServiceRequiredFalse
UnitsRequiredDegrees Fahrenheit
Update_IntervalOptional1.00 (seconds)
ReliabilityOptionalNo_Fault_Detected (plus various fault conditions)
DescriptionOptional“Outside Air Temperature”
Device_TypeOptional“10k Thermistor”
Min_Pres_ValueOptional-100.0 minimum reliably read value
Max_Pres_ValueOptional+300.0 maximum reliably read value
ResolutionOptional0.1
COV_IncrementOptionalNotify if Present_Value changes by increment: 0.5
Time_DelayOptionalSeconds to wait before detecting out-of-range: 5
Notification_ClassOptionalSend COV notification to Notification Class Object: 2
High_LimitOptional+215.0 Upper normal range
Low_LimitOptional-45.0 Lower normal range
DeadbandOptional0.1
Limit_EnableOptionalEnable High-limit-reporting Low-limit-reporting.
Event_EnableOptionalEnable To_Offnormal   To_Fault To_Normal change reporting.
Acked_TransitionsOptionalFlags indicating received acknowledgments for above changes.
Notify_TypeOptionalEvents or Alarms

I’ll have more on BACnet objects in next week’s article. John

This entry was posted in BACnet, Industrial Networking, RTA's Blog and tagged Analog Input Object, Analog Output Object, BACnet, Binary Input Object, Binary Output Object, Binary Value Object, Loop Object, Meta-data, Notification Class Object, Object, Properties.
John S Rinaldi

John Rinaldi is Chief Strategist, Business Development Manager and CEO of Real Time Automation (RTA). After escaping from Marquette University with a degree in Electrical Engineering, John worked in various jobs in the Automation Industry before once again fleeing back into the comfortable halls of academia. At the University of Connecticut, he once again talked his way into a degree, this time in Computer Science (MS CS). John is a recognized expert in industrial networks and the author of Four books: The Industrial Ethernet Book, OPC UA: The Basics, Modbus: The Everyman’s Guide to Modbus, and his latest, OPC UA - Unified Architecture: The Everyman's Guide to OPC UA.

Custom OEM Solutions
AHR EXPO 2015
Recent Posts
  • 06
    Apr
    What Modbus Doesn’t Do Very Well Comments Off on What Modbus Doesn’t Do Very Well
  • 30
    Mar
    Four Things Every Beginner Should Know About Modbus (Told by a Modbus Beginner) Comments Off on Four Things Every Beginner Should Know About Modbus (Told by a Modbus Beginner)
  • 23
    Mar
    How To Sound Smart (or at Least Literate) When Talking to Enginerds Comments Off on How To Sound Smart (or at Least Literate) When Talking to Enginerds
  • 16
    Mar
    Is Your Manufacturing Business Safe from Amazon? Comments Off on Is Your Manufacturing Business Safe from Amazon?
  • 09
    Mar
    What is a Captive Portal? Comments Off on What is a Captive Portal?
Categories
  • Accessories
  • ASCII
  • BACnet
  • Bluetooth
  • Books
  • CAN
  • CC-Link
  • Certifications
  • CIP
  • CoDeSys
  • ControlLogix
  • Customer Support
  • Data Highway
  • Data Logger
  • DeviceNet
  • DF/1
  • EtherCAT
  • Ethernet Physical Layer
  • EtherNet/IP
  • Industrial Networking
  • IO-Link
  • IoT
  • Linux
  • LONworks
  • MicroLogix
  • Misc.
  • Modbus
  • Modbus RTU
  • Modbus TCP
  • MQTT
  • MQTT
  • N2
  • NAT
  • Networking
  • OPC
  • OPC UA
  • Open Control
  • PCCC
  • PLC's
  • PROFIBUS
  • Profinet
  • PTO
  • Radios
  • Ring Topology
  • RTA's Blog
  • SCADA
  • Security
  • Siemens S7
  • Source Code
  • Stacks
  • Technology
  • Templates
  • Testimonial
  • Testing
  • Trade Shows
  • Training
  • Travels
  • Troubleshooting
  • Uncategorized
  • USB
  • VPN
  • Wireless
Tags
Allen-Bradley Allen-Bradley PLC Applications ASCII BACnet CAN CIP Client Cloud CompactLogix ControlLogix DeviceNet Ethernet EtherNet/IP Featured Event I/O Industrial Automation IoT Master MicroLogix Microsoft Modbus Modbus Book Modbus RTU Modbus TCP MQTT ODVA OPC UA OPC UA Book PLC Profibus Profinet ProfiNet IO Protocol Rockwell Automation RS232 RS485 security Server Siemens Slave TCP TCP/IP Windows XML

Need help? Call our Enginerd® Expert Support Team: 1-800-249-1612

PRODUCTS    |     SUPPORT    |     TECHNOLOGIES    |     LEARN    |     ABOUT    |     CONTACT US

BLOG    |     CAREERS    |     PRESS    |     EVENTS    |     NEWSLETTER    |     RMA

N26W23315 Paul Rd
Pewaukee, WI 53072

262-436-9299

Copyright 2021 ©Real Time Automation, Inc.®       Privacy Policy    |   Terms & Conditions
  • Products
    • Accessories
    • Allen-Bradley Solutions
    • Books
    • Data Historian
    • Gateways
    • Barcode to A-B PLC
    • Legacy A-B Solutions
    • Security
    • Software
    • Training
  • Support
    • 435NBX / 490NBX Tools
    • 460 Tools
    • 515RTAENI Tools
    • ScanDr. Tools
    • Support Request Form
    • Data Mapping Templates
    • Hardware Drawings
    • Certifications
  • Technologies
    • AS-INTERFACE
    • BACnet® Overview
    • CANopen
    • CC-link
    • CIP Security
    • DeviceNet
    • EtherCAT
    • EtherNet/IP
    • IEC 61131-3
    • IEEE 1588
    • IO-Link
    • Modbus
    • Modbus TCP/IP
    • Modbus RTU
    • LonWorks
    • OPC UA
    • PROFINET IO
    • PROFIBUS
    • Single Pair Ethernet (SPE)
    • USB
    • XML
  • Learn
  • About
    • Real Time Automation
    • Our Promise To You
    • Testimonials
    • Our Founder
    • Highlighting Wisconsin’s Best Employees
    • Events
    • Careers
    • Press
    • Newsletter
  • Buy
    • Buy Direct
    • Distributors
  • Contact Us
  • Login
Information Delivered to Your Inbox: Improve Your Industrial Automation Knowledge!

Ready to take your automation protocol knowledge to the next level? Subscribe to the Automation Education Email Series to learn the ins and outs of the top industrial protocols in a byte-size weekly format! Sign up now!

This website uses cookies. Some of these cookies make our site work, improve your experience using the site (for example, personalization) and help us improve our site (for example, analytics). By continuing to browse our site, you agree to our use of cookies. Learn more about RTA's privacy policy, including the use of cookies, here.