Gcode visualizer
-
The firmware is already reporting the xyze location of the toolpath, couldn't we extrapolate that to be the toolpath position within a gcode visualization? This is a really interesting idea and might be easy enough to implement… one problem I forsee would be with large gcode files causing problems. I've had 1GB gcode files before, and I doubt the web interface would survive trying to visualize that (in 3d).
-
I've just started using a DuetWifi and the gcode viewer is the only thing I miss from my previous OctoPi setup. One option certainly to have a look at their implementation. I'm perfectly happy with the Hudbrog javascript visualizer , it is the one I use for debugging print problems. Don't personally need a 3D view of the model here, rather something to allow checking the model overall and hopefully live feedback about layer progress.
-
Yes, the Gcode viewer in OctoPrint is perfectly adequate. I read it was similar to that used in http://gcode.ws
-
No progress on this?
Would love to see this feature! -
-
Agree with robm, DWC is really good, but adding the gcode visualization would be a great feature.
-
I think they could add a premium dwc that gives them more incentive in exchange for updates sooner and maybe extr features like this
-
I've been working on implementing gcode.ws in to dwc, currently have it embeded and showing the current layer progress. Working on implementing it in a less hacky way currently
-
That looks really sweet!
Will it allow preview (eg if you have a print in simulation mode) ?- I'm in the habit (octoprint) of quickly sanity-checking the print (esp. base layers/support locations+types) before hitting the no-return button
-
Thats great!
Can you submit it as a pull request to the Github repository?
-
That looks really sweet!
Will it allow preview (eg if you have a print in simulation mode) ?- I'm in the habit (octoprint) of quickly sanity-checking the print (esp. base layers/support locations+types) before hitting the no-return button
Not currently, The simulate mode doesn't update the current layer info, I could calculate the layer using the z position. Is there a reason the simulation mode doesn't provide layer statistics?
Thats great!
Can you submit it as a pull request to the Github repository?
Will do when I'm done, Still a lot that needs to be added before it's on par with Octoprint
