Keyboard Shortcuts
Likes
Search
changing "allway climb" and "normal" in midst of the job
#pcbgcode
#development
Hello comrades! I use pcb-gcode.ulp for some time now and get decent results, probing the copper surface with OpenCNCPilot. But I realized, that the edges of the second+ rounds are not as good as the first one. That is easily explained, since the milling bit is rotating cw and the bit moves in the correct direction for the first run, but in the wrong direction ("climbing") for all sucessive rounds. Now pcb-gcode.ulp has the option to select ?always climb¡° to change the direction of the bit on its way, but this option changes the behavior for all rounds. I wanted to implement another option which allows for turning on the ?always climb¡° selection only for the second and all following rounds, but I can¡¯t fiddle out where in the code I may attack. So my question to all of you: Can anyone give me a hint, where in the code I can start to look, or even better, where the decision between the first and all successive rounds is made?
Harry |
¿ªÔÆÌåÓýUnfortunately, this is due to the way Eagle creates polygons. Regards, On 30 Jun 2019, at 12:47, harry0099@... wrote:
|
¿ªÔÆÌåÓýIf you are use V bit cutters a far easier way might be to reverse the direction of your cutter after the first round. ? Regards Ken ? From: [email protected] <[email protected]>
On Behalf Of John Johnson via Groups.Io
Sent: Monday, 1 July 2019 11:46 AM To: [email protected] Subject: Re: [pcbgcode] changing "allway climb" and "normal" in midst of the job #pcbgcode #development ? Unfortunately, this is due to the way Eagle creates polygons. Regards, On 30 Jun 2019, at 12:47, harry0099@... wrote:
|
Hi John,
ok, then I got something wrong. I thought, your code crawls along the polygons of EAGLE and set up some sort of array or list with coordinates or verctors which then is iterated in this or that direction (having in mind that one can alter the direction via "Climb always"). Since the mentioned "bad edges" are only a visual concern, I can surely live with that, it's definitely no killer for me. Thanks anyway! Harry |
Hello John,
I'm back again on this topic since I back then had the feeling you misunderstood my idea. But I couln'd express it better and so retreated. The topic itself doesn't let me retire of course and I now made an approach on my own. I inserted on line of code (and several lines of comment, of course ;-) Starting at line 1288 of "pcb-gcode.ulp", directly after // set direction of cut around contourI inserted the following code ////////// Harald added 13 Feb 2020?? ??? ??? ??? ??? ??? ?And guess what. Yes, the code performs as described above in the commment and as I wanted it to. I think this is a valuable addition to your wonderfully craftet ULP, but please check that I didn't blast something I overlooked. Please comment on this addition. Thanks! Harald |