X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20210112; t=1681020713;
	h=to:subject:message-id:date:from:in-reply-to:references:mime-version
	:from:to:cc:subject:date:message-id:reply-to;
	bh=GXFy6g6PEI27DbbkxbwtsBTqo2trcRIrIx2gTWF3seA=;
	b=NIY5Fh6I1e+n0MqJgwNsI3A/BtqzpWwxu4wDzKTW3trzS+bC4bBiG+7jcyILKwTBq0
	sZExO6kgaOKkxs53My8q2yTPhjyRrzOvAGHqlHJeUwBa3jRfxQq1cy9XNBuVLh/wnYzI
	APdNBa2qMP6jm3zaHypi3RE1GhG8mJtcSQhYPmWNRN9lFxm+R9eTUvcRgth2FGndlAg0
	ZV6dIQRUAP/UKmOUtio3+RGJ3PrD1NsuweKrTeMhka1tjzG8JIH+fDQdD7vhckz0OzEd
	YntmdPzkC2JQLjE8YrwDhCgNngIpX+39KLGJuogl8wsRJqx0zSOxhCVqOMsN0/9+E5OJ
	kLhw==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20210112; t=1681020713;
	h=to:subject:message-id:date:from:in-reply-to:references:mime-version
	:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
	bh=GXFy6g6PEI27DbbkxbwtsBTqo2trcRIrIx2gTWF3seA=;
	b=KTmXs2k5I7n8k2Ezk7COscpGCQ8jGYtIlKK4UmX56qkr3hzg7I0wmfn70ORWZbZKUf
	S7OnbXyelwcUYGhTaGeCRbcS2zhb4DINsYJLZ+r3Zr1e47qudHfBzKltyhT2koRdUUNf
	2/wLnEsdXE9Vy7KYwct0Ecl5fZ7RUmm+QZSSeZbG2bEew6OgQFDEbW/RFU0ep/xewjkj
	laCfR6YkXfBU8vZ5oZWywQ3BEk0w8gsVsOBu+kY6n1EMVarfTfeB2oc24vKbGX158QLF
	i3WVKQHHyXED5zVypiVa2uNkX9s361FXDxnJ++EfV7gbnXoZN8YKsuq61s5d8mF++Rap
	YVrg==
X-Gm-Message-State:	AAQBX9cuH7tBUja1Qy++kK0mh/fHB84uE76G2rkBhwWfGPBNn4wZGYyG
	UxZesTHAYe8j8Dry5EhiCIwg5gAZZ9ZNyxMKHWyrIcWh0bk=
X-Google-Smtp-Source:	AKy350Yb5y6yh+XOmUi8hPVjXKUz2/P03ITlMSSaxQOKlpjTCeCNTvKA813pL/RyLixtHpa9khLi7clz62UbpXmcQ+k=
X-Received:	by 2002:a05:622a:1ba8:b0:3e6:71d6:5d65 with SMTP id
	bp40-20020a05622a1ba800b003e671d65d65mr2707109qtb.4.1681020713010; Sat, 08
	Apr 2023 23:11:53 -0700 (PDT)
MIME-Version:	1.0
References:	<20230408211414 DOT 675848499AA9 AT turkos DOT aspodata DOT se>
In-Reply-To:	<20230408211414.675848499AA9@turkos.aspodata.se>
From:	"Shashank Chintalagiri (shashank DOT chintalagiri AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date:	Sun, 9 Apr 2023 11:41:41 +0530
Message-ID:	<CALT8Ef4z6W56eucfqHOXpv0_4Rjoc=WJhSjGYUpuSQMsEbmJqg@mail.gmail.com>
Subject:	Re: [geda-user] Possible attribute conflict for refdes: R35
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com

--000000000000758d6a05f8e1227e
Content-Type: text/plain; charset="UTF-8"

For exotic passives and arrays, I always use the part number. Schematic
readability is a smaller problem than being able to communicate BOMs to
purchase people, soldering instructions to whoever is assembling the board,
etc.

The actual values can be put into the symbol as text and they will show up
on the schematic. We do this on a regular basis for most composite
components where some subcomponent values are critical, including opamps
with built in resistor networks. Since its only text, you can also trim it
to whatever information you really want to show. For example, when the
resistors are inside an opamps package, we sometimes only put down the
final gain and impedance numbers.

In case you want to do simulation, a custom spice model should be fairly
simple to create for it. We rarely do simulations though, so I'm not sure
if that presents any other quirks.


On Sun, 9 Apr 2023, 03:21 karl AT aspodata DOT se [via geda-user AT delorie DOT com], <
geda-user AT delorie DOT com> wrote:

>  What value to be used for a resistor array with R1 = R4 < R2 = R3 ?
>
> The technical answer would be to use the part number, but then it would
> be harder to understand the circuit since the resistance value isn't
> obvious.
> One could use the pin label (as e.g. in mcu use), but that would make it
> hard to change the "value" to e.g. 1k, or to change it to discrete
> resistors.
>
> Any idea ?
>
> Regards,
> /Karl Hammar
>
>

--000000000000758d6a05f8e1227e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">For exotic passives and arrays, I always use the part num=
ber. Schematic readability is a smaller problem than being able to communic=
ate BOMs to purchase people, soldering instructions to whoever is assemblin=
g the board, etc.<div dir=3D"auto"><br></div><div dir=3D"auto">The actual v=
alues can be put into the symbol as text and they will show up on the schem=
atic. We do this on a regular basis for most composite components where som=
e subcomponent values are critical, including opamps with built in resistor=
 networks. Since its only text, you can also trim it to whatever informatio=
n you really want to show. For example, when the resistors are inside an op=
amps package, we sometimes only put down the final gain and impedance numbe=
rs.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">In case you wa=
nt to do simulation, a custom spice model should be fairly simple to create=
 for it. We rarely do simulations though, so I&#39;m not sure if that prese=
nts any other quirks.</div><div dir=3D"auto"><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, 9 Apr 2023, =
03:21 <a href=3D"mailto:karl AT aspodata DOT se">karl AT aspodata DOT se</a> [via <a href=
=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>], &lt;<a href=
=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">=C2=A0What value to be used for a resis=
tor array with R1 =3D R4 &lt; R2 =3D R3 ?<br>
<br>
The technical answer would be to use the part number, but then it would<br>
be harder to understand the circuit since the resistance value isn&#39;t <b=
r>
obvious.<br>
One could use the pin label (as e.g. in mcu use), but that would make it<br=
>
hard to change the &quot;value&quot; to e.g. 1k, or to change it to discret=
e resistors.<br>
<br>
Any idea ?<br>
<br>
Regards,<br>
/Karl Hammar<br>
<br>
</blockquote></div>

--000000000000758d6a05f8e1227e--

- Raw text -