Добрый день. Отвалилось устройство работающее по RS485. Устройство 6.9A/1G4 574
До сегодняшнего дня все работало нормально. Что было подключено и нормально работало? Блок ONOKOM для кондиционера haier. Сегодня вижу в интерфейсе, что все “красное”. Что я попытался предпринять для диагностики? Жива ли вообще линия, но modbus_client при остановленном сервисе wb-mqtt-serial выдает ошибку “ERROR occured!” Полез в журнал, там увидел повторяющееся предупреждение (см. скрин). Вижу на экране красным V_OUT_OK - может в этом проблема?
Прилагаю кусок лога mqtt-serial
17-04-2026 12:26:14.420 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:26:09.394 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:26:04.363 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:59.325 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:54.283 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:49.253 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:44.203 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:39.158 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:34.130 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:29.100 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:24.074 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:18.935 WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
17-04-2026 12:25:16.056 INFO: [serial client] Events are disabled for <modbus:166: reboot>
17-04-2026 12:25:16.056 INFO: [serial client] Events are disabled for <modbus:166: reboot>
17-04-2026 12:25:16.056 INFO: [serial client] Events are enabled for <modbus:166:coil: 5>
17-04-2026 12:25:16.056 INFO: [serial client] Events are enabled for <modbus:166:coil: 4>
17-04-2026 12:25:16.056 INFO: [serial client] Events are enabled for <modbus:166:coil: 3>
17-04-2026 12:25:16.056 INFO: [serial client] Events are enabled for <modbus:166:coil: 2>
17-04-2026 12:25:16.056 INFO: [serial client] Events are enabled for <modbus:166:coil: 1>
17-04-2026 12:25:16.056 INFO: [serial client] Events are enabled for <modbus:166:coil: 0>
17-04-2026 12:25:15.857 INFO: [serial device] device modbus:166 is connected
17-04-2026 12:25:15.857 WARNING: [modbus] failed to write: <modbus:166:holding: 5>: Serial protocol error: illegal data address
17-04-2026 12:25:15.823 INFO: [modbus] Continuous read enabled [slave_id is 166]
17-04-2026 12:25:15.823 INFO: [modbus] Continuous read enabled [slave_id is 166]
17-04-2026 12:25:14.410 WARNING: [serial device] device modbus:001 is disconnected
17-04-2026 12:25:14.410 WARNING: [modbus] failed to read 1 holding(s) @ 1 of device modbus:001: Serial protocol error: request timed out
17-04-2026 12:25:14.103 INFO: [serial client] Events are disabled for <modbus:123: reboot>
17-04-2026 12:25:14.103 INFO: [serial client] Events are enabled for <modbus:123:coil: 5>
17-04-2026 12:25:14.103 INFO: [serial client] Events are enabled for <modbus:123:coil: 4>
17-04-2026 12:25:14.103 INFO: [serial client] Events are enabled for <modbus:123:coil: 3>
17-04-2026 12:25:14.103 INFO: [serial client] Events are enabled for <modbus:123:coil: 2>
17-04-2026 12:25:14.103 INFO: [serial client] Events are enabled for <modbus:123:coil: 1>
17-04-2026 12:25:14.103 INFO: [serial client] Events are enabled for <modbus:123:coil: 0>
17-04-2026 12:25:14.103 INFO: [serial client] Events are enabled for <modbus:123:coil: 0>
