Could the plot values checkbox be fixed easily? Since it's a "fix" I suggest it for integration in 4.0.
On Thu, Sep 3, 2015 at 5:42 PM, yann jautard <brico...@free.fr> wrote: > > > > Le 03/09/2015 23:01, Jean-Paul Louis a écrit : > >> Hi nnn, >> >> I do not understand your point about having values on the PCB. NOBODY in >> the industry put values on the PCB. >> > > > I disagree, I have a few examples of recent industrial boards with values > on them. Last one I've seen is an inverter welder. > I do electronic troubleshooting and getting such a board with values > written down is really a pleasant thing when you don't have any > documentation on the device, and when you can't get value from the part > themselves because for some reason they've burned during the failure. > > So for that reason I also put values on silkscreen on my own boards. > > I really can't see the point of moving values to another layer. There is a > checkbox to plot or not the values on the silkscreen layer. Now that > checkbox does nothing, and this is pretty confusing. Leave values on > silkscreen layer and if you dont need them, just do not check the option, > where is the problem ? > > And if you need a Fab layer with the values... ok there is a problem you > can't get it. Well then for that particular purpose, there should be a way > in the plot window to output several layers in a single file like there is > in the print window. > > In fact, I think the three windows "plot", "print" and "export SVG" need > some rework to combine them all in a single one, because each of them have > features that can be needed in some ways to achieve a particular thing. Now > the example is adding values on silkscreen even if they are on a different > layer : you can't get it from the plot window, but you can do it with the > export SVG or print one using the single file output checkbox, and > selecting silk and fab layer. But on the other hand, from these windows you > can't get a gerber file... > > regards, > yann > > To facilitate the assembly, a lot of companies I worked for used a FAB >> drawing with one inch grid, and then generate a list of parts with the >> location on the grid. That’s more than enough to locate a part when >> troubleshooting. >> You can do the same easily. >> >> Just my $0.02, >> Jean-Paul >> AC9GH >> >> >> >> On Sep 3, 2015, at 3:32 PM, nnn <nnn4...@o2.pl> wrote: >>> >>> I don't want remove refdes from silkscreen - just add a copy (text %R) >>> scaled to footprints size - this layer really helps when you need to find >>> component from schematic on a pcb (if you don't have computer with your >>> design in a lab). >>> >>> >>> W dniu 03.09.2015 o 21:25, Andy Peters pisze: >>> >>>> On Sep 3, 2015, at 11:06 AM, nnn <nnn4...@o2.pl> wrote: >>>>> >>>>> Some time ago after short discussion on librarians mailing list it was >>>>> decided to change default reference and value fields of footprints and >>>>> move >>>>> values to F.Fab layer. >>>>> I think it was bad decision. I'm asking here to get more opinions. >>>>> >>>> For the value fields, putting them on the Fab layer is fine. As Chris >>>> notes, pretty much nobody prints the values on the board but having them on >>>> an assembly or fab drawing helps the human who’s stuffing the board. >>>> >>>> I think having the reference designators on any non-silkscreen layer is >>>> a mistake. If the ref-des is on the F.Fab layer, your generated Gerbers >>>> won’t have them on the F.SilkS (or B.Silks) layer, but rather on the Fab >>>> layer — and the PCB fab guys will probably bounce your design back because >>>> they won’t know how to make a silkscreen out of stuff on the F.Fab layer, >>>> especially when a silkscreen layer already exists in the package! >>>> >>>> And to make matters worse, if you had older parts in your library or a >>>> design which had the ref-deses all on the F.SilkS layer, and you add new >>>> footprints which have the ref-des on the F.Fab layer, your Gerbers will be >>>> all confused, since some parts will show a ref-des on the silkscreen and >>>> some won’t. >>>> >>>> I think it’s a matter of expectations: EVERYONE expects the reference >>>> designators to be on a silkscreen layer. >>>> >>>> -a >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~kicad-developers >>>> Post to : kicad-developers@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~kicad-developers >>>> More help : https://help.launchpad.net/ListHelp >>>> >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp