NIDAQmx Base and Cocoa: Creating a NIDAQ task stops my application from quitting

[Tangle]

Dominik,

Today tested exit() from the main thread and [NSThread exit] from both the sampling and the main thread.

All still hung.

The stack traces from both tests look similar to the others (after only a quick look).

Thanks

Lee.

[Dominik-E2]

Hi Lee,

We have filed a formal report documenting the behavior and submitted it to R&D. Unfortunately, we do not have a work-around for the behavior nor a set timeline as to when it will be fixed. The best way to know when it is fixed would be to check the bug fixes in the Readme we release with every new version/patch of the driver. I want to apologize for the inconvenience it is clearly causing and would encourage you to keep trying to find a fix. If you do manage to find a work-around, please post it to our forums so other users can benefit as well. Thank you again for all your help and the numerous files you posted that helped us reproduce the hang.

Regards,

[NIthan]

Hey Lee,

See the post I made here. Basically this is a known issue with any LabVIEW built framework being called from a cocoa app. Since DAQmx Base is a LabVIEW built Framework, it is affected by this bug. Unfortunately, there is no good workaround right now asside from running DAQmx Base calls in the main thread and having to wait a long time when it first loads. This issue will most likely be fixed in the next release of DAQmx Base, currently scheduled for August 2013.

Nathan H.

[Tangle]

Thanks for the update.

I wish you would inform you sales engineers though.  I bought my NI hardware for this specific purpose on you sales engineers word that it would do what I wanted.  That was in May 2011.  When I showed your sales engineers that NI has recognised the issue on the forums and that the hardware cannot do what I want, I am told that officially my applciation is within the specs.

[Steven_T]

Hello,

Technically this issue became known because of the information that you provided. In May 2011 we did not know the problem existed.

Thanks,

Steven T.

[Tangle]

Yes I reaslise this.  However, your Sales eningeers at this point (the issue has been known for 2+ months) do not recognise this issue.

This also follows on from a previous issue, although I cannot find the forum topic.  When I bought my hardware it was known by NI that NIDAQmx Base did not work (at all) on the current (at the time) version of the Apple operating system.  You sales team refused to recognise that issue as well.  It was only after the current version of NIDAQmx Base was relised that I could begin attempting to use my hardware, and I then discovered this exisitng issue.

These two issue combined mean that I have never been able to make use of the NI hardware that I purchased.  This is now the second time I am wating for a NIDAQmx Base update to turn my expensive paperweights into useful DAQ hardware.

I know that this nice disconnect you have beetween tech support and sales means that you can avoid the local laws requiring you to reverse my purchase.  However, it is terrible customer service and I would not risk NI hardware again.

[Tangle]

Ah, I found the thread.   I did not realise my NI profile tracked them.  I see you were a contributor, providing notification that the issue was fixed.

EDIT:  http://forums.ni.com/t5/Multifunction-DAQ/DAQmxBaseCreateTask-gt-Bus-Error-10/m-p/1889103#M69399

[NIthan]

Hey Lee,

I sent you a private message regarding this issue. We would like to try to refund you for the products you've purchased from us. Reply to that PM if you are interested.

Nathan Hickey