Vantage InFusion

This driver was designed and tested with the Vantage InFusion Controller.

Design Center 4.0 Note:

With Design Center 4.0, Vantage has switched to using a secure connection to port 3010, rather than 3001, but you cannot switch to that port and expect it to work. Currently you must re-enable port 3001 in the project.

To reopen the ports~

Open DC and connect to the controller

Go To: System>Controller Settings>Network Settings

Open the Port Settings Tab

Add: Port / Type

2001 / UDP

3001 / TCP

Click OK

Execute a full program~

On the controller - Press and hold the Exit button @7 seconds or until the screen changes to "Security Access"
a. Mode: None

RTI should now communicate again.

Revision History

1.0 The original release of the driver

1.1 Added IP control. Added direct control of Loads, Tasks and T-Stats. All variables are mapped in the XP controller's driver tab

1.11 Fixed problems displaying all the VID maps in the Driver Tab

1.2 Adds 'Zones' to support the 1080HD video switcher
1.21 Passes VIDs over 1000 through to commands without remapping

1.22 Removes upper limit on VID mapping

1.3 Fixes a problem correctly triggering Task events. Adds dynamic naming and configuration (requires configuration changes). Added connection state variable. Added polling for initial conditions. Add Integration Designer APEX support.

1.31 Fixes that only adding buttons increase the device count. Now works on Loads, Temps, and Zones as well.

1.32 IP Port selection added to the configuration and the information about the switch to secure ports is added to the driver info

Variables & commands supported

Supports boolean variables for Button LED and Load States, as well as integer variables for Load Levels. Thermostat variables include Temperature (current and set points), Fan and Cooling modes. Also includes Vantage "Text" objects

Lighting commands are for Button presses (actually press and release), Load Level Set with ramp time, and Button LED Color with flashing. Temperature and mode switching for thermostats and TASK commands with triggers.

Events

The driver supports the following events:

From 1.0 Driver

Button LED On (Button On)

Button LED Off (Button Off)

Added in 1.1

Button Down

Button Up

Load On

Load Off

Thermostat Mode (Heat/Cool) change

Tasks

Added in 1.3

Connected

No Connection

VID Mapping

Vantage uses a continuous address (VID) space for all objects in a system. This means that any object could have virtually any VID. Earlier versions of the InFusion driver used a simple mapping system that swallowed up almost 8% of the shared driver variable space available in an Integration Designer based system file. In many systems this is no problem, but in larger systems this can cause a system to literally run out of space to store variables. Dynamic configuration (entering the number of each device type used) allows us to trim this down by only creating variables for VIDs we actually use, and dynamic naming (entering the name of any device used) makes using the mapping desirable by allowing you to program using the devices name rather than having to remember its VID.

Another advantage of this new system is that you can get feedback from ANY VID. Having 1000 as the highest VID was always an artificial limit needed to prevent the driver from using even more, perhaps all, of the available system variable space. You are still limited to 1000 VIDs total for each device type, but VIDs entered into the map can have any value.

This driver mapping system is still compatible with the earlier version. If you didn't make use of the VID map, you must make sure that you set the number of each type of device to match the highest used VID. Be aware that this will require considerably more system resources than using the map, and the variable and command lists will include all the choices up to that number

VID Mapping in 1.3

In this driver, VIDs are mapped by entering a name and VID for each device used in the system. There are 6 different VID categories in the driver. When a device is entered, its name appears in the variable list, as well as in the pull-down menu for the commands for that device type. It is no longer necessary to remember the VID numbers while programming. as programming is all done by name, although the VIDs are still displayed. The commands break the VIDs into groups of 100 devices to avoid having the pull-down get too long. You can use the 'Set All' command in every section, but that requires putting the device number (mapped number under 1000, VID over 1000), and remains for compatibility with earlier versions only) directly into he command, It is not guaranteed that these commands will be in all future versions of the driver so you should avoid using it.

Variables that give the name for these devices are also included.

Mapping VIDs in APEX

In APEX each Button, Load, Temp, and Zone can be added as a separate source, allowing you to create layers that use a specific device as a source. The devices get added and the Total Device count in the config gets adjusted automatically but you must still go into the driver config and enter the correct VID for that source. You can do that by editing them all together by selecting the driver itself in the workspace, or by selecting that Button, Load, etc. source in the specific room and then editing the parameters for that single device.

Events work similarly – you can edit all the events in the driver directly from the driver configuration, or go to that source and edit the events for that particular source in that room.

Tasks and Texts are not sources, but they will be added when any other source in the driver is added. In order to assign VIDs you must edit their names and VIDs from the Driver section in the Global Room.

Zones in the 1080HD

The Zones variables and commands were added to support the Vantage 1080HD video switcher. The driver has to add these VIDs to the status messages being returned by the controller so leave all unused zone VIDs set to 0