LAVA Forums Buy cool LAVA gear Forums RSS Feed

Welcome Guest ( Log In | Register )

Tags
This content has not been tagged yet

> Related links

Visit our LabVIEW Wiki Hardware Portal


 
Reply to this topic Start new topic
> two conter syncronization on PCI 6221, Gear ratio measurement
Max1971
post Jun 25 2008, 01:06 PM
Post #1


I've come back for more.


Member
Posts: 2
Joined: 30-September 05
Member No.: 3120
Using LabVIEW Since:2008
LV:7.1.1 ,8.5.1 ,.
Italy Nothing Selected Nothing Selected


Hello to everybody,
I'm trying to make a gear ratio measurement and I need two encoders to read gearbox input and output position.
The problem is to syncronize both start and read operation without using external signals and, hopefully, usign only Daqmx commands.

Attached you will find an example of what I'm trying to do.
I've found many examples on the net regarding synconism between AI, AO, AI and Counter, etc. but nothing about two counters.
Thanks a lot for answers.

This post has been edited by Max1971: Jun 25 2008, 01:07 PM
Attached File(s)
Attached File  esempio.vi ( 108.08K ) Number of downloads: 58
 


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post
Ad
post Jun 25 2008, 01:06 PM
Post #















Tags
This content has not been tagged yet
Go to the top of the page
Quote Post
jdunham
post Jun 25 2008, 06:40 PM
Post #2


Very Active
***

Member
Posts: 155
Joined: 6-March 05
From: Mountain View, CA
Member No.: 1764
Using LabVIEW Since:1994
LV:8.5 ,. ,.
United States us_california Nothing Selected


QUOTE (Max1971 @ Jun 25 2008, 06:06 AM) *
I've found many examples on the net regarding synconism between AI, AO, AI and Counter, etc. but nothing about two counters.


You are on the right track.

I don't see why those examples shouldn't help, though I could be more specific if you had links to those examples. The main reason DAQmx is better than the old driver is that the same functions work whether your tasks are AI, AO, or Counters. Int the DAQmx example ...\LabVIEW 8.5\examples\DAQmx\Synchronization\Multi-Function.llb\Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample Clock.vi,
you can see that the counter channel starts counting based on a trigger from another task. You should be able to use that same subvi (...\vi.lib\DAQmx\configure\trigger.llb\DAQmx Start Trigger (Digital Edge).vi) to start your counter task from another counter task's start or input signal.

Good luck.


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post
Max1971
post Jun 26 2008, 08:01 AM
Post #3


I've come back for more.


Member
Posts: 2
Joined: 30-September 05
Member No.: 3120
Using LabVIEW Since:2008
LV:7.1.1 ,8.5.1 ,.
Italy Nothing Selected Nothing Selected


QUOTE(jdunham @ Jun 25 2008, 08:40 PM) *
You are on the right track.

I don't see why those examples shouldn't help, though I could be more specific if you had links to those examples. The main reason DAQmx is better than the old driver is that the same functions work whether your tasks are AI, AO, or Counters. Int the DAQmx example ...\LabVIEW 8.5\examples\DAQmx\Synchronization\Multi-Function.llb\Multi-Function-Ctr Retrigg Pulse Train Generation for AI Sample Clock.vi,
you can see that the counter channel starts counting based on a trigger from another task. You should be able to use that same subvi (...\vi.lib\DAQmx\configure\trigger.llb\DAQmx Start Trigger (Digital Edge).vi) to start your counter task from another counter task's start or input signal.

Good luck.


Probably I don't have the right basefloor about NIdaq and timing/triggering features, but I don't understand exactly what I have to do...


Tags
This content has not been tagged yet
Go to the top of the page
+Quote Post


Reply to this topicStart new topic

 




Time is now: 7th October 2008 - 07:39 AM