Jump to content

rayodyne

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0

About rayodyne

  • Rank
    Active
  1. http://www.metrosol.com GENERAL DESCRIPTION Responsible for software architecture, refactoring and design of Metrosol’s VUV software metrology solution. Serve as a leading developer as part of a small core team of LabVIEW developers. Play a role in defining and realizing customer specific software versions. Serve as the technical “go-to” person for all software related issues. WORK EXPERIENCE REQUIREMENTS Essentials  * 10+ years of experience developing automated test, measurement, data acquisition, and control systems * 5+ years of designing, developing, implementing, and docu
  2. QUOTE (rayodyne @ Apr 23 2009, 12:38 PM) No takers? -Chroma
  3. QUOTE (JdP @ Jun 28 2006, 05:07 AM) Hello there, I've read this post with much interest, however from the comments on the NI Forums and here at LAVA have never addressed how to access a byte array returned from the .NET ManagementBaseObject. All postings and examples (which I'm most thankful for!) have always referred to single string parameter output, from the System.Object (ToString) LabVIEW Invoke node. My problem is I'm not a .NET programmer and the literal translation of the .VB .NET, .VBS or C# is not as simple as one would hope. See attached screen shot example from WMI Code Creato
  4. QUOTE (Aristos Queue @ Mar 26 2009, 12:30 AM) Many thanks, that's got me started again... -Chroma
  5. Hello there, This has got my head-scratching... I'd like to generate a path list of all the vi.lib calls in my application for refactoring purposes. As a bonus, I'd also like to find all of the callers of each vi.lib VI. Using the VI Metrics tool, I was able to generate at least the the VI list by having my application in memory and then masking out the my application source directory by populating the "Exclude files in this folder from statistics" in the VI Metrics dialog. This at least gives me the VI name, is there a more programmatic solution to this problem - is the "Find" capability ex
  6. We in the position of consolidating a LabVIEW pass-through application that communicates with a .NET application via a .NET interface. The LabVIEW pass-through application talks in turn via TCP to our main tool application: .NET Application <=> LabVIEW pass-through application (binary) <=> TCP <=> LabVIEW main tool application (binary). We'd like to remove this pass-through application and provide native NI Vision functionality natively in the .NET application - which I believe we can do with NI Vision. I'd like to understand if anyone out there has been able to embed a Lab
  7. QUOTE (Darren @ Aug 18 2008, 02:14 PM) I deleted some wires in the Temp Sys Demo (8.2.1) top level and some sub-VIs, that's all. -Chroma
  8. QUOTE (Darren @ Aug 17 2008, 09:38 PM) The standard error list dialog. See attached. -Chroma
  9. I'm going through a first pass of upgrading our applications to 8.6 using the NI Labs VIA tool. So far, so good but I'd like to dump the current "Error List" LabVIEW 8.6 is complaining about. Does anyone know if this list can be dumped to file via the clipboard? The dialog is not consistent with the the LabVIEW "Find" dialog, thats allows content to be cut and pasted. -Chroma
  10. I don't how many times I've had to re-engineer LabVIEW code and trying to document critical areas of the code base. I'm suggesting the ability to dump the contents of the the "Search Results" dialog to text file - simple wouldn't you think? Any suggestions on how this file list may be dumped with LV 8.2.1 would be appreciated. -Chroma
  11. QUOTE (rayodyne @ Feb 3 2008, 12:45 PM) This position is still accepting resumes/CVs. Please note at this time we are only able to accept candidates with US Green Card or transferable H1-B status.
  12. QUOTE(rayodyne @ Jan 28 2008, 09:59 AM) This position is still accepting resumes/CVs.
  13. QUOTE(rayodyne @ Jan 21 2008, 03:19 PM) This position is still accepting resumes/CVs.
  14. QUOTE(rayodyne @ Jan 16 2008, 11:57 AM) This position is still accepting resumes/CVs.
  15. http://www.metrosol.com GENERAL DESCRIPTION Responsible for software architecture and design for Metrosol’s VUV metrology solution. Serve as development lead for small team of LabVIEW developers. Play a role in defining and realizing customer specific software versions. Serve as the technical “go-to” person for all software related issues. WORK EXPERIENCE REQUIREMENTS Essentials  10+ years of experience developing automated test, measurement, data acquisition, and control systems 5+ years of designing, developing, implementing, and documenting automated test, measurement, data acquisi
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.