История
27 августа 2024
Нет описания правки
−61
Нет описания правки
−190
Нет описания правки
−138
Новая страница: «== Useful links == * Restoring access — resetting communication settings * Modbus address of the Wiren Board device * Firmware update and recovery utility wb-mcu-fw-updater * Service utility wb-mcu-fw-flasher * Firmware Repository For Wiren Board Modbus Devices | Firmware repository for Wiren Board Modbus devic...»
−215
Новая страница: «#connect the gateway to the computer using a UTP cable directly or through a router, #assign a static IP address to the computer in the gateway network, for example, 192.168.0.201, #open a browser and enter the gateway's IP address, by default 192.168.0.7.»
−167
Новая страница: «The easiest way to change the gateway settings is to connect to its built-in web interface. To do this, you need to:»
−146
Новая страница: «===Configuring the gateway for updating the firmware===»
−81
Новая страница: «If you need to flash several devices, you can first modify their speed, reconfigure the gateway, and then flash them one by one, restore their original speed, and reconfigure the gateway again.»
−1177
Новая страница: «We also recommend updating the bootloader if its version is 1.3.0 . This will allow you to update the firmware at any speed of connection any connection speed.»
−437
Новая страница: «===Updating with default connection settings=== This instruction is used for devices where the current bootloader version is below '''1.3.0''' and/or the current firmware does not support '''131''' register.»
−393
Новая страница: «#Prepare the firmware file and install the socat utility if it is not installed: #:<syntaxhighlight lang="bash"> apt install socat </syntaxhighlight> #Connect twice to the controller via SSH, you should have two windows open: the first one for creating a socat tunnel, the second one for sending commands to the device. #Stop wb-mqtt-serial: #:<syntaxhighlight lang="bash"> systemctl stop wb-mqtt-serial </syntaxhighlight> #In the first window, start redirecting...»
−543
Новая страница: «Below is an example with the following input data:»
−100
Новая страница: «'''Otherwise, the update can only be performed with standard 9600N2 connection settings.'''»
−131
Новая страница: «===Update at any connection speed===»
−379
Новая страница: «The gateway must be set to TCP Server/None mode (for WB-MGE v2, WB-MIO-E v2) or TCP Server mode (for WB-MGE v1, WB-MIO-E v1).»
−300
Новая страница: «==Updating firmware of devices connected to WB-MGE and WB-MIO-E gateways== 350px|thumb|right|Gateway settings for firmware update To update the firmware of a Wiren Board device connected to the WB-MGE and WB-MIO-E gateways via RS-485, it can only be done manually using the wb-mcu-fw-flasher utility. However, firs...»
−238
Новая страница: «Here we flashed the device in bootloader mode with Modbus address <code>25</code> connected to port <code>/dev/ttyRS485-1</code> (<code>COM1</code>) using the file <code>firmware.wbfw</code>.»
−544
Новая страница: «=== Manually === If you cannot use wb-mcu-fw-updater, you can restore the firmware of devices using the service utility wb-mcu-fw-flasher. This method can also be used by Windows computer users.»
−253
Новая страница: «For more information on the recover and recover-all modes, read the documentation in the documentation.»
−64
Новая страница: «To recover the device with address <code>10</code> and connected to port <code>/dev/ttyRS485-1</code>, execute the command: <syntaxhighlight lang="bash"> wb-mcu-fw-updater recover /dev/ttyRS485-1 -a 10 </syntaxhighlight>»
−130
Новая страница: «=== Automatically === To automatically restore the firmware of one or multiple devices, you can use the utility wb-mcu-fw-updater in the modes '''recover''' and '''recover-all'''.»
−180
Новая страница: «== Restoring the device firmware == {{Anchor|fw-recovery}} If an error occurred during the update, the device will enter the bootloader mode and you can restore its firmware.»
−201
Новая страница: «If the device signature and firmware file do not match, you will receive an error message: <syntaxhighlight lang="bash"> Sending info block... Error while sending info block: Slave device or server failure Data format is invalid or firmware signature doesn't match the device </syntaxhighlight>»
−131
Новая страница: «A successful firmware update process looks like this: <syntaxhighlight lang="bash"> ~# wb-mcu-fw-flasher -j -d /dev/ttyRS485-1 -a 25 -f mr6c__1.15.5_master_971fe50.wbfw /dev/ttyRS485-1 opened successfully. Send jump to bootloader command and wait 2 seconds... Ok, device will jump to bootloader. mr6c__1.15.5_master_971fe50.wbfw opened successfully, size 14720 bytes»
−76
Новая страница: «In the above command, using the <code>-j</code> flag, we switched the device connected to the port <code>/dev/ttyRS485-1</code> (<code>COM1</code>) with address <code>25</code> to bootloader mode and then flashed it.»
−570
Новая страница: «To flash multiple devices on the bus, you need to sequentially switch them to the bootloader mode and flash them.»
−130
Новая страница: «Devices can be flashed in the following ways: * by the device's Modbus address. * by the broadcast address, which is <code>0</code>.»
−101
Новая страница: «=== Device preparation ===»
−79
Новая страница: «Manual update can be done with the utility '''wb-mcu-fw-flasher''', which needs to be installed beforehand. The installation method varies and depends on the operating system being used.»
−203
Новая страница: «== Manual Update == {{Anchor|manual}} === Features === This method is used if: * there is no internet access at the object, * you do not have a controller, * you are updating the firmware of devices, connected through WB-MGE and WB-MIO-E gateways.»
−403
Новая страница: «For the full list of parameters and examples of usage, refer to the utility page.»
−107
Новая страница: «For example, let's update the firmware of a device with a modbus address of <code>70</code> connected to port <code>/dev/ttyRS485-1</code>: <syntaxhighlight lang="bash"> wb-mcu-fw-updater update-fw /dev/ttyRS485-1 -a70 </syntaxhighlight>»
−102
Новая страница: «=== Updating a Single Device === To update only one device: # Connect the device via RS-485 to the controller. # Determine the Modbus address of the device you want to update. # Open the controller console via SSH. # Run the utility <code>wb-mcu-fw-updater</code> with the following parameters: the <code>update-fw</code> key, as well as the port and Modbus address.»
−255
Новая страница: «=== Updating all devices on the bus === You can update all devices configured in the '''Serial Devices Configuration''' section of the web interface # Connect the devices via the RS-485 bus to the controller. # Configure the connected devices in the web interface. # Open the controller's console via SSH. # Update all configured devices with the following command: #:<synta...»
−281
Новая страница: «Updating firmware on devices connected to WB-MGE and WM-MIO-E gateways is also performed manually with displaying the network port to local.»
−350
Новая страница: «The utility only works on our controller and requires internet access. If you do not have internet or our controller, refer to the section Manual Update.»
−193
Новая страница: «== Automatic firmware update == 500px|thumb|right|Example of wb-fw-mcu-updater operation {{note|info|When updating the firmware, IR commands stored in WB-MSW and WB-MIR devices are deleted. We recommend saving command banks before updating using the script.}} Automatic firmware update is performed using the utility wb-mcu-fw-updater pre...»
−499
Новая страница: «Distributing firmware updates by releases helps prevent a situation where a new firmware version, without undergoing thorough testing, ends up in a very critical installation. If the new firmware requires new features in the controller's software, either these features will be included in the stable software release along with the firmware, or the firmware update will be delayed in testing until the required features appear in the software.»
−575
Новая страница: «The firmware itself is released in the format of releases, which are linked to controller software releases, but have a different cycle: *'''testing''' — firmware that has passed internal testing lands here, available to users of the controller's testing release; *'''stable''' — three weeks after being published in testing and with no error reports, the firmware is considered stable. At this point, it becomes available t...»
−540
Новая страница: «{{DISPLAYTITLE:Updating Wiren Board Modbus Device Firmware}} == General Information == {{PeerTube | link= https://peertube.wirenboard.com/video-playlists/embed/6623c76e-1abe-4728-959c-f5dde919d80c?playlistPosition=8 | playlist = true | text=Updating Device Firmware (24:08) }} Wiren Board modbus devices have a bootloader, which allows updating firmware via RS-485/Modbus RTU. In bootloader mode, the main functions of the device are disabled, an...»
−343
Обновление для соответствия новой версии исходной страницы.
+20 707
28 мая 2020
26 апреля 2019
25 апреля 2019
Нет описания правки
−23
Новая страница: «'''Attention!''' The flashing of the devices in bootloader mode and of the same modbus address, or the flashing of multiple devices being in the bootloader mode a…»
−211
Новая страница: «It is possible to flash several devices connected to the bus. The devices must be set to bootloader mode and flashed separately with a non-broadcast Modbus addres…»
−305
Новая страница: «=== Flashing several devices on the bus ===»
−35
Новая страница: «Bootloader allows you to download firmware to devices via Modbus address 0. To do this, the device must be the only device on the bus and must be in bootloader mode.»
−137