Hallo Zusammen,
mein neuer SmartSolar 150/70 zeigt bei “Daily history” in der Konsole nur zwei Tage an (Heute und Gestern, seit 2 Wochen in Betrieb). Meine 150/35er zeigen da mindestens die letzten 30 Tage an!
Firmware v3.15, angeschlossen an Cerbo GX per VE-CAN. Per Bluetooth mit der App sind 14 Tage Historie sichtbar.
Der Cerbo läuft seit Ende 2023 (oder so) mit Version v3.31~3 und klassischer UI. Hilft es, wenn ich da ein Update mache?
hallo,
wie hoch ist denn nachts du pv-spannung?
tschuess
5.2V
Für den MPPT gibt es auch ein Update auf 3.16, muß ich mal nach dem Changelog suchen.
Wie sind die MPPTs mit dem GX Gerät verbunden?
Wir hatten hier vor ein paar Tagen dazu erst ein Thema.
Es scheinen über VE.Can nur 2 Tage ausgelesen werden zu können, über VE.direkt kann man mehr auslesen.
Die acht Stück 150/35er haben nur VE.direct und sind folglich darüber angeschlossen. Der 150/70 hat auch VE.Can und hängt daher damit am Cerbo. Für VE.direct müßte ich erst noch ein Kabel zu USB besorgen oder basteln.
Das Changelog SmartSolar Charger - VE.Can Port Models - Firmware Update v3.16 - Victron Professional weiß nichts zu diesem Problem.
Die Suche nach “Daily history” und die Vorschläge beim Verfassen des neuen Themas haben leider die älteren Beiträge nicht gefunden 
In einem Changelog werden ja normalerweise auch keine Bugs aufgeführt.
Ich vermute hier eine Limitierung des VE.Can Protokolls.
hallo,
ueber can-bus hat die history nur 2 tage, aber du kannst sie ja auch ueber bluetooth abrufem, dann bekommst du 30 tage!
tschuess
Das halte ich aber für einen Bug. Das Protokoll kann es laut anderer Beiträge in den älteren Themen, es wird vermutet, daß der Bus geschont werden soll. Das sind aber doch nur eine Handvoll Bytes pro Tag, und die können auch dynamisch bei der Anzeige der Seiten in der Konsole geladen werden. Das Argument zieht also nicht.
A balance must always be maintained between data volume, data integrity, system control, reliability, and processing overhead.
When designing a product and system intended for broad deployment—where the number of connected devices (MPPTs) is variable and not predetermined—it is critical to establish a standard that ensures reliable performance across a wide range of system sizes, from as few as 2 MPPTs up to 25 in a string, with the potential for a second parallel string of 25.
Comprehensive historical data remains accessible through other methods and via the VRM platform for detailed diagnostics and analysis.
All true, but how does this pertain to not transmitting older data? For the bus load, I don’t see any difference between viewing daily data of one MPPT 30 days back and data of 15 MPPTs two days back. Those data won’t be transmitted all the time and can have a low priority in order to ensure realtime operation of the bus. These data can be loaded on demand and/or cached in the Cerbo. Bluetooth works, but requires physical access to the device. As is, it’s just inconsistent behavior between the two connection methods.
You don’t but the system will.
Requires processing on top of everything.
Then there is storage balancing with other system functions.
Ther is also a lot of data and things happening and moving that you aren’t thinking about as well.
Which is what the vrm is.
One device is expected on the ve direct. 30 days is easy.
30 days over 15 devices is 2 days and the connection can take 25 reliably. So 50 days of data then. When only considering one small system when the device and connection type is designed for everyone including the bigger systems it seems limited, but there is a bigger picture.
The VE.Can protocol is way older than VE.direct.
I guess it’s not the traffic, maybe the underlying protocol doesn’t support reading more data?!
I asked Victron but I sure it would read more of the historical data if it would be possible.
hallo,
das ist kein bug. es ist nun mal so, dass es auf dem can-bus nur 2 tage (gestern und heute) in der history gibt.
bei meinen alten can-bus-laderegler gibt es auch nur 2 tage und es fehlen auch noch einige daten, die die neuen mppts liefern.
da ich diese statistik sowieso nicht benutze, weil es damit probleme gab, und alle daten in einer datenbank speichere, mache ich mir meine eigene statistik.
tschuess
Nope, according to v3.50~13 GUIv2 MPPT History Incomplete - #4 by alexpescaru the devices are capable of delivering the data via VE.can. So it’s a design choice. Is it at least documented somewhere? If there was an error message in the console saying “no more data due to bus limitations, for older data look in vrm”, this thread wouldn’t have been startet. But as is, I had to suspect a bug.
CAN is slow at bulk data especially over distance. And yeah an older protocol probably.
The bus is running 500kbit/s, regardless of cable length. And you don’t transmit all history data of all devices at once, if done right you transmit history data of one device and two days at a time, then scroll the console and fetch the next tiny set.
On the mppts? They are 250..?
I suppose so, but then i do see that the GX would need to have more processing power as it needs to run the system and do that. There are probably many things we haven’t thought about that the dev team has had to deal with to get to the decision they have to keep it at two days.
CAN set up length and quality etc. reliability is the main aim of a system. When you can access over the vrm in VC each mppt or over the vrm it makes better sense to err on the side of good control with an overhead.
Not necessarily, default is 250kbit/s. Connecting BMS (500 kbit/s) to VE.Can port? - VictronEnergy
But nevertheless, that speed is not dependent on cable length.
An interesting thread. The CAN bus for the MPPT’s is running at 256K. This is unlikely to have anything to do with bus loading or age of the protocol. If you use VictronConnect, connect to your device via VRM and select the MPPT all 30 days of data is available. Take a short while to load, but that is not surprising as the data is flowing from the MPPT to the GX device to VRM to Victron Connect.
I suspect that it is to do with the missing capabilities that need to be added to the system following the introduction of GUIv2,
The reasons that the values for today are available is that is fetched by the VE.Can driver and stored for use in the GUI. The historic data is not.
I do not have a VE.Direct connected MPPT at the moment ,to understand how that side of it works, but just because the capability exists there does not mean that everything is there for the CAN side of things.
I am sure that this is on the backlog and when priorities allow it will be delivered.
In VRM, I can’t find some of the data available in the console, namely the “Charge time” line. And no, I’m not using GUIv2 and this problem precedes v2 anyway.
