# Using VE direct for FW update of MPPT 100/20

**URL:** <https://community.victronenergy.com/t/using-ve-direct-for-fw-update-of-mppt-100-20/58167>\
**Category:** DIY\
**Tags:** expert, firmware\_update, mppt\_controllers\
**Created:** [19 May 2026 11:18 UTC](https://community.victronenergy.com/t/using-ve-direct-for-fw-update-of-mppt-100-20/58167 "2026-05-19T11:18:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ariyosko](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@ariyosko](https://community.victronenergy.com/u/ariyosko)\
**Post date:** [19 May 2026 11:18 UTC](https://community.victronenergy.com/t/using-ve-direct-for-fw-update-of-mppt-100-20/58167/1 "2026-05-19T11:18:10Z")

</div>

Hello.

I am communicating with my MPPT 100/20 over a USB cable an VE direct.

I am not seeing documentation for doing FW update over this channel. Is it possible? If yes, where is the protocol documented?

Thanks.

---

<div class="post-metadata">

**Author:** ![M\_Lange](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/m_lange/32/16_2.png) [@M\_Lange](https://community.victronenergy.com/u/M_Lange)\
**Post date:** [19 May 2026 11:24 UTC](https://community.victronenergy.com/t/using-ve-direct-for-fw-update-of-mppt-100-20/58167/2 "2026-05-19T11:24:32Z")

</div>

Just use VictronConnect?

---

<div class="post-metadata">

**Author:** ![ariyosko](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@ariyosko](https://community.victronenergy.com/u/ariyosko)\
**Post date:** [19 May 2026 12:25 UTC](https://community.victronenergy.com/t/using-ve-direct-for-fw-update-of-mppt-100-20/58167/3 "2026-05-19T12:25:53Z")

</div>

Hi Matthias, and thanks.

The product is deployed in the field without physical access and is controlled by a Linux machine. I tried (in the office) VictronConnect for Linux in two different Ubuntu setups - in a VirtualBox VM and on a native machine running Ubuntu. On the VM the app hangs immediately upon activation and crashes. On the native machine it never starts. So, I did not consider using VictronConnect a stable option on the controlling machine. Using a workaround like an iPad in remote is also not possible without additional HW (GX) plus cloud connectivity. This will bring the BOM price way over what we can afford, and also maintaining 3rd party connectivity is not acceptable for us.

If you have other venues I did not consider I will be happy to know, but the need here is to do it with only local connectivity of a Linux machine, ARM architecture (although the experiments I did above were done on x86 machines, and since they did not succeed I did not continue to solving the Architecture issue using simulation).

Thanks.

---

<div class="post-metadata">

**Author:** ![nickdb](https://dub1.discourse-cdn.com/victron/user_avatar/community.victronenergy.com/nickdb/32/51440_2.png) [@nickdb](https://community.victronenergy.com/u/nickdb)\
**Post date:** [19 May 2026 13:12 UTC](https://community.victronenergy.com/t/using-ve-direct-for-fw-update-of-mppt-100-20/58167/4 "2026-05-19T13:12:29Z")

</div>

Your choices for updating is either via vrm or Victron connect.  
The (somewhat unsupported) linux variant should work but you may need to try a beta - search for beta victron connect for the link.

---

<div class="post-metadata">

**Author:** ![chrigu](https://avatars.discourse-cdn.com/v4/letter/c/ba9def/32.png) [@chrigu](https://community.victronenergy.com/u/chrigu)\
**Post date:** [19 May 2026 14:09 UTC](https://community.victronenergy.com/t/using-ve-direct-for-fw-update-of-mppt-100-20/58167/5 "2026-05-19T14:09:22Z")

</div>

Im using VC on both Debian 13 and LinuxMint, works fine but hangs upon starting on Debian. Looking in the logs, VC is trying to access some bluetooth protocol for about a minute but then errors out on that. I assume its because i dont have a bluetooth adapter on that PC.

Have you looked into the logs to find out why it crashes?
