i2dx

You Are the Swedish Chef "Bork! Bork! Bork!" Your happy and energetic - with borderline manic tendencies. No one really gets you. And frankly, you don't even get you. But, you sure can whip up a great chocolate mousse The Muppet Personality Test http://www.blogthings.com/themuppetpersonalitytest/ :;

hmm ... there are several possibilities: you could use globals (yes, I can hear the others cry "ouch" ) or you could use queues to send a stop command, or an occurence ... but that all will be difficult to realize, if you use executables, because each lv-exe has it's own runtime-environment ... If you have LV 8 you could use shared variables ... so, my proposal was, to incorporate the movement and the measurement into one programm, to avoid all this hassle ...

did I allready tell you, that I was at an outpost of "Andechs" on Wednesday? (Andechser = bavarias most famous beer, brewed by Benedictine monks since 14xx) I guessed, we allready are? I like this guy! ... and I'd like to attatch: after 163 posts in 1,5 month @labviewforum.de, where I mostly answered questions at the level >> what is a cluster good for? <<, I start to believe HHs proliferate themselfes quicker then rabbits.

ouh, sorry, the "my website" link is in my signature, it is there with every post, and was not intended as a specific link to a solution for your problems. Ok, I don't know much abour your programm, but as far as you described it, it sounds to me, as if it would be the best way, to merge your two programms into one. I would programm the control of the turntable and the data-aquisition in one while loop, and all syncing problems are dust in the wind. Since you have developed the two parts (control of the turntable and the data aquisiton), it should be no problem, to merge them. Or - to cut a long story short: I would do this: Or did I miss the track completely?

come on, you and jim allways tried to cool me down @colinchristofferson you better not write "i2dx, LV8 and PDA-Module" in one message ouh, thank you :blush: ... there is still the NI-guy in me "do something good and talk a lot about it" (an advise of my former boss about how to make career @NI ) That's an argument I REALLY can understand ;-) (see one post above ...)

sometimes, it's so easy

what's about bavarian english? I have seen it, and I have hard about it, but never used any tools from there. I think providing tools for download is difficult. Newbes won't understand them. The pros have there very onw style how to work, and will maybe create their own tools. I have learned my lesson about that with my project duplicator tool. For my part, its essential for my work, but even with complete open sourcecode, nobody seems to be interested (never got feedback ...). Obviously it's allredy to special ... David had more luck with his tunnel wiring wizard, but this obviously matched the needs of many.

OT: this is an answer that would be worth 5 stars, if we had an user reputation system. real hard facts

thx for posting! by the way: which tool do you use to make the flash "screenshots" ?

just to bring up the thread again ... has noone else yet experienced this behaviour? has noone a tip for me? :sob:

I have experienced this bug, too, and I have allready informed the NI support. In my case it simply was an empty tunnel on the right side of a while loop, which remained from a "replace with tunnels" operation on a shift register. It's hard to find, because, it's just a little black dot on the dark frame of the while loop and of course, because the error list is empty. As far as I know there is allready a CAR createt about that bug. BTW: this only happens in LV 8.0.1. I have not checked, if it is still there in 8.0.1 ...

Hello folks, I have - again - a Problem with LV8. I am about to release a new version of my ADO-Toolkit (1.5) and I experience some problems, regarding the palette set: I have developed the new version on my Laptop with LV 7.1. After finishing the LV 7.1 Version, I copied the ADO-Toolkit folder from the LV 7.1 vi.lib/addons directory to the LV 8.0 vi.lib/addons directory and incorporated the LV8 specific code. I started LV 8.0.1 and the palette-set is the same as in LV 7.1 (on my laptop). I copied the LV 7.1 Toolkit from the Laptop to LV7.1 on my PC and everything was fine. But when I copied the LV 8.0.1 version from my Laptop to my PC, I got the palette-view in LV8 of ADO-Tool V1.4.1, which was "installed" on this machine before the "update" to 1.5, and I can not figure out, how to tell LabVIEW 8 to use the new Palette view What I have tried already: (with closed LabVIEW) replaced the ADO-Toolkit folder in vi.lib/addons with the new one (ADO-Tool 1.5/LV8.0.1 from the laptop), started LabVIEW 8 => old palette set (with closed LabVIEW) deleted the ADO-Toolkit folder in the vi.lib/addons directory, started LV8 --> edit palette set (without making any changes) & save chances (the ADO-Toolkit sub palette was removed automatically, not even "Addons" was there...), closed LabVIEW --> copied the new ADO-Toolkit folder (ADO-Tool 1.5/LV8.0.1) into the vi.lib/addons directory, started LabVIEW, the ADO-Toolkit palette was there again, but with the palette set of the old (1.4.1) version. I found a post at forums.ni.com that says: you have to copy the dir.mnu files in the "menus" or "menus/default" subdir of LV 8. I did, but nothing changes, I have still the old palette set. The really strange thing is: On my Laptop all worked fine, as I expected, maybe because I copied it from LV 7.1? But I cannot get rid of the "old" palette view in LV8 on my PC. I really would appreciate if, if someone could give me a tip, how I can make sure, that the people, who download and use the ADO-Toolkit for LV 8, get the correct palette set. And I think, it's not only a problem for me, but for everyone, who wants to develop a toolkit. Thank you in advance, CB

hmmm ... I think: to be capable of 3D LabVIEW programming, you really need the USB 2.0 Brain Plug

if you expect answers from experts, you should ask expert questions. you do not ask an engineer, working in the space industry, either : "will that rocket fly?". but you maybe will ask him questions like: "do you use an open or closed loop control to keep the oxygen throuput stable at the main inlet valve?". (any my guess is, he will use closed loop ...) furthermore: snaping to michael will disqualify you to any further qualified answer. last but not least: michael was friendly based on his coffee index! have you ever thought about buying an "SENSEO" from Phillips? I've got one, and my coffee allways tastes wonderfull at weekend

I can only guess, but for me that sounds like a file size variable overflow. If they use an I32 as (internal) file size variable, they can store file sizes up to 2147483647 Bytes in that variable. If the file is bigger, the I32 will roll over and you will get weird results ... which would explain, that you have no problems with smaller files, but you get into trouble, when using files with a size above 2 GB ... Maybe you can check this out, by testing your SW with 2 files: one with a size of 2GB -1 Btye and the second with 2GB + 1 Byte

hmm ... but then he must have REALLY a lot of globals in his software. I usually use about 20 - 30 globals in a project. Most of them contain "system variables", which are written once at the programm start with things like: application path, path to database, is an exe, path to the ini file, and other programm specific configuration settings read from the ini.file ... and I never experienced any of the problems mentioned in the initial post. But I can imagine, if you make massive usage of globals to pass data between parallel while loops, there could be a problem. Besides: if you mention, that the CPU load goes up to 75% and you can reduce it to 4%, when using old style globals, my question is: are you shure you haven't programmed a race condition? I mean, the switch to the OSG foreces labview to call the OSG-instances one by one, and as far as I know LV makes it sure, that all instances are called in the one iteration before the next iteration starts, which inherentely prevents from race conditions. (did I make it clear what the point is? sorry, can't explain better [the coffee is bad this morning]...)

and I'd like to attach: if you buy an expensive DAQ-System from NI, you should NOT forget the signal conditioning. Inpropper signal conditioning can cause serious problems and you don't know what's going wrong. My advise is: get someone with the appropriate knowledgle about signal conditioning. Just selecting some SCC modules on the NI website will not be a good way ...

wellcome :-) then we are ex-co-workers. I was the one responsible for the NI Services websitem (as a side-job), and I developed the measx.com website when "we" got the "new name". Maybe you got the infamous "Most Experts Are Stoned" derivate from my logo?

wellcome the information you need, is in the registry. I can remember that an ex.coworker wrote an utility in LV to extract that information for exact this purpose you mentioned. I will try to catch him today and ask him, if he can give me the code!

go to the NI website and take a look at the list of Ni certified alliance partners (ni.com/alliance). I am sure, one of them is close to you and willing to help :-)

hmmm .... good objection what about that: a "copryright node", something similar to a e.g. disable structure, which can be "locked" with a password? Or what about a password protected VI, where you can choose, if the BD is viewable (but not editable) or not? (I think, that would be the easiest way to implement that ...)

I would be glad to see, if there were a possibility to add a copyright information to the Block Diagramm, which can only be removed with a password. It could look like e.g. the "Demo Version Branding". If you ask me why: I'd like to be sure, that the students from labviewforum.de do not pass out my demos as their own invention and you could easily brand a VI as Open Source, etc .... What do you think about that?

google told me, to take a look at that page :-) this adds also some explanation to my favourite "typedef bug(?)"