You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: www/docs/guide/fault-finding.md
+16-8
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ If you fail to get a reply from the inverter, typically if step #2 fails, please
37
37
## (A) Cabling & connection
38
38
39
39
While fault finding use as short as possible cable, outside any sprague/trunking. Once
40
-
everything is working, you can switch to a more permanent, much longer cable.
40
+
everything works, you can switch to a more permanent, much longer cable.
41
41
42
42
If you cannot establish a connection, check the RS485 adaptor and cabling. Are you
43
43
plugged into the correct port, is your connector crimped correctly?
@@ -64,12 +64,6 @@ Other factors that might impact connection, or reliability:
64
64
65
65
## (B) Configuration
66
66
67
-
### Only a single connection to the serial port
68
-
69
-
Ensure you only have a single addon connected to the serial port. The following can all potentially access the USB port: mbusd, Node RED, the normal and dev addon version.
70
-
71
-
If you need to have multiple connections to the serial port: ONLY connect mbusd to the serial port. Connect all addons to mbusd (e.g. tcp://192.168.1.x:503).
72
-
73
67
### Check the Modbus Server ID
74
68
75
69
Ensure the Modbus Server ID (`MODBUS_ID` config setting) matches the configured **Modbus SN** value of the inverter. This value must not be zero.
@@ -80,6 +74,12 @@ Please note that this can be reset to zero after a software upgrade on your inve
Ensure you only have a single addon connected to the serial port. The following can all potentially access the USB port: mbusd, Node RED, the normal and dev addon version.
80
+
81
+
If you need to have multiple connections to the serial port: ONLY connect mbusd to the serial port. Connect all addons to mbusd (e.g. tcp://192.168.1.x:503).
82
+
83
83
## (C) Reducing timeouts
84
84
85
85
If you get many timeouts, or if the addon does not read all your sensors on startup (i.e. you see **Retrying individual sensors** in the log), you can try the following:
@@ -89,6 +89,14 @@ If you get many timeouts, or if the addon does not read all your sensors on star
89
89
90
90
Check the cabling and connection again. Use a 1m cable and stand next to the inverter while testing.
91
91
92
+
### Direct serial
93
+
94
+
If your RS485 adaptor is plugged directly into your host, connecting directly to the serial port `PORT: "/usb/ttyX"` might not give you the best results.
95
+
96
+
Once you have a working connection (reading the serial), consider introducing **mbusd** into your setup, in this configuration mbus connects to the serial port and the addon connects via TCP, typically: `PORT: tcp://homeassistant.local:502`
97
+
98
+
**mbusd** and the *pymodbus* driver gives the best results.
99
+
92
100
### Check line voltage / termination resistor
93
101
94
102
If your RS485 adapter has a termination resistor (typically 120 ohms), try removing it.
@@ -101,4 +109,4 @@ but this may drop to around 0.5v with the 120 ohm load.
101
109
RS485 devices are typically multi-drop with a termination resistor on the first and last devices.
102
110
However, the RS485 BMS port may only be intended to connect to a single device.
0 commit comments