How to set MPPT to Charge master? Set 0x200E to b0100001, charger uses internal charge profile.

How to set MPPT to Charge master? Set 0x200E to b0100001. Charger uses internal charge profile.

Ich bastle gerade an einem Programm zu Überschussverwertung an einer Inselanlage.

Hier mal die Eckdaten der Anlage:

2500 Watt PV.

Victron MPPT 100/50.

Batterie 600 Ah 24 Volt.

Inselwechselrichter 24 Volt 2500 Watt.


10 Watt Solarpanel kurzgeschlossen über einen INA226 zur Ermittlung der Stärke der Sonneneinstrahlung.

Diesen INA Wert verrechnen ich mit der aktuellen PV Leistung des MPPT und habe somit die Überschussleistung,

Ist Überschuss vorhanden regle ich über eine Phasenanschnittsteuerung eine 2000 Watt starke Elektroheizung in Stufen von 0 - 255 (später mal einen Warmwasserboiler). Dieser Regelkreis funktioniert soweit.


Als zusätzliche Sicherheit habe ich einen Lastabwurf bei Unterspannung programmiert.

So in der Art " wenn aktuelle Spannung um so viel Volt tiefer ist als Soll-Absorptionsspannung bzw. Soll-Floatspannung dann Lastabwurf".


Die Werte für Floatspannung bzw. Absorptionsspannung ermittle ich momentan etwas umständlich.

Ich mache wenn der Status des MPPT wechselt 2 Spannungsmessungen im Abstand von einer Minute. Danach ziehe die beiden Spannugswerte voneinander ab. Wenn die Differenz nicht größer ist als 0,03 Volt so ist das mein Sollwert für Absoprtion bzw. Float.


Laut Victron Whitpaper sendet ein MPPT wenn man ihn als als Charge Master konfiguriert das Register 0x2001.


"When a unit is set to charge instance master mode it will periodically send the registers 0x2001,

0x2007, 0x2008 and 0x200B using asynchronous hex-messages (:A)."


"0x2001 Charge voltage set-point (*2) 0.01 un16 V".

"Note 2: The charge voltage set-point can be read from the master unit and written to the slave units so

the group will behave as one unit. See network mode register 0x200E."


Das Register 0X2001 ist die Sollspannung des MPPT und genau diesen Wert bräuchte ich.

Dann kann ich nämlich die ganze umständlich Spannungsermittlung rauswerfen und die Temperaturkompensation wäre auch mit drin.


Über die Victron App kann ich den MPPT aber nicht in den Modus Charge Master setzen.

Also geht es nur über den Arduino.


Die Kommandozeile für setzen des Modus Charge Master müsste so lauten:


"Charge master Set 0x200E to b0100001, charger uses internal charge profile"


:8 0E20 00 und dann ??? "b0100001" ??? "checksum" ???


Genau dieses "b0100001" ist mein Problem.


Wie muss ich das schreiben damit der MPPT in den Modus Charge Master geht ?


Gruss Markus

calimero asked
calimero edited ·

3 Answers

ElectroDacus SBMS0 integration with CCGX to control SmartSolar charging

I have built an electrical system for a van to campervan conversion. Sinopoly LiFePO4 cells with ElectroDacus SBMS0, CCGX, MultiPlus 24/5000/120, SmartSolar 150/35, BatteryProtect BP65. The SBMS0 can write status parameters via UART (USB-RS232 interface). I have written a Venus driver to consume these parameters via serial and feed them into the com.victronenergy.battery.ttyUSB0 dbus service. I am writing the following dbus values:

'/Dc/0/Voltage': round(data['battery_voltage'], 2)
'/Dc/0/Current': round(data['battery_current'], 2)
'/Dc/0/Power': round(data['battery_voltage'] * data['battery_current'], 2)
'/Dc/0/Temperature': data['ext_temp']
'/Soc': data['soc']
'/Alarms/LowVoltage': victron_alarm(data['status_uvlk'])
'/Alarms/HighVoltage': victron_alarm(data['status_ovlk'])
'/Alarms/LowSoc': victron_alarm(data['battery_voltage'] <= BATTERY_SOC_LOW_ALARM)
'/Alarms/LowTemperature': victron_alarm(data['ext_temp'] < BATTERY_TEMP_LOW_ALARM)
'/Alarms/HighTemperature': victron_alarm(data['ext_temp'] > BATTERY_TEMP_HIGH_ALARM)
'/Alarms/HighInternalTemperature': victron_alarm(data['status_iot'])
'/Info/MaxChargeVoltage': BATTERY_VOLTAGE_MAX
'/Info/BatteryLowVoltage': BATTERY_VOLTAGE_MIN
'/Info/MaxChargeCurrent': BATTERY_CURRENT_CHARGE_MAX
'/Info/MaxDischargeCurrent': BATTERY_CURRENT_DISCHARGE_MAX
'/Capacity': BATTERY_CAPACITY
'/Alarms/HighChargeCurrent': victron_alarm(data['status_coc'])
'/Alarms/HighDischargeCurrent': victron_alarm(data['status_doc'])
'/Alarms/CellImbalance': victron_alarm(data['cell_voltage_delta'] > 20)
'/Alarms/InternalFailure': victron_alarm(data['status_eccf'] or data['status_open'])
'/Alarms/HighChargeTemperature': victron_alarm(data['battery_current'] > 0.0 and data['ext_temp'] > BATTERY_TEMP_HIGH_ALARM)
'/Alarms/LowChargeTemperature': victron_alarm(data['battery_current'] > 0.0 and data['ext_temp'] < BATTERY_TEMP_LOW_ALARM)
'/Alarms/LowCellVoltage': victron_alarm(data['status_lvc'])
'/System/MinCellVoltage': min(data['cell_voltages'])
'/System/MinVoltageCellId': ','.join(str(cell) for cell, voltage in enumerate(data['cell_voltages']) if voltage == min(data['cell_voltages']))
'/System/MaxCellVoltage': max(data['cell_voltages'])
'/System/MaxVoltageCellId': ','.join(str(cell) for cell, voltage in enumerate(data['cell_voltages']) if voltage == max(data['cell_voltages']))
'/Io/AllowToCharge': victron_bool(data['status_cfet'])
'/Io/AllowToDischarge': victron_bool(data['status_dfet'])

The data appears in the expected places on the CCGX display:

[image]

The SBMS0 signals low/high voltage disconnect via optocouplers (as well as via UART) when the battery is empty/full respectively. I am using this to control the MultiPlus using the Two-Signal BMS assistant as described in the "Connecting other lithium systems to Multis and Quattros" document. I also plan to use the SBMS0 to control loads connected via the BP65 by way of the remote pins.

Ideally I would also use the SBMS0 to control the SmartSolar using the VE.Direct non-inverting remote on/off cable. However, the SmartSolar has a single VE.Direct port, which is in use to connect to the CCGX. I therefore need to use the CCGX to control the SmartSolar.

I have confirmed that remote control of the SmartSolar is possible from the CCGX via dbus:

dbus -y com.victronenergy.solarcharger.ttyO0 /Mode SetValue 1  # on
dbus -y com.victronenergy.solarcharger.ttyO0 /Mode SetValue 4  # off
I am having trouble using the data from the SBMS0, injected via com.victronenergy.battery.ttyUSB0, to control this automatically. With my custom driver installed, the SmartSolar does know that it is supposed to be controlled by the BMS:

[image]

However, even with this configuration, the SmartSolar does not stop charging when the SBMS0 signals battery full/over voltage. I had thought that setting /Io/AllowToCharge would provide this control, but it doesn't seem to.

Which dbus values in com.victronenergy.battery.ttyUSB0 do I need to write so that the SmartSolar will stop charging when the SBMS0 determines that charging is complete?

mija asked
mija commented ·

1 Answer

Victron VenusOS driver for serial connected BMS available - LLT Power / JBD Battery / Overkill Solar Smart BMS

Hi
I have created a VenusOS driver that can talk to BMS/Batteries that has serial communications (instead of the normal CANbus). RS485 & RS232 have been tested.
Currently it only handles the LLT Power / JBD Battery / Overkill Solar Smart BMS range (anything that use the XiaoXiang phone app), but I am busy with the smart Daly BMS and looking at adding the ANT in future as well.

The current release is on GitHub if you want to check it out.

The driver will act as Battery Monitor inside VenusOS and update the following values:

  • State Of Charge
  • Voltage
  • Current
  • Power
  • Can handle batteries with from 3 - 32 cells
  • battery temperature
  • min/max cell voltages
  • raise alarms from the BMS
  • available capacity
  • history of charge cycles

There is also an auto installer using a USB Flash drive or SD card, so no root access is required and the driver can handle VenusOS updates (no need to reinstall after your update)


You can up-vote for your BMS to be added to the driver in the issue list on github.


Louis van der Walt asked
Louis van der Walt edited ·

6 Answers

Chargery BMS on Venus OS

I have enhanced my Chargery BMS driver for Venus OS a lot and it want to share my code! Maybe we can get other BMS data as well to be displayed on Venus/Cerbo etc... My source code (surely open source) is available at https://github.com/Tobi177/venus-chargerybms and surely Victron is allowed to embed it to Venus OS! :) It even have an install script now! :)

Maybe my code can be helpful for any developers! Victron, thank you for your open source support! Much appreciated!

[image]

[image]

[image]

[image]


Bye

Tobi

tobi17 asked
Paul B edited ·

12 Answers

Venus OS v2.70~19 available for testing

Hello all!


new version available for testing. But I’m in a hurry and only on my phone, so this going to be a shorter post than normal. Two changes compared to v2.70~18.


1. fix tanks missing sometimes in the new tank overview page.

2. Fix wifi not being initialised on a fresh system. Mostly noticeable on raspberrypis.


with above, our todo list for v2.70 is empty (!).


so, if you see anything, please post a new answer below.


and for more details of what this is about, search for the v2.70~18 post.


Have a good weekend, Matthijs

mvader (Victron Energy) asked
Mark Maritz commented ·

5 Answers

MPPT Smartsolar - RX pin

Vicrton Smartsolar MPPT 75/15 - I want to disable the charge output to the battery when charging from a main supply charger. I understand you may be be to use the Rx pin on VE port to do this. Is this possible? and if so do I need a 5v signal or can I use 12v. Thanks in advance for any answers.

joncube asked

0 Answers

Venus OS v2.71~1 available for testing

Good morning!

Lets start with explaining what happened with v2.70. That version has been build, but the release of it was cancelled because an issue was found. And as 2.70 is just a number, and numbers are free, we continue now in v2.71.

That issue is fixed now, it relates to the GX Device failing to reconnect to a Fronius PV Inverter, and perhaps other brands as well, after loosing the connection. And that is also the only change in v2.71~1.

I've copied the full change log below.

Same question as usual with regards to testing and reporting.

The next possible official release date is early next week. Its all taking a bit long now which is a pity, but on the other hand I really prefer releasing solid versions; and if that means delaying, then delaying needs to be done!


Looking forward to your reactions,

Matthijs


What is this about?

This post is intended for all people participating in the Venus OS Beta test program. Read that link for more information about the program.


How to report?

For new issues, add a new answer below. If you see the same as someone else, or know more or an answer for him / her, use the comment feature. Careful: adding a new comment versus adding a new answer are really different things, and you need to look closely to know which button to use for what.


Change log

New in v2.71~1, compared to v2.70~19:

  • Fix regression that under some conditions causes a failure to reconnect to a sunspec PV Inverter. This used to work fine in v2.66, and was a regression introduced during v2.70 development. Thank you @offgridsolutions for reporting this!


Rest of changelog, listing all differences to the last official release which is v2.66.

Tanks:

  • Added the new tank overview page. Screenshot below.
  • Increase the margin above the full tank level to 20%. An example to explain this: instead of showing an error in case the measured current is above 20.5mA, show an error when its over 24mA. In that margin, ie. between the configured full level (20mA in my example) and the error level, it will just clip to 100%. Thank you John M. for reporting this improvement; and in general for your push an getting the tanks full featured such as having configurable alarms and having a good overview for them.
  • Use the same tank name in the alarm notifications, the Device list, the mobile overview as well as the new tank overview page.
  • Add tank level alarms. High level alarm and low level alarm. Note that this is only for tank levels measured via the Venus GX, Cerbo GX or GX Tank analog inputs. No alarm levels are supported for tank levels that come in via NMEA2000.
  • Add fluid type 6, gasoline. To fully match the NMEA2000 supported set of fluid types.
  • Support tank senders that send out levels for multiple tanks using different data instances, such as the Garnet Seelevel N2K product, and the Maretron FPM100. Details also here: https://github.com/victronenergy/venus/issues/551.


User interface & various:

  • Change the name of the battery measurements menu to "Battery Measurements" and add a help text indicating that it is (also) for the MFD HTML5 app. This same info is also used for the VRM Dashboard.
  • Better handle AC-Coupled PV on the output of an Inverter RS by adding AC Frequency item, and by showing negative current and power instead of clipping that to zero.
  • Add the firmware version of a Fronius datamanager on the Device subpage. This is added next to the (already shown) firmware version for the PV Inverter itself.
  • Add EM24 Ethernet meter phase configuration setting
  • Improve the CAN-bus statistics page so it all fits on one screen.
  • Fix issue related to Garmin MFDs and the Victron App, because of which the App wouldn't work on the Garmin when doing a certain sequence of power-ups or reboots (ie Garmin first, or GX device first or other way around).
  • NMEA2000-out: include SOH in the NMEA2000-out function. Note that Victron battery monitors such as the BMV series don't have SOH; this applies only when using a lithium battery with integrated CAN-bus *and* that has SOH.


DVCC / ESS / Mode 3 (External control)

  • Hide the Grid feed-in menu when ESS is set to External control, since they are not relevant in that mode.
  • Disable the PV-limiter when ESS mode is set to External Control. This avoids problems where the PV-limiter aims for a different grid setpoint than that set with ESS mode 3. Instead, the customer is responsible for doing his/her own control.
  • Improvements related to Inverter RS Smart Solar. But not fully finished yet.


Managed (CAN-Bus) batteries & PV Inverters:

  • Recognise REC BMS, and show only supported alarms, ie hide all alarm types for which the REC does not send any status, rather than saying "OK" for those. This (showing only the supported alarms) is a nice feature; for which REC is now the only one that supports it; we're looking forward to seeing the same from other battery manufacturers.
  • Fronius PV monitoring: further improve support for large systems by more intelligently quering the Fronius datamanger. Eliminated unnecessary reconnects, and because of that also reduces CPU load on the GX device. Tested at a site with 6 Fronius ECP PV-inverters, and works well: never disconnects now.
  • Can-bus BMS: support CCL & DCL current limits above 3276A.


Connection to VRM:

  • log a warning to VRM in case one or more modules in a managed (CAN-bus) battery is blocking charge.
  • Add various data for the Inverter RS Smart Solar (AC-out power, energy values, some history data for solar)
  • Show VRM down in case the VRM-data-receival system is down; instead of a vague error that might make people think there is an issue on their side.
  • Change the logging frequency of min/max cell voltage/temperature to fix the gaps in the graphs on VRM.


Modbus-TCP

  • Add registers for total power, power capacity, and power limiting. The power limit register is for external control in ESS mode 3. This is an easier method than controlling the PV-inverter directly through SunSpec. https://github.com/victronenergy/venus/issues/821.
  • Add registers for /Hub4/TargetPowerIsMaxFeedIn and for /Hub4/FixSolarOffsetTo100mV
  • Add registers for Inverter RS Smart


Networking / modem

  • Allow using a GSM modem while connected to a local-only network by not setting a default route if there is no default gateway received from DHCP and/or configured manually.


RaspberryPis

  • Note that installing v2.70 on a rpi can only be done by re-installing. Meaning: burn a v2.70 image to an sdcard, overwriting anything on there. Detailed instructions here. And more details in the discussion going on in the comments.
  • Restored the packages (but to anyone using those, be aware that they are really not maintained, and if there in the way again for us we'll just as lightly as previously decide to take them out again. I'm sorry but that's what it is).
  • Support (some of the) RaspberryPi4s. Some of the means that only some older versions work. Newer do not.
  • Make the Bluetooth work on RaspberryPi3 and RaspberryPi4. The functionality is same as other GX Devices: to setup the network. Which means also that there is nothing else: no monitoring of your Victron system, use Remote Console on LAN, or http://venus.local/app/ instead.
  • Use the complete SD-Card size, rather than a fixed size rootfs, by resizing on boot.
  • Enable the radio on by default, instead of blocking it until unblocked by navigating to the wifi menu page in the gui. This fixes it being impossible to configure the wifi on a raspberrypi via VictronConnect/BLE without first going to said menu via Remote Console. Thank you @Stefanie for reporting - quite some time ago.


More developer / hobbyist:

  • Switch from version Rocko to version Zeus of Open Embedded. A (perhaps too) simplified explanation for this is that its like going from Windows 7 to Windows 8, and then not in what you see, but just in what's running in the background. For those interested, more info [here](https://wiki.yoctoproject.org/wiki/Releases). And yes, Zeus is EOL as well. We'll soon switch over to Dunfell.
  • Linux kernel updated from 4.19 to 5.10 for CCGX, Cerbo GX, GX-Card in MP-II and ES-II products as well as the CANvu GX. And updated from 4.9 to 5.10 for the Venus GX. No change for the raspberrypi, that is still on 4.19.
  • Venus GX: Resize partitions on boot to the "new" large style partitioning. Background: up until the end of 2018, we produced our Venus GX-es with a file system partitioning similar to the CCGX. But the Venus GX has much more flash memory inside. So end of 2018 we changed the production methods. And now with this change, any unit produced before then will also automatically be upgraded to the new (larger) size. This change allows us to add more standard functionality in those older Venus GX-es. And also it makes it easier to install Venus OS Large on a Venus GX produced before end of 2018: its no longer necessary to manually do the repartitioning. Just run v2.70 once, and presto.
  • Fix some management dbus-paths in dbus-pump & dbus-generator-starter, no user visible changes.
  • Update Qt5 to 5.13.
  • Mark menu items that are only visible in debug or other special modes with a color; so thats its clear that its not visible in normal usage.


Known issues:

  • In some cases, one or more tanks don't show when selecting the tank type filter button on the bottom. Tanks can also go missing in the mobile overview, aka the "Boat & motorhome overview", enabled in the Settings -> Display & language menu . This missing tanks issue is being looked into.
  • There seems to be an issue with the RaspberryPi3 WiFi, more details here.


Previous v2.70 beta posts




Ps. the screenshots, first one more Marine oriented, second one more off-grid oriented.


[image]


[image]


Ps 2. Screenshot of the new low level alarm for a tank. There is a similar page to configure a high level alarm:

[image]


mvader (Victron Energy) asked
mvader (Victron Energy) commented ·

1 Answer

Question to VE.Direct MPPT protocol

Hello Community,

I am developing a system to control my BlueSolar 75/10 MPPT charger and I have already read the published document on the VE.Direct Hex Protocol.

Is there a register in which the current setpoint voltage of the switching regulator of the MPPT can be read? So to speak, the float or absorption voltage including temperature compensation?

I want to use this information to use the excess solar power with a pwm regulated load.

I tried to read out register Charge Voltage Set-Point 0x2001, but it's set to 0xffff during standalone mode. Even when I switched to MPPT to Charge master mode, the Set-Point 0x2001 was still 0xffff. Does the bluesolar 75/10 not support charge master mode?

If there's no way to read out this directly, I will try to calculate the voltage in my microcontroller by using float or absorption voltage and the battery temperature with the compensation.

I'm already writing the battery temperature into the MPPT and it's reported back correctly.

Thanks,

Thorsten


P.S. I chose Victron products because the protocols and interfaces used are documented.

custom asked
calimero answered ·

1 Answer

Shortest distance, CAN to D-Bus

Hi!

We are currently working on an electrical boat with Victron Energy systems installed.

The boat has a 15kw generator with a bunch of sensors which we have connected to the supported CAN-Bus system on Cerbo GX.

The generator is not a supported one in Venus OS, so for now we decided on installing Venus OS Large because of the simplicity of Node-RED.


We are receiving the CAN-frames as expected in both Node-RED and the bash-terminal through SSH and we now want to pass the translated information to D-Bus.


At this point we are going to attempt adding settings to the D-bus, using the Fischer Panda settings as a base-template.

What we do not know is how to pass this information from Node-RED to the D-bus.


Any help or ideas on the matter would be greatly appreciated.

haakastadir asked
haakastadir edited ·

0 Answers

idea
Kevin Windrem commented Modifications
13

8 Feedback

0 Comments

article
idea
harold suggested Modifications
2

0 Feedback

0 Comments

Additional, external Units in Modbus TCP network with the Cerbo GX as a gate

Hi everyone!

I wonder how to set additional, external Units in Modbus TCP network with the Cerbo GX as a gate.

I've got an CerboGX, other parts from Victron Energy like Multi, Quattro, BMV, ColorControll etc. and GUI created in one of the HMI program (don't want to say the name, producer of it). This program gives me the opportunity to show all the data on my website and mobile live, directly from all of the Units (UnitIDs) shown on Cerbo thanks Modbus TCP.

I want to implement another component to this Modbus TCP network, but I don't know to do this.

For example I want to add a couple of simple switches to tell me if some doors or windows are open or closed.

Do I need another gateway for it?

Thanks.

rajmund asked

0 Answers

SmartSolar 75/15 closed casing

Hi! I would need to install a SmartSolar 75/15 basically in the middle of an ocean. The conditions will be rough and therefor I would need to have the charger in a IP67 closed casing. I'm sure this is not recommended because of the heat produced by the unit, but I was wondering if there was a way.

If I had the wall of the casing made of a metal heatsink and the 75/15 attached to the heatsink with some cooling compound (such as used in CPUs) between the back wall of the 75/15 and the heatsink, could this have a chance of working?

anssi asked
anssi answered ·

3 Answers

Call MPPT 75/10 solar stats with Pi

Hi

Little bit of a noob but hoping someone can guide me or point me to an already existing page...


Currently using a Pi 4 which is powered by solar and running Raspbian OS with CCTV software (Nx Witness)...

what I'm wanting to know is, can I create a script that will allow the Pi to send a ping/call to the MPPT 75/10 (via USB) and in turn the MPPT fires back the battery, load and incoming solar stats....im then wanting to use these stats to monitor the remote units.

Our software doesn't work along side with the Venus images etc


Thanks Guys

dale-shacklock asked
Erik Sporns commented ·

4 Answers

Cannot get remote port via API

We are trying to get remote port through API, but the API is returning an empty set (as seen in Python):

{u'records': {u'data': {u'152': []},
              u'meta': {u'152': {u'code': u'rs',
                                 u'description': u'Remote support port',
                                 u'formatValueOnly': u'%.0F',
                                 u'formatWithUnit': u'Port %.0F'}}},
 u'success': True}

The remote port is enabled and showing in the remote console via VRM website.

The request URL is:

GET https://vrmapi.victronenergy.com/v2/installations/1039/widgets/Graph?attributeCodes[]=rs

Am I understanding the syntax correctly?

Oskari Teeri asked
fabio-de-pascale answered ·

3 Answers

Cerbo GX Relay 2 programing free lancing service (outsourcing)

I am not familiar with coding and re-programing and i would like to ask for a payed service for programing Relay 2 in the Cerbo GX.

karam-el-bayed asked
Erik Sporns answered ·

1 Answer

Modbus TCP unit ID keep on changing without reboot.

Hi Guys and Girls,

I would very much appreciate the help of this great community.

I am running Venus OS v2.66. I have Modbus TCP enabled and I am running Home Assistant to automate my campervan. I am able to read and write to registers and perform task suck as turning on and off the Multiplus (via MK3) based on certain conditions; SOC, Solar power etc.

I have been always having issues with the Multiplus Modbus TCP unit ID's changing without reboot. So I don't really know how it happens nor how to reproduce this. It always switches between ID 238 and 237. So this mess with my automation and therefore I am unable to control the Multiplus unless I change the register in Home Assistant to the corresponding ID shown in Venus. And when I change it it switches back again to the the original value. This can happen once every 2 days or twice a day... It is very random.


Is there a way to force the Multiplus to take one ID only like other devices? The smartshunt seems to always take 237 and the MPPT always on 239.


If it is not possible is there anyway ( for those with Home Assistant know-how) to programmatically read the Unit IDs and change them accordingly or a different approach to read and write Modbus registers?


Is Node-Red the cure here?


Many thanks guys and Girls ..;)


[image]


[image]

vanlifer007 asked
mvader (Victron Energy) commented ·

1 Answer

Gui option to shutdown GX

Hi, please add a option to properly shutdown the GX monitor. It's always better to stop anything before power off a computer. There is always a "Reboot" option in the Settings/General menu but nothing about shutdown.

chuff asked

0 Answers

UPDATE on Raspbery Pi 3B

I am currently running 2.66. When I attempt to check for the latest release candidate I get the message "Error during checking"

[image]

Duncan Hall asked
xbmcnut answered ·

2 Answers

idea

No inverter animation from battery

It doesn't show the battery-inverter animation is that a bug? or do i need to enable it somwehere in settings?


My setup is; Victron Phoenix 12/500 , Smart shunt 500A/50mv , RPI 3B+ as venus device



[image]

[image]

xpatrik asked
xpatrik commented ·

0 Answers

How many times can you reprogram the setpoints in an MPPT 100/50 controller?

I'm using an MPPT charge controller to charge a lithium battery bank. At the end of charge (85 b- 100%) one needs to control the charge current to prevent overcharging of weaker cells. To do this I'd like to used the VE direct port - but how many times can you reprogram the max battery charge current ( register 0xEDF0)?

miked asked
miked answered ·

1 Answer

Setting VebusSetChargeState to Force absorb stops if the BMS set the charge to float and then resets flag

Hi,

If i set the VebusSetChargeState to 2 e.g Forced Absorbtion then the 2 wire BMS signals to go to Float and when the BMS clears the #3 the charger doesn't go back to Absorption but stays in Float, is that intentionally ? @mvader (Victron Energy) do you know?

/peter


peternielsen asked
peternielsen edited ·

0 Answers

Venus OS v2.70~17 available for testing

Good evening!

After releasing v2.70~16 yesterday, we were quickly alerted by several testers that it had an issue which made devices to be no longer visible on the Device list page. We then decided to block v2.70~16, meaning that we removed it from being downloadable/installable.

The bug was fixed today, in v2.70~17. And that is now available for download. So, here is a new page, to also start with a clean set of answers & comments.


What is this about?

This post is intended for all people participating in the Venus OS Beta test program. Read that link for more information about the program.


What to test?

For those having tank levels on their GX device, the new tank overview. Screenshot below. Though be aware that we know something is still amiss with tanks, and we're looking into that.

Other than that, same as last time: basically everything. In v2.70 we have made multiple low level changes. The OE version has been updated from Rocko to Zeus and the Linux kernel has been updated from 4.19 to 5.10. And as a result, bugs and regression may hide in the most unexpected of corners.

Sofar, the status is that its all proving to be quite stable.


The plan with v2.70

With a bit of luck, official release early next week already.


How to report?

For new issues, add a new answer below. If you see the same as someone else, or know more or an answer for him / her, use the comment feature. Careful: adding a new comment versus adding a new answer are really different things, and you need to look closely to know which button to use for what.


Change log v2.70~1 to ~17

Note: I've condensed all separate change logs into one. So this list now contains all changes for v2.70.

v2.70~17 has nothing new compared to v2.70~16. The only change in ~17 is a fix for the issue that was introduced in ~16.


Tanks:

  • Added the new tank overview page. Screenshot below.
  • Increase the margin above the full tank level to 20%. An example to explain this: instead of showing an error in case the measured current is above 20.5mA, show an error when its over 24mA. In that margin, ie. between the configured full level (20mA in my example) and the error level, it will just clip to 100%. Thank you John M. for reporting this improvement; and in general for your push an getting the tanks full featured such as having configurable alarms and having a good overview for them.
  • Use the same tank name in the alarm notifications, the Device list, the mobile overview as well as the new tank overview page.
  • Add tank level alarms. High level alarm and low level alarm. Note that this is only for tank levels measured via the Venus GX, Cerbo GX or GX Tank analog inputs. No alarm levels are supported for tank levels that come in via NMEA2000.
  • Add fluid type 6, gasoline. To fully match the NMEA2000 supported set of fluid types.
  • Support tank senders that send out levels for multiple tanks using different data instances, such as the Garnet Seelevel N2K product, and the Maretron FPM100. Details also here: https://github.com/victronenergy/venus/issues/551.


User interface & various:

  • Change the name of the battery measurements menu to "Battery Measurements" and add a help text indicating that it is (also) for the MFD HTML5 app. This same info is also used for the VRM Dashboard.
  • Better handle AC-Coupled PV on the output of an Inverter RS by adding AC Frequency item, and by showing negative current and power instead of clipping that to zero.
  • Add the firmware version of a Fronius datamanager on the Device subpage. This is added next to the (already shown) firmware version for the PV Inverter itself.
  • Add EM24 Ethernet meter phase configuration setting
  • Improve the CAN-bus statistics page so it all fits on one screen.
  • Fix issue related to Garmin MFDs and the Victron App, because of which the App wouldn't work on the Garmin when doing a certain sequence of power-ups or reboots (ie Garmin first, or GX device first or other way around).
  • NMEA2000-out: include SOH in the NMEA2000-out function. Note that Victron battery monitors such as the BMV series don't have SOH; this applies only when using a lithium battery with integrated CAN-bus *and* that has SOH.


DVCC / ESS / Mode 3 (External control)

  • Hide the Grid feed-in menu when ESS is set to External control, since they are not relevant in that mode.
  • Disable the PV-limiter when ESS mode is set to External Control. This avoids problems where the PV-limiter aims for a different grid setpoint than that set with ESS mode 3. Instead, the customer is responsible for doing his/her own control.
  • Improvements related to Inverter RS Smart Solar. But not fully finished yet.


Managed (CAN-Bus) batteries & PV Inverters:

  • Recognise REC BMS, and show only supported alarms, ie hide all alarm types for which the REC does not send any status, rather than saying "OK" for those. This (showing only the supported alarms) is a nice feature; for which REC is now the only one that supports it; we're looking forward to seeing the same from other battery manufacturers.
  • Fronius PV monitoring: further improve support for large systems by more intelligently quering the Fronius datamanger. Eliminated unnecessary reconnects, and because of that also reduces CPU load on the GX device. Tested at a site with 6 Fronius ECP PV-inverters, and works well: never disconnects now.
  • Can-bus BMS: support CCL & DCL current limits above 3276A.


Connection to VRM:

  • log a warning to VRM in case one or more modules in a managed (CAN-bus) battery is blocking charge.
  • Add various data for the Inverter RS Smart Solar (AC-out power, energy values, some history data for solar)
  • Show VRM down in case the VRM-data-receival system is down; instead of a vague error that might make people think there is an issue on their side.
  • Change the logging frequency of min/max cell voltage/temperature to fix the gaps in the graphs on VRM.


Modbus-TCP

  • Add registers for total power, power capacity, and power limiting. The power limit register is for external control in ESS mode 3. This is an easier method than controlling the PV-inverter directly through SunSpec. https://github.com/victronenergy/venus/issues/821.
  • Add registers for /Hub4/TargetPowerIsMaxFeedIn and for /Hub4/FixSolarOffsetTo100mV
  • Add registers for Inverter RS Smart


Networking / modem

  • Allow using a GSM modem while connected to a local-only network by not setting a default route if there is no default gateway received from DHCP and/or configured manually.


RaspberryPis

  • Note that installing v2.70 on a rpi can only be done by re-installing. Meaning: burn a v2.70 image to an sdcard, overwriting anything on there. Detailed instructions here. And more details in the discussion going on in the comments.
  • Restored the packages (but to anyone using those, be aware that they are really not maintained, and if there in the way again for us we'll just as lightly as previously decide to take them out again. I'm sorry but that's what it is).
  • Support (some of the) RaspberryPi4s. Some of the means that only some older versions work. Newer do not.
  • Make the Bluetooth work on RaspberryPi3 and RaspberryPi4. The functionality is same as other GX Devices: to setup the network. Which means also that there is nothing else: no monitoring of your Victron system, use Remote Console on LAN, or http://venus.local/app/ instead.
  • Use the complete SD-Card size, rather than a fixed size rootfs, by resizing on boot.
  • Enable the radio on by default, instead of blocking it until unblocked by navigating to the wifi menu page in the gui. This fixes it being impossible to configure the wifi on a raspberrypi via VictronConnect/BLE without first going to said menu via Remote Console. Thank you @Stefanie for reporting - quite some time ago.


More developer / hobbyist:

  • Switch from version Rocko to version Zeus of Open Embedded. A (perhaps too) simplified explanation for this is that its like going from Windows 7 to Windows 8, and then not in what you see, but just in what's running in the background. For those interested, more info [here](https://wiki.yoctoproject.org/wiki/Releases). And yes, Zeus is EOL as well. We'll soon switch over to Dunfell.
  • Linux kernel updated from 4.19 to 5.10 for CCGX, Cerbo GX, GX-Card in MP-II and ES-II products as well as the CANvu GX. And updated from 4.9 to 5.10 for the Venus GX. No change for the raspberrypi, that is still on 4.19.
  • Venus GX: Resize partitions on boot to the "new" large style partitioning. Background: up until the end of 2018, we produced our Venus GX-es with a file system partitioning similar to the CCGX. But the Venus GX has much more flash memory inside. So end of 2018 we changed the production methods. And now with this change, any unit produced before then will also automatically be upgraded to the new (larger) size. This change allows us to add more standard functionality in those older Venus GX-es. And also it makes it easier to install Venus OS Large on a Venus GX produced before end of 2018: its no longer necessary to manually do the repartitioning. Just run v2.70 once, and presto.
  • Fix some management dbus-paths in dbus-pump & dbus-generator-starter, no user visible changes.
  • Update Qt5 to 5.13.
  • Mark menu items that are only visible in debug or other special modes with a color; so thats its clear that its not visible in normal usage.


Known issue:

  • In some cases, one or more tanks don't show when selecting the tank type filter button on the bottom. Tanks can also go missing in the mobile overview, aka the "Boat & motorhome overview", enabled in the Settings -> Display & language menu . This missing tanks issue is being looked into.


Previous v2.70 beta posts


Looking forward to your reactions, and have a good weekend,

Matthijs


Ps. the screenshots, first one more Marine oriented, second one more off-grid oriented.


[image]


[image]


Ps 2. Screenshot of the new low level alarm for a tank. There is a similar page to configure a high level alarm:

[image]

mvader (Victron Energy) asked
mvader (Victron Energy) commented ·

6 Answers

Venus OS v2.70 - Wifi not working on raspberrypi

Testing Venus OS v2.70~15 on an Raspberry PI 3B+ and I'm not able to get the WiFi to work. Worked as expected on 2.66, but on 2.70 I just get the message "No Wi-Fi adapter connected" Any other experiencing this or have any tip to make wifi work?


vga

vga asked
ray-mont commented ·

6 Answers

Relay switch for an inverter to be shut off by the battery protect

I am confused about how I can use my battery protect to shut off my inverter when low voltage occurs. I understand that I should not connect the inverter to the battery protect and that I can instead wire the inverter remote on off switch ground to the alarm terminal and the positive to the battery protect positive. But that doesn't seem to shut off the inverter as it should. Does that mean the battery protect does not have a relay switch inside and I need to wire on myself? If so, can someone help me out and show me what I need to buy and how to connect it. At least what I need to buy and I can research how to do it. I really wish the battery protect manual was more detailed and specific on the topic. Thank you in advance.

aceclement asked
aceclement commented ·

1 Answer

How do i use VE configure with Linux (ubuntu)?

With the help from some hints from this post I could run VE configure on my Kubuntu 20.4 notebook. But I used the tool PlayOnLinux instead of Wine directly. Here the steps I did:

  1. Installing Ubuntu Wine Emulator PlayOnLinux
  2. Installing inside PlayOnLinux a recent Wine version (version 5.22 actually)
  3. Click in PlayOnLinux on Install program
  4. Click in the windows below Install a non listed program
  5. Then a assistant appears and gives some hints and asks what you want to do.
  6. Choose install Wine and select V5.22 (I used 32bit version)
  7. Then it downloads Wine and asks for some libraries as Gecko
  8. If this is done the assistant ask to select a install file, search for VE Configure EXE and install it
  9. Now VE Configure should run, ev. you need to tweak some display setting via Configuration settings
  10. Next steps are related to MK3-USB connection, which I explain in a answer below.

[image]

[image]

lucode asked
saxofon answered ·

3 Answers