There may well be a 9.08 someday, and in the meantime, we are 4 minor
releases past 9.07 (which means the current source repository is at
9.07d). Small changes are still being made by myself, and I encourage
others to contribute. If anyone is able to tackle this bug, send the
patch to me and I'll get it into the system.
-Steven Rubin
On 11/22/2020 1:36 PM, rjacobbaker wrote:
One of my students just sent me the following related to problems with
a MATLAB script we use also not being able to read the output of the
newer version of LTspice. This (newer version of LTspice represents
characters with 2 bytes instead of 1) is likely the issue with
Electric so if someone wants to use the newer version of LTspice with
Electric the below might be useful (if you make the programming Java
change).
If there is ever a new version of Electric, that is v. 9.08, it would
be good to get the LTspice code updated so that newer version of
LTspice work with Electric. Again
see: http://cmosedu.com/cmos1/ltspice/ltspice_electric.htm
Best wishes, Jake.
-------------------------------------------------------
Old versions of LTSpice apparently use one byte to represent
characters. The old 'readLtsRaw.m' script would therefore use this
code to read from the header:
header(linenum,charnum)= fread(fid, 1, '*uint8');
The result is that when the new versions of LTSpice use two characters
(UTF16?) every second character is just reading a zero and the
condition checks for end of line
and end of header fail. Changing the code to read two bytes fixes the
issue. the corrected line is:
header(linenum,charnum)= fread(fid, 1, '*uint16');
Updated 11/22/2020
--
Faculty do research to enhance their teaching in the lab and classroom.
http://cmosedu.com/jbaker/jbaker.htm
On Saturday, October 10, 2020 at 1:00:50 PM UTC-7 barba...@gmail.com
wrote:
Very thanks Mr. Steven Rubin for your help with the netlist file
concepts.
Very thanks Dr. Jacob Baker for your proposal, it´s work fine.
El sábado, 10 de octubre de 2020 a las 15:01:25 UTC-4, rjacobbaker
escribió:
When they emailed directly I suggested the following.
By putting the text for the netlist in spice code it should
allow running it directly with LTspice but I haven't tried it.
----------------------------------------
see:
http://cmosedu.com/videos/electric/tutorial1/electric_tutorial_1.htm
and the portion seen below. There is also an associated video:
http://cmosedu.com/videos/electric/electric_tutorial_1_video.mp4
Good luck!
image.png
--
Faculty do research to enhance their teaching in the lab and
classroom.
http://cmosedu.com/jbaker/jbaker.htm
On Sat, Oct 10, 2020 at 11:58 AM Steven Rubin
<str...@staticfreesoft.com> wrote:
Sorry, but this cannot be done easily. Spice netlists
don't have any placement information. This means you would
have to use Electric's placement tool, which would try to
optimize things in a rectangular grid layout, probably not
what you want. And it's not clear that Electric can read
this netlist, although it does have other ways of
importing netlists, so you might have to start by
converting the LTSpice file, a lot of trouble.
It would be best to go to the original program that wrote
the LTSpice netlist and see if it has some other
interchange format that Electric could read.
-Steven Rubin
On 10/10/2020 10:57 AM, Bárbaro Maykel López-Portilla
Vigil wrote:
Hi everyone:
I would like to ask you the following:
I have a netlist file generated in LTSpice (* .net) and I
need to load it in Electric VLSI . My idea is not to
make the schematic circuit in Electric VLSI again. Do you
know how it could be done?
--
You received this message because you are subscribed to
the Google Groups "Electric VLSI Editor" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to electricvlsi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/electricvlsi/5d3c2853-4f13-4d82-b370-6fb40ec47c4bn%40googlegroups.com
<https://groups.google.com/d/msgid/electricvlsi/5d3c2853-4f13-4d82-b370-6fb40ec47c4bn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to
the Google Groups "Electric VLSI Editor" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to electricvlsi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/electricvlsi/cb250d8a-961c-5f6c-f26b-20e5970f4fe0%40staticfreesoft.com
<https://groups.google.com/d/msgid/electricvlsi/cb250d8a-961c-5f6c-f26b-20e5970f4fe0%40staticfreesoft.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "Electric VLSI Editor" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to electricvlsi+unsubscr...@googlegroups.com
<mailto:electricvlsi+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/electricvlsi/dee1c908-4226-4116-bdf2-a868ca45aac9n%40googlegroups.com
<https://groups.google.com/d/msgid/electricvlsi/dee1c908-4226-4116-bdf2-a868ca45aac9n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "Electric
VLSI Editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to electricvlsi+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/electricvlsi/89f5ff17-14f7-8dc6-53f8-934ab99adcfa%40staticfreesoft.com.
