Slash netnames in imported Eagle project?

[svgeesus]

Context: I am making a small correction to an old project of mine, originally done in Eagle. A Schottky diode is supposed to be between Vcc and Vss, while I put it between Vcc and Vdd. So I need to break and make one connection. The rest of the board is correct.

The project was imported in the recommended way:

[HowTo] Importing Eagle boards - use legacy 7.x format!

I have been experimenting a bit with this, and it looks like I can import Eagle 9.6.0 files with the following workflow: Start KiCad, create new project, with the exact same name as the Eagle project. Exit KiCad. (over cautious). Copy the Eagle schematic and PCB (.brd) file into the KiCad project. Import the schematic and PCB into KiCad. If the KiCad project has a different name then the Eagle files, then KiCad does something weird with creating two projects, it gets confused and (sometimes?)…

On the board, some netnames have an initial slash, so they will not connect with other nets that do not have the slash. On the schematic, the net labels do not have the slash; it seems to have been inserted by the import process.

For example /3V3 which will not connect with 3V3. What causes this, and how can I fix it?

I am trying to avoid redoing the whole project from scratch with KiCad symbols and footprints

In case anyone wants to play with the files, they are in
EuroMPE/Duophonic/Eagle/PitchDAC at master · svgeesus/EuroMPE · GitHub

[svgeesus]

I have meanwhile gone through and replaced imported symbols with the KiCad ones, and used KiCad footprints. Also ripping up tracks one by one and re-laying them on the board. This has resolved some but (oddly) not all of the slashed netnames.

[paulvdh]

The slashes are very likely caused by local labels. In KiCad local labels have a full path to the sheet they are in, and thus, local labels in the rootsheet start with a slash. Global labels are absolute though the whole schematic and do not have a slash. But still, local and global labels on the same sheet and with the same name should merge into a single net. Details in my head are a bit fuzzy, but this description should be close.

At the moment I’m not in the mood to look into your project on github. Maybe tomorrow.

[svgeesus]

Finally passes ERC and DRC, after disconnecting and reconnecting troublesome components and re-laying all tracks.

No local labels are visible on schematic or board, although they are still shown in the netlist.

(No need to poke at the Eagle project, I now have a fully KiCad project based on the corrected import. But thanks!)

[paulvdh]

@svgeesus

(No need to poke at the Eagle project, I now have a fully KiCad project based on the corrected import. But thanks!)

Ehm, actually it’s still interesting. Something seems to have gone wrong during the conversion. KiCad should have done it all automatically, so this reeks of some kind of bug. Projects that expose bugs in KiCad in a reliable way are important, as they are a giant step towards fixing the bug.

[Hitchcockney]

i downloaded your files and tested the import and all seems to work good (kicad 809) but I can’t see the “D2” your show in the picture with /3V3 in the downloaded files.

[svgeesus]

Thanks for taking a look.

D1 is there, and the screenshot shows a point where I had attempted to get rid of the local label by deleting D1 and adding a new, KiCad, diode symbol and footprint. Which it didn’t; but ripping up and re-laying the tracks did.

(I should have stated earlier that I was using KiCad 8.09)

[Hitchcockney]

ok I missed D1 as it was placed different compared to the picture and yes its something strange with the files, the /9V5s.

[Hitchcockney]

on the other hand if you have an older version of eagle, like 6.6 for example, this is not a problem, the conversation works with no slashes added, i dont know if that is a problem in eagle or in the kicad converter.