0

Firstly I am new to this and I have tried googling for answer but figured it is best ask the experts.

There is a building management system (BMS) that is using BACnet protocol but my equipment logger only has Modbus TCP/IP. I understand that the market has a converter for this but I will like to know the concept.

  1. Modbus TCP/IP has registry values (e.g 40135) which is dedicated to a specific parameter reading. How does the converter read this registry value in the BACnet BMS? Do you have to specific this registry value in the converter software for the output at BACnet?

  2. In general, what should be input at the BACnet end to read the equipment parameter such as power received?

  3. In this situation, is the BACnet BMS consider the MASTER and the equipment as SLAVE?

I hope someone can take some time to clear my doubts on this. Will really appreciate it.

Thank you.

SunnyBoiz
  • 514
  • 1
  • 5
  • 14

2 Answers2

0

A couple of assumptions on my end regarding the setup:

  • Your equipment is acting as a "Modbus/TCP Slave" (i.e. it will respond to polls from a Modbus/TCP Master)
  • The converter then acts as a Modbus/TCP Master
  • And then the converter acts as a BACnet slave/server (or in BACnet terminology, a "B" device)
  • And your BMS system polls the converter as a BACnet master/client/"A" device

That is the normal setup. Then the converter device has the responsiblity to poll your equipment for the value from the Modbus register, and this is normally only a 16 bit integer, or in some cases, vendors pack a float into two 16 bit integers using a variety of byte-order and floating point formats. It is a mess. Nevertheless, the converter, if is a good one, will allow you to unpack the value into a float, and provision it with some BACnet specific metadata ("Properties") such as Units, BACnet Object Type, Object Instance, Reliability flags etc. etc. and make this new object discoverable by any BMS system.

More sophisticated converters can add other BACnet services, such as Change-of-Value (COV), Intrinsic Alarming, Trend Logging if desired. This is of course, dependent on the particular vendor.

Edward
  • 334
  • 1
  • 3
  • Hi Edward, thanks for the response. In this case, yes I believe my equipment is the Modbus/TCP slave as it is pushing out values to another device. In this situation, lets say if I am purchasing a converter, I suppose the converter should be a Modbus/TCP Master to BACnet slave type? – SunnyBoiz Aug 29 '17 at 00:28
  • The converter has to act as a Modbus/TCP Master and BACnet Server (to use correct terminology). But exactly what the vendor calls it may be ambiguous. For instance, the converter may be a Modbus Master and BACnet Server, but it is connecting a Modbus Slave to a BACnet Client. This configuration will be the most common though. – Edward Aug 30 '17 at 01:00
0

Just to add to what's already been said; a lot of the time - out in the field, there are gateway devices, that encompass the conversion process for you, so unless you're the one setting-up the BMS, you generally don't have to concern yourself with the conversion specifics.

If the device's 'Max(imum) ADPU Length' is set to 480, then the device is probably a Modbus device (/a Modbus device is probably sitting behind the gateway's/converter's (object) point).

DennisVM-D2i
  • 416
  • 3
  • 8