Dewesoft crash/stuck while calculating offline math.

I have about 10 offline calculations that are performed after a test, they are just some self checks, nothing intensive. I run a sequence that switched to analyze mode, recalculates the offline calculations and then stores them (see attached screenshot of sequence and crash). We have been running with no changes to this portion of the sequence for about 6 months until recently when the Acquistion rate was increased to 500 hz from 100 hz, even then we have not see this issue until today when we ran a 45 minute test compared to our normal 5-minute test. I had the person let it run until the sequence got to the next step and hit skip and it still exported the csv and winplot but the recalculating menu bar stayed on the screen. I assume it did not have enough time to run the calculations before trying to store and got stuck. I was wondering if there was a way in the sequencer to wait between the calculation and storing automatically or if something like a delay would have to be used. Alternatively, I just turned all the math back to online which hopefully will fix this short term

Gary,

Thanks for your question. It certainly within the realm of possibility that the 45 minutes runtime is long enough to cause a problem with the calculation where previously the 5 minute runtime was just small enough that it could quickly calculate what you need in the short duration between blocks. In this case there is actually a block that allows you to place a hold between the Calculation and Store blocks called the Delay block that allows you to set your own amount of time that it will delay from one block to the next:

Go ahead and try this and we can determine if that is the best path forward or if we need to try something else.

Great. What is the activation method of the Delay block?

slice masters

@Johnny Wilkes

Currently I just made the delay block long enough to cover my expected delay, so not ideal as short tests don't need any delay. Ideally Dewesoft would just add built-in check in the calculate block so this would not be an issue. The other option would be to check to see if the .dxd file is created and not growing in size this could be done with a system call.