SOMFY animeo LON RTS Module 433 MHz WM User manual

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 1/44
Functional Profile
SOMFY animeo®
LON RTS Module 433 MHz WM
Ref. 1860239
SOMFY animeo®
LON RTS Module 447 MHz WM
Ref. 1860240
Version 1.02
Revision date: 2016/12/20
Ref. 5118943A
Somfy Activites SA
50 Avenue du Nouveau Monde
74300 Cluses
France
www.somfy.com/projects
SOMFY ACTIVITES SA Société Anonyme, capital 35.000 €, RCS Annecy 303.970.230 09/2017

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 2/44
Table of Content
1. Document History ................................................................................................................4
2. Hardware...............................................................................................................................5
3. Node Object #0000...............................................................................................................6
3.1. Overview...................................................................................................................6
3.2. Functional-Block Details............................................................................................7
3.3. Network Variables.....................................................................................................9
3.3.1. Request Input.........................................................................................................9
3.3.2. Status Output.......................................................................................................11
3.3.3. File Directory........................................................................................................12
3.3.4. Programming Mode..............................................................................................13
3.4. Configuration Properties..........................................................................................14
3.4.1. Location Label (optional)......................................................................................14
3.4.2. Device Major Version...........................................................................................14
3.4.3. Device Minor Version...........................................................................................15
4. Radio Control #3200...........................................................................................................16
4.1. Overview.................................................................................................................16
4.2. Functional-Block Details..........................................................................................17
4.3. Network Variables...................................................................................................19
4.3.1. Switch Output.......................................................................................................19
4.3.2. Switch Feedback Input.........................................................................................19
4.3.3. Setting Output......................................................................................................20
4.3.4. Learn Address......................................................................................................20
4.4. Configuration Properties..........................................................................................21
4.4.1. Location Label......................................................................................................21
4.4.2. Transmitter Address.............................................................................................21
4.4.3. Long Operation ....................................................................................................22
4.4.4. Setting Down........................................................................................................22
4.4.5. Setting Up............................................................................................................23
4.4.6. Setting My/Stop.................................................................................................... 23
4.4.7. Step Angle ...........................................................................................................24
4.4.8. Scroll Step............................................................................................................24
5. Analog Sensor #0001.........................................................................................................26
5.1. Overview.................................................................................................................26
5.2. Functional-Block Details..........................................................................................27
5.3. Network Variables...................................................................................................29
5.3.1. Analog Sensor Output x.......................................................................................29
5.4. Configuration Properties..........................................................................................29
5.4.1. Type Of Analog Sensor........................................................................................29
5.4.1.1. Example: CO2 As Analog Sensor.........................................................................30
5.4.1.2. Example: Temperature As Analog Sensor............................................................31
5.4.1.3. Example: Brightness As Analog Sensor............................................................... 31
5.4.1.4. Example: Occupancy As Dry Contact................................................................... 31
5.4.1.5. Example: Watts per square meter As Analog Sensor...........................................32
5.4.2. Max Send Time (Heartbeat).................................................................................32
5.4.3. Min Send Time.....................................................................................................33
5.4.4. Send On Analog Sensor Delta .............................................................................33
5.4.4.1. Example: Send On Power Delta...........................................................................34
5.4.4.2. Example: Send On Percent (CO2) Delta.............................................................. 34

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 3/44
5.4.4.3. Example: Send On Temperatur Delta...................................................................34
5.4.4.4. Example: Send On Brightness Delta....................................................................35
5.4.4.5. Example: Send On Switch Delta...........................................................................35
5.4.4.6. Example: Send On Occupancy Delta...................................................................35
5.4.4.7. Example: Watts per square meter As Analog Sensor...........................................36
5.4.5. Analog Sensor Gain.............................................................................................36
5.4.5.1. Example: Electric Voltage As Analog Sensor .......................................................37
5.4.5.2. Example: Brightness As Analog Sensor............................................................... 38
5.4.5.3. Example: Occupancy Or Switch As Dry Contact ..................................................38
5.4.6. Analog Sensor Offset...........................................................................................38
5.4.6.1. Example: Analog Sensor Offset Power.................................................................38
5.4.6.2. Example: Analog Sensor Offset CO2...................................................................39
5.4.6.3. Example: Analog Sensor Offset Temperature ...................................................... 39
5.4.6.4. Example: Analog Sensor Offset Brightness..........................................................40
5.4.6.5. Example: Analog Sensor Offset Switch................................................................ 40
5.4.6.6. Example: Analog Sensor Offset Occupancy.........................................................40
5.4.6.7. Example: Watts per square meter As Analog Sensor...........................................41
6. Appendix:............................................................................................................................42
6.1. Push button configuration of the radio transmitter ...................................................42
6.2. Push button configuration of the radio transmitter ...................................................43
6.3. SOMFY RTS Transmitter compatible with...............................................................44
6.3.1. LON RTS Module 433 MHz..................................................................................44
6.3.2. Situo RTS Pure 433 MHzLON RTS Module 447 MHz..........................................44

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 4/44
1. Document History
version Modification reason validity date
1.0 First Version 03.12.2014
1.01 Appendix added 09.01.2015
1.02 Device “LON RTS Module
433MHz” added 09.06.2015

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 5/44
2. Hardware
The device has three LEDs and one button. The latter and the yellow LED are used for
service purpose as defined by F.
The green LED signals the operation of the power supply.
The orange LED signals the state of the radio receiver. Blinking means that no transmitter
is registered. As soon as at least one radio transmitter is known the LED stops blinking
and signals further on the reception of a valid radio frame by an one second on wink

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 6/44
3. Node Object #0000
UFPTnodeObject #0000
3.1. Overview
The SOMFY Node Object inherits all mandatory and some optional members from the
LonMark

Node Object # 0000. Various SOMFY specific members have been added.
The Node Object functional profile describes a special type of functional block—called
the Node Object functional block—that is used by network tools to test and manage all
the functional blocks on a device.
The Node Object functional block may also be used to initiate the collecting of remote
control addresses. Any remote control can be linked only once to one interface device.
Although possible it is not advisable to link a radio control twice to a LON system. If
required this functionality should be accomplished in LON.
The Node Object functional block includes a mandatory nviRequest input network
variable and a mandatory nvoStatus output network variable. Other devices and
applications may request a Node Object function by sending a request to the nviRequest
network variable. Upon receiving an update to the nviRequest network variable, the
request is processed and the nvoStatus network variable is updated with either the results
of the request, an in-process indication, or an error indication. The definition of the
nviRequest network variable includes an object ID field to allow the Node Object to
report status and alarm conditions for all functional blocks on a device.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 7/44
3.2. Functional-Block Details

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 8/44
Table 1 SNVT Details
NV
(M/O)* Variable Name SNVT/UNVT Name SNVT/UNVT Index Description
1 (M) nviRequest SNVT_obj_request 92 Requests a particular
mode for a particular
functional block in the
device
2 (M) nvoStatus SNVT_obj_status 93 Reports the status of the
requested functional block
in the device
8 (M) nvoFileDirectory SNVT_address 114 Address for the file
directory containing
descriptors for
configuration files
#1 (O) nviProgMode SNVT_switch 95 Activation of
programming mode to
collect further radio
transmitter devices
* M = mandatory, O = optional
Table 2 SCPT Details
(M/O)* SCPT/UCPT Name
NV Name
Type or SNVT
SCPT/
UCPT
Index
Associated NVs ** Description
O SCPTlocation
nciLocation
SNVT_str_asc (36)
17 Entire Functional
Block Provides descriptive physical location information related to
the entire device.
O SCPTdevMajVer
nciDevMajVer
unsigned short
165 Entire Functional
Block The major version number for the device
O SCPTdevMinVer
nciDevMinVer
unsigned short
166 Entire Functional
Block The minor version number for the device
* M = mandatory, O = optional
** List of NVs to which this configuration property applies.
An “(M)” means that the CP is mandatory if the NV (to which it applies) is implemented.
An “(O)” means that the CP is optional if the NV (to which it applies) is implemented.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 9/44
3.3. Network Variables
3.3.1. Request Input
network input SNVT_obj_request nviRequest;
This input network variable provides the mechanism to request an operation or a mode
for a functional block within a device. For a listing of all possible request codes, and
for the meaning of the function codes for SNVT_obj_request, see the SNVT Master
List.
A request consists of an object ID (the object_id field) and an object request (the
object_request field). The object ID is the functional block index for a functional
block on the device. If a device has a Node Object functional block, its functional
block index must be zero. The remaining functional blocks are numbered sequentially,
starting with one.
The object request specifies a request function for the functional block identified by
the object ID. The object_request_t definition in the SNVT Master List defines the
available request functions; the following requests are the only mandatory request
functions:
RQ_NORMAL
RQ_UPDATE_STATUS
RQ_REPORT_MASK
If an nviRequest update specifies an unsupported request function, the nvoStatus
output network variable must be updated with the invalid request field set to one.
Support for the object-disable, self-test, override, and alarm reporting request functions
is not required.
The request functions are defined as follows:
RQ_NORMAL If the specified functional block was in the disabled or overridden
state, this request cancels that state and returns the functional block to
normal operation. If the functional block was already in the normal state, a
request to enter the normal state is not an error. After device reset, the state
of functional blocks on the device is application-specific. An
RQ_NORMAL request that specifies the Node Object functional block
index is a request for all functional blocks in the device to leave the
disabled and overridden states.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 10/44
RQ_UPDATE_STATUS Requests the status of the specified functional block to be
sent to the nvoStatus output network variable. The state of the functional
block is unchanged. A RQ_ UPDATE_STATUS request that specifies the
Node Object functional block is a request for the status of the device and
all functional blocks on the device. The status bits of the Node Object
(with the exception of invalid_request and invalid_id) are defined to be
the inclusive-OR of the status bits of all the other functional blocks in the
device; with the possible addition of error conditions and other conditions
attributed to the device as a whole, rather than to any individual functional
block. For example, if comm_failure is supported for the Node Object,
then it should be set when reporting the Node Object functional block
status whenever any of the functional blocks in the device reports
communications failure, as well as when there is a communications failure
at the device level.
RQ_REPORT_MASK Requests a status mask reporting the status bits that are
supported by the specified functional block to be sent to the nvoStatus
output network variable. A one bit in the status mask means that the device
may set the corresponding bit in the object status when the condition
defined for that bit occurs. A zero bit in the status mask means that the bit
is never set by the device. For example, if object disable
(RQ_DISABLED) is not supported for a functional block, the disabled
bit in the status mask must be zero for that functional block. If self-test
(RQ_SELF_TEST) is not supported for a functional block, the
fail_self_test and self_test_in_progress bits in the status mask must be
zero for that functional block. If alarm reporting
(RQ_UPDATE_ALARM or asynchronous notification) is not supported,
the in_alarm bit in the status mask must be zero for that functional block.
A RQ_REPORT_MASK request that specifies the Node Object
functional block requests a status mask that is the inclusive-OR of
supported status bits for the device and all functional blocks on the device.
Valid Range
The valid range is any value within the defined limits of SNVT_obj_request.
Default Value
The default value is undefined.
Configuration Considerations
None specified.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 11/44
3.3.2. Status Output
network output SNVT_obj_status nvoStatus;
This output network variable reports the status for any functional block on a device. It
is also used to report the status of the entire device and all functional blocks on the
device.
A status update consists of an object ID (the object_id field) and multiple status fields.
The object ID is the functional block index as described under nviRequest. If the
object ID is zero, the status of the device itself and all functional blocks on the device
are reported.
The status fields are one-bit bitfields. The only required status fields are the
report_mask, invalid_id and invalid_request fields; all other status fields are
optional. If an error condition is active for a reported functional block, the
out_of_limits field is set to one. Following is a description of the required status
fields. See the SNVT Master List for a description of the optional fields.
invalid_request Set to one if an unsupported request code (RQ_xxx) is received on the
nviRequest input network variable.
invalid_id Set to one if a request is received for a functional block index that is not
defined in the device. No further checking of the request code is required
when set to one.
report_mask Set to one if a RQ_REPORT_MASK request is received by the
nviRequest input network variable, and the nvoStatus output network
variable is set to contain the status mask. The status mask is a nvoStatus
value that describes the status bits that are supported beyond the three
mandatory status bits. The status mask consists of all fields in the
nvoStatus output network variable, with the exception of the
report_mask, invalid_id and invalid_request fields. A one bit in the
mask means that the functional block may set the corresponding bit in
the nvoStatus output network variable when the condition defined for
that bit occurs. A zero bit means that the functional block may never set
the bit.
Valid Range
The valid range is any value within the defined limits of SNVT_obj_status with the
exception that the report_mask, invalid_id and invalid_request fields must be set to
one.
Default Value
The default value must be the actual status of the device for all supported fields. All
other fields must be set to zero. The application must update the status such that a
polling of the status, following the request, returns a reasonable value.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 12/44
Configuration Considerations
None.
When Transmitted
The output variable is transmitted when either of the following conditions occurs:
A request is received by the nviRequest input network variable.
Default Service Type
The default service type is acknowledged.
3.3.3. File Directory
network output SNVT_address nvoFileDirectory;
This output network variable reports the starting address of the configuration-file
directory on a Neuron hosted device. It is used when configuration properties are
implemented within configuration files accessed by ANSI/EIA/CEA-709.1 Read
Memory and Write Memory network-management messages. If an nvoFileDirectory
output network variable is implemented on a device, all files on the device must be
accessible using network management read/write messages. For more details, see
Configuration Properties within the L ON M ARK Application-Layer Interoperability
Guidelines.
This output network variable must be implemented in the Node Object functional
block if the device supports the L ON W ORKS FTP with random and sequential access
method. It must not be implemented if the device supports the L ON W ORKS FTP with
sequential access or the direct memory read/write access methods for data files.
Valid Range
The valid range for the file directory address is any value within the user-data memory
space of a Neuron Chip or Smart Transceiver.
Default Value
The typical default value is FS_NUL.
Configuration Considerations
The Node Object implements the file-request and file-position network variables as
inputs, and the file-status network variable as an output. The device can therefore act
as the Sender or the Receiver in a file transfer, but it cannot act as the Initiator of a file
transfer using these network variables.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 13/44
When Transmitted
The output variable is transmitted when either of the following conditions occurs:
During file transfer
When polled
Default Service Type
The default service type is unspecified. Network tools may wish to poll this network
variable for values.
3.3.4. Programming Mode
network input SNVT_switch nviProgMode;
This input network variable activates the programming mode to collect further radio
transmitter devices. Once switched on the device listens for any programming telegram
in the air. As soon as a new radio transmitter message was received the NV changes
back to off and stores the address of the transmitter in the next free memory space.
It is not possible to link one radio transmitter multiple times to one interface device.
Valid Range
The valid range is the range of SNVT_switch.
Default Value
The default value is “0.0 0” (value=0; state=0).
Configuration Considerations
Don’t forget to save the received address (es)! After a timeout of one hour the device
aborts the programming. See nciTransmitterAddr in RadioCtrl Functional Block(s).

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 14/44
3.4. Configuration Properties
3.4.1. Location Label (optional)
SCPTlocation cp_family nciLocation;
This configuration property identifies the subsystem containing the device. It provides
a more detailed description of the device location than can be provided by the Neuron
Chip’s 6-byte location string. This allows network-recovery tools to recover subsystem
information from a device. The subsystem may be a simple location name, or may be a
hierarchical subsystem name. If a hierarchical subsystem name is specified, the
subsystem hierarchy components must be separated by periods ( . ). For example, a
device may have an nciLocation value of “Bldg 1.Floor 2.Rm 29”, representing the
Bldg 1/Floor 2/Rm 29 subsystem. Periods must not otherwise be used in the
nciLocation value. Other characters that cannot be used in the nciLocation value are
the backslash ( \ ), colon ( : ), forward slash ( / ), or double-quotation ( " ) characters
(however, stylistic quotation characters can be used, such as „ , “ , ” , « , and » ). For
very large networks, subsystem numbers may be used instead of subsystem names, for
example: “1.2.29”. This allows deeply nested hierarchies to fit within the 31-character
limit for SCPTlocation.
If a device has multiple locations, such as a device with multiple remote sensors, each
of the functional blocks on the device may also implement a SCPTlocation
configuration property to identify the location of each of the remote components. The
SCPTlocation configuration property associated with the Node Object identifies the
location of the device itself, whereas the other SCPTlocation configuration properties
identify the locations of their respective hardware components.
If a device does not have a Node Object functional block, a SCPTlocation
configuration property that applies to the device may be implemented to document the
device location.
Valid Range
Any NUL-terminated ASCII string up to 31 bytes of total length (including NUL). The
string must be truncated if the length does not allow the thirty-first character to be the
NUL (0).
Configuration Requirements/Restrictions
This CP has no modification restrictions. It can be modified at any time.
3.4.2. Device Major Version
network input config SCPTdevMajVer nciDevMajVer;
This configuration property provides the major version number of a device.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 15/44
The major version number is incremented when the network interface for the device
changes.
Valid Range
Any integer number from 0 to 255.
Default Value
The default value is zero.
Configuration Requirements/Restrictions
Read only.
3.4.3. Device Minor Version
network input config SCPTdevMinVer nciDevMinVer;
This configuration property provides the minor version number of a device.
The minor version number is incremented when the network interface remains the
same, but the device has a different behaviour.
Valid Range
Any integer number from 0 to 255.
Default Value
The default value is zero.
Configuration Requirements/Restrictions
Read only. Only online available.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 16/44
4. Radio Control #3200
4.1. Overview
The SOMFY Radio Control inherits all mandatory and some optional members from
the LonMark

Switch Object # 3200. Various SOMFY specific members have been
added.
This document describes the profile for a Radio Control object. The profile is used
preferably for sunblind radio controls composed of switch-up and switch-down
hardware. The Radio Control object can be used for both closed and open loop
applications.
The Functional Block “Radio Control” exists 30 times in the animeo LON RTS
Module Each could be set individually and separately from the others and can be
linked to exactly one remote control. On one interface device any remote control can
be linked only once.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 17/44
4.2. Functional-Block Details

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 18/44
Table 1 SNVT Details
NV
(M/O)* Variable Name SNVT Name SNVT Index Description
1 (M) nvoSwitch SNVT_switch 95 Switch output value
linked to
Up/Down/My radio
buttons
2 (O) nviSwitchFb SNVT_switch 95 Switch feedback
input
3 (O) nvoSetting SNVT_setting 117 Setting output
# 1(O) nviLearnAddr UNVT_transmitter_addr 1 Address of
registered radio
transmitter device
* M = mandatory, O = optional
Table 2 SCPT Details
Man.
Opt. *
SCPT Name NV
Name
Type or SNVT
SCPTIndex Associated
NVs Description
(O)
SCPTlocation
nciLocation
SNVT_str_asc (36)
1 Entire
Functional
Block
Provides descriptive physical
location information related to the
object.
(O)
UCPTtransmitterAddr
nciTransmitterAddr
UNVT_transmitter_ad
dr
#1 #nv1 (O) Address of registered radio
transmitter device
(O)
UCPTdlyStartLong
nciLongOperation
SNVT_time_sec (107)
#2 Entire
Functional
Block
Time after which long operation
command is generated
(O)
UCPTsettingUp
nciSettingUp
SNVT_setting (117)
#3 nv3 (O) Values which are sent via nvoSetting
if Up command was received
(O)
UCPTs ettingMy
nciS ettingMy
SNVT_setting (117)
#4 nv3 (O) Values which are sent via nvoSetting
if My command was received
(O)
UCPTsettingDown
nciSettingDown
SNVT_setting (117)
#5 nv3 (O) Values which are sent via nvoSetting
if Down command was received
(O)
UCPTstepAngle
nciStepAngle
SNVT_angle_deg
(104)
#6 nv3 (O) Rotation distance for one tilting step
(O)
UCPTscrollStep
nciScrollStep
SNVT_level_cont (21)
#7 nv3 (O) Percentage of value change for tilting
and dimming
* M = mandatory, O = optional
It should be mandatory for CPs that mandatory for an NV that is also mandatory. This is also
valuable for CPs that applies to the Entire Functional Block.
** List of NVs to which this configuration property applies.
An “(M)” means that the CP is mandatory if the NV (to which it applies) is implemented.
An “(O)” means that the CP is optional if the NV (to which it applies) is implemented.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 19/44
4.3. Network Variables
4.3.1. Switch Output
network output SNVT_switch nvoSwitch;
This output network variables provides the switch output linked to the radio buttons.
The Up-button switches on, the Down-button switches off and the My-button toggles
the output.
Depending on the used radio transmitter the value can be increased/decreased for
dimming purpose with the scroll wheel or by long operation of buttons.
Valid Range
The valid range is the range of SNVT_switch. State 0 means OFF, 1 means ON. The
range of the 8-bit intensity value is 0 - 200 (0 - 100% in 0,5% steps). Minimum level is
value 0.
When Transmitted
Whenever the hardware received a corresponding radio message.
Update Rate
There is no maximum update rate. The default minimum update rate is 0 ms. Minimum
update rate is configurable.
Default Service Type
none
4.3.2. Switch Feedback Input
network input SNVT_switch nviSwitchFb;
This input network variable provides the feedback from other devices. This is
important for toggling. It does not initiate any action.
Valid Range
Valid range is the range of SNVT_switch.
Default Value
The default value is state = -1, value = 0,0.

Date: 27.09.17
Functional Profile LON RTS Module WM
animeo LON RTS Module 433/447 MHz . Ref. 51318943A 20/44
4.3.3. Setting Output
network output SNVT_setting nvoSetting;
When blinds are controlled by a controller, such as a sunblind controller, the setting
output is used to change the mode and/or the setpoint of the controller. The controller
can be turned ON or OFF and the setpoint can be adjusted.
Valid Range
The Valid Range is given by the interpretation of the “SNVT_setting related to
sunblinds” as shown in the tables it the chapter “Additional Considerations” in the
Sunblind Actuator Profile.
When Transmitted
Whenever the hardware received a corresponding radio message.
Update Rate
There is no maximum update rate. The default minimum update rate is 0 ms. Minimum
update rate is configurable.
Default Service Type
none
4.3.4. Learn Address
network input UNVT_transmitter_addr nviLearnAddr_n;
This input network variable shows the address of the radio transmitter linked actually
to this Functional Block.
It can be used as well to learn a (new) transmitter address if the actual one has been
deleted before by entering Zero. The device listens then for any programming telegram
in the air. As soon as a new radio transmitter message has been received the NV
displays it and stores the address of the transmitter.
It is not possible to link one radio transmitter multiple times to one interface device.
Valid Range
0x000001 ... 0xFFFFFF