Differences

This shows you the differences between two versions of the page.

--- en:sw:04-unipi-firmware [2020/05/22 11:56]
tomhora
+++ en:sw:04-unipi-firmware [2020/05/22 12:02]
tomhora [Firmware]
@@ Line 83: / Line 83: @@
 === Upgrading firmware in RS485 Modbus extensions ===
-xS/xG series extensions can be upgraded similarly. Instead of **fwspi** utility, just use the alternative named **fwserial** which is also included in the //unipi-firmware-tools// package (installed automatically with //unipi-firmware//). The command-line arguments are very similar as for the fwspi, except RS485 port specification.
+xS/xG series extensions can be upgraded similarly. Instead of **fwspi** utility, just use the alternative named **fwserial** which is also included in the //unipi-firmware-tools// package (installed automatically with //unipi-firmware//). The command-line arguments are very similar as for the fwspi, except serial port specification.
-<WRAP center round info 60%>
+<WRAP center round alert 80%>
-The -p (path) parameter must be set according to the RS485 used for the extension. See section [[en:hw:01-axon:portmap|]] to resolve the appropriate path for each RS485 available within your unit. For example, if extension is connected to //RS485-1/RS485-1.1//: <code>/opt/unipi/tools/fwserial -p /dev/ttyNS0 -P </code>.
+Make sure that there is no other application using/communicating on the used port and do not disconnect power to the Controller or Extension. Any of this will lead to bricking the extension.
+</WRAP>
+<WRAP center round info 80%>
+The -p (path) parameter must be set according to the used serial for the extension - see the [[en:hw:01-axon:portmap|]] to find proper serial port within your unit. For example, if extension is connected to //RS485-1/RS485-1.1//: <code>/opt/unipi/tools/fwserial -p /dev/ttyNS0 -P </code>.
 Note that the fwserial assumes that extension‘s Modbus address, baud rate and parity are in the factory-default state, ie **19200 baud 8N1 with address 15**.
 </WRAP>