BACnet Tag Manager 50/63 Objects Discovered

BACnet Tag Manager 50/63 Objects Discovered https://forum.weintekusa.com/uploads/db0776/original/2X/d/dc8424f1fdeb40ab98b18f61dc1276825d72eae4.png
none 0.0 0

BACnet MS/TP Development Platform

  • HMI Model: cMT-FHDX-220
  • EasyBuilder Pro Version: V6.10.01.252
  • Serial Number: 2204105895

Hello Team Weintek -

In developing a BACnet MS/TP system we have encountered a problem in object (tag) discovery.

The BACnet MS/TP system requires 63 total objects (tags) to be discovered.

Problem: The EBPro Tag Manager only discovers 50 objects (tags), does not discover the remaining 13 objects. This shortfall is reflected in the Tag Manager window and in the exported *.csv file.

YABE and Contemporary Controls BACnet Discovery Tool
All 63 tags are discovered by YABE (Yet Another BACnet Explorer) and Contemporary Controls BACnet Discovery Tool (BDT).

In addition, both YABE and BDT successfully obtain and display the object (tag) names, which are lacking in the Weintek Tag Manager interface and in the *.csv tag file. It would be helpful, perhaps in the future, if the object names could be accommodated.

Screenshots:
EasyBuilderPro System Parameter Settings
63-object (tag) YABE discovery
50-object (tag) Weintek Tag Manager discovery

Q: What might be the causative factor limiting Tag Manager discovery to 50 out of 63 objects for the Weintek system, in contrast to YABE and BDT successfully discovering 63/63 objects?

Thank you.



The 13 tags that your BACnet MSTP slave has belong to one of the following BACnet objects:

  • Character String Value
  • Positive Integer Value

According to our connection guide, those two BACnet objects are not supported in the driver.
Therefore, the Tag Manager window won’t display any tags that are one of the two BACnet objects.

Thanks Tim.

Another needle in yet another haystack…

This one is going to hurt us. (In a major way.)

Tim, by way of follow-up and hopefully useful FYI to your team, we have also found that our BACnet Slave/Server BSV (BitString Value) objects are not discovered, for the same reason as not being supported by the Weintek BACnet driver.

That makes CSV, PIV and BSV BACnet objects unusable for our Weintek applications, which for us is a game killer. We now must seek a different platform for our BACnet systems.

Thank you again for clarifying.

Hi Jim, thought I would make a suggestion. Weintek has always supplied solutions and support whenever needed, however they could not support our BACnet project requirements either. We used a protocol converter from Control Solutions Minnesota. Communicated first try and great customer support. Discuss your application with them 800-872-8613…good luck.