It would be nice if I could make small changes to a tool file in gSender.
Example: When cutting a Dado, if the Dado is found to be too narrow, it would be nice to make the required change and re-run the tool.
Does gSender have this function that Iām unaware of?!?
@JohnnyL I have moved your question to the gSender Question category.
I assume that you want to be able to edit gcode in gSender, correct? If so, Chris announced in February that the current Edge version has a built-in gcode editor, invited people to try it out and send comments.
Thanks for moving my thread to the correct location.
I guess I need to look into gSender Edge to see if that would work for me.
This may be too āin the weedsā for me, but Iām up for any new challenge to broaden my CNC knowledge.
@JohnnyL I made an assumption that may not be valid, John. Thatās why I asked. I assumed that you could read, understand and edit gcode. Edge will allow you to edit the gcode. You still need to know which lines to edit and the new values that you want in them, of course.
If you are looking to gSender to be able to edit the toolpaths that you created in your CAD/CAM program, IMHO I canāt see that ever happening.
Yes @JohnnyL Iād agree with Grant here that outside of tool radius compensation (something which is firmware-side but is always something on our mind to look into in the future) having the ability to adjust the fit on dados after the g-code has already been generated is usually not the role of a g-code sender. How Iād see it is you have these types of typical options:
Grantās suggestion of using the editor is also technically possible, but depending on your file and how knowledgeable you are with g-code this can take a while and requires several line-by-line changes. Technically it would be viable to have an editor that could bulk modify g-code lines for you, but Iām not aware of any tools that can currently do that.
Point 4 addition: Go back in cam and temp edit the existing tool into a wee smaller diameter. Regenerate toolpath and run it without toolchange. This is how I quickly take care of small shavings and adjustments when fits are tight. No new xyz zeroing needed either.
If my old gsender would have a favorite song, it would be this:
@Spamming_Eddie Thatās a really good idea. I usually create several toolpaths for the same cut, but I increase the offset allowance ever so slightly for each toolpath. If the first one is too tight, I run the second one. And the third, etc, etc .
Sometimes, Iāll have three toolpaths already created and on my gSender computer. If I need the 2nd and 3rd toolpaths with the allowance, theyāre already there.
A gSender solution would be the ability to tweek the tool diameter or an allowance directly in gSender and it would compensate for that using the initial gcode .
@Chucky_ott In the post processor that I use, there is no value for the tool diameter, so there is not a value for gSender to tweak. I believe that you are using the same PP as me, grbl mm, correct?
From all the comments, at least at present, the solution to @JohnnyL issue is clearly to return to the CAD/CAM application and make the required adjustments to the toolpaths, then write out new gcode. As you and @Spamming_Eddie have pointed out, there are a few ways to do that efficiently.
@gwilki my comment was meant as a feature request for gSender.
@Chucky_ott Understood. In my ignorance, I simply donāt see how a code reader could be tweaked to amend all the movement values in the gcode based on the the size and/or specs of the tool being used. 
@gwilki some senders (ncSender, ioSender) have a height map feature which corrects the original gcode for any surface deviations. I assume the same could be done to correct for bit diameter.
@Chucky_ott Interesting. Iām not saying that you are not right. Iām pleading ignorance. I thought that the height map features in some code senders required the user to manually probe at a fixed interval in X and Y. Then, using those multiple Z values, the code sender can create a height map. In that scenario, the code sender does not need to āknowā the bit length or its diameter. It is only concerned with the changing Z heights.
To me, again in my ignorancce, I believe that the ātweakingā question posed by the OP is a considerably different exercise.
Anyway, Iāll bow out before taking this discussion any further off the subject. Clearly, I have nothing to add to what has been said already.
@gwilki In retrospect, correcting for Z is way easier than correcting for XY. For an XY correction, youād need to know if you correct inward or outward of the cut. Likely CAM software is the best place to do that.
Iāll be bowing out too 
While it doesnāt directly apply to this discussion, I LOVE having a parametric CAD setup (Fusion in my case). I simply include a variable for āclearanceā where required and if the fit isnāt quite right I tweak that variable, run it through the CAM system and āprestoā.
Tweaking the tool diameter will apply to the entire model which one may or may not want to do.
@JohnnyL I should have asked what CAD/CAM application you are using. @Jens posted a solution to your ātight fitā issue if you are using Fusion. If you are using VCarve, you can simply open the dado toolpath, add in a negative offset, recalculate and create a new gcode. This is similar, I believe, to that @Chucky_ott is suggesting.
Several decent ideas here.
The main point of my request that I could edit a CNC bit in gSender, is to eliminate the back-and-forth process of removing the flash drive, go to the other computer to edit the file, take it back to the gControl computer, re-run project. Rinse/Repeat until fit is perfect.
Yes! I could;
Yes, I measured the stock before programming, but small adjustments are necessary to make slip fits. Hence, the request to make those small adjustments in gSender.
The larger CNCs where I work have this ability. Itās in the tool geometry tables.
I am using Vectric Aspire 12.5 as my CAD/CAM application.
I see your valid point, that the post processor doesnāt have the tool diameter in it, hence gSender canāt adjust it. I guess thatās where it would be nice if gSender can adjust the tool path.
I will consider checking into the G-Code. But for now, Iāll just cut a test piece until I get the fit Iām looking for, then save that dimension for future use of similar materials. The project in question is using Baltic Birch ply.
I think it would be close to impossible for gSender to alter the G-code in a reliable way. Take a simple circle that cuts all the way through the material and you want to adjust the G-code 0.3mm. gSender doesnāt know if your making a hole or a profile cut. Which way should it adjust the code. If your post processor uses short lines instead of an arc it doesnāt even know it has a circle. And itās just going to exponentially harder for more complicated things.
If they could get gSender to figure it out it might take longer than going back to the design PC. Thatās my take on it anyway.
If iām doing small adjustments on my design computer I run a remote clone of gsender on it (I always run a clone on my design pc) and load the adjusted toolpath directly from design pc to machine. I even start it from the design computer, for itās a toolpathe with the same xyz that bulked out the material already. Not much danger of it going wrong.
No commute needed between design and machine. Quick ān easy.
You can do this if your dato is perfectly aligned along the X or Y axis. Just go to 0, move your X or Y a tiny bit, reset 0 and run the job again. That will widen the dato by the amount you moved.
I do this all the time with Z when I donāt quite cut through or a magnet hole isnāt quite deep enough.