Cliff Brake

I can see where the defaults of 0, 0 are not desirable for most scenarios. In the application I'm working on, I need to probe a number of RS485 addresses...

That would help, but the simple solution for my scanning task is still 0/0 bytes/timeout. Anything else requires that I implement packet parsing logic and keep track of elapsed time...

I've done quite a bit of work with modbus here: https://pkg.go.dev/github.com/simpleiot/simpleiot/modbus The documentation is not current -- it now supports TCP as well as RTU. I would consider splitting this...

SIOT can also be used to simulate modbus devices (functions as server) -- I find this handy for modbus development and testing. The following demonstrates client functionality, but server is...

The problem with controlling the RS485 direction control from the application layer is you don't know exactly when the serial driver buffer/fifo is empty. The idea behind the driver/hardware control...

I found one fork where RS485 support has been added: https://github.com/shaunco/go-serial/commit/151562fc1a50a09a1709aabcd3e12f3d5f83af01

closing this as this project appears to not be maintained. I started a new modbus library that will implement both client and server functionality: https://github.com/simpleiot/simpleiot/tree/master/modbus Examples: https://github.com/simpleiot/simpleiot/blob/master/modbus/rtu-end-to-end_test.go https://github.com/simpleiot/simpleiot/blob/master/cmd/modbus-client/main.go https://github.com/simpleiot/simpleiot/blob/master/cmd/modbus-server/main.go

@kraj So I set up a new user with UID 1007, and then added --user $UID:$GID to docker command. It all seems to work, except I get this on the...

I'll try fixuid next unless there is something better.

ok, that works for me -- I'll test a build under a different user just to make sure it works, and then commit.