Периферийные устройства с интерфейсом RS-485 серии WB-xxxx/en: различия между версиями

Материал из Wiren Board
(Новая страница: «== How to install a new Modbus address on our RS-485 device== # Connect the device to the controller, ONLY this device should be connected via the BUS. #: '''If y…»)
(Новая страница: «== Device firmware update == Starting with the new firmware versions of the device, the firmware update functionality (firmware) via the Modbus Protocol is suppor…»)
Строка 134: Строка 134:




== Обновление прошивки устройства ==
== Device firmware update ==
Начиная с новых версий микропрограмм устройства поддерживается функционал обновления прошивки (микропрограммы) по протоколу Modbus. Это дает возможность расширять функциональные возможности устройств и устранять ошибки в микропрограммном обеспечении непосредственно на месте монтажа. Подробнее о перепрошивке устройств рассказано в статье [[WB-MCU-Flasher|Загрузка прошивок на устройства Wiren Board]]. Список версий прошивок, поддерживающих обновление, а также устройств, для которых эта функция реализована, можно найти в статье [[Firmware_Changelog]].
Starting with the new firmware versions of the device, the firmware update functionality (firmware) via the Modbus Protocol is supported. This makes it possible to extend the functionality of the devices and eliminate errors in the firmware directly at the installation site. Read more about flashing devices described in the article [[WB-MCU-Flasher|Download firmware to Wiren Board devices]]. A list of firmware versions that support the update, as well as devices for which this feature is implemented, can be found in [[Firmware_Changelog]].

Версия 17:07, 28 мая 2019

Другие языки:

We produce our own peripherals connected via RS-485 (Modbus).

They are guaranteed to be compatible with the Wiren Board controller and have the best software support.

Online store

Current models

Multichannel energy meter WB-MAP12H Map12h front.jpg
Multichannel energy meter WB-MAP6S MAP6S.JPG
3-phase energy meter WB-MAP3H Map3h shopped small.png
3-phase energy meter WB-MAP3E MAP3E.jpg
Bus couplers WB-MIO and WB-MIO-E MIO.png
Bus coupler WB-MGE WB-MGE.png
WB-MS - hybrid sensor WB-MS .png
WB-MSW v.3 - wall-mounted hybrid sensor WB-MSW3-front.JPG
2-channel relay module WB-MRM2-mini Mrm-2-mini .png
Modbus IR Remote Control WB-MIR v2 MIRv2.jpg
Powerful WB-MR3xV, WB-MR6xV Modbus Relay Modules MR3MR6.jpg
Modbus Relay Module WB-MRPS6 MRPS6-S-2.JPG
Most powerful Modbus Relay Module WB-MRWL3 MRWL3-side view.png
Modbus Relay Modules WB-MR6C WB-MR6C.png
WB-M1W2 - 1-Wire to Modbus bus coupler WB-M1W2.jpg
WB-MAI2-mini/CC analog input module WB-MAI2-pic.png
WB-MWAC - leakage sensor MWAC.JPG
16-channel pulse counter module MCM16 MCM16.JPG
8-channel pulse counter module MCM8 WB-MCM8.png

Current models for special solutions

WB-MR6F Modbus relay module for stepped control of two fans
Modbus Analog inputs module WB-MAI WB-mai.png

Discontinued models

How to install a new Modbus address on our RS-485 device

  1. Connect the device to the controller, ONLY this device should be connected via the BUS.
    If you connect several devices on the bus, their performance will be disrupted!
  2. Run the console commands:
service wb-mqtt-serial stop # stop the standard RS-485 driver
# In the next line, replace "158" with the new address (1 to 247) and "/dev/ttyAPP1" with the controller port to which the device is connected
modbus_client --debug -m rtu -s2 -pnone /dev/ttyAPP1 -a0x00 -t0x06 -r0x80 158 # write new address to device
service wb-mqtt-serial start # start the standard RS-485 driver again


Device firmware update

Starting with the new firmware versions of the device, the firmware update functionality (firmware) via the Modbus Protocol is supported. This makes it possible to extend the functionality of the devices and eliminate errors in the firmware directly at the installation site. Read more about flashing devices described in the article Download firmware to Wiren Board devices. A list of firmware versions that support the update, as well as devices for which this feature is implemented, can be found in Firmware_Changelog.