Skip to content

555 Timer's reset pin is active low, so should have bar over name#924

Closed
ericfont wants to merge 1 commit intosharpie7:masterfrom
ericfont:patch-3
Closed

555 Timer's reset pin is active low, so should have bar over name#924
ericfont wants to merge 1 commit intosharpie7:masterfrom
ericfont:patch-3

Conversation

@ericfont
Copy link
Copy Markdown

Active low pins typically use a naming convention that puts a bar over the name. For the most part, datasheets and wikipedia.org/wiki/555_timer_IC have a bar over the reset pin name. Circuitjs already puts a bar over the 555's trigger pin, so the reset pin should also have a bar.

Active low pins typically use a naming convention that puts a bar over the name. For the most part, datasheets and wikipedia.org/wiki/555_timer_IC have a bar over the reset pin name. Circuitjs already puts a bar over the 555's trigger pin, so the reset pin should also have a bar.
@ericfont
Copy link
Copy Markdown
Author

Separate but related: I would also suggest that the pin currently named "Vin" should be renamed to "Vcc" as per typical naming of voltage supply pins and usage in 555 datasheets and 555's wikipedia page currently. "Vin" is also a little ambiguous (cause all 555 pins except the output and discharge could hypothetically be considered to be input pins). I didn't put it in this PR to keep this PR simple, but I would just suggest you consider also replacing instances of the string "N_VIN" with "N_VCC" and the string "Vin" with "Vcc" in this file.

@esaruoho
Copy link
Copy Markdown

esaruoho commented Mar 3, 2026

This is already fixed — commit ae21ddb added pins[N_RST].lineOver = true to the 555 timer, displaying the overline on the reset pin name. The fix is in both master and v3-dev branches.

@pfalstad
Copy link
Copy Markdown
Collaborator

pfalstad commented Mar 3, 2026

Thanks. I merged this a while ago but github didn't get the memo, I guess. Oh, probably because this is sharpie's repo.

@pfalstad pfalstad closed this Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants