How stepfunc/rodbus works
Rodbus is a commercial Modbus client/server library with TCP, RTU serial, TLS, retries, decoding controls, and C/Java-oriented FFI. The main client workflow is user or binding API -> channel setup -> transport/session -> Modbus request encoding and exchange -> callback or returned values. The server workflow is remote Modbus client -> transport listener -> session -> unit-ID handler -> application data. Sampled code strongly supports transport, TLS authorization, handler dispatch, FFI database access, and generated binding surfaces; some client internals are inferred only from module structure.
Main entry points: client.rs Native FFI API · channel.rs Client Channel · tcp/server.rs TCP Server · src/server.rs FFI Server API
Components 23
Client API
- CLI Client
rodbus-client/src/main.rs - Client Channel
rodbus/src/client/channel.rs - Request Tasks
rodbus/src/client/task.rs
Protocol Core
- Request Codecs
rodbus/src/client/requests - Frame Layer
rodbus/src/common/frame.rs - Decode Controls
rodbus/src/decode.rs
Transports
- TCP Client
rodbus/src/tcp/client.rs - RTU Client
rodbus/src/serial/client.rs - TLS Client
rodbus/src/tcp/tls/client.rs
Server Runtime
- TCP Server
rodbus/src/tcp/server.rs - RTU Server
rodbus/src/serial/server.rs - TLS Server
rodbus/src/tcp/tls/server.rs - Server Sessions
rodbus/src/server/task.rs - Handler Map
rodbus/src/server/handler.rs - Address Filter
rodbus/src/server/address_filter.rs
FFI Surface
- Native FFI API
ffi/rodbus-ffi/src/client.rs - FFI Runtime
ffi/rodbus-ffi/src/runtime.rs - FFI Server API
ffi/rodbus-ffi/src/server.rs - FFI Database
ffi/rodbus-ffi/src/database.rs - Binding Schema
ffi/rodbus-schema/src/client.rs
Other components
- Application User
- Modbus Client
- Modbus Device
Connections 31
- Application User → CLI Client: invokes
- Application User → Native FFI API: invokes
- CLI Client → TCP Client: opens
- CLI Client → RTU Client: opens
- Native FFI API → FFI Runtime: uses
- Native FFI API → TCP Client: creates
- Native FFI API → RTU Client: creates
- Native FFI API → TLS Client: creates
- TCP Client → Client Channel: returns channel
- RTU Client → Client Channel: returns channel
- TLS Client → Client Channel: returns channel
- Client Channel → Request Tasks: dispatches
- Request Tasks → Request Codecs: encodes requests
- Request Tasks → Frame Layer: frames traffic
- Client Channel → Decode Controls: sets decoding
- Frame Layer → Modbus Device: exchanges frames
- Modbus Client → TCP Server: connects
- Modbus Client → RTU Server: connects
- TCP Server → Address Filter: filters peers
- TCP Server → TLS Server: upgrades TLS
- TCP Server → Server Sessions: starts sessions
- RTU Server → Server Sessions: starts sessions
- TLS Server → Server Sessions: authorizes sessions
- Server Sessions → Handler Map: dispatches requests
- Handler Map → FFI Database: reads and writes
- FFI Server API → FFI Database: configures data
- FFI Server API → TCP Server: starts server
- FFI Server API → RTU Server: starts server
- FFI Server API → TLS Server: configures TLS
- Binding Schema → Native FFI API: defines bindings
- Client Channel → CLI Client: returns results