Home Community Discussion Forums Most Active Software Boards LabVIEW Topic

LabVIEW

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Increasing Execution Speed

Re: Increasing Execution Speed

‎08-25-2020 05:37 AM

I am using 3 digital channels on Picoscope. Two of them receive the trigger TTL signals. One channel is for single events signal.  

So, when I split these channels, the rest of the code is doing the same kind of things as before.

 

I have a search for the low frequency trigger. 

first trigger search.png

After, I create two different outputs depending on the fact whether the low frequency trigger is found. So, I have the case structure with almost the same codes. In both cases, to create these outputs I search for the position of the high frequency trigger. 

second trigger search.png

 Based on the position of these trigger I cut the part of the single event array (first bit).

cut.png

And I sum up these data  

sum.png

I need exactly this data . The experiment could be very long. So, it is not an option to save the data first and than to process it. 

 

I completely agree that is seems to be a waste to use I16 for a single bit and that could be the reason why the code is not that fast as it could be. However, I do not know right now any better way. Could you advice anything? 

 

 

 

   

 

0 Kudos
Message 31 of 31
(171 Views)
Reply