System Variables In BACnet

If your controller has a license for BACnet inputs and is updated to variant 7 (eg.2.0.1.7), you will be able to monitor and change system variables on your controller in BACnet.  These are Analog Value objects.

Point Name

In V2.1 Pro Controllers will integrate the name given to a system variable into the Object Name in BACnet.

Example of system variable naming scheme in BACnet

System variable number | Scope | Name

Point Numbers

Pre V2.1 controllers

48 system variables, starting from point number 336. 

V2.1 onwards

NON PRO - 48 system variables, starting from point number 336, unless scoped.

PRO - 148 system variables, starting from point number 336, unless scoped.

In version 2.1, you can now give system variables a "scope" by linking them to specific targets. For example, you can set a variable as the first one connected to Group 0.

This new feature makes your work easier. Instead of creating many sequences that each use a particular system variable, you can make one sequence that automatically uses the correct variable based on its target. This allows you to reuse sequences more easily with different targets and variables.

System variables created before 2.1 have no scope and start from point number 336. When you give a variable a scope, its point number will change.

Scoped variables use a new point numbering system. Each target can have up to 32 system variables. While there are many possible point numbers, you're still limited to using only 48 or 148 of these numbers, depending on your system.