Silly but I can’t find the answer to this one. Once you’ve finished your run on a part how do you save it so everything is ready to go next time?
Nothing I do seems to work. I’ve saved the GCode that was created from dxf files but evidently not correctly as when I try to reload they are not seen. (I assume not save in the correct format). Outside of the LW… I can open and view the GCode also.
Thanks, I considered trying that but …well… I just didn’t when I should have.
I think some of my problems are I worked with commercial CNC Machine Centers and Turning Centers for far too many years and I keep looking for the same vernacular without realizing it…
@Ariel_Yahni_UniKpty : Agreed, but the OP said he’s got problems saving/reloading the gcode… That’s what my reply was toward…
I often do both… If I don’t need to change, I’ll reuse the gcode (saves time), otherwise I’ll grab the workspace and do my changes!
Also I often do my gcode generation on my game-rig (overclocked i5, 32GB RAM) instead of the Pipo that’s on my FABkit, as that makes a huge difference as far as time goes. Then I save both workspace and gcode, and open both on the Pipo to actually do the lasing!
saving the workspace is the handiest tool for that purpose. I have had my computer start to lock up and had I not saved my workspace I would have to recreate all my operations(and I tend to split them up quite a bit so that the outsides cut last). Now its load workspace, generate, connect, and fire!
OK I know why I couldn’t save files. It also happened in workspace.
When you hit the save button in workspace the screen comes up with “Laserweb-Workspace” in the file name. The Save as types says “All Files (.).
If you change the name of the file there and do not know to add “.json” at the end it will not show up when you go to load. It not automatic.
You can also go out of LW and then into the file to see it and add .json to end of the file name. then it will be seen in LW. @Todd_Fleming sorry ‘vernacular’ just popped into me head at that time - grin.
Are you using an up2date LW4?.. Older versions used to have the behavior you describe, but I’ve not seen it for several versions now! As @Todd_Fleming said it now goes for JSON by default now!