Skip to content
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

create a fritzing diagram for connections #42

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

bytecod3
Copy link
Contributor

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

Fritzing circuit for the connections

What types of changes does your code introduce to votingBooth?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Other (please describe):

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • Lint and unit tests pass locally with my changes
  • Kept pull request small so they can be easily reviewed.
  • Make sure not to introduce any compiler warnings.
  • AVOID breaking the continuous integration build.
  • AVOID making significant changes to the driver's overall architecture.
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

What does this implement/fix? Explain your changes.

This PR creates a Fritzing circuit diagram for the voting booth using ESP8266 and its needed connection to the NEXTION Screen

Does this close any currently open issues?

This fixes issue #4

Any relevant logs, error output, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Where has this been tested?

Operating System: LINUX

Platform: UBUNTU 64-bit

Target Platform: Cross-platform

Toolchain Version:

SDK Version:

Further comments

Starting with a 9V 700mAh battery, I created a potential divider to supply 5V to the screen because the NEXTION display uses a 5V voltage level. Similarly, the ESP8266 uses a 3.3V level so I cascaded another potential divider to give 3.3V from the 5V to the ESP8266. For the USART communication between the ESP8266 and the display, the voltage levels have to match so I used a PCA9306 level shifter to do that. I also added a RED LED as an indicator that the whole system is ON.

voting_booth_circuit

Copy link
Member

@rodneyosodo rodneyosodo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use esp32 or if you can find a way to create a board use the sesboard

@bytecod3
Copy link
Contributor Author

Alright. Working on that.

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.

2 participants