Gcode visualizer
-
I think it would look pretty cool if there was a current layer visualization panel on the web interface. Maybe it could update with what paths it has drawn so far. I was thinking just a simple 2D one similar to the way pronterface displays G-code. I don't know how resource intensive it might be but I think it might be a cool extra feature if Chris or someone has the time to spare.
-
This sounds like something best done client side in the browser.
-
Thats what I was thinking. If I can find the time to learn what I need to do to implement it myself I'll sure try.
-
Maybe this? https://github.com/hudbrog/gCodeViewer
-
iDevelo, I was asked to use that plugin about a year ago, but never started working on it. The problem I see with that one is that it only supports rather primitive views.
I stumbled upon this JS plugin which looks quite promising at first sight: https://github.com/joewalnes/gcode-viewer
Does anyone know other G-code visualisation plugins? Which G-code viewer would you prefer?
-
I think that for initial implementation, just showing the current layer, plus being able to look at other layers would be a good start.
A 3d view is nice to have.
In the longer term the ability to show where within the layer the tool head is visually could be useful but that would require tighter feedback between the firmware and the web interface so is not a priority for version 1 (at least that's what I think).
-
Yeah, I was just thinking a view of the current layer + the ability to see the next few layers in just a 3D view. It would be cool to have the progress drawn like in Pronterface/RH, but that would probably require more feedback from the firmware. I haven't really looked around at any viewers, but I can't check out the one that chris linked because the demo site isn't available anymore. I'm not real picky though. I do like viewers like KISS's built in viewer a little better though because the colors are bright and high contrast, which makes it easy to distinguish the path from the background. The joewalnes viewer color scheme seemed a bit too grey on black for my taste.
-
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
