The devices have an LED, which indication can help you understand the operating mode of the device.
Boxer and RS485 indication
If the intercom does not reject calls to the analog handset, you must:
Make sure that there was a command to reject the call (SH/BOXER/MAC/CMND/Module#/RelayLine) 1. Make sure that the Line relay clicks, the LN_in and LN_out contacts are no longer short-circuited 2. Make sure that the Line passes through the LN_in and LN_out contacts of the module and does not have parallel connections from the call panel to the switch 3. If necessary, adjust the resistance of the tuning resistor R14 (located under the heat shrink) connected between the LN_in and LN_out terminals. By default it has a resistance of 120...150 Ohms.
Module IDs
Depending on the purpose of the module, it updates with the necessary firmware with a unique identifier. The values of firmware identifiers (id) depending on the purpose of the device are presented in the table below. You can view device identifiers in the INFO information message as the Module parameter: (A, B, C, D, E, F, G, H), where the serial number of the identifier is equal to its number (module with address 0 is A, 7 is H ).
MQTT commands The following communication format via MQTT Topic has been standardized: %topic%/%prefix%/<command>/<parameter> where %topic% is the device ID. To begin with, use a simple MAC device identification with a preamble. For example, for Boxer: SH/BOXER/<MAC> %prefix% can have one of the following values CMND - commands to control the device, or debugging information from the server STAT - the device reports a change in state or controlled parameter. For example, after executing the cmnd command, the device sends confirmation to the «stat» topic that the command has been completed TELE - periodic report on the status of the device and interfaces. Sending frequency is once per minute
MQTT Boxer and RS485 commands
MQTT Boxer and RS485 commands
Updating In the current implementation, updating occurs automatically. Each time it starts, the update server checks the relevance of the version and, if necessary, updates the devices. The software update file must be in Intel HEX386 format.
To update modules, they must be installed in the system. In cases where the modules incorrectly determine apartment numbers, the first thing you need to do is check that the update occurred correctly.
ATTENTION
For a successful update, you need to configure the port on the “Intercom network” so that the update server is available in it. If the server is unavailable, the update process will fail.
Results of executing the BOXER software update command
Execution result;Description;Possible causes of the error
{"result": 0, "reason": "Update successful"};Update completed successfully;-
{"result": 1, "reason": "DNS resolve error"};Error determining the IP address for the domain name of the TFTP server (update server);The DNS server is faulty or missing. The specified domain name does not exist.
{"result": 1, "reason": "TFTP error"};Error receiving data from TFTP server.;The TFTP server is faulty or missing. The specified update file is missing from the TFTP server
{"result": 1, "reason": "Invalid arguments"};Invalid command arguments specified;-
Domovoy RS485 software update algorithm via BOXER
Update algorithm: 1. The MQTT broker sends a request to update the software of a specific module, indicating the domain name/IP address of the TFTP server and the name of the software file; 2. Boxer sends a command to the module to launch the bootloader; 3. Boxer sends a command to the module to prepare to start the software update. If there is no response from the module, then an error code returns to MQTT and the software update cancels; 4. If a TFTP server domain name is specified, Boxer determines the IP address using DNS. If there is no response from DNS, then an error code returns to MQTT and the software update cancels; 5. Boxer requests a file from the TFTP server. If there is no response from TFTP, then an error code returns to MQTT and the software update cancels; 6. Boxer cyclically requests the following blocks from the TFTP server, verifies the data and sends it to the module for writing to Flash. If an error occurs during the process, an error code returns to MQTT and the software update cancels; 7. Boxer sends a command to the module to complete the software update. If there is no response from the module, then an error code returns to MQTT and the software update cancels; 8. Boxer sends a command to the module to launch the main software and sends a code for the successful completion of the software update to MQTT.
Results of executing the Domovoy RS485 software update command via BOXER
Execution result;Description;Possible causes of the error
{"result": 0, "reason": "Update successful"};Update completed successfully;-
{"result": 1, "reason": "Module update is already in progress"};The update process is already in progress. ;Re-sending a command to update the module software before the completion of the previous one.
{"result": 2, "reason": "Could not initialize module"};The module could not be initialized.; The module is missing or disabled. There are data packet losses on the communication line with the module.
{"result": 3, "reason": "DNS resolve error"};Error determining the IP address for the domain name of the TFTP server (update server).;The DNS server is faulty or missing. The specified domain name does not exist.
{"result": 4, "reason": "TFTP error"};Error receiving data from TFTP server.;The TFTP server is faulty or missing. The specified update file is missing from the TFTP server.
{"result": 5, "reason": "Software data are corrupt"};A software update file integrity violation has been detected.;Errors occur when transferring data over the network. The file on the TFTP server is damaged. There is no access to the TFTP server
{"result": 6, "reason": "Software write error or module not responding"};Writing software to the module error or there is no response from the module.;There is a malfunction of the module's EEPROM (Flash memory). There are data packets losses on the communication line with the module.
{"result": 7, "reason": " HTTP error"};Error receiving data from HTTP server.;The HTTP server is faulty or missing. The specified update file is missing from the HTTP server. There is no access to the HTTP server