"MultiPlus 12/3000/120-16 (Product ID 1909) - firmware v159, GX Error #48, Not updatable (1342)

Q&A and troubleshooting
, , ,
1

Title: MultiPlus 12/3000/120-16 (Product ID 1909) - Firmware v159, GX Error #48, Not updatable (1342)

Hello,

I recently purchased a used MultiPlus 12/3000/120-16 (Product ID 1909) and I am trying to determine whether the unit can be brought up to date and fully unlocked.

Current system:

  • Cerbo GX MK2 (v3.73)
  • MultiPlus 12/3000/120-16
  • BMV-712 Smart (v4.19)
  • Three SmartSolar MPPT chargers (latest firmware)
  • Two 150Ah LiFePO4 batteries
  • VRM Remote Monitoring

The system is fully operational. The MultiPlus charges correctly, inverter operation works correctly, AC input and AC output work correctly, and the Cerbo communicates with the unit.

I have already:

  • Connected using a MK3-USB interface
  • Read the configuration with VEConfigure
  • Created a backup of the configuration
  • Updated Cerbo GX, BMV and all MPPTs to the latest firmware

However I have the following issues:

  1. Cerbo GX reports: “GX Error #48 - DVCC with incompatible firmware”

  2. VRM reports:

    • Installed firmware: v159
    • Latest firmware: v209
    • Status: “Not updatable (1342)”

  3. VEConfigure reports that the firmware does not support Assistants.

  4. The VE.Bus configuration appears to be password protected.

  5. The previous owner does not know the password and does not have the original VEConfigure file.

My questions are:

  1. Is GX Error #48 expected on a MultiPlus running firmware v159?

  2. Will upgrading from v159 to v209 normally resolve GX Error #48?

  3. Can the VE.Bus password protection be removed or reset?

  4. Can a dealer or Victron service partner remove the password protection?

  5. Can a completely new VEConfigure file overwrite the existing configuration?

  6. Can firmware be upgraded without access to the original VEConfigure file?

  7. Is there a recommended upgrade path for Product ID 1909 from firmware v159 to v209?

  8. Does the “Not updatable (1342)” message simply indicate that the firmware is too old for remote upgrade, or does it indicate another limitation?

Any advice would be greatly appreciated.

Thank you.

Best regards,

Christoffer Linnerud Norway

Screenshot_20260615_115129_Chrome
Screenshot_20260615_115129_Chrome1080×2340 197 KB

2

Yes

No

Is this the grid password? Yes. But there is usually no need to change that. What is the grid code set to?
How is your systen programmed now? Are you in a mobile installation?

The 209 will be the newest. But check your chip number on the board or the vrm under device list.

Yes, this will alter everything except the grid code.

3

Thank you.

This is a mobile marine installation on a boat, not a grid-tied installation.

Current system:

  • Cerbo GX MK2 (v3.73)
  • MultiPlus 12/3000/120-16, Product ID 1909, firmware v159
  • BMV-712 Smart
  • Three SmartSolar MPPTs
  • 12V 300Ah LiFePO4 battery bank with external BMS
  • MK3-USB interface available

The seller does not know the VE.Bus password and does not have the original VEConfigure file.

My goal is simply to update the firmware and fully configure the unit for my own installation.

If a new VEConfigure file can overwrite everything except the grid code, does that mean I can completely reconfigure the unit for my boat without knowing the original password?

The unit also appears to have been configured for AGM batteries by the previous owner.

If I upload a completely new VEConfigure file, will all charger settings, absorption voltage, float voltage, charge algorithm and battery-related settings be replaced by my new configuration?

In other words, can I safely convert the unit from its previous AGM setup to a LiFePO4 setup without knowing the original password?

Also, where can I find the chip number in VRM? I can only see Product ID 1909 and firmware 1909159.

4

Correct. It just won’t allow that one alteration. The only time it might possibly be an issue is generator acceptance if you have one.

Great. Its enough for me to know you can’t go higher than 209. But if you can ignore the incompatible error then you will be fine.

5

Thank you.

Just to make sure I understand correctly:

You confirmed that upgrading from firmware v159 to v209 will not normally resolve GX Error #48.

Does that mean GX Error #48 is expected to remain even if I upgrade to the latest available firmware for Product ID 1909?

If so, is GX Error #48 only a warning related to firmware compatibility, or does it mean that some DVCC functionality is actually unavailable or restricted?

In other words, can I safely ignore the warning and expect all normal charging, inverter and DVCC functions to work correctly in my system?

Thank you for your help.

6

[[quote=“Christoffer , post:5, topic:59289, username:Havsorf”]
You confirmed that upgrading from firmware v159 to v209 will not normally resolve GX Error #48.

Does that mean GX Error #48 is expected to remain even if I upgrade to the latest available firmware for Product ID 1909?
[/quote]

Yes for both

quote=“Christoffer , post:5, topic:59289, username:Havsorf”]
DVCC functionality is actually unavailable or restricted
[/quote]

You shouldn’t use ut if the inverter does not meet the minimum requirements. Which it doesn’t hence the error.

See 2 here.

Are your batteries CAN managed or drop in lead replacement types?
If they aren’t, since you are not using ess, then each component follows its programming anyway. The battery bank should be fine and everything will charge correctly if the set up is good.

[That being said i know people who have been running for years with that error and haven’t experienced damage to their drop in replacement batteries.]

7

Thank you, that makes sense.

One final question:

What exactly is causing GX Error #48 on Product ID 1909?

Is it simply because this generation of MultiPlus does not fully support all DVCC functions required by newer GX devices, or is there another specific limitation that triggers the warning?

I am trying to understand whether the warning represents an actual functional limitation in the system, or simply a compatibility warning that can safely be ignored.

8

The older firmware doesn’t respond to the DVCC functions/information as far as i know.
And the chip 1909 can’t take the newer firmware needed.

If you switch off DVCC then the error should clear.