Date   
Eagle 8.6.3. on Windows 10 permission denied #gcode #eagle

Jos Raven
 

I cannot solve this problem on my Windows 10 installed EAGLE 8.6.3.

Can't open C:\EAGLE 8.6.3\ulp\viewer\application.windows\data\optimize_me.txt
Permission denied

I have absolutely no idea how to set the permission for Win 10.

Help please!

Re: Eagle 8.6.3. on Windows 10 permission denied #gcode #eagle

John Swenson
 

Hi Jos,
this has nothing to do with Windows 10, the viewer pops up when generating a G-code file and is looking at the mentioned file. IF your run generates another G-code file, it tries to pop up a new instance of the viewer to display THAT G-code, since the file is already being used by another instance the OS won't let the new viewer open it.

The solution is to manually kill the first viewer (click the X in the upper right) before starting the generation of the second G-code file.

This whole scenario happens when you have something else enabled other than an "etch", such as milling, or text, or drilling, each of these gets its own G-code file.

I think this will fix your problem.

John S.

On 5/19/2019 5:18 AM, Jos Raven wrote:
I cannot solve this problem on my Windows 10 installed EAGLE 8.6.3.
Can't open C:\EAGLE 8.6.3\ulp\viewer\application.windows\data\optimize_me.txt
Permission denied
I have absolutely no idea how to set the permission for Win 10.
Help please!

Re: Eagle 8.6.3. on Windows 10 permission denied #gcode #eagle

Jos Raven
 

Yes, John,
you are right !!
Following your  instruction it works .
On my Win 10 PC I user PCB-GCODE ver. 3.6.2.4

However , on my other PC I have EAGLE 7.2.0 and PCB_GCODE ver. 3.6.0.2 
The problem does not occur with this set-up.
I have, in my configuration, 6 viewer windows open with no problem.
However the windows are reduced to icons on the taskbar.

Thank you for your help,
Regards,
Jos

Re: Eagle 8.6.3. on Windows 10 permission denied #gcode #eagle

Jos Raven
 

Edit;

My other PC runs on Windows 7 .

Jos

changing "allway climb" and "normal" in midst of the job #pcbgcode #development

harry0099@...
 

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?

Explanation:
I think I observed, that pcb-gcode does one first round in which it surrounds all traces once, so when stopping after this first round, one would have a functioning board with all traces as expected, but with too narrow trenches.
The following rounds only widen the already defined trenches to ease soldering.
All following rounds erode the "other side" of the trenches but this happens in "climb mode", resulting in not so good edges.
So I consider it as good practise to change the moving direction of those following rounds to make them again "normal".


Thanks in advance!

Harry

Re: changing "allway climb" and "normal" in midst of the job #pcbgcode #development

John Johnson
 

Unfortunately, this is due to the way Eagle creates polygons.
Your best bet is to find some gcode editor that will allow you to reverse the line directions in the files that pcb-gcode creates.

Regards,
JJ

On 30 Jun 2019, at 12:47, harry0099@... wrote:

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?

Explanation:
I think I observed, that pcb-gcode does one first round in which it surrounds all traces once, so when stopping after this first round, one would have a functioning board with all traces as expected, but with too narrow trenches.
The following rounds only widen the already defined trenches to ease soldering.
All following rounds erode the "other side" of the trenches but this happens in "climb mode", resulting in not so good edges.
So I consider it as good practise to change the moving direction of those following rounds to make them again "normal".

Thanks in advance!

Harry

Re: changing "allway climb" and "normal" in midst of the job #pcbgcode #development

Ken McNabb
 

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: pcbgcode@groups.io <pcbgcode@groups.io> On Behalf Of John Johnson via Groups.Io
Sent: Monday, 1 July 2019 11:46 AM
To: pcbgcode@groups.io
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.
Your best bet is to find some gcode editor that will allow you to reverse the line directions in the files that pcb-gcode creates.

Regards,
JJ

On 30 Jun 2019, at 12:47, harry0099@... wrote:

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?

Explanation:
I think I observed, that pcb-gcode does one first round in which it surrounds all traces once, so when stopping after this first round, one would have a functioning board with all traces as expected, but with too narrow trenches.
The following rounds only widen the already defined trenches to ease soldering.
All following rounds erode the "other side" of the trenches but this happens in "climb mode", resulting in not so good edges.
So I consider it as good practise to change the moving direction of those following rounds to make them again "normal".

Thanks in advance!

Harry

Re: changing "allway climb" and "normal" in midst of the job #pcbgcode #development

harry0099@...
 

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

Re: changing "allway climb" and "normal" in midst of the job #pcbgcode #development

harry0099@...
 

Hi Ken,
interesting idea :-)
Sadly my mill doesn't support ccw rotation of the spindle.
Thanks anyway for the hint.

Harry

Conversion to Garber #eagle

yoram
 

Need help please
I am trying to convert the file to Gerber files
but without success
Can anyone convert them for me?
Many thanks

Yoram

Re: Conversion to Garber #eagle

keith3125
 

If you're using a newer version of Eagle, it's super simple.
With the file open that you want to generate, go to upper 5th to the left , CAM processor button. Click that. It opens the CAM processor window. By default loaded is the 'template_2_layer.cam.
If you're using a service that needs the file zipped, looked for 'zip file' at top middle. If you want 'imperial units, to the right of 'zip files', is a way to change to imperial.
At the bottom, right, click 'process job'. It'll ask you where to save these files. Do that and bingo, you're good.

On Friday, July 5, 2019, 08:16:35 AM EDT, yoram <y_shalom@...> wrote:


Need help please
I am trying to convert the file to Gerber files
but without success
Can anyone convert them for me?
Many thanks

Yoram

Attachments:

Re: Conversion to Garber #eagle

PETER HARRISON
 

Presumably this is an Autodesk "Eagle" board file (.brd).  If you prepared it from Eagle 9.4.x there is an icon "Generate CAM data" which does the Gerber file generation in a form acceptable directly by PCB manufacturers. 

The file " 0 " which downloaded from your link is not in the correct format to be read by "Eagle" so I cant really help - sorry.

Peter H

Re: Conversion to Garber #eagle

peterg1000
 

Attempting to load into Eagle 9.4.2 reports your downloaded ".brd" file as not being an Eagle file!!??

If you prepared it with an earlier version and can import into "9.4.x", the is an toolbar icon which will automatically generate all the Gerber files required by any pcb manufacturer.  One manufacturer (in China) I have used personally accepted the automatically produced .zip file and made excellent boards from it.

Sorry can't be more helpful.

Peter

Re: Conversion to Garber #eagle

yoram
 

Wow
Thanks for the help and support
I downloaded the file from a site - not I created it   ( https://github.com/0xPIT/reflowOvenController  )
I found another file in the library that only with him, I can open the BRD 
Maybe it can help someone help me ...
Many thanks to everyone who made the effort to help

Yoram

Re: Conversion to Garber #eagle

Rollfree
 

Here you have SCH and BRD.

Dne 6.7.2019 v 21:22 yoram napsal(a):

Wow
Thanks for the help and support
I downloaded the file from a site - not I created it   ( https://github.com/0xPIT/reflowOvenController )
I found another file in the library that only with him, I can open the BRD
Maybe it can help someone help me ...
Many thanks to everyone who made the effort to help

Yoram

Re: Conversion to Garber #eagle

peterg1000
 

Downloaded "O" file and renamed as "O.zip". Imported into Eagle 9.4.2 and prepared CAM file as ".zip" file.  This checks out with Gerber viewer on all layers and should be good to go for manufacture.

All the files attached for your information.

Peter

Re: Conversion to Garber #eagle

peterg1000
 

F.Y.I download Gerberlogicx from their website to view Gerber files directly from dated .zip file (attached to previous reply).

Peter

Re: Conversion to Garber #eagle

Patrick
 

I would recommend to watch my video first before you order the PCB 😋

Re: Conversion to Garber #eagle

yoram
 

Well
Thank you all for your help
Special thanks to Patrick
 
After this video I realized that the project was not really ready for production
And accordingly. Not going to build it
It's a shame that I have already ordered all the components :(
 
If someone knows a similar project that can be built, I would thank him

best regards
Yoram

Re: shorting traces - How I messed up & a question about spot-drill-holes #eagle #etch

JimmyB
 

Hi Peter, my name is Jim, and I reading your post about spot drill holes. The word in your article "pcgcode"
should read  pcbgcode ? Sorry about if i'm wrong, but my etching gcode file not placeing spot drill holes.
Try to find answares  all ove the net to my problem, no luck. It also doesn't generate drill and mill files. It shows
this error "Improperly formatted rack entry" .  I had to reinstall windows10 ever since this problem showed up.
Before had no problem at all useing Eagle 7.0.6 and Pcb-gcode 3.6.2.4 try to use different drillrack files, but reading your
posting this shouldn't be my problem. Sorry to bother you all of this, but I'm trying to find solution for this problem.
Any help or idea would be appreciated.
Best regards.