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

Added M1P_V1.0 module (ShellyPlugUS) to Pinouts.md #1309

Merged
merged 1 commit into from
Dec 6, 2023
Merged

Added M1P_V1.0 module (ShellyPlugUS) to Pinouts.md #1309

merged 1 commit into from
Dec 6, 2023

Conversation

jdwhite
Copy link
Contributor

@jdwhite jdwhite commented Dec 6, 2023

The M1P_V1.0 is an ESP8266 module used by the ShellyPlugUS. In addition to pinout information, the accompanying images show the correct pins for TX and RX as the ShellyPlusUS board is mislabelled.

@barbudor
Copy link
Collaborator

barbudor commented Dec 6, 2023

Hi, thanks for the update
Just wanted to check a point regarding 'pins mislabelled'
Do we agree that your picture shows the RX and TX from the module/ESP point of view?
i.e. The RX pin of the module is the serial receive to be connected to the TX pin of the USB adapter and TX to RX?

@jdwhite
Copy link
Contributor Author

jdwhite commented Dec 6, 2023

Thank you for your skepticism. I don't blame you one bit because this can be a point of confusion and I would also question this claim.

Do we agree that your picture shows the RX and TX from the module/ESP point of view? i.e. The RX pin of the module is the serial receive to be connected to the TX pin of the USB adapter and TX to RX?

Yes, this is the case and I was also surprised by this. I've been fiddling with RS232 for over 35 years and flashed many other ESP modules and it's always been module RX <-> USB TX, module TX <-> USB RX for DTE equipment (and I claim it still is and that these pads are mislabelled). After trying unsuccessfully to flash using typical RX<->TX, TX<->RX I swapped TX and RX and it worked. Go figure.

In the spirit of "pics or it didn't happen", here's a pic of it wired up. I've color coded everything the same from the Shelly to the USB/TTL pins. Hopefully you can see the TX/RX markings on the Shelly and the corresponding USB/TTL pins. This will confirm the RX<->RX and TX<->TX wiring. The screenshot in the background is the Tasmota log output from the module. I can also provide a video of me flashing Tasmota in this config, which would confirm two-way communication, if needed.

I realize that my TX/RX connections aren't connected to the module pads as VCC/GND/GPIO0 are, but instead to the marked TX/RX pads that are a few mm away, but they are electrically identical per DVM continuity test. Guessing the manufacturer put those pads there for convenience.

I'm thinking I should also add the close-up wiring diagram photo to the pull request as I'm sure there will be others who question my claim. Was also considering pointing out the "short GPIO0 to ground for 5-10 seconds while energizing to put into programming mode", but that seems pretty standard and as this is a page about pinouts so could argue it doesn't belong here.
Thoughts?

M1P_V1 0 ShellyPlugUS Wiring

M1P_V1 0 ShellyPlugUS Log

@barbudor
Copy link
Collaborator

barbudor commented Dec 6, 2023

À simple 'yes' would have been enough 🤣🤣🤣

Personnaly I would consider that the last photo of the PR is enough but all good for me

Thanks

@barbudor barbudor merged commit ecb906d into tasmota:master Dec 6, 2023
1 check passed
jdwhite added a commit to jdwhite/tasmota-docs that referenced this pull request Dec 8, 2023
Include warnings regarding mislabeled TX/RX solder pads on ShellyPlugUS circuitboard as referenced in tasmota#1309
blakadder added a commit that referenced this pull request Dec 12, 2023
* Update Getting-Started.md

Include warnings regarding mislabeled TX/RX solder pads on ShellyPlugUS circuitboard as referenced in #1309

* Update Getting-Started.md

---------

Co-authored-by: blakadder <[email protected]>
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