3D GCode Viewer integrated with DWC
-
Do you think on the long run the "color" could be somehow connected/attached to some sort of variable within filament-config.g and the actual number of extruders and their loaded filament? Just thinking out loud...
EDIT: (actually I am so impressed by the multi-colour-printer from deckingman, that I think that those multicolourprinters could get on the long run a relaistic visualization what colour the g-code wants to have and if that is realy loaded -> Of course this is maybe more complex with "mixing" hotends vs multiple independent colours after another but not mixing concepts)
-
@LB As I work toward further implementation some of that is totally possible. Originally this viewer popped up in a separate window and didn't collect any duet info. Since this is a plugin now it is much easier to access the object model and data that DWC captures.
Sample of changing extruders color just cause I happen to have one on hand.
-
@Sindarius said in 3D GCode Viewer integrated with DWC:
@LB As I work toward further implementation some of that is totally possible. Originally this viewer popped up in a separate window and didn't collect any duet info. Since this is a plugin now it is much easier to access the object model and data that DWC captures.
Awesome: On the long run I can imagine even a preview of "internal" files like movement-trajectories as lines/curves for bed-levelling and homing or that sort... on most cnc´s those are red-lines...
Yeah, as said, first thing for me would be a wire-frame for the absolut bounding-box of the machine. Second would be small crosses(or cross-hairs(?) I am not a native-english-speaker/-writer) for the absolut-csys (if active) and for the "actual"/temporary csys (with name written beside it would be nice e.g. a small "G5x") or something relative in this bounding box located (IF ACTIVE only of course)...
(As far as I remember the active csys like "G54" are already reflected in DWC when any but the machine-csys G53 is put active)
Sample of changing extruders color just cause I happen to have one on hand.
Looks great!
(
@dc42
)Do you think it is possible with the new conditional-g-code to defina a variable within filament-config.g for the hex-code (this is using a hex-code for the color it seems?)?
-
I'm really impressed. Will test when 3.2 be official release.
With things like that duet ecosystem winnings!! -
@CaLviNx said in 3D GCode Viewer integrated with DWC:
Seeing as we are now off on a tangent, what would be really useful is if there was a way to
have a camera integrated into the "cancel object" software/plugin or what ever you want to call, that could monitor when a segment has failed and automatically modify the g-code on the fly to stop the printer from extruding plastic for that segment.You may not like this, but there's also an octoprint plugin that does this. And yes it could become a plugin here as well.
https://www.thespaghettidetective.com/
The object cancelation functions already right now so that if you had a camera and you yourself saw an object fail, you could send the manual command to cancel that object.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M486_Object_cancellation
The gcode viewer functionality could enable a useful GUI for many features.
-
https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases/tag/0.6.5
Posted a new update. Cleaned up the side menu a bit.
https://user-images.githubusercontent.com/12520045/99151632-3acb8900-2662-11eb-920a-216d9a346b23.png -
@Phaedrux said in 3D GCode Viewer integrated with DWC:
@CaLviNx said in 3D GCode Viewer integrated with DWC:
Seeing as we are now off on a tangent, what would be really useful is if there was a way to
have a camera integrated into the "cancel object" software/plugin or what ever you want to call, that could monitor when a segment has failed and automatically modify the g-code on the fly to stop the printer from extruding plastic for that segment.You may not like this, but there's also an octoprint plugin that does this. And yes it could become a plugin here as well.
https://www.thespaghettidetective.com/
The object cancelation functions already right now so that if you had a camera and you yourself saw an object fail, you could send the manual command to cancel that object.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M486_Object_cancellation
The gcode viewer functionality could enable a useful GUI for many features.
Why would I not like it?
And I reiterate, it would be useful if :
that plugin could monitor when a segment has failed and automatically modify the g-code on the fly to stop the printer from extruding plastic for that segment.
And still this does not explain the reason why someone would even mention a feature that occurs in octoprint, and what relationship that feature has to do with the Author's gcode viewer,
-
@CaLviNx said in 3D GCode Viewer integrated with DWC:
And still this does not explain the reason why someone would even mention a feature that occurs in octoprint, and what relationship that feature has to do with the Author's gcode viewer,
Because he posted a photo showing a canceled object. (The one with the Xs over it) and you asked what the real world use was and veti told you what the use of cancelling an object is and posted a link to the origin of the feature in the form of the octoprint plugin. For such a big brain I'm surprised you're not following along here.
-
@Sindarius said in 3D GCode Viewer integrated with DWC:
https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases/tag/0.6.5
Hey I clicked on your link, could you help me where to find in the forum or duet-wiki a reference how to implement this plugin?
-
@LB upload the zip file via the systems tab.
There will be a pop up asking if you want to install the plugin.
It can then be activated under the plugins tab on the machine specific settings tab -
@LB I just posted a 0.7.0 with async loading
Download the zip from the release page and with the latest DWC 3.2 beta you can simply go to the system tab and upload the file to install the plugin.@jay_s_uk beat me to it
-
weird bug, it seems the bed rendered is too small. (see pic)
any idea?
same on safari and firefox. Mac os big sur.
-
@Thalios I have not yet implemented reading the axis limit so the bed size is fixed @ 235,235 at the moment.
-
I understand! I like it still!
-
@Thalios It's one of the next items on my list. I need to start refactoring some of the structure out into their own classes. Bed is one of my first ones. I plan to hopefully support bed texturing soon-ish and I have had requests to show a volume cube as well. So this will be a part of that. Glad you like
-
@Thalios Give 0.7.6 a shot. I have reworked a chunk of the bed logic so it should pick up the axes limits from the object model now.
https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases/tag/0.7.6Also added build volume. It's a little odd for deltas but it you look top down it works well enough for now.
-
@Sindarius your print area would be useful for other kinematics like scara, polar ... also.
-
works perfectly so far!
-
Implemented billboarded labels over each of the objects. Can be toggled on and off.
-
Should this be working with RRF 3.2b3?
I got an error saying the plugin couldn't be installed because DWC version wasn't correct
