Using the BACnet Configuration of a Project Configured With a Previous Version of PcVue 

From version 11.2 onwards, PcVue uses new, enhanced, technology for its BACnet data acquisition driver. The new technology enables many features that were not previously available, including B-AWS compliance, and provides a way forward for any further developments to the BACnet standard.

The main difference that the project developer will notice is that the previous technology used an external service that had to be configured separately (mainly for the BACnet network interface).

Therefore, if you have a project using BACnet that was created using a version earlier than 11.2, and you want to run it with a newer version, you should first make sure you configure:

  • The BACnet/IP Network Interfaces, including the BACnet device exposed by PcVue,
  • BACnet settings such as the APDU timeout, the scan timeout and the process identifier.

See Configuring a BACnet/IP Network Interface and BACnet Settings for more information.

All other configuration items including Variables mapping, Alarm and Event mapping as well as Notification Class configuration are retained.

Starting with version 11.2, the WebScheduler takes advantage of the enhancements to the configuration of BACnet Schedules, Calendars and Enumerated Associated Labels. In particular, the manual editing of the Schedules.dat file is no longer necessary, it is replaced by the configuration performed within PcVue.

Please refer to the topic WebScheduler configuration overview for more information.