mhi_ac_ctrl_core.loop error: -3

[andi377]

I described the wemos with version v2.5R21. The Wemos is available in the WiFi and also in the MQTT server in the iobroker. The data points have been created, but they are not updated. Where I have now activated the serial monitor in the IDE comes

18:01:26.323 -> mhi_ac_ctrl_core.loop error: -3 18:01:26.423 -> mhi_ac_ctrl_core.loop error: -3 18:01:26.523 -> mhi_ac_ctrl_core.loop error: -3 18:01:26.624 -> mhi_ac_ctrl_core.loop error: -3 18:01:26.724 -> mhi_ac_ctrl_core.loop error: -3

Where is my problem, unfortunately I can't get any further

[absalom-muc]

This message indicates a time out condition for the SCK pin. Please provide the debug outputs from the beginning after reset is released. There should be messages related to the pins SCK, MISO and MOSI, so that you can see if the pins are connected in the right way. (I assume SCK is not connected, but let's see)

[andi377]

Ifound the problem, it was a hardware error, now everything works. Thanks for your help

Is there also a possibility to integrate a ceiling device (FDTC25VF) ?

[andi377]

Today I wanted to rewrite the wemos, only the host name was adjusted. After that, the control no longer works.

The debugfile is attach

Here is the problem?

debug.txt

[absalom-muc]

Ifound the problem, it was a hardware error, now everything works. Thanks for your help

Is there also a possibility to integrate a ceiling device (FDTC25VF) ?

Only if the ceiling device has a CNS connector supporting the same SPI signals as the SRK devices. I don't know if this is the case.

Today I wanted to rewrite the wemos, only the host name was adjusted. After that, the control no longer works.

The debugfile is attach

Here is the problem?

debug.txt

These are the error code: err_msg_valid_frame = 0, err_msg_invalid_signature = -1, err_msg_invalid_checksum = -2, err_msg_timeout_SCK_low = -3, err_msg_timeout_SCK_high = -4 The data received from your AC are faulty. Reason could be a loose contact of the SPI pins (especially SCK and MOSI) or a cable that is too long. (I assume you use the original HW setup for MHI-AC-Ctrl)

[andi377]

yes it the original HW setup for MHI-AC-Ctrl). I just changed the hostname. With one pcb I have the plug directly with the second one with a cable length of approx. 15 cm. I measured the pcb electrically. Only the level converter could be the problem . In the MQTT server I can see that the time stamp for MISO, MOSI and SCK changes when the Wemos is boote debug2.txt d

[absalom-muc]

The frequency values for SCK, MOSI and MISO during boot look perfect and I can see in your debug file that it works without problems for 20 seconds. I have no idea what happens after these 20 seconds. Maybe the esp8266 should be replaced, but that's just a guess.

[andi377]

oday I tried it again with new hardware, one version worked, one didn't. When it worked, the whole thing only went for a certain amount of time. Then the wemos was no longer visible in the WLAN. When checked, the wemos was very warm. What temperature is normal there? I'm slowly running out of ideas on how to get this to work.

[absalom-muc]

oday I tried it again with new hardware, one version worked, one didn't. When it worked, the whole thing only went for a certain amount of time. Then the wemos was no longer visible in the WLAN. When checked, the wemos was very warm. What temperature is normal there? I'm slowly running out of ideas on how to get this to work.

I don't know "normal temperature". Not sure what you mean with "one version worked, one didn't". Have you exchanged the Wemos of the boards? So not clear if you identified a board not working or a Wemos not working.

[absalom-muc]

Since there was no update since long time, I assume this issue is resolved. In case of further questions please don't hesitate to re-open it.