Francois Normandin

QUOTE (LV_FPGA_SE @ Jul 4 2008, 12:56 PM) In Quebec, some of us refer to Canada Day as being "Moving Day". It ends up being a good day to drink beers but for other reasons... Is there any other place in the world where people all move on the same date?

QUOTE (LV_FPGA_SE @ Jul 4 2008, 12:56 PM) In Quebec, some of us refer to Canada Day as being "Moving Day". It ends up being a good day to drink beers but for other reasons... Is there any other place in the world where people all move on the same date?

The forums are awfully quiet when americans are too busy drinking beers... Cheers to you all. :beer:

The forums are awfully quiet when americans are too busy drinking beers... Cheers to you all. :beer:

QUOTE (Aristos Queue @ Jul 3 2008, 01:51 PM) Point taken.

QUOTE (Aristos Queue @ Jul 2 2008, 04:57 PM) Do I understand that you recommend to classify Public/Protected/Private VIs only using virtual folders in project file and not real folders? Is there a known issue with this particular arrangement? Or perhaps a future one? :ninja: I normally like to keep my disk folders about the same as my project files... As Ben says, it's never too late to stop breaking the rules...

Not to mention that some good replies can increase the SNR even in a sea of noise more than others... Actually, SNR should be measured by how much the answers are on target compared with background chatting. Take the spectrum of a radio signal and you'll find 99% of the frequencies are just noise, but then there are three peaks with 30dB+ SNR that stand out of the background. We wouldn't say it's got a -20dB SNR... To keep with the analogy, the initial post would be the carrier wave, and side bands will deconvolute in topic replies... Of course, we also reject one of the sidebands (off-topic chat) because it contains no new information than what's provided by the first, without necessarily decreasing the SNR.

QUOTE (ragglefrock @ Jul 2 2008, 04:26 PM) I agree with these rules. I've created a "_class" folder where I store all my classes. One sub-directory per class. It acts as a user.lib and I add this main directory to the palette for quick access.

QUOTE (neB @ Jul 2 2008, 10:31 AM) I know that you can clone a GOOP class just by right-clicking. Not sure if "Save As" would be sufficient for you if not using GOOP. Would inheritance hierarchy be preserved? I haven't tried it yet. http://lavag.org/old_files/monthly_07_2008/post-10515-1215009934.jpg' target="_blank">

QUOTE (JasonXCX @ Jul 2 2008, 07:02 AM) I initially thought it was a nice application of shape-memory alloys! Well, I'm disappointed...

QUOTE (Justin Goeres @ Jun 30 2008, 11:29 AM) I've used partial transparency to get rid of complaints that one could not see his whole program while I kept a login/logout window hovering as a front-most app. By having 50% transparency, he could see what happened in the background and that effectively stopped the whining. I would probably be happy with background transparency. When the title bar disappears as well, you don't have access to menu or buttons, which could be annoying. One application I see (however trivial) would be to make nice intros while loading. We could have something else than the usual rectangle window. But hey, that's not something I'd fight for... :2cents:

You can download the latest drivers from NI website.

QUOTE (odsnot @ Jun 26 2008, 11:55 PM) As Karrisap mentions, you've got some missing vis because you have not all DAQ drivers installed. I get the same problem you do at home because I don't have any DAQ installed on that computer. It's looking for zadvd.llb that should be installed in vi.lib folder. Install your drivers and you should have no problem loading your code. http://lavag.org/old_files/monthly_06_2008/post-10515-1214568311.jpg' target="_blank">

QUOTE (odsnot @ Jun 26 2008, 10:31 PM) Post your code... How can we help otherwise?

QUOTE (Elktro @ Jun 26 2008, 11:41 AM) well we don't see that part in the code you supplied... from what I could tell, it would execute every loop except the first.

Well, from the part of your program you've shown, num2 doesn't change and will always be equal to abc. num3 = num2 - abc is therefore always 0... so function2(num3) is really while(stop()){do{function2(0)}}. But I see suspension marks which means num2 must change somehow as a result of function2. Here is the equivalent LabVIEW code for your program. It is not as you should do it, just a quick translation of your program as is. I suggest your get abc = function() out of the loop and initialize num2 with it. Then, remove the case structure as your variables will already be initialized.

QUOTE (Aristos Queue @ Jun 23 2008, 01:17 AM) I only browsed through the 8.5 buglist... should have checked in 8.2: Funky LV Class wire QUOTE (Aristos Queue @ Jun 23 2008, 01:17 AM) b) A class is a library. So is an Xcontrol (.xctl) and a StateChart (.lvsc). The "link to" option should work for any of the library types, even though the radio button explicitly mentions .lvlib. If it doesn't work, let me know. Works fine. thanks

I've created a palette with one of my LVOOP classes. After documenting it, I checked with context help and noticed that the class wires were different than in my program. The context help from VI in the block diagram is fine. The one from the palette is wrong (see reference in/out). Can anybody verify/confirm this behavior? I'm using Windows Vista and running LabVIEW 8.5. The class was programmed using GOOP3 from Endevo, but I checked the problem using a Native LabVIEW class also. The wire display seems always the same from the palette (red & black), whatever its design in the class. Here are some picts that illustrate the problem. Correct display: Incorrect display: VI names are different. One refers to the VI inside its class (Password.lvclass:Password_Create.vi) and the palette context help gives only the VI name (Password_Create.vi). That's what makes me wonder if it's a bug or just an expected side-effect of referencing my method outside of its class context... Any thoughts? Maybe LabVIEW 9 needs to have lvclass as an option in the Insert Subpalette menu: :thumbup:

Have a look at the wiki page for tab controls. http://wiki.lavag.org/TAB_Control

Sorry, I didn't want to seem patronizing. Most people posting these kind of requests on LAVA didn't look in the manual prior to asking the question. Since it's not the case here, my apologies. I think your equipment is probably damaged. Do you know if there were any surges before the equipment began to be faulty? I had a similar experience with a Keithley Electrometer (K6517) where a student shorted the high voltage source (1000V) to the current measurement (uA range, no protections). The first time, the equipment protected itself (probably through some capacitive protection) and the compliance error disappeared the next day, everything coming back to normal as if it never happened. We were not so lucky the second time (a year later...) and we had to send the unit to Keithley for repairs. If you're confident about opening the case (warranty issues maybe?), then you can check for ground faults. There is usually a grounded metallic casing on the acquisition board to protect the user from high voltages when he sneaks in. When the short happened in our lab, that case became permanently at -300V! If you can find such a faulty behavior, then there would be no doubt about the way to proceed next. Good luck...

I heard a rumor that NI Week convention center will be equipped with those...

Hi Ranjini, Here's the Source Manual Reference manual extract (page 3-18) for your condition: http://www.keithley.com/products/locurrhir...487/Documents#6 Compliance indication At any time, it is possible that the voltage source will go into compliance (current limit reached). Should this situation occur, the OCOMP annunciator (Output Compliance) will flash and the displayed voltage value for readings of less than 6½ digits will alternate between showing the value and displaying "CMPL". If you are in a menu where the voltage source value is not shown on the right-most four characters of the display, only the flashing OCOMP annunciator will be shown. It seems you're out-of-range. Maybe check the range of this 6487. If both 6487 should be the same range, verify both are set the same. [sENS:VOLT:RANG? + CURR:RANG?] It could also be a current-limit if you're using the voltage source (SOUR:VOLT:RANG? + CURR:RANG?), but if you're measuring voltage (sense), that is not the case. Hope this helps.

Hi Yren, Speech recognition is complex. Good luck! I'm not sure how well you can have LabVIEW decipher words from spectra acquired this way. If I were to attempt this, I'd probably try using a software that already does it, put the words it detects in a buffer and then read the buffer with LabVIEW. Then you can have your program trigger on specific words and actuate your motor... I might be completely wrong about this, but that must take real good signal analysis. I suspect most speech recognition softwares utilize existing libraries of subroutines. Maybe some of these are freely available and documented? You could definitely access those from within LabVIEW using ActiveX or dlls.

QUOTE (Thang Nguyen @ Jun 19 2008, 10:55 AM) Hello Thang, I'm not sure the reason why you get this error (incompatible state). I usually see errors with subpanels whenever I have not closed the subvi's front panel prior to attaching to subpanel, but that's not this particular error... Without your code, I can only guess why you have the error. I've attached some VI's that might help you figure out where the error comes from in your code. http://lavag.org/old_files/post-10515-1213891871.zip'>Download File:post-10515-1213891871.zip (saved for LabView 8.2)

QUOTE (jgcode @ Jun 19 2008, 01:05 AM) Hi JG, Are you referring to FP.Close method? If that's so, then it does not terminate the program. It just closes the front panel and leaves it running. The Abort method would work, but that's rather harsh to close a VI this way. For an about box, do you need a while loop? If you take only a user event frame with "Panel Close" as an option, whenever the user clicks on X, it will terminate and return control to your main app. http://lavag.org/old_files/monthly_06_2008/post-10515-1213853246.jpg' target="_blank">