You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i tried many frequencies combined with some db values (5 db steps)
Debug Serial Log output
No response
Error description
ESP 32 + CMT2300a (set from Blinky Parts) HMS-1600-4T Inverter without WIFI Module implemented. The CMT2300a is connected and all seems to be fine. i tried firmware 0.8.83 (no letters allowed in Serial Number) / 0.8.140 / 0.8.152 and the connection to the inverter was never established. i checked the serial number many times and tried many combinations of frequency and send power. The distance between inverter and esp32 is lower than 10 meters and there is no wall between.
The text was updated successfully, but these errors were encountered:
Does the CMT2300A Interrupt show it is working in the UI System Info ?
Did you connect the GPIO3 of the Blinky Parts breakout board ?
I am not 100% sure though I believe this is/was not necessary for OpenDTU but it is a requirement for AhoyDTU.
Can you provide a picture of your hardware ?
Platform
ESP32
Assembly
the DTU was already assembled
CMT2300a Module
No response
Antenna
external antenna
Power Stabilization
Elko (~100uF)
Connection picture
Version
0.8.152
Github Hash
1
Build & Flash Method
AhoyDTU Webinstaller
Setup
i tried many frequencies combined with some db values (5 db steps)
Debug Serial Log output
No response
Error description
ESP 32 + CMT2300a (set from Blinky Parts) HMS-1600-4T Inverter without WIFI Module implemented. The CMT2300a is connected and all seems to be fine. i tried firmware 0.8.83 (no letters allowed in Serial Number) / 0.8.140 / 0.8.152 and the connection to the inverter was never established. i checked the serial number many times and tried many combinations of frequency and send power. The distance between inverter and esp32 is lower than 10 meters and there is no wall between.
The text was updated successfully, but these errors were encountered: