denvi / flatcam Goto Github PK

I found this discussion about how to make FlatCAM not route the outside edge of the board. This works, as long as the outside edge toolpaths fully enclose the board:

https://muut.com/i/flatcam/usage:how-do-i-not-route-the-outs

But suppose some footprints extend to the board edge, such as these SMA connectors:

If I delete the enclosing toolpaths, I end up losing isolation routing toolpaths in the board interior. I have not been able to find a way around this, thus far, and am curious if there might be a solution that's just not obvious to me somehow.

Thanks!

How to reproduce:

1. I select and double click my .gbr file from the project tab
2. I click "NCC Tool"
3. There are two tools in the "Tools Table"
4. I set their diameters to the same size
5. Program crashes
   

Is there any way to use two tools? one for the biggest tracks and one for the details? that would make the manufacturing process faster. this feature is included by bantamtools

The program detects the areas that were not covered by the tool with a larger diameter and those areas are assigned the tool with a smaller diameter

Hi guys, I've been using flatcam for about a year to design pcbs and acrylic and wood cuts, during all this time I used version 8.993, it showed difficulties when changing the file names, these were not changed when modifying it, so I I opted for a version later than 8.994, unfortunately it doesn't work as it should and has many problems when importing files from DXF and SVG to Gerber format

I would like to know if anyone has the link for the installer for windows of version 8.993 since it is not officially available in the links, there is only the “source code” version that even having installed the dependencies in python the executable freezes , I would appreciate your help to go back to the previous version where most of the things I use work

Hi,

at first thank you for this awsome piece of Software.
I want to report an issue, on the 8.994 BETA Version with the Z-Axis.
The Problem is i use a V-Shaped Tool with a 30 degree angle and 0.1mm V-Dia.
In the Tool Libary i configured a cutting depth of 0.1mm and the Software calculates a Tool Dia of 0.1536mm.
So far so good, but when i generate the G-Code with this V-Tool the Cutting depth in the G-Code is only set to zero (no cutting).
I hope i´ve configured it the right way, it took me quiet a long time to figure out, that the G-Code was the issue not my Z-leveling.

I made a mistake.

FlatCAM 8.994
g-code import is not so robust.
6 circles expected to be shown. only 3 of them accepted as correct.

G21 G90 G17
G0 X0 Y10 Z0
G2 X0 Y10 I0 J-10	(ok)
G2 X0     I0 J-10	(ok)
G2 Y10    I0 J-10	(ok)
G2        I0 J-10	(not ok)
G2 X0 Y10    J-10	(not ok)
G2           J-10	(not ok)

Hello I am new to python and do not understand how to launch this version but I love flatcam and need Clear non-copper funcion could you explain how to install this software ?

I'm finding it difficult to understand how to use the re-cut option. According to the current description it will "generate an extended cut over the first cut section". What exactly is the value specifying? Is it some kind of threshold for what flatcam considers a meeting of lines? Does it specify an overlay width that will be cut away? I have experimented with a few different values, but it looks like the same paths are being generated (just from looking at the plot area, I have not run the gcode on my CNC yet). I have noticed that this option produces very different results than the Passes isolation routing option, which seems to avoids intersections. Is Re-cut a bit like the opposite behavior?

All distro's and even pip have dropped all Qt4 based packages. This application is un-runnable on any modern Linux system. Please update the version of Qt being used. I'm forced to use the windows executable with Wine.

Hi

I tried to build FlatCam on my Gentoo Linux but I had to find out Gentoo Linux does officially not support Qt4 (and pyqt4) anymore in their package manager. So QT4 is a must dependency to build FlatCam?

Good day. When importing drill files into mm, the data is not transferred correctly. The problem exists in all versions. Please correct.

There an issue at https://bitbucket.org/jpcgt/flatcam discussing offsetting all the files. In may case the gerbers and excellon files from KiCAD are referenced to the PCB editor 0,0. This is always off the PCB and is ni use for setting up the CNC miller/router I want the ref point to be a corner of the PCB blankm so I need to fix the offset in all the files. Here's a patch of my install that "works for me".

I didn't use BitBucket issues as they want to "make it easier for me" by insisting I use, and set up, an Atlassian login. It's not easier it's a PITA.

Anyway here's the diff:

diff --git tclCommands/TclCommandOffset.py tclCommands/TclCommandOffset.py
index 17ffdaa..4cd9576 100644
--- tclCommands/TclCommandOffset.py
+++ tclCommands/TclCommandOffset.py
@@ -48,6 +48,12 @@ class TclCommandOffset(TclCommand.TclCommand):
         """
 
         name = args['name']
-        x, y = args['x'], args['y']
-
-        self.app.collection.get_by_name(name).offset(x, y)
+        x, y = float(args['x']), float(args['y'])
+       if name == 'all':
+               names = self.app.collection.get_names()
+               for name in names:
+                       object = self.app.collection.get_by_name(name)
+                       if object.kind == 'gerber' or object.kind == "excellon":
+                               object.offset((x, y))   
+       else:
+               self.app.collection.get_by_name(name).offset((x, y))

I'm not sure that name == 'all' is the right trigger but, like I say, it works for me. Oh, this also fixes a bug where the shell command "offset" doesn't work at all.

I had problems trying to open an Excellon file generated in KiCad v8.0.1, FlatCAM (beta_8.994_x64) complains that "it is probably not an Excellon file".
Various iterations of the KiCad Excellon settings under the Plot > Drill Files options were tried without success (i.e. mm/inch, relative/absolute etc.).

On closer inspection of the KiCad generated .drl file, it was noted that there seemed to be two extra tools defined (whereas the PCB only has holes of all the same size - 0.8mm).

Example from the file, T1 and T2 are not in the KiCad PCB.
; #@! TA.AperFunction,Plated,PTH,ComponentDrill T1C0.000 ; #@! TA.AperFunction,Plated,PTH,ComponentDrill T2C0.001 ; #@! TA.AperFunction,Plated,PTH,ViaDrill T3C0.800 ; #@! TA.AperFunction,Plated,PTH,ComponentDrill T4C0.800

Deletion of T1 and T2 resulted in the file being opened in FlatCAM with no further issues. I suspect the zero diameter tool is the problem.

For clarity I also merged T3 and T4 into one tool.