Jump to content

rayodyne

Members
 View Profile  See their activity

  • Posts

    22

  • Joined

  • Last visited

 Content Type 

Posts posted by rayodyne

  1. Open Position at Metrosol, Inc., Austin, TX, Senior LabVIEW Systems

    in Job Listings

    Posted

    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.

  2. Use of WMI in LabVIEW

    in Calling External Code

    Posted

    QUOTE (rayodyne @ Apr 23 2009, 12:38 PM)

    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

    No takers?

    -Chroma

  3. Use of WMI in LabVIEW

    in Calling External Code

    Posted

    QUOTE (JdP @ Jun 28 2006, 05:07 AM)

    Hello Osvaldo,

    Thanks for posting this executable file. It is a very easy and simple solution to get the Id of the hard disk. The only problem I've seen is that the output of the command is not direct so I must use String functions to get the HardDisk_Id that is the only what I want.

    Thanks again.

    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

  5. How to document vi.lib calls in your LabVIEW Application (Find>>Select

    in Application Design & Architecture

    Posted

    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

  6. Embedding a LabVIEW Binary in a .NET Application?

    in Application Builder, Installers and code distribution

    Posted

    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

  7. Migration from 8.2.1 to 8.6 with NI Labs (VIA) Tool

    in Development Environment (IDE)

    Posted

    QUOTE (Darren @ Aug 18 2008, 02:14 PM)

    Thanks for the clarification. Unfortunately, there is currently no way to export the Error List contents. It does seem like a useful suggestion, though...I recommend you submit this idea to the http://digital.ni.com/applications/psc.nsf/default?OpenForm' target="_blank">Product Suggestion Center.

    -D

    P.S. - I'm also curious about the broken VIs...were they unbroken in 8.5, but broken in 8.6? What specifically is wrong on their diagrams? Are there toolkits you have installed in 8.5 that you don't have installed in 8.6?

    I deleted some wires in the Temp Sys Demo (8.2.1) top level and some sub-VIs, that's all.

    -Chroma

  14. Open Position at Metrosol, Inc., Austin, TX

    in Job Listings

    Posted

    QUOTE(rayodyne @ Jan 16 2008, 11:57 AM)

    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.

    This position is still accepting resumes/CVs.

  15. Open Position at Metrosol, Inc., Austin, TX

    in Job Listings

    Posted

    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.

  16. Using Automated Test Tools (QA) with LabVIEW

    in Application Design & Architecture

    Posted

    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

  17. Using Automated Test Tools (QA) with LabVIEW

    in Application Design & Architecture

    Posted

    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

  20. LuaVIEW Example with GPIB/Serial Hardware

    in Hardware

    Posted

    I have been using LuaVIEW for over a year and it has worked very well for me. I can control all the resources in a PXI chassis (single point and HW timed analog input, AO, DIO, counter PWM) also VISA based instruments such as balance scales, humidity sensors, fluid baths. I have a prototype dialysis machine completely running under LuaVIEW control. All you really need to understand is how to define a LuaVIEW callable LV vi. There is very good documentation on the subject. I am attaching a couple of examples for you to look at. Good Luck!

    Mike Sachs

    Intelligent Systems

    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

  22. LuaVIEW Example with GPIB/Serial Hardware

    in Hardware

    Posted

    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

×
×
  • Create New...

Important Information

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

  I accept