crelf

QUOTE(Holograms2 @ Feb 12 2008, 07:54 AM) QUOTE(Holograms2 @ Feb 12 2008, 07:54 AM) ...calculating how 'round' the image is. That depends on what you mean by 'round' - the image, I assume, isn't round, but some feature in the image is? This will be a whole lot easier to discuss if you upload an example image or two.

QUOTE(Mihael @ Feb 11 2008, 07:24 AM) Glad to hear you got it up and running

QUOTE(Mihael @ Feb 10 2008, 08:44 AM) I can't help you with the GPIB issues, but the 8.0.1 -> 8.2.1 isn't really an update per se - it installs the new 8.2.1 version in parallel with the 8.0.1 version, so there should be a new entry in your start menu - try that.

QUOTE(i2dx @ Feb 8 2008, 03:47 AM) I agree :thumbup:

QUOTE(Daklu @ Feb 7 2008, 01:04 PM) Right - the tab control/indicator is just an enum that other controls can bind to on the front panel - that's really the only relationship they have. The tab constant is a block-diagram-only node, so it's not bound to anything else, so it can be freely used as an enum constant.

QUOTE(Darren @ Feb 6 2008, 06:29 PM) Ooooo - I'd forgotten about that method :)Thanks for everyone's suggestions, I'll do it Darren's way (errr, I mean, I'll suggest the foolish engineer do it Darren's way ) QUOTE(gleichman @ Feb 7 2008, 09:09 AM) Wouldn't it be easier to just go back to the old version stored in source code control server? Yes, yes it would, but was actually a very good reason that this update wasn't covered in our source code control system (most of the project was, just not this update). The reason? I can't tell you :ninja:

QUOTE(TiT @ Feb 7 2008, 03:28 AM) Make you own custom probe

This question is a little off-the-wall, but let's propose a hypothetical situation: some engineer was working on an old project - the code was in version 8, and the idiot engineer opened the code and edited it in 8.2. He/She then saved it in version 8.2. Now he/she didn't change all the VIs in the project, but it's a significant number of them. Rather that going through the process of opening them all up in 8.2, back-saving them to 8, he/she would like to scan the folders for files edited after a certain date and then, using some magical binary file editor, change the version stored inside the VI back to 8. The engineer knows that there's been no functionality added to the VI that depends on LabVIEW 8.2, and is kinda hoping that NI didn't change the VI binary format radically between 8 and 8.2, so is it possible to just change the few bits in the binary file that brand the VI's version? If so, anyone know where that would be? I'm (errr, the foolish engineer) could really use some help

QUOTE(Aristos Queue @ Feb 6 2008, 03:06 PM) My results: (note: I ran this in a VM, so the results might be a little skewed?) Open the "Test Main.vi". Run it and get the test time for LVClasses. Mine was around 57 msec. Now edit "LV Test Class.lvclass:Write Boolean.vi" to turn of dynamic dispatching. Run the test again. This time I got 20-40 msec. Save everything. Run the test. Still 20-40 msec. Close the project and reopen. Run the test again. This time I got 10 msec, which is the same as the time for clusters.

QUOTE(dblk22vball @ Feb 6 2008, 02:12 PM) Maybe I'm not understanding your diagram - is the red disk in the left side view diagram the same red disk in the top view diagrams?

QUOTE(Aristos Queue @ Feb 6 2008, 01:51 PM) Now there's something that belongs in the http://wiki.lavag.org/' target="_blank">LabVIEWwiki! Care to write a short article on your findings, jfazekas?

QUOTE(Justin Goeres @ Feb 6 2008, 12:08 PM) Amen!

QUOTE(Michael_Aivaliotis @ Feb 6 2008, 01:57 AM)

QUOTE(jed @ Feb 5 2008, 08:11 AM) Try the one in the top right of the page for now.QUOTE(crelf @ Feb 5 2008, 08:31 AM) Try the one in the top right of the page for now. I've added a "Common LAVA RSS Feed links" list at the bottom of this page. We can add more links as they become available.

QUOTE(stamatios @ Feb 4 2008, 05:44 PM) Please post your code here - that'll make it a lot easier to come up with answers.

QUOTE(Aristos Queue @ Feb 4 2008, 02:35 PM) Thanks Stephen - that's exactly what I needed.

QUOTE(deirdre @ Feb 4 2008, 12:32 PM) I'd be glad to - but what's innovative in 8.5 over last year's version? I'm not trying to be belligerent, but I'd actually like to know what qualifies it (and the other products that it's up against) for superior innovation?

QUOTE(Jim Kring @ Feb 3 2008, 01:19 AM) Love it! It confirms that internet-based viral media can be a powerful marketing force.

QUOTE(tcplomp @ Feb 2 2008, 03:17 PM) Yes, and no. I like them all in one view, but my viewer groups stuff by subject, and if each thread subject is pre-appended with it's LAVA category, then I'm 100%. Sorry, I though I'd made that clear in my first post. QUOTE(tcplomp @ Feb 2 2008, 03:17 PM) Can you tell me what your reader (thunderbird?) does with the ThinkinG RSS (http://thinkinging.com/feed/)? See image:

QUOTE(Gabi1 @ Feb 2 2008, 05:11 PM) Git yee to the movies! Or a local microbrew! Or a jazz club!

QUOTE(Yen @ Feb 2 2008, 01:40 PM) I don't think so - I think that suggests that the smiley has something to do with the next sentance

QUOTE(tcplomp @ Feb 2 2008, 02:53 PM) Am I missing something here?

QUOTE(Zhrani @ Feb 2 2008, 11:55 AM) Hello

QUOTE(Tim_S @ Feb 1 2008, 01:12 PM) It is, and it isn't. Like any boundary between two environments, there's going to be times where you need to know each of them intimately. That said, simple things (like showing the running sequence, selecting a sequence to run, etc) is pretty straight forward - have a look at the sample LabVIEW OIs that ship with TestStand. If you have intermediate TestStand and LabVIEW knowledge, then you should be able to work it out fairly quickly. If you need to do anything more advanced than that, then you'll need to put in some time to gain the knowledge - but that's true for just about anything the software engineering world...QUOTE(Tim_S @ Jan 29 2008, 07:59 PM) An option has been proposed to me to use LabVIEW as a front end for TestStand and the Data Supervisory and Control Module in a test executive application where there is data acquisition, OPC communication, reporting, calibration, error logging, parallel execution and test/limits configuration. From the very-upper-level description that you've given, it sounds like the option that's been given to you is a good idea. TestStand for the sequencing, DSC for OPC and config, LabVIEW for DAQ, Calibration (maybe the NI Cal is a better option?), and LabVIEw for the OI - sounds about right to me.

QUOTE(TobyD @ Dec 28 2007, 01:41 PM) I wonder if the original and reply could be different colours? I was thinking that different fonts or bold/notbold, italic/notitalic might be and idea, but they are things that can actually be changed by the poster, so that wouldn't be a good idea.