Master/Slave function and Data Log export are available as promised in this final release of Aquasuite 2012.
But, as usual with major improvements, the old profile settings are not compatable, so all names and settings must be re entered.
Sigh.
Good Job AC programmers!

Thanks for the news.

This will be my first time updating, and I have quite a lot of setup done, so I'd like to understand exactly what will need reconfiguring.

Will my current overview page work?

When you say all settings need re-entering, does that mean literally everything - as in all sensors will go back to default names, virtual sensors will disappear etc?

Zitat von »BorisTheSpider«

Thanks for the news.

This will be my first time updating, and I have quite a lot of setup done, so I'd like to understand exactly what will need reconfiguring.

Will my current overview page work?

When you say all settings need re-entering, does that mean literally everything - as in all sensors will go back to default names, virtual sensors will disappear etc?

I had to re-do all my settings & re-do all the sensor names.. It didn't recognise my saved settings I had before anyway..

N.

Thanks for the reply.

I have set up an overview page that took a very long time, with colour-gradient graphs, nicely sized and aligned graphs, separate titles (which fix a flaw in the graphs where the % scale overlays the title) and so on.

I could probably face doing the renaming of sensors, and re-entering of controller curves, but I really don't want to have to redo the overview page.

Can anyone tell me if I will be able to re-use the overview page, possibly by doing "change datasource" on the graphs to re-assign things if possible, but without having to redo the layout, colour gradients etc. etc.

Also, can anyone tell me if I can install the new version alongside the beta, then I could transition over gradually and remove the beta when I'm ready?

I installed the new version, but can't seem to update the firmware! it seems to be just hanging in the last bit.

They are releasing another hotfix patch. The unit is supposed to reset at the 95% point and it isnt doing it.

I powered off PC (normal shutdown) and unplugged from power to let A5 power down and when I restarted it has 1026 firmware loaded and all working A.OK.
I waited for 3 mins while it hung at 95% before shutting down just to be sure.

There is a chance you could brick your unit so if you attempt this your doing it at your own risk... Id suggest waiting for the patch.

PS.. take screen shots of various Aquasuite pages before upgrading as it makes it easier to put all your settings/labels back in.


On another note....

Shoggy can you please share more about how the Shared Memory logging feature is implemented?

Will we be able to collect the data from any existing apps on the market or will programmers need to write their interface to access the shared memory data?

ie will AIDA64 be able to collect the data, I notice AIDA64 has a plugin for TMS-200 & T-Balancer to collect data?!?!?

Zitat von »Phatboy69«

Shoggy can you please share more about how the Shared Memory logging feature is implemented?

This is the same as the normal xml export (same xml sheme). This file is available with the name from "aquasuite-export-.....".
http://msdn.microsoft.com/en-us/library/dd997372.aspx

the file can deserialized with each xml library.

Aquasuite RC-1 will not start up the second time as soon as I set the overview page to "Load page automatically". The only way to get back in that I've found is to install the application again. I get the following .NET error:


Application: aquasuite.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at System.Linq.Enumerable.Last[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<System.__Canon>)
at DeviceAccess.HistoryData.GetStatisticData(System.TimeSpan)
at AquaComputer.Overview.DataControl.DataItem.ValueChange()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.runTryCode(System.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.WrappedInvoke(System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run()
at AquaComputer.Aquasuite.App.Main()

It's then followed by:

Faulting application name: aquasuite.exe, version: 1.0.0.15, time stamp: 0x50a259e1
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2
Exception code: 0xe0434352
Fault offset: 0x000000000000caed
Faulting process id: 0xf80
Faulting application start time: 0x01cdc23bb2f23240
Faulting application path: C:\Program Files\aquasuite 2012\aquasuite.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: f335a47d-2e2e-11e2-8f2f-5404a628c061

We have updated the aquasuite 2012. Download and reinstall the aquasuite.

The function seems to be working properly now. Thanks for the quick update.

For people who already have setup a custom overview page, export it first to a safe place. A new install will replace it with the default demo page.

You would not brick anything there with a firmware update because there is an permanent recovery partition inside the device memory. You could even unplug USB and power while updating and it would not harm the device in any way. You can just flash it again afterwards.

updated four aquaeros today...all connected at the same time. no issues.the only thing ,i had to restart the system after every successful update.
my tubemeters are finally working . oh,the user defined logo..kicks ass...

Went fairly smooth for me....I had Aquasuite not want to load a few times on boot but that seems to have leveled out.
Loving the easy resizable windows.

Zitat von »cristian.ticu«

i had to restart the system after every successful update

In this case it seems that you have not used the latest version. The problem where the device does not restart is already solved since yesterday morning.

There were no firmware updates for the Power Adjust 2 Ultra, is that right?

That is correct.

OK. Thank you.