You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(7) |
Aug
|
Sep
(14) |
Oct
(4) |
Nov
|
Dec
|
2005 |
Jan
(3) |
Feb
|
Mar
(5) |
Apr
(3) |
May
(3) |
Jun
(6) |
Jul
(5) |
Aug
(4) |
Sep
(12) |
Oct
(3) |
Nov
(2) |
Dec
(5) |
2006 |
Jan
(8) |
Feb
(26) |
Mar
(38) |
Apr
(30) |
May
(13) |
Jun
(35) |
Jul
(7) |
Aug
(13) |
Sep
(30) |
Oct
(22) |
Nov
(13) |
Dec
(11) |
2007 |
Jan
(16) |
Feb
(19) |
Mar
(34) |
Apr
(20) |
May
(21) |
Jun
(21) |
Jul
(6) |
Aug
(9) |
Sep
(19) |
Oct
(11) |
Nov
(14) |
Dec
(49) |
2008 |
Jan
(33) |
Feb
(20) |
Mar
(25) |
Apr
(32) |
May
(27) |
Jun
(19) |
Jul
(43) |
Aug
(17) |
Sep
(30) |
Oct
(42) |
Nov
(56) |
Dec
(37) |
2009 |
Jan
(15) |
Feb
(20) |
Mar
(48) |
Apr
(56) |
May
(60) |
Jun
(7) |
Jul
(1) |
Aug
(6) |
Sep
(14) |
Oct
(14) |
Nov
(8) |
Dec
(2) |
2010 |
Jan
(7) |
Feb
(11) |
Mar
(16) |
Apr
(4) |
May
(14) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(4) |
Oct
(20) |
Nov
(1) |
Dec
(7) |
2011 |
Jan
(7) |
Feb
(9) |
Mar
(70) |
Apr
(33) |
May
(14) |
Jun
(13) |
Jul
(8) |
Aug
(15) |
Sep
(9) |
Oct
(13) |
Nov
(6) |
Dec
(8) |
2012 |
Jan
(17) |
Feb
(3) |
Mar
(2) |
Apr
(2) |
May
(3) |
Jun
(5) |
Jul
(5) |
Aug
(2) |
Sep
(3) |
Oct
(5) |
Nov
(8) |
Dec
|
2013 |
Jan
(11) |
Feb
(16) |
Mar
(1) |
Apr
(13) |
May
(4) |
Jun
(11) |
Jul
|
Aug
(4) |
Sep
(6) |
Oct
(9) |
Nov
(2) |
Dec
(4) |
2014 |
Jan
|
Feb
(8) |
Mar
(15) |
Apr
(19) |
May
(18) |
Jun
(11) |
Jul
(8) |
Aug
(17) |
Sep
(22) |
Oct
(11) |
Nov
(15) |
Dec
(3) |
2015 |
Jan
(5) |
Feb
(14) |
Mar
(19) |
Apr
(8) |
May
(2) |
Jun
(3) |
Jul
(17) |
Aug
(7) |
Sep
(14) |
Oct
(2) |
Nov
(3) |
Dec
(9) |
2016 |
Jan
(34) |
Feb
(14) |
Mar
(25) |
Apr
(6) |
May
(10) |
Jun
(10) |
Jul
(4) |
Aug
(3) |
Sep
(5) |
Oct
(16) |
Nov
(13) |
Dec
(5) |
2017 |
Jan
(6) |
Feb
(3) |
Mar
(11) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(5) |
Aug
(11) |
Sep
(9) |
Oct
(6) |
Nov
(5) |
Dec
(2) |
2018 |
Jan
|
Feb
(16) |
Mar
(13) |
Apr
(10) |
May
(11) |
Jun
(16) |
Jul
(11) |
Aug
(8) |
Sep
(7) |
Oct
(2) |
Nov
(3) |
Dec
(1) |
2019 |
Jan
(9) |
Feb
(8) |
Mar
(3) |
Apr
(1) |
May
(18) |
Jun
(1) |
Jul
|
Aug
(12) |
Sep
(3) |
Oct
(2) |
Nov
(3) |
Dec
(3) |
2020 |
Jan
(10) |
Feb
(3) |
Mar
(1) |
Apr
(2) |
May
(16) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(9) |
Dec
(1) |
2021 |
Jan
(2) |
Feb
(2) |
Mar
(1) |
Apr
(2) |
May
(3) |
Jun
|
Jul
|
Aug
(10) |
Sep
(4) |
Oct
(5) |
Nov
(1) |
Dec
|
2022 |
Jan
(1) |
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(4) |
Aug
(5) |
Sep
(6) |
Oct
(5) |
Nov
(3) |
Dec
|
2024 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Claudio G. <cla...@vi...> - 2019-05-10 19:52:21
|
yep, it's a bug... apparently the line at https://github.com/Qucs/qucs/blob/develop/qucs-core/src/components/attenuator.cpp#L43 should be nr_double_t s11 = r * (a - 1) / (a - r * r); (compare with the docs; I did not check the other formulas/cases) Regards, Claudio > Il 10 maggio 2019 alle 21.25 andresmmera <and...@gm...> ha scritto: > > > Hi, > > I uploaded the image to pasteboard: https://pasteboard.co/Ie5PHGm.png > > I also expected that Zref = 75 Ohm should work, but it doesn't. I reckon > that z0 is always set to 50 Ohms (see [2]) so you'll always have a > mismatch whenever Zref!=50 Ohm > > [1] http://qucs.sourceforge.net/tech/node51.html > [2] https://github.com/Qucs/qucs/blob/develop/qucs-core/src//circuit.cpp#L52 > > > On 10/5/19 20:24, Claudio Girardi via Qucs-help wrote: > > Hello, > > I did not actually check, but everything may be fine as it currently is :) . > > The attachment did not get thru, as usual, so I do not know how your test circuit looked like exactly. > > The attenuator has a Zref parameter, which by default is 50 ohm. I'd expect that if you change it to 75 ohm it will behave as it should in your 75 ohm system. If not, this is a bug. Is this what you are seeing? > > > > The docs specify *power* attenuation because, "attenuation" may be ambiguous. If one says "I want to attenuate this signal by a factor of ten" does it mean they want one tenth of the power or one tenth of the voltage? One is the square/square root of the other. The formulas in the docs defines L to be the power attenuation. > > > > Regards, > > Claudio > > > >> Il 10 maggio 2019 alle 19.17 andresmmera <and...@gm...> ha scritto: > >> > >> > >> Hi all, > >> > >> I came across with an unexpected result involving the attenuator component. > >> > >> Well, I placed this component in a 75 Ohm system and for my surprise, I > >> found it was unmatched. I expected that to behave as an RF attenuator > >> [1] so S11, S22 -> -inf for a given Z0 = Zref system. However, it seems > >> that this holds only for a 50 Ohm system. I attach an screenshot (please > >> let me know if the attachment was filtered out by the mail server). > >> Then, I visited the docs [2] I've noticed that they mention that this > >> block is a "(power) attenuator". Indeed, Eqs. 9.76 and 9.79 show that > >> the attenuator won't be matched if Zref != 50. Please excuse my > >> ignorance... what a power attenuator is? I've just found RF power > >> attenuators after googling that. Is there any chance this block can be > >> used as a matched RF attenuator such that Zref != 50Ohm? > >> > >> [1] https://www.microwaves101.com/encyclopedias/attenuators > >> > >> [2] http://qucs.sourceforge.net/tech/node51.html > >> > >> [3] Code: > >> https://github.com/Qucs/qucs/blob/hotfix-0.0.20/qucs-core/src/components/attenuator.cpp > >> > >> > >> 6541 > >> > >> ][' > >> > >> > >> _______________________________________________ > >> Qucs-help mailing list > >> Quc...@li... > >> https://lists.sourceforge.net/lists/listinfo/qucs-help > > > > _______________________________________________ > > Qucs-help mailing list > > Quc...@li... > > https://lists.sourceforge.net/lists/listinfo/qucs-help > > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: andresmmera <and...@gm...> - 2019-05-10 19:26:03
|
Hi, I uploaded the image to pasteboard: https://pasteboard.co/Ie5PHGm.png I also expected that Zref = 75 Ohm should work, but it doesn't. I reckon that z0 is always set to 50 Ohms (see [2]) so you'll always have a mismatch whenever Zref!=50 Ohm [1] http://qucs.sourceforge.net/tech/node51.html [2] https://github.com/Qucs/qucs/blob/develop/qucs-core/src//circuit.cpp#L52 On 10/5/19 20:24, Claudio Girardi via Qucs-help wrote: > Hello, > I did not actually check, but everything may be fine as it currently is :) . > The attachment did not get thru, as usual, so I do not know how your test circuit looked like exactly. > The attenuator has a Zref parameter, which by default is 50 ohm. I'd expect that if you change it to 75 ohm it will behave as it should in your 75 ohm system. If not, this is a bug. Is this what you are seeing? > > The docs specify *power* attenuation because, "attenuation" may be ambiguous. If one says "I want to attenuate this signal by a factor of ten" does it mean they want one tenth of the power or one tenth of the voltage? One is the square/square root of the other. The formulas in the docs defines L to be the power attenuation. > > Regards, > Claudio > >> Il 10 maggio 2019 alle 19.17 andresmmera <and...@gm...> ha scritto: >> >> >> Hi all, >> >> I came across with an unexpected result involving the attenuator component. >> >> Well, I placed this component in a 75 Ohm system and for my surprise, I >> found it was unmatched. I expected that to behave as an RF attenuator >> [1] so S11, S22 -> -inf for a given Z0 = Zref system. However, it seems >> that this holds only for a 50 Ohm system. I attach an screenshot (please >> let me know if the attachment was filtered out by the mail server). >> Then, I visited the docs [2] I've noticed that they mention that this >> block is a "(power) attenuator". Indeed, Eqs. 9.76 and 9.79 show that >> the attenuator won't be matched if Zref != 50. Please excuse my >> ignorance... what a power attenuator is? I've just found RF power >> attenuators after googling that. Is there any chance this block can be >> used as a matched RF attenuator such that Zref != 50Ohm? >> >> [1] https://www.microwaves101.com/encyclopedias/attenuators >> >> [2] http://qucs.sourceforge.net/tech/node51.html >> >> [3] Code: >> https://github.com/Qucs/qucs/blob/hotfix-0.0.20/qucs-core/src/components/attenuator.cpp >> >> >> 6541 >> >> ][' >> >> >> _______________________________________________ >> Qucs-help mailing list >> Quc...@li... >> https://lists.sourceforge.net/lists/listinfo/qucs-help > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Claudio G. <cla...@vi...> - 2019-05-10 18:38:46
|
Hello, I did not actually check, but everything may be fine as it currently is :) . The attachment did not get thru, as usual, so I do not know how your test circuit looked like exactly. The attenuator has a Zref parameter, which by default is 50 ohm. I'd expect that if you change it to 75 ohm it will behave as it should in your 75 ohm system. If not, this is a bug. Is this what you are seeing? The docs specify *power* attenuation because, "attenuation" may be ambiguous. If one says "I want to attenuate this signal by a factor of ten" does it mean they want one tenth of the power or one tenth of the voltage? One is the square/square root of the other. The formulas in the docs defines L to be the power attenuation. Regards, Claudio > Il 10 maggio 2019 alle 19.17 andresmmera <and...@gm...> ha scritto: > > > Hi all, > > I came across with an unexpected result involving the attenuator component. > > Well, I placed this component in a 75 Ohm system and for my surprise, I > found it was unmatched. I expected that to behave as an RF attenuator > [1] so S11, S22 -> -inf for a given Z0 = Zref system. However, it seems > that this holds only for a 50 Ohm system. I attach an screenshot (please > let me know if the attachment was filtered out by the mail server). > Then, I visited the docs [2] I've noticed that they mention that this > block is a "(power) attenuator". Indeed, Eqs. 9.76 and 9.79 show that > the attenuator won't be matched if Zref != 50. Please excuse my > ignorance... what a power attenuator is? I've just found RF power > attenuators after googling that. Is there any chance this block can be > used as a matched RF attenuator such that Zref != 50Ohm? > > [1] https://www.microwaves101.com/encyclopedias/attenuators > > [2] http://qucs.sourceforge.net/tech/node51.html > > [3] Code: > https://github.com/Qucs/qucs/blob/hotfix-0.0.20/qucs-core/src/components/attenuator.cpp > > > 6541 > > ][' > > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: andresmmera <and...@gm...> - 2019-05-10 17:17:26
|
Hi all, I came across with an unexpected result involving the attenuator component. Well, I placed this component in a 75 Ohm system and for my surprise, I found it was unmatched. I expected that to behave as an RF attenuator [1] so S11, S22 -> -inf for a given Z0 = Zref system. However, it seems that this holds only for a 50 Ohm system. I attach an screenshot (please let me know if the attachment was filtered out by the mail server). Then, I visited the docs [2] I've noticed that they mention that this block is a "(power) attenuator". Indeed, Eqs. 9.76 and 9.79 show that the attenuator won't be matched if Zref != 50. Please excuse my ignorance... what a power attenuator is? I've just found RF power attenuators after googling that. Is there any chance this block can be used as a matched RF attenuator such that Zref != 50Ohm? [1] https://www.microwaves101.com/encyclopedias/attenuators [2] http://qucs.sourceforge.net/tech/node51.html [3] Code: https://github.com/Qucs/qucs/blob/hotfix-0.0.20/qucs-core/src/components/attenuator.cpp 6541 ][' |
From: Guilherme B. T. <gui...@gm...> - 2019-05-03 11:17:15
|
Hi David, You report is similar to this https://github.com/Qucs/qucs/issues/915 Same, suggestion, if you can use verilog it might be easier to make it work at this moment. Regards, Guilherme On Fri, May 3, 2019 at 11:13 AM David Todd <dw....@gm...> wrote: > Hello, > the Qucs Digital Simulation gives me errors during simulation building > as follows: > > Simulation Progress > > creating netlist... done. > > Starting C:\qucs\bin\qucsdigi.bat > > > running C++ conversion... > > compiling functions... > > compiling main... > > linking... > > simulating... > > running VCD conversion... > > > Errors and Warnings > > c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: > digi.o:digi.cc:(.text+0x4f3): undefined reference to > `name_stack::push(std::__cxx11::basic_string<char, > std::char_traits<char>, std::allocator<char> >)' > > c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: > digi.o:digi.cc:(.text+0x595): undefined reference to > `name_stack::push(std::__cxx11::basic_string<char, > std::char_traits<char>, std::allocator<char> >)' > > c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: > digi.o:digi.cc:(.text+0x5d6): undefined reference to > `name_stack::push(std::__cxx11::basic_string<char, > std::char_traits<char>, std::allocator<char> >)' > > c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: > digi.o:digi.cc:(.text+0x6a3): undefined reference to > `name_stack::set(std::__cxx11::basic_string<char, > std::char_traits<char>, std::allocator<char> >)' > > c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: > digi.o:digi.cc:(.text+0x731): undefined reference to > `name_stack::set(std::__cxx11::basic_string<char, > std::char_traits<char>, std::allocator<char> >)' > > collect2.exe: error: ld returned 1 exit status > > 'digi.exe' is not recognized as an internal or external command, > > operable program or batch file. > > > It seems to me like the simulation bombs out during the linkinpart of > the simulation? > > The error messages above seems look like C++ code to me ? > > > I have set the simple paths in the w8.1 environments for qucs directory > path anf mingw32 paths: > > c:\qucs\bin and c:\mingw32\bin > > The 'collect2.exe' and digi.exe not recognised. > The above comes from a simple inverter gate with a digital source. > > I wonder if there is something in one of the batch files of the package > causing this problem which I could look for? > > > thanks to anyone who can help? > > David Todd > > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help > |
From: David T. <dw....@gm...> - 2019-05-03 09:13:08
|
Hello, the Qucs Digital Simulation gives me errors during simulation building as follows: Simulation Progress creating netlist... done. Starting C:\qucs\bin\qucsdigi.bat running C++ conversion... compiling functions... compiling main... linking... simulating... running VCD conversion... Errors and Warnings c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: digi.o:digi.cc:(.text+0x4f3): undefined reference to `name_stack::push(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)' c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: digi.o:digi.cc:(.text+0x595): undefined reference to `name_stack::push(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)' c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: digi.o:digi.cc:(.text+0x5d6): undefined reference to `name_stack::push(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)' c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: digi.o:digi.cc:(.text+0x6a3): undefined reference to `name_stack::set(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)' c:/mingw32/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: digi.o:digi.cc:(.text+0x731): undefined reference to `name_stack::set(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)' collect2.exe: error: ld returned 1 exit status 'digi.exe' is not recognized as an internal or external command, operable program or batch file. It seems to me like the simulation bombs out during the linkinpart of the simulation? The error messages above seems look like C++ code to me ? I have set the simple paths in the w8.1 environments for qucs directory path anf mingw32 paths: c:\qucs\bin and c:\mingw32\bin The 'collect2.exe' and digi.exe not recognised. The above comes from a simple inverter gate with a digital source. I wonder if there is something in one of the batch files of the package causing this problem which I could look for? thanks to anyone who can help? David Todd --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
From: Eider F. <rei...@gm...> - 2019-04-24 13:47:25
|
I would like to know how to use the Fourier transform to plot on the graph (amplitude in dB and frequency) to check the noise amplitude at the output of a noise generator circuit? <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Livre de vírus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> |
From: Stefanie S. <ste...@gm...> - 2019-03-23 23:42:44
|
Hi Qucs team, I'm new (very new) to Qucs and have built a digital circuit to simulate given outputs. I've tried to run the simulation a few times with different problems each time. At the moment, when I try to run the simulation, it is aborted due to "fatal error: too many errors emitted". I've included some screenshots of where I've seen some errors (there might also be repeated errors screenshotted, sorry about that) but I'm not entirely sure what I should do to fix this? Is it something that I've done wrong in my schematic?? Thank you for any help, Stefanie |
From: Guilherme B. T. <gui...@gm...> - 2019-03-19 08:17:19
|
Hello, I suppose you are buildind the latest RC or from develop. This bug might be related. https://github.com/Qucs/qucs/issues/901 Try renaming the qucs-core to qucsator in the makefiles. Regards, Guilherme On Thu, Mar 14, 2019 at 8:20 PM Verma, Richa <ver...@bu...> wrote: > Hi > > I am having problem in building Verilog-A project in QUCS. From GUI upon > selecting Build Verilog-A project, qucs calls cpp2lin.makefile from the > below path. > > > /usr/local/include/qucs-core/cpp2lib.makefile > > > But, to my surprise "qucs-core" directory does not exist and hence qucs > stops. However, I could see "qucsator" directory in "include" and could > also see cpp2lib.makefile in "qucsator". I tried to change directory path > but could not change path from qucs GUI. > > > Is there any way I can change path from qucs GUI? > > > NOTE: I have installed qucs and adms in Linux Ubuntu. > > > Regards > > Richa Verma > > PhD Student > > Dept. of Electrical and Computer Engineering > > The Ohio State University > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help > |
From: Verma, R. <ver...@bu...> - 2019-03-14 18:47:55
|
Hi I am having problem in building Verilog-A project in QUCS. From GUI upon selecting Build Verilog-A project, qucs calls cpp2lin.makefile from the below path. /usr/local/include/qucs-core/cpp2lib.makefile But, to my surprise "qucs-core" directory does not exist and hence qucs stops. However, I could see "qucsator" directory in "include" and could also see cpp2lib.makefile in "qucsator". I tried to change directory path but could not change path from qucs GUI. Is there any way I can change path from qucs GUI? NOTE: I have installed qucs and adms in Linux Ubuntu. Regards Richa Verma PhD Student Dept. of Electrical and Computer Engineering The Ohio State University |
From: Juan L. P. <j.l...@lm...> - 2019-02-15 18:17:25
|
Hello, I am having a problem using a coaxial line in a transient analysis. I use the line calculation tool to get values for a 50 Ohm line (it would be nice if the model and the line calculation tool both used either rho or sigma, not one in the model and the other in the tool). S-parameter simulation seems to work OK. When I do transient simulation both the voltage and current from the source go to 0 and I get no output. If I substitute a transmission line for the coax everything is OK. Am I missing something? I have attached the project files. Juan Luglio, PhD JRL Engineering, LLC (414)324-1050 |
From: Rod N. <rod...@gm...> - 2019-02-06 09:56:46
|
Disabling docs allowed the compilation to successfully complete. I am now running qucs0.0.20. However, I still have my original problem with digital simulations. I have tracked this to the freehdl implementation which seg faults. I have tried the simplest digital circuit in qucs, and I have tried the simplest vhdl circuit I can find. Both result in a seg fault. My freehdl version is: statik@Clevo-P15SM-A-SM1-A ~ $ freehdl-config --version 0.0.8 My test.sch is: <Qucs Schematic 0.0.20> <Properties> <View=0,0,800,800,1,0,0> <Grid=10,10,1> <DataSet=test.dat> <DataDisplay=test.dpl> <OpenDisplay=1> <Script=test.m> <RunScript=0> <showFrame=0> <FrameText0=Title> <FrameText1=Drawn By:> <FrameText2=Date:> <FrameText3=Revision:> </Properties> <Symbol> </Symbol> <Components> <AND Y1 1 530 270 -26 27 0 0 "2" 0 "1 V" 0 "0" 0 "10" 0 "old" 0> <DigiSource S1 1 500 260 -35 16 0 0 "1" 1 "low" 0 "1ns; 1ns" 0 "1 V" 0> <DigiSource S2 1 500 280 -35 16 0 0 "2" 1 "low" 0 "1ns; 1ns" 0 "1 V" 0> <.Digi Digi1 1 640 350 0 65 0 0 "TruthTable" 1 "10 ns" 0 "VHDL" 0> </Components> <Wires> <560 270 560 270 "Output" 590 240 0 ""> </Wires> <Diagrams> </Diagrams> <Paintings> </Paintings> and my test.vhdl is: ENTITY andgate IS PORT(ina, inb : IN bit; op : OUT bit); END ENTITY andgate; ARCHITECTURE behavioral OF andgate IS BEGIN op <= ina AND inb; END behavioral; use work.all; entity testbench is end entity testbench; architecture dataflow of testbench is signal inpone, inptwo, outp : bit; begin portmaps : entity andgate port map(inpone, inptwo, outp); testprocess: process is begin inpone <= '0'; inptwo <= '0'; wait for 10 ns; inpone <= '0'; inptwo <= '1'; wait for 10 ns; inpone <= '1'; inptwo <= '0'; wait for 10 ns; inpone <= '1'; inptwo <= '1'; wait for 10 ns; end process testprocess; end architecture dataflow; The command and output for the vhdl is: statik@Clevo-P15SM-A-SM1-A ~/Documents/Forces/CSE APPS/Digital Electronics $ /usr/bin/freehdl-v2cc -m Test._main_.cc -L /usr/share/freehdl/lib -o Test.cc Test.vhdl Segmentation fault (core dumped) and running the test.sch in qucs results in: Starting new simulation on Wed 06. Feb 2019 at 05:55:56:376 creating netlist... done. Starting /usr/local/bin/qucsdigi running C++ conversion... Errors occurred during simulation on Wed 06. Feb 2019 at 05:55:56:567 Aborted. Segmentation fault (core dumped) Can anyone help me get this digital simulation working? Thanks! On 2019-02-06 2:23 a.m., Claudio Girardi via Qucs-help wrote: > Hello, > > you can skip building the documentation by passing --disable-doc to configure. > > > Regards, > > Claudio > >> Il 5 febbraio 2019 alle 22.46 Rod Naugler <rod...@gm...> ha scritto: >> >> Added libx11-dev and it compiles further. Now the error is: >> >> not using octave to update coplanarzl.eps. creating dummy. >> export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex >> export BIBINPUTS=.:; : technical >> export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex >> export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex >> : technical.dvi -o technical.ps >> /usr/bin/ps2pdf technical.ps >> Error: /undefinedfilename in (technical.ps) >> Operand stack: >> >> Execution stack: >> %interp_exit .runexec2 --nostringval-- --nostringval-- >> --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- >> --nostringval-- false 1 %stopped_push >> Dictionary stack: >> --dict:961/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)-- >> Current allocation mode is local >> Last OS error: No such file or directory >> GPL Ghostscript 9.26: Unrecoverable error, exit code 1 >> Makefile:645: recipe for target 'technical.pdf' failed >> make[2]: *** [technical.pdf] Error 1 >> make[2]: Leaving directory >> '/media/statik/Linux_Storage/Public/qucs-0.0.20/qucs-doc/technical' >> Makefile:383: recipe for target 'all-recursive' failed >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory >> '/media/statik/Linux_Storage/Public/qucs-0.0.20/qucs-doc' >> Makefile:381: recipe for target 'all-recursive' failed >> make: *** [all-recursive] Error 1 >> >> It looks like it fails to create, or find, technical.dvi? >> >> > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Claudio G. <cla...@vi...> - 2019-02-06 06:23:46
|
Hello, you can skip building the documentation by passing --disable-doc to configure. Regards, Claudio > > Il 5 febbraio 2019 alle 22.46 Rod Naugler <rod...@gm...> ha scritto: > > Added libx11-dev and it compiles further. Now the error is: > > not using octave to update coplanarzl.eps. creating dummy. > export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex > export BIBINPUTS=.:; : technical > export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex > export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex > : technical.dvi -o technical.ps > /usr/bin/ps2pdf technical.ps > Error: /undefinedfilename in (technical.ps) > Operand stack: > > Execution stack: > %interp_exit .runexec2 --nostringval-- --nostringval-- > --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- > --nostringval-- false 1 %stopped_push > Dictionary stack: > --dict:961/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)-- > Current allocation mode is local > Last OS error: No such file or directory > GPL Ghostscript 9.26: Unrecoverable error, exit code 1 > Makefile:645: recipe for target 'technical.pdf' failed > make[2]: *** [technical.pdf] Error 1 > make[2]: Leaving directory > '/media/statik/Linux_Storage/Public/qucs-0.0.20/qucs-doc/technical' > Makefile:383: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory > '/media/statik/Linux_Storage/Public/qucs-0.0.20/qucs-doc' > Makefile:381: recipe for target 'all-recursive' failed > make: *** [all-recursive] Error 1 > > It looks like it fails to create, or find, technical.dvi? > > |
From: Rod N. <rod...@gm...> - 2019-02-05 21:46:21
|
Added libx11-dev and it compiles further. Now the error is: not using octave to update coplanarzl.eps. creating dummy. export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex export BIBINPUTS=.:; : technical export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex export TEXINPUTS=.:./..:./..:; : -interaction=nonstopmode technical.tex : technical.dvi -o technical.ps /usr/bin/ps2pdf technical.ps Error: /undefinedfilename in (technical.ps) Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push Dictionary stack: --dict:961/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)-- Current allocation mode is local Last OS error: No such file or directory GPL Ghostscript 9.26: Unrecoverable error, exit code 1 Makefile:645: recipe for target 'technical.pdf' failed make[2]: *** [technical.pdf] Error 1 make[2]: Leaving directory '/media/statik/Linux_Storage/Public/qucs-0.0.20/qucs-doc/technical' Makefile:383: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/media/statik/Linux_Storage/Public/qucs-0.0.20/qucs-doc' Makefile:381: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 It looks like it fails to create, or find, technical.dvi? On 2019-02-05 7:13 a.m., Roel Jordans wrote: > Hi Rod, > > I'm not very familiar with compiling qucs from source but looking at > the error message tells me that it's not finding the X11 library > during linking. Can you check if that's correctly installed? > > Cheers, > > Roel > > On 05-02-19 11:13, Rod Naugler wrote: >> Hi all, >> >> I'm trying to compile qucs0.0.20 from source and I'm hitting an error: >> libtool: link: g++ -g -O2 -pipe -fno-exceptions >> -Wno-deprecated-register -std=c++0x -o qucs.real main.o qucs_.o >> ./.libs/libqucsschematic.a -lX11 -lQtScript -lQtSvg -lQtXml >> -lQt3Support -lQtGui -lQtNetwork -lQtSql -lQtCore -ldl >> /usr/bin/ld: cannot find -lX11 >> >> >> Any ideas? >> >> >> Rod >> >> >> >> _______________________________________________ >> Qucs-help mailing list >> Quc...@li... >> https://lists.sourceforge.net/lists/listinfo/qucs-help > > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Gregg N. <gre...@bl...> - 2019-02-05 12:21:47
|
It happens. -----Original Message----- From: Rod Naugler <rod...@gm...> Sent: Tuesday, February 5, 2019 5:14 AM To: quc...@li... Subject: [Qucs-help] Error when compiling qucs 0.0.20 from source Hi all, I'm trying to compile qucs0.0.20 from source and I'm hitting an error: libtool: link: g++ -g -O2 -pipe -fno-exceptions -Wno-deprecated-register -std=c++0x -o qucs.real main.o qucs_.o ./.libs/libqucsschematic.a -lX11 -lQtScript -lQtSvg -lQtXml -lQt3Support -lQtGui -lQtNetwork -lQtSql -lQtCore -ldl /usr/bin/ld: cannot find -lX11 Any ideas? Rod _______________________________________________ Qucs-help mailing list Quc...@li... https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Roel J. <r.j...@sc...> - 2019-02-05 11:32:32
|
Hi Rod, I'm not very familiar with compiling qucs from source but looking at the error message tells me that it's not finding the X11 library during linking. Can you check if that's correctly installed? Cheers, Roel On 05-02-19 11:13, Rod Naugler wrote: > Hi all, > > I'm trying to compile qucs0.0.20 from source and I'm hitting an error: > libtool: link: g++ -g -O2 -pipe -fno-exceptions > -Wno-deprecated-register -std=c++0x -o qucs.real main.o qucs_.o > ./.libs/libqucsschematic.a -lX11 -lQtScript -lQtSvg -lQtXml > -lQt3Support -lQtGui -lQtNetwork -lQtSql -lQtCore -ldl > /usr/bin/ld: cannot find -lX11 > > > Any ideas? > > > Rod > > > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Rod N. <rod...@gm...> - 2019-02-05 10:13:57
|
Hi all, I'm trying to compile qucs0.0.20 from source and I'm hitting an error: libtool: link: g++ -g -O2 -pipe -fno-exceptions -Wno-deprecated-register -std=c++0x -o qucs.real main.o qucs_.o ./.libs/libqucsschematic.a -lX11 -lQtScript -lQtSvg -lQtXml -lQt3Support -lQtGui -lQtNetwork -lQtSql -lQtCore -ldl /usr/bin/ld: cannot find -lX11 Any ideas? Rod |
From: Rod N. <rod...@gm...> - 2019-02-05 00:40:50
|
Good evening, I am trying to get digital simulation working with qucs in Linux Mint 19.1 Mate. I have tried all the available debs and then attempted to compile the latest versions. The compilation failed with errors that are above my ability to fix. Can anyone create the debs for these two components for 64 bit? Ref: Linux 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Thanks! |
From: Gregg N. <gre...@bl...> - 2019-01-29 11:05:51
|
It happens. -----Original Message----- From: Rod Naugler <rod...@gm...> Sent: Tuesday, January 29, 2019 5:18 AM To: Quc...@li... Subject: [Qucs-help] Digital Simulation Seg Fault Hi everyone, I've been using QUCS (and QUCS-S) for the past 4 years but I've never been able to get the digital simulation running. Now I have some time to work at it and I haven't found a solution. Running Linux Mint 19.1 Mate on a Core i7 processor. Qucs 0.0.18 installed from download and freevhdl installed from the software manager I have built the 'Getting started with digital simulation' circuit with the two sources and the AND gate. The output I get is: Output: ------- Starting new simulation on Tue 29. Jan 2019 at 06:07:05:402 creating netlist... done. running C++ conversion... Errors occurred during simulation on Tue 29. Jan 2019 at 06:07:05:588 Aborted. Errors: ------- Segmentation fault (core dumped) Any assistance is appreciated. Rod _______________________________________________ Qucs-help mailing list Quc...@li... https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Rod N. <rod...@gm...> - 2019-01-29 10:17:50
|
Hi everyone, I've been using QUCS (and QUCS-S) for the past 4 years but I've never been able to get the digital simulation running. Now I have some time to work at it and I haven't found a solution. Running Linux Mint 19.1 Mate on a Core i7 processor. Qucs 0.0.18 installed from download and freevhdl installed from the software manager I have built the 'Getting started with digital simulation' circuit with the two sources and the AND gate. The output I get is: Output: ------- Starting new simulation on Tue 29. Jan 2019 at 06:07:05:402 creating netlist... done. running C++ conversion... Errors occurred during simulation on Tue 29. Jan 2019 at 06:07:05:588 Aborted. Errors: ------- Segmentation fault (core dumped) Any assistance is appreciated. Rod |
From: andresmmera <and...@gm...> - 2019-01-22 17:58:39
|
Hi, The image file you mention is missing. Surely, it was filtered out by the mail server. Anyway, I suggest doing the fft postprocessing in Octave. Please find attached an Octave script (fft_test.m) for plotting the voltage spectrum. You may reduce the number of points of the simulation. Just ensure that fs >> fc/2. In order to run the script, go "File->Document Settings..." and tick the "run script after simulation" checkbox. Then press the "Simulate" button as usual. Finally, the following window should pop up: https://imagebin.ca/v/4UPbdQhQYyc0 Hope this helps, Andrés P.S.: I pasted the script here too (https://pastebin.com/Kn1N457Z) On 21/1/19 15:11, Malcolm Sparey via Qucs-help wrote: > To Qucs support > > I have just started using Qucs and have hit a problem with trying to > obtain > a meaningful result with the fft() function. I have attached my > fft_test.sch > file and an image of the plots obtained fft_test.jpg for your > information. > > Am I doing something wrong? > Is there a bug with the software? > > Best regards > mal...@ti... > > > > _______________________________________________ > Qucs-help mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Malcolm S. <mal...@bt...> - 2019-01-21 14:11:23
|
To Qucs support I have just started using Qucs and have hit a problem with trying to obtain a meaningful result with the fft() function. I have attached my fft_test.sch file and an image of the plots obtained fft_test.jpg for your information. Am I doing something wrong? Is there a bug with the software? Best regards mal...@ti... |
From: Juan L. P. <j.l...@lm...> - 2019-01-19 18:31:16
|
Thanks. The cursor keys will have to do for now. Juan From: Claudio Girardi [mailto:cla...@vi...] Sent: Saturday, January 19, 2019 2:00 AM To: quc...@li... Subject: RE: [Qucs-help] S-parameters with non 50 Ohm Z0 Hello, currently the markers can be moved only one frequency point at a time, using the cursor keys. Enhancements with delta markers are planned for the (far) future. Regards, Claudio Il 16 gennaio 2019 alle 23.27 "Juan Luglio, PhD" <j.l...@lm... <mailto:j.l...@lm...> > ha scritto: Thank you. That solves the issue. Is there an easy way to move the marker along the trace? Getting the marker to a desired frequency is challenging. Also is it possible to have the marker find max, min or 3dB points? Juan From: Claudio Girardi [mailto:cla...@vi...] Sent: Wednesday, January 16, 2019 1:43 PM To: quc...@li... <mailto:quc...@li...> Subject: Re: [Qucs-help] S-parameters with non 50 Ohm Z0 Hello, currently the marker does not know the reference impedance of the S-parameters on the plot and by default it assumes it's 50 ohm. You can change the reference impedance used by marker by double clicking on it (on its data "bubble"). Regards, Claudio Il 16 gennaio 2019 alle 19.37 "Juan Luglio, PhD" <j.l...@lm... <mailto:j.l...@lm...> > ha scritto: Hello, I am new to qucs. I down loaded Windows version 0.0.19 for the first time on Sunday. I think I have found a problem with the plotting of S-parameters when the Zo is not 50 Ohms. The problem is with reading Zin from the plot using a marker. A very simple test circuit shows the problem. I am attaching the project files. The circuit consists of a power source with Z set to anything other than 50, I used 75, and a load resistor. If the resistor is 75 Ohms S11 should be 0 (all real). The simulation produces a very small number,- 5.55e-17, which is good (small calculation in accuracy probably due to computer precision? But close enough). If the resistor is 50 Ohms S11 should be -0.2, exactly what the simulation produces. The problem comes when the data is displayed on a Smith chart and a marker is used to obtain Z11. The equation for Z11 is: Z11=Zo((1+S11)/(1-S11)) In the case of the resistor being 75 Ohm: Z11 = 75((1+0)/(1-0)) = 75 the marker shows Z11 =50 , it. When the resistor is 50 Ohm Z11 = 75((1+(-.2))/(1-(-0.2))) = 50 the marker shows Z11= 33.3. The problem is I can't find a place to set the characteristic impedance of the Smith Chart. It appears that the calculations are being done with Zo=50, not 75. For example when the resistor is 75 Ohms if 50 is used for Zo : Z11 = 50(1-0/1+0) = 50 This is the incorrect value displayed by the marker. When the resistor is 50 Ohms: Z11 = 50(1+(-0.20/1-(-0.2)) = 33.3 Again the incorrect value displayed by the marker. Am I missing something? Juan Luglio, PhD JRL Engineering, LLC (414)324-1050 _______________________________________________ Qucs-help mailing list Quc...@li... <mailto:Quc...@li...> https://lists.sourceforge.net/lists/listinfo/qucs-help |
From: Claudio G. <cla...@vi...> - 2019-01-19 07:59:47
|
Hello, currently the markers can be moved only one frequency point at a time, using the cursor keys. Enhancements with delta markers are planned for the (far) future. Regards, Claudio > Il 16 gennaio 2019 alle 23.27 "Juan Luglio, PhD" <j.l...@lm...> ha scritto: > > > Thank you. That solves the issue. > > > > Is there an easy way to move the marker along the trace? Getting the marker to a desired frequency is challenging. Also is it possible to have the marker find max, min or 3dB points? > > > > Juan > > > > From: Claudio Girardi [mailto:cla...@vi...] > Sent: Wednesday, January 16, 2019 1:43 PM > To: quc...@li... > Subject: Re: [Qucs-help] S-parameters with non 50 Ohm Z0 > > > > Hello, > > currently the marker does not know the reference impedance of the S-parameters on the plot and by default it assumes it's 50 ohm. You can change the reference impedance used by marker by double clicking on it (on its data "bubble"). > > > > Regards, > > Claudio > > > > > > > > Il 16 gennaio 2019 alle 19.37 "Juan Luglio, PhD" <j.l...@lm... mailto:j.l...@lm... > ha scritto: > > > > Hello, > > > > I am new to qucs. I down loaded Windows version 0.0.19 for the first time on > > Sunday. I think I have found a problem with the plotting of S-parameters > > when the Zo is not 50 Ohms. The problem is with reading Zin from the plot > > using a marker. A very simple test circuit shows the problem. I am attaching > > the project files. > > > > The circuit consists of a power source with Z set to anything other than 50, > > I used 75, and a load resistor. If the resistor is 75 Ohms S11 should be 0 > > (all real). The simulation produces a very small number,- 5.55e-17, which is > > good (small calculation in accuracy probably due to computer precision? But > > close enough). If the resistor is 50 Ohms S11 should be -0.2, exactly what > > the simulation produces. > > > > The problem comes when the data is displayed on a Smith chart and a marker > > is used to obtain Z11. The equation for Z11 is: > > > > Z11=Zo((1+S11)/(1-S11)) > > > > In the case of the resistor being 75 Ohm: > > > > Z11 = 75((1+0)/(1-0)) = 75 > > > > the marker shows Z11 =50 , it. When the resistor is 50 Ohm > > > > Z11 = 75((1+(-.2))/(1-(-0.2))) = 50 > > > > the marker shows Z11= 33.3. The problem is I can't find a place to set the > > characteristic impedance of the Smith Chart. It appears that the > > calculations are being done with Zo=50, not 75. For example when the > > resistor is 75 Ohms if 50 is used for Zo : > > > > Z11 = 50(1-0/1+0) = 50 > > > > This is the incorrect value displayed by the marker. When the resistor is 50 > > Ohms: > > > > Z11 = 50(1+(-0.20/1-(-0.2)) = 33.3 > > > > Again the incorrect value displayed by the marker. > > > > Am I missing something? > > > > Juan Luglio, PhD > > > > JRL Engineering, LLC > > > > (414)324-1050 > > > > _______________________________________________ > > Qucs-help mailing list > > Quc...@li... mailto:Quc...@li... > > https://lists.sourceforge.net/lists/listinfo/qucs-help > > > > > |
From: Juan L. P. <j.l...@lm...> - 2019-01-16 22:27:35
|
Thank you. That solves the issue. Is there an easy way to move the marker along the trace? Getting the marker to a desired frequency is challenging. Also is it possible to have the marker find max, min or 3dB points? Juan From: Claudio Girardi [mailto:cla...@vi...] Sent: Wednesday, January 16, 2019 1:43 PM To: quc...@li... Subject: Re: [Qucs-help] S-parameters with non 50 Ohm Z0 Hello, currently the marker does not know the reference impedance of the S-parameters on the plot and by default it assumes it's 50 ohm. You can change the reference impedance used by marker by double clicking on it (on its data "bubble"). Regards, Claudio Il 16 gennaio 2019 alle 19.37 "Juan Luglio, PhD" <j.l...@lm... <mailto:j.l...@lm...> > ha scritto: Hello, I am new to qucs. I down loaded Windows version 0.0.19 for the first time on Sunday. I think I have found a problem with the plotting of S-parameters when the Zo is not 50 Ohms. The problem is with reading Zin from the plot using a marker. A very simple test circuit shows the problem. I am attaching the project files. The circuit consists of a power source with Z set to anything other than 50, I used 75, and a load resistor. If the resistor is 75 Ohms S11 should be 0 (all real). The simulation produces a very small number,- 5.55e-17, which is good (small calculation in accuracy probably due to computer precision? But close enough). If the resistor is 50 Ohms S11 should be -0.2, exactly what the simulation produces. The problem comes when the data is displayed on a Smith chart and a marker is used to obtain Z11. The equation for Z11 is: Z11=Zo((1+S11)/(1-S11)) In the case of the resistor being 75 Ohm: Z11 = 75((1+0)/(1-0)) = 75 the marker shows Z11 =50 , it. When the resistor is 50 Ohm Z11 = 75((1+(-.2))/(1-(-0.2))) = 50 the marker shows Z11= 33.3. The problem is I can't find a place to set the characteristic impedance of the Smith Chart. It appears that the calculations are being done with Zo=50, not 75. For example when the resistor is 75 Ohms if 50 is used for Zo : Z11 = 50(1-0/1+0) = 50 This is the incorrect value displayed by the marker. When the resistor is 50 Ohms: Z11 = 50(1+(-0.20/1-(-0.2)) = 33.3 Again the incorrect value displayed by the marker. Am I missing something? Juan Luglio, PhD JRL Engineering, LLC (414)324-1050 _______________________________________________ Qucs-help mailing list Quc...@li... <mailto:Quc...@li...> https://lists.sourceforge.net/lists/listinfo/qucs-help |