aamilev
Members
-
Joined
-
Last visited
Reputation Activity
-
aamilev reacted to Silviu TM in Home Assistant Inverter Integration OptionsHi,
Is there any chance of integrating Anenji hybrid inverters HHC 5.6kw in home assistant? Chinese brand with good behavior over the time... At least 2 years is running without any issue... It has CAN communication with WIFi dongle WIFi pro5, connected to dessmonitor.com servers or SmartEss on Android phones... Has also an RS485 communication port which is not used,at least not by me... Maybe there is a way of adding this inverter in home assistant,with additional hardware like ESP32 boards... Any suggestions? Thank you!
-
That's the serial number that results from the EEPROM losing its contents. Unfortunately it will probably lead to fault code 90 eventually. I don't know what causes the EEPROM to lose contents; possibly glitches on the power supply due to capacitors drying out.
I'm surprised that reflashing fixed it, even temporarily. Perhaps the EEPROM is gettting very bad. How long till fault code 90 is going to happen is also stored in the EEPROM.
It will be best to get the patched firmware running. Presumably, if you can reflash with factory firmware, then you should be able to run the patched firmware, unless I screwed up with the patching. It's a quite simple patch, so it's hopefully unlikely that I screwed up.
It's actually not all that hard to send a new serial number to EEPROM, it's basically one command, though you need ATE commands either side to force it through the display. Unfortunately, that on its own isn't enough to prevent fault code 90. But it's nice to be able to distinguish between the two inverters.
No. As above, the serial number on its own is easy enough, but to avoid fault code 90, you need other values set, and those other values are cryptographically hard. So the best way around that is the patched firmware, unless you have a setserial program for your particular serial number(s).
One of my inverters (installed in 2016) had this problem, and I was able to change the serial number back to the original. I run patched firmware all the time, so fault code 90 was never a problem. That was just after I changed some power supply capacitors. It was so bad that the inverter would restart every few seconds. It's been running fine now for 15 months.
-
aamilev got a reaction from esmail-kassir in Datalogger update/upgradeYes, I am able to change all Inverter Setting via Mobile App and Dessmonitor.com
-
aamilev got a reaction from esmail-kassir in Datalogger update/upgradeI am sorry for late reply.
TT updating their Dataloggers remotely by themselves, no need to do anything. I saw today Version is already 2488.
-
Hello all,
Good news. Finally succeded to re-flash my remote panel and make it work again!!!
These are the steps that I followed.
1 - Connect all (PC to Inverter via RS232 to USB cable) with no power supply given to the Inverter (No battery and No AC IN).
2 - Have RemotePanel_Reflash_MCU SW prepared on PC. (Correct COM port selected)
3 - Provide power supply to inverter (AC In) and immediately (only few seconds after) click on "Update MCU" button in RemotePanel_Reflash_MCU SW.
After steps 3 I started seeing that flash started. More or less after 10 minutes the flash was completed and LCD remote panel was working again.
Thank you guys for the support given. Probably this thread will be useable for someone that will experience same issue in the future.
-
aamilev got a reaction from Solar RO in Axpert chipset chatterPlease be aware that I fugured out that 12.21 is not applicable for both Chipsets!
I tested myself without success and return back to 112.19.
I chaged my Invertors to 11kW and Display doesn't matter the Inverter Rating. Displays can be changed.
-
aamilev got a reaction from Coulomb in Axpert chipset chatterPlease be aware that I fugured out that 12.21 is not applicable for both Chipsets!
I tested myself without success and return back to 112.19.
I chaged my Invertors to 11kW and Display doesn't matter the Inverter Rating. Displays can be changed.
-
aamilev reacted to stakoz in Tommatech 11KW firmware upgradeThank you @Coulomb in case i upgrade to the new 73.63 "as is" above but it does not work for the mppt sticking at 90v in gloomy days and/or the battery premature float bugs - would it be possible to downgrade then back to the patched (2)91.70, or should you then need to patch again the new 73.63 to be re-applied in the inverter?
Many thanks again .
-
aamilev reacted to Coulomb in Tommatech 11KW firmware upgradeYes, there is no problem going backwards in firmware version. Of course, you then lose any improvements that the new firmware brought.
-
aamilev reacted to Coulomb in Tommatech 11KW firmware upgradeThere are scattered changes. it was a bit of a pain to compare them. 73.63 does seem to be an evolution from 91.70.
The major change seems to be with the MPPT control code. 73.63 has some logic I don't recall seeing before, so it's possible that they've finally nailed the stuck at 90V issue. Though it seems to be to be a mishmash of ideas that they have already tried, so I'm not super confident.
As for whether it's worth patching, I think it's worth trying as is first. If it still doesn't solve the stuck at 90 V problem, I can reduce the current threshold as I have for earlier patches.
Huh. One of the changes is to avoid emitting a warning for EEPROM errors in 91.70, in the case of another warning to do with the I²C hardware. That avoidance code is missing in 73.63. But there are also initialisations of the I²C hardware missing; perhaps 73.63 uses software emulation of I²C (something that they seem to have to do with the GigaDevice display chips), and maybe this actually works more reliably than the hardware in the DSP. Hard to imagine, but possible I suppose. At least, there IS a difference with respect to EEPROM warnings, so that alone may make it worth using 73.63, patched or not.
-
aamilev reacted to Coulomb in Axpert chipset chatter@aamilev,
You've been more than generous and more than patient, sorry for the wait. Things are still frantic here, but I made time today for this patch. It should also be useful for @stakoz and presumably others. I wondered what patches to implement, perhaps even the changes found in 72.66. I decided the latter was too new and untested (by forum readers at least), so I decide to keep it simple and start with Georg's original 200 V patches. So this patched firmware has no resets or any attempt at shade management. Shade management is a great idea if you need it, but the present implementation seems to be very panel configuration specific.
This is patched firmware version 269.61, based on factory firmware version 69.61 for the Axpert Max 1 7.2 kW non-twin with the '28066 DSP chip. It fixes the premature float bug, hopefully there isn't a "never float" bug lurking. If there is, it's easily reversed. It also implements all @Georg594's original 200 V minimum MPPT patches (first applied to factory firmware 90.06). On the display, the main U1 firmware version should show as 69.61, but monitoring software and apps should show it as 269.61. Do not use with other models, even other Axpert Maxs, or even an Axpert Max II 7.2 kW. Do not use with a '2809 DSP chip; see the first post of this thread for details.
Use at your own risk.
dsp 269.61 Axpert Max 1 7.2kW '28066 patched.zip
-
aamilev got a reaction from Coulomb in Axpert chipset chatterGood day @Coulomb,
I certainly hope that You fix died Inverter and if is so that will be really highly appreciated if You can find a time to create a patched version from 69.61 or 69.60 for Axpert 7.2k MAX Plus HV 48MPPT as this for 291.70 for Axpert MAX 11kW to prevent the panels from being dragged down below 200 V (was 90 V)? THANK YOU VERY MUCH IN ADVANCE!...
-
aamilev reacted to sharkut in Axpert chipset chatterI Can confirm that fact. I have flash 112.xx version with 12.21 with success no brick 2 month ago.
But be careful since i don't open my display so i can't confirm chipset model.
But the best explaination seems that 12.21 is compatible with 2 chip model
-
aamilev got a reaction from raytry in Axpert chipset chatterAccording to information from TommaTech Support dated 11 Jan 2023, the latest version 12.21 is applicable for all Removable Displays with previous 12.xx or 112.xx version but so far is not confirmed yet in practise.
I am planning to re-flash one of my Displays with 112.19 with 12.21 in close future (after receive spare one on hands) and will post results after that.
If somebody already make such attempt already, please to share results too. Thank You in advance!
Remote_Panel_Reflash_MCU_12.21.rar
-
aamilev got a reaction from Smeagol in Axpert chipset chatterAccording to information from TommaTech Support dated 11 Jan 2023, the latest version 12.21 is applicable for all Removable Displays with previous 12.xx or 112.xx version but so far is not confirmed yet in practise.
I am planning to re-flash one of my Displays with 112.19 with 12.21 in close future (after receive spare one on hands) and will post results after that.
If somebody already make such attempt already, please to share results too. Thank You in advance!
Remote_Panel_Reflash_MCU_12.21.rar
-
aamilev got a reaction from Coulomb in Axpert chipset chatterAccording to information from TommaTech Support dated 11 Jan 2023, the latest version 12.21 is applicable for all Removable Displays with previous 12.xx or 112.xx version but so far is not confirmed yet in practise.
I am planning to re-flash one of my Displays with 112.19 with 12.21 in close future (after receive spare one on hands) and will post results after that.
If somebody already make such attempt already, please to share results too. Thank You in advance!
Remote_Panel_Reflash_MCU_12.21.rar