From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
daqmx terminal probe
BVSmith
Member
05-28-2008 03:13 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I've got a data structure containing a DAQmx terminal and when I probe a wire with this structure the probe number on the block diagram has a gray background and the probe never shows any value when the data passes through (it is always gray).
If I remove the DAQmx terminal from the data structure the probe works properly. Also, in the probe itself, the DAQmx terminal looks more like a string than a pulldown because it has a vertical scrollbar and is much taller than the pulldown in my typedef.
This happens in LabVIEW 7.1.1 and 8.2.1. It doesn't happen in 8.5, but I have to keep with 8.2.1 for now.
Any ideas?
Thanks.
If I remove the DAQmx terminal from the data structure the probe works properly. Also, in the probe itself, the DAQmx terminal looks more like a string than a pulldown because it has a vertical scrollbar and is much taller than the pulldown in my typedef.
This happens in LabVIEW 7.1.1 and 8.2.1. It doesn't happen in 8.5, but I have to keep with 8.2.1 for now.
Any ideas?
Thanks.
Brian Smith
Advanced Light Source
Lawrence Berkeley National Laboratory
Advanced Light Source
Lawrence Berkeley National Laboratory
amcolosk
Member
05-28-2008 03:44 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi BVSmith,
Could you add a picture of the problem or attach the VI so those of us visual people can get it? Also what type of data structure is it in? Are you sure that the possible conditions for calling that particular piece of code are completing as expected?
Could you add a picture of the problem or attach the VI so those of us visual people can get it? Also what type of data structure is it in? Are you sure that the possible conditions for calling that particular piece of code are completing as expected?
05-28-2008 05:53 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
In the attached GIF you can see that the probe on the constant shows the value has passed through, but the DAQmx Terminal probe is still gray and the probe number on the block diagram is gray instead of yellow.
Brian Smith
Advanced Light Source
Lawrence Berkeley National Laboratory
Advanced Light Source
Lawrence Berkeley National Laboratory
amcolosk
Member
05-29-2008 06:39 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi,
I have been able to duplicate your problem in 8.2. Does the terminal selection still make it to the vi, aka, does it still run properly? It appears to me, that the data is still getting passed through the wire, just that the probes can't display the data.
I have been able to duplicate your problem in 8.2. Does the terminal selection still make it to the vi, aka, does it still run properly? It appears to me, that the data is still getting passed through the wire, just that the probes can't display the data.
05-29-2008 10:53 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I figured it out. I just realized that the probes in LabVIEW are just created from controls (duh) and
there must not be one for the DAQmx terminal so it picked a string probe instead.
I was able to create a new probe from the terminal probe explicitely and it works.
I am curious however. I tried to create a new probe based on an existing one and none of the
DAQmx controls are listed in the list of existing probes, but I can probe (e.g.) DAQmx task name.
So where are those probes defined?
Thanks for listening.
Brian
there must not be one for the DAQmx terminal so it picked a string probe instead.
I was able to create a new probe from the terminal probe explicitely and it works.
I am curious however. I tried to create a new probe based on an existing one and none of the
DAQmx controls are listed in the list of existing probes, but I can probe (e.g.) DAQmx task name.
So where are those probes defined?
Thanks for listening.
Brian
Brian Smith
Advanced Light Source
Lawrence Berkeley National Laboratory
Advanced Light Source
Lawrence Berkeley National Laboratory
05-29-2008 10:55 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
In my previous post I meant:
... was able to create one from the DAmx terminal CONTROL ...
... was able to create one from the DAmx terminal CONTROL ...
Brian Smith
Advanced Light Source
Lawrence Berkeley National Laboratory
Advanced Light Source
Lawrence Berkeley National Laboratory
![Tom_W_[DE]](http://forums.ni.com/attachments/ni/130/2061/1/mean_robot.jpg "Tom_W_[DE]"){kind=avatar}
Tom_W_[DE]
NI Employee (retired)
05-29-2008 11:25 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Brian-
Your findings are exactly correct. LabVIEW was incorrectly using a string control in that probe in LabVIEW 8.2. It wasn't something we could fix in DAQmx, unfortunately, but it was fixed in LabVIEW 8.5 (as you already noticed). FYI- this was originally reported to R&D and fixed under issue #46PFGRMI.
Tom W
National Instruments
National Instruments
