Francois Normandin

QUOTE (Eugen Graf @ Jun 13 2008, 03:50 PM) Now I understand your question... sorry about my stupid answer! Duh.

You have to Disconnect your Type Def. You must have erased the CTL or moved it somewhere else. EDIT: You also have errors in "Core_Start.vi", but that I'm sure you can fix.

I could not crash LabVIEW 8.5 with the active reference equality...

Well, "equals to" must have a polymorphic behavior to account for this because refnums cannot be concanated to strings... Therefore, it is especially built-in this function. As Yen says, it could be a bug or a development feature that was forgotten and not cleaned-up.

QUOTE (tcplomp @ Jun 13 2008, 01:35 AM) Hi Ton, Private VI scripting? That's why this VI was password-protected...

Thanks AQ! Works like a charm. :thumbup: Follow-up for the benefit of others: This VI is called by "GetItemInfo.vi" which is unprotected. Therefore, that's where you want to change the default value (2) to whichever you'd like... EDIT: Thanks PJM. I kind of found out too late that I was able to see the connector pane simply by dropping the VI on a block diagram :headbang: ! but I didn't have the code for getting the most recent projects list. I'm sure it's in itself not too hard to find the right folder or registry entry to get it... But as you say, AQ's solution is much simpler. thanks all.

QUOTE (zhpipo16 @ Jun 12 2008, 11:10 AM) Useful information could be about what is the error code the equipment returns. When you send the trac:read? command, do you get an answer from equipment or a timeout? Do you get an empty buffer? You can use status bytes information to further diagnose your problem.

Hi everybody, I'd like to make some modifications to my Getting Started Window Screen. I read AQ's topic about Christina's blog Eye on VIs for editing XML file to do just that. However, I'd like to change the ratio of lvproj vs VIs in the Open section. Since I always code using projects, I'd like to get rid of the VIs & CTLs. I think "GetRecentlyUsedFiles.vi" is the VI that does that trick, but it's password-protected :ninja: . It is set to output the links of the two most recent lvproj and the rest are VIs & CTLs. How can I change it? I don't know the connector pane configuration, so I can't guess what I would need to replace this VI with. At the moment, that would be a shot in the dark. Anyway it's part of a lvlib, so I doubt I could replace it with my own without causing some corruption... Any comments?

QUOTE (neB @ Jun 9 2008, 05:57 PM) That's a quote I'll remember... :laugh:

You can set the property of your VI to "Run when opened". Each time you'll open the VI, it will run. Select File/VI Properties Then choose "Execution" in the category at the top of the window. Check the box "Run when opened". mross' explanations are still true... you have to make sure your VI will be in the correct Default state when you launch, otherwise it will execute and finish before you know it.

I'm still a newbie at LVOOP too , but it is my understanding that you can use "Protected" for Dynamically dispatched VI's. Protected would be "Private" to everybody except for child classes. You can override protected methods.

QUOTE (Michael_Aivaliotis @ Jun 4 2008, 04:23 PM) Got the same thing. It IS annoying. As if there is no way anymore to browse through some new content without getting a feedback. Foe example, I don't use FPGA's at work... but can I watch the webinar without being asked if I need help with this? It reminds me of a movie some years ago where Tom Cruise walks into a store and an hologram appears in front of him saying: "Hello M. X, last time you came here was three weeks ago and you bought a tie. Would you like a shirt to complete your outfit?"

QUOTE (zhpipo16 @ Jun 3 2008, 06:26 PM) The equipment will answer with a string, which you fetch with the command trac:data?. You have to format this string into useful data (array of numbers) that can be sent to a graph or output to a file at your convenience. At this point, I strongly suggest you take a look at LabVIEW tutorials. They take a few hours to go through, but you'll gain a lot of experience about the language. The "pink" case is an indicator. I cannot help you if you don't have a basic knowledge of LabVIEW. I don't want to do your homework if you know what I mean... (No offense meant )

QUOTE (zhpipo16 @ Jun 3 2008, 12:43 PM) First, you should always post your VIs in a library or Zip file when they contain dependencies (Keithley driver in this case). Second, I suggest you use the VISA palette. What you need is to convert a string to an array of floats. Look at the String palette. There are fine tutorials available in the Help of LabVIEW. Download File:post-10515-1212524294.vi (LV 8.5)

QUOTE (rolfk @ Jun 3 2008, 02:31 AM) You're quite right... I'm not very good at using APIs really... but the definition of "EnumWindow" seems to imply that we could get a list of windows with their Z-order, hence order of creation... Specifying which windows are child windows (ActiveX instance) of a certain parent (VI), I think it would be the way to go to identify all of them. Then, there remains the problem of association with the correct window. Seems to me like crelf's suggestion is pertinent: QUOTE (crelf @ Jun 2 2008, 03:59 PM) Is there anyone from NI here with the inside knowledge to this? Does it even have a window title? QUOTE (neB @ Jun 2 2008, 03:54 PM) What is the Window Title for the 3d-graph container for use with that function? I can't even venture a guess. Ben Could it be as simple as Label Name??? EDIT: NOPE! It isn't...

QUOTE (zhpipo16 @ Jun 2 2008, 06:38 PM) TRAC:DATA? is the last command. Convert the result (string, probably comma-separated values) and send to graph.

QUOTE (zhpipo16 @ Jun 2 2008, 05:27 PM) Keithley's website mentions a 1000 readings/s maximum. It is unlikely that you could trigger individual measurements at that rate... You're best option is to use buffered acquisition. Check the manual page section C to get sample programs. You should use the TRACE commands to store TRIG:DEL 0 (Set trigger delay to zero seconds.) TRIG:COUN 2000 (Set trigger count to 2000.) NPLC .01 (Set integration rate to .01 PLC.) DISP:ENAB OFF (Turn display off.) TRAC:POIN 2000 (Set buffer size to 2000.) TRAC:CLE (Clear buffer.) TRAC:FEED:CONT NEXT (Set storage control to start on next reading.) STAT:MEAS:ENAB 512 (Enable buffer full measurement event.) *SRE 1 (Enable SRQ on buffer full measurement event.) *OPC? (Operation complete query) INIT (Start taking and storing readings.) DISP:ENAB ON (Turn display back on.) TRAC:DATA? (Request data from buffer.)

<p style="text-align: left;"><a class="noborder" href="http://lavag.org/old_files/monthly_06_2008/post-10515-1212439546.jpg" target="_blank"></a></p> Building on crelf's input, I used the GetTopWindow() to get the child window's handle (CW Graph) of the current VI, without need of CW graph window title. Download File:post-10515-1212439407.vi (LabVIEW 8.5)

Wouldn't there be an API for a list of all windows currently opened?

You can get a driver from NI website: <http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=239>

There is a VI in Vision toolkit that gets the hWnd located in "..\vi.lib\Vision\Extlibsp.llb\IMAQ Get Window Handle.vi" However, I'm not sure it's possible to get the hWnd this way because it needs a "window number" which I think has to be a window previously opened by LabVIEW Vision. You might need to use Windows APIs for that.

Hello Roy, Welcome to the LAVA community. You'll find that the level of LabVIEW awareness is pretty high here. Some will call it a good signal-to-noise ratio... Having been around for a short while, I can certainly testify that these pages are addictive! Hope you find lots of good things to improve your skills.

Awesome. However, if it's going to be put on the t-shirt, there shouldn't be a broken arrow...

QUOTE (JFM @ May 28 2008, 01:29 AM) Indeed, each time you append some data to file, the "Set Position" will be at the end of what you wrote. If that was at the end of the file, you'll still be at the end of the file without any need to specify it. You can use the "Set Position" VI when you want to change some data in a file without rewriting all of it (changing a status bit or else...). Also, you might want to save your bits as a number instead of text "01010101". Your code & file will both be more compact, and it's easy to convert back to array of bits if needed. See attached picture. http://lavag.org/old_files/monthly_05_2008/post-10515-1211978264.jpg' target="_blank"> EDIT: It took me too long to write! Justin beat me to it... :-)

You need to convert types to be compatible with the datatype accepted by the write.vi (or any VI for that matter). If you choose "string" as your paradigm, then convert everything to string and concatenate in a format you want (tabulated, coma-separated values, custom, etc.) Then write to file. Browse through the palette for "string" manipulations. You will find many fonctions to help you do just that. LabVIEW tutorials and help file contain many examples to get you started with. If you want more specific help, you should show us what you've done so far by uploading a VI with your best effort or posting a picture of your block diagram.