[QucsStudio]

Yes, you are absolutely right! I will change it.

[QucsStudio]

Sorry, this is not yet supported, but on top of the todo list. For small lists, the if() statement could be used, but it’s very tedious.

[QucsStudio]

Hm, seems to be a Linux problem. Sorry, I don’t know about a workaround. I think this can only be avoided internally by a different drawing method.

[QucsStudio]

This is a nice idea indeed! So it’s on the todo list now.

[QucsStudio]

Indeed, the plan for future versions is

* zoom with mouse wheel
* move with right mouse button pressed
* context menu with right mouse button click

As far as I know this is what most programs do.

[QucsStudio]

The correct usage of z-parameter transformation is:

Z_param = stoz()    if your s-parameter ports have 50 ohms
Z_param = stoz(25)   if your s-parameter ports have 25 ohms

This works in equation components only, not in diagram equation.

Anyway, if you want to know the loading of the source, stoz() is not the correct function, because z-parameters are defined with open port terminations.

rtoz(…) does the job (see attached picture).

• This reply was modified 1 year, 10 months ago by maelh. Reason: Convert all remaining http links to https links

[QucsStudio]

Hello,

You’re right, complex port impedances are not supported. A warning would be nice here.

But the Touchstone file component supports the necessary transformation, if the property “func” is set to “complexZ0”. For frequency-independent port impedances, the s1p-file needs two lines only. See example in the picture.

<picture removed because of bug>

• This reply was modified 2 years, 4 months ago by QucsStudio.

[QucsStudio]

Yes, you’re right. This is still on the ToDo list, because it’s more complicated. I think it will not be fixed before version 5.

[QucsStudio]

The s4p files contains data up to 2.4 GHz, your simulation runs up to 24 GHz. I guess this is not what you wanted?

[QucsStudio]

Yes, you’re right. Thanks for the report! It will be fixed in the next release.

[QucsStudio]

Would be great if you can share the project (snp-files plus schematics) that shows the problem. Using QucsStudio package file would be best, of course.

Many thanks!

[QucsStudio]

Thanks a lot for the example! I can reproduce the bug and will fix it.

Workaround: Open the subcircuit schematic before the simulation starts, i.e. select the subcircuit component and press “CTRL+i”.

[QucsStudio]

I cannot reproduce this bug. A single subcircuit works as well as a nested one.

Can you share your examples? Does it always crash? What operation system do you use?

[QucsStudio]

These things should already work using the yvalue(…) and range(…) functions. Please see examples on this website.

[QucsStudio]

I guess that the only problem here is a missing linefeed at the end of the line. Please add it and try again.

[Author]

Posts