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

Inserting beeps or tunes (or other g-code) into percentage-specified positions in generated g-code #17721

Open
Lunarien opened this issue Dec 21, 2023 · 2 comments
Labels
Status: Triage This ticket requires input from someone of the Cura team Type: New Feature Adding some entirely new functionality.

Comments

@Lunarien
Copy link

Is your feature request related to a problem?

Not quite related to a problem. Rather, it could be useful if one could play a beep at a specific percentage of the print, in order to have a better sense of time passing during the print. For example, one could configure the printer to beep or play a tune every 10% of the print.

Describe the solution you'd like

Perhaps the menu in which you manage the start and end g-code for your printer presets could also be used to configure the g-code to be inserted at specific percentages of the print.
This is the menu I mean:
image
Maybe the feature I'm requesting could be configurable under the two g-code editor parts on the image.

Another way of implementing something like this could be to add a setting to the slicing settings that would just make it possible for the printer to beep either after every N% have passed, or at specific percentages, selected via text entry into a text field next to the option, so somewhere like this:
image
I would expect the format to be numbers separated by commas, so, for example, like 10,25,50,75,100

Describe alternatives you've considered

I had an idea of making a Python script that would determine the line numbers by given percentages, and would then insert the g-code for a beep at those lines of slicer-produced g-code. I didn't (yet?) make the script, though.
It would be nice to have it built into Cura, though, so that one doesn't have to use custom python scripts to accomplish this.

Affected users and/or printers

All users who have their printer in the same room as themselves during the print, and that have a printer that supports beeping with at least one tone, and also want to better determine time-effectiveness of the print (and how much they can do/work on during the print).

Additional information & file uploads

You can implement either just beeping/playing a tune at certain percentages, or you can implement adding any g-code instructions at certain percentages of the print.
I wouldn't consider this a high priority feature to have, but it would be nice, and although I don't know the codebase of Cura, it might be a quick feature to add if you make it a percentage-beeping setting. Not as quick if you make it a menu in the place aforementioned.

Sorry if something isn't understandable enough. I can explain parts that might not be concise enough.

@Lunarien Lunarien added Status: Triage This ticket requires input from someone of the Cura team Type: New Feature Adding some entirely new functionality. labels Dec 21, 2023
@5axes
Copy link
Contributor

5axes commented Dec 21, 2023

@GregValiant
Copy link
Collaborator

GregValiant commented Dec 21, 2023

There is a blast from the past. It changed some between that version and the one I finally put up in a pull request.

Remco Burema wanted me to make a lot of changes to the "Advanced Cooling" Script. I informed him I didn't know how (what the hell is a lambda function/thing?) and closed the pull request. In fact, I closed them all. I'll never be a software engineer.
They may be written like crap but the scripts work. I reminded him about bug #14764 . No doubt all that code looked nice, but if it won't even slice a benchy then what's the point.

I've put together an app in Visual Basic and ported over all my post processors. It will be compiled so nobody will see my ugly code. So far I've got 5 slicers supported. I'll start working on Orca this week. Who knows, maybe I can make a dollar (or a Euro) off it.
The final version of Insert at Layer Change I passed to you on the forum. It's certainly cleaner. It includes functionality for "One at a Time" projects as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Triage This ticket requires input from someone of the Cura team Type: New Feature Adding some entirely new functionality.
Projects
None yet
Development

No branches or pull requests

3 participants