You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 20, 2023. It is now read-only.
So trying to use visolate for the first time - Have a board I designed in kicad, reworked so it does not use a ground plane (to work around that issue for now), and loaded it into visolate 3.1.1
But when I load the file, all the elements are huge and overlapping each other. The file appears fine in GerbView 4.0.6 and loads fine in some other tools I've tried also.
Yes, well, your Gerber file is almost certainly in metric (MOMM instead of MOIN at the beginning), and by looking at the code apparently Visolate is perfectly capable of handling metric data - just not when it's in the aperture (track width) descriptions. Hence all your tracks are painted 25.4 times thicker with the observed results. It can be kludge-fixed by manually editing your file and dividing the number(s) after the comma on each line beginning with "%ADDxxx," by 25.4. The result will be a thoroughly invalid Gerber file but Visolate will love it. Or, of course, if you can, you can try exporting your Gerber file in inches and it should work.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So trying to use visolate for the first time - Have a board I designed in kicad, reworked so it does not use a ground plane (to work around that issue for now), and loaded it into visolate 3.1.1
But when I load the file, all the elements are huge and overlapping each other. The file appears fine in GerbView 4.0.6 and loads fine in some other tools I've tried also.
Hopefully I'm just doing something silly...
GRB file: https://drive.google.com/file/d/0B_tI4K3x6U3_ZGJaZmF3cnU4T0E/view?usp=sharing
Screen shots of visolate and GRBView: https://docs.google.com/document/d/18rx4XHdTZHVQnV2tDGZXEY3t52iMsSDvY6d8GqSaxg0/edit?usp=sharing
The text was updated successfully, but these errors were encountered: