Visit our LabVIEW Wiki Hardware Portal
![]() |
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 ,.
|
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)
Tags
This content has not been tagged yet
|
|
|
|
| Ad |
Jun 25 2008, 01:06 PM
Post
#
|
|
|
Tags
This content has not been tagged yet
|
|
|
|
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 ,. ,.
|
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
|
|
|
|
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 ,.
|
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
|
|
|
|
Similar Topics
| Topic Title | Replies | Topic Starter | Views | Last Action | |||
|---|---|---|---|---|---|---|---|
![]() |
1 | pallen | 714 | 13th June 2007 - 03:12 PM Last post by: Ton |
|||
![]() |
7 | Anders Björk | 1050 | 12th November 2007 - 09:10 PM Last post by: george seifert |
|||
![]() |
4 | James P. Martin | 787 | 1st July 2008 - 01:59 PM Last post by: MotionGuy |
|||
![]() |
5 | Viswanath | 606 | 31st July 2008 - 11:30 AM Last post by: djolivet |
|||
![]() ![]() |
| Time is now: 7th October 2008 - 07:39 AM |