EasyBuilder Pro Tag Manager discovers 50 of 63 BACnet MS/TP objects because the remaining 13 use BACnet object types that the Weintek driver does not support. Independent discovery with YABE and the Contemporary Controls BACnet Discovery Tool confirms that the BACnet slave exposes all 63 objects, so the evidence points to driver object-type coverage rather than missing objects in the slave.
Affected configuration and observed result
| Item | Evidence |
|---|---|
| HMI | cMT-FHDX-220 |
| Engineering software | EasyBuilder Pro V6.10.01.252 |
| Network | BACnet MS/TP |
| Objects exposed by the slave | 63 |
| Objects shown by Tag Manager | 50 |
| Objects absent from Tag Manager | 13 |
The same 50-object result appears in the Tag Manager window and its exported CSV file. The two independent BACnet discovery tools find 63 of 63 objects and display their object names.
Root cause: unsupported BACnet object types
The 13 omitted objects are Character String Value or Positive Integer Value objects. These object types are not supported by the Weintek BACnet driver described in the evidence, so Tag Manager does not list them. A separate follow-up also identifies BitString Value objects as unsupported and therefore undiscoverable.
The absence of object names from both the Tag Manager interface and exported CSV is also confirmed. The evidence does not establish whether name omission is caused by the same object-type limitation or by a separate driver/export limitation, so treat it as a distinct compatibility issue.
Diagnostic and application decision
- Run Tag Manager discovery and record the displayed object count and exported CSV count.
- Discover the same BACnet slave with an independent BACnet discovery tool. If it returns all 63 objects while Tag Manager returns 50, the slave is exposing the objects.
- Classify the 13 missing objects by BACnet object type. Character String Value and Positive Integer Value explain the documented shortfall; also check for BitString Value objects because the evidence identifies those as unsupported.
- Decide whether the application can omit or remap the unsupported objects. If CSV, PIV, or BSV data is mandatory, select an interface or platform that supports those object types; discovery retries alone will not add unsupported driver coverage.
Verification criteria
Verify the diagnosis by matching every missing Tag Manager entry to an unsupported object type while confirming that another BACnet tool can read the same object from the slave. Do not treat the exported CSV as an independent discovery result because it mirrors the Tag Manager list. Before deployment, verify both required object values and object names through the selected HMI or interface.
FAQ
Why does Weintek BACnet Tag Manager find only 50 of 63 objects?
The missing 13 objects are Character String Value or Positive Integer Value objects, which the cited Weintek BACnet driver does not support. Tag Manager therefore excludes them from both its window and exported CSV.
Does Weintek Tag Manager discover BitString Value objects?
No. The evidence identifies BitString Value objects as unsupported by the driver and therefore absent from Tag Manager discovery.
Why are BACnet object names missing from the EasyBuilder Pro CSV?
Object names are absent from both the Tag Manager interface and exported CSV, although independent discovery tools display them. The evidence confirms the limitation but does not establish whether it shares the same cause as unsupported object types.