Skip to content

The future of ModbusScope #429

Closed
Closed

Description

@jgeudens

The future of ModbusScope

ModbusScope started as a personal project, but over the years it has grown into something people actually use. It has been a great way for me to deepen my experience with C++ and Qt, and I am proud of what it has become.

How the project is run

I am the sole maintainer, and I intend to keep it that way. This project works best as a single-maintainer effort, so I am not looking to grow a contributor community.

Bug reports, feature ideas, and general feedback are always welcome. That kind of input helps guide the project and keeps it moving in the right direction.

What sets this project apart from a vibe-coded one is long-term commitment. The focus is on continuously improving the application and supporting its users, not just shipping something and moving on. I am committed to doing that for the long run.

How widely is this being used

There is activity in the issue tracker, and download numbers suggest usage beyond my own workplace. Still, those numbers only tell part of the story.

I am considering adding a simple way to monitor update checks to get a better sense of active usage over time. This would only track anonymous usage metrics and would not collect any personal information.

If you are using ModbusScope, a short comment about how and where you use it would be very helpful. It gives me a better sense of how the project is being used in practice.

It would also be useful to know which functionality you rely on the most, and what parts of the application you find most valuable in your day-to-day work. On the other hand, if there are areas that feel unclear, confusing, or harder to use than they should be, I would like to hear about those as well.

What is coming next

I am actively exploring support for protocols beyond Modbus. The groundwork for this is already underway, and I am figuring out what shape it will take and how it will be made available. This could take different forms, including free, commercial, or donation-supported options.

The intent is to keep the existing Modbus functionality free, while keeping flexibility for how additional protocol support may be offered.

More details will follow as things become clearer.

Thanks for using ModbusScope and being part of its long-term journey.

Activity

  1. pinned this issue on Apr 17, 2026
  2. jgeudens commented on Jun 23, 2026

    @jgeudens
    MemberAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions