Issue
There are some BACnet devices that advertise support for services such as RPM, COV etc but malfunction when the service is used. An example of such device is the Johnson Controls TEC2627VVT which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list.
Product Line
EcoStruxure Building Operation
Environment
- BACnet
- Automation Server
- Enterprise Server
Cause
Some BACnet devices with inconsistent protocol implementation are unable to process some BACnet services such as RPM, COV etc.
Resolution
In versions 1.8.1 and onwards allows the user to create a rule under the BACnet interface to configure SBO not to use the service, the rule is then applied to particular BACnet devices specified by 'Vendor Identifier' and 'Model Name' creating in effect a black list of such devices.
After applying the hot fix follow these steps to create the rule:
Using a text editor such as 'Notepad' create a text file and enter the device's vendor ID (5) and model name (TEC2627VVT) followed by the rule (no-rpm, no-cov ) using the format seen in the screen shot below. (You can name the file anything you want),
Save the file to desired location on the PC.
Under the BACnet interface create a new 'Document' object in the 'Application' folder. NOTE: the object MUST be named 'service_blacklist' all low case.
Click 'Next' then import the text file created in step 1 and save the 'Document' object.
Reboot the server.
Once the device is on the black list, SBO will not send 'readPropertyMultiple' requests to the device, it will use only single 'readProperty'.
When disabling RPM and COV for a particular device the blacklist would be as follows.
(no-COV rule added in 1.8.1.23701 and included in the later full release builds)
