Page 1 of 1

Unhandled exception occurred during FW Upgrade to 2.7

Posted: Sun Nov 27, 2022 3:25 pm
by Hikescdnrckys
Unhandled Exception Error Pegasus Micro.zip
(2.64 KiB) Downloaded 291 times
Hi. I have a problem with the quad 12V output ports not staying turned on. I have turned them on through the Utility, clicked the Save icon, but when the device is powered off and then powered on again, the Output ports are Off again by default. I am at 2.6 and when I try to upgrade to 2.7 I get unhandled exception error. Please see attached zip file for full error.

System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Peg.UI.RJesHttpClient.BaseHttpClient.<RequestAsync>d__10`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.RJesHttpClient.BaseHttpClient.<RJesRequestAsync>d__12`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.RJesHttpClient.FirmwareUpdateHttpClient.<UpdateDeviceAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.View.FirmwareUpdate.FirmwareUpdateView.<UpdateDeviceFirmwareAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.View.FirmwareUpdate.FirmwareUpdateView.<Ribtne_Update_ButtonClick>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)

Re: Unhandled exception occurred during FW Upgrade to 2.7

Posted: Sun Nov 27, 2022 9:37 pm
by Evans
Thank you for reporting this.
We are investigating what is the cause of this error.

Re: Unhandled exception occurred during FW Upgrade to 2.7

Posted: Sun Nov 27, 2022 10:21 pm
by Hikescdnrckys
Thanks Evan. If it helps I got the same issue on two different computers, and also tried uninstalling and reinstalling the Unity app. Both computers were on Windows 11 BTW.

Re: Unhandled exception occurred during FW Upgrade to 2.7

Posted: Thu Dec 01, 2022 2:39 pm
by Hikescdnrckys
Evans wrote: Sun Nov 27, 2022 9:37 pm Thank you for reporting this.
We are investigating what is the cause of this error.
Hi Evans.

Is there any update on this issue yet?

Further testing on the Quad 12V Output ports not staying ON shows that if I turn to On, save it using the icon, and save the profile, close the Unity App and then re-open the App, the Output Ports are still ON, BUT if I attempt to reboot the device, it defaults back to OFF. If I power off the device, and then power back on and reopen Unity it also defaults back to OFF. This means before each session using the device on my scope I will need to connect it to my laptop, change the setting and then close the app, but power will have to stay on at all times, else I will lose the setting. This is obviously not acceptable.

Re: Unhandled exception occurred during FW Upgrade to 2.7

Posted: Mon Dec 05, 2022 2:06 pm
by Hikescdnrckys
The problem turned out to be a Windows OS issue. Upgrade fails on multiple Windows 11 computers but succeeds on Windows 10.

Thanks for the excellent support.

Re: Unhandled exception occurred during FW Upgrade to 2.7

Posted: Mon Dec 05, 2022 6:58 pm
by Evans
Thank you for the feedback.
I check with latest Windows 11 which is working fine.
We have seen issues when customer that use KMS pico (serial activator) in Windows which modifies lots of system variables and crashes the update process.
Will continue to investigate the issue.