我目前正在尝试在商用路由器(Ursalink的UR71)和Modbus RTU(施耐德电气的ZBRN2)之间建立Modbus通信。
UR71路由器在Linux OpenWRT上运行LEDE-17.01 Python是v2.7.13 Python使用modbus-tk 0.5.7和pyserial 3.4
我的应用程序需要modbus读取(FC03)和modbus多次写入(FC16)
问题是我成功地将计算机(Windows 10)作为modbus主站运行,但是当我切换为UR71作为modbus主站时,FC16不再工作并发送:
(, ModbusInvalidResponseError('Response length is invalid 0',), )
我制作了一个小示例应用程序来向您展示:
class ModbusLoop(Thread):
def __init__(self):
Thread.__init__(self)
def run(self):
while (True):
try:
# MODBUS READ
logger.debug("Reading modbus FC03...")
result = rtu.execute(1, tkCst.READ_HOLDING_REGISTERS, 6100, 60)
logger.debug(result)
time.sleep(1)
#MODBUS WRITE SINGLE RESISTER
logger.debug("Reading modbus FC06...")
result = rtu.execute(1, tkCst.WRITE_SINGLE_REGISTER, 2010, output_value = 3841)
logger.debug(result)
result = rtu.execute(1, tkCst.WRITE_SINGLE_REGISTER, 2010, output_value = 4097)
logger.debug(result)
time.sleep(1)
logger.debug("Reading modbus FC16...")
result = rtu.execute(1, tkCst.WRITE_MULTIPLE_REGISTERS, 2010, output_value = [3841])
logger.debug(result)
result = rtu.execute(1, tkCst.WRITE_MULTIPLE_REGISTERS, 2010, output_value = [4097])
logger.debug(result)
except:
logger.error(sys.exc_info())
finally:
logger.debug("")
time.sleep(5)
Modbus的初始化如下:
rtu = ur71_modbus.UR71RTU(ur71_init.port_id, ur71_init.baudrate)
rtu.set_timeout(2.0)
rtu.set_verbose(True)
UR71RTU包含串行配置:
ser = serial.Serial(port=self.dev, baudrate=baudrate, bytesize=serial.EIGHTBITS, parity=serial.PARITY_EVEN, stopbits=serial.STOPBITS_ONE, xonxoff=0)
这导致:
2.7.13 (default, Aug 21 2018, 20:45:19)
run.py [2018-11-30 14:00:58 PM] [INFO] Modbus initialization
ur71_modbus.py [2018-11-30 14:00:58 PM] [DEBUG] Linux
modbus_rtu.py [2018-11-30 14:00:58 PM] [INFO] RtuMaster /dev/ttyS1 is opened
run.py [2018-11-30 14:00:58 PM] [DEBUG] Reading modbus FC03...
modbus.py [2018-11-30 14:00:58 PM] [DEBUG] -> 1-3-23-212-0-60-0-87
modbus.py [2018-11-30 14:00:58 PM] [DEBUG]
run.py [2018-11-30 14:00:58 PM] [DEBUG] (0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0)
run.py [2018-11-30 14:00:59 PM] [DEBUG] Reading modbus FC06...
modbus.py [2018-11-30 14:00:59 PM] [DEBUG] -> 1-6-7-218-15-1-109-117
modbus.py [2018-11-30 14:00:59 PM] [DEBUG]
run.py [2018-11-30 14:00:59 PM] [DEBUG] (2010, 3841)
modbus.py [2018-11-30 14:00:59 PM] [DEBUG] -> 1-6-7-218-16-1-101-69
modbus.py [2018-11-30 14:00:59 PM] [DEBUG]
run.py [2018-11-30 14:00:59 PM] [DEBUG] (2010, 4097)
run.py [2018-11-30 14:01:00 PM] [DEBUG] Reading modbus FC16...
modbus.py [2018-11-30 14:01:00 PM] [DEBUG] -> 1-16-7-218-0-1-2-15-1-7-154
modbus.py [2018-11-30 14:01:02 PM] [DEBUG]
run.py [2018-11-30 14:01:02 PM] [ERROR] (, ModbusInvalidResponseError('Response length is invalid 0',), )
run.py [2018-11-30 14:01:02 PM] [DEBUG]
Windows中的相同代码导致:
2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:30:26) [MSC v.1500 64 bit (AMD64)]
INFO:modbus_tk:RtuMaster COM4 is opened
DEBUG:ur71:Serial link checked
DEBUG:ur71:Reading modbus FC03...
DEBUG:modbus_tk:-> 1-3-23-212-0-60-0-87
DEBUG:modbus_tk:
DEBUG:ur71:(0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0)
DEBUG:ur71:Reading modbus FC06...
DEBUG:modbus_tk:-> 1-6-7-218-15-1-109-117
DEBUG:modbus_tk:
DEBUG:ur71:(2010, 3841)
DEBUG:modbus_tk:-> 1-6-7-218-16-1-101-69
DEBUG:modbus_tk:
DEBUG:ur71:(2010, 4097)
DEBUG:ur71:Reading modbus FC16...
DEBUG:modbus_tk:-> 1-16-7-218-0-1-2-15-1-7-154
DEBUG:modbus_tk:
DEBUG:ur71:(2010, 1)
DEBUG:modbus_tk:-> 1-16-7-218-0-1-2-16-1-15-170
DEBUG:modbus_tk:
DEBUG:ur71:(2010, 1)
DEBUG:ur71:
我不知道是什么原因引起的。
我调查了超时(最多10s),inter_byte_timeouts等,但是如果它适用于FC06,为什么它对于FC16应该有所不同?
我测试了minimalmodbus lib,问题是一样的,所以我不认为错误来自modbus-tk lib
我的想法不多了,如果有人已经遇到这种问题,将不胜感激。 也许我现在不了解Linux和Windows上串行端口的某些差异(但是FC06为何还能工作?)?
最好的祝福