On 18/10/17 12:50, Thomas Langås wrote:
On Wed, Oct 18, 2017 at 12:04 PM, Gaurav Juvekar
wrote:
Summary:
- Does KiCad support having an F.Assembly and B.Assembly layer?
- Does KiCad support "special strings" like Altium's .Designator ?
I think F.Fab and B.Fab is what
Hi Thomas,
On 10/18/2017 11:19 AM, Thomas Langås wrote:
> Disclaimer: I come from the world of Altium, and might have a biased workflow.
>
> Is the following possible in any way in KiCad, or is there a different
> workflow that
> supports what I want?
>
> Usually, when I make components, I have
On 10/18/2017 6:50 AM, Thomas Langås wrote:
> On Wed, Oct 18, 2017 at 12:04 PM, Gaurav Juvekar
> wrote:
>>> Summary:
>>> - Does KiCad support having an F.Assembly and B.Assembly layer?
>>> - Does KiCad support "special strings" like Altium's .Designator ?
>> I think F.Fab
On Wed, Oct 18, 2017 at 12:04 PM, Gaurav Juvekar
wrote:
>> Summary:
>> - Does KiCad support having an F.Assembly and B.Assembly layer?
>> - Does KiCad support "special strings" like Altium's .Designator ?
> I think F.Fab and B.Fab is what you want. Reference designator is
Hi,
> Summary:
> - Does KiCad support having an F.Assembly and B.Assembly layer?
> - Does KiCad support "special strings" like Altium's .Designator ?
I think F.Fab and B.Fab is what you want. Reference designator is supported
using "REF**"
--
Regards,
Gaurav Juvekar
Disclaimer: I come from the world of Altium, and might have a biased workflow.
Is the following possible in any way in KiCad, or is there a different
workflow that
supports what I want?
Usually, when I make components, I have a mechanical layer called
"Assembly" where I either duplicate the
6 matches
Mail list logo