background image

Using i!-ConnectLinx

4

i!-ConnectLinx

To specify the name of an action, send a command to the i!-ConnectLinx virtual device describing 

the name of a given channel code. To specify the names of the actions in the above example, you 

would add some code like this:

DATA_EVENT[vdvCLActions]

{

  ONLINE:

  {

    (* Setup actions *)

    (* VCR Play *)

    SEND_COMMAND vdvCLActions,"'ADD ACTION-1,VCR Play"

    (* VCR Stop *)

    SEND_COMMAND vdvCLActions,"'ADD ACTION-2,VCR Stop' "

}

Once i!-ConnectLinx receives these commands, it stores this information in an XML file that can 

be used by i!-ConnectLinx compatible technologies to browse available actions.

In addition to specifying the name of an action, you can also supply a help string and a folder name. 

The help string helps a user understand the intent of the action more clearly. The folder name 

allows you to organize the actions in a tree view so that actions are more easily browsed.

Standard Actions

So far, i!-ConnectLinx has handled custom actions where each action is likely to be different from 

system to system. In the Using i!-ConnectLinx example, page 3, action 1 played the VCR. 

However, in another system, it is very unlikely that action 1 plays the VCR.

i!-ConnectLinx uniquely identifies each action list. Once an i!-ConnectLinx compatible technology 

programs itself to execute an action on a system, it also stores a copy of the system identifier from 

the action list. This identifier is sent to i!-ConnectLinx along with this action execution request. If 

the action identifier does not match the i!-ConnectLinx system that received the request, the action 

is not executed. This eliminates the ambiguity that may exist, since each system’s action 1 may be 

different.

i!-ConnectLinx supports standard actions. Standard actions are actions defined by AMX and 

supported natively by i!-ConnectLinx. When adding actions to 

i!-ConnectLinx, it is best to use the standard action if it is available. That way, the action can be 

executed regardless of which system the i!-ConnectLinx compatible technology was programmed 

to control.

The list of standard actions are listed in the 

i!-ConnectLinxStdFunctionList.xls

 file. The standard 

actions ID are the same is the channel number used to execute the action. For instance, VCR Select 

has an ID of 

1011

 so the programming to support this standard action is:

BUTTON_EVENT[vdvCLActions,1011]        (* VCR Select *)

{

  PUSH:

  {

    // Switch the projector and switcher to select the VCR

  }

}

To add a standard action, look up the action ID in the Standard Function List file, and send that in a 

send command to i!-ConnectLinx to tell it you want to support that action. To change the above 

example to standard action: 

1.

Lookup 

VCR Play

 and 

VCR Stop

 in the Standard Function List.

Continued

Summary of Contents for i!-ConnectLinx

Page 1: ...instruction manual integration Solutions i ConnectLinx...

Page 2: ...ceipt AMX DISCLAIMS ALL OTHER WARRANTIES EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE WITH REGARD TO THE AMX SOFTWA...

Page 3: ...d Operating Systems 1 Minimum PC Requirements 1 Installing i ConnectLinx 2 Using i ConnectLinx 3 Standard Actions 4 Action Arguments 6 Action Persistence and Distribution 7 International Issues Locali...

Page 4: ...ii i ConnectLinx Table of Contents...

Page 5: ...nectLinx module that handles exposing and executing action requests see the Module section on page 11 To support i ConnectLinx you simply include this module in your program define your actions and wr...

Page 6: ...Windows programs before going any further Click Next to proceed 4 In the Select i ConnectLinx Install Location dialog use the Browse button to navigate to a directory other than the default install di...

Page 7: ...s say you want the user to be able to allow the ability to play and stop a VCR Imagine you have two touch panel buttons that do these functions write code that responds to the pushes BUTTON_EVENT TP 1...

Page 8: ...technology programs itself to execute an action on a system it also stores a copy of the system identifier from the action list This identifier is sent to i ConnectLinx along with this action executio...

Page 9: ...x with the macro you want added For example DATA_EVENT vdvCLActions ONLINE Setup actions VCR Select and Play Record SEND_COMMAND vdvCLActions ADD MACRO vcr For a complete list of macros see the i Conn...

Page 10: ...alue from Each argument is numbered in the order they are added Arguments are added by using the ADD NARG ADD LARG ADD SARG and ADD EARG commands When an i ConnectLinx compatible technology requests a...

Page 11: ...ks to any URL with any file name in any folder In the above example the IT department might collect all the action list files and place them in the connectlinx directory of the company s web server Ea...

Page 12: ...wever this file is difficult to edit in a standard text editor so an XML file editor is recommended Alternatively the i ConnectLinxStdText xml file can be created using the i ConnectLinxEngineStdTextW...

Page 13: ...Min Max Step Default Adds a number argument to Action The Arg Name Argument Name is required The Min and Max define the limits for this argument in the range 32767 to 32767 The Step defines the minim...

Page 14: ...Parent Describes a child of a node Returned by GET NODE command ACTION ID Action Help String Folder Describes an action Returned by GET ACTION command NARG Action Arg Name Min Max Step Default Descri...

Page 15: ...LinxEngineMod Module definition code is displayed below DEFINE_MODULE i ConnectLinxEngineMod mdlCL vdvCLActions Where mdlCL is a unique module name i ConnectLinxEngineMod Module Parameter vdvCLActions...

Page 16: ...ve richardson TX 75082 USA 469 624 8000 800 222 0193 fax 469 624 7153 technical support 800 932 6993 033 004 2641 2 05 2005 AMX Corporation All rights reserved AMX the AMX logo the building icon the h...

Reviews: