Novus LOGBOX, Instruction Manual

NOVUS AUTOMATION

20/53

7.2

INSCRIPTION TOPIC 

When connected to a Broker, 

LogBox Wi-Fi

 can receive commands that will be answered through the 

novus/<sn>

*

/response

 topic, as can be 

seen below. 

Commands in this topic can only be sent to the Broker if they have write permission enabled in the NXperience software 

(see 

MQTT Protocol

 section of the 

Configuration Software

 chapter). 

•

novus/<sn>

*

/command: 

Topic for receiving commands sent via MQTT. 

Example:

 {"buzzer_state":0} 

Command 

Type

Example 

Description

anl1_spa_high 

Double 

{"anl1_spa_high":10} 

Allows you to change the channel 1 higher alarm setpoint if the device is 

configured to allow such a configuration (see 

Analog Channels Parameters

section of the 

Configuration Software

 chapter). 

anl1_spa_low 

Double 

{"anl1_spa_low":0} 

Allows you to change the channel 1 lower alarm setpoint if the device is 

configured to allow such a setting  (see 

Analog Channels Parameters

section of the 

Configuration Software

 chapter). 

anl2_spa_high 

Double 

{"anl2_spa_high":10} 

Allows you to change the channel 2 higher alarm setpoint if the device is 

configured to allow such a configuration (see 

Analog Channels Parameters

section of the 

Configuration Software

 chapter). 

anl2_spa_low 

Double 

{"anl2_spa_low":0} 

Allows you to change the channel 2 lower alarm setpoint if the device is 

configured to allow such a setting  (see 

Analog Channels Parameters

section of the 

Configuration Software

 chapter). 

anl3_spa_high 

Double 

{"anl3_spa_high":10} 

Allows you to change the channel 3 higher alarm setpoint if the device is 

configured to allow such a configuration (see 

Analog Channels Parameters

section of the 

Configuration Software

 chapter). 

anl3_spa_low 

Double 

{"anl3_spa_low":0} 

Allows you to change the channel 2 lower alarm setpoint if the device is 

configured to allow such a setting  (see 

Analog Channels Parameters

section of the 

Configuration Software

 chapter). 

dig_spa_high 

Double 

{"dig_spa_high":1} 

Allows you to change the higher alarm setpoint of the digital channel if the 

device is configured to allow such a configuration (see 

Analog Channels 

Parameters

 section of the 

Configuration Software

 chapter). 

dig_spa_low 

Double 

{"dig_spa_low":0}

}

Allows you to change the lower alarm setpoint of the digital channel if the 

device is configured to allow such a configuration (see 

Analog Channels 

Parameters

 section of the 

Configuration Software

 chapter). 

buzzer_state 

Booleana 

{"buzzer_state":1} 

It informs the current state of the buzzer, according to the parameter 

established in the Boolean settings of the sent command.  
See the 

Boolean Format

 section of this chapter for more information about 

Boolean types and formats. 

internal_clock 

Unix Timestamp or 

TDateTime 

{"internal_clock":1533294048} 

If Unix format 

{"internal_clock":43277.40465278} 

If TDateTime format 

Displays the device's internal clock.  
This parameter must be written with the same Timestamp format defined in 

NXperience

. 

See the 

Timestamp

 section of this chapter for more information on the 

formats supported by the device. 

set_download 

Unix Timestamp or 

TDateTime 

{"set_download":1533294048} 

If Unix format 

{"set_download":43277.40465278} 

If TDateTime format 

Command used to request that 

LogBox Wi-Fi

 resend all logs from the 

requested date in the "

/log/channels

" and "

/log/event

" topics (see 

Logs 

Topics

 section of this chapter). 

This parameter must be written with the same Timestamp format defined in 

NXperience

. 

See the 

Timestamp

 section of this chapter for more information on the 

formats supported by the device. 

Table 05 

– Command list 

If successful, the device will send a message that can be viewed in the response topic 

novus/<sn>

*

/response

, as described in the 

Response 

Topic

 section of this chapter. 

If there is any kind of error during the command request, the device will still send a response via the 

novus/<sn>

*

/response

 topic, but it will inform 

the type of error found, as described in 

Table 6

. 

Example:  

Command: 

{"buzzer_state":0}

Answer: 

{"config_receive":"fail","error_type":"NOT_AUTHORIZED_ERROR","parameter":"buzzer_state"} 

*

The 

<sn>

 is the device serial number. That way, there will be no clash of topics in the Broker.