Bit of a stretch, but several years ago I created a bundle for the Textmate editor that did syntax highlighting for Eagle¡¯s ULP language.
And I seem to have lost it.
Would any of you happen to have a copy, or someone else¡¯s?
Or a mode for Emacs?
Thanks,
John
|
[pcbgcode:master] New Issue Created by :
I'm trying to use PCB-Gcode in Fusion 360.
I have installed PCB-Gcode 3.6.2.4 it into the same directory as the rest of the ULPs.
The good news is that the "pcb-gcode-setup.ulp" works fine.
However, when I try to run the "pcb-gcode.ulp" program, I get the following error message:
**/Users/jim/Library/.../examples/ulps/examples/pcb-gcode.ulp(1387):
polygons loop is depreciated.? Use polyPours polyShapes polyCutouts instead.**
Is there a way to fix this?
[pcbgcode:master] New Issue Created by :
I'm trying to use PCB-Gcode in Fusion 360.
I have installed PCB-Gcode 3.6.2.4 it into the same directory as the rest of the ULPs.
The good news is that the "pcb-gcode-setup.ulp" works fine.
However, when I try to run the "pcb-gcode.ulp" program, I get the following error message:
/Users/jim/Library/.../examples/ulps/examples/pcb-gcode.ulp(1387):
polygons loop is depreciated.? Use polyPours polyShapes polyCutouts instead.
Is there a way to fix this?
[pcbgcode:master] New Issue Created by :
I'm trying to use PCB-Gcode in Fusion 360.
I have installed PCB-Gcode 3.6.2.4 it into the same directory as the rest of the ULPs.
The good news is that the "pcb-gcode-setup.ulp" works fine.
However, when I try to run the "pcb-gcode.ulp" program, I get the following error message in Fusion 360:
/Users/jim/Library/.../examples/ulps/examples/pcb-gcode.ulp(1387):
polygons loop is depreciated.? Use polyPours polyShapes polyCutouts instead.
Is there a way to fix this?
|
[pcbgcode:master] reported: corrections and addtions to pcb-gcode
#github
[pcbgcode:master] New Comment on Issue
By :
Congratulations on the educational accomplishment. Very much admire the tenacity!
Roger
|
[pcbgcode:master] new issue: When generating drill file, first drill OK. Remaing drills use "Spot Drill" depth?
#github
[pcbgcode:master] New Issue Created by :
Eagle Ver 9.6
PCB_GCODE ver 3.6.3
Repeatable: Yes.
Requesting drill only:
First hole is OK, subsequent holes use the "Spot Drill" depth. This is a snippet from drill file.
Workaround: Make the "Spot Drill" depth the same as "Drill Depth". And don't forget to return to correct value for "Spotting" while requesting Outlines.
Regards, M.
|
[pcbgcode:master] New Comment on Issue
By :
Thanks!
[pcbgcode:master] Issue closed by .
[pcbgcode:master] New Comment on Issue
By :
I'd like to vote for a "Spot Drill" First Hole / Remaining hole fix. It's always catching me out!
Regards, M.
Could you open an issue for that with a description?
I regret that I¡¯ve lost track of issues and contributions people have made.
|
[pcbgcode:master] New Comment on Issue
By :
I'd like to vote for the "Spot Drill" First Hole / Remaining hole fix. It's always catching me out!
Regards, M.
[pcbgcode:master] New Comment on Issue
By :
I finished my PhD,
Congrats! ??
Harry
[pcbgcode:master] New Comment on Issue
By :
I'd like to vote for a "Spot Drill" First Hole / Remaining hole fix. It's always catching me out!
Regards, M.
|
[pcbgcode:master] reported: corrections and addtions to pcb-gcode
#github
[pcbgcode:master] New Comment on Issue
By :
Thanks Harry and Alexander!
I¡¯ll have a look.
I finished my PhD, so hope to have more time for hobbies now.
¡ª
JJ
On Jul 25, 2022, at 3:52 AM, deHarro @.***> wrote:
?
Hi John,
seemingly you are on closing issues?
So perhaps you should have a short look at my homepage.
There I elaborate on the "always climb" option and a really easy addition to your code to change the cutting direction of ALL pathes to always cut against the feed direction to get clean edges on traces as well as on the copper patches left over.
My patch is always activated, no checkbox in the GUI to have it switched on or off.
Another addition explained there is the patch suggested by Alexander Arkusha to get "spot drill" and "drilling holes", respectively, working as expected.
Hope you see an advantage for your work.
Harry
¡ª
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
[pcbgcode:master] new issue: corrections and addtions to pcb-gcode
#github
[pcbgcode:master] New Issue Created by :
Hi John,
seemingly you are on closing issues?
So perhaps you should have a short look at .
There I elaborate on the "always climb" option and a really easy addition to your code to change the cutting direction of ALL pathes to always cut against the feed direction to get clean edges on traces as well as on the copper patches left over.
My patch is always activated, no checkbox in the GUI to have it switched on or off.
Another addition explained there is the patch suggested by Alexander Arkusha to get "spot drill" and "drilling holes", respectively, working as expected.
Hope you see an advantage for your work.
Harry
|
thanks much.
john ferguson
toggle quoted message
Show quoted text
On 7/24/22 12:30, John Johnson wrote: Hello Folks,
I just created a new release that fixes a couple of long-standing issues.
Issue #5 - images sometimes aren¡¯t found for pcb-gcode-setup, which can make the window taller than your screen.
Issue #6 - documents still had links to the old sites. Updated these to the current groups site, and also bumped the version number to 3.6.3.
Regards,
John
|
Hello Folks,
I just created a new release that fixes a couple of long-standing issues.
Issue #5 - images sometimes aren¡¯t found for pcb-gcode-setup, which can make the window taller than your screen.
Issue #6 - documents still had links to the old sites. Updated these to the current groups site, and also bumped the version number to 3.6.3.
|
[pcbgcode:master] reported: Does PCB-GCode Work with Latest Eagle Version on Mac?
#github
[pcbgcode:master] New Comment on Issue
By :
Yes, it does.
You'll want to get the .zip file from .
When you unzip it, be sure that the directory structure is preserved.
Then you'll need to add the location of the pcb-gcode folder in your directory options. See docs/pcbgcode.pdf for details. The pdf is on your machine, or you can find it .
|
[pcbgcode:master] new issue: Does PCB-GCode Work with Latest Eagle Version on Mac?
#github
[pcbgcode:master] New Issue Created by :
Wondering if PCB-Gcode works on Eagle 9.6 on Mac. It seems to throw an error when I try to run it:
**/Applications/EAGLE-9.6.2/examples/ulps/examples/pcb-gcode.ulp(10):
Unable to open the include file 'source/pcb-gcode.h'**
Thank you!
|
1 New Commit:
[pcbgcode:master] By Johnson, John T <john.johnson@...>:
: Fixed missing figure files. Ignored Texpad intermediate files, and TeX temp files.
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Removed:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
[pcbgcode] JohnAtl pushed new tag .
[pcbgcode] The branch "Release-3.6.2.4" was deleted by JohnAtl
[pcbgcode] JohnAtl pushed new tag .
[pcbgcode] created new tag Release-3.6.2.4.
[pcbgcode:master] Issue closed by .
[pcbgcode:master] New Comment on Issue
By :
Should be resolved now. Please test. Thanks!
|
1 New Commit:
[pcbgcode:master] By Johnson, John T <john.johnson@...>:
: Strange happenings. Fingers crossed that this is 3.6.2.4.
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Added:
Removed:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
Modified:
|
[pcbgcode:master] reported: Mismatch between ULP and settings files versions - won't run
#github
[pcbgcode:master] New Comment on Issue
By :
Thanks for reporting this!
I'll try to have a look soon.
|
[pcbgcode:master] new issue: Mismatch between ULP and settings files versions - won't run
#github
[pcbgcode:master] New Issue Created by :
The settings files (particularly pcb-machine.h) have been updated with new parameters, but the actual ULP hasn't. Looks like there was a new version of pcb-gcode made 4 months ago, but only half uploaded here.
Symptom: after a fresh install of this, when you launch pcb-gcode-setup from Eagle, it fails with "Unknown Identifier 'DEFAULT_WIDTH'.
Nosing around it seems that DEFAULT_WIDTH is no longer in use - in older versions of pcb-gcode it was defined in pcb-machine.h, but that file doesn't have it.
The dates on the files in this current distro are a red flag - all the subfolders are new but the files in the root are ... really old.
|
Re: Older files were on GitHub, anyone want to verify what I've uploaded?
#pcbgcode
#thanks
Hi John, I just see, that the code you uploaded to Github seems to actual be V3.6.0.1, as stated in the header portion of "pcb-gcode.ulp".  The version I have on my machine is of 2014 (plus my additions in Feb 2020). -- Harald _____________________
|
Re: Older files were on GitHub, anyone want to verify what I've uploaded?
#pcbgcode
#thanks
Hi John,
I compared the files on Github to the files I have on my computer, both denoted as V3.6.2.4.
I found, that "my" "pcb-gcode.ulp" is at least heavily commented, compared to the one in your Github.
Also I found functional additions from "mlmSolutions added 14 Feb 14" and from me, "Harald added 13 Feb 2020". This applies to some other files, too.
As of my additions, they are to implement "climb" and "not climb" in one run, that is, changing the milling direction for the first and all other following milling pathes. This results in "good edges" for the traces and the remaining patches, respectively.
I elaborated on those changes on my .
Additionally I have implemented the patch from Alexander Arkusha which fixes the problem with spot-drilling and actual drilling the holes for TH components.
Comparing all files in both repositories is beyond my time and skills, since there are hundreds of changes.
I can provide you with my version of V3.6.2.4, if you are interested in.
All in all, I cannot judge your Github files to work as expected or not, sorry for that. I just didn't test the Github version.
--
Harald
_____________________
|
Personally, I'm on some Discourse forums, and on some Discord channels, and they work well, but are a lot of work (well, I know they are non-zero) and I don't know how much return you'd see.? Now you've added content on github, how about we actually use the discussions and issues list on that? I was peripherally involved on a project whose listserv server had a cease and desist against it so went offline pretty quickly (someone can't read the unsubscribe part of the emails they signed up for - but the ISP had to enforce it unfortunately), and they then moved completely to github and it has been working really well. As an end user you can subscribe to the discussions and releases, so you see when there's a new version updates and when new discussions come up, so it stays very similar to this, but if anything email threading works a bit better than here (occasionally you'll see topics not get grouped properly).? If it was my vote alone, I'd be trying that as it's zero effort as it's already part of the github project, and then reassess.? It's not like this is a highly active, chatty group anyway...??
|
Re: Older files were on GitHub, anyone want to verify what I've uploaded?
#pcbgcode
#thanks
I find that I'm doing 2 and 4 layer boards with 100+ pin
processors.?
I'm not sure how pcb_gcode would help in this situation, although
if I wanted to, I could at least make extender boards, dual sided,
etc.
It would take a bit of effort to replace the controller in a PCB
etcher (which had a license locked etcher controller).
I could do that, then run the whole thing off a 3D printer board
with external drivers (2.5 amp @ 30 volt or so).
I can do it, just haven't found the reason why, and that's
because I don't need extender boards all that much.
Still, for simpler boards (and I do 2 and 4 layer boards now with
embedded TQ-100 (at least) processors), the program can't deliver
what I need.
It's a very? nice piece of work, though, for somewhat simpler
designs.
Harvey
On 3/4/2022 7:46 PM, John Johnson
wrote:
toggle quoted message
Show quoted text
Hi Art,
Thanks for checking that out!
Happy Birthday!
That's quite a milestone. Must be all those years of living right,
plus a liberal application of cutting fluid now and then :-)
Rest assured, if I move the group, you'll be coming along as
admin. So far, no response other than yours. If I move the group,
it probably won't be for a while, as I'm short on time.
Good to hear from you!
Keep making chips.
--
JJ
Art Eckstein wrote:
OK, downloaded the zip file and loaded the dir into eagle 6.1
that I
use and seems to work just fine.? Did some poking around and all
seemed fine.
Country
At 3/2/2022 02:01 PM, John Johnson wrote:
I just uploaded what should be version 3.6.2.4 to GitHub, and
would
appreciate anyone who can verify that it works. I had some
older
files on there, 3.6.0.x.
I don't currently have anything set up to check it with,
sadly, not
even Eagle.
Thanks, JJ
|
John Johnson