idsnt3

Since there are no answers, I am writing a new one. The method you mentioned in the previous post is already being applied to the system. It was applied to stop and restart the measurement twice in the early morning when the machine to be measured was not operating. Confirmed that it works well for 10 days. (25600 sampling) However, in the case of other measuring systems to be applied in the future, this problem must be solved because the operation is carried out 24 hours a day. I have one more question. The QuickDAQ program provided by dt8837 has the same problem. As shown in the attached picture, if Enable Continuous Acquisition is turned off and Duration is set to 2day, it is automatically set to 11:39:03 (hh:mm:ss). (51200 sampling) If turn on the option and proceed with measurement, the measurement graph screen stops when the scan index becomes 2147450880. I'm guessing the cause of the freeze in QuickDAQ is the same as what I asked. Is it possible to fix the problem by modifying the windows driver of DT8837?

Thanks for the reply. In order to solve the problem, the method you mentioned has already been applied to the system. Measuring is stopped and restarted twice in the early morning when the machine to be measured is not running. Confirmed that it works well for 10 days. (25600 sampling) However, in the case of other measuring systems to be applied in the future, this problem must be solved because the operation is carried out 24 hours a day. I have one more question. The QuickDAQ program provided by dt8837 has the same problem. As shown in the attached picture, if Enable Continuous Acquisition is turned off and Duration is set to 2day, it is automatically set to 11:39:03 (hh:mm:ss). (51200 sampling) If turn on the option and proceed with measurement, the measurement graph screen stops when the scan index becomes 2147450880. I'm guessing the cause of the freeze in QuickDAQ is the same as what I asked. Is it possible to fix the problem by modifying the windows driver of DT8837?

Since there was no answer to the added question, I am posting a new post. Tested by limiting RequestedScanIndex to 0~2097152 as shown in the attached file. In this case, no error occurs, but the scan value is not output from the fetch function after one cycle. How do I modify it to take continuous measurements? Or is there no example where I can measure more than 24 hours at 25600 sampling? C++, C#, labview, whatever. AnalogInTachCounterStreaming_MOD_2.vi

Thanks for the reply. Tested by limiting RequestedScanIndex to 0~2097152 as shown in the attached file. In this case, no error occurs, but the scan value is not output from the fetch function after one cycle. Could you please check the source again? Or is there no example that can measure more than 24 hours at 25600 sampling? c++, c#, labview, whatever. AnalogInTachCounterStreaming_MOD_2.vi

hello? I want to make continuous signal measurement using dt8837. I am programming using labview, Sampling is 51200 and adc channel 0 was collected in wrap enalbe mode. A normal waveform is shown on the graph until about 11.5 hours, but after that, an error occurs in the acquisition fetch. AnalogInTachCounterStreaming.vi example was modified and used. As in the basic example, the following expression is applied to fetch as an input variable. RequestedScansIndex = ActualScansIndex + ActualScansRead When ActualScansIndex is about 2^31, the sum of ActualScansRead becomes a negative value. 2147481601 + 5120 = -2147480575 If this value is entered in RequestedScansIndex at the time of 12 hours execution, an error occurs during the fetch process. According to DT8837.chm file, RequestedScansIndex is 0 to (2097152/number of channel). I understand that the lower limit must not be a negative value. The upper limit works normally up to 2^31, so the above explanation doesn't seem right. When the added value becomes a negative value, I tested it by changing the overflow amount to a positive value. Even in that case, after 12 hours the fetch will not proceed any further. 2147481601 + 5120 = -2147480575 => 3073 What value should RequestedScansIndex be after 2^31 for successive acquisitions? thank you AnalogInTachCounterStreaming_MOD.vi