Parsing Fault

108 views
Skip to first unread message

vec...@slingshot.co.nz

unread,
Feb 18, 2014, 12:47:13 AM2/18/14
to fla...@googlegroups.com
Have downloaded Win version and attempted to open a Gerber.   FlatCam gets to 1/4 while saying "parsing" in progress box but nothing more happens.   FlatCam still seems to be live and has not hung.   Gerber file is produced by PADs Power PCB as RS274-X with no macros or fill and can be read and viewed by another program such as LineGrinder.   Contact by email and I can send Gerber or any other info you might need.   FlatCam looks great and I can't wait to use it.   Cheers, Chris

--

jpcaram

unread,
Feb 18, 2014, 10:59:25 PM2/18/14
to fla...@googlegroups.com
Hi Chris,

I looked into the problem and found that some statements in the gerber file use a deprecated format. See page 41, 2nd paragraph in http://www.ucamco.com/Portals/0/Public/The_Gerber_File_Format_Specification.pdf and your file contains lines like X19490Y6100* which should have an operation code like D01/2 at the end. Could you tell me if your version of PADS is very old? PADS is a major player in PCB design so if they are doing it I will support it, but I just want to make sure that your version is not too old and they are now complying to the specification.

Thanks,

JP

jpcaram

unread,
Feb 19, 2014, 12:34:23 AM2/19/14
to fla...@googlegroups.com
I just added support for the Gerber that was causing the problem, specifically:
  • Coordinates without operation code like X1234Y5678, which should be something like X1234Y5678D01. I'm now using the operation code from the previous coordinates if missing.
  • Apertures where using 3 digits with leading zero, like %ADD011C,0.012*%, 011 there, but referencing later on without the zero, this is, just 11. I'm not sure this is non-compliant but it's definitely unnecessary.
To apply the patch, download the latest camlib.py from https://bitbucket.org/jpcgt/flatcam/src and copy it to the directory where the .exe is (if using the windows installer version) or where the flatcam.py is (if using the source).

I'm not making a release for this small patch because there is still a lot to fix.

vec...@slingshot.co.nz

unread,
Feb 20, 2014, 1:05:26 AM2/20/14
to fla...@googlegroups.com
Thanks for that.   I followed your instructions but it comes up with an error.   See attached file.   I am using the Win version and FlatCam has installed to C:Program files\FlatCam. - Chris
CamLib.py error.JPG

jpcaram

unread,
Feb 20, 2014, 8:01:28 AM2/20/14
to fla...@googlegroups.com
It looks like you downloaded the web page instead of the actual .py file. Don't do "Save As", but follow the link and then choose "Raw" to get the actual .py. Any way this is the direct link to the specific version of camlib.py (will not point to the latest if there is a newer one in the future):

vec...@slingshot.co.nz

unread,
Feb 21, 2014, 1:59:36 AM2/21/14
to fla...@googlegroups.com
Thanks, yes it is working now.   I have attempted to play with the job I sent you and after the first few steps it slows right down and takes many minutes to complete the CNC plot.   Thereafter whenever I go to the FlatCam window the CPU usage goes to 50%.   Any suggestions.

I find the setting of the CNC tool width confusing.   Why is it different from the isolation width ?   The CNC tool width seems to revert to 0.4mm after I have set it to 0.2.. and then of course the plot lines are too big.
Chris

jpcaram

unread,
Feb 21, 2014, 3:00:16 PM2/21/14
to fla...@googlegroups.com
Hi Chris,

I'm aware of the slow plotting of CNC jobs. I was creating geometry in a very inefficient way and including too much detail. I'm working on this right now and the fix will definitely be part of the next release. In the meantime I suggest that you keep downloading the latest camlib.py. I did some work that speeds that up, but reduces the resolution of the G-code. See if it fits your needs.

with regards to the tool diameter, when creating the job it determines the offset from the geometry. whithjn the CNC job it only affects how thick the line in the plot looks. It's a feature, not a bug butt need to clarify this a little better in the GUI.

I appreciate your feedback, and thanks for your patience!

JP

vec...@slingshot.co.nz

unread,
Feb 21, 2014, 11:21:49 PM2/21/14
to fla...@googlegroups.com
Downloaded camlib.py but can't detect any difference.   It is fast to isolate but takes several minutes to CNC.   It can't be calculation that uses up so much CPU time - it is not that big a job.   After it has completed CNC then it is very sluggish and gobbles up 50% of CPU time even when just the FlatCam window is selected.

Tool size in CNC does not stay where I set it - I set it to 0.2 and when CNC is finished (after several minutes) it is 0.4064 and the plot shows that it is clearly more than the 0.2 I set

Changing isolation routing dia in "Project Options" does not ripple through to the isolation setting in a selected Geometry Object window.

I saved a project but when I opened it the next day FlaCam crashed.   It is a big file - 4.8Mb

Cheers, Chris


jpcaram

unread,
Feb 22, 2014, 1:03:35 AM2/22/14
to fla...@googlegroups.com
Ok, the slow CNC plotting problem should be completely solved in the latest camlib.py.

I'm adding the tool size problem to the list open bugs. As for the saving/opening, I've seen the problem myself but I don't know what it's about yet.
Reply all
Reply to author
Forward
0 new messages