Sie sind nicht angemeldet.
Lieber Besucher, herzlich willkommen bei: Aqua Computer Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
Not possible.Expand or unlimit the maximum number of virtual temperature sensors to maximum number of controllers in Aquasuite
The device has limited ressources. To expand this function we have to limit other functions.Allow to write any expression with operations, functions and brackets for virtual temperature calculation in floating point
I thought the 'Aqua Service' in aquasuite package might be a good bridge to deliver software sensors data to aquaero engine. And it might be an 'extender' for the processing engine.All funtions are directly computed in the device. The aquasiute is only for visualisatzion and setup.
I thought the 'Aqua Service' in aquasuite package might be a good bridge to deliver software sensors data to aquaero engine. And it might be an 'extender' for the processing engine.All funtions are directly computed in the device. The aquasiute is only for visualisatzion and setup.
If hardware working in standalone mode - OK, all software sensors are unavailable and extended logics is unavailable also. This is reasonable.
As the minimal improvement, sebastian, will the virtual sensors calculations be possible in the future?
Like VS1 is an average of T1 and T2, VS2 is an average of T3 and T4, and VS3 is a maximum of VS1 and VS2...
That might be a great feature if a components require thermal control in more than single point and cooling of a component group should be based on a worst temperature.
Thank You for the answer!
I thought the 'Aqua Service' in aquasuite package might be a good bridge to deliver software sensors data to aquaero engine. And it might be an 'extender' for the processing engine.All funtions are directly computed in the device. The aquasiute is only for visualisatzion and setup.
If hardware working in standalone mode - OK, all software sensors are unavailable and extended logics is unavailable also. This is reasonable.
As the minimal improvement, sebastian, will the virtual sensors calculations be possible in the future?
Like VS1 is an average of T1 and T2, VS2 is an average of T3 and T4, and VS3 is a maximum of VS1 and VS2...
That might be a great feature if a components require thermal control in more than single point and cooling of a component group should be based on a worst temperature.
Thank You for the answer!
Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »Railgun« (17. Dezember 2015, 10:18)
Are you talking about cooling individual components, or separate groups, on an air cooled system?
For the future we plan a solver to calculate and mix different sources to a new sensor in the aquasuite service.
You should be able to do that now
Also, why would you ever need an average out of any sensor.
...
The only think I can see is taking individual core readings, at which point I'd take a max of them, certainly not an average.
What's your setup out of curiosity that would require these calculations?
-