Multiplus II internal temperature

I can’t see the MPPTs temperatuer either… Only temp I see is the battery temp, as I use a Smart Battery Sense. This temperature is also displayed in in every MPPT’s overview page. But its not the MPPT itself.

Yes, you are right. My mistake. I saw a temperature on mppt and I thought it was a mppt temperature, but it is a dvcc shared temperature from battery.

I see that you’ve already participated to the discussion below, where Thomas got the temperatures from his SmartSolars…
https://communityarchive.victronenergy.com/questions/287173/is-there-a-way-to-query-the-internal-temperature-o.html

So playing around in Node RED, looks like the internal temp sensors (PLC’s in series) in the multi only output 3 data levels.

Maybe @guystewart we can get some data on what temps these levels correlate to. If possible.
From there we can have some indication of internal temps, granted they will vary across the unit.

Considering the vast quantum of data points exposed by the MP’s and Cerbo it does seem somewhat of an interesting omission not to include the ADC readout from the PTC’s within the exposed data set. Can’t imagine it’s a proprietary information point since adding 3rd party sensors is simplicity itself…
@guystewart Do you know the reason (Political/Technical) why this simple metric was not included…? and if it could be added to a future FW?
Thanks.

2 Likes

I don’t see anything in the image to suggest it’s not a data point in the dataset within the MP architecture… It’s clearly passed through an ADC to drive the fan speed, thus it’s live data… Unless I missed something in your post…?

I can’t say if it is totally impossible or not, but I have heard in the past that it is not something that is easy to add.

The current implementation of the multiple sensors in series does what it is designed to do in the closed loop of the multi for fan and alarm control.

I don’t know the details but I think that due to the way it has been done (and these design choices were made before the MultiPlus had any communications interfaces) the results would not be so elegant as a simple ‘temperature’ reading, and would just raise more questions than provide answers.

I can say that there are no plans to do any firmware changes to make it more accessible.
So energy would be better spent on some other method (such as using the supplied temperature sensor, or buying a Ruuvi).

As for identifying which of your units is heating up first, a method you could use would be to install the ‘fan’ assistant, and connect that to a digital input. Then that would flag which unit calls the fan first, and that would be the one that needs additional cooling, better balancing or other measures.

Regarding the balancing, check out this recent post by Nick that shows how he used Node Red to identify and then balance his system - Improving parallel system imbalances

I’ve been using installing and supporting victron equipment for well over a decade and If it was something as simple as a few lines of code it would have been implemented by now due to the numerous requests over the years. Just look at everything else that has been continuously improved and implemented.
It’s very likely that if there is an ADC value that it’s never exposed to the processor, or that the fan control is simply analog.
Let’s hope it’s something that is on the cards for the multiplus III.

Hi, my friend solved this using 3D printed inlet with two fans. The fans have their own adjustable speed control by a temperature sensor, and he placed this sensor on the toroid transformer inside Multi. The system is much more quiet overall, because the fans don’t run on max speed most of the time. And it can be overloaded for longer periods of time.
Multi II 5000 has just one fan inside, on one side. MP 8000 has two fans, If i remember correctly.

My only concern is that in case of a fatal MP failure (fire inside the case), the fans could make the situation much worse, because they are powered directly from the main DC bus.

2 posts were split to a new topic: Multiplus temperature

Since I just stumbled over this thread I thought I’d drop in a quick clarification.
What most people will see as the “fan” assistant in a Multi is the “Silence fan” assistant, used to silence the fan based on an input condition - with potential lack of performance as a consequence.

With the Programmable relay assistant, an output relay of the Multi can be activated when the internal fan comes on.
And then that can be used to identify the Multi that could benefit most from extra cooling :slight_smile:
The relay output could even be used to drive an additional cooling fan.

Hope this helps.

Oops! That page doesn’t exist or is private.