C-multiplier again + LTspice note
in [Design]
|
From: Joe on 28 May 2010 12:17 On Fri, 28 May 2010 07:09:46 -0700, George Herold wrote: .... > Any way I'll try again posting the circuit. (This is far from my > circuit, I found it first in Phil Hobbs' book.) ....[big snip] > SYMBOL cap -320 -320 R0 > SYMATTR InstName C5 > SYMATTR Value 1µ > SYMATTR SpiceLine V=25 Irms=7.25 Rser=0.004 Lser=0 mfg="KEMET" > pn="C1206C105K3PAC" type="X5R" Except for the line break which had to be fixed, this looked ok in the news reader, but when saved to file, displayed as SYMATTR SpiceLine V=3D25 Irms=3D7.25 Rser=3D0.004 Lser=3D0 mfg=3D"KEMET" pn=3D"C1206C105K3PAC" type=3D"X5R" SYMBOL cap -320 -320 R0 SYMATTR InstName C5 SYMATTR Value 1=B5 SYMATTR SpiceLine V=3D25 Irms=3D7.25 Rser=3D0.004 Lser=3D0 mfg=3D"KEMET" pn=3D"C1206C105K3PAC" type=3D"X5R" That is, every "=" saved as "=3D" while "µ" (mu) saved as "=B5", all of which required external editing (replace all) before LTspice running under wine on linux would properly load the file. I don't know if the same problem will occur under MS-windows. If it does, maybe it depends on how you copied the text into your newsreader. You could fix the "µ" by manually editing to "u"; see chart on page 63 of scad3.pdf. You can manually fix the line breaks, if you see them when you post, by adding a "+" at the beginning of broken off parts. For example, SYMATTR SpiceLine V=25 Irms=7.25 Rser=0.004 Lser=0 mfg="KEMET" + pn="C1206C105K3PAC" type="X5R"
From: Mike on 28 May 2010 15:05 Joe <joe(a)somewhere.org> wrote: [...] > You can manually fix the line breaks, if you see them when you post, > by adding a "+" at the beginning of broken off parts. For example, > SYMATTR SpiceLine V=25 Irms=7.25 Rser=0.004 Lser=0 mfg="KEMET" > + pn="C1206C105K3PAC" type="X5R" I tried that. LTspice will not accept hard carriage returns in the middle of the attribute. It generates an error while loading. If you press "Ignore", it omits the rest of the line. This gives very strange component attributes:) I see only two solutions. Avoid long lines, or archive to a zip file and post it somewhere. abse is convenient, but not permanent. So if someone wants to review your work a decade from now, they will be disappointed. Another alternative might be to encode the file in Base64 and append it to the newsgroup posting. That means everyone would have to download a Base64 decoder. It would be instantly fatal. So what we need is a way to store binary files that will persist and are easy to decode, or find a way to allow long lines in LTspice. Any ideas? Thanks, Mike
From: George Herold on 28 May 2010 16:19 On May 28, 12:17 pm, Joe <j...(a)somewhere.org> wrote: > On Fri, 28 May 2010 07:09:46 -0700, George Herold wrote: > > ... > > > Any way I'll try again posting the circuit. (This is far from my > > circuit, I found it first in Phil Hobbs' book.) > ...[big snip] > > SYMBOL cap -320 -320 R0 > > SYMATTR InstName C5 > > SYMATTR Value 1µ > > SYMATTR SpiceLine V=25 Irms=7.25 Rser=0.004 Lser=0 mfg="KEMET" > > pn="C1206C105K3PAC" type="X5R" > > Except for the line break which had to be fixed, this looked ok in > the news reader, but when saved to file, displayed as > > SYMATTR SpiceLine V=3D25 Irms=3D7.25 Rser=3D0.004 Lser=3D0 mfg=3D"KEMET" > pn=3D"C1206C105K3PAC" type=3D"X5R" > SYMBOL cap -320 -320 R0 > SYMATTR InstName C5 > SYMATTR Value 1=B5 > SYMATTR SpiceLine V=3D25 Irms=3D7.25 Rser=3D0.004 Lser=3D0 mfg=3D"KEMET" > pn=3D"C1206C105K3PAC" type=3D"X5R" > > That is, every "=" saved as "=3D" while "µ" (mu) saved as "=B5", all > of which required external editing (replace all) before LTspice running > under wine on linux would properly load the file. I don't know if > the same problem will occur under MS-windows. If it does, maybe it > depends on how you copied the text into your newsreader. You could fix > the "µ" by manually editing to "u"; see chart on page 63 of scad3.pdf. > > You can manually fix the line breaks, if you see them when you post, > by adding a "+" at the beginning of broken off parts. For example, > SYMATTR SpiceLine V=25 Irms=7.25 Rser=0.004 Lser=0 mfg="KEMET" > + pn="C1206C105K3PAC" type="X5R" Thanks Joe, (I'm still an LTspice newlywed, so forgive my blunders.) I'll get rid of all the 'named' caps and try again. Does this work? Version 4 SHEET 1 1140 1108 WIRE -688 -448 -768 -448 WIRE -560 -448 -608 -448 WIRE -160 -448 -560 -448 WIRE -128 -448 -160 -448 WIRE -128 -400 -128 -448 WIRE -560 -352 -560 -368 WIRE -496 -352 -560 -352 WIRE -384 -352 -416 -352 WIRE -272 -352 -384 -352 WIRE -768 -320 -768 -448 WIRE -560 -320 -560 -352 WIRE -384 -320 -384 -352 WIRE -128 -288 -128 -304 WIRE -48 -288 -128 -288 WIRE 16 -288 -48 -288 WIRE -128 -256 -128 -288 WIRE -48 -256 -48 -288 WIRE -768 -224 -768 -240 WIRE -560 -224 -560 -256 WIRE -528 -224 -560 -224 WIRE -384 -224 -384 -256 WIRE -384 -224 -528 -224 WIRE -528 -208 -528 -224 WIRE -128 -160 -128 -176 WIRE -48 -160 -48 -192 FLAG -528 -208 0 FLAG -768 -224 0 FLAG -128 -160 0 FLAG -160 -448 Vin FLAG 16 -288 Vout FLAG -48 -160 0 SYMBOL npn -192 -400 R0 SYMATTR InstName Q1 SYMATTR Value 2N4401 SYMBOL voltage -768 -336 R0 WINDOW 123 0 0 Left 0 WINDOW 39 0 0 Left 0 SYMATTR InstName V1 SYMATTR Value 15 SYMBOL voltage -592 -448 R90 WINDOW 0 49 39 VRight 0 WINDOW 123 -48 40 VRight 0 WINDOW 39 0 0 Left 0 SYMATTR InstName V3 SYMATTR Value2 AC 1 SYMATTR Value "" SYMBOL res -576 -464 R0 SYMATTR InstName R1 SYMATTR Value 1k SYMBOL res -400 -368 R90 WINDOW 0 0 56 VBottom 0 WINDOW 3 42 49 VTop 0 SYMATTR InstName R2 SYMATTR Value 1k SYMBOL res -176 -368 R90 WINDOW 0 0 56 VBottom 0 WINDOW 3 32 56 VTop 0 SYMATTR InstName R3 SYMATTR Value 10 SYMBOL res -144 -272 R0 SYMATTR InstName R4 SYMATTR Value 1k SYMBOL cap -576 -320 R0 SYMATTR InstName C1 SYMATTR Value 100µ SYMATTR SpiceLine Rser=0.13 SYMBOL cap -400 -320 R0 SYMATTR InstName C2 SYMATTR Value 100µ SYMATTR SpiceLine Rser=0.13 SYMBOL cap -64 -256 R0 SYMATTR InstName C3 SYMATTR Value 100µ SYMATTR SpiceLine Rser=0.13 TEXT -216 -536 Left 0 ;Cap multiplier (Hobbs fillter) TEXT -224 -504 Left 0 !.ac oct 100 1 1e7
From: Joe on 28 May 2010 19:10 On Fri, 28 May 2010 13:19:52 -0700, George Herold wrote: > On May 28, 12:17 pm, Joe wrote: >> George Herold wrote: .... >>> SYMATTR Value 1µ .... >> SYMATTR Value 1=B5 .... >> "µ" (mu) saved as "=B5" [...] >> You can manually fix the line breaks, if you see them when you post, by >> adding a "+" at the beginning of broken off parts. [...] Mike noted that "LTspice will not accept hard carriage returns in the middle of the attribute" so disregard that. > > Thanks Joe, (I'm still an LTspice newlywed, so forgive my blunders.) > I'll get rid of all the 'named' caps and try again. > > Does this work? > > Version 4 > SHEET 1 1140 1108 .... > SYMATTR InstName C3 > SYMATTR Value 100µ .... It works much better -- loads into LTspice under wine ok. Still gets errors when Run, however, due to the µ (mu) transferring as =B5. However, one can fix that in LTspice, as opposed to using an external editor again.
From: Grant on 28 May 2010 22:04
On Fri, 28 May 2010 19:05:31 GMT, Mike <spam(a)me.not> wrote: >Joe <joe(a)somewhere.org> wrote: > >[...] > >> You can manually fix the line breaks, if you see them when you post, >> by adding a "+" at the beginning of broken off parts. For example, >> SYMATTR SpiceLine V=25 Irms=7.25 Rser=0.004 Lser=0 mfg="KEMET" >> + pn="C1206C105K3PAC" type="X5R" > >I tried that. LTspice will not accept hard carriage returns in the middle >of the attribute. It generates an error while loading. If you press >"Ignore", it omits the rest of the line. > >This gives very strange component attributes:) > >I see only two solutions. Avoid long lines, or archive to a zip file and >post it somewhere. abse is convenient, but not permanent. So if someone >wants to review your work a decade from now, they will be disappointed. > >Another alternative might be to encode the file in Base64 and append it >to the newsgroup posting. That means everyone would have to download a >Base64 decoder. It would be instantly fatal. What you mean is that means you're trying to post a binary (encoded as text) to a text-only (that's plain text) newsgroup, which is a big no no. > >So what we need is a way to store binary files that will persist and are >easy to decode, or find a way to allow long lines in LTspice. Any ideas? Just stop your silly news reader from wrapping long lines, simple! Grant. -- http://bugs.id.au/ |