Добрый день, на объекте WirenBoard 7.4 опрашивает ESM по протоколу Modbus TCP.
Количество опрашиваемых регистров примерно 250 типа float.
Периодически появляются ошибки:
Dec 02 10:29:43 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 406 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 02 10:29:44 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 408 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 02 10:29:45 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 410 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 02 10:29:45 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [serial device] device modbus-tcp:1 is disconnected
Dec 02 10:29:45 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: INFO: [serial device] device modbus-tcp:1 is connected
Dec 02 10:32:14 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 330 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 02 10:32:14 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 332 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 02 10:34:39 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 44 of device modbus-tcp:1: Serial protocol error: request timed out
С чем они могут быть связаны?
Также скорость опроса составляет примерно 2 секунды каждого параметра. Реально ли уменьшить это значение до полсекунды?
Пробовал выставить значение “периода чтения” у каждого канала 500 мс, но в этом случае опрос происходит еще медленнее и появляются “желтые восклицательные знаки” в таблице на вкладке “устройства”.
На этом же объекте ESMы той же конфигурации с теми же регистрами опрашивает сервер также по протоколу Modbus TCP с периодичностью в 200 мс и проблем с опросом нет.
Добрый день.
Обратите внимание на логи, судя по записям:
Dec 03 03:19:39 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: INFO: [serial device] device modbus-tcp:1 is connected
Dec 03 03:21:04 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 464 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 03 03:21:06 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 466 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 03 03:21:06 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [modbus] failed to read 2 holding(s) @ 468 of device modbus-tcp:1: Serial protocol error: request timed out
Dec 03 03:21:06 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: [serial device] device modbus-tcp:1 is disconnected
Dec 03 03:21:11 wirenboard-AF5R2CCQ wb-mqtt-serial[17843]: WARNING: <192.168.250.2:503>: closed due to repetitive errors
Устройство не отвечает на несколько подряд попыток соединиться. Причем не отвечает с периодичностью в 5-30 секунд.
Для диагностики - запустите ping к этому устройству, также попробуйте прочитать его регистры с помощью modbus_client. Лучше попробовать как с контроллера так и с компьютера, для того чтобы получить достоверную картину.
64 bytes from 192.168.250.2: icmp_seq=1 ttl=64 time=0.174 ms
64 bytes from 192.168.250.2: icmp_seq=2 ttl=64 time=0.188 ms
64 bytes from 192.168.250.2: icmp_seq=3 ttl=64 time=0.199 ms
64 bytes from 192.168.250.2: icmp_seq=4 ttl=64 time=0.190 ms
64 bytes from 192.168.250.2: icmp_seq=5 ttl=64 time=0.210 ms
64 bytes from 192.168.250.2: icmp_seq=6 ttl=64 time=0.154 ms
64 bytes from 192.168.250.2: icmp_seq=7 ttl=64 time=0.175 ms
64 bytes from 192.168.250.2: icmp_seq=8 ttl=64 time=0.187 ms
64 bytes from 192.168.250.2: icmp_seq=9 ttl=64 time=0.167 ms
64 bytes from 192.168.250.2: icmp_seq=10 ttl=64 time=0.175 ms
64 bytes from 192.168.250.2: icmp_seq=11 ttl=64 time=0.210 ms
64 bytes from 192.168.250.2: icmp_seq=12 ttl=64 time=0.208 ms
64 bytes from 192.168.250.2: icmp_seq=14 ttl=64 time=0.214 ms
64 bytes from 192.168.250.2: icmp_seq=15 ttl=64 time=0.173 ms
64 bytes from 192.168.250.2: icmp_seq=16 ttl=64 time=0.180 ms
64 bytes from 192.168.250.2: icmp_seq=17 ttl=64 time=0.207 ms
64 bytes from 192.168.250.2: icmp_seq=18 ttl=64 time=0.181 ms
64 bytes from 192.168.250.2: icmp_seq=19 ttl=64 time=0.190 ms
64 bytes from 192.168.250.2: icmp_seq=20 ttl=64 time=0.194 ms
64 bytes from 192.168.250.2: icmp_seq=21 ttl=64 time=0.200 ms
64 bytes from 192.168.250.2: icmp_seq=22 ttl=64 time=0.173 ms
64 bytes from 192.168.250.2: icmp_seq=23 ttl=64 time=0.179 ms
64 bytes from 192.168.250.2: icmp_seq=24 ttl=64 time=0.179 ms
64 bytes from 192.168.250.2: icmp_seq=25 ttl=64 time=0.168 ms
64 bytes from 192.168.250.2: icmp_seq=26 ttl=64 time=0.167 ms
64 bytes from 192.168.250.2: icmp_seq=27 ttl=64 time=0.162 ms
64 bytes from 192.168.250.2: icmp_seq=28 ttl=64 time=0.208 ms
64 bytes from 192.168.250.2: icmp_seq=29 ttl=64 time=0.172 ms
64 bytes from 192.168.250.2: icmp_seq=30 ttl=64 time=0.185 ms
64 bytes from 192.168.250.2: icmp_seq=31 ttl=64 time=0.210 ms
64 bytes from 192.168.250.2: icmp_seq=32 ttl=64 time=0.201 ms
64 bytes from 192.168.250.2: icmp_seq=33 ttl=64 time=0.156 ms
64 bytes from 192.168.250.2: icmp_seq=34 ttl=64 time=0.190 ms
64 bytes from 192.168.250.2: icmp_seq=35 ttl=64 time=0.175 ms
64 bytes from 192.168.250.2: icmp_seq=36 ttl=64 time=0.186 ms
64 bytes from 192.168.250.2: icmp_seq=37 ttl=64 time=0.145 ms
64 bytes from 192.168.250.2: icmp_seq=38 ttl=64 time=0.185 ms
64 bytes from 192.168.250.2: icmp_seq=39 ttl=64 time=0.183 ms
64 bytes from 192.168.250.2: icmp_seq=40 ttl=64 time=0.165 ms
64 bytes from 192.168.250.2: icmp_seq=42 ttl=64 time=0.199 ms
64 bytes from 192.168.250.2: icmp_seq=43 ttl=64 time=0.173 ms
64 bytes from 192.168.250.2: icmp_seq=44 ttl=64 time=0.182 ms
64 bytes from 192.168.250.2: icmp_seq=45 ttl=64 time=0.129 ms
64 bytes from 192.168.250.2: icmp_seq=46 ttl=64 time=0.195 ms
64 bytes from 192.168.250.2: icmp_seq=47 ttl=64 time=0.194 ms
64 bytes from 192.168.250.2: icmp_seq=49 ttl=64 time=0.173 ms
64 bytes from 192.168.250.2: icmp_seq=50 ttl=64 time=0.170 ms
64 bytes from 192.168.250.2: icmp_seq=51 ttl=64 time=0.179 ms
64 bytes from 192.168.250.2: icmp_seq=53 ttl=64 time=0.181 ms
64 bytes from 192.168.250.2: icmp_seq=54 ttl=64 time=0.167 ms
64 bytes from 192.168.250.2: icmp_seq=55 ttl=64 time=0.204 ms
64 bytes from 192.168.250.2: icmp_seq=56 ttl=64 time=0.182 ms
64 bytes from 192.168.250.2: icmp_seq=57 ttl=64 time=0.182 ms
64 bytes from 192.168.250.2: icmp_seq=58 ttl=64 time=0.186 ms
64 bytes from 192.168.250.2: icmp_seq=59 ttl=64 time=0.171 ms
64 bytes from 192.168.250.2: icmp_seq=60 ttl=64 time=0.177 ms
При опросе с помощью modbus_client с интервалом в 1 с появляются следующие ошибки:
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
<00><01><00><00><00><07><01><03><04><3D><BD><DB><DD>
SUCCESS: read 2 of elements:
Data: 0x3dbd 0xdbdd
ERROR Illegal data address
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
<00><01><00><00><00><03><01><83><02>
ERROR occured!
ERROR Illegal data address
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
<00><01><00><00><00><03><01><83><02>
ERROR occured!
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
<00><01><00><00><00><07><01><03><04><3D><BD><DD><CF>
SUCCESS: read 2 of elements:
Data: 0x3dbd 0xddcf
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
<00><01><00><00><00><07><01><03><04><3D><B7><6E><28>
SUCCESS: read 2 of elements:
Data: 0x3db7 0x6e28
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
<00><01><00><00><00><07><01><03><04><3D><B7><0A><64>
SUCCESS: read 2 of elements:
Data: 0x3db7 0x0a64
Connection failed: Operation now in progress
Connecting to 192.168.250.2:503
ERROR Connection timed out: select
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
ERROR occured!
Connecting to 192.168.250.2:503
[00][01][00][00][00][06][01][03][00][00][00][02]
Waiting for a confirmation...
<00><01><00><00><00><07><01><03><04><3D><B7><2C><4F>
SUCCESS: read 2 of elements:
Data: 0x3db7 0x2c4f
Объект расположен удаленно в месте с не с самой лучшей связью, поэтому пинг с компьютера вероятно даст не совсем достоверную информацию. Но могу все же попробовать, если это необходимо после выполненных шагов выше на контроллере.
Приложу файл лога за минуту опроса modbus_client modbus_log.txt (12,4 КБ)
Пинг и не нужен, с компьютера. Попробуйте запросить прочитать ответы по modbus.
Сейчас я вижу что при идентичном запросе
и
устройство отвечает разное.
Точно ли в сети одно устройство с такимс адресом? Я еще не видел чтобы slave то отдвал данные по регистру то возвращал отсутвие запрошенного.
Тогда - тем более непонятно. Устройство, по моему предстаавлению - должно на одинаковые (они ведь одинаковые, я точно сравнил) запросы давать всегда одинаковый ответ. Если запрашивать существующий регистр - то его значение. Если несуществующий - возвращать 0x8*.
Надо заметить что, возможно, устройство не способно отдвать значения с той частотой с котрой его контроллер опрашивает. Для проверки - остановвите wb-mqtt-serial и попробуйте снова с помощью modbus_client опросить, запросив в цикле сотню раз, например как тут: Увеличение скорости WB-MGE v.2 - #34 от пользователя BrainRoot
Пробросил 502 порт на компьютер с устройства и опросил при помощи modbus pool, логи прикладываю к сообщению, ошибок при опросе не обнаружил (100 это опрос 100 регистров, файл без цифры это 2 регистра)
Также на объекте работает сервер, который опрашивает 10 ESMов с частотой 200 мс, там также не было замечено ошибок в работе устройств.
В целом опрос раз в 500мс был бы достаточным, прикладываю опрос раз в 200мс при помощи той же modbus pool Загрузка: modpool_log_200ms.txt…
По поводу цикла пока что пробую, не совсем получается, чуть позже пришлю результат.
Ну, собственно тут и ответ. Устройство не может отвечать так часто как может быть опрошено.
Стоит опрашивать реже, не все программисты настолько же профессиональны как разработчики Wiren board. Наши устройства утилизируют шину на 100%.
Нет, в цикле мы устанавливаем только время ожидания ответа (-o ), а запросы идут с максимальной частотой.
Если добавить в цикл ```read -t 0.2```` напимер (sleep работает только с целыми значениями) - то как раз воспроизведется задержка в 200мс.
В этом случае опрос получился более успешный, но все равно имеет место быть много пропусков:
root@wirenboard-AF5R2CCQ:~# for i in {0..200}; do read -t 0.2 echo $i; modbus_client -mtcp -a1 -c2 -r0 -t0x03 -o10 -p50
3 192.168.250.2; done
-bash: read: `0': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da2 0xae0f
-bash: read: `1': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `2': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da2 0xca94
-bash: read: `3': not a valid identifier
Connection failed: Connection refused
-bash: read: `4': not a valid identifier
Connection failed: Connection refused
-bash: read: `5': not a valid identifier
Connection failed: Connection refused
-bash: read: `6': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `7': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `8': not a valid identifier
Connection failed: Connection refused
-bash: read: `9': not a valid identifier
Connection failed: Connection refused
-bash: read: `10': not a valid identifier
Connection failed: Connection refused
-bash: read: `11': not a valid identifier
Connection failed: Connection refused
-bash: read: `12': not a valid identifier
Connection failed: Connection refused
-bash: read: `13': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da1 0xf56b
-bash: read: `14': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da0 0xff8b
-bash: read: `15': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da0 0xb7d4
-bash: read: `16': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da1 0x3e01
-bash: read: `17': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da1 0x55c6
-bash: read: `18': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da0 0xd683
-bash: read: `19': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da0 0x94b4
-bash: read: `20': not a valid identifier
Connection failed: Connection refused
-bash: read: `21': not a valid identifier
ERROR occured!
-bash: read: `22': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da0 0x8276
-bash: read: `23': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da0 0x8d8f
-bash: read: `24': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da0 0x59bc
-bash: read: `25': not a valid identifier
Connection failed: Connection refused
-bash: read: `26': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `27': not a valid identifier
Connection failed: Connection refused
-bash: read: `28': not a valid identifier
Connection failed: Connection refused
-bash: read: `29': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `30': not a valid identifier
Connection failed: Connection refused
-bash: read: `31': not a valid identifier
Connection failed: Connection refused
-bash: read: `32': not a valid identifier
Connection failed: Connection refused
-bash: read: `33': not a valid identifier
Connection failed: Connection refused
-bash: read: `34': not a valid identifier
Connection failed: Connection refused
-bash: read: `35': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da3 0x221e
-bash: read: `36': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da3 0x08d0
-bash: read: `37': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da3 0xbdcc
-bash: read: `38': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da3 0xa07b
-bash: read: `39': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da8 0xa769
-bash: read: `40': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x14c0
-bash: read: `41': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x41f9
-bash: read: `42': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x23e8
-bash: read: `43': not a valid identifier
Connection failed: Connection refused
-bash: read: `44': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x5663
-bash: read: `45': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x1ee2
-bash: read: `46': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `47': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x368a
-bash: read: `48': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `49': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x807e
-bash: read: `50': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0xe40a
-bash: read: `51': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x296d
-bash: read: `52': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3da9 0x6660
-bash: read: `53': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x4637
-bash: read: `54': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dab 0x1763
-bash: read: `55': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daa 0x6c0f
-bash: read: `56': not a valid identifier
Connection failed: Connection refused
-bash: read: `57': not a valid identifier
Connection failed: Connection refused
-bash: read: `58': not a valid identifier
Connection failed: Connection refused
-bash: read: `59': not a valid identifier
Connection failed: Connection refused
-bash: read: `60': not a valid identifier
Connection failed: Connection refused
-bash: read: `61': not a valid identifier
Connection failed: Connection refused
-bash: read: `62': not a valid identifier
Connection failed: Connection refused
-bash: read: `63': not a valid identifier
Connection failed: Connection refused
-bash: read: `64': not a valid identifier
Connection failed: Connection refused
-bash: read: `65': not a valid identifier
Connection failed: Connection refused
-bash: read: `66': not a valid identifier
Connection failed: Connection refused
-bash: read: `67': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `68': not a valid identifier
ERROR occured!
-bash: read: `69': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x0b3b
-bash: read: `70': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0xf451
-bash: read: `71': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x2623
-bash: read: `72': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x31b9
-bash: read: `73': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dad 0xb8df
-bash: read: `74': not a valid identifier
ERROR occured!
-bash: read: `75': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x40f6
-bash: read: `76': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x5b95
-bash: read: `77': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dad 0xbe6b
-bash: read: `78': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0xc017
-bash: read: `79': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x79ba
-bash: read: `80': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x6a31
-bash: read: `81': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `82': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x4db8
-bash: read: `83': not a valid identifier
Connection failed: Connection refused
-bash: read: `84': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x8785
-bash: read: `85': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x5fe6
-bash: read: `86': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `87': not a valid identifier
ERROR occured!
-bash: read: `88': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x9a5f
-bash: read: `89': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x02a1
-bash: read: `90': not a valid identifier
ERROR occured!
-bash: read: `91': not a valid identifier
Connection failed: Connection refused
-bash: read: `92': not a valid identifier
Connection failed: Connection refused
-bash: read: `93': not a valid identifier
Connection failed: Connection refused
-bash: read: `94': not a valid identifier
Connection failed: Connection refused
-bash: read: `95': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `96': not a valid identifier
Connection failed: Connection refused
-bash: read: `97': not a valid identifier
Connection failed: Connection refused
-bash: read: `98': not a valid identifier
Connection failed: Connection refused
-bash: read: `99': not a valid identifier
Connection failed: Connection refused
-bash: read: `100': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `101': not a valid identifier
Connection failed: Connection refused
-bash: read: `102': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x251d
-bash: read: `103': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dad 0xf33e
-bash: read: `104': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x14c4
-bash: read: `105': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `106': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x416e
-bash: read: `107': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0x40e4
-bash: read: `108': not a valid identifier
ERROR occured!
-bash: read: `109': not a valid identifier
Connection failed: Connection refused
-bash: read: `110': not a valid identifier
Connection failed: Connection refused
-bash: read: `111': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `112': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db8 0xddb8
-bash: read: `113': not a valid identifier
Connection failed: Connection refused
-bash: read: `114': not a valid identifier
Connection failed: Connection refused
-bash: read: `115': not a valid identifier
Connection failed: Connection refused
-bash: read: `116': not a valid identifier
Connection failed: Connection refused
-bash: read: `117': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `118': not a valid identifier
Connection failed: Connection refused
-bash: read: `119': not a valid identifier
Connection failed: Connection refused
-bash: read: `120': not a valid identifier
Connection failed: Connection refused
-bash: read: `121': not a valid identifier
Connection failed: Connection refused
-bash: read: `122': not a valid identifier
Connection failed: Connection refused
-bash: read: `123': not a valid identifier
Connection failed: Connection refused
-bash: read: `124': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db8 0x29cf
-bash: read: `125': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0xe3ea
-bash: read: `126': not a valid identifier
ERROR occured!
-bash: read: `127': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0xa443
-bash: read: `128': not a valid identifier
Connection failed: Connection refused
-bash: read: `129': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db8 0x105b
-bash: read: `130': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0xfc0d
-bash: read: `131': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0xcec4
-bash: read: `132': not a valid identifier
Connection failed: Connection refused
-bash: read: `133': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x81c8
-bash: read: `134': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x9d5e
-bash: read: `135': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `136': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x445b
-bash: read: `137': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0xb575
-bash: read: `138': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0x3033
-bash: read: `139': not a valid identifier
Connection failed: Connection refused
-bash: read: `140': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0xcd3d
-bash: read: `141': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0x95a1
-bash: read: `142': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0xc89f
-bash: read: `143': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0xdb1d
-bash: read: `144': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `145': not a valid identifier
ERROR occured!
-bash: read: `146': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db8 0x4ac6
-bash: read: `147': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db8 0x517f
-bash: read: `148': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db8 0xa028
-bash: read: `149': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db8 0x9963
-bash: read: `150': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0xd369
И в случае, если опрашивать даже 1 раз в секунду, то также имеются пропуски. Примерно сопоставимые, как если бы я опрашивал через wb-mqtt-serial с помощью веб-конфигуратора.
root@wirenboard-AF5R2CCQ:~# for i in {0..200}; do read -t 1 echo $i; modbus_client -mtcp -a1 -c2 -r0 -t0x03 -o10 -p503
192.168.250.2; done
-bash: read: `0': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `1': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db4 0x2146
-bash: read: `2': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db3 0x89cc
-bash: read: `3': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0x9d48
-bash: read: `4': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0xaee4
-bash: read: `5': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x05ca
-bash: read: `6': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db4 0x9d9f
-bash: read: `7': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db4 0x01c3
-bash: read: `8': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `9': not a valid identifier
ERROR occured!
-bash: read: `10': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db3 0x4095
-bash: read: `11': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xac7e
-bash: read: `12': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xd63b
-bash: read: `13': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x7f40
-bash: read: `14': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xfa3a
-bash: read: `15': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db3 0x2e3a
-bash: read: `16': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xddb5
-bash: read: `17': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xdac2
-bash: read: `18': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x4554
-bash: read: `19': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x916f
-bash: read: `20': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xb919
-bash: read: `21': not a valid identifier
Connection failed: Connection refused
-bash: read: `22': not a valid identifier
Connection failed: Connection refused
-bash: read: `23': not a valid identifier
Connection failed: Connection refused
-bash: read: `24': not a valid identifier
Connection failed: Connection refused
-bash: read: `25': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xd56a
-bash: read: `26': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0x4f56
-bash: read: `27': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0x5fdf
-bash: read: `28': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db4 0xce69
-bash: read: `29': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x92ba
-bash: read: `30': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x660c
-bash: read: `31': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0xfdb6
-bash: read: `32': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x41cb
-bash: read: `33': not a valid identifier
Connection failed: Connection refused
-bash: read: `34': not a valid identifier
Connection failed: Connection refused
-bash: read: `35': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0xbdfc
-bash: read: `36': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0xe06f
-bash: read: `37': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0x3daf
-bash: read: `38': not a valid identifier
ERROR occured!
-bash: read: `39': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db4 0x9be3
-bash: read: `40': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0x7a22
-bash: read: `41': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0x4822
-bash: read: `42': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db5 0x0356
-bash: read: `43': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x6a85
-bash: read: `44': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x6ef3
-bash: read: `45': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x5c8e
-bash: read: `46': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x5994
-bash: read: `47': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xd4e6
-bash: read: `48': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x80ec
-bash: read: `49': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0xe23c
-bash: read: `50': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x779d
-bash: read: `51': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db4 0x97d8
-bash: read: `52': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db3 0x42be
-bash: read: `53': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x55c4
-bash: read: `54': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `55': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xb4ed
-bash: read: `56': not a valid identifier
ERROR occured!
-bash: read: `57': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db3 0x9f95
-bash: read: `58': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xc440
-bash: read: `59': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xd88c
-bash: read: `60': not a valid identifier
ERROR occured!
-bash: read: `61': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `62': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x177d
-bash: read: `63': not a valid identifier
ERROR occured!
-bash: read: `64': not a valid identifier
ERROR occured!
-bash: read: `65': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x05f2
-bash: read: `66': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `67': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x0230
-bash: read: `68': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x7606
-bash: read: `69': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x323d
-bash: read: `70': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dae 0xc8c0
-bash: read: `71': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x34f9
-bash: read: `72': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db0 0xabd7
-bash: read: `73': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `74': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dad 0x5e2b
-bash: read: `75': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dac 0xc349
-bash: read: `76': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dac 0xced3
-bash: read: `77': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dab 0xe5d9
-bash: read: `78': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dac 0x2ac9
-bash: read: `79': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `80': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x1abc
-bash: read: `81': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dac 0x79bd
-bash: read: `82': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `83': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dac 0xb386
-bash: read: `84': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dac 0x7893
-bash: read: `85': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3dad 0xfceb
-bash: read: `86': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `87': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x4933
-bash: read: `88': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x4b9f
-bash: read: `89': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `90': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xe2bc
-bash: read: `91': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x854d
-bash: read: `92': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x0908
-bash: read: `93': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x17f5
-bash: read: `94': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x93d9
-bash: read: `95': not a valid identifier
Connection failed: Connection refused
-bash: read: `96': not a valid identifier
Connection failed: Connection refused
-bash: read: `97': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xba4a
-bash: read: `98': not a valid identifier
Connection failed: Connection refused
-bash: read: `99': not a valid identifier
Connection failed: Connection refused
-bash: read: `100': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x4866
-bash: read: `101': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x944a
-bash: read: `102': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `103': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `104': not a valid identifier
ERROR occured!
-bash: read: `105': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db3 0x594f
-bash: read: `106': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0xfe1e
-bash: read: `107': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x13bc
-bash: read: `108': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x2f29
-bash: read: `109': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db7 0x642f
-bash: read: `110': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0xa73d
-bash: read: `111': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db6 0x356d
-bash: read: `112': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xf14d
-bash: read: `113': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db0 0x1030
-bash: read: `114': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db0 0x190d
-bash: read: `115': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db0 0x9f2d
-bash: read: `116': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xeeab
-bash: read: `117': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xfbc8
-bash: read: `118': not a valid identifier
ERROR occured!
-bash: read: `119': not a valid identifier
ERROR occured!
-bash: read: `120': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db0 0x06cf
-bash: read: `121': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xf026
-bash: read: `122': not a valid identifier
Connection failed: Connection refused
-bash: read: `123': not a valid identifier
Connection failed: Connection refused
-bash: read: `124': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x753a
-bash: read: `125': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db2 0x6972
-bash: read: `126': not a valid identifier
ERROR occured!
-bash: read: `127': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db0 0x0761
-bash: read: `128': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0x18a6
-bash: read: `129': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xd28c
-bash: read: `130': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xf0c7
-bash: read: `131': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `132': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xf566
-bash: read: `133': not a valid identifier
Connection failed: Connection refused
-bash: read: `134': not a valid identifier
Connection failed: Connection refused
-bash: read: `135': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `136': not a valid identifier
ERROR occured!
-bash: read: `137': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3daf 0xdc61
-bash: read: `138': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `139': not a valid identifier
ERROR occured!
-bash: read: `140': not a valid identifier
Connection failed: Connection refused
-bash: read: `141': not a valid identifier
Connection failed: Connection refused
-bash: read: `142': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x8131
-bash: read: `143': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x8641
-bash: read: `144': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db0 0xd8d5
-bash: read: `145': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x3004
-bash: read: `146': not a valid identifier
ERROR occured!
-bash: read: `147': not a valid identifier
Connection failed: Operation now in progress
-bash: read: `148': not a valid identifier
SUCCESS: read 2 of elements:
Data: 0x3db1 0x7481
-bash: read: `149': not a valid identifier
ERROR occured!
-bash: read: `150': not a valid identifier
ERROR occured!
Да, запуск вполне.
Ну, - да, 200мс - даже мало, как выясняется. А, ради интереса - посмотрите на системе, которая читает устройство с периодом 200 и нет проблем с опросом, в логи - там нет ошибок совсем?