Is it possible to add to the start-from-line feature so that when you key in your starting line (and click preview or ? ) it can be shown in the visualizer where it is? Sometimes, when doing pocket or profile cuts I like to run the cut again but only in certain areas. It is a lot of guessing on big jobs when I can’t rerun the whole file
@Swinly Lonnie: While you wait for this feature in gSender, you can open the gcode file in ncviewer and you can see a visualization of the file, with the line numbers beside it. It may be worth a try.
Find it a ncviewer.com
Anything is possible - but in this case it would come with a bit of overhead.
Start from line works by virtualizing the file up to the requested start line so we know modals + position. Which means if we wanted to do that, we’d need to virtualize the file any time you changed the line/previewed. Which is fine but also takes time - especially given that it might be a very large file and someone wants to start very deep into it.
I think any changes we’d make in this behaviour would be closer to what Grant mentioned - being able to mouseover the line and get a line number. It’s ultimately not super high priority at the moment.
I’ve seen ncviewer mentioned before but had no idea what it was. Will be trying it out next time this situation arises.
If I break a bit or loose power and my machine stops, restart capability is great. The issue, I have though, is many times the restart line is not correct or for whatever reason the system suggestion is off. My suggested enhancement is since the system can show all the tool paths graphically, could you create a pointer to select a restarting point using the graphic or marking the restart point on the graphic prior to accepting it as a check point prior to accepting the start point? This would allow the user to see if it is set to start at a safe point? I have broken bits that started at a wrong line number and thus at an unsafe starting point as it bit into too much material and was further along then it should have been.
Please let me know if this doesn’t make sense and I will try to elaborate more.
Dan.
Actually this is a great suggestion. I personally would love to have this capability. I cant tell you how many times I had to remove my bit, then start from a line that I guesstimated, just to find out an approximate line to start from. This would save so much time.
@DanM That’s a good idea. You can use a viewer like ncviewer.com to do something similar (you select a line number and see where it is located as opposed to select a location and see the line number). Would be great to have it integrated in gSender.
@DanM I combined your suggestion with a previous one that was asking for the same
also I just wanted to reply to let you know that as of newer Edge versions the line reporting is now much much more accurate (we had to refactor how we did some of the line counting) so if you haven’t tried it yet give it a shot and let us know what you think. Either way I’ll keep the visualizer suggestion up since I think it would be interesting to look into ![]()