Looking for LabVIEW Developers

We are seeking a hands-on National Instruments LabVIEW developer with extensive experience using LabVIEW, FPGA, and Real-Time modules to create robust data acquisition, timing, and control software to interface with NI and non NI instruments. As a LabVIEW developer at SyncSols, you will collaborate with hardware and testing engineers to define, design, develop, test, debug, and maintain LabVIEW code for automatic testing system (ATS).

Job Duties

• Create, modify and maintain LabVIEW applications for systems.
• Work with hardware and testing engineers to specify software requirements.
• Establish and execute test and evaluation procedures.
• Document software, including requirements, design, code, user manuals.
• Follow best practices for software development, archiving, and version control.

Requirements

• Expert at LabVIEW, LabVIEW FPGA, and LabVIEW Real-Time software.
• Substantial experience with real-time, data acquisition and instrument control.
• Certified LabVIEW Developer is a plus.
• Experienced with database operation such as SQL and MS Access.
• Familiarity with standard diagnostic equipment (e.g., oscilloscopes, spectrum analyzers).
• Ability to analyze and resolve equipment and software issues for manufacturing.

Education

Bachelor or Master in EEE, EIE, ECE, Mechanical or equivalent professional experience

Experience

3+ years of industry experience

LOCATION

Chengalpattu (TN) / Bangalore (KA)

If interested, Kindly revert with following details:

Total Exp:

Relevant Exp in Labview:

Relevant Exp in Teststand/Veristand:

Current Location:

Preferred Location:

Current CTC:

Expected CTC:

Official Notice Period:

Candidates who meets the requirements are requested to share the details with your profile to sankar@syncsols.com

GUI Design #1

Idle User Interface Design with Hide/Unhide Settings.

User Interface is the very important for your application. There are lots of constrains and standards for UI developments. Here we will discuss about the idle space allocation using split bars and docking feature for settings.

Split bar – We haven’t used this feature in LabVIEW widely. This will help you to make UI standard. Main advantage is Fit to pane feature enable your UI to adopt different aspect-ratio. In LabVIEW we have 2 split bar.

·         Vertical Split Bar – Splits your LabVIEW panel in vertical manner.

·         Horizontal Split Bar -    Splits your LabVIEW panel in horizontal manner.

UI Design

I will always prefer the above alignment, because this will the standard arrangement in most of the application we used our day to day life.

We can use Split bars to split our Front panel in this manner.

Split Frontpanel.

UI Design.

If you present your UI in this way the customer will have an impression on you. Here with this I’m going to add one small and amazing feature. That will make your UI more advance one. Hiding the Option buttons.

Option enabled

Options hided

So to do this, do we need to write big code? No not at all See the below diagram only one property node will make your life more amazing! ☺☺

Block Diagram.

To download this code, click here.

And we are happy to announce, next week we launch our first UI tool kit in VI package manager. Follow us for more updates.

FB link

Twitter Link

LabVIEW Architectures

LabVIEW Architectures Series 2 of 8

Before going to next architecture let me tell you the inefficiency of the simple state machine.

    

• GUI handling is very tedious job. At that time, they will use serious of select function to check the UI changes.

Handling UI Changes

If your UI has more controls, idle case will become messier. In LabVIEW 2007 NI introduced event structure to capture UI changes. After this, whole way programming was changed. Here is one more advantage, you can configure event time out -1 (Wait until event occur) if there is no UI event your program will freeze (No load in processor).

Event Structure

Event Selector: The event selector label specifies which events cause the currently displayed case to execute. To view other event cases, click the down arrow next to the case name.

Event Time Out: The Timeout terminal specifies the number of milliseconds to wait for an event before timing out.

Event Data Node: The Event Data Node identifies the data LabVIEW returns when an event occurs. Like the Unbundle by Name function, you can resize the node vertically and select the items you need. Use the Event Data Node to access event data elements, such as Type and Time, which are common to all events. Other event data elements, like Char and VKey for example, vary based on the event you configure.

·       If you want to pass the data from one case to another case, you have to use shift register or local variable. If you use local variable your program load will increase. So most of the people started use shift register.

State Machine with Data shift registers

If your program grows data will be increase, so the number of shit register will also increase and your program will become more complex to debug and can’t maintain it.

 To overcome this problem Data Cluster concept introduced.

 Data Cluster: A typedef cluster which is contain all elements to pass one case to another case.

This is the widely used version of simple state machine. Click here to download this state machine.

 ·       What next…? Can you guess what is the missing in above architecture☺? Yes, you are wright state transition. In this method at end of the state only we can determine the next state. This makes your program harder to read and can’t maintain the modularity. Here the String array and Enum array concepts introduced.

Enum Array State Machine

Click here to download this architecture. Same way peoples used string based state machine.

In Next article we will discuss about advanced state machine Architectures.