Not really sure where to put this:

I'm looking through the spreadsheet (experimenting with adding the generator node to Node-Red) and whilst editing on the files my IDE threw an error over a duplicate object key:

Looks like the dbus-obj-path for the com.victronenergy.generator "Manual Start" address has the wrong value, it has "/Generator0/Runtime" whereas I think it should be "Generator0/ManualStart"

Hi All

I’ve just updated my pi3 with this release and all was going well until I tried to add relay 3 and 4. I got the second relay active and working but as soon as I added the 3rd and 4th relays into the gpio list the relay setting page disappears from the main settings page? If I put // infront of the lines the relay setting page comes back. so at the moment the file Looks like-

21 out relay_1
17 out relay_2
//27 out relay_3
//22 out relay_4

with it like this the relay setting page with the two switches is visible and usable.

In my old version 2.30 they all worked?

Any ideas or help would be greatly appreciated

Thanks

Mark

Hello,

I have a Raspberry Pi connected to a SmartSolar MPPT 100/20 and I am monitoring the serial output.

Is there any low voltage disconnect alarm in the serial output? What is the timeout after the alarm is issued if it exists?

If there is no alarm or the alarm timeout is too short to safely shutdown I will have to trigger a shutdown just before the LVD voltage is reached

In the BatteryLife program is the LVD minimum voltage sent in the serial output or can this be retrieved from the charge controller using the serial interface?

Thank you

Would it be possible to integrate NTP or NTP-SEC into CCGX firmware, as this would make an excellent addition thus enabling accurate timing of computers and radio equipment on board

Hi,

I successfully enabled 3 additional relays on RPI running latest stable Venus OS but only first two are visible on GUI.

The other 2 are fully functional using CLI dbus Set/Get.

Is it possible to make them all visible on GUI and how?

Thanks,

Mihai

[image]

[image]

Changes (v2.40~38 up to and including ~45)

General:

• Add "Inverter only" option to the On/Off/Charger-only switch in the Multi/Quattro menus
• Add support to give a custom name to our SmartSolar VE.Can chargers. Note that some other devices connected via VE.Can can also be given a customer name, such as a Skylla-i. But others unfortunately don't support that feature, such as our VE.Can Tank Sender Adapter.
• The "Multiple managed batteries" warning was removed, thanks Wilco.
• Send custom names to the VRM Portal. Soon we'll improve the VRM Portal to use those names, making it possible to customers to set their system up such that all those graphs on the Advanced page are named; rather than the "Solar charger (288)" naming.
• Fix issues related to DVCC and solar chargers; these issues were introduced together with the new features introduced earlier in v2.40 (charge current sense and more).
• Hide the bluetooth on/off switch on devices that don't have bluetooth. (the Cerbo GX has bluetooth).
• Fix bug where, in certain conditions, the Multi/Quattro could not be switched on.
• Fix bug that prevented disabling the Sunday in the ESS Scheduled Charging settings. Bug was introduced in v2.40~19, thank you John H for reporting!.
• Update VE.Bus Error 8 and Error 11 titles to be in line with the updated documentation.
• Add support for the Discovery AES battery, including forcing the DVCC & SVS options to their required setting (DVCC on, SVS off).
• Rename "Battery measurements" menu to "Marine MFD App Configuration" menu. Thank you Matej!
• Force the BMS-Can port on the EasySolar-II GX and MultiPlus-II GX to be able to be used only for that purpose, no longer as a VE.Can port. The reason why we changed that is that we can't guarantee proper functioning of that port for connecting VE.Can products, even worse: we know for sure it won't work reliable. The hardware is not good enough. Product documentation of those products has been updated already a while ago.

Developers:

• Change address of mqtt server. More info here. Note that, for now, there is still only one and the same mqtt server behind all those addresses. A few weeks from now we'll deploy the new cluster. After which still the old server remains in tact: any customer that has issues because of this change, and needs more time to adapt his own setup and software, can solve the problem by reverting back to v2.33.
• Cerbo GX preparations.
• VictronConnect remote settings preparations.
• Add ntp and gpsd as optional opkg installable packages

Hello again all,

After releasing v2.40~34 on October 10th, now we've released v2.40~37 for testing.

If you don't know what this post is about: this is about our GX Product range, and this post is aimed at all the members of the Beta test group. See this information on how to join (and leave) that group is here.

Enjoy the testing. If you see any issues, please post below. Thank you.

Matthijs

Changes from v2.40~34 to v2.40~37

Bug fixes

• Fix race condition that made Remote Firmware updates and/or Remote VEConfigure not always work. Bug was introduced earlier in the v2.40 development. Thank you @Elimac for reporting.
• Fix bug that caused far too much logging for systems with a IMT Solar Irradiation sensor. Thanks @Mark for reporting. Introduced in v2.40 development.
• DVCC / Share Current Sense:
  • fix bug that caused the current to be sent a factor 100 too small to the solar chargers. Introduced in v2.40 development.
  • also send the current to the VE.Can Smart Chargers. (ie. the new models introduced in last months).
• Fix bug in VE.Can driver that made it necessary to do an extra reboot after an update. Bug was introduced during v2.40 development. Thanks at various people for reporting.
• Fix jittering alarm on Z-Cell Redflow batteries. Thanks to Simon for reporting. Introduced in v2.40~25, fixed in v2.40~37.

New features

• Add notification when solar charger firmware or inverter/charger firmware is too old for use with DVCC.
• Add notification when multiple managed battery systems are connected while using DVCC. It can handle only one; not multiple at a time.
• Octo GX and Venus GX: the push button do things (reset network settings as well as enable/disable the wifi access point, I'll elaborate later). And the LED now shows the WiFi Access Point state.
• Add transmitting inverter/charger data to the new NMEA2000-out function
• Identify BYD B-Box L battery separately; to distinguish it in the VRM Device List page from the Pro batteries.

Under the hood changes:

• Update Sunxi Linux kernel to latest 4.19 release
• Prepare for new GX Device
• Add system response time monitoring
• Add extended canbus-bms protocol (not used yet)

end.

For earlier changes in v2.40; see previous post.

Hi,

I have just installed a BYD battery pack onto my off grid system, replacing my ageing Lead Acid batteries. I have run into an issue with monitoring using the MQTT capability of the Venus GX.

Once the BYD battery is connected, the Venus creates a number of new MQTT topics - these include quite a few indicating fault conditions and one called "Connected" (in my case its full topic path is N/9884e3aed7f6/battery/512/Connected).

This topic delivers a payload of {"value": 1} - which is a valid JSON formatted string - great.

However, if the RS485 cable between the venus and the BYD BMS is interrupted, you would expect this value to report {"value": 0} - sadly it does not. The payload becomes NULL (ie nothing) and this is NOT valid JSON. This causes the JSON decoder (at the subscriber end) to throw en exception and causing my alerts to fail.

If values are going to be sent using JSON encoding, ALL values should be JSON encoded.

I have no way of simulating the other fault topics so I can not say if they do the same.

Struggeling to set this up I have:

Ubuntu VM with a bridged adaptor on the same network as the CCGX.

I can ping the CCGX

Installed Node Red (https://nodered.org/docs/getting-started/raspberrypi ) got it running as a service and can view the flow editor.

Installed node-red-contrib-victron by doing steps 1,2 & 3 (https://github.com/victronenergy/node-red-contrib-victron#installation-and-usage)
Now I can see the Victron Energy tab

[image]

A CCGX with Modbus/TCP and MQTT turned.

Root password set and SSH'd into.

Carried out Step 4. (https://github.com/victronenergy/node-red-contrib-victron#installation-and-usage) - rebooted

Back on the Ubuntu VM

export NODE_RED_DBUS_ADDRESS=192.168.1.4:78 (the IP of the CCGX)

restarted node-red

But can't seem to see anything in the node-red editor.

[image]

What am i doing wrong? Do I need to generate the node specification file? (https://github.com/victronenergy/node-red-contrib-victron#generating-the-node-specification-file-developers)

Where do i get 2 .csv files from, I've tried just running (after installing csv-parse and gar via npm)

node parse-services.js --append

but it throws an error:

Please make sure that the files ./csv/dataAttributeEnums.csv and ./csv/dataAttributes.csv exist.

As it seems to be getting lost in the noise. Where can I get dataAttributes.csv &dataAttributeEnums.csv from?
(https://github.com/victronenergy/node-red-contrib-victron#Installation-and-Usage )

Hello all!

This morning we have released beta version v2.40~46 for testing. There is only a handful of changes, see change log below.

Whats next? there are no more open issues to solve, nor features to be completed. Now all that remains for the final release is more testing, double checking that all reported issues were looked into, and waiting a little.

Best regards, Matthijs.

ps. If you don't know what this post is about: this is about our GX Product range, and this post is aimed at all the members of the Beta test group. See this information on how to join (and leave) that group is here.

Changes in v2.40~46

• Added the "ESS Relay test" item to the Multi/Quattro advanced page. It contains either Pending or Completed; and while pending the system refuses to feed in (convert from DC to AC while connected to the grid). For more information see Q9 in the ESS FAQ.
• All translations have been updated.
• Added GPS Altitude to the ModbusTCP registers (register 2808 as an int32) & added GPS Altitude to the data that is sent to the VRM Portal database.

For earlier changes, see changelog for v2.40~38 upto ~45, and changlog for v2.40~35 up to ~37, and changelog for v2.40~1 to v2.30~34.

Hello

i use the Diplay Remote Console with raspberryPI, it is mount it on my Recreation Vehicule , it is only running with DC power

Is there a way to customize the Remote Console?

tks

[image]

I have a Raspberry Pi working well with Venus OS. I would like to control it from another RP. I have good WiFi or Ethernet to both. Is VNC the way to do this? If so how to I get VNC on the Venus OS RP?

Hi has anyone got a clue how to connect the batrium bms to the ccgx, I have cabled it up, put in the correct resistors, gone through all the settings multiple times and can not see the bms on the device list. I have spoken with batrium (and apart from putting a new cable in, which I will do today) they were not a lot of help.

I would appreciate any help you can offer as I am about at the end of my patience :)

Hello

i am trying to do a SSH to the raspberrypi.. i am able to connect with my IP adress on the web, i see the remote screen.

i would like to connect with Putty.... the login as is what? what should i enter there? i try many name but cannot connect

Any help would be apreciate

A

So I finally installed my pi and touch screen in my camper van. Everything is working fine on the victron product side but when I went to disconnect my tank sender from the manual gauge to install on the Expander PI ADC board and it still said shorted. I couldn't figure out what was wrong, then I take out the voltmeter and found that the tank sender is a 0 empty to 90 ohms full.... *facepalm*. I bought my camper van from someone else and the sender was already installed and I just assumed it was a standard NA 240-33ohm sender. Instead of getting a new tank sender, is it possible to change the settings somehow on the Pi to read this tank sender?

At least the panel turned out well (looks like I can't upload any photos).

My system:

ESS configuration with grid meter.

ALL latest firmware.

RPi 3B+ Venus v2.33

SmartSolar MPPT 150/35

Multiplus 2 48/4000/35

DIY Lion Battery.

RPi -> Victron RS485 USB dongle -> ET112

All other connections as standard (mppt (VE.direct USB dongle), multiplus (MK3 USB dongle)).

So, all working fine for weeks. However, remote console this morning showed all devices detected apart from grid meter?

What are my options?

How do I check the RS485 dongle is working correctly, are there errors signalled by the flashing leds. No green leds are flashing just the red one every few seconds.

When I unplug and plug the dongle the green led flashes once and then the red led flashes 8 times then pauses then flashes 15 or so time? Any clues.

The ET112, seems to be fine but how do I test the data is being sent?

Have rebooted RPi, no joy.

Any ideas would be most welcome.

Instead of using an engine-driven alternator, I'd like to make use of the engine compartment's air in-flow to drive a wind turbine. I would think this might be more economical using a high quality Chinese made wind turbine generator; no air intake when vehicle is idling avoids alternator overheating issues. Has anyone done this or know how best to design such a solution to augment the solar charging of my 24v Tesla battery bank.

Hello

The VictronConnect is nice to have a look of the moment but for example

history over hours I cannot see...

My question now: Is the communication protocol public available?

I want to design an application for Arduino o rasp pi to collect data for statistics...

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!

Hi everybody,

I am currently setting up my RV with some Victron equipment (BMV, smart MPPT, etc) as a central element I use a pi with Venus OS.

My question is, is it possible to have Grafana/InfluxDB on the same device? I do not what to run a second pi just for that as energy consumption is always critical.

I am not a Linux guru and struggling installing the docker-composer on my Venus OS pi.

Thank you for any help and/or tips.

Cheers

Dirk

Hello everyone,

It seems almost any information a person would need from the Venus OS device is published to it's own local MQTT server. I have accessed that MQTT server from a client and was able to get voltages and other information out of it. The Raspberry Pi is connected to a Victron 100/15 SmartSolar via a USB to TTL adapter and I can access the information and settings for it from Venus so that is not a problem. I understand the Venus MQTT requires a keep alive message to be sent about once every 60 seconds. I also already run an MQTT server and Home Assistant on another Raspberry Pi that I use for everything else.

How can I get the data I want (or all of it) into Home Assistant? Preferably, I just need to get Venus to send the messages to my normal MQTT server instead of it's own, or maybe a script that subscribes to the Venus MQTT, publishes a keep alive once every 60 seconds, and then forwards all received messages to the normal MQTT?

Thanks for implementing battery current update in latest MPPT firmware version. It nicely complements allowing adaptive absorption time to be turned off (useful for my Lithium with very variable charge rates).

What response should I receive from MPPT firmware version 1.44 when updating the Battery Charge Current with Hex Protocol. Register is 0x200A

0x200A Battery charge current (*8) 0.001 sn32 A

I think I'm receiving "1" which looks promising but I'm more used to seeing the new setting echoed back to me when changing values.

Sent:- :80A200030F8FFFFFD which represents 2 amps.

Returned:- :80A200122

Does this response indicate update successful?

and how?

Thanks,

Mihai

Hi,

We would like to run some experiments with the MQTT service on Victron systems. Is there some sort of sandbox available that we can use? Thanks.

Cheers,

Imre

Hi,

the latest MPPT Hex Protocol documentation refers to Register 200C Device State but does not provide the accepted register values to represent Bulk, Absorption, Float.

What are they?

Thanks