All Posts in Modifications

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

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

• v2.70~5 announcement
• v2.70~6 announcement
• v2.70~8 to ~11 announcement
• v2.70~12 to ~15 announcement
• v2.70~16 announcement

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]

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

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.

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]

I'd like to reopen discussion on this topic. I'm a novice and freely admit that I really don't understand all aspects of how to get this to work. So I may be totally off with this so please correct me if I'm wrong. I've read this thread:

https://groups.google.com/forum/#!msg/victron-dev-venus/mejgJbMjU34/yogWAU5wCAAJ;context-place=forum/victron-dev-venus

I purchased the same board as what's here, the Expander Pi with the mcp3208 12-bit ADC.

From reading this, I'm a bit confused how to wire this up. In that thread, they point to the reference voltage of 1.8v. However the expander pi has a reference voltage of 4.096. But in other threads, they talk about a reference voltage of 5v. I also see the schematic of the BBB Cape and it says 5v as well:

[image]

I'm not sure what is correct or if the reference voltage even matters since both are 12-bit ADCs, the reference voltage shouldn't matter as it's just reading the resistance of the sender. But then I'm confused on how to wire this up with the Expander Pi. Anyone who has this board, would they care to share their setup, possibly with photos or diagrams? I'd appreciate it.

tagging @WKirby as you've always been super helpful!

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)?

can someone help guide me？I am a battery dealer，I want to build communication between Phoenix series inverters and my lithium batteries，please guide me how to do it，thanks

my email address qi5200@foxmail.com

Hello All,

I have been digging through my Cerbo GX settings trying to find a way to display data from both of my PV controllers on the main screen. I found this image online that shows exactly what I'm trying to do.... Any idea how to get this additional data to appear on the display as shown below?

[image]

See my first comment below... mqtt doesn't work for this, but dbus does

tl;dr: How can I emulate a et340 meter on the MQTT bus? What do I need to publish to make Venus believe there is a meter there?

I already have an SMA system installed which includes a SMA Home Manager (SMA's version of the ET340: a meter at the grid connection point). I want to extend my system with a Multiplus-ii and add some storage.

Let's get this out of the way: I know the SMA meter is not officially supported.

SMA's meter outputs the values it sees at the grid connection point once per second, and it does this via multicast. I have written a little python script which subscribes to the multicast, and provides the output like this:

A:  buy: 0.0 A: sell: 821.2 -------------- L1  buy: 0.0 L1 sell: 381.6 L2  buy: 0.0 L2 sell: 81.6 L3  buy: 0.0 L3 sell: 358.0 

The above table is my current buy and sell across all phases ("A"), where I am currently selling 821.2W and buying 0. The values are broken into each phase (so L1 is selling 381, L2 81, and L3 358). There is much more available in the data from the meter, I am only focusing on what is necessary to emulate the 340.

The script is available here: https://gist.github.com/mitchese/afd823c3c5036c5b0e5394625f1a81e4

As I understand the ET340, it connects to the Venus via rs485, and then a cgwacs process is responsible for taking data from RS485 and putting it on dbus. I've also read that MQTT can be used for writing things into Venus as well. My idea is to write a simple python script which connects to the SMA broadcasts, massages the data to whatever venus would expect, and publishes this via MQTT. This should be darn close to what cgwacs is doing.

I have done some publishing to the topics (*** removed my device id) with some bogus-but-sane values to see if I can get my Venus GX to think I have a meter.

W/**********/grid/33/Ac/Energy/Forward {"value": 5000.0} W/**********/grid/33/Ac/Energy/Reverse {"value": 5000.0} W/**********/grid/33/Ac/Power W/**********/grid/33/Ac/L1/Current '{"value": 123.0}' W/**********/grid/33/Ac/L1/Energy/Forward '{"value": 30.0}' W/**********/grid/33/Ac/L1/Energy/Reverse '{"value": 500.0}' W/**********/grid/33/Ac/L1/Power '{"value": 300.0}' W/**********/grid/33/Ac/L1/Voltage '{"value": 230.0}' ...

but this is just a bit of publishing in the dark. I don't actually have a device id, 33 was just a guess. Anyone have some tips on how I can use MQTT?

I also tried a publish to W/***/system/0/Ac/Grid/DeviceType {"value": 340} to see if that would trigger an adoption of the 340 meter.

Currently I have an ET340 for testing and a Venus GX - there is nothing hooked up yet and I'll be ordering the multiplus as soon as I can get this setup.

Good evening!

A new version available to test, v2.70~18. It has one change, a bugfix, reported by @Roman Dvorak: thank you!

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

There is still one more open issue, which proves hard to fix. Its that the tanks can go missing sometimes, ie. hidden on the mobile overview as well as the tank overview page, while still visible on the Device list page. It could be that we have it fixed tomorrow, but can also take another week. So, no more official release this week.

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

Note: Below is a condensed changelog with everything in it from the start of v2.70 development.

New in ~18:

• Fix transmission of data to VRM not working in a specific situation, which was that a BMV or other VE.Direct product had to be configured with a custom name having non-ASCII characters. And besides data transmission to the VRM portal, also other places were checked and where necessary fixed to cater for that. This used to work fine in v2.66, and was a regression introduced during v2.70 development. Thank you @Roman Dvorak for reporting this!

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

• v2.70~5 announcement
• v2.70~6 announcement
• v2.70~8 to ~11 announcement
• v2.70~12 to ~15 announcement
• v2.70~16 announcement
• v2.70~17 announcement

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]

BMV-712 - Is VE Direct 5V tolerant. If not do I have a 3.3V power at pin 4 for building a easy level adjust?

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

Can someone tell me what to send to the MPPT to set register 0x200E to b0100001. I have 
connected it to the serial port of an Arduino and write the program in C. 
Reading out HEX values already works. 

Many Thanks.

Kann mir jemand sagen was ich an den MPPT senden muss um das Register 0x200E auf  b0100001 zu setzen. Ich habe ihn an der seriellen Schnittstelle eines Arduinos angeschlossen und schreibe das Programm in C. 

HEX Werte auslesen funktioniert bereits.



Vielen Dank.   
Markus

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?

I like the html5 app on the Venus But it was not ease to modify. So I used Paho JavaScript Client MQTT and made an HTML page called index.html. I up loaded it, paho, and 2 bmp files with sftp to /var/www/venus/kelly/. I open http://venus.local/kelly in edge. this works with the venus and a 15 kw Quattro. I would like if get some to see if it works with other inverters.

[image]

I could not upload the files here. So the files are at horns.pw/temp

Has anyone been successful in setting up alternative alert notifications (eg. WhatsApp messages instead of emails etc)?

Hello,

I was wondering if it is possible for the VRM app or even Victron connect to alert a user of alarms that have been set up as an alternative to the email alerts?

Some users have email but they never check them so are often unaware of events on their systems.

UPDATE 2021-06-05 morning: (text removed to keep it short).

UPDATE 2021-06-05 22:00: Beta version v2.70~16 had an issue, for which we decided to remove it from the auto-update list within hours of making it available. This is solved in v2.70~17, which is now available for download and in the auto install system. Compared to v2.70~17 has one fix: it fixes the problem that devices were missing from the Device list page on the gui. Also while looking into that we found an open issue, related to tanks, which I added further below. See "known issues".

Good evening!

End of our afternoon, we made v2.70~16 is available for testing in the field.

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

To learn more about the changes made in earlier v2.70 beta versions, make sure to read these two links:

• v2.70~5 announcement
• v2.70~6 announcement
• v2.70~8 to ~11 announcement
• v2.70~12 to ~15 announcement

What to test?

For those having tank levels on their GX device, the new tank overview. Screenshot below.

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~16 & v2.70~17

• 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 their push an getting the tanks full featured such as having configurable alarms.
• Use the same tank name in the alarms, the Device list, the mobile overview as well as the new tank overview page.

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.

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.

Known issues

• In some cases a tank doesn't show when selecting the tank type filter button on the bottom. And also in the mobile overview tanks can go missing. This is being looked into.

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]

Hey guys, i used google apps script and an Apple shortcut to create a "Where is my van?!" button (i maybe forget a lot where i park...). It also works on iphones and with google maps instead of apple maps

Video below, beware, there is a lot of hair. :D

If there is interested in this project, ill put in on github in the coming days.

Edit: This actually can be completely done in apple shortcut:

https://www.icloud.com/shortcuts/99e4bf99096c45979f900dfcdb30df14

Its necessary to turn on untrusted shortcuts in settings -> shortcuts. If you dont trust me, you can check out all the steps before running it yourself. During setup it will ask for your credentials and site id (find it in the url when you have your site open). Note: two factor auth will break it.

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]

G'day! I was able to connect RPi to MPPT 75-15 via VE.Direct to USB successfully, but following the Q&A on below page, I could not get RPi to recognise MPPT on pin 6, 8, 10. I have used a simple BSS138 based bi-directional level-shifted 5V from MPPT end to 3.3V RPi GPIO. Are there any other settings that have to be done on the RPi side? Any light from someone resolved similar issue is much appreciated!

https://community.victronenergy.com/questions/23853/connect-raspberry-pi-directly-to-mppt-over-serial.html

Components: Raspberry Pi 3 B+ with Venus OS v2.62, MPPT 75/15 v1.54

UPDATE 2021-01-11: see accepted answer, the green one - usually on top.

ORIGINAL

Hi all,

As some of you know, Venus OS for raspberrypi is a hobby project by our developers, worked on in their free time.

And raspberrypi4 support has been wanted and asked for since a while now, as thats the now commonly available raspberrypi model.

We hoped and waited for someone in the community to step up and do the work, but that didn't happen. Perhaps too specialised a set of skills required (openembedded, linux, and-so-forth) - and I must admit that its quite the time investment to work on that.

Anyway, the good news is that we have a new set of images available. One image for the raspberrypi2 and 3, and another for the raspberrypi4.

So now, rather than looking to - or waiting for - the community to do the development work, we're hoping for people to do the testing work. Welcome to comment what work in your system and what does not.

Enjoy, Matthijs

Changes compared to our existing raspberrypi images:

1. Update linux from 4.9 to 4.19
2. The whole sdcard is now used and roughly 1/3 is assigned to /data
3. both root filesystems are also increased to roughly 1/3 each
4. u-boot settings are now stored redundantly on the sdcard; the FAT

   partition is no longer written to.

Not much has been tested, so the question is how many thing still work.

Note: these images are intended for that, testing, don't use them in anything serious. There are no automatic updates / bug fixes e.g.

This code is open source, and the changes are in this branch: https://github.com/victronenergy/meta-victronenergy/tree/WIP_rpi4

Downloads:

• raspberrypi2 and 3: http://updates.victronenergy.com/feeds/tmp/venus-image-raspberrypi2-20200517094246-v2.60~22.rootfs.wic.gz
• raspberrypi4: http://updates.victronenergy.com/feeds/tmp/venus-image-raspberrypi4-20200517094427-v2.60~22.rootfs.wic.gz

Note that they are full images. Its not possible to install it as a .swu file. They need to be burned to an sdcard, which erases all contents on that sdcard. For detailed instructions, see the Venus OS on raspberrypi instructions.

Things to test

Report results in the comments and answers below. Always include the exact model of RaspberryPi you are using please, and just to make sure there are no confusions, report firmware version & build number of Venus OS that you are using too.

	rpi3	rpi4
Serial console (debug)	OK (rpi3B-v1.2 by Matthijs)	OK (rpi4B - Matthijs)
hdmi console	OK (rpi3B-v1.2 by Matthijs)	Not OK (rpi4B - Matthijs)
hdmi gui (remove /etc/venus/headless)	OK (rpi3B-v1.2 by Matthijs)	OK (rpi4B - Matthijs)
USB keyboard	OK (rpi3B-v1.2 by Matthijs)	OK (rpi4B - Matthijs)
GPS Dongles (pls report which one you use)	OK (rpi3B+ by PoloC)
Onboard WiFi	OK (rpi3B+ by PoloC)	OK (by Innar)
Onboard Bluetooth (note that I don't know on which rpis bluetooth is supposed to work)	Not OK (rpi3B-v1.2 by Matthijs)
VE.Direct USB		OK (by Innar)
MK3-USB to a Multi		OK (by Innar)
GX GSM
CAN (see here)
That inserting a USB stick makes VRM Logger recognise it		OK (rpi4B - Matthijs)
Pressing eject & then taking the stick out OK		Not OK (rpi4B - Matthijs)
Digital inputs
Analog inputs
Read through kernel bootlogs
.swu updating online (impossible to test for now)
.swu updating offline (sdcard or usbstick) (impossible to update for now)
booting into backup image (impossible to update for now)
Touchscreens and other add-ons that are being used
Logging to VRM (and thus DNS)		OK (by Innar)

Is it possible to update Venus OS on Raspberry PI?

If so, can this be done via the on-line update? Right now I'm getting an error when checking for updates.

Or does the Venus OS update need to be done via memory stick?

I'm fitting a Cerbo GX to an off grid camper build and looking to use the digital inputs to monitor the alarm system, open door, etc. But I can't find specs on what can trigger the inputs. Can I use 12v ish triggers from the vehicle or do I need to run relays to isolate and use a 0v negative trigger? Also what is the current, voltage limit on the relays?