Skip to content

Console "Show verbose" does not show raw machine responses (e.g. $?) #573

Closed

Description

@calmarc

Describe the bug
The "Show verbose" option in the Console does not work.

Even when enabled, the console only shows high-level messages like Device state changed: IDLE / JOG / HOME and never displays the actual raw responses from the controller (e.g. the full reply to $?, ?, $$, $I, etc.).

To Reproduce
Connect to a GRBL machine (Fox-Alien Vasto in my case)
Open the Console tab in the bottom panel
Enable "Show verbose"
Send $? or ? or $$
Observe that only state-change messages appear, no raw GRBL response
Expected behavior
With "Show verbose" enabled, the console should show the complete raw communication (including status reports like <Idle|MPos:...|WPos:...> and replies to $ commands).

Actual behavior
Only filtered high-level log lines are shown. Raw data is never visible.

Environment
Rayforge version: 1.13.0b1
OS: Linux
Machine: Fox-Alien Vasto (GRBL)
Connection: USB serial
Additional context
This makes debugging (checking soft limits, coordinate systems, buffer sizes, etc.) very difficult.

rayforge_debug_2026-10-16_23-41-14.zip

Activity

  1. knipknap commented on Oct 17, 2026

    @knipknap
    Contributor

    Hi, and thanks for the report plus the debug archive - that made this easy to pin down.

    You're seeing this correctly: the raw responses are no longer reaching the console at all. During the 1.13 rework I moved the GRBL serial communication out of the Python code into a new, faster session engine. The old implementation logged every line the machine sent (status reports, replies to $$ and $I, and so on) as log messages, which is exactly what the console and its "Show verbose" switch display. The new engine handles that communication internally and currently only reports higher-level events like state changes and connection status - so the verbose switch has nothing left to show. Your debug log confirms it: the session contains state changes, but not a single raw machine response.

    This is a bug on my side, not a setting you're missing. The fix is to have the new communication engine pass raw incoming (and outgoing) lines back into the logging pipeline again, so the console shows the full conversation as it did before - status polls behind the verbose switch, and everything else ($$, $I, welcome message, etc.) normally. I'll restore that in an upcoming build; in the meantime the session log files in the debug archive do contain the state changes, but unfortunately not the raw serial data either, so there's no good workaround for inspecting $$ output at the moment.

  2. added
    rca-doneA root cause analysis was attached
    pr-neededA PR is required to resolve this issue.
    pr-startedImplementation has started
    and removed
    pr-neededA PR is required to resolve this issue.
    on Oct 17, 2026
  3. knipknap commented on Oct 17, 2026

    @knipknap
    Contributor

    Fixed: #576

    The raw communication is back. The fix ships in two parts: the new raydriver 0.4.0 release now passes every line the device sends (status reports, ok/error acknowledgements, replies to $$ and $I, the welcome banner) back to Rayforge, and the driver feeds those lines into the console's logging pipeline again. With "Show verbose" enabled you'll see the status polls; everything else shows up normally, just like before the 1.13 rework. Outgoing commands are logged too.

    Thanks again for the debug archive — it made pinning this down straightforward.

  4. knipknap commented on Oct 17, 2026

    @knipknap
    Contributor

    This is now in main and will be included in Rayforge 1.13.0-beta2. Thank you for reporting!

  5. added a commit that references this issue on Oct 18, 2026
    84a88f4
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

    bugSomething isn't workingrca-doneA root cause analysis was attached

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions