Iggystlev - Hey folks. I am still rather new to...
Hey folks. I am still rather new to tscircuit so if I am asking this in the wrong place lmk where I should ask. I have finished laying out a circuit in tscircuit and it seems to be working well for everything I need so far, except for traces. The autorouter seems to be creating s
Hey folks. I am still rather new to tscircuit so if I am asking this in the wrong place lmk where I should ask.
I have finished laying out a circuit in tscircuit and it seems to be working well for everything I need so far, except for traces. The autorouter seems to be creating some odd traces here and there, which normally I would try to clean up by hand but I am running into some friction getting that to behave. Using the `pcbPath` attribute seems to work, but the way I am currently using it is too clunky. I have been typing in a number, watching the live pcb view update, seeing if that is right and continuing on. Coming from KiCad's trace editing tools makes me feel like there must be a better way, even if it is just exporting to kicad to do trace routing and then getting importing the trace coords back into tscircuit's `pcbPath` array. Can anyone shed some light on better ways to layout traces?
Iggystlev
Here are some examples of the odd traces i am seeing
for working around it, yes pcbPath is the only option we currently offer for fixing it- most of the other options would cause too much data to be committed
Seve
<trace pcbPath />
Seve
if you are at the stage where you're ordering, a lot of people will export out into KiCad for small final adjustments they aren't able to make with pcbPath
Seve
we have very good reasons for not manually routing- having that data inside the TSX "makes the ai dumber" (it's super token inefficient). You may want to consider using calc strings as well
I tried making an issue in-app but it returned an error said I was trying too many times after trying once, so I assumed it was not setup. Thank you for the other links.
Oh interesting, maybe use github directly? Or that doc allows you to create a link to the autorouting problem, you could share it here
Iggystlev
the tscircuit-autorouter repo seems to be for the newer "capacity-autorouter". I dont think that is the one I am using, I am using the default one. I tried setting that one up the other day but ran into a package issue. Unfortunately I dont have a screenshot of that error, I want to say it was something to do with object-hash subpackage?. Ok I'll try to organize these issues and see what I can get reproductions of. I appreciate the effort on your end.
Seve
Ofc we want everything to work by default!!! The capacity autorouter is the same as the tscircuit autorouter/default autorouter
Iggystlev
I thought the default was `sequential-trace`. I think I had some llm output that indicated some other issues I was running into with routing were typical of sequential-trace, maybe it hallucinated.
Seve
Yea we deprecated sequential trace recently because it was almost never able to successfully make a board
Iggystlev
ahh, that makes sense.
I am using tscircuit@0.0.2229 right now, would that mean I am definitely using the capacity-autorouter?
Seve
Yep!
Iggystlev
Perfect, then ill make that ticket about this routing issue next chance I get at my computer. Thanks again!
Seve
Thank you! We are always looking for bugs!!!
Want to add to the conversation?
Reply in Discord so your notes stay connected to the source.
