USB-6009 Daqmx Base 3.3 Cannot creat 2 or more channels on Windows mobile 6

Hello,
I have USB-6009, PDA iPAQ 214, WM6, Daqmx base 3.3, Labview 2009. In order to create new mobile project I use wizard and standart dynamic example: Cont Acq&Graph Voltage-Int Clk.vi. All works ok, but if I add more chanels in VI "Create Channels" or place new VI block and enter "Dev1/ai1", exe on my PDA cannot work correctly. Exception after RUN. I have no idea how build correct application with 3 channels without this exeption... On PC all works. Whay right way to create channels? I attach VI which don't work, for examle. I read daqmxbase cannot support WM6, but 1 channel work ideal!
Attachments:
diagramm.jpg ‏113 KB

Vital000,
I forgot to mention that, yes, Windows Mobile 6 is not supported along side of DAQmx Base. That means you might be able to get some of the same functionality(limited) that you would with Windows Mobile 5, but most likely not 100% functionality. This could explain why 1 channel works and multiple channels do not. I will try and help you out, but as this is not supported my ability to help is limited.
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Similar Messages

USB 6009 DAQmx Deployment

Hi.
I have created a 4 channel differential data logging scope with a NI USB-6009. I would like to deploy this 'easily' to many of my colegues. I have app builder and the ability to build apps, but I would like to include the correct drivers for the 6009 in with the installer (although I have selected NI_DAQmx Core Runtime and NI_DAQmx MAX config support).
For the running of the app, I have created a Task that consists of 4 channels. I would like it for my end user not to have to configure this. Does anyone know how I might acheive this? My experience of deployment is limited.
Many thanks, Alec

Hi Alec,
It's also worth installing DAQmx MAX Configuration Support from the install builder if you still want to be able to modify the tasks from MAX as well.
Best Regards,
Chris
National Instruments - Tech Support

USB-6009 DAQmx parallel devices

Hello, im using a NI USB-6009. And I have to read two analog Inputs, write two analog outputs and two digital outputs. All this in parallel.
It works if I connect them successively, but then the VI is too slow for a good measurement.
So my question is, can it generally work if the dataflow isn't given trough the hole chain, but rather coincidently trough the single parts of the VI?
Now it doesn't work.
Solved!
Go to Solution.
Attachments:
NI_USB_2.vi ‏36 KB

Hi there thanks you very much for the fast answers.
Now it works very well. First I had a error with the AI's but now I take them together and the error is gone.
regards
Moritz
Attachments:
NI_USB_3.vi ‏42 KB

Cannot create pdf in outlook in Windows 8.0 os why

I am using Outlookk 2013 in Windows 8.0 and I cannot create a pdf directly from outlook
on my other computers windows 7.0 and Outlook 2010 I can do this what am i doing wrong or how can i fix this

Outlook is a Microsoft product, so you might search at http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US
If you are using an Adobe program WITH outlook, such as Acrobat, go to the link below to find the Acrobat forum
If you start at the Forums Index http://forums.adobe.com/index.jspa
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right to open the drop down list and scroll

Cannot create HP recovery disc for windows 8.1

i am not able to create hp recovery disc error says cannot create the image media after the burning processing the recovery

Contact HP Support in your country /region to order Recovery Media. Worldwide contact info can be accessed here >>Contact HP
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

After Installation Thunderbird cannot create any e-mailaccount in Windows 8.1

Dear friends,
I have installed Thunderbird on my recently installed Win 8.1 system. TB installes, opens, but then I cannot create anything else but a Newsgroupaccount. The wizard for creating a new, or importing existing e-mailaccounts does not appear at all. The column for Accounts, the list with the Messages shows up, but remains completely blanc not showing anything at all but a Grey field. I've tried copying my Profile folder from my 'old' Linux machine, and the addressbook has been copied allright. But I cannot write any message, as no single e-mailaccount has been created, cannot be created, no matter how i approach this menu.
I have de-installed and removed everything, also in registry, and installed again. No changes. Same problem.
is it possible that my Win 8.1 sytem might be the culprit?
Sincerely, Rudi

Perhaps I should add a screendump of what my Thunderbird 31.2.0 look like. . .

How to create the C++ DLL for Windows Mobile and how to import it in C#

Hi All,
     Please can u guide me for creating DLL on C++ and using it in C#
     1) Steps to create the DLL using C++ for Windows Mobile
     2) And where to place the DLL after builiding to make use of it in my C# project
Thanks in Advance!!!
Thanks & Regards,
Sharan

Hello all,
I know this is an old thread but i have to give it a try ( i am stuck with an almost identical problem but cant solve it since 5 days googling and reading.
I am developing an app for Unitech HT660e which has Win CE. THe app is complete but now i need some more control over the barcode scanner. In order to gain controll i need to use USI.dll which is explained in this documentation (chapter 2 has the link to
the SDK which contains the USI.dll ) :
http://www.datacol.co.nz/pdf/uni_prog-guide_1.21.pdf
But i also get : Cant find PInvoke DLL 'USI.dll'.
In chapter 4 is SysIOAPI.DLL mentioned which i cant fin.
Chapter 17 has USICF.dll which may be interesting bcos this one can be added as reference and "using USICF" . I am using compact framework 3.5 for this and the emulator is "usa windows mobile 5.0 pocket pc r2 emulator".
Reading your post i noticed i can use the "Pocket PC 2003 SE Emulator" but it gives me the same error.
Maybe i need to include a path in my code but i tried this as well...and get the same problem. Maybe i am missing something.
Here is my code:
using USICF;
using System.Runtime.InteropServices;
namespace SmartDeviceProjectzaDLLtesting
    public partial class Form1 : Form
        [DllImport("USI.dll", EntryPoint = "VibrationOn")]   //ignorethis?:,CallingConvention=CallingConvention.Winapi)]//Cdecl)]    //EntryPoint = "VibrationOn")]
        public static extern void VibrationOn(bool bEnable);
        public Form1()
            InitializeComponent();
        private void Form1_Load(object sender, EventArgs e)
           // USICF.USIClass usiba = new USICF.USIClass(this); // this gives an exception as well
           VibrationOn(true); // thiis causes the exception
//           VibrationOn(false);

Java.lang.OutOfMemoryError: cannot create any more threads

Server: AIX
OS Level: 4.3.3
JDK 1.1.8
I have an application that creates a lot of worker Threads. For each widget, a new Thread is created. If there are 431 widgets, the program displays the OutOfMemory error and exits. If I reduce the number of widgets by 9 and only create 422 Threads everything works fine. I print out the TotalMemory() and the FreeMemory() just before it dies and there seems to be plenty of memory left. I have tried setting the following settings "-ms50m" and "-mx400m", but it seemed to make no difference. Any ideas?
Total Memory: 10211320
Free Memory: 1461640
I also ran using the "verbosegc" option. Here is that output:
<GC: freeing class [B(300291f8)>
<GC: freeing class java.lang.Compiler(3002a920)>
<GC: unloaded and freed 2 classes>
GC: Wed May 26 13:13:08 2004
<GC(async)(1): freed 635 objects, 24440 bytes in 8 ms, 65% free (684736/1048568)>
<GC(1): begin: 2630 ms, mark: 7 ms, sweep: 1 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[1]: managing allocation failure. need 1552 bytes, action=1 (21984/1048568)>
<GC: freeing class java.lang.NoSuchMethodException(30024300)>
<GC: freeing class java.rmi.UnexpectedException(30027610)>
<GC: freeing class sun.rmi.registry.RegistryImpl_Stub(30027b68)>
<GC: freeing class sun.security.provider.SHA(300250a8)>
<GC: unloaded and freed 4 classes>
GC: Wed May 26 13:13:14 2004
<GC(2): freed 6754 objects, 335560 bytes in 25 ms, 34% free (357544/1048568)>
<GC(2): begin: 8262 ms, mark: 18 ms, sweep: 7 ms, compact: 0 ms>
<AF[1]: completed in 532 ms>
<FIN: async finalizer thread waking>
<AF[2]: managing allocation failure. need 1552 bytes, action=1 (223896/1048568)>
GC: Wed May 26 13:13:14 2004
<GC(3): freed 1787 objects, 92008 bytes in 56 ms, 30% free (315880/1048568)>
<GC(3): begin: 8795 ms, mark: 20 ms, sweep: 5 ms, compact: 31 ms>
<GC(3): moved 9012 objects, 470088 bytes in 31 ms>
<AF[2]: completed in 544 ms>
<AF[3]: managing allocation failure. need 424 bytes, action=1 (13584/1048568)>
GC: Wed May 26 13:13:15 2004
<GC(4): freed 3960 objects, 199056 bytes in 27 ms, 20% free (212640/1048568)>
<GC(4): begin: 9621 ms, mark: 22 ms, sweep: 5 ms, compact: 0 ms>
<AF[3]: managing allocation failure. need 424 bytes, action=2 (212640/1048568)>
<AF[3]: managing allocation failure. need 424 bytes, action=3 (212640/1048568)>
<AF[3]: zeroed 3 of 3 soft refs in 3 ms>
GC: Wed May 26 13:13:16 2004
<GC(5): freed 14 objects, 744 bytes in 23 ms, 20% free (213384/1048568)>
<GC(5): begin: 10082 ms, mark: 20 ms, sweep: 3 ms, compact: 0 ms>
<AF[3]: managing allocation failure. need 424 bytes, action=3003 (213384/1048568)>
<AF[3]: zeroed 0 of 0 soft refs in 3 ms>
<AF[3]: managing allocation failure. need 424 bytes, action=4 (213384/1048568)>
<AF: expanded heap by 1048576 to 2097144 bytes, 60% free>
<AF[3]: completed in 1218 ms>
<AF[4]: managing allocation failure. need 1552 bytes, action=1 (134080/2097144)>
GC: Wed May 26 13:13:16 2004
<GC(6): freed 15077 objects, 748816 bytes in 107 ms, 42% free (882896/2097144)>
<GC(6): begin: 10726 ms, mark: 34 ms, sweep: 14 ms, compact: 59 ms>
<GC(6): moved 12562 objects, 828712 bytes in 59 ms>
<AF[4]: completed in 509 ms>
<AF[5]: managing allocation failure. need 1552 bytes, action=1 (12744/2097144)>
GC: Wed May 26 13:13:17 2004
<GC(7): freed 11655 objects, 575824 bytes in 55 ms, 28% free (588568/2097144)>
<GC(7): begin: 11542 ms, mark: 41 ms, sweep: 14 ms, compact: 0 ms>
<AF[5]: completed in 604 ms>
<AF[6]: managing allocation failure. need 3280 bytes, action=1 (558216/2097144)>
GC: Wed May 26 13:13:18 2004
<GC(8): freed 420 objects, 22088 bytes in 110 ms, 27% free (580304/2097144)>
<GC(8): begin: 11966 ms, mark: 41 ms, sweep: 8 ms, compact: 61 ms>
<GC(8): moved 11582 objects, 723272 bytes in 61 ms>
<AF[6]: completed in 473 ms>
<AF[7]: managing allocation failure. need 1552 bytes, action=1 (12304/2097144)>
GC: Wed May 26 13:13:18 2004
<GC(9): freed 7364 objects, 374360 bytes in 59 ms, 18% free (386664/2097144)>
<GC(9): begin: 12741 ms, mark: 48 ms, sweep: 11 ms, compact: 0 ms>
<AF[7]: managing allocation failure. need 1552 bytes, action=2 (386664/2097144)>
<AF[7]: managing allocation failure. need 1552 bytes, action=3 (386664/2097144)>
<AF[7]: zeroed 0 of 0 soft refs in 9 ms>
<AF[7]: managing allocation failure. need 1552 bytes, action=4 (386664/2097144)>
<AF: expanded heap by 1048576 to 3145720 bytes, 45% free>
<AF[7]: completed in 617 ms>
GC: Wed May 26 13:13:19 2004
<GC(10): freed 9825 objects, 492936 bytes in 172 ms, 38% free (1199928/3145720)>
<GC(10): begin: 13426 ms, mark: 56 ms, sweep: 16 ms, compact: 99 ms>
<GC(10): moved 22853 objects, 1415864 bytes in 99 ms>
GC: Wed May 26 13:13:20 2004
<GC(async)(11): freed 26 objects, 2440 bytes in 66 ms, 38% free (1196344/3145720)>
<GC(11): begin: 14222 ms, mark: 58 ms, sweep: 8 ms, compact: 0 ms>
<AF[8]: managing allocation failure. need 16400 bytes, action=1 (112112/3145720)>
<GC: freeing class java.rmi.UnexpectedException(30027610)>
<GC: freeing class sun.rmi.registry.RegistryImpl_Stub(30027b68)>
<GC: freeing class sun.security.provider.SHA(30020b30)>
<GC: unloaded and freed 3 classes>
GC: Wed May 26 13:13:24 2004
<GC(12): freed 5185 objects, 1014736 bytes in 71 ms, 35% free (1126848/3145720)>
<GC(12): begin: 18001 ms, mark: 59 ms, sweep: 12 ms, compact: 0 ms>
<AF[8]: completed in 830 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:25 2004
<GC(async)(13): freed 3882 objects, 824912 bytes in 72 ms, 35% free (1114576/3145720)>
<GC(13): begin: 19693 ms, mark: 60 ms, sweep: 12 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:27 2004
<GC(async)(14): freed 3455 objects, 739696 bytes in 75 ms, 35% free (1101776/3145720)>
<GC(14): begin: 21321 ms, mark: 62 ms, sweep: 13 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[9]: managing allocation failure. need 16400 bytes, action=1 (364032/3145720)>
GC: Wed May 26 13:13:28 2004
<GC(15): freed 3223 objects, 704488 bytes in 74 ms, 33% free (1068520/3145720)>
<GC(15): begin: 22665 ms, mark: 61 ms, sweep: 13 ms, compact: 0 ms>
<AF[9]: completed in 496 ms>
<FIN: async finalizer thread waking>
<AF[10]: managing allocation failure. need 16400 bytes, action=1 (270272/3145720)>
GC: Wed May 26 13:13:30 2004
<GC(16): freed 6494 objects, 712488 bytes in 81 ms, 31% free (982760/3145720)>
<GC(16): begin: 23905 ms, mark: 66 ms, sweep: 15 ms, compact: 0 ms>
<AF[10]: completed in 617 ms>
<FIN: async finalizer thread waking>
<AF[11]: managing allocation failure. need 16400 bytes, action=1 (522936/3145720)>
GC: Wed May 26 13:13:30 2004
<GC(17): freed 4048 objects, 474384 bytes in 81 ms, 31% free (997320/3145720)>
<GC(17): begin: 24759 ms, mark: 66 ms, sweep: 15 ms, compact: 0 ms>
<AF[11]: completed in 645 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:31 2004
<GC(async)(18): freed 2878 objects, 372312 bytes in 81 ms, 31% free (988168/3145720)>
<GC(18): begin: 25455 ms, mark: 67 ms, sweep: 14 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[12]: managing allocation failure. need 16400 bytes, action=1 (649312/3145720)>
GC: Wed May 26 13:13:32 2004
<GC(19): freed 1540 objects, 323336 bytes in 203 ms, 30% free (972560/3145720)>
<GC(19): begin: 26489 ms, mark: 68 ms, sweep: 14 ms, compact: 121 ms>
<GC(19): moved 28510 objects, 1684672 bytes in 121 ms>
<AF[12]: completed in 735 ms>
<FIN: async finalizer thread waking>
<AF[13]: managing allocation failure. need 16400 bytes, action=1 (75360/3145720)>
GC: Wed May 26 13:13:34 2004
<GC(20): freed 5621 objects, 854200 bytes in 81 ms, 29% free (929560/3145720)>
<GC(20): begin: 27906 ms, mark: 66 ms, sweep: 15 ms, compact: 0 ms>
<AF[13]: completed in 598 ms>
<FIN: async finalizer thread waking>
<AF[14]: managing allocation failure. need 16400 bytes, action=1 (185408/3145720)>
GC: Wed May 26 13:13:35 2004
<GC(21): freed 3437 objects, 727680 bytes in 80 ms, 29% free (913088/3145720)>
<GC(21): begin: 29354 ms, mark: 67 ms, sweep: 13 ms, compact: 0 ms>
<AF[14]: completed in 600 ms>
<FIN: async finalizer thread waking>
<AF[15]: managing allocation failure. need 16400 bytes, action=1 (255960/3145720)>
GC: Wed May 26 13:13:36 2004
<GC(22): freed 3369 objects, 631744 bytes in 86 ms, 28% free (887704/3145720)>
<GC(22): begin: 30784 ms, mark: 72 ms, sweep: 14 ms, compact: 0 ms>
<AF[15]: completed in 798 ms>
<FIN: async finalizer thread waking>
<AF[16]: managing allocation failure. need 1552 bytes, action=1 (277648/3145720)>
GC: Wed May 26 13:13:38 2004
<GC(23): freed 4319 objects, 571728 bytes in 208 ms, 27% free (849368/3145720)>
<GC(23): begin: 31820 ms, mark: 69 ms, sweep: 15 ms, compact: 124 ms>
<GC(23): moved 32020 objects, 1918840 bytes in 124 ms>
<AF[16]: completed in 716 ms>
<FIN: async finalizer thread waking>
<AF[17]: managing allocation failure. need 16400 bytes, action=1 (57816/3145720)>
GC: Wed May 26 13:13:39 2004
<GC(24): freed 8529 objects, 635392 bytes in 93 ms, 22% free (693208/3145720)>
<GC(24): begin: 32859 ms, mark: 74 ms, sweep: 18 ms, compact: 1 ms>
<AF[17]: managing allocation failure. need 16400 bytes, action=2 (693208/3145720)>
<FIN: async finalizer thread waking>
<AF[17]: synchronously running 4 finalizers>
<AF[17]: synchronous finalization attempt took 1 ms>
GC: Wed May 26 13:13:39 2004
<GC(25): freed 11 objects, 2376 bytes in 89 ms, 22% free (694032/3145720)>
<GC(25): begin: 33407 ms, mark: 75 ms, sweep: 14 ms, compact: 0 ms>
<AF[17]: managing allocation failure. need 16400 bytes, action=3 (694032/3145720)>
<AF[17]: zeroed 9 of 9 soft refs in 15 ms>
GC: Wed May 26 13:13:40 2004
<GC(26): freed 58 objects, 3472 bytes in 90 ms, 22% free (697504/3145720)>
<GC(26): begin: 33957 ms, mark: 76 ms, sweep: 14 ms, compact: 0 ms>
<AF[17]: managing allocation failure. need 16400 bytes, action=3003 (697504/3145720)>
<AF[17]: zeroed 0 of 0 soft refs in 16 ms>
<AF[17]: managing allocation failure. need 16400 bytes, action=4 (697504/3145720)>
<AF: expanded heap by 1048576 to 4194296 bytes, 41% free>
<AF[17]: completed in 1842 ms>
<AF[18]: managing allocation failure. need 8208 bytes, action=1 (265952/4194296)>
GC: Wed May 26 13:13:41 2004
<GC(27): freed 17813 objects, 1444896 bytes in 238 ms, 40% free (1710840/4194296)>
<GC(27): begin: 35625 ms, mark: 80 ms, sweep: 26 ms, compact: 132 ms>
<GC(27): moved 24970 objects, 1390720 bytes in 132 ms>
<AF[18]: completed in 936 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:43 2004
<GC(async)(28): freed 3519 objects, 866264 bytes in 96 ms, 40% free (1699032/4194296)>
<GC(28): begin: 37429 ms, mark: 79 ms, sweep: 17 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:45 2004
<GC(async)(29): freed 7470 objects, 964488 bytes in 97 ms, 39% free (1646808/4194296)>
<GC(29): begin: 39287 ms, mark: 79 ms, sweep: 18 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:47 2004
<GC(async)(30): freed 4130 objects, 807712 bytes in 97 ms, 38% free (1625440/4194296)>
<GC(30): begin: 40857 ms, mark: 80 ms, sweep: 17 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:48 2004
<GC(async)(31): freed 6462 objects, 911544 bytes in 103 ms, 37% free (1579288/4194296)>
<GC(31): begin: 42499 ms, mark: 83 ms, sweep: 19 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[19]: managing allocation failure. need 16400 bytes, action=1 (544024/4194296)>
GC: Wed May 26 13:13:50 2004
<GC(32): freed 9174 objects, 963288 bytes in 255 ms, 35% free (1507304/4194296)>
<GC(32): begin: 43944 ms, mark: 85 ms, sweep: 22 ms, compact: 148 ms>
<GC(32): moved 31280 objects, 1760488 bytes in 148 ms>
<AF[19]: completed in 727 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:51 2004
<GC(async)(33): freed 5334 objects, 916464 bytes in 105 ms, 35% free (1479760/4194296)>
<GC(33): begin: 45710 ms, mark: 85 ms, sweep: 20 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:13:53 2004
<GC(async)(34): freed 4727 objects, 843296 bytes in 110 ms, 34% free (1452368/4194296)>
<GC(34): begin: 47271 ms, mark: 89 ms, sweep: 21 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[20]: managing allocation failure. need 1552 bytes, action=1 (201640/4194296)>
GC: Wed May 26 13:13:55 2004
<GC(35): freed 15729 objects, 1102776 bytes in 311 ms, 31% free (1304416/4194296)>
<GC(35): begin: 48752 ms, mark: 104 ms, sweep: 32 ms, compact: 175 ms>
<GC(35): moved 35105 objects, 1835792 bytes in 175 ms>
<AF[20]: completed in 894 ms>
<FIN: async finalizer thread waking>
<AF[21]: managing allocation failure. need 16400 bytes, action=1 (78240/4194296)>
GC: Wed May 26 13:13:56 2004
<GC(36): freed 12481 objects, 1155656 bytes in 122 ms, 29% free (1233896/4194296)>
<GC(36): begin: 50490 ms, mark: 96 ms, sweep: 26 ms, compact: 0 ms>
<AF[21]: completed in 626 ms>
<FIN: async finalizer thread waking>
<AF[22]: managing allocation failure. need 16400 bytes, action=1 (352488/4194296)>
GC: Wed May 26 13:13:58 2004
<GC(37): freed 4977 objects, 846352 bytes in 122 ms, 28% free (1198840/4194296)>
<GC(37): begin: 52136 ms, mark: 98 ms, sweep: 24 ms, compact: 0 ms>
<AF[22]: completed in 788 ms>
<FIN: async finalizer thread waking>
<AF[23]: managing allocation failure. need 16400 bytes, action=1 (447480/4194296)>
GC: Wed May 26 13:13:59 2004
<GC(38): freed 3784 objects, 727792 bytes in 127 ms, 28% free (1175272/4194296)>
<GC(38): begin: 53702 ms, mark: 101 ms, sweep: 26 ms, compact: 0 ms>
<AF[23]: completed in 732 ms>
<FIN: async finalizer thread waking>
<AF[24]: managing allocation failure. need 16400 bytes, action=1 (505640/4194296)>
GC: Wed May 26 13:14:01 2004
<GC(39): freed 3844 objects, 648688 bytes in 125 ms, 27% free (1154328/4194296)>
<GC(39): begin: 54998 ms, mark: 98 ms, sweep: 27 ms, compact: 0 ms>
<AF[24]: completed in 667 ms>
<FIN: async finalizer thread waking>
<AF[25]: managing allocation failure. need 16400 bytes, action=1 (561280/4194296)>
GC: Wed May 26 13:14:02 2004
<GC(40): freed 4740 objects, 548792 bytes in 302 ms, 26% free (1110072/4194296)>
<GC(40): begin: 55896 ms, mark: 102 ms, sweep: 26 ms, compact: 174 ms>
<GC(40): moved 32891 objects, 1661088 bytes in 174 ms>
<AF[25]: completed in 743 ms>
<FIN: async finalizer thread waking>
<AF[26]: managing allocation failure. need 16400 bytes, action=1 (292096/4194296)>
GC: Wed May 26 13:14:03 2004
<GC(41): freed 6267 objects, 774336 bytes in 139 ms, 25% free (1066432/4194296)>
<GC(41): begin: 57515 ms, mark: 113 ms, sweep: 26 ms, compact: 0 ms>
<AF[26]: completed in 772 ms>
<FIN: async finalizer thread waking>
<AF[27]: managing allocation failure. need 16400 bytes, action=1 (315984/4194296)>
GC: Wed May 26 13:14:05 2004
<GC(42): freed 4472 objects, 726008 bytes in 129 ms, 24% free (1041992/4194296)>
<GC(42): begin: 58864 ms, mark: 104 ms, sweep: 25 ms, compact: 0 ms>
<AF[27]: managing allocation failure. need 16400 bytes, action=2 (1041992/4194296)>
<AF[27]: synchronously running 18 finalizers>
<FIN: async finalizer thread waking>
<AF[27]: synchronous finalization attempt took 3 ms>
GC: Wed May 26 13:14:05 2004
<GC(43): freed 46 objects, 6040 bytes in 129 ms, 24% free (1046480/4194296)>
<GC(43): begin: 59401 ms, mark: 106 ms, sweep: 23 ms, compact: 0 ms>
<AF[27]: managing allocation failure. need 16400 bytes, action=3 (1046480/4194296)>
<AF[27]: zeroed 0 of 0 soft refs in 23 ms>
<AF[27]: managing allocation failure. need 16400 bytes, action=4 (1046480/4194296)>
<AF: expanded heap by 1048576 to 5242872 bytes, 39% free>
<AF[27]: completed in 1233 ms>
<AF[28]: managing allocation failure. need 16400 bytes, action=1 (439288/5242872)>
GC: Wed May 26 13:14:08 2004
<GC(44): freed 7949 objects, 1599288 bytes in 289 ms, 38% free (2038576/5242872)>
<GC(44): begin: 62021 ms, mark: 106 ms, sweep: 27 ms, compact: 156 ms>
<GC(44): moved 22967 objects, 1133840 bytes in 156 ms>
<AF[28]: completed in 1044 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:14:10 2004
<GC(async)(45): freed 4094 objects, 840880 bytes in 133 ms, 38% free (2030528/5242872)>
<GC(45): begin: 63875 ms, mark: 108 ms, sweep: 25 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[29]: managing allocation failure. need 8208 bytes, action=1 (114768/5242872)>
GC: Wed May 26 13:14:12 2004
<GC(46): freed 21586 objects, 1635288 bytes in 154 ms, 33% free (1750056/5242872)>
<GC(46): begin: 65807 ms, mark: 115 ms, sweep: 39 ms, compact: 0 ms>
<AF[29]: completed in 691 ms>
<FIN: async finalizer thread waking>
<AF[30]: managing allocation failure. need 1552 bytes, action=1 (696192/5242872)>
GC: Wed May 26 13:14:13 2004
<GC(47): freed 14485 objects, 957856 bytes in 376 ms, 31% free (1654048/5242872)>
<GC(47): begin: 66906 ms, mark: 122 ms, sweep: 38 ms, compact: 216 ms>
<GC(47): moved 34318 objects, 1722880 bytes in 216 ms>
<AF[30]: completed in 927 ms>
<FIN: async finalizer thread waking>
<AF[31]: managing allocation failure. need 16400 bytes, action=1 (459760/5242872)>
GC: Wed May 26 13:14:14 2004
<GC(48): freed 13009 objects, 1168784 bytes in 153 ms, 31% free (1628544/5242872)>
<GC(48): begin: 68716 ms, mark: 119 ms, sweep: 34 ms, compact: 0 ms>
<AF[31]: completed in 747 ms>
<FIN: async finalizer thread waking>
<AF[32]: managing allocation failure. need 16400 bytes, action=1 (538768/5242872)>
GC: Wed May 26 13:14:17 2004
<GC(49): freed 8330 objects, 1021448 bytes in 339 ms, 29% free (1560216/5242872)>
<GC(49): begin: 70875 ms, mark: 122 ms, sweep: 33 ms, compact: 184 ms>
<GC(49): moved 24324 objects, 1119304 bytes in 184 ms>
<AF[32]: completed in 1494 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:14:19 2004
<GC(async)(50): freed 4448 objects, 927416 bytes in 152 ms, 29% free (1545096/5242872)>
<GC(50): begin: 72825 ms, mark: 122 ms, sweep: 30 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[33]: managing allocation failure. need 16400 bytes, action=1 (158984/5242872)>
GC: Wed May 26 13:14:21 2004
<GC(51): freed 10590 objects, 1250112 bytes in 167 ms, 26% free (1409096/5242872)>
<GC(51): begin: 74814 ms, mark: 130 ms, sweep: 37 ms, compact: 0 ms>
<AF[33]: completed in 736 ms>
<FIN: async finalizer thread waking>
<AF[34]: managing allocation failure. need 1552 bytes, action=1 (402752/5242872)>
GC: Wed May 26 13:14:22 2004
<GC(52): freed 13192 objects, 837080 bytes in 415 ms, 23% free (1239832/5242872)>
<GC(52): begin: 75673 ms, mark: 135 ms, sweep: 41 ms, compact: 238 ms>
<GC(52): moved 34722 objects, 1631272 bytes in 238 ms>
<AF[34]: managing allocation failure. need 1552 bytes, action=2 (1239832/5242872)>
<FIN: async finalizer thread waking>
<AF[34]: synchronously running 6 finalizers>
<AF[34]: synchronous finalization attempt took 1 ms>
GC: Wed May 26 13:14:22 2004
<GC(53): freed 21 objects, 4984 bytes in 161 ms, 23% free (1241712/5242872)>
<GC(53): begin: 76457 ms, mark: 130 ms, sweep: 31 ms, compact: 0 ms>
<AF[34]: managing allocation failure. need 1552 bytes, action=3 (1241712/5242872)>
<AF[34]: zeroed 0 of 0 soft refs in 34 ms>
<AF[34]: managing allocation failure. need 1552 bytes, action=4 (1241712/5242872)>
<AF: expanded heap by 1048576 to 6291448 bytes, 36% free>
<AF[34]: completed in 1415 ms>
<AF[35]: managing allocation failure. need 16400 bytes, action=1 (252936/6291448)>
GC: Wed May 26 13:14:24 2004
<GC(54): freed 23814 objects, 1717504 bytes in 453 ms, 31% free (1970440/6291448)>
<GC(54): begin: 78098 ms, mark: 148 ms, sweep: 51 ms, compact: 253 ms>
<GC(54): moved 34460 objects, 1684384 bytes in 253 ms>
<AF[35]: completed in 952 ms>
<FIN: async finalizer thread waking>
<AF[36]: managing allocation failure. need 16400 bytes, action=1 (143712/6291448)>
GC: Wed May 26 13:14:26 2004
<GC(55): freed 26403 objects, 1600136 bytes in 203 ms, 27% free (1743848/6291448)>
<GC(55): begin: 79739 ms, mark: 148 ms, sweep: 55 ms, compact: 0 ms>
<AF[36]: completed in 758 ms>
<FIN: async finalizer thread waking>
<AF[37]: managing allocation failure. need 61912 bytes, action=1 (1223696/6291448)>
GC: Wed May 26 13:14:27 2004
<GC(56): freed 5320 objects, 370504 bytes in 481 ms, 25% free (1594200/6291448)>
<GC(56): begin: 80478 ms, mark: 153 ms, sweep: 47 ms, compact: 281 ms>
<GC(56): moved 43171 objects, 1952320 bytes in 281 ms>
<AF[37]: completed in 883 ms>
<FIN: async finalizer thread waking>
<AF[38]: managing allocation failure. need 16400 bytes, action=1 (394680/6291448)>
GC: Wed May 26 13:14:28 2004
<GC(57): freed 14083 objects, 964208 bytes in 209 ms, 21% free (1358888/6291448)>
<GC(57): begin: 81774 ms, mark: 160 ms, sweep: 49 ms, compact: 0 ms>
<AF[38]: managing allocation failure. need 16400 bytes, action=2 (1358888/6291448)>
<FIN: async finalizer thread waking>
<AF[38]: synchronously running 12 finalizers>
<AF[38]: synchronous finalization attempt took 1 ms>
GC: Wed May 26 13:14:28 2004
<GC(58): freed 36 objects, 5168 bytes in 206 ms, 21% free (1360952/6291448)>
<GC(58): begin: 82355 ms, mark: 160 ms, sweep: 46 ms, compact: 0 ms>
<AF[38]: managing allocation failure. need 16400 bytes, action=3 (1360952/6291448)>
<AF[38]: zeroed 0 of 0 soft refs in 50 ms>
<AF[38]: managing allocation failure. need 16400 bytes, action=4 (1360952/6291448)>
<AF: expanded heap by 1101824 to 7393272 bytes, 33% free>
<AF[38]: completed in 1294 ms>
<AF[39]: managing allocation failure. need 16400 bytes, action=1 (674336/7393272)>
GC: Wed May 26 13:14:31 2004
<GC(59): freed 16138 objects, 1510224 bytes in 584 ms, 29% free (2184560/7393272)>
<GC(59): begin: 84491 ms, mark: 178 ms, sweep: 60 ms, compact: 346 ms>
<GC(59): moved 55092 objects, 2219584 bytes in 346 ms>
<AF[39]: completed in 1242 ms>
<FIN: async finalizer thread waking>
<AF[40]: managing allocation failure. need 8208 bytes, action=1 (120088/7393272)>
GC: Wed May 26 13:14:33 2004
<GC(60): freed 17355 objects, 1880752 bytes in 245 ms, 27% free (2000840/7393272)>
<GC(60): begin: 86760 ms, mark: 183 ms, sweep: 62 ms, compact: 0 ms>
<AF[40]: completed in 866 ms>
<FIN: async finalizer thread waking>
<AF[41]: managing allocation failure. need 1552 bytes, action=1 (221648/7393272)>
GC: Wed May 26 13:14:35 2004
<GC(61): freed 21131 objects, 1627296 bytes in 591 ms, 25% free (1848944/7393272)>
<GC(61): begin: 88506 ms, mark: 181 ms, sweep: 63 ms, compact: 347 ms>
<GC(61): moved 57273 objects, 2733408 bytes in 347 ms>
<AF[41]: completed in 1170 ms>
<FIN: async finalizer thread waking>
<AF[42]: managing allocation failure. need 16400 bytes, action=1 (84512/7393272)>
GC: Wed May 26 13:14:36 2004
<GC(62): freed 18625 objects, 1461576 bytes in 263 ms, 20% free (1546088/7393272)>
<GC(62): begin: 90212 ms, mark: 196 ms, sweep: 67 ms, compact: 0 ms>
<AF[42]: managing allocation failure. need 16400 bytes, action=2 (1546088/7393272)>
<FIN: async finalizer thread waking>
<AF[42]: synchronously running 14 finalizers>
<AF[42]: synchronous finalization attempt took 1 ms>
GC: Wed May 26 13:14:37 2004
<GC(63): freed 46 objects, 6728 bytes in 252 ms, 20% free (1549712/7393272)>
<GC(63): begin: 90853 ms, mark: 197 ms, sweep: 55 ms, compact: 0 ms>
<AF[42]: managing allocation failure. need 16400 bytes, action=3 (1549712/7393272)>
<AF[42]: zeroed 0 of 0 soft refs in 61 ms>
<AF[42]: managing allocation failure. need 16400 bytes, action=4 (1549712/7393272)>
<AF: expanded heap by 1294336 to 8687608 bytes, 32% free>
<AF[42]: completed in 1441 ms>
<AF[43]: managing allocation failure. need 16400 bytes, action=1 (658696/8687608)>
GC: Wed May 26 13:14:40 2004
<GC(64): freed 20119 objects, 2108800 bytes in 611 ms, 31% free (2767496/8687608)>
<GC(64): begin: 93853 ms, mark: 197 ms, sweep: 68 ms, compact: 346 ms>
<GC(64): moved 46120 objects, 1817512 bytes in 346 ms>
<AF[43]: completed in 1340 ms>
<FIN: async finalizer thread waking>
<AF[44]: managing allocation failure. need 16400 bytes, action=1 (348696/8687608)>
GC: Wed May 26 13:14:43 2004
<GC(65): freed 24943 objects, 2286616 bytes in 280 ms, 30% free (2635312/8687608)>
<GC(65): begin: 97187 ms, mark: 209 ms, sweep: 71 ms, compact: 0 ms>
<AF[44]: completed in 1027 ms>
<FIN: async finalizer thread waking>
<AF[45]: managing allocation failure. need 16400 bytes, action=1 (921208/8687608)>
GC: Wed May 26 13:14:45 2004
<GC(66): freed 25648 objects, 1677408 bytes in 628 ms, 29% free (2598616/8687608)>
<GC(66): begin: 99185 ms, mark: 203 ms, sweep: 72 ms, compact: 353 ms>
<GC(66): moved 40683 objects, 1679720 bytes in 353 ms>
<AF[45]: completed in 1269 ms>
<FIN: async finalizer thread waking>
<AF[46]: managing allocation failure. need 16400 bytes, action=1 (298648/8687608)>
GC: Wed May 26 13:14:48 2004
<GC(67): freed 24497 objects, 2194248 bytes in 280 ms, 28% free (2492896/8687608)>
<GC(67): begin: 102480 ms, mark: 209 ms, sweep: 71 ms, compact: 0 ms>
<AF[46]: completed in 1045 ms>
<FIN: async finalizer thread waking>
<AF[47]: managing allocation failure. need 16400 bytes, action=1 (926440/8687608)>
GC: Wed May 26 13:14:51 2004
<GC(68): freed 16029 objects, 1506568 bytes in 649 ms, 28% free (2433008/8687608)>
<GC(68): begin: 104589 ms, mark: 212 ms, sweep: 71 ms, compact: 366 ms>
<GC(68): moved 37208 objects, 1532696 bytes in 366 ms>
<AF[47]: completed in 1219 ms>
<FIN: async finalizer thread waking>
<AF[48]: managing allocation failure. need 16400 bytes, action=1 (173384/8687608)>
GC: Wed May 26 13:14:52 2004
<GC(69): freed 51791 objects, 2147296 bytes in 315 ms, 26% free (2320680/8687608)>
<GC(69): begin: 106490 ms, mark: 225 ms, sweep: 90 ms, compact: 0 ms>
<AF[48]: completed in 934 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:14:54 2004
<GC(async)(70): freed 6219 objects, 1029800 bytes in 283 ms, 26% free (2288904/8687608)>
<GC(70): begin: 108407 ms, mark: 217 ms, sweep: 66 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:14:56 2004
<GC(async)(71): freed 5729 objects, 880760 bytes in 283 ms, 25% free (2248616/8687608)>
<GC(71): begin: 110141 ms, mark: 217 ms, sweep: 66 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[49]: managing allocation failure. need 16400 bytes, action=1 (969720/8687608)>
GC: Wed May 26 13:14:59 2004
<GC(72): freed 5892 objects, 1249144 bytes in 687 ms, 25% free (2218864/8687608)>
<GC(72): begin: 112714 ms, mark: 223 ms, sweep: 68 ms, compact: 396 ms>
<GC(72): moved 39455 objects, 1664056 bytes in 396 ms>
<AF[49]: completed in 1301 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:01 2004
<GC(async)(73): freed 8020 objects, 1112008 bytes in 306 ms, 25% free (2175920/8687608)>
<GC(73): begin: 115094 ms, mark: 232 ms, sweep: 74 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:03 2004
<GC(async)(74): freed 3458 objects, 784440 bytes in 285 ms, 24% free (2157712/8687608)>
<GC(74): begin: 116914 ms, mark: 221 ms, sweep: 64 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:05 2004
<GC(async)(75): freed 4251 objects, 820752 bytes in 288 ms, 24% free (2133176/8687608)>
<GC(75): begin: 118932 ms, mark: 222 ms, sweep: 66 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:07 2004
<GC(async)(76): freed 3670 objects, 792432 bytes in 295 ms, 24% free (2111200/8687608)>
<GC(76): begin: 120808 ms, mark: 228 ms, sweep: 67 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:09 2004
<GC(async)(77): freed 5047 objects, 853656 bytes in 293 ms, 23% free (2078848/8687608)>
<GC(77): begin: 122707 ms, mark: 225 ms, sweep: 68 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:11 2004
<GC(async)(78): freed 2987 objects, 762568 bytes in 295 ms, 23% free (2063392/8687608)>
<GC(78): begin: 124622 ms, mark: 228 ms, sweep: 67 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:12 2004
<GC(async)(79): freed 4024 objects, 809992 bytes in 295 ms, 23% free (2040800/8687608)>
<GC(79): begin: 126488 ms, mark: 226 ms, sweep: 69 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:14 2004
<GC(async)(80): freed 4276 objects, 820272 bytes in 300 ms, 23% free (2013800/8687608)>
<GC(80): begin: 128277 ms, mark: 230 ms, sweep: 70 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:16 2004
<GC(async)(81): freed 2995 objects, 763960 bytes in 299 ms, 22% free (1998048/8687608)>
<GC(81): begin: 130138 ms, mark: 229 ms, sweep: 70 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
<AF[50]: managing allocation failure. need 16400 bytes, action=1 (1239008/8687608)>
GC: Wed May 26 13:15:18 2004
<GC(82): freed 3634 objects, 725728 bytes in 731 ms, 22% free (1964736/8687608)>
<GC(82): begin: 131754 ms, mark: 234 ms, sweep: 71 ms, compact: 425 ms>
<GC(82): moved 57964 objects, 2313288 bytes in 425 ms>
<AF[50]: managing allocation failure. need 16400 bytes, action=2 (1964736/8687608)>
<FIN: async finalizer thread waking>
<AF[50]: synchronously running 18 finalizers>
<AF[50]: synchronous finalization attempt took 0 ms>
GC: Wed May 26 13:15:19 2004
<GC(83): freed 43 objects, 7568 bytes in 296 ms, 22% free (1970752/8687608)>
<GC(83): begin: 132865 ms, mark: 231 ms, sweep: 65 ms, compact: 0 ms>
<AF[50]: managing allocation failure. need 16400 bytes, action=3 (1970752/8687608)>
<AF[50]: zeroed 0 of 0 soft refs in 74 ms>
<AF[50]: managing allocation failure. need 16400 bytes, action=4 (1970752/8687608)>
<AF: expanded heap by 1523712 to 10211320 bytes, 34% free>
<AF[50]: completed in 1951 ms>
GC: Wed May 26 13:15:20 2004
<GC(async)(84): freed 3361 objects, 465256 bytes in 663 ms, 34% free (3478624/10211320)>
<GC(84): begin: 133983 ms, mark: 237 ms, sweep: 67 ms, compact: 359 ms>
<GC(84): moved 10549 objects, 445792 bytes in 359 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:22 2004
<GC(async)(85): freed 4413 objects, 819304 bytes in 304 ms, 33% free (3453600/10211320)>
<GC(85): begin: 136216 ms, mark: 235 ms, sweep: 69 ms, compact: 0 ms>
<FIN: async finalizer thread waking>
GC: Wed May 26 13:15:24 2004
<GC(async)

Noting that you are using a IBM vm and a rather old one at that...
Threads take java memory. Normally the solution is to increase the maximum java heap. Doing that depends on the memory that the system supports and the maximum that the VM allows and the default that it uses.
You might want to verify the command line options you are using. You might want to also find out what happens if you use a larger number or smaller one.
And if all else fails you can use a thread pool rather than trying to create seperate threads.

My iphone4 says cannot creat any more free icloud accounts

Went and got iphone turned on payed for activation and was told everything fine and all ready to use . now the cloud says it can no longer make any more free icloud accounts how can i get my icloud to accept my account

Hi Alisson.Oliver,
Welcome to the Support Communities!
Are you asking about email aliases for your iCloud account? If so, the limit is three. This article will explain how to manage them.
iCloud: About email aliases
http://support.apple.com/kb/ht4897
Cheers,
- Judy

Cannot find Data Neighborhood in NI-DAQmx Base to create a Task

I cannot find Data Neighborhood in NI-DAQmx Base inorder to create a Task.
I am trying to follow the "Learning with LabVIEW 8" tutorial book.
I am using a NI USB-6008, and have downloaded NI-DAQmx Base 3.0.
The book says to right click on Data Neighborhood and "Create New". I cannot find Data Neighborhood anywhere. The help documents referance Data Neighborhood but I still can not find it. Is Data Neighborhood not in the base version?
Please Help Thank you

Hi Lazysmartperson,
DAQmx base uses a different utility to create tasks. This is called the NI DAQmx Base Configuration Utility. It can be found in Windows by going to Start » Programs » National Instruments » NI-DAQmx Base » Utilities » C Interface. The reason behind this is because NI DAQmx Base is typically used on non windows operating systems such as Linux, Mac OSX, and some RT systems. Since there is no Measurement and Automation Explorer (MAX) for these operating systems we use a different utility for customers to configure tasks. If there is no specific reason you cannot use DAQmx, I would highly recommend switching to it. Our DAQmx driver is fully supported within MAX and should show up as in Matthew's last post. If you are looking to develop in DAQmx Base so that the applications can be used later on Linux, Mac, or other DAQmx base supported operating systems, I would suggest taking a look at the DAQmx Base Configuration Utility.
I hope this helps,
Paul C.

NI-DAQmx Base 3.2

hi,
As far as I know, NI-DAQmx Base 3.2 can create channel for voltage and thermocouple. How may I create channel for acceleration and pressure?
Thank You for helping

Hi,
Thank you for your reply.
In DAQmx create channel drop-down menu, we have acceleration and pressure. But, in DAQmxBase create channel drop-down menu, we do not have acceleration and pressure. That's the reason why I doubt we cannot use DAQmxBase for acceleraion and pressure.

USB 6009 thermocouple noise

I'm using NI-DAQmx 7.5, Labview 7.0, and a USB-6009.
I'm trying to get a more accurate reading from my j-type thermocouple. It is now distorted with noise and jumps rapidly +/- 20 degrees around room temp without any heat being applied. When heat is applied, it climbs as it should but with the same variation. I haven't moved to the labview side of it yet, I'm still trying to get a usable reading in MAX. I have it wired as a differential input with a floating signal source. I've installed 10k ohm resistors for bias current return as instructed. Installing the resistors helped but still leaves me with the readings shown in the attached pic. I've also tried grounding my USB 6009 with no results. Please help. john
Attachments:
thermocouple reading.jpg ‏41 KB

Hi John,
What you are running into is a problem with the actual voltage resolution of your USB-6009. This device has 14-bits of resolution over a minimum range of +/- 1V. That means that the voltage resolution is (1 - (-1))V / (2^14) = 2V / (16384) = 122uV. While this is an excellent resolution for such a low cost USB device, you will still notice problems when trying to make a thermocouple measurement. The reason for that is that Thermocouples make a very small output voltage (see image below).
Common thermocouple types have the following response:
K type: 41 microVolts per degree Celsius
J type: 56 microVolts per degree Celsius
T type: 52 microVolts per degree Celsius
There are a few options for ways to get around this limitation.
Good: You could read the signal in as a voltage and then manually convert that voltage into a temperature. This would be the least accurate method, but it should allow you to average out your signal and then use the Convert Thermocouple Reading.vi to show the voltage as a temperature.
Better: If you want to keep using the USB-6009 to measure thermocouple, what you really need to do is first amplify your signal before you connect it with your device. This should increase your resolution of the thermocouple allowing you to get more accurate temperature specs. This will require some more complex programming to properly scale your measurements, but it will give you more accurate readings for relatively little cost.
Best: Opt for getting a USB device that is designed for taking temperature measurements such as the USB-9211A. This device would give you a voltage resolution of 160mV/2^24 = 9.54 nV! That's over 12500x the resolution of the USB-6009 that you currently have.
Hopefully the above information helps you better understand what is going on and why. If you have any other questions feel free to post them here.
Message Edited by Otis [DE] on 01-13-2006 11:37 AM
Message Edited by Otis [DE] on 01-13-2006 11:38 AM
Otis
Training and Certification
Product Support Engineer
National Instruments
Attachments:
761029-Thermocouple_Voltages.GIF ‏10 KB

USB-6009 AI and AO

Hello,
I have an USB-6009 DAQmx device. I would like to measure analogue input with the possible highest sampling rate (48kHz) . At the same time, I need to ramp a voltage analogue output from 0 to 5 Volts, lets say during 2 minutes. These two tasks do not require close syncing. Regarding to the spec, the highest rate of the AO is 150 Hz. It is ok for my application.
So the AI measurement will use device internal clock, and the AO can only work with software timing. Is it possible to independently ramping the voltage output and at the same time, reading the analogue input? If not, is there a workaround for this device?
Thanks for advice!
Regards,
Solved!
Go to Solution.

I have made a test version (the final solution will do measurement for 2 minutes, so I will need to ramp up the analogue signal from 0 to 5 Volts in 2 minutes, and I think 10 msec will give a sufficiently smooth ramp curve --> 24000 steps over the 5V range).
In this test VI I do measurement on two analogue inputs using internal timing, and in parallel, I do the ramp signal with software timing (I guess it is not advised to go below 10 msec because Windows can slow down too much?).
Additional question: when I use DAQ on the two input channels, I understand that, the available highest rate is half of the maximum. But when I plot the two channels, the points are at the same time on the XY graph. How does LabView interleave data from the two channels during measurement?
Thanks for help and advice,
Regards,
Attachments:
Test1.vi ‏213 KB

How to recognize s-series daq card in DAQmx Base 2.0

I installed the "DAQmx BASE 2.0", and then installed 3 PCI DAQ boards. It can recognize PCI-6024E and PCI-6713, but not PCI-6133.
I followed exactly the same procedure as in the document called "How do I use NI-DAQmx Base with PCI/PXI Devices on Windows?"
http://digital.ni.com/public.nsf/websearch/9C4E9FD0C7469BC286256F100074EADC?OpenDocument
However, there is a web page (the link below) having labview example programs using DAQmx Base for "NI 6110 S Series Multifunction DAQ". So I think probably there is a way to recognize the S-series devices in DAQmx base.
http://digital.ni.com/public.nsf/allkb/722DDAB4E914073D8625708100773677
Does anybody know how to recognize S-series device in DAQmx Base 2.0?
Thanks

Alan,
Thank you very much for the quick response.
The reason I explored DAQmx: I want to do RLP and DAQmx Base has a simpler interface and more examples for RLP.
The reason I want to go RLP instead of DAQmx is a long story.
Summary of my applications:
I need to read 4 input voltage (using PCI-6133) and then generate 12 voltages (using two PCI-6713 each has 8 outputs). Since the 12 generated voltages are related to the 4 input voltages, single sample /N channel AD/DA is required. The speed for the overall control loop has to be >100 kHz.
Summary of my configurations:
PIII, 700 MHz CPU, 512 MB RAM
PCI-6133 and PCI 6713, LabVIEW 7.0, and DAQmx 8.0
I also have PCI-6110 and PCI-6024E cards for comparison
Summary for 4 channel single point acquisition (See the table below, AD only)
1) The difference between P3/700MHz computer and P4/3GHz computer is very small
2) The S-series performed worse than E- and M- Series
     Spec (kS/s)   Tested by me(700MHz P3)   by NI engineer (3GHz P4)
6024E   200/4            15.7 kHz                    17.36 kHz
6040E   250/4                                        18.9 kHz
6251   1000/4                                        23.0 kHz
6133   2500/1            13.8 kHz
Summary for single channel single point acquisition (See the table below, AD only)
1) The S-series performed much worse than E- and M- Series (simultaneous sampling is worse?)
     Spec (kS/s)    Tested by me (700MHz P3)
6024E    200/1           54.8 kHz
6110    5000/1           19.4 kHz
6133    2500/1           14.5 kHz
Simulated device          135 kHz
Summary for single channel single point AO (See the table below, DA only)
The spec of 6024E is only 10kS/s, but the loop can run at 132 kHz (the output from the port was not correct for sure). Using a simulated device (either 6024E or 6713), the loop rate is ~ 134 kHz (probably due to my low speed computer). This means the latency from 6024E devices is virtually zero. However, the latency from 6713 is way too much.
      Spec (kS/s)   tested by me (700MHz P3)
6024E    10/1             132 kHz
6713   1000/1              38 kHz
Simulated device          134 kHz
From all the above tests, it seems that s-series device (6133) and AO device (6713) perform much poorly in single point mode compared to E-series device (6024E). I thought the difference might be due to the driver in DAQmx. So, I want to try RLP to see whether I can gain up control loop speed to 100 kHz for my applications.
Your suggestions and advices are appreciated.
Thanks
Jin-Xing

USB 6009 and DAQmx Base Concerns

Hello,
I just received a USB-6009 multifunction DAQ device along with DAQmx Base for use on Windows XP with LabWindows/CVI ver 7.1. Both the 6009 and DAQmxBase are successfully installed however I have several questions, I hope I am missing something obvious:
1. The Task Configuration Utility is not needed for use with LabWindows/CVI? I believe I read this in the Getting Started Guide.
2. There is no function panel for the DAQmxBase functions? I even searched the installation CD and found no .fp files. So the only way to know what functions are available with DAQmxBase is to open the NIDAQmxBase.h file and search through the function prototypes? Then, to know what a function does it is necessary to open the C Function Reference Manual via the Windows Start button and search for the function name of interest?
3. When creating a digital input or output channel with DAQmxBaseCreateDIChan or DOChan is it only possible to setup a "channel" as an entire port? Is it not possible to setup a channel as a single input or output line? Similarly, once the channel is configured is it only possible to read or write an entire port with DAQmxBaseReadDigitalU8 or WriteDigitalU8? I was expecting something similar to the DIG_out_line function used in Traditional NI-DAQ where a board number, port number, line number and state are passed so that a signal output line can be set on or off.
Thanks in advance for the assistance,
- Aaron

Aaron T. wrote:
Hello, I just received a USB-6009 multifunction DAQ device along with DAQmx Base for use on Windows XP with LabWindows/CVI ver 7.1. Both the 6009 and DAQmxBase are successfully installed however I have several questions, I hope I am missing something obvious: 1. The Task Configuration Utility is not needed for use with LabWindows/CVI? I believe I read this in the Getting Started Guide.
**The Task Configuration Utility is not necessary, except that there is significant functionality missing from DAQmx Base but present in the utility. That includes a lot of what DAQmx calls "proerties", and includes things like the convert rate for AI scanning.
2. There is no function panel for the DAQmxBase functions? I even searched the installation CD and found no .fp files. So the only way to know what functions are available with DAQmxBase is to open the NIDAQmxBase.h file and search through the function prototypes? Then, to know what a function does it is necessary to open the C Function Reference Manual via the Windows Start button and search for the function name of interest?
**I don't use CVI so I don't know anything about this. It strikes me that even if you have such a panel reading the documentation is a good idea
3. When creating a digital input or output channel with DAQmxBaseCreateDIChan or DOChan is it only possible to setup a "channel" as an entire port? Is it not possible to setup a channel as a single input or output line? Similarly, once the channel is configured is it only possible to read or write an entire port with DAQmxBaseReadDigitalU8 or WriteDigitalU8? I was expecting something similar to the DIG_out_line function used in Traditional NI-DAQ where a board number, port number, line number and state are passed so that a signal output line can be set on or off.
**Well, the ReadMe file says that USB-6008/9 is supported with both Line I/O and Port I/O. On the other hand, the documentation for DAQmxBaseCreateDOChan and DAQmxBaseCreateDIChan say for the lineGrouping parameter, "Always pass DAQmx_Val_ChanForAllLines." So your question is a good one! Perhaps one of the NI engineers can comment on this.
- Aaron
Thanks in advance for the assistance,
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com

USB-6009 Daqmx Base 3.3 Cannot creat 2 or more channels on Windows mobile 6

Similar Messages

Maybe you are looking for