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

Suspected case of routing database corruption again. #4227

Open
vanepp opened this issue Feb 16, 2025 · 0 comments
Open

Suspected case of routing database corruption again. #4227

vanepp opened this issue Feb 16, 2025 · 0 comments

Comments

@vanepp
Copy link
Contributor

vanepp commented Feb 16, 2025

Current Behaviour

This sketch

Untitled Sketch 2.fzz.zip

from this rather long forum post starting about here

https://forum.fritzing.org/t/battery-expansion-shield-18650-v3/26791/87

I think indicates routing database corruption in 1.0.4. Unfortunately, as usual, we don't have any idea what caused the original corruption. I'm hoping that looking at the .fzz file may give you some clue to what happened to cause this. Here I right clicked on the J7 pin with the green arrow. The path lights as expected (circled in green) but an isolated via with no apparent connection is indicated as part of this net (which I suspect is the routing data base corruption.)

Image

the green haze on the trace near the via that it thinks belongs to this net may also be a clue.

Image

now delete the top layer wire in order to move the bottom layer wire to the top layer and allow the removal of 2 vias and extending the line on the bottom layer,

Image

but the move the bottom layer wire to the top layer goes wrong.

Image

the wire moves to the via (that Fritzing thinks is part of this net) and the line segment it used to go to is now disconnected which is what makes me think this is routing database corruption again.
As far as I know the sketch was created on 1.0.4 and I am working on it on 1.0.4 so both sides are on the latest version. Hopefully the .fzz file will shed some illumination on what may have gone wrong.

Build:
Version 1.0.4
(CD-2088-0-a8c6ef7c 2024-10-07) 64 [Qt 6.5.3]

Operating System:
Windows 10

Steps to reproduce:

See ## Current Behaviour

Expected Behaviour

Hopefully correct operation i.e the trace connects correctly.

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

No branches or pull requests

1 participant