rayodyne

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 documenting automated test, measurement, data acquisition, and control systems using LabVIEW or LabVIEW RT. Semiconductor metrology candidates preferred. * Experience in Semiconductor metrology software applications preferred. Knowledge of Semiconductor communication protocols desirable. * Experienced with machine vision and pattern matching/recognition. Semiconductor metrology candidates preferred. * Experienced with motion control and vision systems for metrology equipment. * Knowledge of SEMI specifications covering all aspects of software desirable. Technical Requirements – Hardware * Broad knowledge of instrumentation and data acquisition technologies including Motion Control, IEEE-1394, USB, distributed I/O, GPIB, PXI, NI Data Acquisition, NI Modular Instruments, GigE Vision. * Strong hands-on hardware troubleshooting and software debugging skills. Technical Requirements – Software  * Experience using Source Code Control Systems (CVS/SVN) with LabVIEW * Familiar with integrating 3rd party Instrument Drivers, DLLs and .NET objects into LabVIEW * Familiar with all current LabVIEW application architectures * Experience developing LabVIEW software using National Instruments APIs: NI-Vision, NI-IMAQ, NI-DAQmx, NI-DAQ, NI-FieldPoint * Experience with connecting LabVIEW to database management systems preferred, including MS SQL, Oracle, mySQL * Development experience with other environments: LabWindows/CVI, TestStand, C, C++, C#, embedded programming or scripting (Tcl, Perl) desirable. * Expert trouble shooting and debug skills at instrument driver and API level. Familiar with NI-SPY, NI-MAX, API sniffers Skills Requirements  * Interest in playing a lead role in architecture and development. * Outgoing personality with good communication skills, both written and verbal. * Experience creating documentation for large scale LabVIEW projects spanning VI descriptions, system diagrams, schematic diagrams. * Pursue certifications, including NI Certified LabVIEW Architect. * Experience writing system and software requirements specifications a plus. * Evaluate requirements specifications and develop technical proposals. * Experience with project driven approach to development using standard IEEE software methodologies. EDUCATION REQUIREMENTS  * BS in Science or Engineering. MS or PhD a plus. * National Instruments Certified LabVIEW Developer (preferred or equivalent industry experience) * National Instruments Certified Architect (highly desired) Please note at this time we are only able to accept candidates with US Green Card or transferable H1-B status. To apply for a position, please email your resume to graeme.cloughley@metrosol.com. You may also apply by sending your resume to Metrosol, Inc., Attn: Human Resources, 2101 Donley Drive, #101, Austin TX 78758.

QUOTE (rayodyne @ Apr 23 2009, 12:38 PM) No takers? -Chroma

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 Creator. Imports System Imports System.Management Imports System.Windows.Forms Namespace WMISample Public Class MyWMIQuery Public Overloads Shared Function Main() As Integer Try Dim searcher As New ManagementObjectSearcher( _ "root\WMI", _ "SELECT * FROM MSStorageDriver_ATAPISmartData") For Each queryObj As ManagementObject in searcher.Get() Console.WriteLine("-----------------------------------") Console.WriteLine("MSStorageDriver_ATAPISmartData instance") Console.WriteLine("-----------------------------------") If queryObj("VendorSpecific") Is Nothing Then Console.WriteLine("VendorSpecific: {0}", queryObj("VendorSpecific")) Else Dim arrVendorSpecific As Byte() arrVendorSpecific = queryObj("VendorSpecific") For Each arrValue As Byte In arrVendorSpecific Console.WriteLine("VendorSpecific: {0}", arrValue) Next End If Next Catch err As ManagementException MessageBox.Show("An error occurred while querying for WMI data: " & err.Message) End Try End Function End Class End Namespace The specifics is translating the two lines, Dim arrVendorSpecific As Byte(), arrVendorSpecific = queryObj("VendorSpecific") into something meaningful that LabVIEW can understand. Ultimately, we should receive a byte array and be able to select the elements as appropriate from this. Can someone more savvy with .NET and LabVIEW integration help me sleep better at night? Regards, Chroma

QUOTE (Aristos Queue @ Mar 26 2009, 12:30 AM) Many thanks, that's got me started again... -Chroma

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 exposed in anyway with VI Server? Regards, ChromaBurst

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 LabVIEW binary into a .NET application, so as to make the UI appear seamless. This is not our preferred route, but may prevent us from completely re-writing the UI in LabVIEW, otherwise we will need to heavily customize our .NET UI to support message passing and live camera output via NI Vision. Any thoughts? -rayodyne

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

QUOTE (Darren @ Aug 17 2008, 09:38 PM) The standard error list dialog. See attached. -Chroma

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

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

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.

QUOTE(rayodyne @ Jan 28 2008, 09:59 AM) This position is still accepting resumes/CVs.

QUOTE(rayodyne @ Jan 21 2008, 03:19 PM) This position is still accepting resumes/CVs.

QUOTE(rayodyne @ Jan 16 2008, 11:57 AM) This position is still accepting resumes/CVs.

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 acquisition, and control systems using LabVIEW or LabVIEW RT. Semiconductor metrology candidates preferred. Experience in Semiconductor metrology software applications preferred. Knowledge of Semiconductor communication protocols desirable. Experienced with machine vision and pattern matching/recognition. Semiconductor metrology candidates preferred. Experienced with motion control and vision systems for metrology equipment. Knowledge of SEMI specifications covering all aspects of software desirable. Technical Requirements – Hardware Broad knowledge of instrumentation and data acquisition technologies including Motion Control, IEEE-1394, USB, distributed I/O, GPIB, PXI, NI Data Acquisition, NI Modular Instruments, GigE Vision. Strong hands-on hardware troubleshooting and software debugging skills. Technical Requirements – Software  Experience using Source Code Control Systems (CVS/SVN) with LabVIEW Familiar with integrating 3rd party Instrument Drivers, DLLs and .NET objects into LabVIEW Familiar with all current LabVIEW application architectures Experience developing LabVIEW software using National Instruments APIs: NI-Vision, NI-IMAQ, NI-DAQmx, NI-DAQ, NI-FieldPoint Experience with connecting LabVIEW to database management systems preferred, including MS SQL, Oracle, mySQL Development experience with other environments: LabWindows/CVI, TestStand, C, C++, C#, embedded programming or scripting (Tcl, Perl) desirable. Expert trouble shooting and debug skills at instrument driver and API level. Familiar with NI-SPY, NI-MAX, API sniffers Skills Requirements  Interest in playing a lead role in architecture and development. Outgoing personality with good communication skills, both written and verbal. Experience creating documentation for large scale LabVIEW projects spanning VI descriptions, system diagrams, schematic diagrams. Pursue certifications, including NI Certified LabVIEW Architect. Experience writing system and software requirements specifications a plus. Evaluate requirements specifications and develop technical proposals. Experience with project driven approach to development using standard IEEE software methodologies. EDUCATION REQUIREMENTS  BS in Science or Engineering. MS or PhD a plus. National Instruments Certified LabVIEW Developer (preferred or equivalent industry experience) National Instruments Certified Architect (highly desired) To apply for a position, please email your resume to graeme.cloughley@metrosol.com. You may also apply by sending your resume to Metrosol, Inc., Attn: Human Resources, 2101 Donley Drive, #101, Austin TX 78758.

Hello there, I was reading with interest the NI LabVIEW forum posting "How the LabVIEW exposes its controls to the Visual Test/automated test tools?". This posting is six years old and I'm trying to gauge what developers are using for automated testing of GUIs out there. I'm looking for an environment that supports LabVIEW GUI controls and dialogs natively - if you have to spend considerable time making LabVIEW "fit" then it's prorbably not worth the effort. Can anyone share some experiences with different types of products? Rational/IBM's Visual Test dones't seem to be sold anymore but VistaTask (http://www.vista-software.com) looks promising... -Chroma

Hello there, I was reading with interest the NI LabVIEW forum posting "How the LabVIEW exposes its controls to the Visual Test/automated test tools?". This posting is six years old and I'm trying to gauge what developers are using for automated testing of GUIs out there. I'm looking for an environment that supports LabVIEW GUI controls and dialogs natively - if you have to spend considerable time making LabVIEW "fit" then it's prorbably not worth the effort. Can anyone share some experiences with different types of products? Rational/IBM's Visual Test dones't seem to be sold anymore but VistaTask (http://www.vista-software.com) looks promising... -Chroma

From this post on the NI forum also: NI forum - similar question for PXI

Hello there, Was looking for some Visio stencils to help our documentation process. I could only find this company offering anything near what we need, but look at the price!!! Agilent Shapes R&S Shapes Any suggestions/experiences for a cheaper solution for T&M? -Chroma

Many thanks for your prompt reply - greatly appreciated! Yes, I'll be a pain (sorry) and ask do you have a LV 7.x version? Best regards, Chroma

[quote name='Lars-G

We're currently evaluating whether LuVIEW can indeed be used as a "TestStand Lite" but we're having problems trying to demonstrate a simple poll of a GPIB instrument and serial device. We'd like to run a Lua script that calls LabVIEW VIs, the Lua script would contain the configuration parameters for the LabVIEW VIs. Does anyone have a simple hardware example showing the appropriate use of the VItemplates? I have to commend CIT, the documentation supplied is excellent (especially for the SCADA example) but we can't seem to find a hardware example. Regards, Chroma