HI i have PIP-3024MK need oem firmware i make update from file  PIP-5048MK now it's brick any help !!??

2 hours ago, naeemvip3 said:

i make update from file  PIP-5048MK now it's brick

I'm sorry to hear that. It's scandalous that the inverter lets you do this.

I can confirm that Axpert King 5kW firmware is only for 5kW models; it's not one of the ones that handles two power levels with the same firmware.

So the only way out of your problem is to load 3kW firmware. Alas, though I have nearly a dozen King main firmwares, they are all 5kW.

You will have to get a firmware update from your supplier.

The only alternative would be to replace the control board with a new one, specifically intended for 3kW Kings, pre-loaded with 3kW firmware. That's going to be even harder, I suspect. There are many variations on control boards, and many of the variations are quite subtle. And of course, the firmware loaded onto the processor is invisible.

I wish my news could be better.

thank for ur answer i wish found the firmware more easy

finally i found the firmware for KING 3KW and it's work very good and this file 

U1 51.97

U2 2.70 

PIP-3024MK CPUv51.97 MCU02.70.rar

2 hours ago, naeemvip3 said:

finally i found the firmware for KING 3KW and it's work very good

Excellent, and thanks for the file.

Dare I ask where you found it?

02.70 is the same as the latest removable display firmware for 5kW Kings and VM IIIs.

51.97 appears to be a compilation of the same source code as 71.97, with different #defines or -Dblah arguments to the compile. The dsp.hex files have the same date; the 24V firmware 23 minutes before the 48V firmware. One surprising difference is that the period for EPWM5 is halved in the 24 V firmware, and not in the 48 V firmware. I forget what the EPWM5 (Extended PWM channel 5) port is used for in the Kings. One of the commands (QMCHGCR) has two extra fields in the 48 V firmware, because the maximum charging current has two more options (130 and 140 A). I only got about 20% through the comparison.

On 2022/08/29 at 2:15 PM, Coulomb said:

Excellent, and thanks for the file.

Dare I ask where you found it?

02.70 is the same as the latest removable display firmware for 5kW Kings and VM IIIs.

51.97 appears to be a compilation of the same source code as 71.97, with different #defines or -Dblah arguments to the compile. The dsp.hex files have the same date; the 24V firmware 23 minutes before the 48V firmware. One surprising difference is that the period for EPWM5 is halved in the 24 V firmware, and not in the 48 V firmware. I forget what the EPWM5 (Extended PWM channel 5) port is used for in the Kings. One of the commands (QMCHGCR) has two extra fields in the 48 V firmware, because the maximum charging current has two more options (130 and 140 A). I only got about 20% through the comparison.

Hello Coulomb, so can I use this  MCU (2.70) with my Axpert King? I've  bricked my remote panel with 2.66a and after replace I got 2.61 FW in it. Could not find this FW anywhere....

Thx

On 2022/09/08 at 9:14 PM, Sauron IO said:

Hello Coulomb, so can I use this  MCU (2.70) with my Axpert King?

Yes, I believe so.

 

On 2022/09/08 at 9:14 PM, Sauron IO said:

I've  bricked my remote panel with 2.66a

I can't understand that. Perhaps it had slow optos??

On 2022/09/08 at 9:14 PM, Sauron IO said:

and after replace I got 2.61 FW in it.

Do you mean you obtained a replacement removable display, and that replacement came with 02.61? That is indeed old, and 02.70 should work in its place.

I've flashed 2.66A to my remote panel and it went dead (and yes, I've tried all the tricks to flash again  ). 
Thank you, so I'll try to flash this version. BTW I have 72.00 firmware in my King 5k, do you have plans to patch this version for premature float bug?

Thx again for your reply

6 hours ago, Sauron IO said:

BTW I have 72.00 firmware in my King 5k, do you have plans to patch this version for premature float bug?

I'd like to, most especially if it fixes some long standing PV problems. But I've not seen a firmware update file for 72.00, so I'm still waiting.