Viewing posts with category: Firmware & Software

VictronConnect v1.9

Good morning! A short post, as I should be spending my time swimming with the kids instead of writing blogposts. 😉

Change log v1.9:

  • Phoenix Inverter: Hide “Low battery shut down” setting when dynamic cutoff is enabled.
  • BlueSolar MPPT: Make possible to select 36 and 48V battery voltage on BlueSolar MPPT 150/35 rev2
  • BMV: Include BMV-70x firmware v3.08 update

And the previous one, since I had not made a post about it yet:

Change log v1.8:

  • Include Phoenix Inverter firmware v1.03 update
  • Fix Phoenix Inverter “Low battery shutdown voltage” setting is locked and showing “Dynamic”

Best regards and have a good day,

Matthijs

Phoenix Inverters 250, 375 and 500VA – Dynamic Cut-off

Good afternoon!

Recently released, but two weeks ago, is the new Phoenix Inverter VE.Direct firmware version v1.03, which besides a few internal changes, has a major new feature – the addition of Dynamic Cut-off. Some of you may know it from Hub-4. What it does is this: instead of using one fixed battery voltage as the low battery shutdown level, it also looks at the battery current. This makes sense, as we all know battery voltage drops when putting a load on it; caused by the internal resistance of a battery bank.

Continue reading

VictronConnect 1.7 – Android 6 compatibility and more

Good morning all,

Next step in making life easier: VictronConnect version v1.7 has been released. It includes three major improvements:

  1. Save the 30 day history of a solar charger as a CSV file
  2. Convert the data log that the Color Control GX saves on SD cards and USB sticks to an Excel file
  3. Fixed several Android 6 related Bluetooth connection issues

Continue reading

Color_Control_GX

Color Control GX v1.60

Good morning!

Version v1.60 is now available. Containing one fix:

When using Hub-1 Assistant, policy 4 “Prevent feeding back energy to grid”, in combination with VE.Direct MPPT firmware version v1.17 or later, the MPPTs stopped charging. The problem was introduced in the previous firmware version (v1.51) and is now fixed.

Note that we have also changed our internal procedures to prevent issues like this from happening again.

Continue reading