LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Digital input to rpm

Solved!
Go to solution

Someone please help me with this... Smiley Sad

0 Kudos
Message 11 of 25
(2,990 Views)

@ashnu wrote:

Thanks all for the reply : Smiley happy:

 

@


You really only need to click the "Device Pinouts" button in MAX

Capture1.PNG

to find PFI8/P2.0 is CTR0 SOurce and on pin 37

Capture.PNG

Which puts it right here on the BNC 2110:

Capture.PNG


"Should be" isn't "Is" -Jay
0 Kudos
Message 12 of 25
(2,965 Views)

This is the properties I am able to see with wat u suggested with Creating counting task with frequency.. 

Spoiler
 

 

0 Kudos
Message 13 of 25
(2,958 Views)

I am not able to see any of those values of M, B to be inserted here!

0 Kudos
Message 14 of 25
(2,957 Views)

@ashnu wrote:

I am not able to see any of those values of M, B to be inserted here!


From the DAQ Wizard

See that "Custom Scaling" Button Pull it down select "Create New..." Select Linear as the type and you get to this screen

Capture.PNG

M is "Slope" B is "Y Intercept" Type RPM in the Scaled units Box


"Should be" isn't "Is" -Jay
Message 15 of 25
(2,943 Views)

Thank you sooo much for such a detailed and clear explanation. But unfortunately I am not getting any signal when I rotate the turbine 😞

0 Kudos
Message 16 of 25
(2,933 Views)

I am very much sure about the proper connections with the hardware! Because it works very well with the digital Output (the LED glows when the turbine runs) but where as when I select counter input then I don't see any signal coming from DAQ Assistant., I have just connected graph indicator for this, but I dont see anything!!!!!

0 Kudos
Message 17 of 25
(2,923 Views)

Hey guys, 

 

I am back with the digital input as I am not getting any signal in counter input. So I used the VI given by Hooovahh.

 

I am having a problem at counting the number of rising edges. I saw the summation output was just 0 or 1 every time I ran the program when the turbine was running. The actual RPM reading in the instrument was 500, whereas I got just 0 or 30 rpm. 
How to rectify the problem near the counting of rising edges?
 
Your replies matters the most for me 🙂
0 Kudos
Message 18 of 25
(2,893 Views)
Solution
Accepted by topic author ashnu

So there was an issue with my VI but it sounds like you are having several troubleshooting problems and I suggest becoming more familiar with probes, to inspect the data to see where the problems is.  The VI I posted had an Or when it should have had an And in the compound arithmatic function.  So now the compound arithmatic should show rising edges where the value was low, then became high.  It then counts the number of times it sees this rising edge and does the rest of the math like normal.

 

Start by seeing if the data read from the DAQ is what you expect.  Then see if the number of edges are what you expect.  Keep going until you find where the data you get, isn't the data you expect and figure out why.

Message 19 of 25
(2,864 Views)

Thank a lot for explaning me everything soo cleary and with patience. 

 

I did as you said and I came to kow that I am getting from DAQ assistant either all 0s or all 1s for the given samples (Ex: for 1000 samples, I get all 1s or 0s in 1000x1 array). If I am not wrong, I am suppose to get a mixture of 0s and 1s within the 1000 samples right? 

0 Kudos
Message 20 of 25
(2,844 Views)