rstrouse
WT32-ETH01 wiring of GDO0
Hardware
ESP32 WT32-ETH01
Firmware version
v2.4.6
Application version
v2.4.6
What happened? What did you expect to happen?
Hello and thank you for this great project. Especially the excellent documentation speeds up the setup process.
However, I still have a question about wiring.
I setup the HW using a WT32-ETH01 connected to CC1101 transceiver. I flashed ESP32 with v2.4.6 and did a basic config-setup of LAN network and radio. LAN is working fine.
Radio config has been done according to the wiring below. Wiring between CC1101 and WT32-ETH01:
CC1101 WT32-ETH01
--------------------------------------------
(1) GND <--> GND
(2) VCC <--> 3v3
(3) GDO0 (rf-tx-pin) <--> GPIO32
(8) GDO2 (rf-rx-pin) <--> GPI39
(4) CSN (rf-ss-pin) <--> GPIO33
(5) SCK (rf-sclk-pin) <--> GPIO17
(6) MOSI (rf-mosi-pin) <--> GPIO14
(7) MISO/GDO1 (rf-miso-pin) <--> GPIO15
Receiving radio signals form my RF remote works. I can see the commands in the logs tab. However, when I try to pair my Somfy motor with ESPSomfy-RTS no RF signal is sent. The motor does not jog. So receiving works but there's no sending.
Since GDO0 is for sending I decided to connect it to GPIO02 as suggested in the Simple Hardware Guide and now sending works like a charm.
So far so good. I could live with that change but my question is: Why sending doesn't work with GPIO32 ?
Now you might refer to this troubleshooting tip suggesting that I mixed up rf-tx-pin and rf-rx-pin. However, I have the same hardware with the wiring above in use with Tronferno project and sending even works with GPIO32 there. Why is that?
BR, Andy
How to reproduce it (step by step)
1. Setup hardware
2. Flash firmware
3. Configure Network
4. Configure Radio. Especially the GPIO connection GDO0 <--> GPIO32
5. Verify receiving of signals from RF remote
6. Pairing with a Somfy motor fails (motor does not jog)
7. Change wiring of GDO0 to GPIO02
8. Pairing with a Somfy motor works (motor jogs)
Logs
For some LAN ESP32 implementations GPIO32 and 33 have strange properties. I don't completely understand why that is but perhaps it has something to do with the way the LAN8720A PHY is wired up. Bear in mind that GDO0 is an input/output pin.
