All Posts in Modifications

Hi everyone,

Although new to all things RPi I've managed to get the VenusOS installed and various items working like the brightness and backlight off timer... but having trouble getting the dbus-adc and relays to work correctly?

Wondered if someone get give me afew pointers in laymens terms to help me along please?

• dbus-adc

installed dbus-adc file into /opt/victronenergy/ (Used putty pscp (couldn't get bitvise to work)
chmod 755 /opt/victronenergy/dbus-adc/start-adc.sh
chmod 755 /opt/victronenergy/dbus-adc/dbus-adc
chmod 755 /opt/victronenergy/dbus-adc/service/run
chmod 755 /opt/victronenergy/dbus-adc/log/run (Added folder called log and a file called run inside it - then found it in the service directory?
touch /var/log/dbus-adc (sets time stamp of the file or created one)
ln -s /opt/victronenergy/dbus-adc/service /service/dbus-adc

I can't seem to getting working at all, even though I'm sure I've followed everything correctly?

• Relays

I've got 4 relays showing but only Relay 1 and 2 are working through the gui?

Tested with - # dbus -y com.victronenergy.system /Relay/1/State GetValue

Switch off = 0

Switch on = 1

Think I've included all the details needed and I've added some Pics too...

Spent the last two days trying to figure it out...

Searched the net and on here but I must be missing something daft?

Thanks,

Pete.

101.jpg102.jpg103.jpg104.jpg130.jpg

This started as a post about an unexpected upgrade but that was answered, so this is now about my experience in upgrading my Rpi to Venus OS 2.60

I am running on an Rpi (should not make a difference).

I have my downloads set to:

Auto Update: Check only
Update Feed: Latest release (not latest releases candidate)

On Friday my system said there was a new version - I did a manual check and it said 2.60.

So guessing that 2.60 had been released I installed it, and ran all my scripts to reinstall the services and UI I have written. All looked good.

The new version running says it is 2.60 date and time 20200906 135923

But it would appear not to be a final release:

a) because there there does not appear to have been any announcement

b) It appears to not be complete - notably the custom tank level sensor settings are not working.

(selecting custom flashed the button on custom and then reverts on a second or two to whatever was previously set)

So the question is what did my system download and install, and why ?

Good evening, to most, and otherwise good day!

Its time for a new test version of v2.80. In case you don't know what this message is about, please start with reading this link.

The highlights of v2.80 are the new AC Load monitoring, the new DC metering function which now are visible in the Device List in the UI, and also new since this version are various improvements to the HTML5 MFD App, including the addition of translations.

And, let me share a bit of a sneak peak: the next test version adds support for the Ruuvi Tag wireless temperature sensors. Powered by a coin-cell battery, lasting 2 to 3 years, these sensors are extremely easy to install. I consider them a great addition to remotely monitor a (holiday) cottage, van or boat during the winter, for example. Requires a Cerbo GX, since it works with Bluetooth. Other GX devices having a USB-bluetooth dongle inserted might work as well, same as Rpis, but we haven't tested nor designed for that.

What to test?

Same as before: the new features I mentioned just now. As well as, just like announced previously, basically everything: there are several major changes in v2.80, which can each make things break in unexpected places. The first change is that the used Python version has been updated from 2.7 to 3. Also the Open Embedded release was upgraded from Zeus to Dunfell, and lastly we changed to a read-only rootfs. All combined this means that (a) lots of tools and packages used will have changed to a newer version, and (b) lots of Victron code has been changed to be compatible with Python 3.

How to post an issue?

Preferably all issues are organised as answers to this question. One answer per issue. So first check the existing threads. If you have the same as someone else already reported, welcome to add a comment saying "me too". And preferably some more details. And in case its not listed yet, add a new Answer. Note that Answers and Comments are two different things here on community.

Lastly, if possible please revert to v2.73, to double check if the issue you're seeing was present there as well. Regressions require a different treatment than other issues and bugs, and one of the first things that needs doing in triaging a report is distinguishing between the two.

The plan for v2.80

Development and testing will continue for quite a while; we won't make September anymore. So now, with a bit a luck, somewhere in October this year. The main new feature that needs further completion is DC metering for both loads and production (alternator or hydro or wind for example).

Changes below.

For now, all the best and have a good weekend,

Matthijs Vader

Changes since previous test version, which was v2.80~17:

HTML5 MFD App

• Add lock button that helps prevent accidental button presses like "Start generator" or "Multi Off".
• Add Dutch, Chinese, French, German and Italian to thelanguages.
• Add a placeholder & message in case no data is present.
• Add 3A button to the input limit selector.
• Hide 3rd phase in case of a split-phase system.
• Fix keyboard buttons not working in Remote Console.

Inverter RS

• remove support when connected on VE.Direct. As emailed publicly, from v2.80 onwards the Inverter RS, and in the future also the Multi RS, must be connected using the VE.Can port. Connecting them with the VE.Direct port to a GX device no longer works. MPPT RS still works on both, and will remain working on both.

DC Monitor (the new feature for the BMV-712 and SmartShunt already introduced in an earlier v2.80 test version)

• add entries into the Device-list

DVCC

• Force good settings for BMZ ESS Batteries: DVCC=ON, SVS=Off, STS=Off
• Force-enable SVS for the Lynx Smart BMS

ModbusTCP

• Solar chargers and Inverter RS: remove registers for per-tracker current, and add registers for per-tracker power.
• Add registers for DC Monitor types: alternator, dcsource, dcload, dcsystem and fuelcell

VRM Portal

• Fix problem with slower data updates on the portal and higher CPU use on the GX device. Issue was introduced earlier during v2.80 development. Thank you @gnagflow , @N-DEE , @matthiasroetzer and probably more help reporting that.
• Remove logging of Solar PV current. Instead, only PV Array Power and PV Array Voltage is logged.

Other:

• Bluetooth connection for VictronConnect: fix 000000 pin code, this was broken earlier in v2.80 development. Thank you Stefanie for point this out!
• Add Easter Island and Christmas Island timezone options
• Fix default values for AC input 1 and AC input two. Now they are Gird and Generator again, instead defaulting to "AC input not available". This was broken in Venus OS v2.60.
• Add names for various new model inverter/chargers.

Internal/developer:

• In various places we removed the solar charger PV array current (Amps) values. From D-Bus, MQTT, VRM Logger, Modbus-TCP, Node-red. And instead made sure that Power and Voltage is available for each array. This reduces unnecessary D-Bus traffic and as such optimises the maximum number of installable Solar Chargers. Note that this might break existing MQTT, ModbusTCP or similar integrations. Which is a pity ofcourse, though we do think its better like this going forward. Any UI or integration can ofcourse itself calculate the current by dividing the power by the voltage. Just like the GUI in Venus OS itself does now.

Complete v2.80 change log, compared to v2.73:

No time for that now, I'll make that later (again).

It seems that detailed Excel downloads in the VRM portal are now limited to a maximum of 6 months ago, where I think it was a longer period. Has anything changed here?

Hi, guys !
I've been running the Venus OS on my Raspberry Pi for a couple of months now and it is really running smooth and ok - had some problems with discovery of a device, but it was caused by an defect cable. So here's the question?

Anyone who have opinions on how healthy it is to unplug this OS without running a graceful shutdown or halt? I do not know exactly how Venus OS handles memory cache, temp files, etc. There is no menu option that says anything about shutdown, only reboot, so I normally either just unplug it or do a cumbersome thing of logging in to ssh from my mobile.
Maybe the development department could put a shutdown option as well as the already existing reboot?

managed to get screen working touch etc but cannot get slider or screen blanking has this been resolved yet on the raspberry pi4 4gig using a raspberry 3.5inch screen if so can someone leave a link.

Thanks

I have seen lots of questions about this, but no great answers for my set up. My batteries, cerbo gx mppt’s along with almost everything else is located in the Lazarette of my boat. The BMV display is in the wheelhouse via 50’ of cable. Is there a way I can connect the BMV 712 to the Cerbo GX without running more cable?

Could Victron make the smart shunt with the VE Direct port AND the RJ45 plug? That way I could connect the BMV712 and the cerbo gx to a smart shunt. I know its redundant, but I do not like dead gauges or holes in my panel.

It seems like a waste to abandon the 712 dispaly.

I'm using the Node Red feature in the Large version of venus os and buiding my own FUN Dashboard :) .I'm trying to access the 30-day history that one can see in Venus OS in the corresponding tab of Solarcharger that is connected to VenusGX and show it in some form on the Dashboard, but I can't seem to find the right building block. The Solarcharger block only contains the current value variables.

How to access and display History data with Node Red?

Hi

i have a raspi 4 with the large Venus OS image on it and a connected mppt100/30 .

output is a 7inch ips touch panel. This works very well.

Node red is activated and i use this to decode the serial output from a vortronic 400A Shunt so i have now following values in node-red at the moment:

- Voltage from the Board and Starter battery in V

- strength of the electrical current in A

-Battery level of the board battery in %

-size of the Boardbattery in AH

now i would like to send this as input to emulate a bmv7xx to the venus os to show it on the display as a bmv.

has someone a idea , best of would be directly in node-red itself

thanks in advance

hello,

is it possible to use a Phoenix Charger Control Panel with a MultiPlus (48/1600/20), and set with this panel the loading current of a battery-pack?

thanks, dirk

Hello this Saturday!

The short detour to v2.73 is over. A new v2.80 version is available for field testing, v2.80~16. For the release blog post of v2.73, see here.

In case you don't know what all this is about: this message is part of the Venus OS Beta test program. Read that link for more information.

By now, v2.80 is has some quite noticeable new features. For example the completely new AC Load monitoring, the improvement in the Total of all phases mode for ESS, the new DC metering function and still more.

What to test?

The new features I mentioned just now. As well as, just like announced previously, basically everything: there are several major changes in v2.80, which can each make things break in unexpected places. The first change is that the used Python version has been updated from 2.7 to 3. Also the Open Embedded release was upgraded from Zeus to Dunfell, and lastly we changed to a read-only rootfs. All combined this means that (a) lots of tools and packages used will have changed to a newer version, and (b) lots of Victron code has been changed to be compatible with Python 3.

How to post an issue?

Preferably all issues are organised as answers to this question. One answer per issue. So first check the existing threads. If you have the same as someone else already reported, welcome to add a comment saying "me too". And preferably some more details. And in case its not listed yet, add a new Answer. Note that Answers and Comments are two different things here on community.

Lastly, if possible please revert to v2.72, to double check if the issue you're seeing was present there as well. Regressions require a different treatment than other issues and bugs, and one of the first things that needs doing in triaging a report is distinguishing between the two.

The plan with v2.80

Development and testing will continue for quite a while; I expect at least until late September; possible also into October this year.

Changes since previous test version, which was v2.80~14:

• Add AC Load monitoring. All energy meter types can now be configured to a new "role": AC Load monitor. This is done in the menu where you also choose between Grid, PV Inverter and Generator. With AC Load monitor selected, the load will be shown in the Device list. Note that we still need to work on VRM for this (add it to the Advanced page, and perhaps elsewhere as well), and also note that measured loads are not used in any calculations.
• Wifi menu: ask for confirmation before forgetting/disconnecting from a network, as well as before disabling the Access Point; to prevent accidental locking oneselves out, especially when remote.
• Fix the MFD HTML5 App, a regression introduced earlier in v2.80 broke it.
• Slightly renamed a few VE.Bus errors and error 8 & 11 detailed status codes to be less ambiguous.
• Managed batteries & DVCC
  • add support for charge request message by the battery: if the battery signals that it needs charging, then the Victron system will do so when possible: AC must available on the input. Affects only ESS, and then more specifically one of the Optimised modes, not the Keep batteries charged mode. The GX device will not auto-start a generator for this.
  • detect BMZ-ESS batteries. Next step is to force-enable DVCC for them.
  • add custom name support: user and installer can configure a name for the battery. This name is stored on the GX device.
  • Remove managing Phoenix Inverters VE.Direct with DVCC. This was added earlier during v2.80 development, but doesn't work well; and will not be added back anytime soon. The Inverter RS is still supported.
• Developers: dbus-mqtt: fix regression introduced earlier in v2.80, that broke it: the (now legacy) method of doing a keepalive when sending messages with a payload. Thank you scuba-shan for reporting that.

Picture: the new AC Load option:

[image]

Complete v2.80 change log, compared to v2.73:

User interface (CCGX, GX Touch, Remote console):

• Add eject button to the offline firmware update menu.
• Fix issue that caused the overview to change when switching off the Multi in a system configured for ESS
• Fix an issue where the grid meter reading disappeared from the gui when the Multi is off
• Slightly renamed a few VE.Bus errors and error 8 & 11 detailed status codes to be less ambiguous.

DVCC & managed batteries:

• Force DVCC settings for Pylontech batteries as per documentation (DVCC on, SVS and STS both off). This is now the same as already in place for various other battery makes.
• Add full support for the Inverter RS, including CVL, CCL, SVS, STS and SCS.
• Switch off inverters when a managed battery says DCL=0, same as how that works for inverter/chargers already.
• Only use the selected battery monitor; affects systems that have a managed battery and a BMV (or similar) Victron battery monitor installed.
• Add support for charge request message by the battery: if the battery signals that it needs charging, then the Victron system will do so when possible: AC must available on the input. Affects only ESS, and then more specifically one of the Optimised modes, not the Keep batteries charged mode. The GX device will not auto-start a generator for this. The only batteries supporting this are certain models of BYD batteries. I don't know which ones right now, I'll add more info when I have it.
• Detect BMZ-ESS batteries. Next step is to force-enable DVCC for them, which will be done in next v2.80 version.
• Add custom name support: user and installer can configure a name for the battery. This name is stored on the GX device.
• Remove managing Phoenix Inverters VE.Direct with DVCC. This was added earlier during v2.80 development, but doesn't work well; and will not be added back anytime soon. The Inverter RS is still supported.

ESS:

• Change the "Total of all phases" mode to be symmetrical: all phases are adjusted to convert the same amount of power from, as well as to, DC. In the past, this option primarily avoided passing power through the DC-bus to avoid inefficiency, but didn't take full advantage of the billing arrangement to use all the available power when there is a shortfall on another phase. Now it divides the work equally across the phases, thereby making the full capacity available, and with no impact on billing.
  
  An example: at night, no solar, there is a large load on L1 - say 6kW. And no load on the other phases, and a 3 x 3kVA inverter/charger configuration. Old: the L1 inverter/charger would be at max power, discharging, which resulted in buying ~3.5kW. New: all three inverter/chargers are each doing 2kW, zero Watts on the meter.
  
  Similarly in a excess PV situation: if there would be 6kW excess PV on L1, and the same inverter/charger configuration, then in the old situation it would charge the battery with one inverter/charger only, and the rest of the power would be sold back to the grid. In the new situation, it all inverter/chargers will be charging at approximately equal power, and the total being 6kW of charger.
  
  Lastly, note that the balance of feeding in excess PV power coming from solar chargers, has not been changed. There is no need to actively make that symmetrical, since when there is so much energy available that its necessary each inverter/charger will automatically start operating at full power. No need to actively manage that.

VRM Portal:

• VRM: transmit status of L2 in a North American split-phase system, to enable proper visualisation. This relates to the recently introduced MultiPlus-II 12V 3000VA 2x120V. Note that the VRM Dashboard itself still needs to work to use this information. Its the last one: all other user interfaces (VictronConnect, GX Touch / Remote Console) already show information on L2.

Other:

• Support the new DC Monitor feature, recently released as a firmware update for the BMV-712s (v4.07) and SmartShunts (v4.07). The purpose is to be able to use those dc meters not as a battery monitor but as a dc meter. For example to measure the output of an alternator, or a wind generator. Or, measure the power draw of a certain load or group of loads. First of all to visualise it, and later it can perhaps be used in DVCC as well. Note that this release is just the first step, more coming later such as proper visualisation in the overview and VRM.
• Add AC Load monitoring. All energy meter types can now be configured to a new "role": AC Load monitor. This is done in the menu where you also choose between Grid, PV Inverter and Generator. With AC Load monitor selected, the load will be shown in the Device list. Note that we still need to work on VRM for this (add it to the Advanced page, and perhaps elsewhere as well), and also note that measured loads are not used in any calculations.
• Wifi menu: ask for confirmation before forgetting/disconnecting from a network, as well as before disabling the Access Point; to prevent accidental locking oneselves out, especially when remote.
• Support exfat filesystem, for large removable media (sdcards, usb sticks). Note that this is not for the raspberrypis, since (only they) still ship with a version of Linux that does not support exfat.

Bluetooth

• Fix Bluetooth pincodes starting with a 0; this was broken since the first release of BLE functionality in Venus OS.
• Implement keep-alive functionality: improves robustness with certain phones by avoiding Venus OS thinking its still connected and then remaining connected while its not.
• Fix GX device not being visible on other phones while already connected to one. Now it is visible in the 2nd phone, but then with an explanation that to connect, the other phone needs to actually disconnect first. This is now on par with how other Victron products work with Bluetooth.

Developer / under the hood

• Change the rootfs to be default read-only. Careful, this is quite the change in case you're modifying your rootfs. The reason behind this is quality and robustness. Every boot is now the same, instead of an initial boot possibly being different from the second or the third. And less writes to the storage, which reduces the wear, and more advantages. The downside is obviously that its a bit more hassle in case you want to modify the software. To learn how, read here this commit.
  • /opt/victronenergy/swupdate-scripts/remount-rw.sh will make it writable again (until the next swu update)
  • additional services should now be stored in /opt/victronenergy/service instead of /service or else they won't survive a reboot
  • closes https://github.com/victronenergy/venus/issues/217
• Change the used Open Embedded release from Zeus to Dunfell. More details about OE releases are here. For a long time, Venus OS was based on Rocko. Recently we changed it to Zeus, which was an intermediary step to get to Dunfell. Dunfell is relatively recent LTS (long term support) version; so happy to be at that version, and expecting to be able to leave it at this for quite some time to come.
• Change the used Python version from v2.7 to v3.. This was something we needed to do anyway, and sort of a requirement that comes with switching over to Dunfell. For those that wrote their own code this does mean work. See also this post on community.

Known issues

• Installations with an Inverter RS connected via VE.Can might have an issue: continuous crashes of the systemcalc service. To be fixed in next v2.80 test version.

Hi there,

I have a followed the instructions here and I'm not getting an boot loading data on the screen after copying the tft35a-overlay.dtb file and editing the config file as stated.

The screen initially lights white then goes dark but never with any text. I've tested the LCD by installing the pre-built image on this page and it's working fine. I also notice that the link provided above for the method differs from the WiKi here so not quite sure which one is the right one.

Any pointers would be appreciated.

FYI, version is 2.72 on Pi3 connected to VRM. I also have SSH access if that helps with debugging.

Hello all

I have been playing with Docker/Grafana on Windows and have perfect dashboard for my use. However I dont want to run another windows machine in the motorhome

I purchased a Raspberry Pi 4 and installed as per the instructions on this site but Grafana wont load on port 3000 even though the docker site on port 8088 works perfectly

Has anyone else had this issue?

Thanks for your help

Hi.

I need help to make open source Grafana work on my Mac mini. https://github.com/victronenergy/venus-docker-grafana

The problem is that I struggle to install this correctly. Unfortunately I am not so good at command lines, so hope somebody could give me some tips to get this up and going?

I have cerbo-gx and this is connected with ve.can to nmea2000 cable and mqtt is activated so it should be correct. I have mac os catalina and installed Grafana and docker as described in the venus-docker-grafana project and so far I think this is ok.

-Step 2 with download of docker compose file I only get one page of text and here is my problem with command lines..

-The same goes for step 3, no idea how to place the file..

-Step 4 I do not get access to (http: // localhost: 8088 /) but docker is installed and works fine when I open the app.

-Step 5 and access to Grafane works fine.

Am I far off target or are there minor details missing? Very grateful if somebody can help solve this.

Good afternoon (or morning, night, evening... ) all,

A new version out for testing, v2.80~17.

In case you don't know what all this is about: this message is part of the Venus OS Beta test program. Read that link for more information.

Already, v2.80 is has some quite noticeable new features. For example the completely new AC Load monitoring, the improvement in the Total of all phases mode for ESS, the new DC metering function and still more. This new version mainly adds a few more minor improvements.

What to test?

The new features I mentioned just now. As well as, just like announced previously, basically everything: there are several major changes in v2.80, which can each make things break in unexpected places. The first change is that the used Python version has been updated from 2.7 to 3. Also the Open Embedded release was upgraded from Zeus to Dunfell, and lastly we changed to a read-only rootfs. All combined this means that (a) lots of tools and packages used will have changed to a newer version, and (b) lots of Victron code has been changed to be compatible with Python 3.

How to post an issue?

Preferably all issues are organised as answers to this question. One answer per issue. So first check the existing threads. If you have the same as someone else already reported, welcome to add a comment saying "me too". And preferably some more details. And in case its not listed yet, add a new Answer. Note that Answers and Comments are two different things here on community.

Lastly, if possible please revert to v2.73, to double check if the issue you're seeing was present there as well. Regressions require a different treatment than other issues and bugs, and one of the first things that needs doing in triaging a report is distinguishing between the two.

The plan with v2.80

Development and testing will continue for quite a while; I expect at least until late September; possible also into October this year. The main new feature that needs further completion is DC metering for both loads and production (alternator or hydro or wind for example).

Best regards,

Matthijs Vader

Changes since previous test version, which was v2.80~16:

• Added time zone for Christmas Island.
• Improve WiFi recovery from Failure status: still, after several improvements done in the past about this already, there were some situations where the WiFi status in the menu showed Failure - and basically the GX device had given up on re-connecting. This change prevents that. Do note that, especially for unattended systems, we always recommend to use the VRM auto-reboot feature.
• Improve ET340 in combination with Zigbee link, when installed in a lossy/noisy environment.
• Modbus-TCP: Fix definition of register 2710 (DVCC override charge voltage). Since the mistake rendered it largely useless, and this is a fairly new register, no new register is allocated.
• Fix Inverter RS compatibility issue when used with DVCC (causing continuous appearing and disappearing data on the overview page)
• Show "Recharge" in the overview if the system is charging because a CAN-BUS BMS battery requested the system to do so. Note that this requested charge is new, see previous post.
• Force DVCC on, SVS off and STS off for BMZ batteries

Complete v2.80 change log, compared to v2.73:

I'll compile this later.

Hi All

Just installed a raspberry Pi 3B+ with Venus GX Firmware as a gataway for my solar system on my boat.

It works pretty fine!

I used the official Pi3 Case for it.

I didn't install any heatsink or fan.

As it can get pretty warm in my boat, just wondering how the device can handle the temperature?

What happen if it would overheat? It will power down automaticly?

Is it nessesary to install a heatsink or fan or I'am good to go how it is right now?

Does anyone has some exprerience on that topic?

Many thanks

Hi Folks.

I have set up my raspberry pi 2B with Venus 2.66 and got it to display the gui on the 2.2" non touch screen hat built into my pi case, the one with six buttons and IR receiver.

In case anyone else is using this screen there is an overlay available for the 2.2" screen hat here-

https://github.com/raspberrypi/firmware/tree/master/boot/overlays. it is called pitft22.dtbo. ;-)

As it is not a touch screen I would like to use the six physical buttons on the hat to control my venus in a similar way to the CCGX. these are wired to GPIO pins on the pi hat. can anyone tell me how the CCGX buttons are wired to it's processor?

I have tried adding the gpio-key.dtbo to the venus overlays folder and editing the config file to run the overlay using "dtoverlay=gpio-key, gpio=24,active_low=1,gpio_pull=up, label=Down, keycode=108"

This should give me a down button on GPIO pin 24 but the button is not responding.

Any help appreciated.

Cheers.

Bob.

I cannot for the life of me get DC Feed-in working.

Gear:

Multiplus II 5000

2x 150/35

Batrium BMS to 45kwh Lion battery

A stack of AC solar on the AC Input side

EM24 grid meter

EM24 - to measure AC solar production.

Scenario:

Battery full 4.1v per cell or 57.4v

BMS sending CCL of 0

DC Feed-In enabled

Settings:

MPII and MPPT float / absorption set to 57.4, However it doesn’t seem to make any difference as I’ve set these higher without effect.

What Happens:

With DC Feed-in enabled the MPPTs correctly go flat out. However rather than the power being inverted by the MP II and going into the grid, it goes into the battery despite it being full.

If I disable DC Feed-in the MPPTs correctly ramp down (because the battery is full)

I cannot get a safe system with DC Feed-in enabled -

It will cook the battery.

From what I can gather, my BMS is sending the correct target voltage 54.7 and correct CCL of either 0 or 0.5 ( the balance current)

I see many other posts with DC Feed-in issues but none with any resolution to this specific issue.

Note: I don’t have any limits on feed-in set.

any help would be appreciated.

Hi everyone,

I implemented the VE.Bus/MK2 protocol following "Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf" and using a MK2 USB device. All commands and functions work as described.

However switching over to an MK3 USB device, the three Quattros i'm testing with do not react to command 'S' as expected. Using the same commands, the MK2 does the job.

The whitepaper mentions certain jumper settings in the MK2 (which i never touched, the S command worked with a standard MK2 device) however when I opened the MK3 device there were no jumpers inside to play around with.

I have not seen any mention in the whitepaper regarding this. Is there a specific command to issue or a flag I need to set in the MK3 for this command to work properly?

Thank you forward for any responses!

Hi!
I would like to disable the AES of my Multiplus 12/3000/50 via NodeRed in case a certain condition is true.
But so far I am not able to find the setting for AES in the Victron devices in NodeRed on my VictronOS installation (Raspi4).
Maybe someone knows something?

On our new Leopard catamaran we have 2 start batteries and a house bank (all agm’s). When on shore power the house bank charges via the multiplus, but not the start batteries, which only apparently charge via the engine alternators. How do I connect the start batteries to the multiplus to facilitate their charging while on shore power?

Hi

I have created a VenusOS driver that can talk to BMS/Batteries that has serial communications (instead of the normal CANbus). RS485 & RS232 and Venus 2.60+ (including v2.80) have been tested.

Currently it works with

• LLT Power / JBD Battery / Overkill Solar BMS
• Daly Smart BMS / Daly Sinowealth based BMS
• ANT BMS
• MNB spi BMS - disabled by default as it requires extra libraries installed to work. Contact @Mike Dorsett for information
• JKBMS / Heltec

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

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

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

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

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

We are using VRM portal to access and monitor our systems (Venus GX/Victron Multiplus) , but would like to use ssh remotely to login as root to the console to install/update python scripts running on the Venus. SSH is enabled in the Venus GX interface, but how to remotely access the Venus by ssh ?

Both the SmartShunt and Multiplus have temperature sensor inputs yet these sensors do not appear in the GX device list as temperature sensors.

Does anyone know of a way to make this happen so I can display those values in my temps mod to the Mobile Overview and Flow Overview pages provided by my GuiMods? For temperatures, I look for dbus services with a temperature service type.

Hello all,

half an hour ago we made v2.60~34 available for testing. Short version of this news this time, see previous v2.60 beta post for background.

Changes:

• Marine MFD html5 app: instead of hiding metrics that don’t fit on the page, now use pagination.
• GX GSM: increase the max length of the APN.
• GUI: Fix the backlight slider on touch screens

have a good weekend, Matthijs

Hi,

I am building a solar powered HAM relay, depending on the SOC of the battery, individual components should be switched off. In the Venus GX I can switch one relay with the generator control, but not the second one. Has anyone ever reprogrammed it so that the second relay can be switched to SOC. I want to switch everything off with the relay of the BMV in an emergency

Hi,

i looken into the victron API v2 and followed the documentation to create a personal access token. This worked very well. I received the following details. (i blanked out some info here)

PersonalAccessToken:success:true,token:aXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, idAccessToken:1XXXXX

So i would expect this step was successful, but when i would like to use this token i got an error: success": false, "errors": "Access denied for this object", "error_code": null

The first thing which looks strange to me, this token length is much more shorter than the token after the login was created by username/password.

I also changed the "X-Authorization" header from Bearer to Token and try to use the following get request without success.

https://vrmapi.victronenergy.com/v2/users/{ID}/installations

accesstokens/list

The ID i was using for connection was the id of the AccessToken.

Is this correct?

Do i have to do a login before using this accessToken?

Currently i am completly lost how to use this accessToken. Login with username/password is not a valid solution because i am using a sms_token and do not want to use my mobile before using the connection.

Thank you very much for your help.