lumapu / ahoy

Various tools, examples, and documentation for communicating with Hoymiles microinverters
https://ahoydtu.de
Other
953 stars 225 forks source link

AhoyDTU Hoymiles HM800 - Wrong data rate? #1149

Closed lunanigra closed 1 year ago

lunanigra commented 1 year ago

The communication between AhoyDTU and Hoymiles inverter is not stable. Sometimes everything ok for days, then not connection at all (RX no answer).

Status of NRF24L01+ is shown as connected. But data rate seems being not correct - I assume data rate should be 250 kbps.

Is there a way to set the data rate hard-coded?

Hardware

nRF24L01+ Module

Antenna:

Power Stabilization:

image

kiu77 commented 1 year ago

In such strange cases a somehow notsological procedure helped me: Just reflash the ESP with erasing the flash and then update to a newer version of the firmware. Then make the settings new.

I had behaviour in some ESP32 which could not fixed otherwise.

lunanigra commented 1 year ago

@kiu77, thanks for your quick response. I will try reset and/or erasing the flash.

Just for understanding... Is the data rate an indicator for possible errors? Or is it not such easy?

kiu77 commented 1 year ago

At least the displayed data range sounds very strange to me. BTW: just resetting the settings didn't work in my cases. I had to flash with erasing.

lumapu commented 1 year ago

so you could fix it by reflashing with erase?

lunanigra commented 1 year ago

Sorry, not so far... Inverter is located at my parent's house. Will check on weekend (at the latest).

lunanigra commented 1 year ago

@kiu77, @lumapu, I erased ESP32 and re-flashed AhoyDTU. Data rate is shown as 256 kbps now - unluckily this is the only change.

Still only "RX no answer". I'm wondering what could be wrong?

Any idea what else to check?

lumapu commented 1 year ago

the pinout, we changed the default pinout recently

lunanigra commented 1 year ago

Ok, will check wiring again. But must be at least nearly correct as nRF24L01+ is shown as connected.

Following the v0.7.36 release notes pin assignment was changed for ESP8266 only.

fsck-block commented 1 year ago

Hi @lunanigra had the same problem some month ago. After changing the NRF24l01+ module all works well again. BTW: The data rate is hard coded to 250bps. In my case the module change the data rate by it's own.

kiu77 commented 1 year ago

Good aspect, @fsck-block , I had one nrf24 module from eByte (about of 20) with defect and an ESP32 module (out of 20) which give little smoke rings... A defect quote of 5% is not small.

kiu77 commented 1 year ago

@lunanigra Did you check if in setup -> system config CE is set to GPIO4?

lunanigra commented 1 year ago

After changing the pin assignment of CE/CS the data rate is shown with 2 mbps again. I tried three different nRF24L01+ modules. Of course no idea if they are working; but at least one was newly ordered. Overall no change...

image image

lumapu commented 1 year ago

I don't understand why the datarate goes up to 2Mbps

fsck-block commented 1 year ago

I don't understand why the datarate goes up to 2Mbps

After facing this issue I did some investigation. It happen's in method HMRadio::sendPacket. After calling mNrf24.stopListening() the datarate was changed from 250kbps to 2Mbps. Did also a check of the library function but no obvious bug.
Tried to set the datarate back to 250kbp at this point but without success.

lumapu commented 1 year ago

@fsck-block thank you for pointing out that setting the data rate back does not fix the issue. This was my next attempt but now I don't have to test this.

lumapu commented 1 year ago

any updates here? @lunanigra

lunanigra commented 1 year ago

@lumapu, same as before - data rate goes to 2 mbps and "RX no answer".

Besides this I don't see anything wrong. Maybe it is a hardware issue. But quite strange as there are no clear other errors.

Any experiences how important the elko is? I tried with and without... Just wondering if needed at all?

kiu77 commented 1 year ago

@lunanigra I think your theory is right: a hardware defect. The Elko can't be responsible for changing the data rate.

lunanigra commented 1 year ago

As I tried three nRF24L01+ modules so far wondering what kind of hardware defect it might be?

Something on ESP32 itself or the wiring? But as the nRF24L01+ is shown as connected it must be small or quite strange defect...

lumapu commented 1 year ago

can't imagine that 3 NRF modules should be defect. Do you provide 3.3V to the modules (not 5V)? Have you tried another ESP as well? Can you check that the chip select works properly?

kiu77 commented 1 year ago

Can you show a photo of your setup?Am 02.10.2023 um 13:51 schrieb Lukas Pusch @.***>: can't imagine that 3 NRF modules should be defect. Do you provide 3.3V to the modules (not 5V)? Have you tried another ESP as well? Can you check that the chip select works properly?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

lunanigra commented 1 year ago

@kiu77, the nRF24L01+ is connected to 3.3V. Also don't see anything wrong on CS.

But will set up everything from scratch the next days. Perhaps there really something with the breadboard wiring.

Btw., is the elko really useful? Or in which cases it is needed... When using bad power supply?

kiu77 commented 1 year ago

Some say so. I have it on my PCB. All I can say is that my system works. And that I hat 2 dead or problematic ESP32 and 2 nRF24+ until now (out of over 20 pieces of each).

lunanigra commented 1 year ago

After putting the used components on PCB it looks stable. Surprisingly, as I never had issues on breadboard before. However, thanks for support :)

kiu77 commented 1 year ago

So good luck!