HM-1500 with Firmware V01.00.30 after uograde from 00.18 #1888

yzffrog · 2024-04-05T20:31:21Z

What happened?

after the firmware update at the inverter every read request from the openDTU sets the actual earning value to 0 (resets the value)

To Reproduce Bug

every read request

Expected Behavior

as usual - not setting the value to 0

Install Method

Pre-Compiled binary from GitHub

What git-hash/version of OpenDTU?

v24.3.31

Relevant log/trace output

No response

Anything else?

No response

The text was updated successfully, but these errors were encountered:

tbnobody · 2024-04-05T20:35:29Z

after the firmware update at the inverter every read request from the openDTU sets the actual earning value to 0 (resets the value)

I don't know what you are meaning. How did you do the firmware update of the inverter? Are you using two DTUs (original + DIY) at the same time?
Did you do the firmware update at night? The inverter is not reachable at night. Therefor no values can be read.

yzffrog · 2024-04-05T20:37:28Z

after the firmware update at the inverter every read request from the openDTU sets the actual earning value to 0 (resets the value)

I don't know what you are meaning. How did you do the firmware update of the inverter? Are you using two DTUs (original + DIY) at the same time? Did you do the firmware update at night? The inverter is not reachable at night. Therefor no values can be read.

The firmware update on the inverter was done by HM OTA - cause heve been unspecific HW-Errors i reported to HM , after i noticed the issue i activated the HM-DTU so could see there also the value reset is done, using the HM DTU only everything works fine, usuing openDTU only the reset is performed

tbnobody · 2024-04-05T20:44:05Z

every read request from the openDTU sets the actual earning value to 0 (resets the value)

if every read request set's it to zero, how do you know that it is unequal zero? If it is set to zero it has to be greater then zero at a specific time. Please explain a little bit more detailed.

And also provide a console log with the transmitted data to doublecheck what's delivered from the inverter towards the DTU.

yzffrog · 2024-04-05T20:46:17Z

every read request from the openDTU sets the actual earning value to 0 (resets the value)

if every read request set's it to zero, how do you know that it is unequal zero? If it is set to zero it has to be greater then zero at a specific time. Please explain a little bit more detailed.

And also provide a console log with the transmitted data to doublecheck what's delivered from the inverter towards the DTU.

I played around with request intervals so i can see data that is cleared after the next request

i an relatively sure the console log will not help, cause it seems to me the inverter software is the problem anyway i can perform this tomorrow at daytime..

yzffrog · 2024-04-06T09:10:20Z

that how the graph looks like - the field 'Tagesertrag'iss set to 0 on everey request from openDTU

tbnobody · 2024-04-06T09:59:53Z

Please provide a console log (as text, no screenshot)
Please provide screenshot of the Device Info Dialog

yzffrog · 2024-04-06T20:07:09Z

<div id="app" data-v-app=""><nav class="navbar navbar-expand-md fixed-top bg-body-tertiary" data-bs-theme="dark" style=""><div class="container-fluid"><a href="http://192.168.88.26/" class="navbar-brand" style="display: flex; height: 30px; padding: 0px;"><svg width="30" height="30" viewBox="0 0 16 16" fill="currentColor" role="img" focusable="false" class="d-inline-block align-text-top text-warning"></svg></a></div></nav></div><a href="http://192.168.88.26/" class="navbar-brand" style="display: flex; height: 30px; padding: 0px;"><span style="margin-left: 0.5rem;"> OpenDTU </span></a><div class="collapse navbar-collapse" id="navbarNavAltMarkup"><ul class="navbar-nav navbar-nav-scroll d-flex me-auto flex-sm-fill"><li class="nav-item"><a href="http://192.168.88.26/" class="nav-link">Live View</a></li><li class="nav-item dropdown"><a class="nav-link dropdown-toggle" href="http://192.168.88.26/settings/device#" id="navbarScrollingDropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Settings</a></li><li class="nav-item dropdown"><a class="nav-link dropdown-toggle" href="http://192.168.88.26/settings/device#" id="navbarScrollingDropdown" role="button" data-bs-toggle="dropdown" aria-expanded="false">Info</a></li><li class="nav-item"><a href="http://192.168.88.26/about" class="nav-link">About</a></li><li class="flex-sm-fill"></li><li class="nav-item dropdown me-2">*</li></ul></div><li class="nav-item dropdown me-2"></li><form class="d-flex" role="search"></form><nav class="navbar navbar-expand-md fixed-top bg-body-tertiary" data-bs-theme="dark" style=""><div class="container-fluid"><div class="collapse navbar-collapse" id="navbarNavAltMarkup"><ul class="navbar-nav navbar-nav-scroll d-flex me-auto flex-sm-fill"><form class="d-flex" role="search"></form></ul></div></div></nav><div class="container-xxl" role="main"><div class="page-header"><div class="row"><div class="col-sm-11"><h1>Device-Manager </h1></div></div></div><form><nav><div class="nav nav-tabs" id="nav-tab" role="tablist"></div></nav></form></div><div class="tab-pane fade show active" id="nav-pin" role="tabpanel" aria-labelledby="nav-pin-tab" tabindex="0"><div class="card"><div class="card-body"><div class="row mb-3"><label for="inputPinProfile" class="col-sm-2 col-form-label">Selected profile:</label><div class="col-sm-10"></div></div></div></div></div><div class="tab-content" id="nav-tabContent"><div class="tab-pane fade show active" id="nav-pin" role="tabpanel" aria-labelledby="nav-pin-tab" tabindex="0"><div class="card"><div class="card-body"><div class="row mb-3"><div class="col-sm-2"></div><div class="col-sm-10"></div></div><div class="alert alert-danger mt-3" role="alert">Your

device may stop responding if you select an incompatible profile. In
this case, you must perform a deletion via the serial interface.

Connection overview

Category	Name	Selected	Active
Cmt	clk		-1
cs		-1
fcs		-1
gpio2		-1
gpio3		-1
sdio		-1
Display	clk	22	22
cs		255
data	21	21
reset		255
type	3	3
Eth	clk_mode	0	0
enabled	false	false
mdc	-1	-1
mdio	-1	-1
phy_addr	-1	-1
power	-1	-1
type	0	0
Led	led0		-1
led1		-1
Nrf24	clk	18	18
cs	5	5
en	4	4
irq	16	16
miso	19	19
mosi	23	23

OpenDTU

[Live View](http://192.168.88.26/)
[Settings](http://192.168.88.26/settings/device#)
[Info](http://192.168.88.26/settings/device#)
[About](http://192.168.88.26/about)
*

Device-Manager
Selected profile:
Your device may stop responding if you select an incompatible profile. In this case, you must perform a deletion via the serial interface.
Connection overview
Category Name Selected Active
Cmt clk -1
cs -1
fcs -1
gpio2 -1
gpio3 -1
sdio -1
Display clk 22 22
cs 255
data 21 21
reset 255
type 3 3
Eth clk_mode 0 0
enabled false false
mdc -1 -1
mdio -1 -1
phy_addr -1 -1
power -1 -1
type 0 0
Led led0 -1
led1 -1
Nrf24 clk 18 18
cs 5 5
en 4 4
irq 16 16
miso 19 19
mosi 23 23

tbnobody · 2024-04-06T21:49:41Z

Please provide a console log (as text, no screenshot)

Please also provide a screenshot of the Device Info Dialog

Sorry, I meant the Inverter info dialog

yzffrog · 2024-04-07T21:07:05Z

hm, sorry i cannot idetify where i can find the inverter info dialog, regaring console log: when i trigger the request and afterwards open the console log - will this show the info you need ?

MetaChuh · 2024-04-07T22:45:12Z

@yzffrog

please click here:
(follow the red arrow)

greetings,
metachuh

yzffrog · 2024-04-08T07:34:58Z

Inverter Info

Serial | 116183063371 -- | -- Production Year | 2022 Production Week | 30 Model | Unknown model! Please report the "Hardware Part Number" and model (e.g. HM-350) as an issue here. Detected max. Power | 0 W Bootloader Version | 0.0.0 Firmware Version | 0.2.56 Firmware Build Date | 1911-09-09 11:52:32 Hardware Part Number | 124097 Hardware Version | 00.00 Inverter Info Serial 116183063371 Production Year 2022 Production Week 30 Model Unknown model! Please report the "Hardware Part Number" and model (e.g. HM-350) as an issue [here](https://github.com/tbnobody/OpenDTU/issues). Detected max. Power 0 W Bootloader Version 0.0.0 Firmware Version 0.2.56 Firmware Build Date 1911-09-09 11:52:32 Hardware Part Number 124097 Hardware Version 00.00

looks not as i expected...

Did it again...better

Inverter Info

yzffrog · 2024-04-08T17:45:08Z

regaring console log: when i trigger the request and afterwards open the console log - will this show the info you need ?

yzffrog · 2024-04-09T06:35:17Z

Console:
Fetch inverter: 116183063371
08:30:37.808 > TX RealTimeRunData Channel: 3 --> 15 83 06 33 71 80 16 73 88 80 0B 00 66 14 E0 8F 00 00 00 00 00 00 00 00 D2 4C B7
08:30:38.362 > RX Period End
08:30:38.362 > All missing
08:30:38.362 > Nothing received, resend whole request
08:30:38.362 > TX RealTimeRunData Channel: 23 --> 15 83 06 33 71 80 16 73 88 80 0B 00 66 14 E0 8F 00 00 00 00 00 00 00 00 D2 4C B7
08:30:38.407 > Interrupt received
08:30:38.461 > RX Channel: 3 --> 95 83 06 33 71 83 06 33 71 01 00 01 01 C3 00 C6 00 CC 03 7C 03 99 00 00 90 A8 80 | -80 dBm
08:30:38.507 > Interrupt received
08:30:38.552 > RX Channel: 61 --> 95 83 06 33 71 83 06 33 71 02 00 00 94 FB 00 53 00 54 01 9F 00 95 00 9E 02 6C 04 | -80 dBm
08:30:38.598 > Interrupt received
08:30:38.650 > RX Channel: 61 --> 95 83 06 33 71 83 06 33 71 03 02 90 00 00 89 1A 00 00 8A 36 00 3D 00 3F 09 47 67 | -80 dBm
08:30:38.894 > RX Period End
08:30:38.894 > Last missing
08:30:38.894 > Request retransmit: 4
08:30:38.894 > TX RequestFrame Channel: 40 --> 15 83 06 33 71 80 16 73 88 84 3B
08:30:38.944 > Interrupt received
08:30:38.995 > RX Channel: 3 --> 95 83 06 33 71 83 06 33 71 84 13 84 0B 77 00 DC 00 7C 03 E5 00 E5 00 03 3C 7F 19 | -80 dBm
08:30:39.048 > RX Period End
08:30:39.048 > Success
08:30:39.256 > TX AlarmData Channel: 61 --> 15 83 06 33 71 80 16 73 88 80 11 00 66 14 E0 8F 00 00 00 00 00 00 00 00 08 57 6C
08:30:40.080 > RX Period End
08:30:40.080 > All missing
08:30:40.080 > Nothing received, resend whole request
08:30:40.080 > TX AlarmData Channel: 75 --> 15 83 06 33 71 80 16 73 88 80 11 00 66 14 E0 8F 00 00 00 00 00 00 00 00 08 57 6C
08:30:40.866 > RX Period End
08:30:40.866 > All missing
08:30:40.866 > Nothing received, resend whole request
08:30:40.866 > TX AlarmData Channel: 3 --> 15 83 06 33 71 80 16 73 88 80 11 00 66 14 E0 8F 00 00 00 00 00 00 00 00 08 57 6C
08:30:41.664 > RX Period End
08:30:41.664 > All missing
08:30:41.664 > Nothing received, resend whole request
08:30:41.664 > TX AlarmData Channel: 23 --> 15 83 06 33 71 80 16 73 88 80 11 00 66 14 E0 8F 00 00 00 00 00 00 00 00 08 57 6C
08:30:42.466 > RX Period End
08:30:42.466 > All missing
08:30:42.466 > Nothing received, resend whole request
08:30:42.466 > TX AlarmData Channel: 40 --> 15 83 06 33 71 80 16 73 88 80 11 00 66 14 E0 8F 00 00 00 00 00 00 00 00 08 57 6C
08:30:42.512 > Interrupt received
08:30:42.559 > RX Channel: 75 --> 95 83 06 33 71 83 06 33 71 81 11 00 00 01 D8 C4 18 | -80 dBm
08:30:43.219 > RX Period End
08:30:43.219 > Success

yzffrog · 2024-04-09T06:36:06Z

Yield day is reset.

yzffrog · 2024-04-15T09:57:17Z

Anything i can provide in addition ? Any news ? kr

yzffrog · 2024-05-05T19:57:28Z

Thats what i did its within zje github dialogue kr greg Am Mo., 8. Apr. 2024 um 00:45 Uhr schrieb MetaChuh ***@***.***

…

: @yzffrog <https://github.com/yzffrog> please click here: (follow the red arrow) Bildschirmfoto.2024-04-08.um.00.40.17.png (view on web) <https://github.com/tbnobody/OpenDTU/assets/45773305/da2ac101-7527-4d2d-8c83-2bcff39d767b> greetings, metachuh — Reply to this email directly, view it on GitHub <#1888 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BG7YX7LESY6IIJS4TXS47HDY4HEA5AVCNFSM6AAAAABFZX2RMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGYZTEOBSGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

yzffrog · 2024-05-24T08:31:29Z

yzffrog · 2024-05-24T08:32:28Z

sorry seems was a misundrerstanding,the output is much better readable now inverter has still the same issue

yzffrog added the bug Something isn't working label Apr 5, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

HM-1500 with Firmware V01.00.30 after uograde from 00.18 #1888

HM-1500 with Firmware V01.00.30 after uograde from 00.18 #1888

yzffrog commented Apr 5, 2024

tbnobody commented Apr 5, 2024

yzffrog commented Apr 5, 2024 •

edited

Loading

tbnobody commented Apr 5, 2024

yzffrog commented Apr 5, 2024 •

edited

Loading

yzffrog commented Apr 6, 2024

tbnobody commented Apr 6, 2024

yzffrog commented Apr 6, 2024

tbnobody commented Apr 6, 2024

yzffrog commented Apr 7, 2024

MetaChuh commented Apr 7, 2024

yzffrog commented Apr 8, 2024 •

edited

Loading

yzffrog commented Apr 8, 2024

yzffrog commented Apr 9, 2024

yzffrog commented Apr 9, 2024

yzffrog commented Apr 15, 2024

yzffrog commented May 5, 2024 via email

yzffrog commented May 24, 2024

yzffrog commented May 24, 2024 •

edited

Loading

HM-1500 with Firmware V01.00.30 after uograde from 00.18 #1888

HM-1500 with Firmware V01.00.30 after uograde from 00.18 #1888

Comments

yzffrog commented Apr 5, 2024

What happened?

To Reproduce Bug

Expected Behavior

Install Method

What git-hash/version of OpenDTU?

Relevant log/trace output

Anything else?

tbnobody commented Apr 5, 2024

yzffrog commented Apr 5, 2024 • edited Loading

tbnobody commented Apr 5, 2024

yzffrog commented Apr 5, 2024 • edited Loading

yzffrog commented Apr 6, 2024

tbnobody commented Apr 6, 2024

yzffrog commented Apr 6, 2024

tbnobody commented Apr 6, 2024

yzffrog commented Apr 7, 2024

MetaChuh commented Apr 7, 2024

yzffrog commented Apr 8, 2024 • edited Loading

Inverter Info

Inverter Info

yzffrog commented Apr 8, 2024

yzffrog commented Apr 9, 2024

yzffrog commented Apr 9, 2024

yzffrog commented Apr 15, 2024

yzffrog commented May 5, 2024 via email

yzffrog commented May 24, 2024

yzffrog commented May 24, 2024 • edited Loading

yzffrog commented Apr 5, 2024 •

edited

Loading

yzffrog commented Apr 5, 2024 •

edited

Loading

yzffrog commented Apr 8, 2024 •

edited

Loading

yzffrog commented May 24, 2024 •

edited

Loading