Does anyone know if Victron has a modernized Cerbo-GX in the development pipeline?
I was surprised when Victron did the Cerbo MK2, when they did NOT change the CPU, although they already developed the Ekrano.
What I’m looking for is more CPU performance, as i discovered that the use of Venus-OS Large, and using some more NodeRed Flows and virtual devices (let alone a Dashboard V2!), is bringing the Cerbo to its limits very fast. Even with enhanced Watchdog Load average limits.
(Flows already roughly optimized, minimized Modbus usage, just very small and simple V1 Dashboard, etc.)
So, they offer the Ekrano, with a 4-core instead of 2-core CPU, but unfortunately i cannot (really want not) to bring all cabling to the place where I have my GX-Touch display now… IF the Ekrano would offer an additional HDMI output and I could just let the Ekranos display alone: Fine. But No.
What I do not want, is to fiddle around with Venus-OS on Raspi. I could, technically, but I don’t want to spent time in this.
I just want a little more performance, and do not want to introduce a second NodeRed on some additional Homeserver, etc.
The NodeRed on Cerbo solution seems the perfect idea for a neat simple easy, flexible and powerful setup! Just enhancing the 2- to the 4-core CPU would be more than enough (for me).
That brings me to the question: isn’t Victron already planning a Cerbo with the same CPU as in the Ekrano?
Does anybody know about?
I have two Cerbo GX MKII devices. One with scripts. One without. Both with dashboards. One with the old one and one with FlowFuse. Yet. No problems here. Almost sounds like you need less scrips or better optimisation of your flows. But let’s start with a graph of the Gateway - D-Bus round-trip time of your Cerbo GX MKII. Your: “bringing the Cerbo to its limits very fast” doesn’t tell me really anything.
Ala guidelines. No doubt something will eventually come along but it’s not something we can help with.
When will new product X, Y or Z be available?
Please do not ask the community when products, updates or approvals will be ready or available.
New products are announced at various shows and on the Victron blog website. This is done when the specifications are quite certain, but before there is a good indication around supply dates. Delays can occur. Victron Professionals can subscribe to our weekly newsletter which provides updates.
Check the price list on our website. For soon-coming-but-not-yet-in-available products, it lists an indicative release date. Once in the price list, you can place an order with your distributors, and then you will be among the first to receive the product when it starts shipping. Anything not listed in the price list yet is not progressed far enough for us to give out a date. So we will not comment on availability questions.
Thanks for your comment. But that wasn’t quite my question. There are lots of threads about that, I read them, acted on them and I’m aware of all of that.
Question is about if anyone know about future GX devices with more processing power.
No. We don’t. Of course there will eventually be one. We won’t know until it actually exists.
Depending on comms requirements you could consider a Pi in the short-term.
I am keen for a meatier device myself and it is inevitable.
Ok. Sure, but you wrote that your flows were already ‘roughly optimised’. So I was under the impression that possible improvements could still be made. I had a pre-installed flow/script combo that was improved by a forum member and my GX device has since been a lot more responsive. That could have been a workaround until a faster GX is released.
i have 16 flows and several svg graphic dashboards on my cerbo mk1 and no issues what so ever,
i have found certain things like a dashboard histogram could laod up and bog the system down. it really depends on what you have and how its done.
1 Like
OGPS
(Ed @ Off-Grid Power Systems - offgridps.com)
13
Lots of serial devices (i.e. VE.Direct and USB connections) will also slow things down. The Cerbo GX is weak sauce these days but that’s the way of things. The Ekrano is definitely a better choice for lots of devices, automations, NodeRed flows, etc. The GX Android app is a good workaround for casual access away from the Ekrano. Victron makes a wall mount enclosure for the Ekrano and with the exception of the VE.Direct cables coming loose when you open the enclosure, it works well. But, that’s a different topic.
Yeah, Histograms/Charts are eating performance like hell!
There are so many flows, virtual devices, modbus/MQTT actions for EV-chargers, heatpump, etc..
I already stripped down to the neccessary, but I am not happy with it, when I’m always limited in adding more things. Yes, e.g. I would want to do much more on the dashboard side, also with charts. But not on that Cerbo…
Oh. I saw it will be in June already. As I’m heavily occupied the next time, and won’t have much time left for this hobby, I probably wait if there will be any announcement. Good idea!
In that case I wouldn’t wait and get the Ekrano and sell the Cerbo GX device. And display in case you happen to own one. Still good value for money used. Problem solved.
Yes it is more expensive, but I assume that a new faster Cerbo GX will offer more and be also more expensive than the current one.
I can’t get NodeRed to function in any meaningful manner on a Cerbo; had the first one replaced under warranty and still can’t get even basic scripts to run without losing connection to the server and rebooting into safe mode.
On an unrelated note, I can’t even get assistants to run correctly in my inverter, so in my experience, if it’s not a plain vanilla install, I haven’t seen it work reliably.
If you’re running a beta, there are currently known issues with that.
I eventually moved from a venus to a cerbo and have many flows, the cerbo has no issue and has plenty of resources free.
It will depend on how many devices you have and also on the mods. We have seen some pretty poor implementations of drivers that were very inefficient.
There are an extraordinary number of nodered implementations out there running without issues, plenty with complex workflows.
