Query Commands

In this Topic ShowHide

When you send a query command, the message returned contains the query command data which was sent, followed by the reply; this data makes up the query reply. If you send a query command in raw format, for example, the query reply will comprise all ten Words of the command plus the Word(s) that makes up the reply. It is necessary for the reply to contain the command data as the system will not guarantee the order of replies.

General Query Commands

101 - Query Clusters

When you send a Query Clusters command, the reply provides you with all the Cluster IDs that exist in the system.

Command

Send: Command (101)

Reply

Returns a bit field indicating the presence of all clusters:

Command (101), Cluster Count, 8x32 bit Words detailing the existence of the clusters 1-253 (bits 0, 254, 255 are always zero)

ASCII Example

If you send the following Query Clusters command:

>V:1,C:101#

If there are clusters 1, 2 and 253, then the reply will be:

?V:1,C:101=1,2,253#

Raw Example

If you send the following Query Clusters command:

 0x00010065  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If there are 1, 2 and 253 clusters, then the reply will be:

 0x01010065  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00030006  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x20000000

102 - Query Routers

When you send a Query Routers command, the reply provides you with all the Cluster Member (Router) IDs that exist in the specified cluster.

Command

Send: Command (102), Cluster (1..253)

Reply

Returns a bit field indicating the presence of all routers within the specified cluster:

Command (102), Router Count / Cluster ID (1..253), 8x32 bit Words detailing the existence of the routers 1-254 (bits 0 and 255 are always zero)

ASCII Example

If you send the following Query Routers in cluster 253 command:

>V:1,C:102,@253#

If there are routers 252, 253 and 254 in cluster 253, then the reply will be:

?V:1,C:102,@253=252,253,254#

Raw Example

If you send the following Query Routers in cluster 253 command:

 0x00010066  0x000000FD  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If there are routers 252, 253 and 254 in cluster 253, then the reply will be:

 0x01010066  0x000000FD  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00030000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x70000000

103 - Query Last Scene In Block (LSIB)

When you send a Query Last Scene Collection of lighting levels for each channel assigned to the same group as the scene. In Block command, the reply provides you with the last scene that was recalled in the specified scene block.
 

Command

Send: Command (103), Group (1..16383), Block (1..8)

Reply

Returns the number of the last recalled scene in the scene block:

Command (103), Group (1..16383), Block (1..8), Last Scene In Block (1..16)

ASCII Example

If you send the following Query LSIB command (including the group and scene block parameters):

>V:1,C:103,G:5,B:2#

If the last scene called in the block is 4, then the reply will be:

?V:1,C:103,G:5,B:2=4#

Raw Example

If you send the following Query LSIB command (including the group and scene block parameters):  

 0x00010067  0x00000005  0x00000000  0x00020000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the last scene called in the block is 4, then the reply will be:

 0x01010067  0x00000005  0x00000000  0x00020000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000004

109 - Query Last Scene In Group (LSIG)

When you send a Query Last Scene Collection of lighting levels for each channel assigned to the same group as the scene. In Group command, the reply provides you with the last scene that was recalled in the specified group.
 

Command

Send: Command (109), Group (1..16383)

Reply

Returns the number of the last recalled scene in the group:

Command (109), Group (1..16383), Last Scene In Group (1..128)

ASCII Example

If you send the following Query LSIG command:

>V:2,C:109,G:5#

If the last scene called in the group is 78, then the reply will be:

?V:2,C:109,G:5=78#

104 - Query Device Type

DALI Stands for Digital Addressable Lighting Interface. Standardised digital protocol for lighting control, allowing communication between control devices and LIUs (control gear). , DIGIDIM, Imagine (SDIM Stands for ‘Serial DIMming communication’. It is a Helvar communication protocol.) and DMX Stands for Digital Multiplex. A type of subnet, used mainly for stage lighting and effects control. devices are all capable of returning a device type. Devices can return more than one piece of type information.

For an ASCII query the response will be four comma separated values, the last of which is the protocol; the penultimate is the device type; and the remaining two are extra device information.

For a raw query the response will be returned in a 32 bit Word. The least significant byte contains the protocol; the next least significant byte contains the main device type; the two most significant bytes contain extra device information.

The devices protocols are as follows:

Command

Send: Command (104), Cluster (1..253), Router (1..254), Subnet A subnet is a part of a router. There are two or more subnets on each router. The subnet allows the flow of network traffic between hosts to be segregated, based on network configuration. By organising hosts into logical groups and joining them, subnetting, network security and performance can be improved. (1..4), Device (1..255)

Reply

Returns the device type:

Command (104), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Device Type (see tables below)

ASCII Example

If you send the following Query Device Type command (including the full address of the device):

>V:1,C:104,@2.2.1.1#

If the device is a 100 Rotary, then the reply will be:

?V:1,C:104,@2.2.1.1=00100802#

Raw Example

If you send the following Query Device Type command (including the full address of the device):  

 0x00010068  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the device is a 100 Rotary, then the reply will be:

 0x01010068  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000 0x00100802

DALI Device Type Information

DIGIDIM Control Device Type Information

Imagine (SDIM) Device Type Information

DMX Device Type Information

DIGIDIM Control Key Type Information

100 - Query Device Types and Addresses

When targeted at a subnet it will respond with all of the devices types with corresponding index, as in command 104.  The device type and index pairs are in this format: Device Type @ index.

ASCII Example

If you send the following Query Device Type command (including the full address of the device):

>V:2,C:100@2.2.1#

If the DALI subnet has 2 devices, one being a 100 Rotary at index 1, and the other being a 110 Slider at index 10, then the reply will be:

?V:2,C:100@2.2.1.1=00100802@1,00110702@10#

105 - Query Description Group

DALI Stands for Digital Addressable Lighting Interface. Standardised digital protocol for lighting control, allowing communication between control devices and LIUs (control gear). , DIGIDIM Helvar’s range of products based on the DALI standard. The DIGIDIM range is composed of a series of controllers and lamp interface units that are designed to communicate using DALI commands., Imagine ( SDIM Stands for ‘Serial DIMming communication’. It is a Helvar communication protocol. ) and DMX Stands for Digital Multiplex. A type of subnet, used mainly for stage lighting and effects control. devices are all capable of returning a description of the group.

The replies in the following examples are the default descriptions for those devices/objects. However, the reply will return group name according to the conventions you have applied to your lighting system A network of client PCs, routers, control devices, control gear, and lamps via Designer. For example, if the group has been named 'Building' then this will be returned in the Query Description Group reply.

Command

Send: Command (105), Group (1...16383)

Reply

Returns: Command (105), Group (1...16383), Group description

ASCII Example

If you send the following Query Description Group command (including the group number):

>>V:1,C:105,G:5#

The reply will be the command sent and the reply containing the group description of the group requested i.e.

?V:1,C:105,G:5=Group 5#

Raw Example

If you send the following Query Description Group command (including the group number):  

 0x00010069  0x00000005  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the description is Group 5, then the reply will be:

 0x01010069  0x00000005  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000 0x47726F75 0x70203500

106 - Query Description Device

DALI Stands for Digital Addressable Lighting Interface. Standardised digital protocol for lighting control, allowing communication between control devices and LIUs (control gear). , DIGIDIM, Imagine ( SDIM Stands for ‘Serial DIMming communication’. It is a Helvar communication protocol. ) and DMX Stands for Digital Multiplex. A type of subnet, used mainly for stage lighting and effects control. devices are all capable of returning a description of a specific device.

The replies in the following examples are the default descriptions for those devices/objects. However, the reply will return group name according to the conventions you have applied to your lighting system via Designer. For example, if the device has been named 'Ballast 10' then this will be returned in the Query Description Group reply.

Command

Send: Command (106), Cluster (1..253), Router (1..254), Subnet A subnet is a part of a router. There are two or more subnets on each router. The subnet allows the flow of network traffic between hosts to be segregated, based on network configuration. By organising hosts into logical groups and joining them, subnetting, network security and performance can be improved. (1..4), Device (1..255)

Reply

Returns a description of the device:

Command (106), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Device description

ASCII Example

If you send the following Query Description Device command (including the full address of the device):

>V:1,C:106,@2.2.1.1#

If the device is called 'Ballast', then the reply will be:

?V:1,C:106,@2.2.1.1=Ballast#

Raw Example

If you send the following Query Description Device command (including the full address of the device):  

 0x0001006A  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the device is called 'Ballast', then the reply will be:

 0x0101006A  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000 0x42616C6C 0x61737400

Discovery Query Commands

The following set of commands are extensions to version 1 and are designed to allow for the discovery of a Helvar router system.

107 - Query Workgroup Name - UDP Broadcast

By broadcasting this command all Helvar routers that exist on a network, providing that they can see the message, will respond with the workgroup name to which they belong. If there are multiple workgroups, then there will be responses from all routers in all workgroups.

ASCII Example

If you broadcast (using UDP) the following Query Workgroup Name command:

>V:2,C:107#

All routers will respond with:

?V:2,C:107=WorkgroupName#

For example, a router with workgroup name 'Restaurant' will respond with: ?V:2,C:107=Restaurant#

108 - Query Workgroup Membership

A router will respond to this query with the address strings of the routers that are members of the workgroup.

An address string contains the IP address of the router, and takes the form of '@10.254.1.1'.

ASCII Example

If you send the following Query Workgroup Membership command:

>V:2,C:108#

A typical response will be:

?V:2,C:108=@10.254.1.1,@10.254.1.2,@10.254.1.3#

165 - Query Groups

A router will respond to this query with the group identifiers of all groups that have been programd to the router's workgroup.

The response is a comma delimited string of group identifiers.

ASCII Example

If you send the following Query Groups command:

>V:2,C:165#

A typical response will be:

?V:2,C:165=1,2,3,4,...,100#

164 - Query Group

A router will respond to this query with the address strings of all devices that are members of the group.

The device address string contains the cluster, router, subnet and device index, and takes the form of '@1.1.1.34'.

ASCII Example

If you send the following Query Groups command:

>V:2,C:164,G:100#

A typical response will be:

?V:2,C:164,G:100=@1.1.1.34,@1.1.1.35,@1.1.1.36#

166 - Query Scene Names

A router will respond to this query with the scene descriptions that are prefixed with the corresponding group, block and scene.

The scene description string contains the group, block, and scene numbers and scene description, and takes the form of '@G.B.S:Description'.

ASCII Example

If you send the following Query Groups command:

>V:2,C:166#

A typical response will be:

?V:2,C:166=@1.1.1:Morning@1.1.2:Afternoon@1.1.3:Night#

167 - Query Scene Info

When targeted at a load interface, the response will include all of the scene levels.

The response will contain all 136 scene levels, in a comma delimited format.

Ignores are represented by '*'. Last Level is represented by 'L'.

ASCII Example

If you send the following Query Groups command:

>V:2,C:167@1.1.1.4#

A typical response will be:

?V:2,C:167@1.1.1.4=100,75,50,25,0,0,0,0,0,0,0,0,L,L,L,0,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,*,(33-128),*,*,*,*,*,*,*,*#

Note: (33-128) in the above example represents scenes 33 to 128.

Load Interface Maintenance Query Commands

When targeted at a load interface, the response will represent the maintenance property value.

The load interface must support the iDim Ballast range. For information, visit the iDim section of the Helvar Website.

70 - Query Lamp Running Hours

71 - Query Ballast Running Hours

72 - Query Maximum Voltage

73 - Query Minimum Voltage

74 - Query Maximum Temperature

75 - Query Minimum Temperature

Device State Query Commands

110 - Query Device State

E.g. disabled, lamp fault, missing, overtemperature, Function Test in progress, Function Test passed etc.

Command

Send: Command (110), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Returns the device state:

Command (110), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Device State (see table below)

ASCII Example

If you send the following Query Device State command (including the full address of the device):

>V:1,C:110,@2.2.1.1#

If the device has been disabled, then the reply will be:

?V:1,C:110,@2.2.1.1=1#

Raw Example

If you send the following Query Device State command (including the full address of the device):  

 0x0001006E  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the device has been disabled, then the reply will be:

 0x0101006E  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

The state of a device is described by the following set of flags:

111 - Query Device Is Disabled

Query whether the device has been disabled.

Command

Send: Command (111), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Returns the lamp state:

Command (111), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Device Disabled State (1=Disabled, 0=Enabled)

ASCII Example

If you send the following Query Device Is Disabled command (including the full address of the device):

>V:1,C:111,@1.1.2.58#

If the device has been disabled, then the reply will be:

?V:1,C:111,@1.1.2.58=1#

Raw Example

If you send the following Query Device Is Disabled command (including the full address of the device):  

 0x0001006F  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the device has been disabled, then the reply will be:

 0x0101006F  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

112 - Query Lamp Failure

Query whether the lamp has failed.

Command

Send: Command (112), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Returns the lamp state:

Command (112), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Lamp Failure State (1=Failed, 0=OK)

ASCII Example

If you send the following Query Lamp Failure command (including the full address of the device):

>V:1,C:112,@1.1.2.58#

If the lamp has failed, then the reply will be:

?V:1,C:112,@1.1.2.58=1#

Raw Example

If you send the following Query Lamp Failure command (including the full address of the device):  

 0x00010070  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the lamp has failed, then the reply will be:

 0x01010070  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

113 - Query Device Is Missing

Query whether the device is missing.

Command

Send: Command (113), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Returns a message indicating whether the device is missing or not:

Command (113), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Device Missing State (1=Missing, 0=Present)

ASCII Example

If you send the following Query Device Is Missing command (including the full address of the device):

>V:1,C:113,@2.2.1.1#

If the device is missing, then the reply will be:

?V:1,C:113,@2.2.1.1=1#

Raw Example

If you send the following Query Device Is Missing command (including the full address of the device):  

 0x00010072  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the device is missing, then the reply will be:

 0x01010072  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

114 - Query Device Is Faulty

Query whether the device is faulty.

Command

Send: Command (114), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Returns a message indicating whether the device is faulty or not:

Command (114), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Device Faulty State (1=Faulty, 0=OK)

ASCII Example

If you send the following Query Device Is Faulty command (including the full address of the device):

>V:1,C:114,@2.2.1.1#

If the device is faulty, then the reply will be:

?V:1,C:114,@2.2.1.1=1#

Raw Example

If you send the following Query Device Is Faulty command (including the full address of the device):  

 0x00010071  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the device is faulty, then the reply will be:

 0x01010071  0x00020002  0x00010001  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

129 - Query Emergency Battery Failure

Query whether the emergency ballast's battery has failed.

Command

Send: Command (129), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Returns the emergency battery state:

Command (129), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Battery Failure State (1=Failed, 0=OK)

ASCII Example

If you send the following Query Emergency Battery Failure command (including the full address of the device):

>V:1,C:129,@1.1.2.58#

If the emergency ballast's battery has failed, then the reply will be:

?V:1,C:129,@1.1.2.58=1#

Raw Example

If you send the following Query Emergency Battery Failure command (including the full address of the device):  

 0x00010081  0x00010001  0x00020058  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the emergency ballast's battery has failed, then the reply will be:

 0x01010081  0x00010001  0x00020058  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

Measurement / Input / Level Query Commands

150 - Query Measurement

For analogue types, e.g. light measurement (Multisensor), analogue input (Analogue Input Unit).

Command

Send: Command (150), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Subdevice (1..16)

Reply

Returns the measurement from the device / subdevice:

Command (150), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Subdevice (1..16), Measurement (1..100)

ASCII Example

If you send the following Query Measurement command (including the full address of the subdevice):

>V:1,C:150,@2.2.1.1.4#

If the measurement from the subdevice is 100, then the reply will be:

?V:1,C:150,@2.2.1.1.4=100#

Raw Example

If you send the following Query Measurement command (including the full address of the subdevice):  

 0x00010096  0x00020002  0x00010001  0x00040000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the measurement from the subdevice is 100, then the reply will be:

 0x01010096  0x00020002  0x00010001  0x00040000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000064

151 - Query Inputs

Returns the state or digital input(s) of: a device (e.g. for the PIR detector of a Multisensor - 0x01=occupied within past minute, 0x00=unoccupied); or the LEDs of a button panel; or the switch inputs of an input unit. If sent to the device level, summarises the digital input state. If sent to the subdevice level, gives the state of that subdevice’s input.

Command

Send: Command (151), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Subdevice (1..16)

Reply

Returns the input state of the device / subdevice:

Command (151), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Subdevice (1..16), Input State (see below)

The majority of subdevices have on and off states and are therefore represented by 0 (OFF) or 1 (ON). For example, buttons with LEDs will either be pressed (LED on) or not pressed (LED off). See below for the exceptions.

Mini Input Unit:           As there are 8 inputs on this device there will be 8 states e.g. 01001100 would be represented in ASCII as 50.

Slider:                        0..100 (level in %)

Analogue Input Unit:    0..100 (level in %)

ASCII Example

If you send the following Query Inputs command to a subdevice (including the full address of the subdevice):

>V:1,C:151,@2.2.1.1.4#

If the state of the subdevice is ON, then the reply will be:

?V:1,C:151,@2.2.1.1.4=1#

Raw Example

If you send the following Query Inputs command to a subdevice (including the full address of the subdevice):  

 0x00010097  0x00020002  0x00010001  0x00004000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the state of the subdevice is ON, then the reply will be:

 0x01010097  0x00020002  0x00010001  0x00004000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

152 - Query Load Level

Command

Send: Command (152), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (152), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Load Level (1..100)

ASCII Example

If you send the following Query Load Level command (including the full address of the device):

>V:1,C:152,@1.1.2.15#

If the load level is 25%, then the reply will be:

?V:1,C:152,@1.1.2.15=25#

Raw Example

If you send the following Query Load Level command (including the full address of the device):  

 0x00010098  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the load level is 25%, then the reply will be:

 0x01010098  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000019

ASCII Example

If you send the following Query Load Level command (including the full address of the device):

>V:1,C:152,@1.1.2.15#

If the load level is set at 1% and the switch on level is 2%, then the reply will be:

?V:1,C:152,@1.1.2.15=2147483649#

Raw Example

If you send the following Query Load Level command (including the full address of the device):  

 0x00010098  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the load level is 1% and the switch on level is 2%, then the reply will be:

 0x01010098  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x80000001

The ASCII and Raw reply responses, 2147483649 and 0x80000001 are synonymous. If these replies are returned following a query load level request then the device at the specified address is 'Off' even though it appears 'On'.

For further reference, the Raw Word table denotes the response to query load level command when device is set to 'off':

Power Consumption Query Commands

160 - Query Power Consumption

Query the power consumption of a device.

Command

Send: Command (160), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (160), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Power (in W)

ASCII Example

If you send the following Query Power Consumption command (including the full address of the device):

>V:1,C:160,@1.1.2.15#

If the power consumption of the device is 23 W, then the reply will be:

?V:1,C:160,@1.1.2.15=23#

Raw Example

If you send the following Query Power Consumption command (including the full address of the device):  

 0x000100A0  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the power consumption of the device is 15 W, then the reply will be:

 0x010100A0  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x0000000F

161 - Query Group Power Consumption

Query the power consumption of all devices in a group.

Command

Send: Command (161), Group (1..16383)

Reply

Command (161), Group (1..16383), Power Consumption (in Watts)

ASCII Example

If you send the following Query Group Power Consumption command (including the group number):

>V:1,C:161,G:16#

If the group's power consumption is 105 W, then the reply will be:

?V:1,C:161,G:16=105#

Raw Example

If you send the following Query Group Power Consumption command (including the group number):  

 0x000100A1  0x00000010  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the group's power consumption is 105 W, then the reply will be:

 0x010100A1  0x00000010  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000069

Emergency Test Query Commands

170 - Query Emergency Function Test Time

Command

Send: Command (170), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (170), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Emergency Function Test Time (hh:mm:ss dd-mmm-yyyy)

ASCII Example

If you send the following Query Emergency Function Test Time command (including the full address of the device):

>V:1,C:170,@1.1.2.15#

If the Emergency Function Test Time is 08:00 on 1st July 2009, then the reply will be:

?V:1,C:170,@1.1.2.15=08:00:00 01-Jul-2009#

Raw Example

The raw time value is calculated in seconds from 00:00:00, 1 January 1970.

If you send the following Query Emergency Function Test Time command (including the full address of the device):

 0x000100AA  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the Emergency Function Test Time is 08:00 on 1st July 2009, then the reply will be:

 0x010100AA  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x4A3DE880

171 - Query Emergency Function Test State

Command

Send: Command (171), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (171), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Emergency Function Test State (combinations of the following emergency state values).

Emergency State Values

ASCII Example

If you send the following Query Emergency Function Test Pending command (including the full address of the device):

>V:1,C:171,@1.1.2.15#

If the Emergency Function Test is pending, then the reply will be:

?V:1,C:171,@1.1.2.15=16#

Raw Example

If you send the following Query Emergency Function Test Pending command (including the full address of the device):  

 0x000100AB  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the Emergency Function Test is pending, then the reply will be:

 0x010100AB  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000010

172 - Query Emergency Duration Test Time

Command

Send: Command (172), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (172), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Emergency Duration Test Time (hh:mm:ss dd-mmm-yyyy)

ASCII Example

If you send the following Query Emergency Duration Test Time command (including the full address of the device):

>V:1,C:172,@1.1.2.15#

If the Emergency Duration Test Time is 06:00 on 1st January 2010, then the reply will be:

?V:1,C:172,@1.1.2.15=06:00:00#

Raw Example

The raw time value is calculated in seconds from 00:00:00, 1 January 1970.

If you send the following Query Emergency Duration Test Time command (including the full address of the device):  

 0x000100AC  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the Emergency Duration Test Time is 06:00 on 1st January 2010, then the reply will be:

 0x010100AC  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x4B306060

173 - Query Emergency Duration Test State

Command

Send: Command (173), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (173), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Emergency Duration Test Pending (combinations of the emergency state values described in command 171)

ASCII Example

If you send the following Query Emergency Duration Test Pending command (including the full address of the device):

>V:1,C:173,@1.1.2.15#

If the Emergency Duration Test is pending, then the reply will be:

?V:1,C:173,@1.1.2.15=16#

Raw Example

If you send the following Query Emergency Duration Test Pending command (including the full address of the device):  

 0x000100AD  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the Emergency Duration Test is pending, then the reply will be:

 0x010100AD  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000010

174 - Query Emergency Battery Charge

Query the remaining charge of the emergency ballast battery.

Command

Send: Command (174), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (174), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Emergency Battery Charge (0..100%)

ASCII Example

If you send the following Query Emergency Battery Charge command (including the full address of the emergency ballast):

>V:1,C:174,@1.1.2.15#

If the emergency ballast battery has 40% charge remaining, then the reply will be:

?V:1,C:174,@1.1.2.15=40#

Raw Example

If you send the following Query Emergency Battery Charge command (including the full address of the emergency ballast):

 0x000100AE  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the emergency ballast battery has 40% charge remaining, then the reply will be:

 0x010100AE  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000028

175 - Query Emergency Battery Time

Query the current total running time of the emergency ballast battery.

Command

Send: Command (175), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (175), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Emergency Battery Time (1 ... 255 hours)

ASCII Example

If you send the following Query Emergency Battery Time command (including the full address of the emergency ballast):

>V:1,C:175,@1.1.2.15#

If the emergency ballast battery running time has been 12 hours, then the reply will be:

?V:1,C:175,@1.1.2.15=12#

Raw Example

If you send the following Query Emergency Battery Time command (including the full address of the emergency ballast):

 0x000100AF  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the emergency ballast battery running time has been 12 hours, then the reply will be:

 0x010100AF  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x0000000C

176 - Query Emergency Total Lamp Time

Query the current total lamp running time from any power source.

Command

Send: Command (176), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255)

Reply

Command (176), Cluster (1..253), Router (1..254), Subnet (1..4), Device (1..255), Emergency Total Lamp Time (1 ... 1020 hours)

ASCII Example

If you send the following Query Emergency Total Lamp Time command (including the full address of the emergency ballast):

>V:1,C:176,@1.1.2.15#

If the emergency ballast total lamp running time has been 100 hours, then the reply will be:

?V:1,C:176,@1.1.2.15=100#

Raw Example

If you send the following Query Emergency Total Lamp Time command (including the full address of the emergency ballast):

 0x000100B0  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the emergency ballast total lamp running time has been 100 hours, then the reply will be:

 0x010100B0  0x00010001  0x0002000F  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000064

System Query Commands

185 - Query Time

Command

Send: Command (185)

Reply

Returns the local system time:

Command (185), Local System Time (hh:mm:ss dd-mmm-yyyy)

ASCII Example

If you send the following Query Time command:

>V:1,C:185#

If the time is 14:36:39 on 1st July 2009, then the reply will be:

?V:1,C:185=1245591399#

Raw Example

The raw time value is calculated in seconds from 00:00:00, 1 January 1970.

If you send the following Query Time command:

 0x000100B9  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the time is 14:36:39 on 1st July 2009, then the reply will be:

 0x010100B9  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x4A3E3767

186 - Query Longitude

Command

Send: Command (186)

Reply

Returns the longitude An imaginary line that extends from the North Pole to the South Pole of Earth. Each line is referred to by the angle between it and the line at 0 degrees longitude (known as the Greenwich Meridian). Each line is therefore known as an angle of longitude.:

Command (186), Longitude (H ddd0mm’ss” - where H = Hemisphere, d = degrees, m = minutes and s = seconds)

ASCII Example

If you send the following Query Longitude command:

>V:1,C:186#

If the longitude of your location is W 064° 38’21”, then the reply will be:

?V:1,C:186=232701#

Raw Example

Longitude is calculated from the raw value received as follows:

The calculation is as follows:

ddd0 = 185100 / 3600 = 51.416666666666666666666666666667 - 0.416666666666666666666666666667 (remainder) = 51

mm’ = 0.416666666666666666666666666667 (remainder) x 60 = 25.00000000000000000000000000002 - 0.00000000000000000000000000002 (remainder) = 25

ss” = 0.00000000000000000000000000002 (remainder) x 60 = 0.0000000000000000000000000012 = 0

If you send the following Query Longitude command:  

 0x000100BA  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the longitude of your location is W 064° 38’21”, then the reply will be:

 0x010100BA  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00038CFD

This is how you calculate the longitude values from this hexadecimal value:

0x00038CFD = 232701

ddd0 = 232701 / 3600 = 64.639166666666666666666666666667 - 0.639166666666666666666666666667 (remainder) = 64

mm’ = 0.639166666666666666666666666667 (remainder) x 60 = 38.35 - 0.35 (remainder) = 38

ss” = 0.35 (remainder) x 60 = 21

187 - Query Latitude

Command

Send: Command (187)

Reply

Returns the latitude An imaginary line that extends horizontally around the Earth. Each line is referred to by the angle between it and the line at 0 degrees latitude (known as the Equator). Each line is therefore known as an angle of latitude.:

Command (187), Latitude (H dd0mm’ss” - where H = Hemisphere, d = degrees, m = minutes and s = seconds)

ASCII Example

If you send the following Query Latitude command:

>V:1,C:187#

If the latitude of your location is N 64° 38’21”, then the reply will be:

?V:1,C:187=232701#

Raw Example

The raw latitude value is calculated as per the longitude value (see above),

If you send the following Query Latitude command:  

 0x000100BB  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the latitude of your location is N 64° 38’21”, then the reply will be:

 0x010100BB  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00038CFD

188 - Query Time Zone

Command

Send: Command (188)

Reply

Returns the timezone offset (difference in seconds, moving westward, between UTC and local time [GMT]):

Command (188), Time Difference (-12..12 hours)

ASCII Example: Central European Time [1 hour's time difference from GMT]

If you send the following Query Time Zone command:

>V:1,C:188#

If your location is in Central Europe at 1 hour ahead of Greenwich Mean time (GMT), then the reply will be:

??V:1,C:188=-3600#

ASCII Example: Central Time (US and Canada) [6 hours' time difference from GMT]

If you send the following Query Time Zone command:

>V:1,C:188#

If you are located at 6 hours offset from Greenwich Mean time (GMT), then the reply will be:

?V:1,C:188=21600#

Raw Example

If you send the following Query Time Zone command:  

 0x000100BC  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If you are located at 1 hour offset from Greenwich Mean time (GMT), then the reply will be:

 0x010100BC  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0xFFFFF1F0

189 - Query Daylight Saving Time

Command

Send: Command (189)

Reply

Returns the DST:

Command (189), DST (1=ON, 0=OFF)

ASCII Example

If you send the following Query DST command:

>V:1,C:189#

If Daylight Saving Time is enabled, then the reply will be:

?V:1,C:189=1#

Raw Example

If you send the following Query DST command:  

 0x000100BD  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If Daylight Saving Time is enabled, then the reply will be:

 0x010100BD  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000001

190 - Query Software Version

Query the router firmware version.

Command

Send: Command (190)

Reply

Returns the software version:

Command (190), Software Version (e.g. 4.2.2)

ASCII Example

If you send the following Query Software Version command:

>V:1,C:190#

If the router firmware version is 4.2.2, then the reply will be:

?V:1,C:190=67240448#

Raw Example

If you send the following Query Software Version command:

 0x000100BE  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000

If the router firmware version is 4.2.2, then the reply will be:

 0x010100BE  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x00000000  0x04020200

191 - Query HelvarNet Version

Query the HelvarNet An Ethernet I/O protocol which allows third party devices (e.g. AV equipment) to query and control a 910/920 router system and perform some basic system configuration, over an Ethernet (TCP/IP) connection. software version.

Command

Send: Command (191)

Reply

Returns the software version:

Command (191), HelvarNet Version (e.g. 1)

ASCII Example

If you send the following HelvarNet Software Version command:

>V:1,C:191#

If the HelvarNet version is 1, then the reply will be:

?V:1,C:191=1#

Raw Example

If you send the following Query Software Version command:

0x000100BF 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000

If the Designer software version is 4.2.2, then the reply will be:

0x010100BF 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000001

Related Topics

• Query Command Table

• Query Reply Tables

• Control Command Table

• Control Command Descriptions

• Configuration Command Descriptions

• Configuration Command Table

• HelvarNet Overview

• HelvarNet Routing Entries

• Messages

• Command Format

• DALI Logarithmic Dimming Levels

• Diagnostics