Периодически отваливаются устройства на шине Wb-MGE

Периферийные устройства Шлюзы WB-MIO и WB-MGE
1

Система на базе WB8. Линия, где мастером выступает WB-MGE, очень странно себя ведет. Там всего 3 устройства (датчик WB-MSW v.4 слэйв 26, реле WB-MR6C v.2 слэйв 14, WB-MWAC v.2 слэйв 165), питание 12в (просадок по питанию нет, стабильно больше 11,9в), линия очень короткая (около 2м), сейчас настроена на 9600 без терминаторов (до этого было 115200 с терминатором физическим и в WB-MGE- пробовал по разному), общается с контроллером по WI-FI точке контроллера (т.е. сеть из 2 устройств), но пробовал и через роутер, настроена как прозрачный RTU - периодически на шине отваливаются устройства на 10-100сек, пробовал менять тайминги таймаута и записи в порт (сейчас 1000 и 5000) - ничего не дает. Не могу понять где кроется проблема. В день может быть от 1-2 до 10-15 отвалов. Проводная (вторая) линия от контроллера вроде бы стабильная. Полные логи и диагностику приложил
Верхушка логов:

Часть логов

wb-mqtt-serial.service (2026-01-13T18:30:17.250Z - 2026-01-12T22:50:53.620Z)

2026-01-13T18:30:17.250Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:30:11.971Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 coil(s) @ 4 of device modbus:165: Serial protocol error: request timed out
2026-01-13T18:30:10.461Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:30:08.776Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 input(s) @ 283 of device modbus:26: Serial protocol error: request timed out
2026-01-13T18:30:04.651Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:54.350Z [wb-mqtt-serial] INFO: [serial client] Events are disabled for <modbus:26: reboot>
2026-01-13T18:29:54.348Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:26:input: 283>
2026-01-13T18:29:54.136Z [wb-mqtt-serial] INFO: [serial device] device modbus:26 is connected
2026-01-13T18:29:54.134Z [wb-mqtt-serial] INFO: [modbus] Init setup register “CO₂ Sensor Enabled”: <modbus:26:coil: 3><-- 0 (0x0)
2026-01-13T18:29:54.086Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Safety Action”: <modbus:26:holding: 956><-- 0 (0x0)
2026-01-13T18:29:54.041Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Safety Poll Timeout (s)”: <modbus:26:holding: 955><-- 6000 (0x1770)
2026-01-13T18:29:53.992Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Baud rate”: <modbus:26:holding: 110><-- 96 (0x60)
2026-01-13T18:29:53.942Z [wb-mqtt-serial] INFO: [modbus] Init setup register “CO₂ Baseline Calibration”: <modbus:26:holding: 95><-- 0 (0x0)
2026-01-13T18:29:53.894Z [wb-mqtt-serial] INFO: [modbus] Continuous read enabled [slave_id is 26]
2026-01-13T18:29:49.750Z [wb-mqtt-serial] WARNING: <192.168.42.153:502>: closed due to repetitive errors
2026-01-13T18:29:48.247Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:47.743Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:47.240Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:45.233Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:44.730Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:44.226Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:43.722Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 discrete(s) @ 3 of device modbus:14: Serial protocol error: request timed out
2026-01-13T18:29:42.211Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:41.708Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:41.204Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:40.700Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 coil(s) @ 4 of device modbus:165: Serial protocol error: request timed out
2026-01-13T18:29:39.189Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:36.760Z [wb-mqtt-serial] WARNING: <192.168.42.153:502>: closed due to repetitive errors
2026-01-13T18:29:35.256Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:34.753Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:34.249Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:33.748Z [wb-mqtt-serial] WARNING: [serial device] device modbus:26 is disconnected
2026-01-13T18:29:33.744Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 input(s) @ 5 of device modbus:26: Serial protocol error: request timed out
2026-01-13T18:29:32.242Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:31.738Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:31.234Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 input(s) @ 4 of device modbus:26: Serial protocol error: request timed out
2026-01-13T18:29:29.731Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:03.211Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:02.708Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:29:02.204Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:56.484Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:55.980Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 discrete(s) @ 3 of device modbus:14: Serial protocol error: request timed out
2026-01-13T18:28:54.469Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:53.966Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:53.462Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:52.958Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 input(s) @ 283 of device modbus:26: Serial protocol error: request timed out
2026-01-13T18:28:51.453Z [wb-mqtt-serial] INFO: [serial client] Events are disabled for <modbus:26: reboot>
2026-01-13T18:28:51.451Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:26:input: 283>
2026-01-13T18:28:51.242Z [wb-mqtt-serial] INFO: [serial device] device modbus:26 is connected
2026-01-13T18:28:51.240Z [wb-mqtt-serial] INFO: [modbus] Init setup register “CO₂ Sensor Enabled”: <modbus:26:coil: 3><-- 0 (0x0)
2026-01-13T18:28:51.197Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Safety Action”: <modbus:26:holding: 956><-- 0 (0x0)
2026-01-13T18:28:51.152Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Safety Poll Timeout (s)”: <modbus:26:holding: 955><-- 6000 (0x1770)
2026-01-13T18:28:51.107Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Baud rate”: <modbus:26:holding: 110><-- 96 (0x60)
2026-01-13T18:28:51.060Z [wb-mqtt-serial] INFO: [modbus] Init setup register “CO₂ Baseline Calibration”: <modbus:26:holding: 95><-- 0 (0x0)
2026-01-13T18:28:50.999Z [wb-mqtt-serial] INFO: [modbus] Continuous read enabled [slave_id is 26]
2026-01-13T18:28:50.700Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:50.197Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:49.697Z [wb-mqtt-serial] WARNING: [serial device] device modbus:26 is disconnected
2026-01-13T18:28:49.692Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 input(s) @ 5 of device modbus:26: Serial protocol error: request timed out
2026-01-13T18:28:48.189Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:47.685Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:47.181Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:46.677Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 input(s) @ 4 of device modbus:26: Serial protocol error: request timed out
2026-01-13T18:28:45.174Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:44.671Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:43.462Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 coil(s) @ 4 of device modbus:165: Serial protocol error: request timed out
2026-01-13T18:28:41.951Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:41.447Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:22.527Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:22.023Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 discrete(s) @ 3 of device modbus:14: Serial protocol error: request timed out
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are disabled for <modbus:14: reboot>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:input: 499>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:input: 483>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:discrete: 3>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:coil: 5>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:coil: 4>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:coil: 3>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:coil: 2>
2026-01-13T18:28:20.509Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:coil: 1>
2026-01-13T18:28:20.507Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:14:coil: 0>
2026-01-13T18:28:20.279Z [wb-mqtt-serial] INFO: [serial device] device modbus:14 is connected
2026-01-13T18:28:20.279Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Use outputs 5 and 6 for curtain 3 control”: <modbus:14:holding: 1282><-- 0 (0x0)
2026-01-13T18:28:20.221Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Use outputs 3 and 4 for curtain 2 control”: <modbus:14:holding: 1281><-- 0 (0x0)
2026-01-13T18:28:20.177Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Use outputs 1 and 2 for curtain 1 control”: <modbus:14:holding: 1280><-- 0 (0x0)
2026-01-13T18:28:20.134Z [wb-mqtt-serial] INFO: [modbus] Init setup register “secp_waiting_time_title”: <modbus:14:holding: 1143><-- 300 (0x12c)
2026-01-13T18:28:20.074Z [wb-mqtt-serial] INFO: [modbus] Init setup register “secp_waiting_time_title”: <modbus:14:holding: 1142><-- 300 (0x12c)
2026-01-13T18:28:20.021Z [wb-mqtt-serial] INFO: [modbus] Init setup register “secp_waiting_time_title”: <modbus:14:holding: 1141><-- 300 (0x12c)
2026-01-13T18:28:19.968Z [wb-mqtt-serial] INFO: [modbus] Init setup register “secp_waiting_time_title”: <modbus:14:holding: 1140><-- 300 (0x12c)
2026-01-13T18:28:19.925Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_hold_time_title”: <modbus:14:holding: 1103><-- 1000 (0x3e8)
2026-01-13T18:28:19.881Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_hold_time_title”: <modbus:14:holding: 1102><-- 1000 (0x3e8)
2026-01-13T18:28:19.830Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_hold_time_title”: <modbus:14:holding: 1101><-- 1000 (0x3e8)
2026-01-13T18:28:19.783Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_hold_time_title”: <modbus:14:holding: 1100><-- 1000 (0x3e8)
2026-01-13T18:28:19.734Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 6”: <modbus:14:holding: 951><-- 0 (0x0)
2026-01-13T18:28:19.675Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 5”: <modbus:14:holding: 950><-- 0 (0x0)
2026-01-13T18:28:19.627Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 4”: <modbus:14:holding: 949><-- 0 (0x0)
2026-01-13T18:28:19.579Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 3”: <modbus:14:holding: 948><-- 0 (0x0)
2026-01-13T18:28:19.530Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 2”: <modbus:14:holding: 947><-- 0 (0x0)
2026-01-13T18:28:19.478Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 1”: <modbus:14:holding: 946><-- 0 (0x0)
2026-01-13T18:28:19.434Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 6”: <modbus:14:holding: 943><-- 0 (0x0)
2026-01-13T18:28:19.388Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 5”: <modbus:14:holding: 942><-- 0 (0x0)
2026-01-13T18:28:19.338Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 4”: <modbus:14:holding: 941><-- 0 (0x0)
2026-01-13T18:28:19.295Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 3”: <modbus:14:holding: 940><-- 0 (0x0)
2026-01-13T18:28:19.251Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 2”: <modbus:14:holding: 939><-- 0 (0x0)
2026-01-13T18:28:19.190Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 1”: <modbus:14:holding: 938><-- 0 (0x0)
2026-01-13T18:28:19.146Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 6”: <modbus:14:holding: 935><-- 0 (0x0)
2026-01-13T18:28:19.097Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 5”: <modbus:14:holding: 934><-- 0 (0x0)
2026-01-13T18:28:19.053Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 4”: <modbus:14:holding: 933><-- 0 (0x0)
2026-01-13T18:28:19.010Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 3”: <modbus:14:holding: 932><-- 0 (0x0)
2026-01-13T18:28:18.966Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 2”: <modbus:14:holding: 931><-- 0 (0x0)
2026-01-13T18:28:18.922Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Output 1”: <modbus:14:holding: 930><-- 0 (0x0)
2026-01-13T18:28:18.879Z [wb-mqtt-serial] INFO: [modbus] Init setup register “dp_title”: <modbus:14:holding: 684><-- 3 (0x3)
2026-01-13T18:28:18.824Z [wb-mqtt-serial] INFO: [modbus] Init setup register “dp_title”: <modbus:14:holding: 677><-- 3 (0x3)
2026-01-13T18:28:18.780Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 626><-- 1 (0x1)
2026-01-13T18:28:18.736Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 625><-- 1 (0x1)
2026-01-13T18:28:18.691Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 624><-- 1 (0x1)
2026-01-13T18:28:18.648Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 618><-- 1 (0x1)
2026-01-13T18:28:18.602Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 617><-- 1 (0x1)
2026-01-13T18:28:18.555Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 616><-- 1 (0x1)
2026-01-13T18:28:18.508Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 610><-- 1 (0x1)
2026-01-13T18:28:18.463Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 609><-- 1 (0x1)
2026-01-13T18:28:18.413Z [wb-mqtt-serial] INFO: [modbus] Init setup register “lp_title”: <modbus:14:holding: 608><-- 1 (0x1)
2026-01-13T18:28:18.370Z [wb-mqtt-serial] INFO: [modbus] Init setup register “sp_title”: <modbus:14:holding: 571><-- 3 (0x3)
2026-01-13T18:28:18.327Z [wb-mqtt-serial] INFO: [modbus] Init setup register “sp_title”: <modbus:14:holding: 562><-- 3 (0x3)
2026-01-13T18:28:18.276Z [wb-mqtt-serial] INFO: [modbus] Init setup register “sp_title”: <modbus:14:holding: 553><-- 3 (0x3)
2026-01-13T18:28:18.229Z [wb-mqtt-serial] INFO: [modbus] Init setup register “sp_title”: <modbus:14:holding: 544><-- 3 (0x3)
2026-01-13T18:28:18.186Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Baud rate”: <modbus:14:holding: 110><-- 96 (0x60)
2026-01-13T18:28:18.140Z [wb-mqtt-serial] INFO: [modbus] Init setup register “debounce_time_title”: <modbus:14:holding: 23><-- 50 (0x32)
2026-01-13T18:28:18.097Z [wb-mqtt-serial] INFO: [modbus] Init setup register “debounce_time_title”: <modbus:14:holding: 22><-- 50 (0x32)
2026-01-13T18:28:18.054Z [wb-mqtt-serial] INFO: [modbus] Init setup register “debounce_time_title”: <modbus:14:holding: 21><-- 50 (0x32)
2026-01-13T18:28:18.007Z [wb-mqtt-serial] INFO: [modbus] Init setup register “debounce_time_title”: <modbus:14:holding: 20><-- 50 (0x32)
2026-01-13T18:28:17.964Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Mode”: <modbus:14:holding: 16><-- 2 (0x2)
2026-01-13T18:28:17.921Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Mode”: <modbus:14:holding: 14><-- 0 (0x0)
2026-01-13T18:28:17.878Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Mode”: <modbus:14:holding: 13><-- 0 (0x0)
2026-01-13T18:28:17.828Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Mode”: <modbus:14:holding: 12><-- 6 (0x6)
2026-01-13T18:28:17.784Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Mode”: <modbus:14:holding: 11><-- 6 (0x6)
2026-01-13T18:28:17.739Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Mode”: <modbus:14:holding: 10><-- 6 (0x6)
2026-01-13T18:28:17.695Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Mode”: <modbus:14:holding: 9><-- 6 (0x6)
2026-01-13T18:28:17.649Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Safety Poll Timeout (s)”: <modbus:14:holding: 8><-- 1000 (0x3e8)
2026-01-13T18:28:17.598Z [wb-mqtt-serial] INFO: [modbus] Init setup register “Outputs State After Power On”: <modbus:14:holding: 6><-- 0 (0x0)
2026-01-13T18:28:17.555Z [wb-mqtt-serial] INFO: [modbus] Init setup register “disable legacy input mode control”: <modbus:14:holding: 5><-- 0 (0x0)
2026-01-13T18:28:17.511Z [wb-mqtt-serial] INFO: [modbus] Continuous read enabled [slave_id is 14]
2026-01-13T18:28:16.263Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:15.759Z [wb-mqtt-serial] WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
2026-01-13T18:28:15.256Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 input(s) @ 34 of device modbus:165: Serial protocol error: request timed out
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are disabled for <modbus:165: reboot>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:input: 36>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:input: 35>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:input: 34>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:input: 33>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:input: 32>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:discrete: 5>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:discrete: 4>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:discrete: 3>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:discrete: 2>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:discrete: 1>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:discrete: 0>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:coil: 3>
2026-01-13T18:28:13.743Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:coil: 2>
2026-01-13T18:28:13.741Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:coil: 1>
2026-01-13T18:28:13.741Z [wb-mqtt-serial] INFO: [serial client] Events are enabled for <modbus:165:coil: 0>
2026-01-13T18:28:13.502Z [wb-mqtt-serial] INFO: [serial device] device modbus:165 is connected

приложен диагностический архив, доступен только сотрудникам поддержки
(269,6 КБ)

wb-mqtt-serial_20260113T213017.log (166,4 КБ)

4

Добрый день!

Вижу ошибки CRC, таймауты и отключение шины из-за большого количества ошибок.

Рекомендую проверить настройки на каждом устройстве они должны совпадать с настройками на контьроллере:

  • скорость;
  • чётность;
  • количество стоп-битов.

Прошу уточнить, что вы имеете в виду под фразой:

мастером выступает WB-MGE
5

Прошу уточнить, что вы имеете в виду под фразой:

не очень корректно выразился, - шлюз подключен по фай-фаю к контроллеру, а к шлюзу подключена шина. Не очень понимаю где в устройствах смотреть четность и битность

Скрины

Снимок экрана 2026-01-14 163822
Снимок экрана 2026-01-14 163822545×567 8.49 KB

Снимок экрана 2026-01-14 163914
Снимок экрана 2026-01-14 1639141250×756 23.8 KB

Снимок экрана 2026-01-14 163930
Снимок экрана 2026-01-14 1639301410×540 13.7 KB

Снимок экрана 2026-01-14 163921
Снимок экрана 2026-01-14 1639211245×719 17.7 KB

6

Для просмотра параметров, настроенных на устройстве, вам потребуется статья в нашей документации: Настройка параметров подключения по RS-485 для Modbus-устройств Wiren Board — Wiren Board

7

Снимок экрана 2026-01-14 205929
Снимок экрана 2026-01-14 2059291679×485 31.4 KB

вроде все правильно

подправив скрипт в виде

Спойлер

#/bin/bash

function ProgressBar {
let _progress=(${1}*100/${2}*100)/100
let _done=(${_progress}*4)/10
let _left=40-$_done
_fill=$(printf “%${_done}s”)
_empty=$(printf “%${_left}s”)

printf “\rProgress : [${_fill// /#}${_empty// /-}] ${_progress}%%”
}

i=0

for j in {9600,115200,57600,38400,19200,4800,2400,1200};
do

for l in {1,2};
do
for k in {none,odd,even};
do
ProgressBar ${i} 48; i=$((i+1))
for i in {1..247}; do
modbus_client -mtcp 192.168.42.153 --debug -o 200 -a$i -t3 -r0x80 -b$j -s$l -p$k
done 2>/dev/null | grep Data: | sed -e ‘s/ //g’ -e ‘s/\n//’ | xargs -I {} printf “\tSpeed:$j\tStop bits:$l\tParity:$k\tModbus address:{}” | grep Data: | sed -e ‘s/Data://’ ; ProgressBar ${i} 11808 ; var=$((i+1))
done
done
done
ProgressBar ${i} 48

не получилось почему то, проценты идут а ответа нет в итоге

8

теперь вообще все 3 отвалились и не подключаются обратно. Попробовал не по вай фай а через роутер - вроде поднялось, это может быть из за плохой связи вай фай? Вроде к шлюзу выносную антенну подключил, расстояние около 10м всего, бетона нет. Да и периодические отвалы и через роутер были/
upd.: отвалы все равно есть, их вроде бы меньше - ночью ни одного, но утром опять

Спойлер
15-01-2026 06:14:11.894 WARNING: [serial client] Reading events failed: Serial protocol error: socket closed
15-01-2026 06:14:11.438 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 06:14:10.931 WARNING: [serial device] device modbus:26 is disconnected
15-01-2026 06:14:10.411 ERROR: [serial client] Serial protocol error: <192.168.1.90:502> connect error: timeout
15-01-2026 06:14:05.404 WARNING: <192.168.1.90:502>: closed due to repetitive errors
15-01-2026 06:14:03.895 WARNING: [register handler] failed to write: <modbus:14:coil: 4>: Serial protocol error: request timed out
15-01-2026 06:14:03.891 WARNING: [serial device] device modbus:14 is disconnected
15-01-2026 06:14:02.380 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 06:14:01.877 WARNING: [register handler] failed to write: <modbus:14:coil: 4>: Serial protocol error: request timed out
15-01-2026 06:13:33.889 WARNING: [modbus] failed to read 1 coil(s) @ 4 of device modbus:165: Serial protocol error: malformed response: invalid crc
15-01-2026 06:13:32.953 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 06:09:20.383 WARNING: [modbus] failed to read 1 input(s) @ 5 of device modbus:26: Serial protocol error: malformed response: invalid crc
15-01-2026 06:09:19.703 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 06:04:14.380 WARNING: [modbus] failed to read 1 input(s) @ 283 of device modbus:26: Serial protocol error: malformed response: invalid crc
15-01-2026 06:04:13.552 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 06:01:05.344 WARNING: [modbus] failed to read 1 input(s) @ 5 of device modbus:26: Serial protocol error: request timed out
15-01-2026 06:00:24.872 WARNING: [modbus] failed to read 1 coil(s) @ 4 of device modbus:165: Serial protocol error: malformed response: invalid crc
15-01-2026 06:00:24.031 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 04:11:22.714 WARNING: [modbus] failed to read 1 coil(s) @ 4 of device modbus:165: Serial protocol error: malformed response: invalid crc
15-01-2026 04:11:22.147 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 04:07:18.207 WARNING: [modbus] failed to read 1 input(s) @ 283 of device modbus:26: Serial protocol error: malformed response: invalid crc
15-01-2026 04:07:17.634 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 04:06:11.206 WARNING: [modbus] failed to read 1 discrete(s) @ 3 of device modbus:14: Serial protocol error: malformed response: invalid crc
15-01-2026 04:06:10.548 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 02:38:37.734 WARNING: [modbus] failed to read 1 input(s) @ 283 of device modbus:10: Serial protocol error: request timed out
15-01-2026 02:04:46.987 WARNING: [modbus] failed to read 2 input(s) @ 4 of device modbus:26: Serial protocol error: malformed response: invalid crc
15-01-2026 02:04:46.044 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 02:02:45.980 WARNING: [modbus] failed to read 1 input(s) @ 5 of device modbus:26: Serial protocol error: malformed response: invalid crc
15-01-2026 02:02:45.278 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 01:12:17.916 WARNING: [modbus] failed to read 1 input(s) @ 283 of device modbus:26: Serial protocol error: malformed response: invalid crc
15-01-2026 01:12:17.073 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 01:12:10.917 WARNING: [modbus] failed to read 1 coil(s) @ 4 of device modbus:165: Serial protocol error: malformed response: invalid crc
15-01-2026 01:12:10.173 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
15-01-2026 01:06:12.910 WARNING: [modbus] failed to read 1 input(s) @ 5 of device modbus:26: Serial protocol error: malformed response: invalid crc
15-01-2026 01:06:12.123 WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
14-01-2026 23:42:36.418 WARNING: [register handler] failed to write: <modbus:6:coil: 2>: Serial protocol error: malformed response: invalid crc

может вопрос в самой шине? Или может имеет смысл попробовать не прозрачный а обычный tcp?

9

Добрый день!

Для исключения проблем с сетью рекомендую выполнить проверку командой ping с увеличенным размером пакета. Для Windows команда выглядит следующим образом:

ping -t -l 2048 [IP-адрес устройства]

Если в течение длительного периода пакеты не теряются, значит сигнал сети в норме и связь стабильна.

Я попробую воспроизвести описанное поведение на стенде. Вы можете протестировать работу по протоколу TCP, однако и в «прозрачном» режиме связь должна работать стабильно.

10

я вообще уже ничего не понимаю, при этом веб интерфейс доступен. При этом C:\Users\Lepi4>ping 192.168.1.90 проходит. Хорошо, сейчас через роутер, но почему тогда при подключении к вайфай контроллера была эта же проблема. На всякий случай обновил прошивку MGE до 1.0.6.

11

Я верно понимаю, что при подключении по проводу работа нормализовалась и проблем нет, а по беспроводному каналу наблюдаются сложности с передачей данных и отсутствуют ping-запросы?

12

нет, проблемы и там и там одинаковые, но по беспроводному явно больше. Пинг я прислал по проводному подключению через роутер,. Беспроводное я пинг не делал. Сейчас прошло 50 минут после обновления прошивки, пока ни одного сообщения warn или err. Но пинг по вашей команде по прежнему не проходит, при этом все работает штатно. Без опций (ping 192.168.1.90 ) пингуется.

Поясню - изначально шлюз был подключен к вайфай точке контроллера через выносную антенну, каждый час а то и больше, было кратковременное отключение шлюза в следствии ошибок что я присылал, вчера вечером все совсем упало на 30 минут и я переключил на проводное соединение через роутер. Ситуация сильно не изменилась, за исключением восстановления соединения - стало быстрее (возобновлялась связь через 30-60 сек). Сейчас обновил прошивку, пока стабильно но времени мало прошло.

К сети в итоге вопросы то быть не могут - если проблема в роутере, почему через вайфай контроллера тоже самое? И наооборот…

14

Нет ли в сети VLAN или радиоканала между устройствами? Попробуйте уменьшить размер пакета, например до 1024 байт. Ситуация, при которой большой пакет не передается, выглядит странно: если в сети нет специальных устройств, всё должно работать штатно.

image
image513×108 1.97 KB

Если на шине вновь возникнут ошибки, прошу прислать новый диагностический архив для анализа.

15

1024 пингуется, пинг отрабатывает вплоть 1472 байта. 1473 уже все

по вайфай с контроллером тоже самое, это что то в шлюзе

root@wirenboard-ATKKQSS:~# ping -s 2048 192.168.42.153
PING 192.168.42.153 (192.168.42.153) 2048(2076) bytes of data.
^C
— 192.168.42.153 ping statistics —
6 packets transmitted, 0 received, 100% packet loss, time 5125ms

root@wirenboard-ATKKQSS:~# ping -s 1472 192.168.42.153
PING 192.168.42.153 (192.168.42.153) 1472(1500) bytes of data.
1480 bytes from 192.168.42.153: icmp_seq=1 ttl=64 time=262 ms
1480 bytes from 192.168.42.153: icmp_seq=2 ttl=64 time=76.3 ms
1480 bytes from 192.168.42.153: icmp_seq=3 ttl=64 time=93.1 ms
1480 bytes from 192.168.42.153: icmp_seq=4 ttl=64 time=17.4 ms
1480 bytes from 192.168.42.153: icmp_seq=5 ttl=64 time=37.5 ms
^C
— 192.168.42.153 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 17.352/97.282/262.177/86.731 ms
root@wirenboard-ATKKQSS:~# ping -s 1500 192.168.42.153
PING 192.168.42.153 (192.168.42.153) 1500(1528) bytes of data.
^C
— 192.168.42.153 ping statistics —
3 packets transmitted, 0 received, 100% packet loss, time 2027ms

глюков на 1.0.4 прошивке в плане сети не было раньше замечено?

16

Ранее проблем с сетью не было.
Все известные неисправности описаны в статье: WB-MGE v.3 Errata.

Предлагаю пока понаблюдать за работой устройства. Если оно будет работать пару дней без нареканий, я тогда помечу тему решенной.

17

Хорошо, пока за 5 часов ни одной ошибки

1 лайк
18

Добрый день!

Подскажите, пожалуйста, удалось ли вам решить проблему?

19

Не более одного отвала за день, и не каждый день, и тут же обратно цепляется (возможно роутер перегружен),т.е. проблема была в прошивке

20

Хорошо, тогда помечаю тему решенной.