"It would also be good to have an option to crop everything outside the board edge so that in files such as the pic_programmer demo we do not have silk prints magically floating in the air."
I was thinking in the situation from a point of view of kicad as a CAD tool, it shouldn't hide from the user what it is wrong and may need a design review. So user should clean as much as possible the garbage outside the board, if not, it will be shipped in the gerber files. I know that in the PCB process that garbage and mistakes will be removed / or reproduced, but I was thinking that 3d-viewer should not lead the designer (special the less experienced people) in something that they expect because they see it that way on 3d-viewer but was not properly designed. Anyone else on feedback on this? Mario Luzeir ________________________________________ From: Cirilo Bernardo [[email protected]] Sent: 09 January 2016 21:44 To: Mário Luzeiro Cc: [email protected] Subject: Re: [Kicad-developers] T-shapes, castellated pads, cut-outs, slots.. and 3d-viewer For the first 2 links: This shape cannot really be represented in kicad except by cutouts - but we have no mechanism to separate plated from non-plated cutouts. In the first link we cannot use simple slots to represent this shape because the wider slot would have a large rounded end which extends beyond the narrow slot, but in the case where the slots are the same width I see no problem with allowing it since the designer may actually want that. It will be up to the designer to check the final design before production anyway. For the castellated edge (amazonaws link), this is becoming more common. I would expect the board edge to cut through the pads/holes in pads to produce the expected castellation. It would also be good to have an option to crop everything outside the board edge so that in files such as the pic_programmer demo we do not have silk prints magically floating in the air. In your last link someone did a bad job of attempting a castellation. This is not really a problem for kicad, it is a problem for the designers and fabricators. The only bad geometry which I would not allow is a cutout/drill hole which intersects the board outline at a single point or one which intersects at two points to create two separate bodies. I would not allow such geometry because it's an annoying case to handle even in MCAD software and makes absolutely no sense from the manufacturing perspective. In the case of not creating two separate bodies - kicad will yield awful results in such a case anyway because it is somewhat inflexible and requires a single body outline. This is one reason why I'd like to have a 'board outline layer' and 'cutout layer' rather than the single 'edge cuts' layer. - Cirilo On Sun, Jan 10, 2016 at 1:19 AM, Mário Luzeiro <[email protected]<mailto:[email protected]>> wrote: Hello all, Related with the 3d-viewer refactoring, how is kicad handling this (subject) cases and how it should be represented? The question is, what is supported and should be correct represented and what is not supported and should be... correct represented. So, For example, if we do a t-shap castellated with segment pads, should the slot be subtracted or should 3d-viewer draw the two pads to user will know that there is something wrong there and will not be mistaked? http://www.hitech.com.mk/Resources/Images//PCB/Tech/t-14.JPG http://i.stack.imgur.com/qyvAX.jpg Another case: If a user make a plated hole but it is cut half by a cut-outline (a hole) how should it be represented? Should I draw the plated hole, or should I subtract the cut-outline to it? https://kicad-info.s3.amazonaws.com/286e33b6746414c43e274332cae0bb34de1693c4afb.jpg IMO, if it is allowed and the way to manufacture it, then I should make the "Boolean operations". If that is not allowed and not possible to manufacture. then I should not "make any operations" and show it as-is. So user will see in 3d-viewer that it does not look good: http://i.stack.imgur.com/OwZaI.png Also, what are the things you have in mind in future to support this cases (i.e.: is there anything I can do so it will work in future?) Thanks all! Mario Luzeiro _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected]<mailto:[email protected]> Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
