ShaunR

Or-ing "THE" =0.

Just OR the =0 with the stop and it will work without an extra occurrence and without a timeout..It is a sequencing issue rather than a race condition-as with AQs version.

I stand correct4ed (when did they add that then?) IMHO this is how the other primitives should behave (and that includes diagram, project and control refs). I've lost count of the number of times I have had to correct others' code because the refs aren't closed. It is these primitives that are counter and intuitive rather than the occurrence. Oh for the days when Labview meant you didn't have to worry about memory leaks. Seems to me that they work similarly to a notifier (since they have a timeout) without the pit-fall of memory leaks.

Because the local variable will be evaluated well before the first loop reaches the large number and will present a FALSE to the stop terminal. Everything (in the second loop) then waits for the occurance. Once Loop 1 actually fires; loop 2 then proceeds with the FALSE, goes around again and then waits, once more, on the occurance-which never arrives since the first loop has already terminated. This is why no-one uses them. Its too easy to get race conditions that hang your app because they don't have a time-out. It will work correctly IF you put the occurance and the local into a sequence structure that guarantees the local is read AFTER the occurance (another reason no-one uses them since they don't have error terminals and forces you to use those pesky sequence structures.)

That won't work.

I just set the block diagram background colour in the preferences. I use a different colour for each LV version so I'm aware of what version I'm in. I also use it as a "completion" indicator". I start out with all the diagram in a colour and set cases, frames etc it back to white once that frame/module or whatever is completed. That way I (or my colleagues) can see at a glance where I need to do some more work. Yes. It sticks with the vi.

Should you really be asking that question?

The byte sequence will change every re-compile-so it is unlikely to persist exactly as in that post across versions or even the same versions with different bitness. But at some point you have to say "Is it? or Isn't it? a correct password" and finding it is easier if there is a dialogue since you know where to start. I think most of NIs password protected files are purely to hide the terrible coding. Not that bothered if someone sees mine.

Ahh. I see what you mean (I thought it was at least in Dispatcher-have to check) Here they are).

There is nothing special about the clear error. It is just a control and indicator unwired. These are my versions of the clear error and clear specific error (you can find them in many of my submissions to the CR) that uses far less realestate and can be placed between property nodes (and similar) without having to route wires around.

Just one final thought on this (probably not relevant). I have seen exactly what you describe when a machine has Bluetooth . The 5- 8 second freezes go away when the Bluetooth adapter is disabled. I never got to the bottom of this since the machine didn't need Bluetooth, so I just disabled it.

Good point...... Don't forget to press the "Generate" button to regenerate the product code in the version page if your copying an installer.

Not really.....but... The project file is xml. So in the past I have cut and pasted the section <Item Name="Build Specifications" Type="Build"> ..... </item> and it worked fine.

Yup. I do it the same way as sachsm.

I thought I already was . Isn't my name on an openG FP somewhere?

Naaah. I'd prefer it like like JGs. You would have made a huge profit in only 3 weeks.

I believe it is (or at least a wrapper for it). This is the prototype it (TCP Get Raw Net Object.vi) uses as the call to LabVIEW int32_t NCGetRawNetObject(uint32_t nc, uintptr_t *netobject); It is just a typecast to get the nc parm from the connection ID.

Well. there is an "Addons" palette. So shouldn't "Addons" be in there? I know your post is against top level folders but I also don't prefer bunching other tools in the labview installed locations as I prefer separation between the standard labview installed software and addons/toolkits. It's already a case that we have to drill down 3 or 4 layers of folders to find (for example) the TCPIP vis. It is that that causes menus to roam across the screen rather than having them further up the hierarchy. There is (as I have mentioned) the addons folder. There is also the User Libraries and Favourites on the top level which rarely have much in them...if anything. Better use of the top level palette folders would make more sense. But we are being told that we shouldn't use the User Libraries folder?

The execution systems consist of a number of (typically 4...up to 8) threads. In this respect, you are specifying a smaller "pool" of threads that labview should use for a particular VI or set of VIs rather than explicitly defining which threads things run in.

You can still use it, but show the caption instead of the label. I use a similar method for changing languages. Captions are not used nearly as frequently as they should be (IMHO)

I guess that by saying you are using the "Client Request Waveform" that you are actually polling for the wave forms rather than streaming. This is really bad for performance since you get double the amount of network latency. 16000 data points (assuming double precision numbers) equates to about 125KB. On a 100Mb connection you should be getting in the region of 60-80 updates per sec (10MB/125kB = 80). For an example of streaming waveforms, take a look at Transport.lvlib

All controls/indicators have a "visible" property.

Peak detection above or below waist? (Peaks above=female, peak below=male) Seriously though. I read somewhere that the fundamental frequencies for males voices are about 120Hz and for female are about 210Hz. so i expect Fourier is the way forward.

Labwindows is (essentially) ANSI C. But it is the packaged libraries you will have to learn since they are proprietary to NI. I would dive straight in with Labwindows (C doesn't have front panels for example) and any good book on C will do for the stuff in-between.

How about a pitch shifter (make people sound like they are on helium). If you google, there is even an example in labview.