Dear all,

 

I can successfully connect to the MPP Solar inverter model U5648MS inverter  to watchpower using the COM port.  However when I try to upgrade the firmware I get the following error: 

 

I can confirm that the COM port used is the correct comport and that this comport is also not used by any other application ( have also confirmed that watchpower is not running in the background).

 

The error message does not appear immediately but after a few seconds  ( I estimate 7-10 seconds)

 

What is the reason that I can establish a serial communication with watchpower but cannot upgrade the firmware?

 

Screech

On 2024/02/28 at 8:11 PM, Screech said:

The error message does not appear immediately but after a few seconds  ( I estimate 7-10 seconds)

My guess is that you have the wrong firmware update file. You might have the firmware update file for the '28066 DSP, while you have a '2809 DSP; or vice versa.

What main firmware do you have now, and what are you trying to update to?

Edit:

Quote

What is the reason that I can establish a serial communication with watchpower but cannot upgrade the firmware?

If I'm right, it's because the reflash tool is sending command A to the inverter, but the inverter's firmware will only respond to command B. These are special commands for initiating the reflash process.

Edit 2:

And yes, if I'm right, the error message is very unhelpful and confusing.

Edited February 29, 20242 yr by Coulomb

12 hours ago, Coulomb said:

What main firmware do you have now, and what are you trying to update to?

I am currently running:

Main cpu : 74.01

Remote panel: 30.01

 

And I am trying to update to:

Main cpu : 74.04

Remote panel: 30.07

 

 

I also have a feeling that they have send me the wrong firmware upgrade package but the support of MPP solar is very slow in responding back (takes almost 2 days mail exhcanges).

 

Is there another reliable way of getting teh firmware and how can I know which DSP  I have etc.

 

According to the vendor after updating those two firmwares I will be able to switch between utility and battery base on the battery SOC (when battery is communicating through the BMS port) instead of its voltage which is the functionality that I am looking for.

 

Regards,

 

 

 

 

Edited March 1, 20242 yr by Screech

12 hours ago, Screech said:

I am currently running:

Main cpu : 74.01

Remote panel: 30.01

 

And I am trying to update to:

Main cpu : 74.04

Remote panel: 30.07

So this is a U5648MS? (Also known as an Axpert MKS 4 5.6 kW).

As far as I know, 74.04 is a '2809 firmware, and the reflash tool appears to be old-style with no way to enter a hex file name (used the fixed name dsp.hex in the same folder as the executable). So I'm puzzled why in your screen capture, the word "28066" appears in the title bar of the application's window. Maybe they supplied the wrong reflash tool?

You may care to diff the 74.04 dsp.hex in your firmware update file with the one here:

You might also care to try that firmware update file's reflash tool.

To tell what DSP you have,  usually you use the main firmware to decide, and I have firmwares 74.02, 74.03, and 74.04, all of which I've labelled as '2809. If you are prepared to open your case, you can tell the DSP (at least '2809 versus '28066) using the Chipset Chatter post.

If you post a link or attachment to your firmware update file, or PM me a link or attachment, I can compare them here, and/or determine whether the firmware is for a '2809 or a '28066.

13 hours ago, Screech said:

According to the vendor after updating those two firmwares I will be able to switch between utility and battery base on the battery SOC (when battery is communicating through the BMS port) instead of its voltage which is the functionality that I am looking for.

Alas, my notes say that a firmware has to respond to a QDOP command for this to work, and 74.04 does not appear to support that command. Maybe that means that there are different 74.04 firmwares; it would not be the first time. But also, I don't recall how I decided that the QDOP command  was involved; I might be wrong there. I don't have display firmware version 30.07 to check, either.