Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mmu: Don't log Query (Q0) requests/responses when MMU is Idle #4455

Closed
wants to merge 1 commit into from

Conversation

gudnimg
Copy link
Collaborator

@gudnimg gudnimg commented Oct 19, 2023

An idea I have to resolve #4414

If a Query is running in Idle state machine, then don't log anything but still allow asynchronous requests/responses to be logged. For example a register read via M707 will still show up fine.

image

This makes the serial log muuch cleaner when the MMU is idle. When running a printjob, it is only when a command such as toolchange is running that everything will be logged again.

If a Query is running in Idle state machine, then don't log anything.

But still allow asynchronous requests to be logged.
For example a register read via M707.

This makes the serial log muuch cleaner when the MMU is idle.
@github-actions
Copy link

All values in bytes. Δ Delta to base

Target ΔFlash ΔSRAM Used Flash Used SRAM Free Flash Free SRAM
MK3S_MULTILANG 42 0 246064 5633 7888 2559
MK3_MULTILANG 42 0 245350 5642 8602 2550

@gudnimg
Copy link
Collaborator Author

gudnimg commented Nov 25, 2023

Closing this PR since it won't be merged. I will keep the branch open though since it may be useful.

@gudnimg gudnimg closed this Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MMU MMU2s and MMU3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Too much MK3S<->MMU2 communication logging on serial port
2 participants