JoelStienlet
JoelStienlet
Hello, Sadly this bug report doesn't provide much information, we have the form without the answers. I haven't been able to reproduce this on fedora 31.
Hello, Just my 2 cent on this one: I think there is already a way to set a custom callback for this: https://github.com/stephane/libmodbus/blob/master/doc/modbus_rtu_set_custom_rts.txt I've tried toggling RTS on an FTDI...
Also to note that there is a bug when using tcdrain() with FTDI chips (that you can call to wait until all the data have been sent). link to another...
I totally agree. After reading the datasheet again, it looks like the TXDEN pin is shared between two functionalities: RI and TXDEN, but sadly RI is the default functionality. To...
For the hardware question: I dit the test setting bit 4 at 0x0B in the eeprom of my FT4232H mini-module board, and indeed the TXDEN pin goes high during transmission...
I think you have to call modbus_set_slave() before modbus_read_registers()
I think it would be better to make the necessary checks in the wrapper with: int modbus_get_slave(modbus_t *ctx); before every call of modbus_read_registers().
This change will not break any existing code I suppose. But once the change is made, there is no going back, as reverting from errno to assert() could break newer...
Some additional thoughts: assert() could also cause problems in other situations: - it makes it more difficult to perform proper logging of the error. - we don't know if some...
I think it should be || indeed. According to a documentation: "Protocol Identifier (2 bytes): This field is always 0 for Modbus services and other values are reserved for future...