The Lutron Machine driver allows the FieldServer to transfer data to and from devices over RS232 using Lutron eLumen protocol. The FieldServer can emulate either a Server or Client,
although the Lutron Machine driver is only available in Client configuration. Any Server drivers
are for FieldServer testing purposes only.
Max Nodes Supported
FieldServer Mode Nodes Comments
Client 1
Server 1
The Lutron Grafik Machine Zone/Area Machine driver, hereafter simply referred to as the Lutron
Machine driver, provides a BACNet IP interface to a Lutron eLumen panel. The driver can be
configured to represent zones or areas as used in the Lutron eLumen panel. The FieldServer
acts as both Client and Server to provide BACNet objects to an external BACNet Client. In
Server mode, the FieldServer collects data from the eLumen panel and holds the data ready for
reads from an external BACNet Client. In Client mode, the FieldServer executes pre-defined
commands on the eLumen panel, for example, running scripts.
Only one Lutron Machine driver Client node is able to be
connected to a Lutron eLumen panel.
One BACNet IP node provides an upstream interface to the
Lutron eLumen panel.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4. Configuring the FieldServer as a Lutron Machine Client
For a detailed discussion on FieldServer configuration, please refer to the FieldServer
instruction manual. The information that follows describes how to expand upon the factory
defaults provided in the configuration files included with the FieldServer (See “.csv” sample files
provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Lutron eLumen panel.
4.1. Data Arrays/Descriptors
The configuration file tells the FieldServer about its interfaces, and the routing of data
required. In order to enable the FieldServer for Lutron Machine communications, the driver
independent FieldServer buffers need to be declared in the “Data Arrays” section, the
destination device addresses need to be declared in the “Client Side Nodes” section, and
the data required from the Servers needs to be mapped in the “Client Side Map Descriptors”
section. Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the
default.
4.4.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name
Data_Array_Name
Data_Array_Offset
Function
Name of this Map
Descriptor
Name of Data Array
where data is to be
stored in the
FieldServer
Starting location in Data
Array
Function of Client Map
Descriptor
Up to 32 alphanumeric
characters
One of the Data Array
names from “Data Array”
section above
0 to maximum specified in
“Data Array” section above
ARCO, AWT, RDBC,
Passive_Client
4.4.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fetch data from
Grafik_Command
Specifies the command that will be
sent to the eLumen.
One of the node names
specified in “Client Node
Descriptor” above
Area Machine:
run_script_AB
area_sts_offscene
sel_scene_in_area
run_script_multi
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Zone Machine:
run_script_AB
zone_intensity
fade_zone
run_script_multi
zone_intensity
sys_var_val_bin
sys_var_val
Name of Data Array that contains a
DA_Lut_List
list of parameters needed to
A Data Array name.
execute the command.
DA_Lut_List_Offset
The offset into the DA_Lut_List
Data Array from where the list data
is to be used.
0 to the maximum offset
into the DA_Lut_List
Data Array.
Name of Data Array that contains
DA_Lut_Parms
parameters needed to execute the
A Data Array name.
command.
DA_Lut_Parms_Offset
The offset into the DA_Lut_Parms
Data Array where the driver will
retrieve the parameters.
0 to the maximum offset
into the DA_Lut_Parms
Data Array.
Area GRAFIK system area number 0 – 511
Sys_var GRAFIK system variable number 0 – 65535
Zone GRAFIK system zone number 0 – 511
Length of Map Descriptor. The
Length
length is an indication of the
number of data elements this Map
Descriptor is responsible for
updating. It is used in the overall
points calculation of the
See example Map
Descriptors for individual
lengths per Map
Descriptor.
FieldServer.
The length of the Data Array
Multi_Scripts_Length
specified under DA_Lut_List when
used with Grafik command:
1 – 10,000
run_script_multi
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.4.4. Map Descriptor Example 1 - Binary Output (Zone and Area Machine)
A write to the Binary Output Data Array which is shared by a BACNet IP Map Descriptor will execute one of two scripts on the
eLumen panel. The script numbers corresponding to binary inactive (0) and active (1) are specified in the Data Array specified by
“DA_Lut_List” from offset specified by “DA_Lut_List_Offset”. Script numbers range from 0 to 65535.
The Data Array specified under “DA_Lut_List” must be preloaded with script numbers as shown below:
//================================================================================
// Binary Output Scripts Setup
//
// All values are in decimal (0 - 65535)
// ScriptA in even locations, ScriptB in uneven locations, values in Preload_Data_Value
// ScriptA will be run when writing zero into the Object ID
// ScriptB will be run when writing non-zero into the object ID
4.4.5. Map Descriptor Example 2 - Binary Input (Zone Machine)
A read from the Binary Input Data Array which is shared by a BACNet IP Map Descriptor will return the relay state for the given zone.
The Lutron Machine Map Descriptor regularly polls the eLumen panel to retrieve the value of zone intensity. The value of each
BACNet object presenting Binary Output is inactive if the intensity is zero and active if the intensity is non-zero. Zone numbers range
from 0 to 511
The ARCO function is the same as RDBC except that the length of the Map Descriptor is taken as the number of zones to poll. The
start zone number is specified under the “Zone” Map Descriptor field. More than one ARCO Map Descriptor may be used to poll two
series of zone numbers, eg. from 5-10 and from 300-340. ARCO Map Descriptors with Length 1 perform the same function as
RDBC Map Descriptors with the same length.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.4.6. Map Descriptor Example 3 - Binary Input (Area Machine)
A read from the Binary Input Data Array which is shared by a BACNet IP Map Descriptor will return the scene-on state for the given
area. The Lutron Machine Map Descriptor regularly polls the eLumen panel to retrieve the scene-on state for the given area. The
value returned by the BACNet object is inactive (0) if the off scene is selected and active (1) if any other scene is selected. The off
scene numbers range from 0 to 65535 and are preloaded in the Data Array specified under “DA_Lut_List”.
The ARCO function is the same as RDBC except that the Map Descriptor length is taken as the number of areas to poll. The start
area number is specified under the “Area” Map Descriptor field. More than one ARCO Map Descriptor may be used to poll two series
of area numbers, eg. from 5-10 and from 300-340. ARCO Map Descriptors with Length 1 perform the same function as RDBC Map
Descriptors with the same length.
The Data Array specified under “DA_Lut_List” must be preloaded with scene numbers as shown below:
//================================================================================
// Binary Input Scenes Setup
//
// All values are in decimal ( 0 - 65535 )
// Insert the off-scene number in the preload_data_value field
Preloads
Data_Array_Name , Preload_Data_Format , Preload_Data_Value , Location
4.4.7. Map Descriptor Example 4 - Analog Output 1 (Area Machine)
A write to the Analog Output Data Array which is shared by a BACNet IP Map Descriptor will command an area to a preset scene on
the Lutron eLumen panel. Scenes range from 0 to 65535 and area numbers range from 0 to 511
The area field must be used to indicate the start area number that will be associated with the first element of the Data Array specified
under Data_Array_Name. Area numbers increase with the Length field in association with increasing offset into the Data Array.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.4.8. Map Descriptor Example 5 - Analog Output 1 (Zone Machine)
A write to the Analog Output Data Array which is shared by a BACNet IP Map Descriptor will command a zone on the Lutron eLumen
panel to the written intensity. Intensities are written as a percentage value (0 to 100%).
The zone field must be used to indicate the start zone number that will be associated with the first element of the Data Array
specified under Data_Array_Name . Zone numbers increase with the Length field in association with increasing offset into the Data
Array.
Fade and Delay times per zone must be preloaded into the Data Array specified under “DA_Lut_Parms”:
//================================================================================
// Analog Output1 Settings Setup
//
// All values are in decimal ( 0 - 65535 )
// Fade time in even locations, Delay time in uneven locations
// Fill in time values under Preload_Data_Value
4.4.9. Map Descriptor Example 6 - Analog Output 2 (Zone and Area Machine)
A write to the Analog Output Data Array which is shared by a BACNet IP Map Descriptor will execute one of multiple scripts on the
Lutron eLumen panel. The value written into the Analog Output Data Array is used as an offset into the Data Array defined under
“DA_Lut_List” to retrieve a script number. Script numbers range from 0 to 65535.
The Multi_Scripts_Length field is used to indicate the maximum size of the Data Array specified under Data_Array_Name. One Map
Descriptor per object must be defined with a Multi_Scripts_Length value of 1 or greater.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
The script numbers per BACNet object element need to be preloaded into the Data Arrays defined under “DA_Lut_List”.
//====================================================================
// Analog Output2 Settings Setup
//
// All values are in decimal ( 0 - 65535 )
// Specify up to 10 scripts for each Object ID by editing Preload_Data_Value
Preloads
Data_Array_Name , Preload_Data_Format , Preload_Data_Value , Location
4.4.10. Map Descriptor Example 7 - Analog Input (Area Machine)
A read from the Analog Input Data Array which is shared by a BACNet IP Map Descriptor will return the last scene selected in a
given area on the Lutron eLumen panel. The Lutron Machine Map Descriptor regularly polls the Lutron eLumen panel to retrieve the
scene numbers.
//================================================================================
// Analog Input Settings Setup
//
// All values are in decimal ( 0 - 65535 )
// Insert a first available scene number under the Data_Array_High_Scale field for each Object ID or
// use the scale fields as desired to scale scene numbers.
// Object IDs are contiguous
The ARCO function is the same as RDBC except that the length of the Map Descriptor is taken as the number of areas to poll. The
start area number is specified under the “Area” Map Descriptor field. More than one ARCO Map Descriptors may be used to poll two
series of area numbers, eg. from 5-10 and from 300-340. ARCO Map Descriptors with Length 1 fullfil the same function as RDBC
Map Descriptors with the same length.
Data_Array_
Offset,
Function, Node_name, Data_Type, Object_
ID,
Length, Relinquish_Default, Data_Array_
Low_Scale,
Data_Array_
High_Scale,
Node_
Low_Scale,
Node_
High_Scale
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.4.11. Map Descriptor Example 8 - Analog Input (Zone Machine)
A read from the Analog Input Data Array which is shared by a BACNet IP Map Descriptor will return the intensity to which a given
zone is set on the Lutron eLumen panel. The Lutron Machine Map Descriptor regularly polls the Lutron eLumen panel to retrieve the
zone intensities. The intensity value returned is scaled to a percentage value (0 to 100%). Zone numbers range from 0 to 511.
The ARCO function is the same as RDBC except that the length of the Map Descriptor is taken as the number of zones to poll. The
start zone number is specified under the “zone” Map Descriptor field. More than one ARCO Map Descriptors may be used to poll two
series of zone numbers, eg. from 5-10 and from 300-340. ARCO Map Descriptors with Length 1 fullfil the same function as RDBC
Map Descriptors with the same length.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.4.12. Map Descriptor Example 9 - Multistate Output (Zone and Area Machine)
A write to the Multistate Output Data Array which is shared by a BACNet IP Map Descriptor will execute one of multiple scripts. The
multiple scripts are specified in the Data Array defined under “DA_Lut_List”. The value written into the Multistate Output Data Array
is used as the offset into the Data Array defined under “DA_Lut_List” to retrieve a script number from the Data Array. Script numbers
range from 0 to 65535.
The Multi_Scripts_Length field is used to indicate the maximum size of the Data Array specified under Data_Array_Name. One Map
Descriptor per object must be defined with a Multi_Scripts_Length value of one or greater.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
The scripts per object element must be preloaded into the Data Array defined under “DA_Lut_List”:
//=====================================================================
// Multistate Output Scripts Setup
//
// All values are in decimal ( 0 - 65535 )
// Specify up to 10 scripts for each Object ID by editing Preload_Data_Value
4.4.13. Map Descriptor Example 10 - Binary Value (Zone and Area Machine)
A read from the Binary Value Data Array which is shared by a BACNet IP Map Descriptor will return the current value of a
system variable in the Lutron eLumen panel. The value returned is inactive (0) if the system variable is zero and active (1) if
non-zero. The Lutron Machine Map Descriptor regularly polls the Lutron panel to retrieve the system variable values. A write
to the Binary Value Data Array will set the system variable to 255 on active (1) write or to zero on inactive (0) write.
The ARCO function is the same as RDBC except that the length of the Map Descriptor is taken as the number of system variables to
poll. The start system variable number is specified under the “Sys_Var” Map Descriptor field. More than one ARCO Map Descriptor
may be used to poll two series of system variable numbers, eg. from 5-10 and from 300-340. ARCO Map Descriptors with Length 1
fullfil the same function as RDBC Map Descriptors with the same length.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.4.14. Map Descriptor Example 11 - Analog Value (Zone and Area Machine)
A read from the Analog Value Data Array which is shared by a BACNet IP Map Descriptor will return the current value of a system
variable in the Lutron eLumen panel. The variable values range from 0 to 255. The Lutron Machine Map Descriptors are regularly
updated with system variable values from the active Binary Value Map Descriptors. A write to the Analog Value Data Array will set
the system variable to the written value.
The Passive_Client function is used to prevent double-polling the Lutron eLumen panel for system variables. The Analog Value Map
Descriptors should be set up identical to the Binary Value Map Descriptors in terms of the Sys_Var and Length fields to ensure
system variable values will be stored correctly.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com