HMS2000 Error ID 52 Unknown

fred777 commented 4 months ago

What happened?

Not sure if this is being tracked already (no results according to search) - but on HMS inverters there seems to exist an error event with ID 52 that has no description:

To Reproduce Bug

no idea

Expected Behavior

meaningful description being shown instead of just "unknown"

Install Method

Pre-Compiled binary from GitHub

What git-hash/version of OpenDTU?

c144b68

Relevant log/trace output

No response

Anything else?

No response

Please confirm the following

[X] I believe this issue is a bug that affects all users of OpenDTU, not something specific to my installation.
[X] I have already searched for relevant existing issues and discussions before opening this report.
[X] I have updated the title field above with a concise description.

tbnobody commented 4 months ago

If the descriptions shows "Unknown" it's not (yet) found out what it means. If you see something in a documentation or App I am happy to add the message.

schneeer commented 4 months ago

Hi. User manual:

211: No input

Check whether this port is connected to a PV module.
If a PV module is connected, check the DC cable connections between the connector and the PV module.

220: Input undervoltage Check the input voltage at the PV-3 connector.

52: unknown -> Please ask support.

Have you ever checked the connections? A comparison measurement with a voltage tester of the voltage on several modules could show whether a module is defective. Remember that you should not plug or unplug anything under load.

stefan123t commented 1 month ago

@fred777 I just checked the current v1.1.29 of the S-Miles Installer APK if they have any translations inside. https://apkpure.com/s-miles-installer/com.hm.hemaiInstall1

and yes there is warn_code.json (ns, zh_cn and en_us) as attached to #2258 which contains the following codes 211, 73, 72, 47, 46, 14, 13, 12, 11 as mentioned in https://github.com/tbnobody/OpenDTU/issues/1068#issuecomment-1752114118

  "211": {
    "ns": "mi.warn.name.211",
    "zh_cn": "PV3端口无输入",
    "en_us": "PV3 No input"
  },
...
  "73": {
    "ns": "mi.warn.name.73",
    "zh_cn": "过温降载功能启用",
    "en_us": "TW function enable"
  },
  "72": {
    "ns": "mi.warn.name.72",
    "zh_cn": "电网过频降载FW功能启用",
    "en_us": "FW function enable"
  },
  "71": {
    "ns": "mi.warn.name.71",
    "zh_cn": "电网过压降载VW功能启用",
    "en_us": "VW function enable"
  },
...
  "47": {
    "ns": "mi.warn.name.47",
    "zh_cn": "FB过流",
    "en_us": "FB overcurrent"
  },
  "46": {
    "ns": "mi.warn.name.46",
    "zh_cn": "FB过流",
    "en_us": "FB overvoltage"
  },
...
  "36": {
    "ns": "mi.warn.name.36",
    "zh_cn": "INV过流过压",
    "en_us": "INV overvoltage or overcurrent"
  },
...
  "14": {
    "ns": "mi.warn.name.14",
    "zh_cn": "电网相位突变",
    "en_us": "Grid phase mutation"
  },
  "13": {
    "ns": "mi.warn.name.13",
    "zh_cn": "电网频率突变",
    "en_us": "Grid frequency mutation"
  },
  "12": {
    "ns": "mi.warn.name.12",
    "zh_cn": "电网电压幅值大幅跌落",
    "en_us": "Grid voltage sharp drop"
  },
  "11": {
    "ns": "mi.warn.name.11",
    "zh_cn": "浪涌冲击",
    "en_us": "Grid voltage surge"
  },

And a lj_warn_code.json too, the latter being in simplified chinese only.

@fred777 I translated some of the missing Event IDs like 52, 53 from the chinese lj_warn_code.json:

"52_1": "1. 220V power connection line is disconnected\n2. 220V power relay is damaged", "52_2": "1. 220V control power supply is abnormal", "53_1": "1. External IO 24V power supply is abnormal", "53_2": "1. External IO 24V power supply is abnormal", "53_3": "1. Internal IO 24V power supply is abnormal", "53_4": "1. Internal IO 24V power supply is abnormal",

But I did not find 220 as mentioned by @schneeer here https://github.com/tbnobody/OpenDTU/issues/2090#issuecomment-2185254972

fred777 commented 1 month ago

Great! So let's hope that this was just a glitch and my NA relay is not damaged..... :man_shrugging:

At least the error did not pop up again since back then.

stefan123t commented 1 month ago

@fred777 yes 🤞 good luck and lets hope HOPE ! Well I just guessed based on the index of those explanations in lj_warn_code.json So this is not a direct Event code description but more of an indication what it may be.

tbnobody / OpenDTU