A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-97 Lutron Machine
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
FS-8700-97_Lutron_Machine Manual
Page 3 of 11
1.
Lutron Machine Description
The Lutron Machine driver allows the FieldServer to transfer data to and from devices over RS-
232 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
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.
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.
FS-8700-97_Lutron_Machine Manual
Page 4 of 11
2.
Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART #
Description
FS-8915-10
FS-8917-02
FS-8700-97
UTP cable (7 foot) for RS-232 use
RJ45 to DB9F connector adapter
Driver Manual.
2.2.
2.2.1.
Provided by the Supplier of 3rd Party Equipment
Hardware
Part #
Description
Lutron eLumen Panel
2.2.2.
Required 3rd Party Software
An external BACnet IP Client to interface to the Lutron Machine on the FieldServer.
2.2.3.
Required 3rd Party Configuration
BACnet IP Client must be set up to access FieldServer over the network.
FS-8700-97_Lutron_Machine Manual
Page 5 of 11
3.
Hardware Connections
The FieldServer is connected to the Lutron eLumen panel as shown in the connection drawing
below:
Configure the eLumen panel according to manufacturer’s instructions.
FS-8917-02
LUTRON SERIAL
RS-232 INTERFACE
PART # 470-784
8917-02 WIRE LIST
CAT 5 CABLE
FS-8915-10
FUNCTION
RX
FROM
TO
COLOUR
WHITE
BROWN
YELLOW
GREEN
RED
BLACK
ORANGE
BLUE
RJ45-01
RJ45-02
RJ45-03
RJ45-04
RJ45-05
RJ45-06
RJ45-07
RJ45-08
DB9M-02
DB9M-08
DB9M-06
DB9M-05
CTS
DSR
GND
GND
DTR
RTS
TX
DB9M-04
DB9M-07
DB9M-03
Serial
Power OK
(408)-262-2299
Tx
EIA232
Rx Tx
Rx
-
+
Ethernet
USB
EIA485
LUTRON ELUMEN RS-232
CONNECTION DIAGRAM
FS-B2010
BASE NAME:
FILE NAME: FS-T28700-84 .VSD
DATE: 11/12/04
BY: MC
FS-8700-97_Lutron_Machine Manual
Page 6 of 11
120V 15A
Dedicated Control
Feed
Wallstation link
To control stations
eLumen
Processor
Aux Link (RS-485)
User Interface link
Dimmer panel link
To dimmer panels
Inter-processor link
Serial
Power OK
Tx
EIA232
Rx Tx
Rx
-
+
Ethernet
USB
EIA485
FS-B2010
(408)-262-2299
LUTRON ELUMEN RS-485
CONNECTION DIAGRAM
BASE NAME:
FILE NAME: FS-T28700-84 .VSD
DATE: 11/12/04
BY: MC
FS-8700-97_Lutron_Machine Manual
Page 7 of 11
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.
Section Title
Data_Arrays
Column Title
Function
Legal Values
Up to 15 alphanumeric
characters
Data_Array_Name
Provide name for Data Array
Float, Bit, UInt16, SInt16,
Provide data format. Each Data Packed_Bit,
Byte,
Data_Array_Format
Data_Array_Length
Array can only take on one format.
Packed_Byte,
Swapped_Byte
Number of Data Objects. Must be
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
1-10,000
Example
// Data Arrays
Data_Arrays
Data_Array_Name,
Binary_Output,
Binary_Input,
Analog_Output,
Analog_Input,
Data_Format,
Bit,
Bit,
Uint16,
Uint16,
Data_Array_Length
512
512
512
512
FS-8700-97_Lutron_Machine Manual
Page 8 of 11
4.2.
Client Side Connection Descriptions
Section Title
Connections
Column Title
Function
Legal Values
Specify which port the device
Port
is
connected
to
the P1-P8, R1-R21
FieldServer
Protocol
Baud*
Parity*
Data_Bits*
Stop_Bits*
Specify protocol used
Specify baud rate
Specify parity
eLumen
9600
None
8
Specify data bits
Specify stop bits
Specify
1
hardware
Handshaking*
Poll _Delay*
None
handshaking
Time between internal polls
0-32000 seconds, 1 second
Example
// Client Side Connections
Connections
Port,
P1,
Protocol,
eLumen,
Baud,
9600,
Parity,
None,
Handshaking,
None,
Poll_Delay
0.100s
1
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
FS-8700-97_Lutron_Machine Manual
Page 9 of 11
4.3.
Client Side Node Descriptors
Section Title
Nodes
Column Title
Node_Name
Function
Provide name for node
Legal Values
Up to 32 alphanumeric characters
The eLumen processor address.
Only decimal values are allowed:
e.g. 11 hex must be entered as
17.
Node_ID
0-255
Protocol
Specify protocol used
eLumen
Specify which port the device is
connected to the FieldServer
Specifies the eLumen command
and data format
P1-P8, R1-R21
Connection
Node_type
Hex, decimal
Example
// Client Side Nodes
Nodes
Node_Name,
LUT_GRF6_0,
Node_ID,
17,
Protocol,
eLumen,
Port,
P1,
Node_Type
Hex
4.4.
4.4.1.
Client Side Map Descriptors
FieldServer Related Map Descriptor Parameters
Column Title
Function
Legal Values
Name of this Map Up to 32 alphanumeric
Map_Descriptor_Name
Data_Array_Name
Descriptor
characters
Name of Data Array
where data is to be
One of the Data Array
names from “Data Array”
section above
stored
in
the
FieldServer
Starting location in Data 0 to maximum specified in
Array “Data Array” section above
Function of Client Map ARCO, AWT, RDBC,
Descriptor Passive_Client
Data_Array_Offset
Function
4.4.2.
Driver Related Map Descriptor Parameters
Column Title
Function
Legal Values
One of the node names
specified in “Client Node
Descriptor” above
Area Machine:
Node_Name
Name of Node to fetch data from
run_script_AB
Specifies the command that will be
sent to the eLumen.
Grafik_Command
area_sts_offscene
sel_scene_in_area
run_script_multi
FS-8700-97_Lutron_Machine Manual
Column Title
Page 10 of 11
Legal Values
Function
area_status
sys_var_val_bin
sys_var_val
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.
The offset into the DA_Lut_List 0 to the maximum offset
Data Array from where the list data into the DA_Lut_List
DA_Lut_List_Offset
DA_Lut_Parms
is to be used.
Data Array.
Name of Data Array that contains
parameters needed to execute the A Data Array name.
command.
The offset into the DA_Lut_Parms 0 to the maximum offset
DA_Lut_Parms_Offset Data Array where the driver will into the DA_Lut_Parms
retrieve the parameters.
Data Array.
Area
GRAFIK system area number
0 – 511
Sys_var
Zone
GRAFIK system variable number
GRAFIK system zone number
Length of Map Descriptor. The
length is an indication of the
number of data elements this Map
Descriptor is responsible for
updating. It is used in the overall
0 – 65535
0 – 511
See
example
Map
Descriptors for individual
lengths
Descriptor.
Length
per
Map
points
calculation
of
the
FieldServer.
The length of the Data Array
specified under DA_Lut_List when
used with Grafik command:
run_script_multi
Multi_Scripts_Length
1 – 10,000
4.4.3.
Timing Parameters
Column Title
Scan_Interval
Function
Rate at which data is
Legal Values
≥0.001s
polled
FS-8700-97_Lutron_Machine Manual
Page 11 of 24
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.
BACnet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default
SMD00_BO,
Binary_Output,
0,
Server,
Virtual_BCU_11, BO,
1,
512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Run_Script_0,
Data_Array_Name,
Binary_Output,
Data_Array_Offset,
0,
Function,
AWT,
Node_name,
LUT_GRF6_0,
Grafik_Command,
run_script_AB,
DA_Lut_List,
Script_list_BO,
DA_Lut_List_Offset,
0,
Length
512
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
Preloads
Data_Array_Name ,
Preload_Data_Format ,
Preload_Data_Value ,
Location
// Binary Output Object ID 1
Script_list_BO ,
Script_list_BO ,
Uint16
Uint16
,
,
1
2
,
,
0
1
// Binary Output Object ID 2
Script_list_BO ,
Script_list_BO ,
Uint16
Uint16
,
,
3
4
,
,
2
3
FS-8700-97_Lutron_Machine Manual
Page 12 of 24
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
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default
SMD00_BI,
Binary_Input,
0,
Server,
Virtual_BCU_11, BI,
1,
512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Zone_int_0,
Data_Array_Name,
Binary_Input,
Data_Array_Offset,
0,
Function, Node_name,
Grafik_Command,
zone_intensity,
Zone, Length
0, 512
ARCO,
LUT_GRF6_0,
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.
FS-8700-97_Lutron_Machine Manual
Page 13 of 24
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”.
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
SMD00_BI, Binary_Input, 0, Server, Virtual_BCU_11, BI,
Data_Type, Object_ID, Length, Relinquish_Default
1, 512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Area_sts_0, Binary_Input, 0, ARCO, LUT_GRF6_0, area_sts_offscene, 0,
Grafik_Command,
Area, DA_Lut_List, DA_Lut_List_Offset, Length
off_scene, 0, 512
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
// Binary Input Object ID 1
off_scene
,
Uint16
Uint16
,
,
0
1
,
,
0
1
// Binary Input Object ID 2
off_scene
,
FS-8700-97_Lutron_Machine Manual
Page 14 of 24
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
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
SMD000_AO, Analog_Output, 0, Server, Virtual_BCU_11, AO,
Data_Type, Object_ID, Length, Relinquish_Default
1, 512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Sel_scene_0,
Data_Array_Name,
Analog_Output,
Data_Array_Offset,
0,
Function,
AWT,
Node_name,
LUT_GRF6_0,
Grafik_Command,
sel_scene_in_area,
area,
0,
Length
512
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.
FS-8700-97_Lutron_Machine Manual
Page 15 of 24
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%).
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default
SMD000_AO,
Analog_Output,
0,
Server,
Virtual_BCU_11, AO,
1,
512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Fade_to_lvl_0,
Data_Array_Name,
Analog_Output,
Data_Array_Offset,
0,
Function,
AWT,
Node_name,
LUT_GRF6_0,
Grafik_Command,
fade_zone,
zone,
0,
DA_Lut_Parms,
Zone_pars_AO1,
DA_Lut_Parms_Offset,
0,
Length
512
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
Preloads
Data_Array_Name ,
Preload_Data_Format ,
Preload_Data_Value ,
Location
// Analog Output1 Object ID 1
Zone_pars_AO1 ,
Zone_pars_AO1 ,
Uint16
Uint16
,
,
0
1
,
,
0
1
// Analog Output1 Object ID 2
Zone_pars_AO1 ,
Zone_pars_AO1 ,
Uint16
Uint16
,
,
2
3
,
,
2
3
FS-8700-97_Lutron_Machine Manual
Page 16 of 24
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.
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default
SMD512_AO,
Analog_Output,
512,
Server,
Virtual_BCU_11, AO, 513, 512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Run_script_512,
Data_Array_Name,
Analog_Output,
Data_Array_Offset,
512,
Function,
AWT,
Node_name,
LUT_GRF6_0,
Grafik_Command,
run_script_multi,
DA_Lut_List,
Scr_lst_AO2_512,
DA_Lut_List_Offset,
0,
Length,
1,
Multi_Scripts_Length
10
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.
FS-8700-97_Lutron_Machine Manual
Page 17 of 24
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
// Analog Output2 Object ID 513
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Scr_lst_AO2_512 ,
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
,
,
,
,
,
,
,
,
,
,
100
200
300
400
500
600
700
800
900
65000
,
,
,
,
,
,
,
,
,
,
0
1
2
3
4
5
6
7
8
9
// Analog Output2 Object ID 514
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Scr_lst_AO2_513 ,
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
,
,
,
,
,
,
,
,
,
,
101
201
301
401
501
601
701
801
901
65001
,
,
,
,
,
,
,
,
,
,
0
1
2
3
4
5
6
7
8
9
FS-8700-97_Lutron_Machine Manual
Page 18 of 24
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.
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptors_
Name,
SMD00_AI,
Data_Array_
Name,
Analog_Input,
Data_Array_
Offset,
0,
Function,
Server,
Node_name,
Data_Type,
AI,
Object_
ID,
1,
Length,
1,
Relinquish_Default,
0,
Data_Array_
Low_Scale,
0,
Data_Array_
High_Scale,
100,
Node_
Low_Scale,
0,
Node_
High_Scale
100
Virtual_BCU_11,
The last scene value may be scaled:
//================================================================================
// 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
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Last_scene_0,
Data_Array_Name,
Analog_Input,
Data_Array_Offset,
0,
Function,
ARCO,
Node_Name,
LUT_GRF6_0,
Grafik_Command,
area_status,
Area,
0,
Length
512
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.
FS-8700-97_Lutron_Machine Manual
Page 19 of 24
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.
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default
SMD00_AI, Analog_Input, 0, Server, Virtual_BCU_11, AI,
1,
512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Zone_inta_0,
Data_Array_Name,
Analog_Input,
Data_Array_Offset,
0,
Function,
ARCO,
Node_name,
LUT_GRF6_0,
Grafik_Command,
zone_intensity,
zone,
0,
Length
512
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.
FS-8700-97_Lutron_Machine Manual
Page 20 of 24
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.
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default,
SMD00_MO,
MultiSt_Output,
0,
Server,
Virtual_BCU_11, MO, 1, 512, 0,
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Run_scriptms_0,
Data_Array_Name,
MultiSt_Output,
Data_Array_Offset,
0,
Function,
AWT,
Node_name,
LUT_GRF6_0,
Grafik_Command,
run_script_multi,
DA_Lut_List,
Scr_lst_MSO_0,
DA_Lut_List_Offset,
0,
Length,
1,
Multi_Scripts_Length
10
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.
FS-8700-97_Lutron_Machine Manual
Page 21 of 24
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
Preloads
Data_Array_Name
Preload_Data_Format
Preload_Data_Value
Location
// Multistate Output Object ID 1
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Scr_lst_MSO_0 ,
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
,
,
,
,
,
,
,
,
,
,
110
210
310
410
510
610
710
810
910
65010
,
,
,
,
,
,
,
,
,
,
0
1
2
3
4
5
6
7
8
9
// Multistate Output Object ID 2
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Scr_lst_MSO_1 ,
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
Uint16
,
,
,
,
,
,
,
,
,
,
120
220
320
420
520
620
720
820
920
65020
,
,
,
,
,
,
,
,
,
,
0
1
2
3
4
5
6
7
8
9
FS-8700-97_Lutron_Machine Manual
Page 22 of 24
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.
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default
SMD00_BV,
Binary_Value,
0,
Server,
Virtual_BCU_11, BV,
1,
512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Zone_var_0,
Data_Array_Name,
Binary_Value,
Data_Array_Offset,
0,
Function,
ARCO,
Node_name,
LUT_GRF6_0,
Grafik_Command,
sys_var_val_bin,
Sys_Var, Length
0,
512
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.
FS-8700-97_Lutron_Machine Manual
Page 23 of 24
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.
BACNet IP Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_name,
Data_Type, Object_ID, Length, Relinquish_Default
SMD00_AV, Analog_Value, 0, Server, Virtual_BCU_11, AV,
1,
512,
0
Lutron Machine Map Descriptor
// Client Side Map Descriptors
Map_Descriptors
Map_Descriptor_Name,
Zone_vara_0,
Data_Array_Name,
Analog_Value,
Data_Array_Offset,
0,
Function,
Passive_Client, LUT_GRF6_0,
Node_name,
Grafik_Command,
sys_var_val,
Sys_Var, Length
0,
512
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.
FS-8700-97_Lutron_Machine Manual
Appendix A. Revision History
Page 24 of 24
Driver Doc.
Date
Resp Format
Comment
Ver.
1.00
1.01
Rev.
0
1
07/04/03 DR
07/08/03 DR
09/05/03 DR
09/09/03 DR
Created
Updated driver version, SPR2912
1.02
1.02
1
2
Updated with ARCO Map Descriptor usage
Updated with passive Client mapdescs
Updated according to DUR0215.
formatting
Updated
10/15/03 MF
1.02
3
1/21/04
3/22/04
JD
1.02
1.02
4
5
Releasing
DR
Updated for release
Updated formatting. Added new revision table.
Changed page setup to letter.
Releasing
Changed references to Grafik to eLumen –
DUR0484.
3/24/04
6/10/04
11/3/04
MC
JD
MC
1.02
1.02
1.03
6
7
0
Meg Meg
Connection diagrams added for RS-232 and
RS-485. Modifications to scope of supply table.
Table formatting. Map Descriptor example titles
added. Added RS-485 compatibility.
12/30/04 Meg Meg
1.03
1
4/12/05
4/27/05
JD
JD
JD
JD
1.03
1.03
1
2
Releasing
Corrected page numbering. Releasing.
|