Legacy DAQ Issue

I'm updating a lab setup and switching from some old legacy programs to new NI-DAQMX stuff. After doing the straightforward updates for the new version of Labview, alot of my VI's continue to throw 10401 errors. As I understand it, this is because they're still using the traditional DAQ driver. Since I have a lot of VI's calling things like "AI Acquire Waveform (waveform).vi" I need to make a lot of replacements. Is there an easy way to use the DAQ assistant to generate code to replace legacy functions? Has anyone seen any documentation that links old DAQ functions with replacement DAQMX stuff? I have a lot of old DAQ stuff to replace and little idea about how to even start.

Hi,
See here http://zone.ni.com/devzone/cda/tut/p/id/4342 also http://zone.ni.com/devzone/cda/tut/p/id/5959#toc1.
Hope this helps.

Similar Messages

Import Fail crm 2011 to crm 2013 Legacy component issue

Hi All
We are getting issues during organization import from crm 2011 to crm 2013 , the error is
"We have detected the presence of legacy component(s) during upgrade, these components are not supported in Dynamics CRM 2013. Please refer to upgrade log file C:\Users\Administrator\AppData\Roaming\Microsoft\MSCRM\Logs\LegacyFeatureCheck.xml
for more information."
when we check log file it shows the error "ISV folder under CRM Website contains one or more files"
Even we removed everything from ISV folder , Iframe urls from app , solution which is using ISV urls ,plugins and custom workflows but still the error is same
Please help to resolve this issue .
Thank you
Sharique

Hi,
Please refer below blog having details about "Removal of the 2007 Endpoint and Legacy Features"
http://blog.simonjackson.info/2013/07/whats-changing-in-crm-2013-from-sdk.html
The following legacy Microsoft Dynamics CRM 4.0 features will be removed or will no longer be supported in the next major product release:
ISV folder support for custom web applications
Microsoft Dynamics CRM 4.0 plug-ins
Microsoft Dynamics CRM 4.0 client-side scripting
Microsoft Dynamics CRM 4.0 custom workflow activities
Also you can download a tool that can detect legacy feature on your server
http://go.microsoft.com/fwlink/p/?LinkID=309565
Entire documentation is available at below article.
http://msdn.microsoft.com/en-us/library/dn281891.aspx
Hope this helps.
Ajay Chawla

MSI-6380E: IO-APIC MPS v1.4 and bios v5.4 USB legacy support issues

I am wondering why the linux kernel says there's
something strange with the SMP table and why flashing
the bios up to version 5.6 to solve low RPM issue with
my TT Volcano CPU fan took me to the point of flashing
back to 5.4 for unattended bus USB hangup! ;(
Please note the following error message under
6380E-v5.6:
usb.c: USB device not accepting new address=3
(error=-110)
will these issues will be eventually fixed or should I
change my motherboard hoping to find a serious implementation for USB and MPS standards on a newer board?
Why the IO-APIC table isn't recognized as a standard
Intel MPS 1.4 table?
found SMP MP-table at 000fb920
hm, page 000fb000 reserved twice.
hm, page 000fc000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f7000 reserved twice.
On node 0 totalpages: 65520
zone(0): 4096 pages.
zone(1): 61424 pages.
zone(2): 0 pages.
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: VIA Product ID: VT5440B APIC at: 0xFEE00000
Processor #0 Pentium(tm) Pro APIC version 17
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-19, 2-20, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 19.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 00178002
....... : max redirection entries: 0017
....... : PRQ implemented: 1
....... : IO APIC version: 0002
WARNING: unexpected IO-APIC, please mail
What has been changed in USB legacy support between
v5.4 and v5.5? :O

255MB LOWMEM available.
found SMP MP-table at 000fb920
hm, page 000fb000 reserved twice.
hm, page 000fc000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f7000 reserved twice.
On node 0 totalpages: 65520
zone(0): 4096 pages.
zone(1): 61424 pages.
zone(2): 0 pages.
Intel MultiProcessor Specification v1.1
Virtual Wire compatibility mode.
OEM ID: VIA Product ID: VT5440B APIC at: 0xFEE00000
Processor #0 Pentium(tm) Pro APIC version 17
I/O APIC #2 Version 2 at 0xFEC00000.
Processors: 1
Kernel command line: auto BOOT_IMAGE=Linux ro root=307
Initializing CPU#0
Detected 1100.067 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 2195.45 BogoMIPS
Memory: 255996k/262080k available (1788k kernel code, 5696k reserved, 636k data,
112k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: Common caps: 0383fbff c1cbfbff 00000000 00000000
CPU: AMD Athlon(tm) Processor stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000080
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-19, 2-20, 2-22, 2-23 not connected
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 18.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 00178002
....... : max redirection entries: 0017
....... : PRQ implemented: 1
....... : IO APIC version: 0002
WARNING: unexpected IO-APIC, please mail
to linux-smp[...]
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 001 01 0 0 0 0 0 1 1 39
02 001 01 0 0 0 0 0 1 1 31
03 001 01 0 0 0 0 0 1 1 41
04 001 01 0 0 0 0 0 1 1 49
05 000 00 1 0 0 0 0 0 0 00
06 001 01 0 0 0 0 0 1 1 51
07 001 01 0 0 0 0 0 1 1 59
08 001 01 0 0 0 0 0 1 1 61
09 001 01 0 0 0 0 0 1 1 69
0a 000 00 1 0 0 0 0 0 0 00
0b 000 00 1 0 0 0 0 0 0 00
0c 001 01 0 0 0 0 0 1 1 71
0d 001 01 0 0 0 0 0 1 1 79
0e 001 01 0 0 0 0 0 1 1 81
0f 001 01 0 0 0 0 0 1 1 89
10 001 01 1 1 0 1 0 1 1 91
11 001 01 1 1 0 1 0 1 1 99
12 001 01 1 1 0 1 0 1 1 A1
13 000 00 1 0 0 0 0 0 0 00
14 000 00 1 0 0 0 0 0 0 00
15 001 01 1 1 0 1 0 1 1 99
16 000 00 1 0 0 0 0 0 0 00
17 000 00 1 0 0 0 0 0 0 00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:17-> 0:21
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:18
IRQ11 -> 0:16
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
.................................... done.
mmm X(, look at this, please:
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 89
PCI: No IRQ known for interrupt pin A of device 00:11.1. Probably buggy MP table.
VP_IDE: chipset revision 6
I don't get such complaint using MPS v1.4 on this KT3 Ultra motherboard

How do I update a program written for a Legacy DAQ into one for a USB DAQ?

I am trying to rewrite a program, replacing all of the AI Waveform Scan and AO Update Channel VIs in it with DAQmx VIs. This seems to be the only way for the USB DAQ to respond to the program and not get any errors. I was just hoping for some help in how to replace those VIs with updated DAQmx ones. Attached is the part of the program that I am working on. There is a slight error because of some changes I have made, but the gist of the program is still there.
Thanks!!
Attachments:
DAQdriver.vi ‏52 KB

What I would suggest is that in either your init state or outside the loop, create two separate tasks for the analog in and the analog out. This means using separate DAQmx Create Channel, DAQmx Timing, DAQmx Start Task, etc. Then, you would have the tasks in your shift registers and pass just the appropriate task to either a DAQmx Write or DAQmx Read. No need to pass channel or device. In the End state, you would add a DAQmx Clear Task for each.

Exchange 2013 - 2007 coexistence legacy namespace issues

Got an odd config here. Exchange 2007 CCR mode co-existing with split role 2013 servers over 2 Data Centers. Each DC has its own subnet so DAG has 2 IPs. New Certificate purchased with extra legacy namespace and loaded onto ISA and F5 as well as the
exchange servers.
I can send and receive from the Exchange 2013 servers. But I'm struggling to deploy the legacy namespace
Here's where it gets ugly. The client wants to continue (short term) to put legacy.company.com through ISA2006 servers and 2013 traffic through F5 load balancers. On the f5 side the path goes through a firewall then an f5 to the mailgateway
When we cut over to legacy (dns changes etc) OWA suffered intermittent Internal 500 errors. Active sync had to be pointed to webmail to work (we had it set blank as per Steve Goodmans recommendation) and Outlook Anywhere had no connectivity.
Urls were set correctly
Outlook Anywhere -> webmail.company.com
Autodiscover -> webmail.company.com
WebServices -> legacy.company.com
OWA -> legacy.company.com
OAB -> legacy.company.com
UM -> legacy.company.com
ActiveSync -> legacy.company.com
This is our 4th attempt to get this working. We can only work in the small hours so we are all fairly tired. Pointers anyone?

Hello,
Do you mean when the user access mailbox from internet, the load balancing will not occur? If so, I recommend you check your configuration as the following article:
http://technet.microsoft.com/en-us/library/aa997148.aspx .
The user of ISA Server load balancing will eliminates the need for setting up the load balancing cluster on the exchange server CAS side.
If I have any misunderstanding, please free let me know.
Cara Chen
TechNet Community Support

Can I install an older version of traditional DAQ that support legacy DAQ with DAQmx for support of a new card?

I have a LabPC+ that works fine, but is not supported in the latest versions of NI DAQ. I also have a 6024E that I would like to use. I know that the version of DAQ that supports the LabPC+ also supports that 6024E, but I would prefer to use the latest DAQmx with this. Is this possible?

Hi Brain:
Doesn't look like it, the PC+ will only go up to 6.9.3 tradition DAQ
http://www.ni.com/support/daq/versions_legacy.htm
while the 6024E will go up to 7.4.1 traditional or 7.5mx or 8.0mx, dependiong on OS.
http://www.ni.com/support/daq/versions_pci_pxi.htm
I assumed these cards were PCI based.
I am not a DAQ expert, so hopefully someone can verify this.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Simultaneous Measurement with 6120 card using DAQ legacy

I'm incorporating a PXI-6120 card into our test system for simultaneous measurement. We currently have a wrapper built in VB for the Ni-DAQ legacy driver. There's a pretty tight deadline on getting this integrated and since the 6120 card is compatible with the Legacy driver, I'd like to use that instead of DAQmx. I've been looking through the AI read commands in Ni-DAQ legacy and they all seem to call out a single channel, so there would be a time delay in geting all 4 channels measuring simultaneously. I'm unable to find a command that selects specific channels or even all of the analog input channels to begin measuring at the same time (true simultaneous measuement). I've believe I saw this capability with DAQmx. How is this done with DAQ legacy?

I haven't worked in PXI, but have done a lot of VB6 programming with the legacy DAQ stuff. Sounds like what you need to do is a SCAN - which is multi-channel. There are different ways of doing this depending on whether you want to start the daq device collecting data and then have your app do other stuff, coming back periodically to check if the data collection is done. Or if you're simply looking to grab a quick set of readings, check out the Scan_Op command.
I believe in most (all?) scans you need to collect more than one reading per channel - but you can do as few as 2 per - then average them.
Hope this helps!
Rick

Does labview run time engine 8.6 LVRTE86std.exe supports DAQ?

Due to the LONG TIME required to build an installer with exe, and this kind of DAQ issues http://forums.ni.com/ni/board/message?board.id=170&message.id=324343&query.id=1071542#M324343
I want to just give the user the Labview run time engine 8.6 LVRTE86std.exe http://joule.ni.com/nidu/cds/view/p/id/1101/lang/en , and ask them to copy paste the exe.
But does the LVRTE86std.exe contains all the necessary dependency for DAQ? Including the Sound and Vibration dependencies required for DAQ? Is there some document I can look up to see whether LVRTE86std.exe supports DAQ and I dont have to build an installer of my own?
Solved!
Go to Solution.

No, the runtime does not include DAQmx. It does not include any hardware drivers. That is discussed in numerous posts.

LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program

Hello!
We have the following problem:
LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program
We freshly installed LabView 8.2 (2006) and NI-DAQ 7.4.4 on a PC running Windows XP (Service Pack 3). We built a larger vi that remotely controls a traditional NI-DAQ card (AT-AO-10) on a second PC via NI-VISA 5.0.3. We were successfully running this program until a power failure caused the first computer to crash. After this crash we were unable to start the program again: LabView freezes while loading the vi. LabView itself can be started but freezes when adding I/O operations from the NI-DAQ palette to a block diagram.
We have tried to re-install NI-DAQ 7.4.4, but it did not help. We then re-installed all NI software, but still no improvement. In the end we decided to reinstall ALL software, first Windows XP, then LabView and finally NI-DAQ 7.4.4. This worked. However, after a few days of running the program we had to abort LabView via Windows Task manager and afterward we again experienced the same problem as before: LabView freezes when loading the program.
Obviously, we cannot afford to reinstall Windows every time. Are there any known Windows XP / NI-DAQ issues that might cause the freezing of LabView? We would be very grateful for any idea.
Best regards,
Matthias

Hello Sprice,
Browse the shipping examples according to “Directory Structure” and then select
DAQ to find the Traditional DAQ examples.
There a lot of examples that are written for counters (Counter >>
daq-stc.llb >> Count Edges (DAQ-STC).vi).
What kind of signals are your photons creating? Are they TTL compatible at a certain
frequency? You don’t care about overwriting
your buffer?
Respectfully,
Rob F
Test Engineer
Condition Measurements
National Instruments

Losing communication with DAQ devices - help greatly appreciated

All,
I have been working on a VI whose function is the following:
- Acquire data from three sources
     - A block of eight displacement sensors connected via RS232 (using a USB adapter)
   - An NI-USB 6210 card measuring voltages across eight batteries
   - Another NI-USB 6210 card measuring voltage across four load cells (these correspond to batteries one through four).
   - Data acquired at 1 Hz, written at 0.2 Hz (no buffer - simply writes one fifth of data recorded)
- Open/close a relay board based on certain inputs
- Provide basic UI functionality to control data manipulation, display data, and write data to text files
- Write data to text files
We have run four tests with this VI. Each test runs for anywhere from 24 to 48 hours. During three of these four tests, we have lost connection with one or both of our NI DAQ cards. I have attached one of the output files - notice that in the 'Current (mA)/Voltage (V)' and 'Load (N)' columns, at a certain point on of the cards starts reading 'NaN', followed soon after by the other card. Note that this has happened on two different computers, one laptop and one desktop, both of which had hibernate/sleep disabled.
For your reference, I have attached the VI. This VI will not run as there are some subVIs that I have not included; these subVIs do not do anything critical to the execution of the program. The program generally runs as follows:
- Initially, a subVI runs that aids the user in selecting the appropriate COM port and USB devices.
- The VISA device and DAQ cards are initialized, all relays are opened, variables are initialized
- In parallel, there are two producer timed loops, one consumer for loop and an event loop
   - One producer loop continuously acquires voltage data from both DAQ cards. When the loop is over, basic DC voltage values are taken from all samples in each buffer, and the values are enqueued
     - One producer loop acquires one reading per loop from the displacement sensor (via a VISA Write -> VISA read), and the response string is enqueued.
   - The consumer loop runs at a similar timing as the producer loops (blocked using queues). It manipulates, displays, and records acquired data. It also opens relay channels if the corresponding displacement values are greater than a set threshold.
     - The event loop opens text files for writing when a button is depressed, as well as performing basic tasks such as clearing graphs, etc.
What is the cause of this issue? What am I doing wrong? This error is preventing us from running tests at our company. Any help is greatly appreciated.
Thank you,
Bryan
Attachments:
DAQ issue VI.vi ‏124 KB
sample output.txt ‏1230 KB

Wayne,
Thanks for your reply. Unfortunately, my knowledge is limited in this area. We are using an ADU208 USB relay from Ontrak (information here: http://www.ontrak.net/ADU208.htm). We are using the bundled subVIs to open/close each channel of the relay depending on the acquired data. How could this relay board affect the DAQ communication?
It may also be important to note - I have tried to make this VI so that all devices need not be used all of the time. That is, sometimes we choose to not use the relay, sometimes we choose to not measure load, and sometimes we choose not to measure current. This means that we do not always have the same hardware connected, but the software runs the same and deals with the resulting errors appropriately (hopefully). The previously attached output file is from a test where the relay was not connected, however the relay commands were still run (and presumably threw errors).
Thanks again for your help
Bryan

VIs worked in LabVIEW 2009 but do not work in LabVIEW 2010

The VIs were originally written in LV 7.1 but then compiled in LV 2009 and saved. These VIs worked fine on Windows XP machine.
Unfortunately, the XP machine was crashed and I am trying to run these VIs in LV 2010, with windows 7, 32 bit.
I have installed traditional DAQ drivers (latest version, 7.5) alongwith DAQmx (version 9.8).
We use these VI to control the vacuum valves, using PCI 6503.
To initiate we first use a VI that reset the valves and the PCI card. The name of the first vi is: portconfig.vi This vi uses port config and port write VIs. I see the error 10401 from port config vi, when I run step by step (i.e., sequence 1). However, the VI runs but not doing any actual work.
The second VI that depends on first VI, and therefore the second VI is also not working. on this VI we have buttons (representing valve) and when we click on them, the valves should shut off or open, but nothing happens in LV2010. the same VIs worked in LV2009!
PCI 6503 card is defined under devices and interfaces in MAX. It is not defined under legacy DAQ devices. When I test PCI 6503, it works.
I am attaching both the VIs (there are in QuadMain.llb). I dont know how to get the actual VI from the harddisk...
first open portconfig.vi
then open Control Panel.vi
there are global variables used in Control Panel.vi, there are listed in Valve Global.VI, which is in globals.LLB (second attachement).
I really appreciate if someone can convert these VIs for LV 2010.

Jpdas06 wrote:
Yes, I am doing that. But this is holding up the experiments. So I thought an easy fix for now and then once the work load goes down i can concentrate on changing the port config.vi using DAQmx.
I would really appreciate if you or someone can provide me steps for listing PCI 6503 as both types in MAX.
Thanks again.
You should be able to see the DAQ card in both driver interfaces DAQmx and Traditional DAQ. I just checked on one of out test fixtures. We have MAX 5.6, DAQmx 9.8 and Traditional DAQ 7.5 on Windows 7 32-bit. We use LabVIEW 2013 executables on this PC, but this really doesn't matter.
I believe the only exception, when you don't see cards in both drivers, is when the card is supported in DAQmx only. But in your case this card (PCI 6503) is supported by DAQmx and TDAQ.
I had some issues before renaming devices in Traditional DAQ. If you have more than one card, the device names not always match in both drivers. You could have one card for example as Device 2 in TDAQ and then as Dev 4 in DAQmx.
I would uninstall and install again the Traditional DAQ driver. I never added cards manually to the drivers. This should happen automatically.

RDA and MAX

Dear community,
I have a short question on a strange behavior of vi containing legacy DAQ functions.
I need to start NI MAX first before launching Labview and vi files, otherwise
loading hangs up at /DAQ/lvdaq.dll. Any traditional DAQ channels cannot be created on the front panel,
any data acquisition vi cannot be used.
Also, without staring MAX first, I cannot open Labview example vis in "daq" folder.
It seems somehow that lvdaq.dll cannot be loaded properly.
However, if I delete a legacy device created RDA needed for data acquisition, then everything works without any issues.
Would you tell me how to fix this problem?
Thank you for your time and kind advice.
Sugar7

Hello
Thank you for your message.
A PCI-6014 DAQ card is on a remote computer and I'd like to access to this card through RDA for a simple analog input measurement.
I could recognize this card on a client computer and a test on MAX was also fine.
If I close MAX and try to open a Labview vi file which contains NI-DAQ functions, loading always hangs up at /DAQ/lvdaq.dll.
In another example, If I create a NI-DAQ channel on a blank front panel, Labview itself got frozen.
However, if MAX is launched first, then these problems never show up.
My guess is that loading lvdaq.dll has a problem.
If you need more info to fix this issue, please let me know.
I appreciate your kind support.

Global tasks (handler)

I have programmed legacy DAQ cards like the 6024 using LabWindows CVI for 15 years. Now I have to use a USB 6218 and DAQmx. I want to use a counter to measure my loop time. If I start a task (like start the counter) in one subroutine call I can not call that same task in another subroutine call (like read the counter). The task handler ID seems to only be a local variable. The task or taskhandler can not be made a global variable. If the create, start, read, stop, and clear tasks are all in the same subroutine, everything works. I hope I am stating this problem correctly, I am an engineer who knows some programming, not a pure programmer.

RobertoBozzolo,
First of all, thank you kindly for your quick response and help. I think you are onto the source of my problem. I have attached some information to explain the code. The program is very large. I thought I have defined the Task Handler at the system level with a static definition. But when I compile the code, I get a message that the task handler is undefined.
I hope I have explained my code in the attachecment well enough for you to see the problem.
I have to share with you that I have never used task handlers. Somehow, since CVI was started I have gotten by without out it. Right now I am not a fan of the DAQmx approach to data acquisition and control. I used to be able to use simple easy IO or legacy library routines that were very straight forward and used a minimum of code. I also tried defining the tasks in Measurement and Automation Explorer, but I could not get those to work also. I thought it was just me but I talked to two other engineers who also dabble in programming and they too are not happy with the improvement.
I think the issue is that we have to be better programmers. Instead of just engineers who use the CVI tool.
Again, I want to thank you for any help that you can offer.
Mike
Attachments:
Taskhandler issue.docx ‏22 KB

Exception Type: EXC_BAD_ACCESS (SIGBUS) FCP projects gets corrupted?

My FCP is constantly crashing when rendering a project I'm working on.
Seems like these questions about project corrupting are popping here and there.
Will FCP have the plague of Premiere of project corrupting which stalled project finishing badly?
http://discussions.apple.com/thread.jspa?threadID=1496985
http://discussions.apple.com/thread.jspa?threadID=1517330
http://forums.creativecow.net/readpost/8/987100
http://discussions.apple.com/thread.jspa?messageID=7184376
http://discussions.apple.com/message.jspa?messageID=7189036

My problem seems to be solved by making a new account.
Old account was made in Tiger and maybe there is some legacy/compability issues with accounts in .4 & .5.
This might also help others, if their accounts were made in Tiger.

How to configure a continuous pulse generation that doesn't end after the VI exits with DAQmx?

Hi,
I'm just learning the DAQmx and I have run into a problem.
With the legacy DAQ API I could configure a counter to create continuous pulses and
when I needed change the freq or duty cycle, I would just call the the configuration function
again. The pulses were generated even after I closed LV, so it was all in the hardware.
Now, with DAQmx api, it seems that this is not possible. I read a forum post saying that
LV will end the pulse generation after the VI exits. Is there a workaround for this?
I could ofcourse create a LV thread for this, but I liked the old one better
It was simpler and I didn't need to worry about threads so much.
All LV operations are going to be inside a DLL that is called from outside of LV, so I can't
use LV threads in a simple way, e.g. putting things inside a while loop. Just that you'll
know why I wan't to avoid using the threads.
Thanks.

It is possible to achieve this behavior using the DAQmx API by using the DAQmx Create Task VI to explicitly create the task (rather than relying on DAQmx Create Channel to do it implicitly) and setting the AutoCleanup attribute to False. This method prevents LabVIEW from automatically clearing the task when your VI (or the function you'll be exporting to your C .dll) finishes executing. The disadvantage is that you might accidentally "leak" a task if you're not careful. In order to stop the pulse generation on command, you can either reset the device or somehow store the task name you created and come back later to call DAQmx Stop and/or Clear Task.
Here's how you would start the generation:
...and how you could come back and stop it later, using the task name you created:
Hopefully this helps-
Message Edited by Tom W [DE] on 11-16-2007 07:54 AM
Tom W
National Instruments
Attachments:
autoCleanup.JPG ‏17 KB
clearTask.JPG ‏4 KB

Legacy DAQ Issue

Similar Messages

Maybe you are looking for