i2dx

aehem ... does your machine have enough memory to load the file completely? if you dont have at least 6 GB Ram, it will be swapped anyway?! I think you have to work with the file pointers and pick out that data, you need in that moment.

whatever ... even if it is possible, what it is good for? I don't know how PharLab handles this calls and how it influences the determinism?

are there any special requirements to participate? I mean, I'd like to get my chance to swear during the development process, not after it's released any mybe a nitpicker like me can help to improve the product

I don't know, too, but I guess there is a reason, why you have do download and install megabytes of data to get the .NET framework running on your PC ... and I disbelieve that you will get it running without the registry. OK, you could maybe use some .NET controls, but what sould that be good for?

hmm, maybe you should try to get your wife under better control mine uses an old iBook G3 for Web/mail/etc ...

hmmm ... I use LV 7.1 / 8.0 on my laptop allmost every day (I have RT + PDA Module installed). Ok, it's not super fast, but it's ok ...

youpp on the last roadshow, I attended, there was one of the core LV developers, showing us a lot of "yet undocumented features" (that was nice ...) unluckily the PXI crashed, and he had to reboot and to restart LabVIEW after minutes, and a red face he smumbles: "it seems, that there is every toolkit we ever shipped installed on this machine" but to apologize this. I don't think its originally a problem of LabVIEW. There is much code which has to be loaded. The new PC hardware is that quick, that it depens on the HDD to push all that data into the RAM. If you have once started it, closed it and started it again, LV is ready in seconds. So it's up to the HDD manufacturers to fix the gap between the theoretically availiable transfer-rate (150mB/s with SATA, I guess?) and the real transfer rate ... OK, you can buy a ultra fast SCSI HDD for your workstation, but who wants a jet engine under his desktop?

besides, you could the the idea: hey, if I have allready VS2005 (and the standard edition is sufficient ...) I could try to write PDA Software with C# .... and I have to admitt, I did allready and it's not THAT difficult to get used to it ... if you think twice, you could get the impression, NI does not like the PDA Toolkit and would be glad to "shift" the users/developers to Microsoft? OK, I am a "impatient-quick-ranting user", but the PDA Toolkit isn't that bad! And to be honest: who really want's to care about datatype conversion when communicatig with TCP/IP between an PDA/C# Software and a PC/LabVIEW Software? I will give my local sales representative the appropriate input, when I meet him next time

a few days ago, I was browsing the NI FTP-Server for updates, and I found an Update to Version 8.0.1 for the PDA Module. Update Readme The bad news are: If you want Windows Mobile 5 Support, you need a Visual Studio 2005 License. I'm not very amused about that, because I think a toolset, which costs about 1200 Euros should contain all tools needed for developing and deploing Besides: VS 2005 Pro costs about 1200 euros, too ... What do you think about that? cheers, CB

I'd like to append, that I experienced timing problems with parallel loops in the PDA-Module, too. I did not track it down, and so I can not give any detailed advice, but last but not least, I came to the conclusion, that it's no good idea to use parallel while loops with the PDA Module. I experienced the problems, when I tried to use a "quite normal queued statemachine" on the pda ....

take a look at this post: Topic#2839

thanks a lot, PJM, you opened the door. first I got an error at the "to more specific class" node, where the "GObject" references are converted to SubVI references. But when I deleted the Refnum specifier, and created a new one - again with the SubVI-Class - it worked fine. :question: I added the property "VI Reference" into the loop and now I am able to get the VI References of ALL (including those in Disable Structures !) of the selected VI! I hope I will soon find the time to implement that into my Project duplicator tool :thumbup: Download File:post-885-1142452162.zip

COOOOOL

I know this bug VERY WELL! do you use a unflatten from string somewhere in your PDA app, where you unflatten a typedef'ed cluster?

here it is: PWM with Digital Output

@michael: my cofee tastes terrible this morning, and I should be at work allready, but ... it is an easy task, and it should be done quickly - with the adequate basic know how, which you can get from the --> example finder (help -> find examples) and the --> quick start tutorial (C:\Programm Files\National Instruments\LabVIEW XXX\manuals\gtstrtlv.pdf) one of the cheapest (and easy to use) DAQ devices is a NI-USB-6008, which should provide sufficient accuracy for a PT 100, if you want to use a thermocouple, you need a device with a better ADC ...

cool! Nice tip. I have allready made a suggestion at the "NI wish-list", that it sould be possible to create "derivates" from one build spec, e.g. the one time, you want to build a full installer, or an exe with all support files, the other time, you just want to update the exe file, or you want to update the exe and specific support files .... etc. I also wrote in my suggestion, that the build number should count up automatically and there should be a system variable, containing the actual build number. Maybe it's a little bit difficult to syncronize the build count among the derivates, but hey, they created labview, that task should be easy to them [edit: why the heck, do I see the typos not until I have posted the message? maybe I need a >post< and a >really post< button - yes, I know there's a preview button ...]

not all, I did not want to harass them ;-) but at least ... I know allmost all AEs in the german support center. I am sure, they all wish they were in holliday, when I call again. One support request was open allmost 6 month, until they could reproduce and find a solution. By the way: (I think I never posted it here ...) [and michael will kill me, because I do not keep the threads clean, again] if you ever get an error -89130 on your PXI, when trying to route a signal to one of the PXI-Trigger-Lines, it means that your application has started before the DAQmx-driver has been completey loaded. But starting the Routing forces the DAQmx driver to load, so ingnore that error, reset the device and do it again (with maybe 10 seconds WaitTime) ...

remove all the VIs in "dynamic VIs and Support VIs", except this ones, you call via VI-Server during Runtime. The subVIs of the MainVI are included automatically to the executable. As the warning tells you, you can't include a polymorpic VI as a dynamic VI, because LV needs to know which instance to call. The polymorpic VI itself is a "empty hull" ...

no, I do not remember the days before UNDO - what a luck. And I have to admit - counted in Guru-years - I am still a newbie

thanks a lot! how old are you? I'm 0x22! - and i love the hex-system since I am 0x1d

Whow! Jim, you have found the BEST method ever to obfuscate your code. :-) Is it correct, that the "case selector" is NOT floating? what happens, if you put it inside a case and click the "next case" arrow?

thank's a lot, guys! i'll check it out today evening ...

I don't think it's a problem with the ADO-Toolkit itself. As far as I understand the warning, you try to use a polymorphic VI as startup VI. And especially using DB Variant to Data.vi as startup VI makes absolutely no sense to me. Maybe there is an error in your buildscrpit? I am allmost sure, you do not want to use that VI as startup VI, or I am on the wrong track.

nice tip! thank you. I found out that there is a "new" method for lvlibs, but I had no time yet to implement that anyway ... thank you for your feedback. You are the first one (except the 5 stars I got from anonymous ...) so I really appreciate it. I tried to improve it a little bit today, but I had to figure out the scripting property "SubVIs" is giving back an empty array ... [posted here] That would be extremely helpful to catch these SubVIs, which are in disable structures, and if I could catch the VIs in disable structures, I could put the dynamic VIs in a disable structure and copy them with the structure ...