Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

schematic error causes component line format error #812

Closed
bobu01 opened this issue Jul 6, 2024 · 2 comments · Fixed by #814
Closed

schematic error causes component line format error #812

bobu01 opened this issue Jul 6, 2024 · 2 comments · Fixed by #814
Labels
Milestone

Comments

@bobu01
Copy link

bobu01 commented Jul 6, 2024

qucs-s can write a schematic file that can't be opened later. The example schematic has a spice .PARAM block. The block has a name string that contains unwanted space characters. The simulation runs fine and the schematic is saved without complaint. Later, the schematic fails to open due to the space characters in the .PARAM line.

For example, this line is no good:
<SpicePar VCC and VREF 1 820 360 -27 18 0 0 "VCC=5" 1 "THH=VCC*2/3" 1 "THL=VCC/3" 1>

qucs_s_format_error

This issue can be fixed by opening the .sch file in a text editor and removing the unwanted spaces from the name. (If you can find them.)

The system is an up to date Arch Linux distro. qucs-s version is 24-2-1, installed from Arch AUR.

trig_load_sch.zip

@ra3xdh ra3xdh added the bug label Jul 6, 2024
@ra3xdh ra3xdh added this to the 24.3.0 milestone Jul 6, 2024
@tomhajjar
Copy link

tomhajjar commented Jul 7, 2024

So the .PARAM name was invalid. It was "VCC and VREF" versus the proper "VCC_and_VREF".

What other ASCII characters or control characters beside a "space" can't be used?

ngspice doesn't like netlist filenames with "space" either.

@ra3xdh
Copy link
Owner

ra3xdh commented Jul 7, 2024

The spaces in device name should not be allowed. I prepared a fix for this. See #814.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants