Post Go back to editing

SensorPal Crashing

Category: Software
Product Number: EVAL AD9540 ELCZ with ADICUP3029
Software Version: 2.5.2.5

A student researcher and I have downloaded SensorPal to use with a 5940 ELCZ evaluation board. As we are testing the software and board, the SensorPal program frequently crashes (suddenly closes). When this happens, it is while we are trying to move a tool into the workspace or adjust measurement settings. 

This is happening on two different computers. We downloaded SensorPal on 2022 May 23. The version is 2.5.2.5 which seems to be the most recent. 

If anyone has any tips or suggestions, please let us know. Thanks!

 Could you please assist in this query?

  • FormerMember
    0 FormerMember on Jun 10, 2022 10:05 AM in reply to FormerMember

    Hi    not sure if you missed this, but could you please help this user out.

  • Hi,

    may I know the following details?

     

    • OS used, and version.
    • Do you have admin rights in their PC?
    • Have you tried to right click -> Run as administrator the SensorPal GUI?
    • Have you tried restarting the PC?
    • Have you tried reinstalling the SensorPal GUI?
    • What techniques produces the crash?
    •   the SensorPal program frequently crashes (suddenly closes). When this happens, it is while we are trying to move a tool into the workspace or adjust measurement settings. ”. How frequent does it crash? Always or after a few start measurement?
    • Did you update the firmware using the Firmware Updater?

          

  • Akila, thank you for the response. This issue is happening on my laptop and on my student's. We both have the same laptop (HP Elitebook) and I believe we both have the same OS (they're school computers).

    • The OS is Windows 10 Enterprise version 20H2, install/update date is January 2022
    • I do have administrative permission.
    • I tried running as administrator and still had the same issue.
    • I tried restarting the PC and still had the same issue.
    • I tried uninstalling and reinstalling SensorPal and still have the same issue.
    • I can better describe the issue: We open SensorPal and will select different experiment types and expand menus to look the the available settings (we're completely new to the AD5940 and SensorPal, so we're browsing to learning what it can do). The SensorPal application will suddenly close after we select a different experiment type or after we expand a settings menu. This happens every time we use SensorPal. Sometimes it closes after the first action, sometimes it closes after a few minutes of navigating around. It closes when we are just browsing the application. Usually we aren't trying to start a measurement and don't even have a device connected, but SensorPal will close within a few minutes. 
    • The version of SensorPal is 2.5.2.5, the application checks for the most up-to-date version each time it opens. We have opened SensorPal a few times with the AD5940 connected and have been able to update the firmware on the ADICUP3029, but the SensorPal crashing happens both with and without a connected device.

    Let me know if there is any other information that might be helpful. Thank you!

    -Mike

  • Hi,

    • Did you change the installation directory when installing the application?
    • Could you locate the HTMLFiles folder under the SensorPal’s installation folder and check the number of files are in there?
      • The default installation directory, it is on C:\Program Files (x86)\Analog Devices\SensorPal\HTMLFiles
      • If there are less than 81 files, can you screenshot the files inside this folder? Just to check if there are missing file in case.
    • I can’t reproduce the bug on my side. I tried opening every technique (all electrochemical and all bioelectric) and expanded the menus and hovered the mouse pointer through all the settings but it didn’t crash.
    • It would really be helpful if you can provide a step by step guide on what you do in the GUI before it crashes.
      • For example: Open GUI. Drag Linear Sweep Voltammetry to Work Area. Hover the mouse pointer here and there, etc.

     

  • Akila,

    I did not change the directory during installation, and the HTMLFiles folder does have 81 items:

    Previously I'd just been randomly clicking around before SensorPal would close, but today I tried repeated steps. This is a sequence of actions that I attempted 5 times, and SensorPal crashed each time at the same step:

    • Open SensorPal
    • Version check says it is up-to-date, close the version check window
    • Close the tutorial
    • Initial experiment in Work Area is Square Wave Voltammetry
    • Drag Impedance experiment to Work Area
    • Change amplitude to 100 mV
    • Change start frequency to 100000 Hz (100 kHz)
    • Change points to 10
    • Open Frequency Sweep tab
    • Check Enable
    • Change stop frequency to 100 Hz
    • Check Logarithmic
    • Minimize Frequency Sweep tab
    • Open Miscellaneous Settings tab and then re-minimize 
    • Open Resistance Values Settings tab
    • Click on each variable in Resistance Values Settings tab but don't change them
    • Minimize Resistance Values Settings tab
    • Open Digital Filter Settings tab and then re-minimize
    • Open Electrode Settings tab
    • Click on each variable in Electrode Settings tab but don't change them
    • Minimize Electrode Settings tab
    • Drag Cyclic Voltammetry experiment to Work Area
    • Change step potential to 5 mV
    • Change scan rate to 100 mV/s
    • Attempt change cycle count from -1 to 10, but SensorPal closes when I try to click in the box to change the -1.

    I'm curious to see if that sequence is ok on your end. Thanks for the help!

    -Mike

  • I'm getting this error as well.

    Win10 ver21H1 64bit i7-3820 16GB ram, all other applications stopped. Not virtualised, bare metal

    .net framework 528372 (Windows 10 May 2020 Update and Windows 10 October 2020 Update and Windows 10 May 2021 Update)

    sensor pal v 2.5.2.6

    EVAL-AD5941BATZ plugged into a ADICUP3029.

    Managed to load firmware into the ADICUP3029

    I can remove the default measurement technique, add in any other EXCEPT battery impedance, and it's happy. Drag in the Battery Impedance technique, app crashes.

    I've run with admin rights, no change

    restarted system, no change. 

    reinstalled sensorpal, no change

    run MS's .net repair application no change

    Windows event viewer captures the following two errors:

    Application: SensorPal.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.IO.FileNotFoundException
    at System.IO.__Error.WinIOError(Int32, System.String)
    at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean)
    at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare, Int32, System.IO.FileOptions, System.String, Boolean)
    at System.Net.FileWebStream..ctor(System.Net.FileWebRequest, System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare, Int32, Boolean)
    at System.Net.FileWebResponse..ctor(System.Net.FileWebRequest, System.Uri, System.IO.FileAccess, Boolean)

    Exception Info: System.Net.WebException
    at System.Net.FileWebResponse..ctor(System.Net.FileWebRequest, System.Uri, System.IO.FileAccess, Boolean)
    at System.Net.FileWebRequest.GetResponseCallback(System.Object)

    Exception Info: System.Net.WebException
    at System.Net.FileWebRequest.EndGetResponse(System.IAsyncResult)
    at MS.Internal.WpfWebRequestHelper.EndGetResponse(System.Net.WebRequest, System.IAsyncResult)
    at System.Windows.Navigation.NavigationService.HandleWebResponse(System.IAsyncResult)
    at System.Windows.Navigation.NavigationService+<>c__DisplayClass106_0.<HandleWebResponseOnRightDispatcher>b__0(System.Object)
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, 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 System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(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.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
    at System.Windows.Application.RunDispatcher(System.Object)
    at System.Windows.Application.RunInternal(System.Windows.Window)
    at System.Windows.Application.Run(System.Windows.Window)
    at SensorExpertGUI.App.Main()

    AND

    Faulting application name: SensorPal.exe, version: 2.5.2.6, time stamp: 0x62b27006
    Faulting module name: KERNELBASE.dll, version: 10.0.19041.1766, time stamp: 0x270baf18
    Exception code: 0xe0434352
    Fault offset: 0x0012c3a2
    Faulting process id: 0xbec
    Faulting application start time: 0x01d892b86fbee65d
    Faulting application path: C:\Program Files (x86)\Analog Devices\SensorPal\SensorPal.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: aff4067f-8cc2-49ca-a38d-3b07b489cc56
    Faulting package full name:
    Faulting package-relative application ID:

    Thank you, 

    Mark

    Keen 

  • Hi Mark,

    I have been experiencing the exact same error during the last weeks. Only the Battery Impedance was not working. Sometimes, after the software was open for some minutes, I would try to active the Battery Impedance Method and it would work.

    I have made the decision to stop using the SensorPal and started to use the IAR Workbench with the development files from GItHub and it has been working perfectly since them.

    Hope you find the solution soon.

    Cheers!

    pmarq

  • Thanks pmarq,

    I'm currently downloading IAR workbench as I type this, and will load development files and use this method too. Was all excited when I unpacked my eval kit that arrived today, lined up a bunch of cells to test, and had no joy.

    Need to wrap my head around low level control if I'm going to incorporate the AD5941 into my battery management system design anyway. I was trying to have fun before the hard work begins. 

    Regards,

    Mark

  • The reason is that there are 3 help files missing, or badly referenced. 

    The tools.json file refers to the following files, that do not exist:

    "HTMLFiles\\batteryimpedance_help_magphase.html",
    "HTMLFiles\\batteryimpedance_help_mag.html",
    "HTMLFiles\\batteryimpedance_help_phase.html",

    2 options:

    1) create the 3 files

    2) rename the file names in the json file, by removing "battery", as the "impedance_help..." files exist. (Once you do that, you can also change the "defaultsequence" to point to your preferred tool.)

    Both methods work for me. 

    The real answer would be a new version of the software, but this workaround might help people.