Data stops logging without warning

[cbsw]

I have been logging voltage data in LabView SignalExpress Full v3.0, and I have come to find that the data stops logging if:

1) another run is started without saving the previous run, and

2) multiple displays are added while a run is in progress.

The program saves the starting 10 seconds or so of data, but the rest of it is lost, even though the amount of time running is saved (as in, the log file shows 5 hours running and two data points taken). The project is taking continuous samples at 100m Hz.

Any advice as to what might be causing this, how to fix it if possible, or if there are other circumstances that could cause this to happen that I should be aware of, would be much appreciated.

[Jonathan_S1]

Hi,

Could you describe your setup a little bit?  When you start logging, are you logging for a finite number of iterations or time, or are you logging indefinitely?  I'm a little confused how you could start a 2nd log while another one is running.  All of your logs should be saved in the bottom left hand corner.

What types of displays have you added that causes this? Or is it arbitrary?

Jon S

[cbsw]

Hi Jon,

The setup is measuring the voltage of several batteries over time. There is an alarm setup that stops draining the batteries after they reach 1V (a FET in series with the battery/resistor circuit is set low by the alarm). I am checking the setup manually so I can see the recovery voltage settle after the alarm is triggered for each battery, and will stop the logging when they have all been triggered. 

Sorry, I wasn't clear about saving the runs. A couple of times I realized that I had an incorrect setup (alarm was triggering the wrong voltage, etc.), and so I stopped the run without saving it. When I started a new one, it did not record any data.

Some of my problems may be related to this topic that I found: http://digital.ni.com/public.nsf/allkb/D14903D870AD971586257570007C1841

In some of the cases, I renamed the logs right after they started. I realize now this may have been the real cause of the display issue. With the display issue, I brought up multiple data view displays so that I could view previous runs and compare them while there was another run recording. The run stopped recording after I brought on these multiple displays and zoomed in on the current run. However, I did rename the current log while doing this, so the displays may not have caused the issue.

Please let me know if there are any other issues like this that I should be aware of, so I can prevent losing any more data.

Thank you --

cbsw 

[Jonathan_S1]

Thanks for clarifying.  Here's a list of known issues with SignalExpress 3.0.  You can sift through them and see if any of them may be pertinent to what you are doing.

http://digital.ni.com/public.nsf/allkb/F542F58D65F5BA618625745D0081A5E8?OpenDocument

Jon