On Tuesday 07 July 2015 09:13:19 Todd Zuercher wrote: > ----- Original Message ----- > From: "Gene Heskett" <[email protected]> > To: [email protected] > Sent: Tuesday, July 7, 2015 5:55:27 AM > Subject: Re: [Emc-users] encoder opto update > > One of the things that makes it difficult is that because I have never > been able to make cool radii compensation work so that the backplot > shows a line where the actual cutting edge of the tool travels, I have > been forced to make my code do its own compensation. This works, but > the backplot is wrong, showing a very skinny slot because it traces > the center of the tool and not the cutting edges path. > > Any time I have tried to do the cutter comp stuff, I get a message > that there is not enough room between the moves to do it, even if the > tool is a .0312" dia tool, and the entry move in air is better than a > damned inch! > > This example works for me. It cuts the inside of a 1" square with > 0.25 diameter tool. > > g20g40 > g0x1.2y1.25z0.25 > g41.1 d0.25 > g1x1.4y1.0z0f50 > x2y1 > x2y2 > x1y2 > x1y1 > x1.6y1 > g40x1.8y1.25z0.25 > > But the backplot in Axis still only shows the center of the toolpath > (a .75" square), not the coordinates programed in the g-code (the > outside of the 1" square).
And that is the problem in a nutshell. This could be solved in two ways. 1. By feeding the backplot engine with the gcode, but adding tool rad and cut (dig,climb) so it draws the cutting edges path. All cuts in this code are climb cuts that I wrote, or re-wrote that way but its originally Mr. Gleisters code, extensively edited. 2. Having the backplot leave a trail that _is_ the tool diameters width as obtained from the tool table. This could be done by taking out the xor operation that clears the trailing edge of the tool drawn as it travels, leaving only the single pixel. Either way, it s/b switchable to restore the current method for those "used to it". Method 2 would truly give us a WYSIWYG backplot, much more usable in the long run IMO. I realize that the backplot depth/retention would suffer, as I have noted many times where I am making multiple passes, that it eventually runs out of red memory and clears it back to white, then redraws the red on the next pass. How hard a problem to solve I haven't a clue. Its also not a problem for me. Feature request for 2.8.0 final? Change subject: I replaced the old tube monitor with a new LED/LCD model a year ago, and the mode x runs it in gives me squat circles because its running in some wide screen mode but assumeing a 4/3, when its 16 by 9 now. Anybody know a fix? Thanks all. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
