Open tgober opened 2 years ago
yes, the firmware is backwards compatible. you just need to configure it correctly according to the connections on the adapter (depends on how the jumpers are set)
I am using a custom made pcb inspired by the ebus adapter 2.2 version with a esp32-devkitc with a wroom 32d esp32. The firmware seems to work fine but i have different pins for rx/tx. Can you give me hints how to configure different pins (in my case it is GPIO16 + 17)? I would like to avoid adding botch wires to my pcb design.
for reference: the pinout of my board https://docs.espressif.com/projects/esp-idf/en/latest/esp32/_images/esp32-devkitC-v4-pinout.png
only the options listed in the UI are usable for RX/TX
... ah too bad, for the esp32, any IO pins can be reconfigured for one of the UARTs. But i see, that there are restrictions when using the esp8266.
I use a eBUS adapter 2 and try to connect it with a nodeMCU (because the D1 stopped working). Should the adapter3 FW work with the old boards? I tried the modes "direct RX/TX" and "swapped D7/D8". Then I ran the ebusd in a docker env. For the RX part only the swapped option seems to work, but the TX doesn't send anything on the bus. Then I passed the --generatesyn option into the container and stopped the syncer on the but. The log tells me, that an ">aa" was send, but I also receive an "unable to receive sent AUTO-SYN symbol: ERR: read timeout" error. Also I can't see any SYNC char on the bus nor on the UART.
Can you help?