Check GPO pins (uart: section), you might need to swap the pins in the config

[opwierde]

Hi all, might be a silly question but I do not understand how to do the following:
(check GPO pins (uart: section), you might need to swap the pins in the config)

There is no data coming from my heat pump yet and I am hoping that this could be the issue. Everything seems to have gone well otherwise (installing, wifi link, esp32s3 status)

[gekkekoe]

Sounds like you are using a wrong board definition. Can you post your esphome-ecodan.yaml and specify what hardware you are using and how its wired? If you used the recommended hardware and schematics, it should work out of the box.

[opwierde]

As you can see the wiring is a bit confusing due to the plugs I had.

ESP 32 -> CN105
black -> red
red -> white
white -> yellow
yellow -> orange

I have compared it to your connections below and tested with ohm meter to be sure Tx and Rx are connected. Power is good as it does come online when plugged into the cn105

grove	cn105
pin 1 - black (gnd)	pin 4 - black (gnd)
pin 2 - red (5v)	pin 3 - red (5v)
pin 3 - white (GPIO 2)	pin 2 - white (Tx)
pin 4 - yellow (GPIO 1)	pin 1 - yellow (Rx)

esphome-ecodan.txt

[gekkekoe]

wires looks okay and if you tested it (you are making yourself hard by using the wires like this), it should be fine. Just to double check, you did check the TX/RX cables from one connector to the other connector right?

The atom s3 comes online right ? Just not connecting to the heatpump?
When you connect to http://ip_esp what does it say ? Trying to connect messages? you should see the http esphome page.
else post output of
esphome logs --device ip esphome-ecodan.yaml

What you could try is swap white and red (coming from the esp32). So white -> white and red -> yellow. But I don't think that's the issue.

[opwierde]

Now I have learned how to switch the wires in a grove connector... next time it will look better.
Swapped the Tx and Rx without result, attached the output on the homepage. A lot of unsuccessful connect messages.

[F1p]

What are you connecting to? Air-to-Water and what FTC board version 3/4/5/6/7?

[opwierde]

Air to water, FTC6. The MEL cloud adapter does work on the CN105 connector. I re-connected it to check.

[gekkekoe]

It tries to send connect sequence and does not get a response (could also be that the connect never gets transmitted over the line). Please check if wire of rx/tx is ok(check at both connector ends)

But it seems okay, what unit and FTC are. you connecting btw? I am running out of ideas why it is not working...

[F1p]

Can you show the port you are connecting to on the FTC board please?

[opwierde]

Removed the MEL cloud plug and connected the ESP32

[F1p]

Looks ok to me too, I would check electrical connection of the cable as per the suggestion again

Not to hijack or anything, but you can flash my MQTT based project and check if you get the same if you wish:

esptool.exe --chip esp32s3 --port "COM12" --baud 921600 --before default_reset --after hard_reset write_flash -e -z --flash_mode dio --flash_freq 80m --flash_size 4MB 0x0 "ECODAN_Bridge_v5.2.6-h3.bootloader.bin" 0x8000 "ECODAN_Bridge_v5.2.6-h3.partitions.bin" 0xe000 "boot_app0.bin" 0x10000 "ECODAN_Bridge_v5.2.6-h3.bin"

You can connect to Telnet and check the connection messages

[gekkekoe]

he could try it, but I think RX/TX is broken somehow...

[F1p]

he could try it, but I think RX/TX is broken somehow...

Agree, should make no difference

[gekkekoe]

if the melcloud adapter is working then the cn105 is fine. Unit should be supported.
Did you measure/check the RX/TX from both connector ends? (so measure from CN105 connect to the grove connector).

The cable must be broken or the atom is not okay. Do you have a spare atom ? Else you can map the RX/TX to pin 38/39. But you need to adjust some configs for this (this is assuming that pin 1/2 are broken).

You could try to run the atom outside the unit via usb c cable (and don't connect the cn105, so run it stand alone). And measure the cn105 cable connector RX/TX. it should do 3.3v on TX/RX pins.

[gekkekoe]

Sorry my bad, I flashed a heishamon firmware (with different pin layout) on one of my test unit atom :) With the correct firmware you should see
TX ~3.4V, but will fluctuate when it's sending connect sequence
RX ~3.4V

Your readings implies that pins are not correctly configured.

So I think

1. pin config is wrong
2. your cable is wrong

Try recompile, by cleaning first

esphome clean ecodan-esphome.yaml
esphome compile ecodan-esphome.yaml
esphome upload --device ip ecodan-esphome.yaml

If it still does not work, measure without cable directly on your atom grove port.

[gekkekoe]

Checked without wires as well. Same issue

ah okay then there's something wrong with the TX pin. try clean build install one last time and then order new atom :(
And monitor TX for like 1 mins, each time it tries to connect you should see voltage changing

When you do get a new atom test it standalone and measure voltages if it behaves as expected before plugging it in.

[opwierde]

Yes, I will order a new one. I hooked up my scope and the Tx signal looked pretty bad, a lot of ringing so I might have blown the output circuit somehow.

[gekkekoe]

thats quite an achievement, did you wire 12v to it ? :D

[opwierde]

Polyester track suit and no anti-static precautions is my favourite method