We just installed Kicad v7.0.10 (using flatpak) and are trying to route a very simple schematic. We loaded the Freerouting plugin from the Kicad plugin interface and it works only on one layer: it does auto-route, but it won’t create VIAs.
We also tried exporting the DSN directly and loading it in Freerouter outside of flatpak and it behaved the same way…so we know its not a flatpak+freerouter issue. My guess is that our board is not configured properly in Kicad (we are very new to Kicad, this is our first project). It is a default board set to 2-layers (we found the “Edit->Board Settings” page but it was already set to 2-layers).
The layout is all default except that we’ve added a board outline and dragged the footprints around somewhat so the ratlines do not overlap as much. The router gets most of the way, but definitely needs vias to the second layer to complete routing.
Are there any settings that need to be made to inform Freerouter that VIAs can be generated?
Anything you can do to help would be greatly appreciated!
This is what it looks like after Freerouter exits:
Freerouter will generate vias when it needs to. It looks like your accelerometer1 and Compass1 footprints are too small to allow routing to all the pads. Are you sure they are that small, much smaller than even the LVD regulator?
Thank you for your help pointing out that the pad size was the problem. Ultimately, vias weren’t the problem, but because it couldn’t connect to the pad, it never reached the point of needing vias.
Alright, here’s how we fixed it:
We went into file->board setup, and changed the defaults in the net classes tab to what the specs from JLCPCB were. The problem was that the drc was preventing the traces to connect to the pads because they we’re too close together. We knew that the footprints we’re the right size because we downloaded the ecad model from SamacSys. Here is a screenshot of the settings for flex pcb from JLCPCB that fixed this problem:
Don’t trust any source blindly. At a minimum you should verify the basic dimensions of the footprint with the datasheet to verify them. There are just too many possible sources for errors.
