Драйвер ModBus
-
А драйвер запущен? В логе есть что нибудь при уровне Debug? `
Уж не помню где дебаг включается в новой админке…! ````
modbus-0 2016-10-19 14:27:50.315 info terminating
RangeError: 2016-10-19 14:27:50.302 error at Socket.Readable.push (_stream_readable.js:111:10)
RangeError: 2016-10-19 14:27:50.302 error at readableAddChunk (_stream_readable.js:153:18)
RangeError: 2016-10-19 14:27:50.302 error at Socket.emit (events.js:169:7)
RangeError: 2016-10-19 14:27:50.302 error at emitOne (events.js:77:13)
RangeError: 2016-10-19 14:27:50.302 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-tcp-client.js:129:22)
RangeError: 2016-10-19 14:27:50.302 error at Object.emit (/opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit-event-bus/src/stampit-event-bus.js:20:38)
RangeError: 2016-10-19 14:27:50.302 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-client-core.js:135:17)
RangeError: 2016-10-19 14:27:50.302 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-client-core.js:91:33)
RangeError: 2016-10-19 14:27:50.302 error at Buffer.readUInt8 (buffer.js:718:5)
RangeError: 2016-10-19 14:27:50.302 error at checkOffset (buffer.js:680:11)
RangeError: 2016-10-19 14:27:50.302 error index out of range
uncaught 2016-10-19 14:27:50.301 error exception: index out of range
modbus-0 2016-10-19 14:27:50.292 info Connected to slave 192.168.11.205
modbus-0 2016-10-19 14:27:50.239 warn Serial is not available
modbus-0 2016-10-19 14:27:50.235 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus
host-Bee-IoT 2016-10-19 14:27:49.803 info instance system.adapter.modbus.0 started with pid 4679
host-Bee-IoT 2016-10-19 14:27:47.318 info instance system.adapter.modbus.0 terminated with code 0 (OK)
modbus-0 2016-10-19 14:27:47.307 info terminating
host-Bee-IoT 2016-10-19 14:27:47.298 info stopInstance system.adapter.modbus.0 killing pid 4668
host-Bee-IoT 2016-10-19 14:27:47.298 info stopInstance system.adapter.modbus.0
host-Bee-IoT 2016-10-19 14:27:47.298 info object change system.adapter.modbus.0
modbus-0 2016-10-19 14:27:39.556 warn Module serialport is not available
modbus-0 2016-10-19 14:27:12.621 info Connected to slave 192.168.11.205
modbus-0 2016-10-19 14:27:12.571 warn Serial is not available
modbus-0 2016-10-19 14:27:12.567 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus
host-Bee-IoT 2016-10-19 14:27:12.129 info instance system.adapter.modbus.0 started with pid 4668
host-Bee-IoT 2016-10-19 14:27:12.126 info object change system.adapter.modbus.0
host-Bee-IoT 2016-10-19 14:27:09.269 info object change system.adapter.modbus.0
host-Bee-IoT 2016-10-19 14:26:36.974 info object change system.adapter.modbus.0
host-Bee-IoT 2016-10-19 14:16:51.782 info Do not restart adapter system.adapter.modbus.0 because disabled or deleted
host-Bee-IoT 2016-10-19 14:16:51.782 error instance system.adapter.modbus.0 terminated with code 3 (Adapter disabled or invalid config)
host-Bee-IoT 2016-10-19 14:16:38.916 info object change system.adapter.modbus.0
host-Bee-IoT 2016-10-19 14:16:21.327 info Restart adapter system.adapter.modbus.0 because enabled
host-Bee-IoT 2016-10-19 14:16:21.327 error instance system.adapter.modbus.0 terminated with code 0 (OK)
Error: 2016-10-19 14:16:21.302 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:773:21
Error: 2016-10-19 14:16:21.302 error at /opt/iobroker/node_modules/iobroker.modbus/main.js:1150:13
Error: 2016-10-19 14:16:21.302 error at clear (/opt/iobroker/node_modules/iobroker.modbus/main.js:1147:22)
Error: 2016-10-19 14:16:21.302 error at Object.main.start (/opt/iobroker/node_modules/iobroker.modbus/main.js:1631:53)
Error: 2016-10-19 14:16:21.302 error at Object.Factory [as complete] (/opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/dist/stampit.js:177:48)
Error: 2016-10-19 14:16:21.302 error at /opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/node_modules/lodash/internal/createForEach.js:15:9
Error: 2016-10-19 14:16:21.302 error at arrayEach (/opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/node_modules/lodash/internal/arrayEach.js:15:9)
Error: 2016-10-19 14:16:21.302 error at /opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/dist/stampit.js:185:31
Error: 2016-10-19 14:16:21.302 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-serial-client.js:119:9)
Error: 2016-10-19 14:16:21.302 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-serial-client.js:19:23)
Error: 2016-10-19 14:16:21.302 error No portname.
uncaught 2016-10-19 14:16:21.301 error exception: No portname.
modbus-0 2016-10-19 14:16:21.234 warn Serial is not availableЕсли удаляю драйвер, а затем его ставлю вновь, то список с COM портами раскрывается (на выбор "Выбирите порт" и "Not available") Если сохранить изменения и снова зайти в настройки, то выбора уже никакого нет. А поддерживаются только ttyS* порты, или ttyUSB* тоже? `Я уже вижу
Serial is not available
А build-essential поставлены? `
А как-же без нееbuild-essential is already the newest version (12.1ubuntu2).При дебаге есть не обльшие отличия…
modbus-0 2016-10-19 15:06:44.372 debug statesDB connected modbus-0 2016-10-19 15:06:44.366 debug objectDB connected host-Bee-IoT 2016-10-19 15:06:44.036 info instance system.adapter.modbus.0 started with pid 5312 host-Bee-IoT 2016-10-19 15:06:44.032 info object change system.adapter.modbus.0 host-Bee-IoT 2016-10-19 15:06:36.076 info Restart adapter system.adapter.modbus.0 because enabled host-Bee-IoT 2016-10-19 15:06:36.076 error instance system.adapter.modbus.0 terminated with code 0 (OK) modbus-0 2016-10-19 15:06:36.067 info terminating inMem 2016-10-19 15:06:36.062 debug message modbus.0.* modbus.0.info.connection val=false, ack=true, ts=1476864396059, q=0, from=system.adapter.modbus.0, lc=1476864395998А поддерживаются только ttyS* порты, или ttyUSB* тоже?
В npm install iobroker.modbus - старый!!!
Ставлю с гита.
-
Переткнул USB-RS485 из ESXi в OrangePi PC.
Там дает выбрать /dev/tyyS0 или /dev/ttyUSB0.
Выбираю /dev/ttyUSB0.
После сохранения больше выбрать не дает ничего из портов.
! ````
host-orangepi-iot 2016-10-19 15:16:29.016 info Restart adapter system.adapter.modbus.0 because enabled
host-orangepi-iot 2016-10-19 15:16:29.015 error instance system.adapter.modbus.0 terminated with code 0 (OK)
inMem 2016-10-19 15:16:28.964 debug message modbus.0.* modbus.0.info.connection val=false, ack=true, ts=1476864988957, q=0, from=system.adapter.modbus.0, lc=1476864988781
TypeError: 2016-10-19 15:16:28.938 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:131:20)
TypeError: 2016-10-19 15:16:28.938 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
TypeError: 2016-10-19 15:16:28.938 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:229:12)
TypeError: 2016-10-19 15:16:28.938 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:305:9)
TypeError: 2016-10-19 15:16:28.938 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:707:35)
TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:773:21
TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.modbus/main.js:1150:13
TypeError: 2016-10-19 15:16:28.938 error at clear (/opt/iobroker/node_modules/iobroker.modbus/main.js:1147:22)
TypeError: 2016-10-19 15:16:28.938 error at Object.main.start (/opt/iobroker/node_modules/iobroker.modbus/main.js:1631:53)
TypeError: 2016-10-19 15:16:28.938 error at Object.Factory [as complete] (/opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/dist/stampit.js:177:48)
TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/node_modules/lodash/internal/createForEach.js:15:9
TypeError: 2016-10-19 15:16:28.938 error at arrayEach (/opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/node_modules/lodash/internal/arrayEach.js:15:9)
TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/dist/stampit.js:185:31
TypeError: 2016-10-19 15:16:28.938 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-serial-client.js:119:9)
TypeError: 2016-10-19 15:16:28.938 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-serial-client.js:42:26)
TypeError: 2016-10-19 15:16:28.938 error at new SerialPort (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/node_modules/serialport/lib/serialport.js:101:11)
TypeError: 2016-10-19 15:16:28.938 error Invalid "baudRate" must be a number got: 9600
uncaught 2016-10-19 15:16:28.930 error exception: Invalid "baudRate" must be a number got: 9600
modbus-0 2016-10-19 15:16:27.951 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus
modbus-0 2016-10-19 15:16:27.772 debug statesDB connected
modbus-0 2016-10-19 15:16:27.732 debug objectDB connected
host-orangepi-iot 2016-10-19 15:16:25.456 info instance system.adapter.modbus.0 started with pid 26218
host-orangepi-iot 2016-10-19 15:16:22.948 info instance system.adapter.modbus.0 terminated with code null ()
host-orangepi-iot 2016-10-19 15:16:22.947 warn instance system.adapter.modbus.0 terminated due to SIGTERMМеня пугает строчка - Invalid "baudRate" must be a number got: 9600root@orangepi-iot:~# ls -l /dev/ttyS* /dev/ttyUSB*
crw--w---- 1 root tty 251, 0 Oct 12 17:17 /dev/ttyS0
crw-rw---- 1 root dialout 188, 0 Oct 19 15:12 /dev/ttyUSB0
root@orangepi-iot:~#Может права на порт задать другие? -
Переткнул USB-RS485 из ESXi в OrangePi PC.
Там дает выбрать /dev/tyyS0 или /dev/ttyUSB0.
Выбираю /dev/ttyUSB0.
После сохранения больше выбрать не дает ничего из портов.
!
host-orangepi-iot 2016-10-19 15:16:29.016 info Restart adapter system.adapter.modbus.0 because enabled host-orangepi-iot 2016-10-19 15:16:29.015 error instance system.adapter.modbus.0 terminated with code 0 (OK) inMem 2016-10-19 15:16:28.964 debug message modbus.0.* modbus.0.info.connection val=false, ack=true, ts=1476864988957, q=0, from=system.adapter.modbus.0, lc=1476864988781 TypeError: 2016-10-19 15:16:28.938 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:131:20) TypeError: 2016-10-19 15:16:28.938 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2016-10-19 15:16:28.938 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:229:12) TypeError: 2016-10-19 15:16:28.938 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:305:9) TypeError: 2016-10-19 15:16:28.938 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:707:35) TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:773:21 TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.modbus/main.js:1150:13 TypeError: 2016-10-19 15:16:28.938 error at clear (/opt/iobroker/node_modules/iobroker.modbus/main.js:1147:22) TypeError: 2016-10-19 15:16:28.938 error at Object.main.start (/opt/iobroker/node_modules/iobroker.modbus/main.js:1631:53) TypeError: 2016-10-19 15:16:28.938 error at Object.Factory [as complete] (/opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/dist/stampit.js:177:48) TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/node_modules/lodash/internal/createForEach.js:15:9 TypeError: 2016-10-19 15:16:28.938 error at arrayEach (/opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/node_modules/lodash/internal/arrayEach.js:15:9) TypeError: 2016-10-19 15:16:28.938 error at /opt/iobroker/node_modules/iobroker.modbus/node_modules/stampit/dist/stampit.js:185:31 TypeError: 2016-10-19 15:16:28.938 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-serial-client.js:119:9) TypeError: 2016-10-19 15:16:28.938 error at Object. (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/src/modbus-serial-client.js:42:26) TypeError: 2016-10-19 15:16:28.938 error at new SerialPort (/opt/iobroker/node_modules/iobroker.modbus/node_modules/jsmodbus/node_modules/serialport/lib/serialport.js:101:11) TypeError: 2016-10-19 15:16:28.938 error Invalid "baudRate" must be a number got: 9600 uncaught 2016-10-19 15:16:28.930 error exception: Invalid "baudRate" must be a number got: 9600 modbus-0 2016-10-19 15:16:27.951 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus modbus-0 2016-10-19 15:16:27.772 debug statesDB connected modbus-0 2016-10-19 15:16:27.732 debug objectDB connected host-orangepi-iot 2016-10-19 15:16:25.456 info instance system.adapter.modbus.0 started with pid 26218 host-orangepi-iot 2016-10-19 15:16:22.948 info instance system.adapter.modbus.0 terminated with code null () host-orangepi-iot 2016-10-19 15:16:22.947 warn instance system.adapter.modbus.0 terminated due to SIGTERM`
У меня всё также -
-
-
Интересно. Что конкретно заработало? TCP? Master? с кем общается? `
TCP заработал как и 0.3.11 (пока одно устройство ID 5 на arduino и 9 Holding регистров)На виртуалке ни вкакую не хочет в IOB видеть COM порты через USB.
Что странно, то USB GSM модемы отлично работают в asterisk на этoм-же сервере.
PS: RTU на OrangePi PC так-же не дает выбрать порт после сохранения…
Но в логах уже есть обнадеживающие записи, касательно USB переходника
! ````
host-orangepi-iot 2016-10-19 20:58:37.473 info Restart adapter system.adapter.modbus.0 because enabled
host-orangepi-iot 2016-10-19 20:58:37.472 error instance system.adapter.modbus.0 terminated with code 0 (OK)
modbus-0 2016-10-19 20:58:37.433 info terminating
TypeError: 2016-10-19 20:58:37.344 error at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/component-emitter/index.js:134:20)
TypeError: 2016-10-19 20:58:37.344 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
TypeError: 2016-10-19 20:58:37.344 error at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:323:16)
TypeError: 2016-10-19 20:58:37.344 error at Decoder.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/index.js:247:12)
TypeError: 2016-10-19 20:58:37.344 error at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20)
TypeError: 2016-10-19 20:58:37.344 error at Decoder. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
TypeError: 2016-10-19 20:58:37.344 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:333:8)
TypeError: 2016-10-19 20:58:37.344 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:131:20)
TypeError: 2016-10-19 20:58:37.344 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15)
TypeError: 2016-10-19 20:58:37.344 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:229:12)
TypeError: 2016-10-19 20:58:37.344 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:305:9)
TypeError: 2016-10-19 20:58:37.344 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:707:35)
TypeError: 2016-10-19 20:58:37.344 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:773:21
TypeError: 2016-10-19 20:58:37.344 error at /opt/iobroker/node_modules/iobroker.modbus/main.js:1258:13
TypeError: 2016-10-19 20:58:37.344 error at clear (/opt/iobroker/node_modules/iobroker.modbus/main.js:1255:22)
TypeError: 2016-10-19 20:58:37.344 error at Object.main.start (/opt/iobroker/node_modules/iobroker.modbus/main.js:1583:26)
TypeError: 2016-10-19 20:58:37.344 error modbusClient.connect is not a function
uncaught 2016-10-19 20:58:37.334 error exception: modbusClient.connect is not a function
modbus-0 2016-10-19 20:58:36.299 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus
host-orangepi-iot 2016-10-19 20:58:33.737 info instance system.adapter.modbus.0 started with pid 31857
host-orangepi-iot 2016-10-19 20:58:31.239 info instance system.adapter.modbus.0 terminated with code 0 (OK)
modbus-0 2016-10-19 20:58:31.204 info terminating
host-orangepi-iot 2016-10-19 20:58:31.157 info stopInstance system.adapter.modbus.0 killing pid 31773
host-orangepi-iot 2016-10-19 20:58:31.155 info stopInstance system.adapter.modbus.0
host-orangepi-iot 2016-10-19 20:58:31.145 info object change system.adapter.modbus.0
modbus-0 2016-10-19 20:58:06.901 info List of port: [{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyUSB0","manufacturer":"1a86","serialNumber":"1a86_USB2.0-Serial","pnpId":"usb-1a86_USB2.0-Serial-if00-port0","vendorId":"0x1a86","productId"
modbus-0 2016-10-19 20:57:53.650 warn Error: connect ECONNREFUSED 127.0.0.1:502
modbus-0 2016-10-19 20:57:52.541 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus
iobroker 2016-10-19 20:57:49.956 info exit 0
iobroker 2016-10-19 20:57:49.936 info host.orangepi-iot object system.adapter.modbus.0 created -
Интересно. Что конкретно заработало? TCP? Master? с кем общается? `
TCP заработал как и 0.3.11 (пока одно устройство ID 5 на arduino и 9 Holding регистров)На виртуалке ни вкакую не хочет в IOB видеть COM порты через USB.
Что странно, то USB GSM модемы отлично работают в asterisk на этoм-же сервере.
PS: RTU на OrangePi PC так-же не дает выбрать порт после сохранения…
Но в логах уже есть обнадеживающие записи, касательно USB переходника
!
host-orangepi-iot 2016-10-19 20:58:37.473 info Restart adapter system.adapter.modbus.0 because enabled host-orangepi-iot 2016-10-19 20:58:37.472 error instance system.adapter.modbus.0 terminated with code 0 (OK) modbus-0 2016-10-19 20:58:37.433 info terminating TypeError: 2016-10-19 20:58:37.344 error at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/component-emitter/index.js:134:20) TypeError: 2016-10-19 20:58:37.344 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2016-10-19 20:58:37.344 error at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:323:16) TypeError: 2016-10-19 20:58:37.344 error at Decoder.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/index.js:247:12) TypeError: 2016-10-19 20:58:37.344 error at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20) TypeError: 2016-10-19 20:58:37.344 error at Decoder. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2016-10-19 20:58:37.344 error at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:333:8) TypeError: 2016-10-19 20:58:37.344 error at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:131:20) TypeError: 2016-10-19 20:58:37.344 error at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-bind/index.js:21:15) TypeError: 2016-10-19 20:58:37.344 error at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:229:12) TypeError: 2016-10-19 20:58:37.344 error at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:305:9) TypeError: 2016-10-19 20:58:37.344 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:707:35) TypeError: 2016-10-19 20:58:37.344 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:773:21 TypeError: 2016-10-19 20:58:37.344 error at /opt/iobroker/node_modules/iobroker.modbus/main.js:1258:13 TypeError: 2016-10-19 20:58:37.344 error at clear (/opt/iobroker/node_modules/iobroker.modbus/main.js:1255:22) TypeError: 2016-10-19 20:58:37.344 error at Object.main.start (/opt/iobroker/node_modules/iobroker.modbus/main.js:1583:26) TypeError: 2016-10-19 20:58:37.344 error modbusClient.connect is not a function uncaught 2016-10-19 20:58:37.334 error exception: modbusClient.connect is not a function modbus-0 2016-10-19 20:58:36.299 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus host-orangepi-iot 2016-10-19 20:58:33.737 info instance system.adapter.modbus.0 started with pid 31857 host-orangepi-iot 2016-10-19 20:58:31.239 info instance system.adapter.modbus.0 terminated with code 0 (OK) modbus-0 2016-10-19 20:58:31.204 info terminating host-orangepi-iot 2016-10-19 20:58:31.157 info stopInstance system.adapter.modbus.0 killing pid 31773 host-orangepi-iot 2016-10-19 20:58:31.155 info stopInstance system.adapter.modbus.0 host-orangepi-iot 2016-10-19 20:58:31.145 info object change system.adapter.modbus.0 modbus-0 2016-10-19 20:58:06.901 info List of port: [{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyUSB0","manufacturer":"1a86","serialNumber":"1a86_USB2.0-Serial","pnpId":"usb-1a86_USB2.0-Serial-if00-port0","vendorId":"0x1a86","productId" modbus-0 2016-10-19 20:57:53.650 warn Error: connect ECONNREFUSED 127.0.0.1:502 modbus-0 2016-10-19 20:57:52.541 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.modbus iobroker 2016-10-19 20:57:49.956 info exit 0 iobroker 2016-10-19 20:57:49.936 info host.orangepi-iot object system.adapter.modbus.0 created`iobroker upload modbusу тебя версия старая
У меня свисток зацепило с 0.4.1, пока нечем упровлять
log
inMem 2016-10-19 18:21:16.512 debug message *.logging system.adapter.admin.0.logging val=false, ack=true, ts=1476890476494, q=0, from=system.adapter.admin.0, lc=1476890476494 modbus-0 2016-10-19 18:21:11.815 debug sendTo "listUart" to system.adapter.admin.0 from system.adapter.modbus.0 modbus-0 2016-10-19 18:21:11.813 info List of port: [{"comName":"/dev/ttyS0"},{"comName":"/dev/ttyS1"},{"comName":"/dev/ttyS2"},{"comName":"/dev/ttyS3"},{"comName":"/dev/ttyUSB0","manufacturer":"1a86","serialNumber":"1a86_USB2.0-Ser_","p inMem 2016-10-19 18:21:11.637 debug message messagebox.system.adapter.modbus.0 messagebox.system.adapter.modbus.0 command=listUart, message=null, from=system.adapter.admin.0, message=null, id=244, ack=false, time=1476890471631, _id=75 inMem 2016-10-19 18:21:10.952 debug message *.logging system.adapter.admin.0.logging val=true, ack=true, ts=1476890470933, q=0, from=system.adapter.admin.0, lc=1476890470933 inMem 2016-10-19 18:20:26.355 debug message modbus.0.* modbus.0.info.pollTime val=8, ack=true, ts=1476890426342, q=0, from=system.adapter.modbus.0, lc=1476890426342 inMem 2016-10-19 18:20:26.346 debug message modbus.0.* modbus.0.info.connection val=true, ack=true, ts=1476890426332, q=0, from=system.adapter.modbus.0, lc=1476890426332 modbus-0 2016-10-19 18:20:26.330 info Connected to slave modbus-0 2016-10-19 18:20:25.459 info starting. Version 0.4.1 in /opt/iobroker/node_modules/iobroker.modbus modbus-0 2016-10-19 18:20:25.349 debug statesDB connected modbus-0 2016-10-19 18:20:25.320 debug objectDB connected host-Server-PC 2016-10-19 18:20:23.522 info instance system.adapter.modbus.0 started with pid 17789 host-Server-PC 2016-10-19 18:20:23.480 info object change system.adapter.modbus.0 host-Server-PC 2016-10-19 18:19:55.221 info object change system.adapter.modbus.0 -
Мы достаточно близко подошли к решению.
Попробуй ещё раз обновиться `
0.4.1Теперь COM порт запоминает!
Я вижу появился бонус "RTU over TCP".
Проверить работу RTU смогу только завтра (это часов через 12)
PS: Как можно виртуалку на ESXi с USB-COM портом победить? При выборе Not available.
! log
host-Bee-IoT 2016-10-19 22:57:09.443 info stopInstance system.adapter.modbus.0 killing pid 3868 host-Bee-IoT 2016-10-19 22:57:09.443 info stopInstance system.adapter.modbus.0 host-Bee-IoT 2016-10-19 22:57:09.443 info object change system.adapter.modbus.0 modbus-0 2016-10-19 22:56:50.658 warn Module serialport is not available modbus-0 2016-10-19 22:56:44.854 error IP address is not defined modbus-0 2016-10-19 22:56:44.815 warn Serial is not available modbus-0 2016-10-19 22:56:44.811 info starting. Version 0.4.1 in /opt/iobroker/node_modules/iobroker.modbus host-Bee-IoT 2016-10-19 22:56:44.368 info instance system.adapter.modbus.0 started with pid 3868 >! ```` IOB Ubunturoot@Bee-IoT:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 002 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@Bee-IoT:~# ls -l /dev/ttyS* /dev/ttyUSB*
crw-rw---- 1 root dialout 4, 64 окт 19 20:57 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 окт 19 20:57 /dev/ttyS1
crw-rw---- 1 root dialout 4, 74 окт 19 20:57 /dev/ttyS10
crw-rw---- 1 root dialout 4, 75 окт 19 20:57 /dev/ttyS11
crw-rw---- 1 root dialout 4, 76 окт 19 20:57 /dev/ttyS12
crw-rw---- 1 root dialout 4, 77 окт 19 20:57 /dev/ttyS13
crw-rw---- 1 root dialout 4, 78 окт 19 20:57 /dev/ttyS14
crw-rw---- 1 root dialout 4, 79 окт 19 20:57 /dev/ttyS15
crw-rw---- 1 root dialout 4, 80 окт 19 20:57 /dev/ttyS16
crw-rw---- 1 root dialout 4, 81 окт 19 20:57 /dev/ttyS17
crw-rw---- 1 root dialout 4, 82 окт 19 20:57 /dev/ttyS18
crw-rw---- 1 root dialout 4, 83 окт 19 20:57 /dev/ttyS19
crw-rw---- 1 root dialout 4, 66 окт 19 20:57 /dev/ttyS2
crw-rw---- 1 root dialout 4, 84 окт 19 20:57 /dev/ttyS20
crw-rw---- 1 root dialout 4, 85 окт 19 20:57 /dev/ttyS21
crw-rw---- 1 root dialout 4, 86 окт 19 20:57 /dev/ttyS22
crw-rw---- 1 root dialout 4, 87 окт 19 20:57 /dev/ttyS23
crw-rw---- 1 root dialout 4, 88 окт 19 20:57 /dev/ttyS24
crw-rw---- 1 root dialout 4, 89 окт 19 20:57 /dev/ttyS25
crw-rw---- 1 root dialout 4, 90 окт 19 20:57 /dev/ttyS26
crw-rw---- 1 root dialout 4, 91 окт 19 20:57 /dev/ttyS27
crw-rw---- 1 root dialout 4, 92 окт 19 20:57 /dev/ttyS28
crw-rw---- 1 root dialout 4, 93 окт 19 20:57 /dev/ttyS29
crw-rw---- 1 root dialout 4, 67 окт 19 20:57 /dev/ttyS3
crw-rw---- 1 root dialout 4, 94 окт 19 20:57 /dev/ttyS30
crw-rw---- 1 root dialout 4, 95 окт 19 20:57 /dev/ttyS31
crw-rw---- 1 root dialout 4, 68 окт 19 20:57 /dev/ttyS4
crw-rw---- 1 root dialout 4, 69 окт 19 20:57 /dev/ttyS5
crw-rw---- 1 root dialout 4, 70 окт 19 20:57 /dev/ttyS6
crw-rw---- 1 root dialout 4, 71 окт 19 20:57 /dev/ttyS7
crw-rw---- 1 root dialout 4, 72 окт 19 20:57 /dev/ttyS8
crw-rw---- 1 root dialout 4, 73 окт 19 20:57 /dev/ttyS9
crw-rw---- 1 root dialout 188, 0 окт 19 22:55 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 окт 19 22:55 /dev/ttyUSB1
root@Bee-IoT:~#! ````
-
у тебя версия старая
У меня свисток зацепило с 0.4.1, пока нечем упровлять `
На тот момент была только 0.4.0 (с доработками)А у тебя IOB локально работает или на виртуалке?
И как свисток свисток подключен к IOB? `
ioBroker локально работает, USB-RS485 настройка /dev/ttyUSB2. ttyUSB0 и ttyUSB1 мастера 1-wite. -
Serial RTU - на сколько смог проверил. (пока одно устройство ID 5 на arduino и 9 Holding регистров)
Работает…
Странно, если разорвать RS-485, а потом обратно соединить, то опрос невзобновляется. (Recconect time - 60000 ms)
В логах````
modbus-0 2016-10-20 10:27:07.660 warn Poll error count: 1 code: {"err":"timeout"}Приходится перезапускать драйвер. -
Serial RTU - на сколько смог проверил. (пока одно устройство ID 5 на arduino и 9 Holding регистров)
Работает…
Странно, если разорвать RS-485, а потом обратно соединить, то опрос невзобновляется. (Recconect time - 60000 ms)
В логах````
modbus-0 2016-10-20 10:27:07.660 warn Poll error count: 1 code: {"err":"timeout"}Приходится перезапускать драйвер. `Попробуй ещё раз обновиться.
-
Странно, если разорвать RS-485, а потом обратно соединить, то опрос невзобновляется. (Recconect time - 60000 ms)
В логах````
modbus-0 2016-10-20 10:27:07.660 warn Poll error count: 1 code: {"err":"timeout"}Приходится перезапускать драйвер. `Попробуй ещё раз обновиться. `
0.4.2Ждал 5 минут, опросы не взобновились.
Я только разрываю линию RS-485.
Кажется когда эксперементировал с ModbusTCP то при разрыве WiFi было так-же.
-
Добрый день всем.
Столкнулся со странной штукой - установлен драйвер 0.4.5, хочу затащить в IOB данные с контроллера datakom via Modbus RTU.
Для чего через socat был поднят виртуальный serial порт в системе (виртуалка VurtualBox).
Тестовая утилитка modpoll видит устройство через виртуальный порт и прекрасно получает данные:
./modpoll -m rtu -a 1 -t 4 -r 48 -b 9600 -p none /dev/ttyvir0! modpoll 3.4 - FieldTalk™ Modbus(R) Master Simulator
! Copyright (c) 2002-2013 proconX Pty Ltd
! Visit http://www.modbusdriver.com for Modbus libraries and tools.
! Protocol configuration: Modbus RTU
! Slave configuration...: address = 1, start reference = 48, count = 1
! Communication.........: /dev/ttyvir0, 9600, 8, 1, none, t/o 1.00 s, poll rate 1000 ms
! Data type.............: 16-bit register, output (holding) register table
! -- Polling slave... (Ctrl-C to stop)
! [48]: 120
! – Polling slave... (Ctrl-C to stop)
! [48]: 120
! – Polling slave... (Ctrl-C to stop)
! [48]: 120
! – Polling slave... (Ctrl-C to stop)
! [48]: 120
Но тут мое счастье и закончилось. Драйвер не видит этот порт в упор в списке. Права 666 не помогли.Решил немного обмануть драйвер, сделал виртуальный порт как ttyS33. Результат - драйвер не видит ничего вообще. В списке undefined.
Как пофиксить, никто не знает?
-
Можешь создать в папке node_modules/iobroker.modbus файл port.js:
var serialport = require('serialport'); serialport.list(function (err, ports) { console.log(JSON.stringify(ports, null, 2)); process.exit(); });Запустить его из консоли node port.js
Вот что я вижу:
C:\ioBroker\node_modules\ioBroker.modbus>node port.js [ { "comName": "COM3", "manufacturer": "Intel", "pnpId": "PCI\\VEN_8086&DEV_1E3D&SUBSYS_ABCDED&REV_04\\3&11583666&0&B3" }, { "comName": "COM1", "manufacturer": "(����������� �����)", "pnpId": "ACPI\\PNP0501\\1" } ]А у тебя?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginSupport us
532
Online32.7k
Users82.6k
Topics1.3m
Posts