From 7.0.1 to 7.0.2-0: Error reading simulation model

Schematic Library Symbols
1

Hi! (desperate grin)
Just updated to 7.0.2-0 because I had some odd problems (other subject). Before, DRC had only some odd problems that “out of the blue” appeared. Again, not the topic here.
Installed (MacOS) and run the DRC again. With more errors. I get some 20++ errors with a message like "Error reading simulation model from symbol ‘#PWR047’. And that #PWR047 is just a simple stupid -10V in this example. All other active parts (diodes, uC, OpAmps, you name it) do have a similar error.

Yes, if I try to edit the simulation model, it can’t be found. Well, I don’t care, I don’t need it.
I’m not using spice, I gave up on it in KiCAD. But that’s OK for me, not complaining. Might be me fault.

Other than switching back to 7.0.1, what else might I do?

1 Like
2

Well, that was easy.
In “File → Schematic Setup → Elektrical Rules → Viloation Setup” I set “SPICE model issues” to ignore to get rid of these errors.
Seems that changed from 7.01.1 to 7.0.2 silently.

2 Likes
3

It’s a bug in 7.0.2 that will be fixed in 7.0.3 - the errors are spurious. You found the workaround :slight_smile:

1 Like
4

Ah, thanks for the confirmation!
So I assume that the zillion of “off grid errors” I suddenly get (despite clearly snapping to the grid) in the schematics editor is also a “spurious error”. I’ll treat it the same way. That started out of the blue in 7.0.1, so I hoped it was fixed in 7.0.2. Just to get new errors. :slight_smile: It’s OK, I can live with that.

And one more thing, while I am at it: Where should I report errors in a symbol?

Thanks,
Nick

5

Open an issue here: KiCad / KiCad Libraries / KiCad Symbols · GitLab

6

Problem still exists in 7.0.5.

I can’t find it in the GitLab Issues, either.

Is your grid what you think it is? I’m not sure when N was assigned as the Next Grid hotkey but I only noticed it recently. If you hit N when you’re trying to hit M, it changes the grid and there’s no obvious feedback unless you’re staring at the grid spacing value. I was ending up with stuff off grid and “off grid errors” until I nuked that hotkey.

7

That error disappeard the same way it came. Suddenly, without doing anything (maybe I just restarted).
I also checked the grid. But if connections snap to the grid, it doesn’t matter what grid I use. And for sure, I moved both ends to match any grid.

8

If my grid is 0.05" and I (inadvertently) change the grid to 0.025" and lay out symbols on that, and run ERC, I don’t get grid errors. But then if I switch the grid back to 0.05", then I do.

9

But then if I switch the grid back to 0.05", then I do

The ERC-grid-check tests:
Are all wire-endpoints and all Pin-connection-points (all pins from the symbols) aligned to the current used grid?
If the some wires/pins are not aligned to the current grid, than you get an error.

So with your example: drawing first wires/symbols on a fine grid (0.025), than switch back to standard 0,05grid → error message.

10

I looked again, it’s there and closed because the bug is fixed — but I still see these errors because:

image
image923×133 16.4 KB

Which leads me to wonder:

Is there a way to change the default violation severity? If you don’t intend to simulate ANY schematic (in KiCad) then it’s an annoyance to have to edit the severity on every new project.

Granted, you can use a template that has the severity changed; but is there a way to change the default for non template projects?

11

I commented in the issue, but for everyone else: what you suggest was implemented a while back - the SPICE model ERC check is disabled by default in new projects. Jeff’s comment was referring to existing projects.

12

this issue is considered duplicate. I have just added a couple of comments here instead:

I hope that this issue will be reconsidered.

Salvatore

13

I think you may have guided to the wrong closed issue:
ERC: Failed to read simulation model from fields (#14562) · Issues · KiCad / KiCad Source Code / kicad · GitLab is the one that mentions the existence of the ERC warnings. It was closed by the change to set those warning to default off (so that new projects would have to opt in if the user were actively using simulation). Unfortunately, existing projects have to be manually modified to turn off that warning, since KiCad won’t overwrite your project configuration on updates.

1 Like
14

yes, it’s true, but this confirms that from v7.0.1 to v7.0.2 there has been a change, since in v7.0.1 there weren’t those ERC errors.

I don’t know what was the default for this setting in 7.0.1, was it already set to “Ignore”? And was it changed to “Error” in 7.0.2?

In 7.0.3 maybe?

I have tried now to create a new project and the default is “Ignore”.

Ok, now it’s all more clear :slight_smile:

Salvatore

15

I’m not sure when exactly the ERC error was added, but I do remember the whole simulation system being pretty broken till 7.0.2 at least, so it is possible that it was added earlier but not functioning properly till recently. In the jump from 7.0.1 to 7.0.5, you got to skip through a lot of ERC fixes, though they don’t automatically “fix” existing project settings.

In general though, I don’t think it is a big deal to disable ERC warnings that aren’t relevant to you (if you come across more in the future).

16

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.