10-01-2013 09:58 PM
Hi all,
What I want is to update a high refresh rate monitor using a hardware clock set exactly at 120 Hz. For that, I think that the easiest y to configure a counter to count digital edges and register an arbitrary function to the hardware event. The arbitrary function would read te counter value (or just increment a variable) and update the screen depending on the value (actually I want to display a revolving clock).
The problem is that I can't get my program to work with a NI USB-6215, because of hardware incompatibility with hardware timed edge detection (or something like that). Any idea to do this, hopefyllu using only one counter?
I also have a PCI-4461 and PCI-6071E
Thanks!!
10-02-2013 09:12 AM
Hi,
What's the problem about using the PCI-6071E ? (2 counters) I guess that it should work ! 🙂
10-02-2013 01:03 PM
10-03-2013 08:07 AM
I have tried to configure a simulated PCI-6071E device in "HW-timed single point", and it seems to work (no error returned by the DAQmx function...and as you said previously, it doesn't work for USB-6215).
10-03-2013
08:13 AM
- last edited on
08-09-2024
05:52 PM
by
Content Cleaner
Another point is that you will need to use counter output (and not counter input !), as explained here :
10-03-2013 02:27 PM
10-03-2013 03:55 PM
10-04-2013 02:45 AM
While I cannot give you any help on your original question, I'm pretty sure that you cannot use Config_DAQ_Event_Message (which is part of Traditional NI-DAQ package) in a program that uses NI-DAQmx driver, as those environments cannot be mixed in the same application.
Let's see if Julien can share its code with you.
With reference to one of your previous questions, a simulated device permits you to start developing an application making references to hardware resources even without having the actual board installed. Simulated devices mimic the operation of real devices supplying in some case a test signal for you to test the application (e.g. they give you a sine-pattern signal on analog inputs). A code that compiles and runs on a simulated device can be ported to a real board to terminate development with actual hardware and signals, with a reasonable confidence that it does not need deep rearrangments to work correctly.
10-04-2013
03:08 AM
- last edited on
08-09-2024
05:53 PM
by
Content Cleaner
I've not used any "Config_DAQ_Event_Message" for testing. I have used "DAQmxRegisterSignalEvent" and there is no error returned by the function (see both screenshots).
But there is something that I don't understand. "Counter Output" does not seem to have the expected signification. I mean : events are not generated when counter value change.
As explained here, "The Counter Output Event is an event that occurs when the counter reaches its terminal count."
So I begin to wonder wether or not using counter output signal is relevant for your application !
10-04-2013
09:45 AM
- last edited on
08-09-2024
05:53 PM
by
Content Cleaner
Here is a link on LabVIEW forum that maybe can help you :
https://forums.ni.com/t5/LabVIEW/Using-DAQ-to-trigger-non-DAQ-event/td-p/2579469
If counter input does not work with "change detection event" signal, maybe you can try with a digital input, as suggested by Norbert in the last post.
I'm sorry because I try to find some solution but I have not any HW to try it before. So, I might suggest some bad solutions, but it's worth trying. ^^