Mbaz88

Thanks a lot for the clear explanation, that really helps me understand what’s going on. I checked on the inverter display and it shows: U1 30.22.0. The model is a SAKO Sunpolo 8.2 kW (48 V). Unfortunately, after only about 2 months of use it went into fault F90, just as you described with the clone detection. I have already tried flashing with different .inv files through HID USB, but every time it fails with the “Firmware update check ready error”. It’s disappointing that the seller didn’t mention this, and after spending this much money I now realize they sold me a clone unit that locks up after a short time. Could you please let me know if there’s a patched firmware available for U1 30.22.0 that bypasses the clone check, or if there’s another way to rescue this inverter? Thanks again for your guidance — it’s frustrating what the seller did, but I really appreciate the help from this community.

Hello everyone, I have a Sunpolo 8.2 kW inverter (label: 48 V battery, 8.2 kW / 12 kW rated power) which I believe is an Axpert MAX 8 kW clone. After just 2 months of working fine, the inverter suddenly started showing F90 fault error on the display and is now unusable. When I connect it to the PC, it only shows up as HID (no COM port), so I have been trying to re-flash the firmware using ArenalINVReflashTool (Rev00.06). So far I have tried: HV8K firmwares (72.xx) → fails with “Firmware update check ready error”. VP5K firmwares (92.xx) → same error. MAX II firmwares (81.xx) → same error. The inverter reacts when I start the update (LCD asks to confirm), but then fails with the error above and goes into fault 32. I suspect I am using the wrong .inv firmware for this specific model. My questions: Which is the correct DSP firmware version (.inv) for the Axpert MAX 8 kW / Sunpolo 8.2 kW 48 V model? Does anyone here have a working .inv firmware package (U1 90.06 or 92.06 for MAX 8 kW 48 V) that is accepted by the HID tool? Once flashed, will this restore the COM port, or is HID the only method for this model? I would really appreciate any guidance or a link to the correct firmware. Thank you!