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

connecting esp-01 to anet A8 #355

Closed
drunkscientist opened this issue Aug 1, 2019 · 5 comments
Closed

connecting esp-01 to anet A8 #355

drunkscientist opened this issue Aug 1, 2019 · 5 comments

Comments

@drunkscientist
Copy link

it looks like someone got close #334 before having a bad day, i would like to hopefully finish what they started and update the wiki. i dont have the same board model (not sure if the green connectors for power/bed/extruder are newer or older) but is it safe to assume that the connectors for j3 are the same? if im reading this board correctly, it has some sort of 1117 regulator, and j3 has a 3.3v pin which should have enough to power the esp. the rx/tx of the esp can then connect to tx/rx of j3, probably through a level shifter/voltage divider. or do i need to bypass the onboard ch340 chip? i was trying to understand why there were extra wires being soldered. if that is the case would it not be easier to use the middle pair of pins from the USB BLE header, according to this diagram those middle two pins are AIFO and AOFI, which connect directly to the atmegas rx/tx pins, and they become the usb_tx/rx at the ch340. i might have confused myself...

@luc-github
Copy link
Owner

@rhialto56 got success #334 (comment)
He may answer your question

For me you need to use serial pins not ch340 usb pins to connect to ESP

@drunkscientist
Copy link
Author

ok after much staring at this schematic and tutorials pictures, im pretty confident the AOFI and AIFO pins are connected directly to the atmega. assuming they are, i should be able flash the esp and connect rx/tx lines to there and be good? just need to make sure to disconnect before using usb

@luc-github
Copy link
Owner

Any update on this ?

@drunkscientist
Copy link
Author

had other unrelated hardware failure before i could test. still plan to try again once replacements arrive

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants