Skip to content

A delightful little Modbus library for Java.

active 2023-08-212026-05-09 (UTC)

Complete coverage26,560 / 26,560 hourly files (100%) · 2 absent upstream2023-08-152026-08-25 (UTC)
Events
157
Pushes
79
Pull requests
0
Issues
7
Stars
28
Forks
5

Activity over time

Daily event counts in the loaded window

Line chart, 993 days from 2023-08-21 to 2026-05-09. Pushes: 79 total, peak 8 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 7 total, peak 1 in a day. Comments: 16 total, peak 4 in a day. Stars: 28 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
msqr927909
maisun3002
SpencerLommel2001
vishalkgajjar2002
dafik1001
ladrl1001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#13msqr2026-03-12 22:46
    Allow compatibility with Netty 4.1.x
  • Issue comment#13ladrl2026-03-12 15:12
    Allow compatibility with Netty 4.1.x
  • Issue#12msqr2026-03-11 23:57
    Netty 4.1.x compatibility
  • Issue#10SpencerLommel2025-08-04 05:42
    Coil Support
  • Issue comment#10SpencerLommel2025-08-04 05:41
    Coil Support
  • Issue comment#10msqr2025-08-04 05:10
    Coil Support
  • Issue comment#11msqr2025-07-26 23:18
    NettyTcpModbusServer to produce Client connecting and disconnecting events
  • Issue#11msqr2025-07-26 23:18
    NettyTcpModbusServer to produce Client connecting and disconnecting events
  • Issue comment#11vishalkgajjar2025-07-26 15:28
    NettyTcpModbusServer to produce Client connecting and disconnecting events
  • Issue comment#11vishalkgajjar2025-07-26 04:05
    NettyTcpModbusServer to produce Client connecting and disconnecting events
  • Issue comment#11msqr2025-07-26 03:16
    NettyTcpModbusServer to produce Client connecting and disconnecting events
  • Issue#11vishalkgajjar2025-07-24 03:57
    NettyTcpModbusServer to produce Client connecting and disconnecting events
  • Issue#9msqr2024-08-01 18:43
    Question regarding my use-case
  • Issue comment#9msqr2024-07-27 18:18
    Question regarding my use-case
  • Issue comment#9maisun2024-07-27 16:14
    Question regarding my use-case
  • Issue comment#9maisun2024-07-27 06:52
    Question regarding my use-case
  • Issue comment#9msqr2024-07-26 21:55
    Question regarding my use-case
  • Issue#9maisun2024-07-26 09:53
    Question regarding my use-case
  • Issue#8msqr2023-10-26 18:48
    After about 24 hours of operation, starting the client before reading and closing after reading in 60s intervals, I get an endless loop of the client cannot be started because there is a timeout on closing
  • Issue comment#8msqr2023-10-26 18:48
    After about 24 hours of operation, starting the client before reading and closing after reading in 60s intervals, I get an endless loop of the client cannot be started because there is a timeout on closing
  • Issue comment#8dafik2023-10-26 12:11
    After about 24 hours of operation, starting the client before reading and closing after reading in 60s intervals, I get an endless loop of the client cannot be started because there is a timeout on closing
  • Issue comment#7msqr2023-10-19 20:25
    call client.start().get(); on stopped client causes error.
  • Issue comment#8msqr2023-10-19 20:24
    After about 24 hours of operation, starting the client before reading and closing after reading in 60s intervals, I get an endless loop of the client cannot be started because there is a timeout on closing

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 28 stars here means stars gained during the window, not the repo's star count.