freemodbus icon indicating copy to clipboard operation
freemodbus copied to clipboard

A Modbus ASCII/RTU and TCP implementation

Results 7 freemodbus issues
Sort by recently updated
recently updated
newest added

mb_slave_samlpe msh >mb_slave_samlpe Function[_rt_mutex_take]: scheduler is not available (0) assertion failed at function:_rt_mutex_take, line number:1169

Running the example rtu slave with no flow control. Just using USB to UART0 for now. When I use FinSH to run the slave demo, everything seems to work, but...

在user_mb_app_m.c的eMBMasterRegHoldingCB函数中直接将eMode赋值为MB_REG_WRITE了,然后 在mbfuncholding_m.c的eMBMasterFuncReadHoldingRegister函数中,使用MB_REG_READ 模式调用eMBMasterRegHoldingCB函数。 这种方式导致使得eMBMasterRegHoldingCB的eMode参数失去了意义, 感觉将eMBMasterRegHoldingCB中的eMode = MB_REG_WRITE;代码去掉,然后 eMBMasterFuncReadHoldingRegister函数中使用MB_REG_WRITE作为参数调用eMBMasterRegHoldingCB函数,这样从操作是否更合理一点? 同样的问题也存在线圈操作相关的接口。

Hi, just tested out the tcp-modbus pack, but it seems to hang almost every time on short data or bad data. Seems to happen here: xMBTCPPortSendResponse(const UCHAR *pucMBTCPFrame, USHORT usTCPLength)...

the problem is triggered following these steps: 1.1 - Plug the USB RS485 interface and run a modbus server script in PC side (uModbus "python") 1.2 - Request reading coils...

我这里所说的超时既不是T35也不是T15,而是从机超时应答的等待时间,可以看到协议栈中有两个这样的参数,不是很理解这两个参数的区别?比如说 读保持寄存器函数 `eMBMasterReqErrCode eMBMasterReqWriteHoldingRegister( UCHAR ucSndAddr, USHORT usRegAddr, USHORT usRegData, LONG lTimeOut );` 这里最后一个设置为 RT_WAITING_FOEVER,经常会接收错误,但是如果我修改了宏定义中的freemodbus/modbus/include/mbconfig.h中的 `/*! \brief If master send a frame which is not broadcast,the master will wait sometime...