question

rodolfo avatar image
rodolfo asked

Error 1342

Will Victron solve Error 1342 in remote firmware update in MK2 devices soon?

vrm firmware update
1 comment
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nickdb avatar image nickdb ♦♦ commented ·
Could you be more detailed in your question, this really is vague. Did you mean MP2? Please spell it out with some screenshots, detailing your system components, versions etc.


moving to questions and answers section.

0 Likes 0 ·
2 Answers
rodolfo avatar image
rodolfo answered ·

https://community.victronenergy.com/questions/128704/remote-firmware-update-1342-error.html

1674397109860.png


1674397109860.png (202.1 KiB)
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

nickdb avatar image
nickdb answered ·

The topic clearly explains it is a limitation of the old CCGX hardware, with the OP confirming a new one works.

It is also clearly documented in limitations and requirements section of the VE BUS remote firmware updates doc:

1.2 Limitations and requirements

  • Minimum already installed VE.Bus firmware version must be 426

  • There must be no VE.Bus BMS connected to the VE.Bus network, and also no Digital Multi Control (DMC) panel. See section 2.2 for more information.

  • In case of a Color Control GX (CCGX), it must have serial number HQ1707 or newer: see FAQ Q2 for how to check this.

  • In case of another GX Device, ie. a Cerbo, Venus GX, or otherwise, there is no minimum hardware version - they all meet the requirements.

  • Venus OS firmware must be 2.65 or later.

  • Two Way Communication must be enabled in the VRM menu of the GX device


Closing topic as duplicate.



1 comment
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

rodolfo avatar image rodolfo commented ·

I know everything you say.... nothing new. My question again:

Will Victron solve this problem via firmware, or it is impossible to solve it without changing the CCGX for a new one?

0 Likes 0 ·

Related Resources

Additional resources still need to be added for this topic