Seve - Do we have a doc for pinout diagrams? @s...

Do we have a doc for pinout diagrams? @shibo we should get a good example
43 Replies
Seve
SeveOP2w ago
The bounty for pinout is pretty big as well so i think it makes sense to have a doc as completion criteria for a big feature, should be quick? Maybe we need svg.tscircuit.com support for the new svg type
Seve
SeveOP2w ago
@shibo this could be a good one for the docs
No description
Seve
SeveOP2w ago
https://tscircuit.com/seveibar/pico so this component is a receiver, so maybe we’d need to clone it
seveibar/PICO - tscircuit
Generated from JLCPCB part number C7203002 To import and use the PICO component in a project: 1. Import the component:
import { PICO } from "@tsci/seveibar.PICO"
import { PICO } from "@tsci/seveibar.PICO"
2. Use the component in a circuit:
<PICO name="U1" />
<PICO name="U1" />
The component has 49 pins with various functions like GPIO (GP0-GP28), power (3V3_EN, VSYS), and debug (SW...
Seve
SeveOP2w ago
I think we could also extend it with pin attributes?
shibo
shibo2w ago
can we do something simpler for now?
Seve
SeveOP2w ago
it should be pretty simple though no? we just have to put on pinAttributes
Seve
SeveOP2w ago
No description
Seve
SeveOP2w ago
i think there are a couple bugs in the pinout, i don't think that bounty is ready to be claimed, there's overlapping traces, the rotation bug, and the multi-label support doesn't seem to work right
No description
Seve
SeveOP2w ago
it's separating multi-labels with a "|" symbol
import { PICO_W } from "@tsci/seveibar.PICO_W"

export default () => (
<board>
<PICO_W
name="U1"
pcbRotation="90deg"
pinAttributes={{
GND_AGND: { includeInBoardPinout: true },
"3V3_EN": { includeInBoardPinout: true },
"GND1": { includeInBoardPinout: true },
}}
/>
</board>
)
import { PICO_W } from "@tsci/seveibar.PICO_W"

export default () => (
<board>
<PICO_W
name="U1"
pcbRotation="90deg"
pinAttributes={{
GND_AGND: { includeInBoardPinout: true },
"3V3_EN": { includeInBoardPinout: true },
"GND1": { includeInBoardPinout: true },
}}
/>
</board>
)
like it doesn't need to be perfect to claim the bounty but i think it's missing some important things the main thing for a bounty is "would the end-user accept it" even begrudgingly- I also mentioned this to @Anas , but ultimately if an end-user wouldn't accept the result there shouldn't be a claim on the bounty
shibo
shibo2w ago
I'll use this as a test case
Seve
SeveOP2w ago
I can fill out the rest of the pin labels if it's helpful?
shibo
shibo2w ago
ofcourse thanks
Seve
SeveOP2w ago
i also flipped to -90deg and noticed it flipped the U1 designator
No description
shibo
shibo2w ago
it should never flip
Seve
SeveOP2w ago
this might be something we do in assembly incorrectly too(?)
shibo
shibo2w ago
how do you want the seperation to be? separate boxes?
Seve
SeveOP2w ago
yea, you can see that they do this kind of organized separation as well
No description
Seve
SeveOP2w ago
and see the pin number on the right side? Looks great
Seve
SeveOP2w ago
No description
Seve
SeveOP2w ago
RE: how to determine the label order- you probably need to consider the "side" it's on, to reverse the sort, but otherwise you can just do a sort we'll let the user specify something like pinoutPrefixColors={{ "GP": "green", "SPI": "pink" }} in future work
Seve
SeveOP2w ago
just posting more design references
No description
shibo
shibo2w ago
what ordering, the labels should just align with their pads right?
Seve
SeveOP2w ago
I mean the ordering of label pills, i.e. ["SPI1_RX", "GP8", "pin11"] basically you flip the alphabetical sort order based on what it's facing direction is
Seve
SeveOP2w ago
i.e. GP is always closest to center
No description
Seve
SeveOP2w ago
another design reference, i think this has the best "pills"
No description
shibo
shibo2w ago
👀
Seve
SeveOP2w ago
ah yea sorry got distracted
Seve
SeveOP2w ago
No description
shibo
shibo2w ago
Its so buggy Good test
shibo
shibo2w ago
@Seve there shouldn't be pinouts in the top right? they should just aligned left or right
No description
Seve
SeveOP2w ago
we could allow for customization of it later, i think it depends on the label sizes tbh short term maybe just have it be a non-user-configurable flag and go with left/right?
shibo
shibo2w ago
I cant find examples of up down positionsb Looks like its unconventional
Seve
SeveOP2w ago
yea ok
shibo
shibo2w ago
@Seve how are these looking?
No description
Seve
SeveOP2w ago
definitely better but there's still a lot of issues right, why do we need to space these out at all btw?
No description
No description
Seve
SeveOP2w ago
there really shouldn't even be many lines in this particular pinout
No description
Seve
SeveOP2w ago
like how are you determining that pin label pill size? it seems like if the pills were scaled appropriately there wouldn't be a need for the lines that could be a board property or something too, like <board pinoutLabelHeight="0.075in"> but I also think we should have a default that matches the 0.1in jumper convention by default
shibo
shibo2w ago
I didn't think of scaling the pills with the pad width
Seve
SeveOP2w ago
i don't think they should be, i think all pills should be the same size, it's just that almost all of these types of boards have conventional 0.1in jumper spacing, so our default should just set the pill height where boards with this type of common jumper work perfectlyu
shibo
shibo2w ago
@Seve those pills that read sideways, do they look good?
Seve
SeveOP2w ago
i would avoid them sorry for the delay

Did you find this page helpful?