All Posts in Modifications

Hi,

I have a Raspi 3b+ running Raspbian Jessy with a TFT display.

This is the 3,5inch display https://joy-it.net/en/products/RB-TFT3.5

Do I have a chance to run Venus OS on this Raspi with this display?

Hello. I have problem with this. (three phase) Configuration is 3x Multiplus II 3000W 48V, GX modul, 1x MPPT regultor 150V/85 and 1x MPPT regulator 150/70, 1x VictronSMARTHUNT 500A with 16x lifepo4 battery 300Ah. BMS is JIKONG B2A24S150 and current senzor. With ESS configure. When battery is fully charged and connect with GRID system fall down and multiplus II is restart When enegry is in FV panels. I disabled feed-in is disabled. Grid metering is "Inverter/Chrarger" If I use off-grid everything is corect don´t resatart. Have you ever solved this problem.

I want to implement my own Battery Management System which should be connected over the CANBUS CAN-BMS protocol to the cerbo gx.

I found out so far that the BMS to need transmit the following CAN IDs to the cerbo gx.
0x351, 0x355, 0x356, 0x35A, 0x35B, 0x35E, 0x370

[image]

Regards,

Pascal

Hi all,

I would like to use Node Red to program my Multiplus II-GX so that the max inverter power can be controlled by

(i) time of day (so that the dishwasher does not deplete the battery and the fan does not run at night) and

(ii) battery voltage (so big loads do not take it below the 47.0 volt cut-off limit).

Has anyone done this before? If not, where do I start (I have no prior knowledge of setting up Node Red flows)? Is there a Victron sandbox where I can try out ideas without risk of crashing a live system?

TIA

Good evening!

Next version of v2.90 to test.

Various small changes further adding to the significant ones announced yesterday in v2.90~3.

Plan for v2.90: there will be a few more betas, and testing time ofcourse, before this is released. But no other large changes; to try and keep the timeline to official release reasonable.

All the best and have a good evening, Matthijs

Change log (compared to v2.85)

v2.90~5:

• HTML5 app: fix white screen issue on MFDs that do not support localStorage, eg. Simrad NSX 3007, 3009 & 3012. Thank you Gustav for reporting.
• Venus OS Large: fix node-RED dashboard button missing from VRM portal. Thank you houser and others for reporting.
• VRM: fixes for the Generator control, ESS controls and EV Charging station controls
• EV Charging Station: stability fixes
• Inverter/charger connections:
  • add new MultiPlus-II 48/15000/200-100.
  • Fix VE.Bus BMS error path issue
• RV-C: Fix DC_SOURCE_STATUS_2 temperature field.

v2.90~3:

• Prepare for remote configuration of Victron products connected using the VE.Can comms. port: up until now, Remote Configuration is only possible for products connected using VE.Direct, as well as our VE.Bus product range. And this change is the one making up for that missing piece. The corresponding VictronConnect version is also available as a beta, see here.
• Add support for new Carlo Gavazzi EM530 and EM540 meter. Sub-Family X and PFC is supported, part numbers:
  • EM530DINAV53XS1X
  • EM530DINAV53XS1PFC
  • EM540DINAV23XS1X
  • EM540DINAV23XS1PFC
• Add option to configure the UI to show all temperatures in Fahrenheit.
• Fix main battery temperature missing, or wrong value shown, sometimes on the VRM Dashboard.
• Add Venus OS Large to the standard build. To learn what Venus OS Large is about, read here.
  • Having this in the standard build is rather good news. It (a) removes the need for the large images to now and then be built manually. And (b) you can now, once v2.90~3 is installed, in the menu, select the large image and update to that, see Settings -> Firmware -> Online updates -> Image type (normal vs large). And (c) Venus OS Large can now be updated using the Online update system. However: there seems to be a bug in (b). More news about that later.
  • Note that node-red no longer runs as root.
• Add various new VE.Bus models (Quattro-IIs and MultiPlus-IIs)
• Prepare for (or possibly even finish, I'll confirm later) Generator control widget on the VRM Portal website. Note that this includes various underwater changes to clean some things up, which should not make any effect.
• Add daily tracker history for Inverter RS and Multi RS, including transmission to VRM.
• Add first implementation of RV-C support. Its mostly RV-C out, ie making information of the Victron system available on the RV-C network where RV systems can pick it up to show in their user interfaces. Detailed spec will be published later.

DVCC:

• Force good settings for the FreedomWON eTower batteries: DVCC on, SVC and STS off.
• Better handle BMS disconnection issues: in some cases the solar chargers would not start showing Error #67 when unplugging the BMS. Now they do.
• Detect Dyness batteries, so they no longer show up under as a Pylon battery. Settings remain the same: DVCC force enabled on, SVS and STS force enabled off.
• Inverter/chargers: show state as "Ext. control"; instead of Bulk or Absorption, when controlled by a BMS/DVCC. When controlled by a BMS the inverter/charger would never show float, which caused questions. Now it just shows externally controlled, simpler, and more accurate: there is no bulk -> absorption -> float charge algorithm when controlled by BMS.

Less relevant for most users:

• GX LTE/GX GSM: prepare for allowing user configuration of PPP username and password, which some providers need. Note that this can't be used yet, gui change is pending.
• Prepare for the new coming model of the VE.Bus BMS, aka VE.Bus BMS v2; including remote firmware updates of the BMS.
• EV Charging station: add support for future models (AC22NS & AC22E) as well as some other preparations of features that can't be used yet until a future Venus OS beta version.
• Prepare for Widgets, a feature coming in next version of VRM App for iOS and Android.
• Update Linux kernel from 5.10.42 to 5.10.109, which updates to LTS for security issues and bug fixes, also adds support for Cerbo B1 and Ekrano, and adds ntfs support.
• Update Open Embedded Dunfell branches: various fixes to low level systems and tools.
• Various stability fixes to the xupd & xupc tools (which are part of remote firmware updates)
• Transmit default gateway to VRM as well as CPU temperature; for debugging.
• Add pre/post hooks to installation from USB stick: https://github.com/victronenergy/venus/issues/853

I haven't seen this on this forum before, so I thought I'd share: it is surprisingly easy to install a LCD on a raspberry Pi that needs absolutely zero configuration or calibration, either for the screen or touch.

Just search for "DSI" screens on Amazon or others, those are the screens that use the flat ribbon connection on the Pi instead of GPIOs, otherwise they look pretty much identical.

Those DSI screens are similarly priced as the small GPIO-based screens, but usually have a higher resolution (800x400 or higher), capacitive touch that requires no calibration, and of course they use no GPIO.

The nicest part is that once you connect the screen, that's it, no further action needed, it works. Just power up your Pi, remove `/etc/venus/headless`, reboot and you're in business!

I bought a "Waveshare" brand 4" screen on Amazon (perfect size for a Pi), but many other sizes/brands exist, I suspect they all behave the same. "Raspberry Pi DSI Screen" is a good search query.

Hope this is useful to others!

Hi community,

inspired by the dbus-shelly-3em-smartmeter from @fabian-lauer, I created my own dbus-shelly-1pm-pvinverter GitHub project to use a Shelly 1PM in VenusOS as a PV inverter. Maybe some one else find it useful.

Here are some screenshots from my current setup with these three Shelly devices (2x1PM and 3EM):

[image]

[image]

[image]

[image]

From surfing the community Q&A I can see some of you geeks have integrated your Smartthings system with Victron GX. Can I ask (please & Thank you) if you could point me to any resources for doing this.?

Hello All!

I am attempting to connect to the Victron MQTT broker using typescript using this package mqtt - npm (npmjs.com)

This is the code I currently have (I have replaced some parts with * to hide personal information but I can assure that these details are correct):

const mqtt = require('mqtt')
const TRUSTED_CA_LIST = `-----BEGIN CERTIFICATE-----
***
***
***
***
***
-----END CERTIFICATE-----`

function _get_vrm_broker_url(vrm_id: string) {
    var sum = 0
    for (var i = 0; i < vrm_id.length; i++) {
        sum += vrm_id.charCodeAt(i)
    }
    var broker_index = sum % 128
    return "mqtt" + broker_index + ".victronenergy.com"
}

const client = mqtt.connect('mqtts://' + _get_vrm_broker_url('*****'), {
    username: '*****',
    password: '*****',
    ca: TRUSTED_CA_LIST,
})

client.on('connect', function () {
    console.log('connected')
})

However when I test this in the browser I get the following error message:

WebSocket connection to 'wss://mqtt91.victronenergy.com/' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

I hope someone can tell me where I'm going wrong and lead me in the right direction,

thank you for your time!

Josh

just a quick Q if anyone experienced this.

After running same setup for 1.5yrs on various betas, for the first time lost VRM access.

It was a few days after upgrading to 2.90~3Large from 2.82something and following the 4G router providing internet connection to the boat running out of data (which is not the first time...)

Anyway, didn't have enough time, rebooted router (Teltonika RUT240) and rpi a few times, eventually switched from a wired connection to wifi and influxDB connection to work server was restored. However, VRM reports "last updated 1day ago". Other devices connected/reporting onboard work fine. Needless to say, connecting to remote console from laptop on same network onboard works fine.

Could be a router mishap, could not.

Didn't have time to reboot router to 2.82Large and see if things work or not, will do tonight.
Reluctant to upgrade to 2.90~8 as each upgrade means one hour editing signalK files for my custom NMEA2000 PGNs and recompiling ZeroTier-One, I should really sort/scrip this...

cheers

V.

I am using this library to run a custom MQTT client to connect to my Cerbo GX over pure MQTT (port 1883). This connects and seems to subscribe successfully, but then no messages come down unless.... I connect another client to the GX over WebSocket MQTT (port 9001), specifically the official Venus HTML5 App.

The issue is pretty consistent: I start my custom client, it happily receives CONNACK and accepts my subscription requests, and then just remains silent. I open the HTML5 App, it establishes its own connection via WebSockets, and immediately my custom client starts receiving messages for topics it is subscribed to. I close the browser window, my client continues receiving messages for about a minute before it receives an empty message for each of the subscribed topics, and finally messages stop coming.

Open the HTML5 App again — messages for my custom client resume, close it — they stop. The 1883 connection stays alive/subscribed all the time.

Why would that be happening? How could possibly the GX MQTT broker decide whether to send messages down 1883 depending on whether another client is connected on 9001? Is there any way to make it work on 1883 independently?

Cerbo GX firmware v2.66.

Hi,

Rather short, I’ll expand this later.

Previous post: https://community.victronenergy.com/questions/133780/venus-os-v2905-available-for-testing.html

Changes since then:

- add wakespeed support (monitoring). Requires wakespeed firmware which is not available yet! I’ll post the details of that once available. Should be within a few weeks.

- Improve Bluetooth sensor menu & options (continuous scanning, see all inserted adapters, and more)

- improve bluetooth radio on Cerbo Gx stability: if it malfunctions due to over temperature, the chances of it restarting when cooled down are now higher. But rest stays and will always remain the same for current hardware version: for any serious use, insert a usb bluetooth adapter as per manual.

- gx lte & gx gsm: Add modem username/password settings, required by some providers

- various EV Charger improvements (menu, connection stability, VRM)

- Fix the sign of the current and power for DC meters that are configured as source (except fuel cell and alternator, which were correct). broken since venus v2.80~18

- Add missing "Inverter only" mode to mobile overview

- Add support for VE.Bus BMS v2 firmware updates

- Venus OS Large: fix Node-RED Dashboard button missing on VRM and fix image selection / check for update function in online update menu.

Hi,

The latest release (38) appears to have removed my Ruuvi temperature sensors.

[image]

thanks in advance

[image]

I recently started to map the Modbus signals in home assistant and noticed the Modbus IDs for grid meter and PV inverter meter are the same, on other installations I found them to be different, I would have expected them to be different as to not cause conflicts, is this normal? Would this cause issues in data flow?

Can the Modbus IDs changed at will?

Thanks George

The new and updated Raspberry Pi Zero 2 W was just released. Will it be possible to run Venus OS Large on it? It seems to be pretty much an RPI 3 but with a lot less power consumption.