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

Printing percentage complete data #32

Open
orangevan opened this issue Jan 15, 2021 · 4 comments
Open

Printing percentage complete data #32

orangevan opened this issue Jan 15, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@orangevan
Copy link

orangevan commented Jan 15, 2021

Hi Andy, I have run some comparitive TCP dumps from the flashprint software and the adventure client.
I see the ADV client checks ~M119 and ~M105 to get the data it shows on the status page.
Flashprint also check ~M27 to capture the Percent complete.
I think just adding a query to ~M27 would provide you the ability to display Percent complete. Thoughts?
TCP REQUEST FOR M27 ~M27
TCP RESPONSE TO M27 REQUEST CMD M27 Received. SD printing byte 72/100 ok

@andycb
Copy link
Owner

andycb commented Jan 16, 2021

This is great. I like it. If it’s something you’re interested in, I’m totally happy to take a PR to add this. Else, I’ll track it here in the backlog for me to get to.

@andycb andycb added the enhancement New feature or request label Jan 16, 2021
@orangevan
Copy link
Author

If i was skilled enough to code this in, i totally would take a swing at it. Unfortunately i'm not quite there. I will need to wait for you to get to it in the backlog of features. (note, i think the remembering the IP address (and/or discovering IP by sending the UDP packet on 18000 or 19000 i dont remember which) is definitely more useful than the percentage feature)

@orangevan
Copy link
Author

In line with this, I think it would be awesome if the Status screen displayed the current extruder position (X,Y,Z) from M114. The A Parameter is how much filament has been extruded in millimeters. Once it gets up to 1000, it resets to 0. (in the gCode files, it uses a G92 E0 code to set it back to 0 for the next meter. I don't know if there's any way to keep track of it for a running tally, but if you count the number of G92 E0's in a gcode file and then take the last G1 E value it's the total length of filament.... (I foresee a fair amount of challenges to implement the A value accurately, but XYZ I expect would about as easy as M27...

Anyhow here's an example of the M114 from my Debug screen during a print
~M114\n
CMD M114 Received. \nX:31.57 Y:31.56 Z:5.35 A:825.2 B:0 \nok \n

@Gaweringo
Copy link
Contributor

discovering IP by sending the UDP packet on 18000 or 19000

I found a github repo which supposedly has this ability. I haven't really looked through it. Just now found it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants