qucs-devel — Development related topics. Please subscribe before posting.

[Qucs-devel] Federated Simulation

[Kevin C. <cam...@gm...>]

There are a bunch of problems with current simulators and languages, 
here's some fixes I proposed for SystemVerilog -

https://docs.google.com/document/d/1PYPo_ZAiOtVXl53TDIBxyPwWoXFiwSpSYHCl3LPexXU/edit?usp=sharing

- they could be equally well applied to VHDL.

Since enthusiasm for fixing HDLs seems to be zero (none of that was 
adopted), my current tack is to fix things in a "federation" layer that 
acts as glue between multiple simulators -

20240206_PreConG_Cameron.PDF 
<https://chipletsummit.com/proceeding_files/a0q5f0000044zma/20240206_PreConG_Cameron.PDF>

If anyone on this reflector wants to get involved, do get in touch.

Example of something to add through federation -

peaclab/PACT: PACT: A Parallel Compact Thermal Simulator 
<https://github.com/peaclab/PACT>

Regards,
Kev.
https://www.linkedin.com/in/kevcameron/

[Qucs-devel] Another Qucs roadmap and call for collaboration update

[Felix S. <fe...@sa...>]

On Tue, Jan 07, 2025 at 12:15:11AM +0100, Felix Salfelder wrote:
> [..]
> The schematic file format upgrade is now ongoing. The next iteration
> will address the transfer of circuit models to related tools not under
> our control.

Hello all.

We have another request for help with standardisation somehow related to
Qucs.

Qucs is now able to dump circuits into a vendor independent format for
any purpose and use, specifically outside of Qucs. To harvest the
benefits from within Qucs, some streamlining is due. For example,
Gnucsator demonstrates the implementation of some device models, yet the
integration into Qucs still uses the arcane and fragile netlister.

With schematics and the devices represented in a neutral and unambiguous
format, circuits will no longer be tied to processing with Qucs. Such
circuits can either be shared amongst other compliant editors, analysed
by a compliant tool, or mangled (in a way not specific to Qucs) for use
in traditional tools.

Hence we need to update Qucs to allow for a painless user defined and
more versatile component/symbol representation. For this, we will
further follow the Verilog standard(s), which define(s) the mapping from
a device instance to a symbol drawing or model implementation.

Towards this goal, the component library format needs an upgrade to a
Verilog based format, adding established standard support for named
ports, parameter ranges, hierarchical system parameters, output
variables, attributes and others. As previously for the schematic
format, and thanks to NLnet, we offer a sort-of internship style
position for this task.

The bulk of this work only requires some C++ and Qt knowledge paired
with the willingness to learn concepts new to you.

Best wishes
felix

[Qucs-devel] Qucs roadmap and call for collaboration, update

[Felix S. <fe...@sa...>]

On Wed, Oct 02, 2024 at 05:43:13PM +0200, Felix Salfelder wrote:
> This is a reminder that we are looking for help [..]

Finally, this seems to be happening.

David has joined us and is picking up speed. His first patches fix
issues with connectivity in the netlist generation. This somehow
concludes the transition to a native Qt5 graphics scene.

Feature-wise, the schematic editor is now on par with what should have
been in Qucs 0.0.20. But with effective tests, we are now set to
refactor further.

The schematic file format upgrade is now ongoing. The next iteration
will address the transfer of circuit models to related tools not under
our control.

Best wishes
felix

Re: [Qucs-devel] Qucs roadmap and call for collaboration, reminder

[Felix S. <fe...@sa...>]

On Wed, Oct 02, 2024 at 10:36:11AM -0700, Kevin Cameron wrote:
> Key to making Verilog-AMS work was the connect-module methodology, but
> Cadence broke it in implementation, and it has never been fixed. However,
> it was also limited to Verilog-A nets and 4-state logic.
> 
> Similarly SystemVerilog (30+ years on) brought in user-defined
> nettypes (UDNs) to match VHDL's capabilities, but like VHDL failed to
> support multi-type resolution or bidirectional components.

Dear Kevin.

Thanks for your input.

Our projects, both Qucs and Gnucap are centered around Free Software.
Whatever commercial tools can do since 1980 is of little relevance for
us. We aim to provide a reference implementation as a starting point.
For sure we will not impose restrictions on what you might do with it.

> [..]
> So if anyone wants to solve some of the problems that have lingered in HDLs
> since the 1980s, I'm happy to team up on doing it as a federation layer
> with existing simulators.

I can sense the confusion about modelling language semantics and generic
simulator capabilities. Any modular simulator provides a federation
layer, when used as such. The essence of it is an algorithm that has
been intended in Gnucap for a long time. We are now getting there, since
funding for it has been made available (mostly thanks to NLnet).

Qucs is meant to serve schematic entry and GUI purposes. Please use the
gnucap-devel mailing list to discuss those simulator related topics.

Best regards
Felix

Re: [Qucs-devel] Qucs roadmap and call for collaboration, reminder

[Kevin C. <cam...@gm...>]

Key to making Verilog-AMS work was the connect-module methodology, but
Cadence broke it in implementation, and it has never been fixed. However,
it was also limited to Verilog-A nets and 4-state logic.

Similarly SystemVerilog (30+ years on) brought in user-defined
nettypes (UDNs) to match VHDL's capabilities, but like VHDL failed to
support multi-type resolution or bidirectional components.

I proposed some fixes for SV last year, but no proposals were accepted for
the UDN problems -


https://docs.google.com/document/d/1PYPo_ZAiOtVXl53TDIBxyPwWoXFiwSpSYHCl3LPexXU/edit?usp=sharing

I would recommend Xyce over Gnucap, but you can make a PWL API work in any
analog simulator. I did it for Gnucap, but the code didn't stick there
either.

  https://cameron-eda.com/2020/06/03/rolling-your-own-ams-simulator/

At this point, if you are interested in multi-abstraction simulation
(logic, power, RF, photonics...) I suggest going down the "federated
simulation" road, which is being investigated at Accellera -


https://www.accellera.org/news/press-releases/398-accellera-announces-formation-of-the-federated-simulation-standard-working-group

- although I don't trust Accellera to do a good job, or anything
open-source.

So if anyone wants to solve some of the problems that have lingered in HDLs
since the 1980s, I'm happy to team up on doing it as a federation layer
with existing simulators.

BTW, I own this (Verilog-AMS) modeling technique that is the only way to
catch CDC bugs in functional simulation -

   http://www.v-ms.com/ICCAD-2014.pdf

I'm happy to license it to anyone with an open-source simulator that wants
to make money out of their efforts, anyone working on SERDES hardware
should be interested.

Regards,
Kev.



On Wed, Oct 2, 2024 at 8:43 AM Felix Salfelder <fe...@sa...> wrote:

> Dear All,
>
> We made significant progress on the simulator and model compiler [1].
> Some of the traditional Qucs/Qucsator devices have been ported to
> Verilog-A, with others to come, as time permits (It's actually fun, but
> we have promises to keep [2].)
>
> In particular, we now expose standardised event driven analog modelling
> and true mixed simulation to the users, opening an unseen range of
> possibilities and applications.
>
> This is a reminder that we are looking for help, just not exclusively
> with Qucs, see [2].
>
> Best wishes
>
> [1] https://lists.gnu.org/archive/html/gnucap-devel/2024-10/msg00000.html
> [2] https://nlnet.nl/project/Gnucap-MixedSignals/
> [3] https://sourceforge.net/p/qucs/mailman/message/58796863/
>
>
> _______________________________________________
> Qucs-devel mailing list
> Quc...@li...
> https://lists.sourceforge.net/lists/listinfo/qucs-devel
>

[Qucs-devel] Qucs roadmap and call for collaboration, reminder

[Felix S. <fe...@sa...>]

Dear All,

We made significant progress on the simulator and model compiler [1].
Some of the traditional Qucs/Qucsator devices have been ported to
Verilog-A, with others to come, as time permits (It's actually fun, but
we have promises to keep [2].)

In particular, we now expose standardised event driven analog modelling
and true mixed simulation to the users, opening an unseen range of
possibilities and applications.

This is a reminder that we are looking for help, just not exclusively
with Qucs, see [2].

Best wishes

[1] https://lists.gnu.org/archive/html/gnucap-devel/2024-10/msg00000.html
[2] https://nlnet.nl/project/Gnucap-MixedSignals/
[3] https://sourceforge.net/p/qucs/mailman/message/58796863/

[Qucs-devel] Qucs-S 24.3.2 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developer,

The Qucs-S v24.3.2 has been released. This version contains no new 
features, only fixed a critical bug: 
https://github.com/ra3xdh/qucs_s/issues/948

The release page is available here: 
https://github.com/ra3xdh/qucs_s/releases/tag/24.3.2
Installation instructions: 
https://github.com/ra3xdh/qucs_s/wiki/Installation

Regards,
Vadim Kuznetsov

[Qucs-devel] Qucs-S 24.3.1 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developer,

The Qucs-S v24.3.1 has been released. This version contains no new 
features, only bugfixes and small improvements. Fixed some critical bugs 
in plotting subsystem. The release packages has been built automatically 
using Github CI actions.

See the release notes and download links here: 
https://github.com/ra3xdh/qucs_s/releases/tag/24.3.1
The discussion page is here: 
https://github.com/ra3xdh/qucs_s/discussions/937
Installation instructions: 
https://github.com/ra3xdh/qucs_s/wiki/Installation

Regards,
Vadim Kuznetsov

[Qucs-devel] Qucs-S v24.3.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v21.3.0 release. The packages and 
installation instructions could be found at the release page: 
https://github.com/ra3xdh/qucs_s/releases/tag/24.3.0

This release contains a number of important improvements. Here are the 
main features added in v24.3.0:

* SpiceLibComp redesign. This device is renamed to /Spice Library 
Device/ and provides an easy way
to add SPICE model to schematic and assign symbol to it.
* Added possibity to import SPICE model for Diode, BJT, MOSFET, and JFET 
unified devices using special button in component properties
* Implemented symbol files editing
* Redesign of schematic rendering engine. Improve rendering quality on 
HiDPI displays
* Improved Qucsconv GUI to reflect new converter features
* Fixed ASCO operation using QucsatorRF
* QucsatorRF updated to version 1.0.1 This update mainly related to file 
formats comverter See 
https://github.com/ra3xdh/qucsator_rf/releases/tag/v1.0.1 for release notes
* Linux and WIndows binary packages switched to Qt6
* Implemented MacOS installation support using homebrew
* Introduced continuous releases

The full changelog could be found at the release page: 
https://github.com/ra3xdh/qucs_s/releases/tag/24.3.0 The Qucs-S package 
is not related to the recent revival of the old Qucs development.

Regards,
Vadim Kuznetsov

Re: [Qucs-devel] Qucs roadmap and call for collaboration

[Kevin C. <cam...@gm...>]

Another topic, if anyone is interested:

I'm looking at developing a (C++) "federated simulation" layer for 
plugging multiple simulators together to tackle things like Chiplet 
system design.

The federation-layer will tackle some of the parallel-processing and 
mixed-signal problems that folks have failed to address in VHDL, 
SystemVerilog, and Verilog-AMS over the last 30+ years.

Regards,
Kev.
https://www.linkedin.com/in/kevcameron/

PS: there is an on-going effort at Accellera on this topic, but it's 
pay-to-play.

On 7/16/2024 4:24 AM, Felix Salfelder wrote:
> Dear all.
>
> Qucs has been recently ported to Qt5 after a long silence, enabling us
> to move on with topics related to contemporary circuit modelling and
> simulation in FOSS tools. The code is currently on github [1] (sorry),
> but we welcome testing and bug fixing.
>
> Meanwhile, our standardised data format for schematic interchange is
> taking shape [2]. It is not yet-another-one but based on a widely used
> and open industry standard. This format will enable us to overcome
> vendor lock-in by means of an unambiguous representation of
> digital/analog/mixed-signal circuit models, netlists, schematics, and
> layout. The bits relevant for use in the Qucs schematic editor are in
> place. See [3] for a roadmap.
>
> We are offering guidance for a developper to implement the data format,
> in Qucs or elsewhere. Funding for an intern within the range of a
> student summer project compensation will be feasible thanks to NLnet [4]
> and enabled by ongoing work on Verilog-AMS in Gnucap [5].
>
> Eligibility for funding is not tied to institutional relations, and
> there is some flexibility wrt. country of residence. To collaborate with
> us or apply for a project, simply get in touch. I will follow-up on this
> list, as things evolve.
>
> Please share this post with potentially interested parties.
>
> Best wishes
> Felix
>
> [1] https://github.com/Qucs/qucs
> [2] http://gnucap.org/dokuwiki/doku.php/gnucap:user:netlist_import_and_export
> [3] https://github.com/Qucs/qucs/blob/develop/ROADMAP
> [4] https://nlnet.nl/
> [5] https://nlnet.nl/project/Gnucap-MixedSignals/
>
>
> _______________________________________________
> Qucs-devel mailing list
> Quc...@li...
> https://lists.sourceforge.net/lists/listinfo/qucs-devel

[Qucs-devel] Qucs roadmap and call for collaboration

[Felix S. <fe...@sa...>]

Dear all.

Qucs has been recently ported to Qt5 after a long silence, enabling us
to move on with topics related to contemporary circuit modelling and
simulation in FOSS tools. The code is currently on github [1] (sorry),
but we welcome testing and bug fixing.

Meanwhile, our standardised data format for schematic interchange is
taking shape [2]. It is not yet-another-one but based on a widely used
and open industry standard. This format will enable us to overcome
vendor lock-in by means of an unambiguous representation of
digital/analog/mixed-signal circuit models, netlists, schematics, and
layout. The bits relevant for use in the Qucs schematic editor are in
place. See [3] for a roadmap.

We are offering guidance for a developper to implement the data format,
in Qucs or elsewhere. Funding for an intern within the range of a
student summer project compensation will be feasible thanks to NLnet [4]
and enabled by ongoing work on Verilog-AMS in Gnucap [5].

Eligibility for funding is not tied to institutional relations, and
there is some flexibility wrt. country of residence. To collaborate with
us or apply for a project, simply get in touch. I will follow-up on this
list, as things evolve.

Please share this post with potentially interested parties.

Best wishes
Felix

[1] https://github.com/Qucs/qucs
[2] http://gnucap.org/dokuwiki/doku.php/gnucap:user:netlist_import_and_export
[3] https://github.com/Qucs/qucs/blob/develop/ROADMAP
[4] https://nlnet.nl/
[5] https://nlnet.nl/project/Gnucap-MixedSignals/

Re: [Qucs-devel] Qucs-S 24.2.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I have recently prepared Qucs-S v24.2.1 hotfix release. This release 
contains no new features except the fix for the critical bug with DC 
bias simulation and the fix of Fedora RPM package build failure. See the 
release notes: https://github.com/ra3xdh/qucs_s/releases/tag/24.2.1

Regards,
Vadim Kuznetsov

On 25.03.24 21:55, Vadim Kuznetsov wrote:
> Hello Qucs and Ngspice developers,
>
> I am glad to present a new Qucs-S v24.2.0 release. The packages and 
> installation instructions could be found at the release page: 
> https://github.com/ra3xdh/qucs_s/releases/tag/24.2.0
>
> This release contains a number of important improvements. Here are the 
> main features added in v24.2.0:
>
> * QucsatorRF is now a part of the package; no need to compile and 
> install qucsator manually;
> * Qucs-RFLayout tool could be launched from Tools menu; this tool must 
> be installed separately. Refer to 
> https://github.com/thomaslepoix/Qucs-RFlayout
> * Redesign of the Qucsconv GUI
> * Matching tool backported from unreleased Qucs-0.0.20
> * Added RF devices group; backported different RF devices for Qucsator
>
> The full changelog could be found at the release page.
>
> Regards,
> Vadim Kuznetsov

[Qucs-devel] Qucs-S 24.2.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v24.2.0 release. The packages and 
installation instructions could be found at the release page: 
https://github.com/ra3xdh/qucs_s/releases/tag/24.2.0

This release contains a number of important improvements. Here are the 
main features added in v24.2.0:

* QucsatorRF is now a part of the package; no need to compile and 
install qucsator manually;
* Qucs-RFLayout tool could be launched from Tools menu; this tool must 
be installed separately. Refer to 
https://github.com/thomaslepoix/Qucs-RFlayout
* Redesign of the Qucsconv GUI
* Matching tool backported from unreleased Qucs-0.0.20
* Added RF devices group; backported different RF devices for Qucsator

The full changelog could be found at the release page.

Regards,
Vadim Kuznetsov

[Qucs-devel] Qucs-S 24.1.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v21.1.0 release. The packages and 
installation instructions could be found at the release page: 
https://github.com/ra3xdh/qucs_s/releases/tag/24.1.0

This release contains a number of important improvements. Here are the 
main features added in v24.1.0:

* Ngspice simulation support rework
* Added new devices
* Massive update of the libraries; added analog ICs libraries
* Added new RF features including RLCG support for SPICE
* Many HiDPI displays support improvements

The full changelog could be found at the release page.

Regards,
Vadim Kuznetsov

[Qucs-devel] Federated Simulation

[Kevin C. <cam...@gm...>]

Just FYI -

https://www.accellera.org/news/press-releases/382-accellera-announces-proposed-working-group-to-explore-federated-simulation-standard

If anyone is interested in making a highly parallel multi-domain simulation
system using open source simulators, let me know.

Regards,
Kev.

[Qucs-devel] Qucs-S 2.1.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v2.0.0 release. The packages and 
installation instructions could be found at the release page: 
https://github.com/ra3xdh/qucs_s/releases/tag/2.1.0

This release contains a number of important improvements. Here are the 
main features added in v2.1.0:

* Added tuner simulation mode (used implementation by Kevin Voet)
* Added support for touchstone s2p file devices for Ngspice 
(implementation by Dan Dickey and Jim Mittel)
* Diagrams are placed on schematic and *.dpl files are disabled by default
* Toolbar icons replaced by SVG images; improved look for HiDPI
* Implemented automatic generation of high resolution device icons for 
the left panel

The full changelog could be found at the release page.

Regards,
Vadim Kuznetsov

[Qucs-devel] Qucs-S 2.0.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v2.0.0 release. The packages and 
installation instructions could be found at the release page: 
https://github.com/ra3xdh/qucs_s/releases/tag/2.0.0

This release contains an important change of the simulator switching 
system. The switching of the simulation kernel without restart of the 
application is possible now. See the release notes and documentation for 
more details.

[Qucs-devel] Qucs-S 1.1.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v1.1.0 release. The packages and 
installation instructions could be found at the release page 
https://github.com/ra3xdh/qucs_s/releases/tag/1.1.0

Here is the summary of changes:

    * Qucs-S supports digital simulation mode using IcarusVerilog or 
FreeHDL backends
    * Qucs-S runs DC bias simulation mode if schematic contains DC 
simulation only
    * Selection rectangle update

[Qucs-devel] Qucs-S v1.0.2 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v1.0.2 release. The packages and 
installation instructions could be found at the release page 
https://github.com/ra3xdh/qucs_s/releases/tag/1.0.2  Here is the summary 
of the new features:


     * Added XSPICE flip-flop digital devices
     * Added INDQ and CAPQ devices representing inductor and capacitor 
with Q-factor
     * Added .LIB directive support
     * Added SPICE entries for I and V file sources
     * Added symbols for 4 and 5 terminal BJT device
     * Improved Qt6 and MacOS compatibility


Regards,
Vadim Kuznetsov

[Qucs-devel] default branch in github repo

[Felix S. <fe...@sa...>]

Hi All.

Downstream seems to be stuck with packaging working development
versions, see e.g. [1]. I suggest to rearrange the repository a bit.

The "develop" branch points to the old and unmaintained combined qucs
package, that nobody seems able to build or use. It is the default
branch on github, and feeds into the otherwise useless (?) "qucs-git"
package.

As stated on the AUR packaging board [2] I can think of two ways
forward.  I'd like to simply archive "develop" and rename the
"develop_filtered" branch to "develop", to get out of this.

Please let me know if you are against this change.

NB: Fortunately (or coincidentally) the Qucs-S project shares the
history with the "develop_filtered" branch. Modular Qucs does too (or
should).

NB2: Metapackage advocates are advised to use (i.e. shape up) the
qucs-pkg repo. Others should use individual packages.

Best wishes
felix


[1] https://aur.archlinux.org/packages/qucs-git
[2] https://aur.archlinux.org/packages/qucs

[Qucs-devel] Qucs-S 1.0.1 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v1.0.0 release. The packages and 
installation instructions could be found at the release page 
https://github.com/ra3xdh/qucs_s/releases/tag/1.0.1 Here is the summary 
of the new features:


   * Added support for Verilog-A defined devices using Ngspice+OpenVAF. 
Old Qucsator+ADMS
     workflow is marked as deprecated. Ngspice >=39 is required to 
support OpenVAF.
   * Implemented sweeping of variables with parameter sweep using Ngspice
   * Added possibility to build Qucs-S with Qt6 The -DWITH=QT6=ON option 
for cmake is required.
     The source code of the Qucs-S is Qt6 compatible now.
   * Simulator prefixes like "ngspice/" are not show anymore on plot 
traces if the plot contains data
     from only one simulator
   * Added TL071/TL072 opamp models
   * Added 555_timer.lib library containing the 555 timer model
   * Added extended BJT and Schottky diodes libraries

Regards,
Vadim Kuznetsov

[Qucs-devel] Fwd: some fun with "spice models" .... 1N4004 vs 1N4007

[Felix S. <fe...@sa...>]

Hi there.

Al asked me to forward some fun with diodes, see below. The original
message can be found here [1]. For non-subscribers, the thread will
continue here [2] (happy new year!).

Cheers
felix

[1] https://lists.gnu.org/archive/html/gnucap-devel/2022-12/msg00002.html
[2] https://lists.gnu.org/archive/html/gnucap-devel/2023-01/index.html

== below
On Sat, Dec 31, 2022 at 06:43:04PM -0500, al davis via Gnucap-devel wrote:

It's on topic because these things are used by Gnucap too, with exactly
the same meaning.  (and issues)

Here's a couple of links:
https://www.el-component.com/diodes/1n4004
https://www.el-component.com/diodes/1n4007

For a fun exercise, compare them.  Try to explain the differences.

Felix .. please repost this to the Qucs help list in hopes that our
LTspice loving friend sees it.

These spice syntax models are intended for use with all Spice-syntax
simulators, including Gnucap, NGspice, LTspice, Smartspice, Hspice, and
a bunch of others.  You should get the same results on all of them.
(within appropriate tolerances)

So this is intended as "food for thought".  Can you explain the
differences between these models?  Do you know what the real difference
between a 1N4004 diode and a 1N4007 diode is?

I will sit quiet on this for a few days to give people some time to
think about it.

[Qucs-devel] AMS / mixed types on wires

[Kevin C. <cam...@gm...>]

For anyone interested in adding mixed types on wires to VHDL/SV or
co-simulation, here's a proposal I have for IEEE P1800 -

https://docs.google.com/document/d/1PYPo_ZAiOtVXl53TDIBxyPwWoXFiwSpSYHCl3LPexXU/edit?usp=drivesdk

One of the drivers for this is bridging SystemC-AMS and SV, but given the
low probability of success at P1800, maybe the SC-AMS guys can be steered
to QUCS.

Kev.

On Sun, Oct 30, 2022, 3:40 PM Vadim Kuznetsov <ra...@gm...> wrote:

> Hello Qucs and Ngspice developers,
>
> I am glad to present a new Qucs-S v1.0.0 release. The packages and
> installation instructions could be found at the release page
> https://github.com/ra3xdh/qucs_s/releases/tag/1.0.0 Here is the summary
> of the new features:
>
>
> * Added basic support for logic gates simulation (Ngspice >= 38) required
> * Added possibility to set engineering notation (like 1k, 1M, etc.) for
> numbers on diagrams
> * Added symbol preview and search feature for component library in main
> windows
> * Backported qucs-attenuator, qucs-transcalc and qucs-powercombining
> from Qucs-0.0.20
> * Added possibility to set dB units for Y-axis on diagrams from the
> diagram properties dialog
> * Backported advanced features for projects tree from Qucs-0.0.20
> * Show warning if schematic file name changed, but dataset/display file
> name are not updated
> * Revised examples tree (by Tom Hajjar); legacy Ngspice-incompatible
> examples
>    moved to examples/qucsator subdirectory
>
> Regards,
> Vadim Kuznetsov
>
>
> _______________________________________________
> Qucs-devel mailing list
> Quc...@li...
> https://lists.sourceforge.net/lists/listinfo/qucs-devel
>

[Qucs-devel] Qucs-S 1.0.0 release

[Vadim K. <ra...@gm...>]

Hello Qucs and Ngspice developers,

I am glad to present a new Qucs-S v1.0.0 release. The packages and 
installation instructions could be found at the release page 
https://github.com/ra3xdh/qucs_s/releases/tag/1.0.0 Here is the summary 
of the new features:


* Added basic support for logic gates simulation (Ngspice >= 38) required
* Added possibility to set engineering notation (like 1k, 1M, etc.) for 
numbers on diagrams
* Added symbol preview and search feature for component library in main 
windows
* Backported qucs-attenuator, qucs-transcalc and qucs-powercombining 
from Qucs-0.0.20
* Added possibility to set dB units for Y-axis on diagrams from the 
diagram properties dialog
* Backported advanced features for projects tree from Qucs-0.0.20
* Show warning if schematic file name changed, but dataset/display file 
name are not updated
* Revised examples tree (by Tom Hajjar); legacy Ngspice-incompatible 
examples
   moved to examples/qucsator subdirectory

Regards,
Vadim Kuznetsov

Re: [Qucs-devel] requesting info on QUCS usage for Industrial application

[Tiwari, S. <Shu...@ta...>]

Hello Vadim,
Many thanks for your speedy response..

DE VU3SXN / KC3CWD.

BR
Shubham
________________________________
From: Vadim Kuznetsov <ra...@gm...>
Sent: Saturday, August 27, 2022 11:40:59 PM
To: Tiwari, Shubham <Shu...@ta...>
Cc: quc...@li... <quc...@li...>; quc...@li... <quc...@li...>
Subject: Re: [Qucs-devel] requesting info on QUCS usage for Industrial application

IMPORTANT: This message originated from outside TATA TECHNOLOGIES. Please use caution when opening attachments or following links. Do NOT enter your TTL credentials when prompted by external links.
Hello Shubham,

> Is the software completely free to use as we like or we need to get some approval and Licencing ?

Qucs is licensed under GPL that allows to use software in business processes for any purpose without notification of the developer. So you may use Qucs inside your organization free of charge. Only restriction is not to distribute software products derived from Qucs sources under other license. It implies when you modify Qucs sources itself. See also https://en.wikipedia.org/wiki/GNU_General_Public_License<https://secure-web.cisco.com/1kxV6tVO34MXTeTaedjtd84o0gFMhFRKhJw2yQL_e3iMUd3l01UPdQb8e0oBOlK5IIlCJCcdNKcIG40klQxPXAgyhTkzBUda4jnDXkqEaNXFiRsScO2E6UdCK7sffMferLHxsEelTqAmAoNgWIjjwW5NVLD8m3MJxuLrTFszMYs04xQ83yTJ3wnsXMQGX2lPSUjSrbvQynKmpQklpGzQjO_7ci0sHRp_30O3JsUt7eIYfdiV0wxOrx_F0abjNRrhIcXXvY3yT7ROwQGKHxp53STfS2pKDDlx7WleFUFhFNoMs7T5tc5jqul9CK7CDLMAXRHCT2-I9ZnoGwY6dxxx73BK2rS6AAxjDHxY1CxetxPFXxQwjFou1ovqwjC-BH-luM2wMBZi_dgAfO5giF4V6SG7fPv8rXIi6tcYJJGpyjNfO-d-9AWs0gy7uqWh2JF1RjRMIzC5OE5jmoANS8PGuZ9Pl8xZfbTfDf9JjCtH--tg/https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FGNU_General_Public_License>

> Can I use your software QUCS for making Spice simulations for projects that I am working on?

Qucs is not a good choice for SPICE simulation. Qucs is based on its own simulation kernel which is SPICE-incompatible and uses another netlist syntax. Also Qucs still be based on Qt4 toolkit that is EOL in 2015. It may cause problems on modern OS. If you need SPICE simulation look at  Qucs-S https://ra3xdh.github.io/<https://secure-web.cisco.com/1eHZhHrBWAvOjgiG0lYv-uriQkywPZu0GgLYAyNxrQ55wUupr1ZDtw9sEHRnX1JiB9QHa3fRbzeVgqZqERvMnwWv9MJKKENJ_gExCI432gsrf5ob7ZwSCrw0FTzlj-j7g8MST3wXFGgO2E98TbUyT7vFwjCk7Ja2QcJVuXHuP7CyKoI6_HSwWSqNIn4lBJyCWfo_vUnT_oIX43lPxarMkR9XdUmJmeCDSh8QeYGGNTnFnppb7OuhRiAB0ek97gDmeh6bATB9sUSKSfbqdxmfXER2VfLFpKc78JWwgwJR2qTzRoCJ-MHitJtDoedfUQUNyB77H99B17iD219qEOo4Sw4q_22m8GN5JjEXLfqEMVoCHZLgfkW2nb86m1ITCes2KW5Eo45AL3fi85K8uNbGRNzoLrkDkQKAVAzpkAuZYAtg2bngCdOK6XCFEqb_z3cORLOqheVPZpiw8piuwdyNmWz34fThMJHJxsIbqAb1ngAE/https%3A%2F%2Fra3xdh.github.io%2F> with Ngspice simulation kernel that is SPICE compatible. Qucs-S is fully ported to Qt5 toolkit and available for modern platforms.

Regards,
Vadim



сб, 27 авг. 2022 г. в 09:14, Tiwari, Shubham via Qucs-devel <quc...@li...<mailto:quc...@li...>>:
Hello Qucs team,

Small query to you all,
I am working as an electronics integration engineer in company called TATA Technologies Ltd.

Can I use your software QUCS for making Spice simulations for projects that I am working on?
Is the software completely free to use as we like or we need to get some approval and Licencing ?


Sincerely
Shubham Tiwari
Technical lead
TATA Technologies.Ltd
https://www.tatatechnologies.com/in/<https://secure-web.cisco.com/1vrZB_yOdxsPLwzimjPq1Augxoi0gFp_20wvef60QMrb4XVu6Whx23bGpiIHjr5Bi7gP9lXaLPReGwlaJdTqK31DI7krl5Lrb6qfxgzxOzHfCFTPVHGmJ97aDw3ZXhcxH4I5hpoNMfoND3OZT7D7cszwFcxil5KmemW1Zg2DLvYSf-LqSEUs-qnhpcJbe3rn2Gts1zzo9bgmbvhSyVOl-msRs-gFjFj6z7fx_PjGS9UdwQ5UFxgQ2fQsV4VswibsxP_VGg_tJXtznJyCfX4f3vfcVZMy6K3UOhjHkrPCgZhcC2IkAxLwbAtGAqde7FMfrRs40HfTaqdvxfXrtYDS7tWLbaOXJiZ33on0yRSDBAYlErsQ_ritk1k5w5JSuGlhJZlQSfd_9noKsQGBdfG0qs4tI55_UmQoZQ2G_nsEUs-HQ7gmDiLVXn_KMLposDPeNVU66j7_1Z0YXb4LcT1YSlKRneWdLBv2IMvUJNqH8y-M/https%3A%2F%2Fwww.tatatechnologies.com%2Fin%2F>



********************************************************************************************************************************************
Email Disclaimer: The contents of this e-mail and any attachment(s) may contain confidential or privileged information for the intended recipient(s). Unintended recipients are prohibited from taking action on the basis of information in this e-mail and using or disseminating the information, and must notify the sender and delete it from their system. Tata Technologies will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in this e-mail.
***********************************************************************************************************************************************

_______________________________________________
Qucs-devel mailing list
Quc...@li...<mailto:Quc...@li...>
https://lists.sourceforge.net/lists/listinfo/qucs-devel<https://secure-web.cisco.com/1zgKpQvQfq65g4Y5WTIiSTdbpy3qtUAPp4zKVvD-M8jhgJuC8uZ-B-6odCuwS7dyB3dXI_jaYbcXp3wIM5wmDpffY1pjxBukq7PH7EfjENmN1kMK1m0q6YsKvldlEjSDrdFjczHps3obQcgS_KwyBdTW5CGTdS6pgX4g1xAdjAivFFhdI7_1yFZVFzQVmj_2j6fJA7xJEolQpJoPMfnvSNgas9AN4hg3TFYO55DrJQtfRWVMN_zuxG9z5_0-Wa0mUf747iZnvWU80E7gIWGtKOOaIFRA1FUXeL8qwfDAnb2epjW6r_c76j30tT79DkLHa_DhlfCoEcZPyOeHmVI2S9zXAeY1aBWNxZmgAZTolZo5IF2FO6qqs4Ji6BEi_Dp6HoFAJdFaxMeN0_n2iedX98LUiS9y-iDbPkOd2lNGsb4AEtvv1-5fAFD0FcjIwYl3g504Zq0YLdm2qeJwaIHkTGoOfuZkiPEudUw-97xqAW88/https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fqucs-devel>

********************************************************************************************************************************************
Email Disclaimer: The contents of this e-mail and any attachment(s) may contain confidential or privileged information for the intended recipient(s). Unintended recipients are prohibited from taking action on the basis of information in this e-mail and using or disseminating the information, and must notify the sender and delete it from their system. Tata Technologies will not accept responsibility or liability for the accuracy or completeness of, or the presence of any virus or disabling code in this e-mail.
***********************************************************************************************************************************************