LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Counting on sensors

Yes, I understand and I try avoiding feedback node, but let's say the acquired data is greater than 10.5 for more than 5 seconds, your counter will keep counting. 

Maybe what we need to know is for how long the acquired data would stay greater than 10.5.

0 Kudos
Message 21 of 27
(520 Views)

@GRCK5000 wrote:

Yes, I understand and I try avoiding feedback node, but let's say the acquired data is greater than 10.5 for more than 5 seconds, your counter will keep counting. 

Maybe what we need to know is for how long the acquired data would stay greater than 10.5.


It should not be the case, basically for every iteration it acquires data it should validate irrespective of timing (nowhere he mentioned timing).

Let him come back after testing. 

----------------------------------------------------------------------------------------------------------------
Palanivel Thiruvenkadam | பழனிவேல் திருவெங்கடம்
LabVIEW™ Champion |Certified LabVIEW™ Architect |Certified TestStand Developer

Kidlin's Law -If you can write the problem down clearly then the matter is half solved.
-----------------------------------------------------------------------------------------------------------------
0 Kudos
Message 22 of 27
(510 Views)

Palanivel! Don't talk to me like that. Lol... just kidding 😁. I'm also learning myself, but yeah let's see what he says after testing.

0 Kudos
Message 23 of 27
(507 Views)

Im going to be real honest I am so confused with what is going on. Because the GRCK5000 your code only counts to 1, while PALANIV your code once it is triggered it just counts when the it gets tripped, but only when going really fast. It is missing all of the slow trips. But when having the refresh rate at 1 isn't that the fastest it will go. It is reading too slowly. So using the Palaniv side of the code, is there any way to speed it up. This is what I used.

0 Kudos
Message 24 of 27
(485 Views)

Hi Collin,

modify use "convert from dynamic data" as shown with the arrow below.

GRCK5000_0-1682662206908.png

 

 

0 Kudos
Message 25 of 27
(476 Views)

@collin_g_10 wrote:

Im going to be real honest I am so confused with what is going on. Because the GRCK5000 your code only counts to 1, while PALANIV your code once it is triggered it just counts when the it gets tripped, but only when going really fast. It is missing all of the slow trips. But when having the refresh rate at 1 isn't that the fastest it will go. It is reading too slowly. So using the Palaniv side of the code, is there any way to speed it up. This is what I used.


The code which i have shared is nothing to do with timing (Fast/Slow), The timing is purely depends on your Data Acquisition part and your wait time.

 

Still you are not clarifying your use case. When do you want to Increment the count (For every value >10.5 or whenever there is a transition from 10.5 to Lesser and Lesser Value to 10.5).

 

IMHO:People here are to help the new learners to Understand and do the stuff by themselves so need to be clear on your issue and able to understand the work that we do for you.

----------------------------------------------------------------------------------------------------------------
Palanivel Thiruvenkadam | பழனிவேல் திருவெங்கடம்
LabVIEW™ Champion |Certified LabVIEW™ Architect |Certified TestStand Developer

Kidlin's Law -If you can write the problem down clearly then the matter is half solved.
-----------------------------------------------------------------------------------------------------------------
0 Kudos
Message 26 of 27
(471 Views)

Hi Collin,

Can you answer these questions asked by PALANIV? We just need clarification. Try your best to be as clear as possible, use pictures or anything if needed. 

But feel free to try the code that I have attached below.

0 Kudos
Message 27 of 27
(458 Views)