search

buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing
0 stars 0 forks source link

Gerber exported files missing the .gm1 (outline) data #2786

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
To recreate the bug:
1. Create a new project
2. Add something to it (any random component will do)
3. Export the PCB to Gerber format
4. View the .gm1 file in gerbv - it has no contour.

Attached a sample file created with above steps and the .gm1 contour file as 
created by Fritzing.

Expected output would be the board outlines. What we get is NO outlines.

Two amd64 versions of Fritzing have the same bug on Ubuntu 13.10 (amd64).
* 0.8.0 (b08d5 2013-06-12) [Qt 4.8.4]
* 0.8.3 (b048f 2013-07-27) [Qt 4.8.3]

changing PCB type from Rectangle to anything else and back has no effect. 
Deleting the PCB element and creating a new one has no effect.

Original issue reported on code.google.com by flud...@gmail.com on 23 Nov 2013 at 4:35

Attachments:

GoogleCodeExporter commented 9 years ago 
The attached .gm1 file is indeed empty. However, just tested this using 
Fritzing 0.8.3 under Ubuntu 12.10 (and Windows 7 for that matter), and the 
contour file is correctly generated. I guess I will try 13.10...

Original comment by irasc...@gmail.com on 23 Nov 2013 at 7:39

GoogleCodeExporter commented 9 years ago 
I can confirm I am able to generate correct GM1 files in a Windows XP VM using 
the latest fritzing. Problem seems to affect Ubuntu 13.10 only...

Original comment by flud...@gmail.com on 23 Nov 2013 at 11:58

GoogleCodeExporter commented 9 years ago 
I've tested it again, this time on a i386 install of Ubuntu 13.10, the file is 
generated correctly!

So far, the only affected system I can find is the Ubuntu 13.10 AMD64. That 
quite narrows it down.

Original comment by flud...@gmail.com on 25 Nov 2013 at 5:42

GoogleCodeExporter commented 9 years ago 
Just created an Ubuntu 13.10 AMD-64 virtual machine. No updates so far, just 
the original installation, then downloading and running Fritzing. Given these 
conditions, the contour file generated from gerber_no_outline.fzz looks fine. I 
will install updates and try again. Though not definitive, this suggests it may 
not be a general 13.10 issue, but specific to your installation. 

Just a guess, but I have seen odd behavior with Fritzing under Linux when there 
is already a version of Qt installed...

Original comment by irasc...@gmail.com on 25 Nov 2013 at 10:13

GoogleCodeExporter commented 9 years ago 
looks ok after updates as well.

Original comment by irasc...@gmail.com on 25 Nov 2013 at 10:43

GoogleCodeExporter commented 9 years ago 
That's odd... Attached the dpkg list filtered for the Qt versions installed on 
both machines, they have the same packages installed (as dependencies), just 
the architecture difference.

Both machines are identically configured Ubuntu 13.10.

"Kwak" is the 32bit machine and "Brand" is the 64bit machine.

Are there debug options I can enable to get some usefull debugging output?

Original comment by flud...@gmail.com on 26 Nov 2013 at 2:13

Attachments:

GoogleCodeExporter commented 9 years ago 
if you run fritzing from the command line, you can add -d to turn on debugging 
output. You may get lucky and see something relevant.

Are the gerber files for the other layers correct? Also, just for grins, maybe 
put up a performance monitor during gerber export to see whether memory is 
getting choked.

Original comment by irasc...@gmail.com on 26 Nov 2013 at 2:37

GoogleCodeExporter commented 9 years ago 
I just added -d and found only one thing indicating a possible fault:
"QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0"
All other layers seem to be generated OK apart from some glitches (dots in some 
layers, see attached gerber files). Those dots are easily removed using gerbv.

As for performance monitoring, the AMD64 machine has 8GB of RAM and the runtime 
of the Gerber export is too short (Less then one second) to be able to detect 
any significant change in memory usage.

Attached:
* The complete log of starting Fritzing (it opens the last used sketch) and 
only exporting the PCB to Gerber.
* The Fritzing file I first discovered the issue with
* The Gerber Output of said fritzing file while making the log.

Original comment by flud...@gmail.com on 26 Nov 2013 at 3:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Issue has moved to new issue tracker at github. Please continue the discussion 
at https://github.com/fritzing/fritzing-app/issues

Original comment by andre.knoerig@gmail.com on 23 Sep 2014 at 3:42