VRM Duplicating Multiplus II Device with Raspberry Pi
Why am I seeing duplicates of my Multiplus II showing up in VRM? I have tried deleting the duplicates but they come back.
[image]
warwick
asked
Why am I seeing duplicates of my Multiplus II showing up in VRM? I have tried deleting the duplicates but they come back.
[image]
warwick commented ·
0 Answers
VRM API hasMains only available in the list of installations when request is not extended - alarm is only available in the extended
Hi!
Is it on purpose that hasMains attribute is missing from the extended query of installations on the VRM API? Is there an other way to get from that response?
In case of alarm the opposite is true, it is only in the extended request.
thanks
eliott
eliott
asked
Hi!
Is it on purpose that hasMains attribute is missing from the extended query of installations on the VRM API? Is there an other way to get from that response?
In case of alarm the opposite is true, it is only in the extended request.
thanks
eliott
mvader (Victron Energy Staff) edited ·
1 Answer
Help with Raspberry Pi with Expander Pi (for RTC and tank levels)
I got my expander pi for the RTC and tank level ADC. I'm trying to follow the directions to get the ADC working, but I'm stuck. https://groups.google.com/forum/#!searchin/victron-dev-venus/expander$20pi%7Csort:date/victron-dev-venus/V-JKXfBxXbA/-4kUe5qVFgAJ
https://gist.github.com/aaronsb/3a8de2bfc6081ecda268a353125bae14
I followed this:
#copy dtb to /u-boot/overlays I DID THIS FROM THE DOWNLOADED FILE
#excerpt from post:
#I had to convert the mcp3008-overlay.dtb to a dts file, change all references to 3008 to 3208, and convert it back to a dtb file, to get it to give me 12-bits (4095).
#(I've enclosed the dtb file if anyone needs it). The line in config.txt should read "dtoverlay=mcp3208:spi0-0-present" I DID THIS
#https://groups.google.com/d/msg/victron-dev-venus/mejgJbMjU34/WglmnUPQAwAJ
opkg install kernel-module-mcp320x I DID THIS
chmod 755 /opt/victronenergy/dbus-adc/start-adc.sh I get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
chmod 755 /opt/victronenergy/dbus-adc/dbus-adc I get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
chmod 755 /opt/victronenergy/dbus-adc/service/run I get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
chmod 755 /opt/victronenergy/dbus-adc/log/runI get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
touch /var/log/dbus-adc I DID THIS
ln -s /opt/victronenergy/dbus-adc/service /service/dbus-adc I get -sh: chmod:: command not found
Since I couldn't get that working, I thought I would get the RTC to work, but couldn't get that either. I followed this:
###### RTC Clock for DS1307 ######
#install kernel module package.
opkg install kernel-module-rtc-ds1307 I DID THIS
#create /data/rc.local I DID THIS
#add this line to it to run on startup.
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device I DID THIS
hwclock -s I DID THIS
#end lines
#for reference
#hwclock -w
#write the system time to rtc
When I try this, I get: hwclock: can't open '/dev/misc/rtc': No such file or directory
#hwclock -r
#reads it back from the rtc
When I try this, I get: hwclock: can't open '/dev/misc/rtc': No such file or directory
#hwclock -s writes rtc back to system time
When I try this, I get: hwclock: can't open '/dev/misc/rtc': No such file or directory
Any help would be appreciated.
nebulight
asked
I got my expander pi for the RTC and tank level ADC. I'm trying to follow the directions to get the ADC working, but I'm stuck. https://groups.google.com/forum/#!searchin/victron-dev-venus/expander$20pi%7Csort:date/victron-dev-venus/V-JKXfBxXbA/-4kUe5qVFgAJ
https://gist.github.com/aaronsb/3a8de2bfc6081ecda268a353125bae14
I followed this:
#copy dtb to /u-boot/overlays I DID THIS FROM THE DOWNLOADED FILE
#excerpt from post:
#I had to convert the mcp3008-overlay.dtb to a dts file, change all references to 3008 to 3208, and convert it back to a dtb file, to get it to give me 12-bits (4095).
#(I've enclosed the dtb file if anyone needs it). The line in config.txt should read "dtoverlay=mcp3208:spi0-0-present" I DID THIS
#https://groups.google.com/d/msg/victron-dev-venus/mejgJbMjU34/WglmnUPQAwAJ
opkg install kernel-module-mcp320x I DID THIS
chmod 755 /opt/victronenergy/dbus-adc/start-adc.sh I get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
chmod 755 /opt/victronenergy/dbus-adc/dbus-adc I get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
chmod 755 /opt/victronenergy/dbus-adc/service/run I get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
chmod 755 /opt/victronenergy/dbus-adc/log/runI get chmod: /opt/victronenergy/dbus-adc/start-adc.sh: No such file or directory
touch /var/log/dbus-adc I DID THIS
ln -s /opt/victronenergy/dbus-adc/service /service/dbus-adc I get -sh: chmod:: command not found
Since I couldn't get that working, I thought I would get the RTC to work, but couldn't get that either. I followed this:
###### RTC Clock for DS1307 ######
#install kernel module package.
opkg install kernel-module-rtc-ds1307 I DID THIS
#create /data/rc.local I DID THIS
#add this line to it to run on startup.
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device I DID THIS
hwclock -s I DID THIS
#end lines
#for reference
#hwclock -w
#write the system time to rtc
When I try this, I get: hwclock: can't open '/dev/misc/rtc': No such file or directory
#hwclock -r
#reads it back from the rtc
When I try this, I get: hwclock: can't open '/dev/misc/rtc': No such file or directory
#hwclock -s writes rtc back to system time
When I try this, I get: hwclock: can't open '/dev/misc/rtc': No such file or directory
Any help would be appreciated.
buzzlightyear answered ·
1 Answer
PV on AC-out1 first and then MPPT
hoi,
Is there something ( a way ) that the PV-inverter (AC-outA1) has prior instead of the DC MPPTS ?
what i mean is :
My ABB pv-inverter goes off and back on several times on a day when my battery is full and there is to much solar to feed it back to the grid (now on 19A limit)
i have 4000w PV-inverter on the AC-output and (for now) 4000wp on the DC side...
and ofcourse thats to much solar power when the battery is full. (or almost full)
so that the PV inverter (AC-out1) can go full power and the DC mppts go in limit?
because the freq. shifting is not going so good i think.. :(
grtz kristof
P.S.
ABB is connected via zigbee (no RJ45 possible)
now i gone test the last "beta v2.30-43" , but i read the description and didnt see thats in it ..
[image]
Kristof
asked
hoi,
Is there something ( a way ) that the PV-inverter (AC-outA1) has prior instead of the DC MPPTS ?
what i mean is :
My ABB pv-inverter goes off and back on several times on a day when my battery is full and there is to much solar to feed it back to the grid (now on 19A limit)
i have 4000w PV-inverter on the AC-output and (for now) 4000wp on the DC side...
and ofcourse thats to much solar power when the battery is full. (or almost full)
so that the PV inverter (AC-out1) can go full power and the DC mppts go in limit?
because the freq. shifting is not going so good i think.. :(
grtz kristof
P.S.
ABB is connected via zigbee (no RJ45 possible)
now i gone test the last "beta v2.30-43" , but i read the description and didnt see thats in it ..
[image]
0 Answers
Color Control GX firmware v2.04 needed and not available at the Victron repository.
Hi guys,
I might have the need of a certain firmware of CCGX in order to be able to execute the equalization process from the CCGX without having to unplug the CCGX from the MPPT and plug the bluetooth wongle into the MPPT everytime I need to equalize. The little VE.Direct plugs won't handle many ins and outs. I've downloaded and installed all versions available up to date to no avail. The Victron repository seems to lack several versions such as the 2.04, which, of course I didn't back up at before messing with it! :( I've been scuba diving for this through the Victron repository and other websites that offer drivers and such for a while now, and I can't find much other than version 1.6 or less via softpedia. I'm not too keen on lowering the version more than what the manual says it used to have when I bought it. I would really appreciate it if someone knows a link to download v 2.04 or could back up their own v2.04 and upload it to a cloud! Thanks!
Funkaddict
asked
Hi guys,
I might have the need of a certain firmware of CCGX in order to be able to execute the equalization process from the CCGX without having to unplug the CCGX from the MPPT and plug the bluetooth wongle into the MPPT everytime I need to equalize. The little VE.Direct plugs won't handle many ins and outs. I've downloaded and installed all versions available up to date to no avail. The Victron repository seems to lack several versions such as the 2.04, which, of course I didn't back up at before messing with it! :( I've been scuba diving for this through the Victron repository and other websites that offer drivers and such for a while now, and I can't find much other than version 1.6 or less via softpedia. I'm not too keen on lowering the version more than what the manual says it used to have when I bought it. I would really appreciate it if someone knows a link to download v 2.04 or could back up their own v2.04 and upload it to a cloud! Thanks!
Funkaddict answered ·
2 Answers
Markus
Boekel
Mark
Boekel
Mark
3Likes
Loads show in rPi Venus RC don't add up
Hi there,
New to this community and new to Victron equipment but rather excited about the possibility...
Ive purchased a VE.Direct 800VA Inverter, BMV-702, 100/75 MPPT, 80W Polo Panel and enough USB to VE.Direct cables to plug in to a rPi. The setup is installed in my shed for now, once I've played enough, the plan is to build a micro-camper as well as take part of my house off-grid. Maybe I should say at this point this is all a hobby and I don't rely on any of this equipment, yet...
Anyway, the RC doesn't show the correct load on the system, its duplicated. In the image below, my inverter is using 46W, which is about right as I was charging some things but the DC Power shows 51W which is wrong, it should only be about 5W (powering the rPi via a 12V to 5V USB adaptor). When I switch the inverter off, both the AC Loads and the DC power drop, AC goes to "-" and DC Power to 5W (as expected). Is there a way to correct this?
[image]
Thanks in advance,
Chris
woody
asked
Hi there,
New to this community and new to Victron equipment but rather excited about the possibility...
Ive purchased a VE.Direct 800VA Inverter, BMV-702, 100/75 MPPT, 80W Polo Panel and enough USB to VE.Direct cables to plug in to a rPi. The setup is installed in my shed for now, once I've played enough, the plan is to build a micro-camper as well as take part of my house off-grid. Maybe I should say at this point this is all a hobby and I don't rely on any of this equipment, yet...
Anyway, the RC doesn't show the correct load on the system, its duplicated. In the image below, my inverter is using 46W, which is about right as I was charging some things but the DC Power shows 51W which is wrong, it should only be about 5W (powering the rPi via a 12V to 5V USB adaptor). When I switch the inverter off, both the AC Loads and the DC power drop, AC goes to "-" and DC Power to 5W (as expected). Is there a way to correct this?
[image]
Thanks in advance,
Chris
Boekel answered ·
1 Answer
VRM Feature Request : Midpoint Graph
I'd love to see my mid point over time. I've got a situation where it seems to flip high and low, would be nice to see that data graphed out.
neoneddy
asked
I'd love to see my mid point over time. I've got a situation where it seems to flip high and low, would be nice to see that data graphed out.
0 Answers
Venus Packages on Raspbian Lite (Stretch)
Hello!
Has anyone been successful with this guide:
https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-packages on a raspberry pi using the latest Raspbian (lite) Stretch? I get a segmentation fault when trying to run /opt/victronenergy/vedirect-interface/vedirect-dbus directly
I can provide more info (core dump, etc)
Can anyone confirm what the latest actual venus PI images run on? I thought about trying to extract the vedirect-dbus binary from that image and trying.
Novice
asked
Hello!
Has anyone been successful with this guide:
https://github.com/victronenergy/venus/wiki/raspberrypi-install-venus-packages on a raspberry pi using the latest Raspbian (lite) Stretch? I get a segmentation fault when trying to run /opt/victronenergy/vedirect-interface/vedirect-dbus directly
I can provide more info (core dump, etc)
Can anyone confirm what the latest actual venus PI images run on? I thought about trying to extract the vedirect-dbus binary from that image and trying.
buzzlightyear commented ·
5 Answers
Venus OS image on Raspberry Pi Zero (W)
Hi,
Some questions here pertain to using our packages on a RaspberryPi Zero W running Rasbian OS Lite. This question is about something else: testing if the RaspberryPi Venus OS image runs on those Pi Zeros.
Our wiki states:
- Raspberry Pi Zero: we don't know if this is supported (its a community project: please try and let us know!)
- Raspberry Pi Zero W & WH: same thing: we don't know.
Is there any one out here that could look into that? Could be as simple as testing; and all works; and then we know and change the wiki.
Or not; and then more work is needed; for which we’ll need some outside / community help.
mvader (Victron Energy Staff)
asked
Hi,
Some questions here pertain to using our packages on a RaspberryPi Zero W running Rasbian OS Lite. This question is about something else: testing if the RaspberryPi Venus OS image runs on those Pi Zeros.
Our wiki states:
- Raspberry Pi Zero: we don't know if this is supported (its a community project: please try and let us know!)
- Raspberry Pi Zero W & WH: same thing: we don't know.
Is there any one out here that could look into that? Could be as simple as testing; and all works; and then we know and change the wiki.
Or not; and then more work is needed; for which we’ll need some outside / community help.
buzzlightyear commented ·
4 Answers
Venus OS v2.30~43 available for testing
Good day beta-testers!
v2.30~43 is now available for testing. Please post feedback below this item in the Answers section.
This release contains more minor fixes and improvements.
Marine MFD Integration
As explained before, the main new feature in v2.30 is the integration with MFDs as used on the helm of a yacht. And that feature is ready for testing. To do so, enable MQTT in Settings -> Services, and then open a webbrowser and navigate to http://[ipaddress]/app. In some cases http://venus.local/ will work as well. Also it can already be tested on compatible Navico and Garmin displays. Preliminary documentation is available here:
- https://www.victronenergy.com/live/venus-os:mfd-navico
- https://docs.victronenergy.com/gx/mfd-garmin.html
Changes in v2.30~41 up to and including v2.30~43
General:
- Remote Console now uses a different authentication mechanism. This (finally!) fixes a long running problem for some customers related to the IP Address being used for authentication.
- Fix issue when removing an MK3-USB from the GX device; in case you are wondering: using an MK3-USB together with a GX device is quite an uncommon configuration. Its used with RaspberryPis, and also used to connect a second inverter/charger system to a GX device.
- HTML5 app: various small improvements.
- Improve reporting and working with Overload, Temperature, Low battery and High DC ripple alarms and warnings. Both in the notifications page on the device itself as on VRM. In such event; now only one alarm needs to show up; not multiple at the same time.
- Fix issue in Remote VEConfigure: changing battery capacity and a few other settings do not require a system reset; but that reset was carried out anyway. Now, you can change those settings without a short, unannounced, blackout.
- Fix bug that, in certain specific conditions, caused a CPU overloaded system to hang; rather than restart and start clean.
ESS:
- Don't stop discharging when SOC indicates 0%. When Minimum SOC setting is configured to 0%; the system is now allowed to run until another threshold makes it stop; there is no more checking on SOC.
- Fix bug that caused the system to power the loads from the grid while in the scheduled charging window once the batteries were fully charged. Now; first the grid is used to fully charge the batteries, as it should when in a scheduled charging window, and once the batteries are full it prioritises PV over the grid, only using the latter in case there is not enough PV power.
ModbusTCP:
- Add register for ESS Maximum inverter power
- Add register for DVCC Maximum system charge current
Developers
- Enabling ssh is now a separate setting; no longer tied together with the Remote Support Setting. For this and some other changes; we've start using iptables firewalling.
---
Do not contact any support channels when having issues when running a beta firmware version. Instead; report on community via the link on the top of this email, or contact me directly.
Also, never run beta firmware in systems that need to just work.
For more information on the Venus OS beta-test program, see here: https://www.victronenergy.com/live/ccgx:beta-testing
Thank you for your testing efforts again! And have a good night, or day,
Matthijs Vader
Ps. changes of previous testing version:
Changes in v2.30~36, up to and including ~40
MFD App:
- Feature: Add an experimental mobile view (scrolling enabled on mobile browsers /w slim aspect-ratios.)
- Bugfix: a 'gray box' can be seen at the bottom of the screen on Ubuntu/Firefox browsers.
- Bugfix: The Solar Charger component appears to be flickering near 0W inputs.
- Bugfix: The layout jitters for a short while after closing the remote console.
- Enhancement: Add a nice and friendly boat image to DC Loads component.
- Enhancement: Streamline all metrics components to be slimmer and make the relevant data 'pop up'. Show a shorthand version of the device name in the component.
- Enhancement: Streamline the batteries component. Show a slim battery component when the system sees only a single battery monitor.
- Enhancement: Change the Input Limit buttons in Charger and Inverter/Charger components.
- Enhancement: Remove the Connection Status button.
- Enhancement: Make the background color a bit darker.
- Enhancement: Make the components align to a virtual rectangle.
Other
- Fix issue in saving the generator run time; thank you Paul B for reporting this one.
- Change 'Periodic test run" into "Periodic run"; less confusing. Thank you Paul B.
- Make it clear that the demo mode is enabled; by periodically showing a pop-up.
- Make it clear on the Battery measurements setup page (for the MFDs), that the main battery monitor is always enabled.
- Prepare remote firmware update functionality for future products.
ModbusTCP:
- add register for AC-input Phase rotation warning for inverter/charger systems.
- add register that shows MPPT solar charger operational state (0=Off;1=Voltage/current limited;2=MPPT active;255=Not available)
- add register 2902 for ESS mode: 1: Enabled with phase compensation. 2: Enabled without phase compensation, 3: external control.
Change log v2.30~27 to ~35:
General:
* Major update of the new Marine MFD integration.
* Add Settings -> System Setup -> Battery measurements page. This is where you can configure the `Batteries` page in the MFD Integration app. Also known by some as the HTML5 feature. See this video: https://www.dropbox.com/s/nlvqttx320zyaba/Battery%20Measurements.mov?dl=0
* Add Battery temperature measured by Multis and Quattros: its shown in the menus; it can be selected to use it for Shared Temperature Sense; its logged to the VRM Portal; and its available on ModbusTCP.
* Add network watchdog: automatically reboot the Venus-device in case it has not been able to sent data to VRM for a while. See Settings -> VRM online portal -> Reboot device when no contact.
* Fix Remote VEConfigure being slow; this issue was introduced earlier in v2.30 development.
* Rename the "ESS" state to "External control" for solar chargers. This fixes the confusion around off-grid systems where no ESS was running; but still were reporting it. Thank you JohnC, Guy and others for reporting this.
* GX GSM: Enable the GPS also when there is no simcard inserted. Thank you Jondal for raising this.
* Generator start/stop: hide the battery monitor selection. It now always uses the same battery monitor as is used by the rest of the system. Except systems that already had a different battery monitor configured: their behaviour will not change by installing this update.
* Generator start/stop: log the condition that is causing the generator to be running to VRM so its possible to analyse why the generator was started. For now only visible on the XLS and CSV download buttons on VRM.
* Various fixes and improvements for the CANvu GX; there are no pending todos or open issues any more.
* Fix various touch & other issues in the gui
* Firmware updates: allow downgrading; this fixes the problem that it wasn't possible to go from a candidate version, v2.20~something for example, to the latest official version, v2.18 for
example, and back.
* Add support for the next generation of Zigbee to USB Converters - DRF2658C
* Fix Phoenix VE.Bus Inverters being called MultiPlus. They are now properly recognised as an Inverter.
* Add support for the new SmartSolar VE.Can chargers.
DVCC:
* Make multiple BMSes in the same system work well by making the BMS selection deterministic: it will use the BMS with the lowest configured BMS instance for DVCC. Any others are just shown in the menus. This allows, for example, to add a second Lynx Ion BMS with battery pack used for (only) a large electric bow-thruster; besides another pack thats used as the boats main service battery.
* Improve the Shared Temperature Sensor function: Multi/Quattro inverter/chargers, Venus GX temperature accessory and the VE.Can Solar Chargers were added as possible inputs to measure -and share- battery temperature. Before this change it only accepted BMV and Lynx Shunt battery monitors.
ESS:
* Fix ESS operation in systems with more than one VE.Bus system connected (second is then connected using a MK3-USB): ESS will always use the main VE.Bus system, selected by sorting on instance number.
CCGX only:
* Fix the CPU load. Thank you Torsten for raising this, its back at its normal level again.
ModbusTCP:
* Add registers for manual start, runtime, and RunByConditionCode which shows why the generator is running.
Developers & under the hood:
* store Multi/Quattro settings which are stored on the Venus-device per connection. These inclue the settings found in the Device list -> Multi/Quattro -> Alarm setup menu. Settings for devices connected on the on-board VE.Bus port will be maintained. But settings for devices connected using a MK3-USB, such as a RaspberryPi, will be reset to defaults.
* fix some bugs in vebus-updater
* fix some `corner issues` in time handling
* fix gui fixes related to mouse / touch / Remote Console
* fix (very rare) logging to VRM issue (unique-id file not found)
* VE.Direct: Add check that bidirectional communication is possible (except for BMV60x). In the support desk we have seen multipe self-made USB-VE.Direct cables now; of which only the RX signal works; rather than RX and TX. And that works somewhat; but not 100%; and nobody understands why. So; now the code tests if its a properly working cable; and if not; hides the connected device completely.
* enable zeroconf name resolution using mDNS and llmnrd: venus.local.
* Tested to work on iOS and macOS: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* Tested to work on Windows: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* But does not work on Android, since it does not seem to support any zeroconf style name resolution mechanism: https://bugs.chromium.org/p/chromium/issues/detail?id=405925&desc=2
Change log v2.30~24 up to and including v2.30~27
General:
* Fix setting the date & time not working properly for off-grid systems: changes to the date and time were only stored to the device when being rebooted from within the menus (which nobody ever does). Power cycling a unit would make it jump back to the previous date & time. This is now fixed. Note that only installations without internet were affected: with internet, the date and time are set automatically; as well as stored properly. This bug has always been in the system, since the first release.
* Debounce VE.Bus warnings: warnings now stay valid for at least 20 seconds in order to reduce the number of warning -> ok -> warning changes; notifications and VRM emails.
* Add the names of various new VE.Bus inverter/chargers
* ESS with DVCC enabled: Fix solar voltage offset not going into DVCC mode. Thank you Simon H. for finding and reporting this.
* Fix internet connection issues for a small number of systems; by lowering the MTU to 1450. If affected you typically see that logging data to VRM works, but Remote Console does not work; and Remote VEConfigure and Remote Firmware Update work partially: scanning typically works; but anything using full packet sizes; such as uploading a firmware file; or transferring the VEConfigure file; does not work and returns error 1300. More information here: https://community.victronenergy.com/questions/3608/how-to-solve-error-1300-on-remote-ve-configure.html.
GUI:
* Add manual mode for relay two (Venus GX) - Thank you Ole S. for contributing this.
* Add diagnostics page for Fiamm 48TL series batteries. Thank you Ivo G. for contributing this.
* Change the "Solar Charger" -> "BMS Controlled switch" into a reset button: the feature is auto-enabled. Therefor, having an on/off switch was confusing. Now
Under-the-hood & developer related changes:
* Fix that data was not sent to VRM in some rare occasions. Only seen on Warwick his beaglebone and new Venus devices not released yet (random entropy & python ssl patch).
* Nodejs 8.4.0 -> 8.15.0; preparing for node-red; see here: https://github.com/victronenergy/venus/issues/378.
* Add xupd and xupc: commandline firmware update tools for coming products
* Report data partition errors on the GUI & and on VRM (error 42).
* Update Oceanvolt drivers to latest versions
* Limit max logs size; reducing space on the data partition
* Remove /log symlink; Use /data/log
* Enable tun/tap for all kernels
* Enable netfilter for various kernels
* Re-enable rfkill for the CCGX kernel; its went missing in the change from 3.7 to 4.19
CHANGE LOG v2.22 -> v2.30~23
General:
* Add the first version of the Marine MFD aka Chart-plotter integration. Tested with the Navico brands; Garmin and Raymarine. See blogposts for more information. Note that this is not officially supported yet; we're still making lots of changes, and it doesn't work on a Raymarine display unless that is running a development firmware verions, and this is also pending official approval from the mentioned MFD manufacturers. More information here:
https://www.victronenergy.com/blog/2018/11/02/mets-2018-preview-glass-bridge-smart-everywhere/.
* Add multiple demos; One ESS demo, and two Marine/Motorhome oriented demos are available to choose from.
* GX GSM: Fix handling of bad PIN
* Add a low-cell voltage warning and alarm for Lynx Ion BMS systems. Not that this only works for the Lynx Ion BMS. It does not work for the (discontinued) Lynx Ion + Shunt models. It will first issue a warning; and that will change to an alarm once the voltage is so low that the system has disabled the 'allow-to-discharge' signal; which shuts down any connected inverters and other loads.
* Carlo Gavazzi Energy Meter power or current overload now results in no data being stored; this used to be a very high value; distorting the graphs on VRM. Thank you Tilo Ritz for reporting.
GUI:
* Fix mouse/touch getting stuck when touching cancel while the options menu is closing.
* Various small improvements; mostly to make it work better when using it on a touch device; such as the CANvu GX and as Remote Console is typically used.
* Fix duplicated vebus warning and alarms in the menu and notifications (bug was introduced in v2.18)
* Fix issue where en empty battery service appeared in the Device list when the `PageLynxIonDiagnostic` was entered
* Update Eastern Europe time zones; fixes issues with Romania and other countries
PV Inverter monitoring and control - add support for ABB PV-Inverters:
* Fix incorrect handling of negative power values. This caused logging of incorrect values: above 655 kW.
* Allow for types with dashes in the serial-numbers, such as ABB PV Inverters.
* Enable power limiting for ABB PV-inverters: same as Fronius Zero Feed-in; use the Fronius switch to enable it. Note that this is an opportunistic trial: it might work; might not; And if hard to fix we might consider not to fix it in case it doesn't work.
ESS:
* Fix bug in Scheduled charging that caused the PV to not be optimally used when in the scheduled charging window.
* When Active AC input is a generator, enable the Fronius zero-feedin limiter. Thanks to Simon Hackett for reporting.
* (Systems with CAN-bus BMS batteries, and DVCC enabled only): Compensate for PV-power when calculating maximum discharge power from BMS current limits.
DVCC:
* Fix CAN-Bus BMS overwriting the maximum charge current as configured in VEConfigure
Venus GX:
* Improve flexibility of the multiplier setting for the pulse counter; the spinbox has been replaced with a normal edit box where a number can be entered now; with up to 6 decimal places.
ModbusTCP:
* Make battery relay writable, i.e. Lynx Shunt (thanks Shane)
* Add paths related to charge current and temperature alarms.
Developers and others:
* CCGX: Update the kernel from 3.7 to 4.19.
* Reduce wear on the internal flash storage (remove the sync mount option from the /data partition & add express sync calls to all places that need it)
* Add a link local interface parallel to the ethernet: this make the link local address directly available instead of only after a DHCP timeout. See https://github.com/victronenergy/venus/issues/361
* Fix (very rare) issue that causes the internet connection not working on a CanVU (dns race condition)
* Raspberrypi 3B+: fix the wifi. Thanks to Per and others for helping us out.
* Update vbdup, the commandline tool to update a VE.Bus device, to version 1.00; lots of improvements, including -I think- that it can now also be used to update a MultiPlus-II and MultiGrid.
* rtl8723bu wifi driver: update to latest version to fix building for Linux 4.19. This driver is used in the Venus GX.
* Reduce CPU load when ESS is enabled; and also for ModbustCP connected PV Inverters
* Rename vecan-mk2 to mk2-dbus
* Update qt5 to qt5.11
* Further improve CCGX robustness by starting the watchdog really early (in the bootloader; u-boot)
* Generate an alarm (Error 42) in case the data partition can't be mounted
mvader (Victron Energy Staff)
asked
Good day beta-testers!
v2.30~43 is now available for testing. Please post feedback below this item in the Answers section.
This release contains more minor fixes and improvements.
Marine MFD Integration
As explained before, the main new feature in v2.30 is the integration with MFDs as used on the helm of a yacht. And that feature is ready for testing. To do so, enable MQTT in Settings -> Services, and then open a webbrowser and navigate to http://[ipaddress]/app. In some cases http://venus.local/ will work as well. Also it can already be tested on compatible Navico and Garmin displays. Preliminary documentation is available here:
- https://www.victronenergy.com/live/venus-os:mfd-navico
- https://docs.victronenergy.com/gx/mfd-garmin.html
Changes in v2.30~41 up to and including v2.30~43
General:
- Remote Console now uses a different authentication mechanism. This (finally!) fixes a long running problem for some customers related to the IP Address being used for authentication.
- Fix issue when removing an MK3-USB from the GX device; in case you are wondering: using an MK3-USB together with a GX device is quite an uncommon configuration. Its used with RaspberryPis, and also used to connect a second inverter/charger system to a GX device.
- HTML5 app: various small improvements.
- Improve reporting and working with Overload, Temperature, Low battery and High DC ripple alarms and warnings. Both in the notifications page on the device itself as on VRM. In such event; now only one alarm needs to show up; not multiple at the same time.
- Fix issue in Remote VEConfigure: changing battery capacity and a few other settings do not require a system reset; but that reset was carried out anyway. Now, you can change those settings without a short, unannounced, blackout.
- Fix bug that, in certain specific conditions, caused a CPU overloaded system to hang; rather than restart and start clean.
ESS:
- Don't stop discharging when SOC indicates 0%. When Minimum SOC setting is configured to 0%; the system is now allowed to run until another threshold makes it stop; there is no more checking on SOC.
- Fix bug that caused the system to power the loads from the grid while in the scheduled charging window once the batteries were fully charged. Now; first the grid is used to fully charge the batteries, as it should when in a scheduled charging window, and once the batteries are full it prioritises PV over the grid, only using the latter in case there is not enough PV power.
ModbusTCP:
- Add register for ESS Maximum inverter power
- Add register for DVCC Maximum system charge current
Developers
- Enabling ssh is now a separate setting; no longer tied together with the Remote Support Setting. For this and some other changes; we've start using iptables firewalling.
---
Do not contact any support channels when having issues when running a beta firmware version. Instead; report on community via the link on the top of this email, or contact me directly.
Also, never run beta firmware in systems that need to just work.
For more information on the Venus OS beta-test program, see here: https://www.victronenergy.com/live/ccgx:beta-testing
Thank you for your testing efforts again! And have a good night, or day,
Matthijs Vader
Ps. changes of previous testing version:
Changes in v2.30~36, up to and including ~40
MFD App:
- Feature: Add an experimental mobile view (scrolling enabled on mobile browsers /w slim aspect-ratios.)
- Bugfix: a 'gray box' can be seen at the bottom of the screen on Ubuntu/Firefox browsers.
- Bugfix: The Solar Charger component appears to be flickering near 0W inputs.
- Bugfix: The layout jitters for a short while after closing the remote console.
- Enhancement: Add a nice and friendly boat image to DC Loads component.
- Enhancement: Streamline all metrics components to be slimmer and make the relevant data 'pop up'. Show a shorthand version of the device name in the component.
- Enhancement: Streamline the batteries component. Show a slim battery component when the system sees only a single battery monitor.
- Enhancement: Change the Input Limit buttons in Charger and Inverter/Charger components.
- Enhancement: Remove the Connection Status button.
- Enhancement: Make the background color a bit darker.
- Enhancement: Make the components align to a virtual rectangle.
Other
- Fix issue in saving the generator run time; thank you Paul B for reporting this one.
- Change 'Periodic test run" into "Periodic run"; less confusing. Thank you Paul B.
- Make it clear that the demo mode is enabled; by periodically showing a pop-up.
- Make it clear on the Battery measurements setup page (for the MFDs), that the main battery monitor is always enabled.
- Prepare remote firmware update functionality for future products.
ModbusTCP:
- add register for AC-input Phase rotation warning for inverter/charger systems.
- add register that shows MPPT solar charger operational state (0=Off;1=Voltage/current limited;2=MPPT active;255=Not available)
- add register 2902 for ESS mode: 1: Enabled with phase compensation. 2: Enabled without phase compensation, 3: external control.
Change log v2.30~27 to ~35:
General:
* Major update of the new Marine MFD integration.
* Add Settings -> System Setup -> Battery measurements page. This is where you can configure the `Batteries` page in the MFD Integration app. Also known by some as the HTML5 feature. See this video: https://www.dropbox.com/s/nlvqttx320zyaba/Battery%20Measurements.mov?dl=0
* Add Battery temperature measured by Multis and Quattros: its shown in the menus; it can be selected to use it for Shared Temperature Sense; its logged to the VRM Portal; and its available on ModbusTCP.
* Add network watchdog: automatically reboot the Venus-device in case it has not been able to sent data to VRM for a while. See Settings -> VRM online portal -> Reboot device when no contact.
* Fix Remote VEConfigure being slow; this issue was introduced earlier in v2.30 development.
* Rename the "ESS" state to "External control" for solar chargers. This fixes the confusion around off-grid systems where no ESS was running; but still were reporting it. Thank you JohnC, Guy and others for reporting this.
* GX GSM: Enable the GPS also when there is no simcard inserted. Thank you Jondal for raising this.
* Generator start/stop: hide the battery monitor selection. It now always uses the same battery monitor as is used by the rest of the system. Except systems that already had a different battery monitor configured: their behaviour will not change by installing this update.
* Generator start/stop: log the condition that is causing the generator to be running to VRM so its possible to analyse why the generator was started. For now only visible on the XLS and CSV download buttons on VRM.
* Various fixes and improvements for the CANvu GX; there are no pending todos or open issues any more.
* Fix various touch & other issues in the gui
* Firmware updates: allow downgrading; this fixes the problem that it wasn't possible to go from a candidate version, v2.20~something for example, to the latest official version, v2.18 for
example, and back.
* Add support for the next generation of Zigbee to USB Converters - DRF2658C
* Fix Phoenix VE.Bus Inverters being called MultiPlus. They are now properly recognised as an Inverter.
* Add support for the new SmartSolar VE.Can chargers.
DVCC:
* Make multiple BMSes in the same system work well by making the BMS selection deterministic: it will use the BMS with the lowest configured BMS instance for DVCC. Any others are just shown in the menus. This allows, for example, to add a second Lynx Ion BMS with battery pack used for (only) a large electric bow-thruster; besides another pack thats used as the boats main service battery.
* Improve the Shared Temperature Sensor function: Multi/Quattro inverter/chargers, Venus GX temperature accessory and the VE.Can Solar Chargers were added as possible inputs to measure -and share- battery temperature. Before this change it only accepted BMV and Lynx Shunt battery monitors.
ESS:
* Fix ESS operation in systems with more than one VE.Bus system connected (second is then connected using a MK3-USB): ESS will always use the main VE.Bus system, selected by sorting on instance number.
CCGX only:
* Fix the CPU load. Thank you Torsten for raising this, its back at its normal level again.
ModbusTCP:
* Add registers for manual start, runtime, and RunByConditionCode which shows why the generator is running.
Developers & under the hood:
* store Multi/Quattro settings which are stored on the Venus-device per connection. These inclue the settings found in the Device list -> Multi/Quattro -> Alarm setup menu. Settings for devices connected on the on-board VE.Bus port will be maintained. But settings for devices connected using a MK3-USB, such as a RaspberryPi, will be reset to defaults.
* fix some bugs in vebus-updater
* fix some `corner issues` in time handling
* fix gui fixes related to mouse / touch / Remote Console
* fix (very rare) logging to VRM issue (unique-id file not found)
* VE.Direct: Add check that bidirectional communication is possible (except for BMV60x). In the support desk we have seen multipe self-made USB-VE.Direct cables now; of which only the RX signal works; rather than RX and TX. And that works somewhat; but not 100%; and nobody understands why. So; now the code tests if its a properly working cable; and if not; hides the connected device completely.
* enable zeroconf name resolution using mDNS and llmnrd: venus.local.
* Tested to work on iOS and macOS: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* Tested to work on Windows: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* But does not work on Android, since it does not seem to support any zeroconf style name resolution mechanism: https://bugs.chromium.org/p/chromium/issues/detail?id=405925&desc=2
Change log v2.30~24 up to and including v2.30~27
General:
* Fix setting the date & time not working properly for off-grid systems: changes to the date and time were only stored to the device when being rebooted from within the menus (which nobody ever does). Power cycling a unit would make it jump back to the previous date & time. This is now fixed. Note that only installations without internet were affected: with internet, the date and time are set automatically; as well as stored properly. This bug has always been in the system, since the first release.
* Debounce VE.Bus warnings: warnings now stay valid for at least 20 seconds in order to reduce the number of warning -> ok -> warning changes; notifications and VRM emails.
* Add the names of various new VE.Bus inverter/chargers
* ESS with DVCC enabled: Fix solar voltage offset not going into DVCC mode. Thank you Simon H. for finding and reporting this.
* Fix internet connection issues for a small number of systems; by lowering the MTU to 1450. If affected you typically see that logging data to VRM works, but Remote Console does not work; and Remote VEConfigure and Remote Firmware Update work partially: scanning typically works; but anything using full packet sizes; such as uploading a firmware file; or transferring the VEConfigure file; does not work and returns error 1300. More information here: https://community.victronenergy.com/questions/3608/how-to-solve-error-1300-on-remote-ve-configure.html.
GUI:
* Add manual mode for relay two (Venus GX) - Thank you Ole S. for contributing this.
* Add diagnostics page for Fiamm 48TL series batteries. Thank you Ivo G. for contributing this.
* Change the "Solar Charger" -> "BMS Controlled switch" into a reset button: the feature is auto-enabled. Therefor, having an on/off switch was confusing. Now
Under-the-hood & developer related changes:
* Fix that data was not sent to VRM in some rare occasions. Only seen on Warwick his beaglebone and new Venus devices not released yet (random entropy & python ssl patch).
* Nodejs 8.4.0 -> 8.15.0; preparing for node-red; see here: https://github.com/victronenergy/venus/issues/378.
* Add xupd and xupc: commandline firmware update tools for coming products
* Report data partition errors on the GUI & and on VRM (error 42).
* Update Oceanvolt drivers to latest versions
* Limit max logs size; reducing space on the data partition
* Remove /log symlink; Use /data/log
* Enable tun/tap for all kernels
* Enable netfilter for various kernels
* Re-enable rfkill for the CCGX kernel; its went missing in the change from 3.7 to 4.19
CHANGE LOG v2.22 -> v2.30~23
General:
* Add the first version of the Marine MFD aka Chart-plotter integration. Tested with the Navico brands; Garmin and Raymarine. See blogposts for more information. Note that this is not officially supported yet; we're still making lots of changes, and it doesn't work on a Raymarine display unless that is running a development firmware verions, and this is also pending official approval from the mentioned MFD manufacturers. More information here:
https://www.victronenergy.com/blog/2018/11/02/mets-2018-preview-glass-bridge-smart-everywhere/.
* Add multiple demos; One ESS demo, and two Marine/Motorhome oriented demos are available to choose from.
* GX GSM: Fix handling of bad PIN
* Add a low-cell voltage warning and alarm for Lynx Ion BMS systems. Not that this only works for the Lynx Ion BMS. It does not work for the (discontinued) Lynx Ion + Shunt models. It will first issue a warning; and that will change to an alarm once the voltage is so low that the system has disabled the 'allow-to-discharge' signal; which shuts down any connected inverters and other loads.
* Carlo Gavazzi Energy Meter power or current overload now results in no data being stored; this used to be a very high value; distorting the graphs on VRM. Thank you Tilo Ritz for reporting.
GUI:
* Fix mouse/touch getting stuck when touching cancel while the options menu is closing.
* Various small improvements; mostly to make it work better when using it on a touch device; such as the CANvu GX and as Remote Console is typically used.
* Fix duplicated vebus warning and alarms in the menu and notifications (bug was introduced in v2.18)
* Fix issue where en empty battery service appeared in the Device list when the `PageLynxIonDiagnostic` was entered
* Update Eastern Europe time zones; fixes issues with Romania and other countries
PV Inverter monitoring and control - add support for ABB PV-Inverters:
* Fix incorrect handling of negative power values. This caused logging of incorrect values: above 655 kW.
* Allow for types with dashes in the serial-numbers, such as ABB PV Inverters.
* Enable power limiting for ABB PV-inverters: same as Fronius Zero Feed-in; use the Fronius switch to enable it. Note that this is an opportunistic trial: it might work; might not; And if hard to fix we might consider not to fix it in case it doesn't work.
ESS:
* Fix bug in Scheduled charging that caused the PV to not be optimally used when in the scheduled charging window.
* When Active AC input is a generator, enable the Fronius zero-feedin limiter. Thanks to Simon Hackett for reporting.
* (Systems with CAN-bus BMS batteries, and DVCC enabled only): Compensate for PV-power when calculating maximum discharge power from BMS current limits.
DVCC:
* Fix CAN-Bus BMS overwriting the maximum charge current as configured in VEConfigure
Venus GX:
* Improve flexibility of the multiplier setting for the pulse counter; the spinbox has been replaced with a normal edit box where a number can be entered now; with up to 6 decimal places.
ModbusTCP:
* Make battery relay writable, i.e. Lynx Shunt (thanks Shane)
* Add paths related to charge current and temperature alarms.
Developers and others:
* CCGX: Update the kernel from 3.7 to 4.19.
* Reduce wear on the internal flash storage (remove the sync mount option from the /data partition & add express sync calls to all places that need it)
* Add a link local interface parallel to the ethernet: this make the link local address directly available instead of only after a DHCP timeout. See https://github.com/victronenergy/venus/issues/361
* Fix (very rare) issue that causes the internet connection not working on a CanVU (dns race condition)
* Raspberrypi 3B+: fix the wifi. Thanks to Per and others for helping us out.
* Update vbdup, the commandline tool to update a VE.Bus device, to version 1.00; lots of improvements, including -I think- that it can now also be used to update a MultiPlus-II and MultiGrid.
* rtl8723bu wifi driver: update to latest version to fix building for Linux 4.19. This driver is used in the Venus GX.
* Reduce CPU load when ESS is enabled; and also for ModbustCP connected PV Inverters
* Rename vecan-mk2 to mk2-dbus
* Update qt5 to qt5.11
* Further improve CCGX robustness by starting the watchdog really early (in the bootloader; u-boot)
* Generate an alarm (Error 42) in case the data partition can't be mounted
Kris commented ·
4 Answers
VictronConnect App on Sailfish OS
Hi,
I am trying to connect to my Victron SmartSolar 75/10 to the VictronConnect App on my sailfish OS phone with Android Support.
The App starts and I can see the SmartSolar charger in the Bluetooth settings of the phone (I did not pair it), but the VictronConnect App does not see the Charger at all. It tells me that it need google location services every second or third search attempt, but it does not find the Charger.
Has any one got an idea or has succeeded to establish a connection with such a setup?
Thanks,
Holger
busman
asked
Hi,
I am trying to connect to my Victron SmartSolar 75/10 to the VictronConnect App on my sailfish OS phone with Android Support.
The App starts and I can see the SmartSolar charger in the Bluetooth settings of the phone (I did not pair it), but the VictronConnect App does not see the Charger at all. It tells me that it need google location services every second or third search attempt, but it does not find the Charger.
Has any one got an idea or has succeeded to establish a connection with such a setup?
Thanks,
Holger
0 Answers
Venus rPi and Bluetooth
I'm aware that Bluetooth is currently not supported in the Venus OS for Raspberry Pi. Is anyone currently working on this that I can share code/help with? Am wanting to pick up the data from a BlueSmart 24|16|1 in the Pi as I can't see that the Blue Smart has any cabled options (ve.Direct etc)
oli
asked
I'm aware that Bluetooth is currently not supported in the Venus OS for Raspberry Pi. Is anyone currently working on this that I can share code/help with? Am wanting to pick up the data from a BlueSmart 24|16|1 in the Pi as I can't see that the Blue Smart has any cabled options (ve.Direct etc)
Guy Stewart (Victron Energy Staff) commented ·
0 Answers
Venus OS script for controlling house heating system
Hi guys,
I would like to implement a Venus OS script for controlling house air-to-water heat pump (HP) based on the following conditions:
HP ON when (Battery SOC >= 60%) AND (Battery temperature <= 22 grd C) AND (More than 5 minutes PV Yield >= 1000W)
HP OFF when: (Battery SOC <= 40%) OR (Battery temperature >= 25 grd C) OR (More than 5 minutes PV Yield <= 100W)
For starting and stopping the HP, besides using the room thermostat and remote SMS control system, I will use a supplementary relay controlled by Venus OS running on RPI. My ESS and house heating system topology is depicted below.
[image]
Any hint is well appreciated.
Kind regards,
Mihai
MihaiR
asked
Hi guys,
I would like to implement a Venus OS script for controlling house air-to-water heat pump (HP) based on the following conditions:
HP ON when (Battery SOC >= 60%) AND (Battery temperature <= 22 grd C) AND (More than 5 minutes PV Yield >= 1000W)
HP OFF when: (Battery SOC <= 40%) OR (Battery temperature >= 25 grd C) OR (More than 5 minutes PV Yield <= 100W)
For starting and stopping the HP, besides using the room thermostat and remote SMS control system, I will use a supplementary relay controlled by Venus OS running on RPI. My ESS and house heating system topology is depicted below.
[image]
Any hint is well appreciated.
Kind regards,
Mihai
MihaiR commented ·
1 Answer
changelog for Venus OS v2.30~42 ?
@mvader (Victron Energy Staff)
I noticed Venus OS v2.30~42. - Can you please publish a changelog
Anil Ghatikar
asked
@mvader (Victron Energy Staff)
I noticed Venus OS v2.30~42. - Can you please publish a changelog
_OS_ answered ·
1 Answer
External/existing Node-Red connectivity to Venus OS
Is it possible, will it be possible to connect an external/existing Node-Red setup to Venus OS instead of using the internal Node-Red that will be available in a future release of Venus OS?
acs
asked
Is it possible, will it be possible to connect an external/existing Node-Red setup to Venus OS instead of using the internal Node-Red that will be available in a future release of Venus OS?
acs commented ·
3 Answers
Venus OS v2.30~40 available for testing
Good day beta-testers!
v2.30~40 is now available for testing. Please post feedback below this item in the Answers section.
As explained last time, the main new feature in v2.30 is the integration with MFDs as used on the helm of a yacht. And that feature is ready for testing. To do so, enable MQTT in Settings -> Services, and then open a webbrowser and navigate to http://[ipaddress]/app. In some cases http://venus.local/ will work as well. Also it can already be tested on compatible Navico and Garmin displays. Preliminary documentation is available here:
https://www.victronenergy.com/live/venus-os:mfd-navico
https://www.victronenergy.com/live/venus-os:mfd-garmin
Changes in v2.30~36, up to and including ~40
MFD App:
- Feature: Add an experimental mobile view (scrolling enabled on mobile browsers /w slim aspect-ratios.)
- Bugfix: a 'gray box' can be seen at the bottom of the screen on Ubuntu/Firefox browsers.
- Bugfix: The Solar Charger component appears to be flickering near 0W inputs.
- Bugfix: The layout jitters for a short while after closing the remote console.
- Enhancement: Add a nice and friendly boat image to DC Loads component.
- Enhancement: Streamline all metrics components to be slimmer and make the relevant data 'pop up'. Show a shorthand version of the device name in the component.
- Enhancement: Streamline the batteries component. Show a slim battery component when the system sees only a single battery monitor.
- Enhancement: Change the Input Limit buttons in Charger and Inverter/Charger components.
- Enhancement: Remove the Connection Status button.
- Enhancement: Make the background color a bit darker.
- Enhancement: Make the components align to a virtual rectangle.
Other
- Fix issue in saving the generator run time; thank you Paul B for reporting this one.
- Change 'Periodic test run" into "Periodic run"; less confusing. Thank you Paul B.
- Make it clear that the demo mode is enabled; by periodically showing a pop-up.
- Make it clear on the Battery measurements setup page (for the MFDs), that the main battery monitor is always enabled.
- Prepare remote firmware update functionality for future products.
ModbusTCP:
- add register for AC-input Phase rotation warning for inverter/charger systems.
- add register that shows MPPT solar charger operational state (0=Off;1=Voltage/current limited;2=MPPT active;255=Not available)
- add register 2902 for ESS mode: 1: Enabled with phase compensation. 2: Enabled without phase compensation, 3: external control.
---
Do not contact any support channels when having issues when running a beta firmware version. Instead; report on community via the link on the top of this email, or contact me directly.
Also, never run beta firmware in systems that need to just work.
For more information on the Venus OS beta-test program, see here: https://www.victronenergy.com/live/ccgx:beta-testing
Thank you for your testing efforts again! And have a good night, or day,
Matthijs Vader
Ps. changes of previous testing version:
Change log v2.30~27 to ~35:
General:
* Major update of the new Marine MFD integration.
* Add Settings -> System Setup -> Battery measurements page. This is where you can configure the `Batteries` page in the MFD Integration app. Also known by some as the HTML5 feature. See this video: https://www.dropbox.com/s/nlvqttx320zyaba/Battery%20Measurements.mov?dl=0
* Add Battery temperature measured by Multis and Quattros: its shown in the menus; it can be selected to use it for Shared Temperature Sense; its logged to the VRM Portal; and its available on ModbusTCP.
* Add network watchdog: automatically reboot the Venus-device in case it has not been able to sent data to VRM for a while. See Settings -> VRM online portal -> Reboot device when no contact.
* Fix Remote VEConfigure being slow; this issue was introduced earlier in v2.30 development.
* Rename the "ESS" state to "External control" for solar chargers. This fixes the confusion around off-grid systems where no ESS was running; but still were reporting it. Thank you JohnC, Guy and others for reporting this.
* GX GSM: Enable the GPS also when there is no simcard inserted. Thank you Jondal for raising this.
* Generator start/stop: hide the battery monitor selection. It now always uses the same battery monitor as is used by the rest of the system. Except systems that already had a different battery monitor configured: their behaviour will not change by installing this update.
* Generator start/stop: log the condition that is causing the generator to be running to VRM so its possible to analyse why the generator was started. For now only visible on the XLS and CSV download buttons on VRM.
* Various fixes and improvements for the CANvu GX; there are no pending todos or open issues any more.
* Fix various touch & other issues in the gui
* Firmware updates: allow downgrading; this fixes the problem that it wasn't possible to go from a candidate version, v2.20~something for example, to the latest official version, v2.18 for
example, and back.
* Add support for the next generation of Zigbee to USB Converters - DRF2658C
* Fix Phoenix VE.Bus Inverters being called MultiPlus. They are now properly recognised as an Inverter.
* Add support for the new SmartSolar VE.Can chargers.
DVCC:
* Make multiple BMSes in the same system work well by making the BMS selection deterministic: it will use the BMS with the lowest configured BMS instance for DVCC. Any others are just shown in the menus. This allows, for example, to add a second Lynx Ion BMS with battery pack used for (only) a large electric bow-thruster; besides another pack thats used as the boats main service battery.
* Improve the Shared Temperature Sensor function: Multi/Quattro inverter/chargers, Venus GX temperature accessory and the VE.Can Solar Chargers were added as possible inputs to measure -and share- battery temperature. Before this change it only accepted BMV and Lynx Shunt battery monitors.
ESS:
* Fix ESS operation in systems with more than one VE.Bus system connected (second is then connected using a MK3-USB): ESS will always use the main VE.Bus system, selected by sorting on instance number.
CCGX only:
* Fix the CPU load. Thank you Torsten for raising this, its back at its normal level again.
ModbusTCP:
* Add registers for manual start, runtime, and RunByConditionCode which shows why the generator is running.
Developers & under the hood:
* store Multi/Quattro settings which are stored on the Venus-device per connection. These inclue the settings found in the Device list -> Multi/Quattro -> Alarm setup menu. Settings for devices connected on the on-board VE.Bus port will be maintained. But settings for devices connected using a MK3-USB, such as a RaspberryPi, will be reset to defaults.
* fix some bugs in vebus-updater
* fix some `corner issues` in time handling
* fix gui fixes related to mouse / touch / Remote Console
* fix (very rare) logging to VRM issue (unique-id file not found)
* VE.Direct: Add check that bidirectional communication is possible (except for BMV60x). In the support desk we have seen multipe self-made USB-VE.Direct cables now; of which only the RX signal works; rather than RX and TX. And that works somewhat; but not 100%; and nobody understands why. So; now the code tests if its a properly working cable; and if not; hides the connected device completely.
* enable zeroconf name resolution using mDNS and llmnrd: venus.local.
* Tested to work on iOS and macOS: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* Tested to work on Windows: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* But does not work on Android, since it does not seem to support any zeroconf style name resolution mechanism: https://bugs.chromium.org/p/chromium/issues/detail?id=405925&desc=2
Change log v2.30~24 up to and including v2.30~27
General:
* Fix setting the date & time not working properly for off-grid systems: changes to the date and time were only stored to the device when being rebooted from within the menus (which nobody ever does). Power cycling a unit would make it jump back to the previous date & time. This is now fixed. Note that only installations without internet were affected: with internet, the date and time are set automatically; as well as stored properly. This bug has always been in the system, since the first release.
* Debounce VE.Bus warnings: warnings now stay valid for at least 20 seconds in order to reduce the number of warning -> ok -> warning changes; notifications and VRM emails.
* Add the names of various new VE.Bus inverter/chargers
* ESS with DVCC enabled: Fix solar voltage offset not going into DVCC mode. Thank you Simon H. for finding and reporting this.
* Fix internet connection issues for a small number of systems; by lowering the MTU to 1450. If affected you typically see that logging data to VRM works, but Remote Console does not work; and Remote VEConfigure and Remote Firmware Update work partially: scanning typically works; but anything using full packet sizes; such as uploading a firmware file; or transferring the VEConfigure file; does not work and returns error 1300. More information here: https://community.victronenergy.com/questions/3608/how-to-solve-error-1300-on-remote-ve-configure.html.
GUI:
* Add manual mode for relay two (Venus GX) - Thank you Ole S. for contributing this.
* Add diagnostics page for Fiamm 48TL series batteries. Thank you Ivo G. for contributing this.
* Change the "Solar Charger" -> "BMS Controlled switch" into a reset button: the feature is auto-enabled. Therefor, having an on/off switch was confusing. Now
Under-the-hood & developer related changes:
* Fix that data was not sent to VRM in some rare occasions. Only seen on Warwick his beaglebone and new Venus devices not released yet (random entropy & python ssl patch).
* Nodejs 8.4.0 -> 8.15.0; preparing for node-red; see here: https://github.com/victronenergy/venus/issues/378.
* Add xupd and xupc: commandline firmware update tools for coming products
* Report data partition errors on the GUI & and on VRM (error 42).
* Update Oceanvolt drivers to latest versions
* Limit max logs size; reducing space on the data partition
* Remove /log symlink; Use /data/log
* Enable tun/tap for all kernels
* Enable netfilter for various kernels
* Re-enable rfkill for the CCGX kernel; its went missing in the change from 3.7 to 4.19
CHANGE LOG v2.22 -> v2.30~23
General:
* Add the first version of the Marine MFD aka Chart-plotter integration. Tested with the Navico brands; Garmin and Raymarine. See blogposts for more information. Note that this is not officially supported yet; we're still making lots of changes, and it doesn't work on a Raymarine display unless that is running a development firmware verions, and this is also pending official approval from the mentioned MFD manufacturers. More information here:
https://www.victronenergy.com/blog/2018/11/02/mets-2018-preview-glass-bridge-smart-everywhere/.
* Add multiple demos; One ESS demo, and two Marine/Motorhome oriented demos are available to choose from.
* GX GSM: Fix handling of bad PIN
* Add a low-cell voltage warning and alarm for Lynx Ion BMS systems. Not that this only works for the Lynx Ion BMS. It does not work for the (discontinued) Lynx Ion + Shunt models. It will first issue a warning; and that will change to an alarm once the voltage is so low that the system has disabled the 'allow-to-discharge' signal; which shuts down any connected inverters and other loads.
* Carlo Gavazzi Energy Meter power or current overload now results in no data being stored; this used to be a very high value; distorting the graphs on VRM. Thank you Tilo Ritz for reporting.
GUI:
* Fix mouse/touch getting stuck when touching cancel while the options menu is closing.
* Various small improvements; mostly to make it work better when using it on a touch device; such as the CANvu GX and as Remote Console is typically used.
* Fix duplicated vebus warning and alarms in the menu and notifications (bug was introduced in v2.18)
* Fix issue where en empty battery service appeared in the Device list when the `PageLynxIonDiagnostic` was entered
* Update Eastern Europe time zones; fixes issues with Romania and other countries
PV Inverter monitoring and control - add support for ABB PV-Inverters:
* Fix incorrect handling of negative power values. This caused logging of incorrect values: above 655 kW.
* Allow for types with dashes in the serial-numbers, such as ABB PV Inverters.
* Enable power limiting for ABB PV-inverters: same as Fronius Zero Feed-in; use the Fronius switch to enable it. Note that this is an opportunistic trial: it might work; might not; And if hard to fix we might consider not to fix it in case it doesn't work.
ESS:
* Fix bug in Scheduled charging that caused the PV to not be optimally used when in the scheduled charging window.
* When Active AC input is a generator, enable the Fronius zero-feedin limiter. Thanks to Simon Hackett for reporting.
* (Systems with CAN-bus BMS batteries, and DVCC enabled only): Compensate for PV-power when calculating maximum discharge power from BMS current limits.
DVCC:
* Fix CAN-Bus BMS overwriting the maximum charge current as configured in VEConfigure
Venus GX:
* Improve flexibility of the multiplier setting for the pulse counter; the spinbox has been replaced with a normal edit box where a number can be entered now; with up to 6 decimal places.
ModbusTCP:
* Make battery relay writable, i.e. Lynx Shunt (thanks Shane)
* Add paths related to charge current and temperature alarms.
Developers and others:
* CCGX: Update the kernel from 3.7 to 4.19.
* Reduce wear on the internal flash storage (remove the sync mount option from the /data partition & add express sync calls to all places that need it)
* Add a link local interface parallel to the ethernet: this make the link local address directly available instead of only after a DHCP timeout. See https://github.com/victronenergy/venus/issues/361
* Fix (very rare) issue that causes the internet connection not working on a CanVU (dns race condition)
* Raspberrypi 3B+: fix the wifi. Thanks to Per and others for helping us out.
* Update vbdup, the commandline tool to update a VE.Bus device, to version 1.00; lots of improvements, including -I think- that it can now also be used to update a MultiPlus-II and MultiGrid.
* rtl8723bu wifi driver: update to latest version to fix building for Linux 4.19. This driver is used in the Venus GX.
* Reduce CPU load when ESS is enabled; and also for ModbustCP connected PV Inverters
* Rename vecan-mk2 to mk2-dbus
* Update qt5 to qt5.11
* Further improve CCGX robustness by starting the watchdog really early (in the bootloader; u-boot)
* Generate an alarm (Error 42) in case the data partition can't be mounted
==============================================
*|LIST:DESCRIPTION|*
Note that to unsubscribe, hitting the unsubscribe link below does not work. Instead, change your system to work on Official-releases. Instead of working on test versions. Which by the way is never advised for customer installations. More information here:
https://www.victronenergy.com/live/ccgx:beta-testing
Unsubscribe *|EMAIL|* from this list:
*|UNSUB|*
mvader (Victron Energy Staff)
asked
Good day beta-testers!
v2.30~40 is now available for testing. Please post feedback below this item in the Answers section.
As explained last time, the main new feature in v2.30 is the integration with MFDs as used on the helm of a yacht. And that feature is ready for testing. To do so, enable MQTT in Settings -> Services, and then open a webbrowser and navigate to http://[ipaddress]/app. In some cases http://venus.local/ will work as well. Also it can already be tested on compatible Navico and Garmin displays. Preliminary documentation is available here:
https://www.victronenergy.com/live/venus-os:mfd-navico
https://www.victronenergy.com/live/venus-os:mfd-garmin
Changes in v2.30~36, up to and including ~40
MFD App:
- Feature: Add an experimental mobile view (scrolling enabled on mobile browsers /w slim aspect-ratios.)
- Bugfix: a 'gray box' can be seen at the bottom of the screen on Ubuntu/Firefox browsers.
- Bugfix: The Solar Charger component appears to be flickering near 0W inputs.
- Bugfix: The layout jitters for a short while after closing the remote console.
- Enhancement: Add a nice and friendly boat image to DC Loads component.
- Enhancement: Streamline all metrics components to be slimmer and make the relevant data 'pop up'. Show a shorthand version of the device name in the component.
- Enhancement: Streamline the batteries component. Show a slim battery component when the system sees only a single battery monitor.
- Enhancement: Change the Input Limit buttons in Charger and Inverter/Charger components.
- Enhancement: Remove the Connection Status button.
- Enhancement: Make the background color a bit darker.
- Enhancement: Make the components align to a virtual rectangle.
Other
- Fix issue in saving the generator run time; thank you Paul B for reporting this one.
- Change 'Periodic test run" into "Periodic run"; less confusing. Thank you Paul B.
- Make it clear that the demo mode is enabled; by periodically showing a pop-up.
- Make it clear on the Battery measurements setup page (for the MFDs), that the main battery monitor is always enabled.
- Prepare remote firmware update functionality for future products.
ModbusTCP:
- add register for AC-input Phase rotation warning for inverter/charger systems.
- add register that shows MPPT solar charger operational state (0=Off;1=Voltage/current limited;2=MPPT active;255=Not available)
- add register 2902 for ESS mode: 1: Enabled with phase compensation. 2: Enabled without phase compensation, 3: external control.
---
Do not contact any support channels when having issues when running a beta firmware version. Instead; report on community via the link on the top of this email, or contact me directly.
Also, never run beta firmware in systems that need to just work.
For more information on the Venus OS beta-test program, see here: https://www.victronenergy.com/live/ccgx:beta-testing
Thank you for your testing efforts again! And have a good night, or day,
Matthijs Vader
Ps. changes of previous testing version:
Change log v2.30~27 to ~35:
General:
* Major update of the new Marine MFD integration.
* Add Settings -> System Setup -> Battery measurements page. This is where you can configure the `Batteries` page in the MFD Integration app. Also known by some as the HTML5 feature. See this video: https://www.dropbox.com/s/nlvqttx320zyaba/Battery%20Measurements.mov?dl=0
* Add Battery temperature measured by Multis and Quattros: its shown in the menus; it can be selected to use it for Shared Temperature Sense; its logged to the VRM Portal; and its available on ModbusTCP.
* Add network watchdog: automatically reboot the Venus-device in case it has not been able to sent data to VRM for a while. See Settings -> VRM online portal -> Reboot device when no contact.
* Fix Remote VEConfigure being slow; this issue was introduced earlier in v2.30 development.
* Rename the "ESS" state to "External control" for solar chargers. This fixes the confusion around off-grid systems where no ESS was running; but still were reporting it. Thank you JohnC, Guy and others for reporting this.
* GX GSM: Enable the GPS also when there is no simcard inserted. Thank you Jondal for raising this.
* Generator start/stop: hide the battery monitor selection. It now always uses the same battery monitor as is used by the rest of the system. Except systems that already had a different battery monitor configured: their behaviour will not change by installing this update.
* Generator start/stop: log the condition that is causing the generator to be running to VRM so its possible to analyse why the generator was started. For now only visible on the XLS and CSV download buttons on VRM.
* Various fixes and improvements for the CANvu GX; there are no pending todos or open issues any more.
* Fix various touch & other issues in the gui
* Firmware updates: allow downgrading; this fixes the problem that it wasn't possible to go from a candidate version, v2.20~something for example, to the latest official version, v2.18 for
example, and back.
* Add support for the next generation of Zigbee to USB Converters - DRF2658C
* Fix Phoenix VE.Bus Inverters being called MultiPlus. They are now properly recognised as an Inverter.
* Add support for the new SmartSolar VE.Can chargers.
DVCC:
* Make multiple BMSes in the same system work well by making the BMS selection deterministic: it will use the BMS with the lowest configured BMS instance for DVCC. Any others are just shown in the menus. This allows, for example, to add a second Lynx Ion BMS with battery pack used for (only) a large electric bow-thruster; besides another pack thats used as the boats main service battery.
* Improve the Shared Temperature Sensor function: Multi/Quattro inverter/chargers, Venus GX temperature accessory and the VE.Can Solar Chargers were added as possible inputs to measure -and share- battery temperature. Before this change it only accepted BMV and Lynx Shunt battery monitors.
ESS:
* Fix ESS operation in systems with more than one VE.Bus system connected (second is then connected using a MK3-USB): ESS will always use the main VE.Bus system, selected by sorting on instance number.
CCGX only:
* Fix the CPU load. Thank you Torsten for raising this, its back at its normal level again.
ModbusTCP:
* Add registers for manual start, runtime, and RunByConditionCode which shows why the generator is running.
Developers & under the hood:
* store Multi/Quattro settings which are stored on the Venus-device per connection. These inclue the settings found in the Device list -> Multi/Quattro -> Alarm setup menu. Settings for devices connected on the on-board VE.Bus port will be maintained. But settings for devices connected using a MK3-USB, such as a RaspberryPi, will be reset to defaults.
* fix some bugs in vebus-updater
* fix some `corner issues` in time handling
* fix gui fixes related to mouse / touch / Remote Console
* fix (very rare) logging to VRM issue (unique-id file not found)
* VE.Direct: Add check that bidirectional communication is possible (except for BMV60x). In the support desk we have seen multipe self-made USB-VE.Direct cables now; of which only the RX signal works; rather than RX and TX. And that works somewhat; but not 100%; and nobody understands why. So; now the code tests if its a properly working cable; and if not; hides the connected device completely.
* enable zeroconf name resolution using mDNS and llmnrd: venus.local.
* Tested to work on iOS and macOS: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* Tested to work on Windows: a Venus device can now be found on those clients by typing http://venus.local in a webbrowser.
* But does not work on Android, since it does not seem to support any zeroconf style name resolution mechanism: https://bugs.chromium.org/p/chromium/issues/detail?id=405925&desc=2
Change log v2.30~24 up to and including v2.30~27
General:
* Fix setting the date & time not working properly for off-grid systems: changes to the date and time were only stored to the device when being rebooted from within the menus (which nobody ever does). Power cycling a unit would make it jump back to the previous date & time. This is now fixed. Note that only installations without internet were affected: with internet, the date and time are set automatically; as well as stored properly. This bug has always been in the system, since the first release.
* Debounce VE.Bus warnings: warnings now stay valid for at least 20 seconds in order to reduce the number of warning -> ok -> warning changes; notifications and VRM emails.
* Add the names of various new VE.Bus inverter/chargers
* ESS with DVCC enabled: Fix solar voltage offset not going into DVCC mode. Thank you Simon H. for finding and reporting this.
* Fix internet connection issues for a small number of systems; by lowering the MTU to 1450. If affected you typically see that logging data to VRM works, but Remote Console does not work; and Remote VEConfigure and Remote Firmware Update work partially: scanning typically works; but anything using full packet sizes; such as uploading a firmware file; or transferring the VEConfigure file; does not work and returns error 1300. More information here: https://community.victronenergy.com/questions/3608/how-to-solve-error-1300-on-remote-ve-configure.html.
GUI:
* Add manual mode for relay two (Venus GX) - Thank you Ole S. for contributing this.
* Add diagnostics page for Fiamm 48TL series batteries. Thank you Ivo G. for contributing this.
* Change the "Solar Charger" -> "BMS Controlled switch" into a reset button: the feature is auto-enabled. Therefor, having an on/off switch was confusing. Now
Under-the-hood & developer related changes:
* Fix that data was not sent to VRM in some rare occasions. Only seen on Warwick his beaglebone and new Venus devices not released yet (random entropy & python ssl patch).
* Nodejs 8.4.0 -> 8.15.0; preparing for node-red; see here: https://github.com/victronenergy/venus/issues/378.
* Add xupd and xupc: commandline firmware update tools for coming products
* Report data partition errors on the GUI & and on VRM (error 42).
* Update Oceanvolt drivers to latest versions
* Limit max logs size; reducing space on the data partition
* Remove /log symlink; Use /data/log
* Enable tun/tap for all kernels
* Enable netfilter for various kernels
* Re-enable rfkill for the CCGX kernel; its went missing in the change from 3.7 to 4.19
CHANGE LOG v2.22 -> v2.30~23
General:
* Add the first version of the Marine MFD aka Chart-plotter integration. Tested with the Navico brands; Garmin and Raymarine. See blogposts for more information. Note that this is not officially supported yet; we're still making lots of changes, and it doesn't work on a Raymarine display unless that is running a development firmware verions, and this is also pending official approval from the mentioned MFD manufacturers. More information here:
https://www.victronenergy.com/blog/2018/11/02/mets-2018-preview-glass-bridge-smart-everywhere/.
* Add multiple demos; One ESS demo, and two Marine/Motorhome oriented demos are available to choose from.
* GX GSM: Fix handling of bad PIN
* Add a low-cell voltage warning and alarm for Lynx Ion BMS systems. Not that this only works for the Lynx Ion BMS. It does not work for the (discontinued) Lynx Ion + Shunt models. It will first issue a warning; and that will change to an alarm once the voltage is so low that the system has disabled the 'allow-to-discharge' signal; which shuts down any connected inverters and other loads.
* Carlo Gavazzi Energy Meter power or current overload now results in no data being stored; this used to be a very high value; distorting the graphs on VRM. Thank you Tilo Ritz for reporting.
GUI:
* Fix mouse/touch getting stuck when touching cancel while the options menu is closing.
* Various small improvements; mostly to make it work better when using it on a touch device; such as the CANvu GX and as Remote Console is typically used.
* Fix duplicated vebus warning and alarms in the menu and notifications (bug was introduced in v2.18)
* Fix issue where en empty battery service appeared in the Device list when the `PageLynxIonDiagnostic` was entered
* Update Eastern Europe time zones; fixes issues with Romania and other countries
PV Inverter monitoring and control - add support for ABB PV-Inverters:
* Fix incorrect handling of negative power values. This caused logging of incorrect values: above 655 kW.
* Allow for types with dashes in the serial-numbers, such as ABB PV Inverters.
* Enable power limiting for ABB PV-inverters: same as Fronius Zero Feed-in; use the Fronius switch to enable it. Note that this is an opportunistic trial: it might work; might not; And if hard to fix we might consider not to fix it in case it doesn't work.
ESS:
* Fix bug in Scheduled charging that caused the PV to not be optimally used when in the scheduled charging window.
* When Active AC input is a generator, enable the Fronius zero-feedin limiter. Thanks to Simon Hackett for reporting.
* (Systems with CAN-bus BMS batteries, and DVCC enabled only): Compensate for PV-power when calculating maximum discharge power from BMS current limits.
DVCC:
* Fix CAN-Bus BMS overwriting the maximum charge current as configured in VEConfigure
Venus GX:
* Improve flexibility of the multiplier setting for the pulse counter; the spinbox has been replaced with a normal edit box where a number can be entered now; with up to 6 decimal places.
ModbusTCP:
* Make battery relay writable, i.e. Lynx Shunt (thanks Shane)
* Add paths related to charge current and temperature alarms.
Developers and others:
* CCGX: Update the kernel from 3.7 to 4.19.
* Reduce wear on the internal flash storage (remove the sync mount option from the /data partition & add express sync calls to all places that need it)
* Add a link local interface parallel to the ethernet: this make the link local address directly available instead of only after a DHCP timeout. See https://github.com/victronenergy/venus/issues/361
* Fix (very rare) issue that causes the internet connection not working on a CanVU (dns race condition)
* Raspberrypi 3B+: fix the wifi. Thanks to Per and others for helping us out.
* Update vbdup, the commandline tool to update a VE.Bus device, to version 1.00; lots of improvements, including -I think- that it can now also be used to update a MultiPlus-II and MultiGrid.
* rtl8723bu wifi driver: update to latest version to fix building for Linux 4.19. This driver is used in the Venus GX.
* Reduce CPU load when ESS is enabled; and also for ModbustCP connected PV Inverters
* Rename vecan-mk2 to mk2-dbus
* Update qt5 to qt5.11
* Further improve CCGX robustness by starting the watchdog really early (in the bootloader; u-boot)
* Generate an alarm (Error 42) in case the data partition can't be mounted
==============================================
*|LIST:DESCRIPTION|*
Note that to unsubscribe, hitting the unsubscribe link below does not work. Instead, change your system to work on Official-releases. Instead of working on test versions. Which by the way is never advised for customer installations. More information here:
https://www.victronenergy.com/live/ccgx:beta-testing
Unsubscribe *|EMAIL|* from this list:
*|UNSUB|*
JasonTav commented ·
6 Answers
Can I connect 2 non-Victron inverters to Venus OS?
Hi, I have a setup with 2 Axpert inverters of 4kW each connected in parallel to 12 PV panels, the grid, 2 Blue Nova batteries and the load. I want to install a Venus OS monitoring system on raspberry Pi. Blue Nova has confirmed that I can put the batteries in parallel and connect just one of them to collect information from both. Can I do the same with the Axperts, or should I connect both of them with the Venus system separately with their own RS485/USB cable? If so, how will Venus deal with the different inputs? Many thanks.
BasZ
asked
Hi, I have a setup with 2 Axpert inverters of 4kW each connected in parallel to 12 PV panels, the grid, 2 Blue Nova batteries and the load. I want to install a Venus OS monitoring system on raspberry Pi. Blue Nova has confirmed that I can put the batteries in parallel and connect just one of them to collect information from both. Can I do the same with the Axperts, or should I connect both of them with the Venus system separately with their own RS485/USB cable? If so, how will Venus deal with the different inputs? Many thanks.
Anil Ghatikar answered ·
3 Answers
Does vrmlogger perform any averaging based on log interval?
Hello,
I'd like to know whether VRMlogger uploads instantaneous data from the dbus, or whether there is some averaging done?
For example, If one updates a value on the d-bus every 30 seconds while the Vrmlogger /LogInterval is set to 600 seconds, is any averaging done on the data?
Thank you,
Ryan
ryanb
asked
Hello,
I'd like to know whether VRMlogger uploads instantaneous data from the dbus, or whether there is some averaging done?
For example, If one updates a value on the d-bus every 30 seconds while the Vrmlogger /LogInterval is set to 600 seconds, is any averaging done on the data?
Thank you,
Ryan
mvader (Victron Energy Staff) answered ·
1 Answer
can I connect and monitor my Digital Multi Controller GX system to my home computers via CAT6?
my camper van is parked beside my house, too far for Bluetooth.
michael shore
asked
my camper van is parked beside my house, too far for Bluetooth.
WKirby answered ·
1 Answer
Modifications
16 People are following this space.
