07-27-2020 01:24 AM
Can anyone help me? I have a project to measure rpm using Arduino and fc-30 encoding, is there an example so that the data from the hardware can be displayed in labVIEW with LINX?
07-27-2020 01:59 AM
Hi yog,
@yog30 wrote:
I have a project to measure rpm using Arduino and fc-30 encoding
Maybe you should explain the meaning of "fc-30 encoding"…
@yog30 wrote:
is there an example so that the data from the hardware can be displayed in labVIEW with LINX?
There are several examples to display data, measured by Arduino, with LabVIEW.
What have you tried?
Where did you fail?
Have you tried to use the Arduino IDE instead of LINX and employ the (virtual) COM port of the Arduino to transfer data?
07-27-2020 02:12 AM
Thank Gred,
The working principle of the FC-03 encoding sensor. When something comes in "opto interruptor" gap, DO output will produce HIGH or 5V logic (leds) green DO will die). While under normal conditions, DO will produce logic LOW (green led DO live).
I have listed my project below, In this labview program I can only search for chopped. What I want the program to look for counts per minute or rotation per minute (RPM).
07-27-2020 02:22 AM - edited 07-27-2020 02:26 AM
Hi yog,
@yog30 wrote:
I have listed my project below, In this labview program I can only search for chopped. What I want the program to look for counts per minute or rotation per minute (RPM).
Why do you need two local variables and a case structure? Why do you need orange DBL when you want to count integer pulses?
You already know the "count", so all you need to do is to calculate the difference between current "count" and some previous "count" value and divide by the time elapsed in between!
Simple solution:
07-27-2020 02:34 AM
Hi Gred,
I use a case structure because the data is in the form of analog read, the values are 0 and 5 so I use it to get true false and my true value is chopped and displayed using DBL.
07-27-2020 04:29 AM
Hi Yog30,
Notice that you can do the same thing with less "hidden code" by using a Select node like Gerd shows in his post.
In this way, if the boolean is true then it will add one, and if not it will output the input value.
Then the shift register handles the 'link' between iterations (you could also use a Feedback Node, but I think Shift Registers like in Gerd's example are often clearer).