-
Notifications
You must be signed in to change notification settings - Fork 70
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
add analog 8ch mux/demux #323
base: master
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
The dual power is a bit funky, @carrotIndustries any ideas? |
Bot!
|
This review is brought to you by the Horizon EDA Poolbot commit 33131f8. Items in this PR
Parts overview (excluding derived)Bold items are from this PR
Derived partsBold items are from this PR
Parts tableValues in italic are inherited
DetailsPartsbase TSSOP-16 MUX/DEMUX 8ch with EN✔️ Checks passed
Flags
74HC4051PWInerhits from base TSSOP-16 MUX/DEMUX 8ch with EN ✔️ Checks passed
EntitiesSingle MUX/DEMUX 8ch with EN✔️ Checks passed
UnitsDual power with GND✔️ Checks passed
Symbol: Dual power with GND✔️ Checks passed
Single-ended MUX/DEMUX 8ch with EN✔️ Checks passed
Symbol: MUX/DEMUX 8ch with EN✔️ Checks passed |
As always bot will fail because base part doesn't have description.
I'm not sure about multiplexer's I/O naming. I made base part according Nexperia datasheet where channels named Y0, Y1,..., Y7, and output (let's call it so) named Z. On internet I found many examples with different namings. Our logic components (AND, OR, XOR.....) already in pool uses letters A, B, C, .... for channels and 'Y' for output. Maybe I should continue that way.... Every manufacturer uses their own naming for multiplexer's I/Os...