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 | Associated Target and Index | Name

In version 2.1, you can now give system variables an associated target.  For example, you can set a variable as the first system variable associated with 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 and index. This allows you to reuse sequences more easily with different targets and variables.

For example: 

We make system variable 0's associated target Group 0, tag 0.

We make system variable 1's associated target Group 1, tag 0.

We make system variable 2's associated target Group 2, tag 0.

We can then reference this tag (and that we have inherited the target) for our delay.

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.

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

Variables with an associated target 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.