We have a 4x4 vehicle install where we have added a second orion xs and a battery bank upgrade.
The first one had some decent history on it, however after the system update we have noted that neither the origional orion or the new one have or show any history graphs for charging.
But there have been several trips with charging and successful cycles on the house battery.
FW 1.07 and 1.08
Are there any other users with this issue?
I also have Orion XS in a 4x4 setup. Mine remains powered (via the start battery connection) even though the house battery is isolated when the vehicle is not in use. It loses the Trend screen settings and data after a few days but not the overall statistics on the History screen. I guess memory is limited and it either over-writes the trend data or stops recording it after a few days of inactivity.
However very irritating to have to reselect Trend parameters every time I use the vehicle.
Any news on this @guystewart ?
I don’t,
But I have forwarded it to the team to ask.
I seem to have a similar problem.
when I use Victron Connect over Bluetooth to query my Victron MMPTs I can see many days of history on the History tab, and I see current data on the Trends graph , but also within a few moments, the app has fetched about 30 days of trends data . That’s great and what I expect from my Orion XS
However, my Orion XS shows no history and only shows “current” data on the Trends graphs. By “current” I mean fresh data for the last few seconds / minutes in the live Bluetooth session of connection with VictronConnect. If I switch away from the app, and back again, I lose even the data from a few moments ago .
The OrionXS is on firmware v1.08. Will firmware 1.12 fix this ?
Orion XS 12/12-50 A3F0 firmware 1.08
Victron Connect v6.24
Report attached
VictronConnect_report OrionXS-nohistory-20251205.log (662.6 KB)
Hi @ChasingBlue
As can be read at 11. Stored trends & Instant readout, the Orion XS does not support stored trends.
With kind regards,
Thiemo van Engelen
Ah ha! That explains it then! 
is this a limitation of the hardware, or might we see this functionality with a future firmware upgrade ?
it would be very useful for monitoring performance, optimisation, diagnosis/troubleshooting etc.
Thank you.
Hi @ChasingBlue
There is (probably) no hardware limitation, it just hasn’t been added to the firmware.
With kind regards,
Thiemo van Engelen
