LabVIEW/TestStand/PXI Engineering Architect Role in fast growing Semiconductor Services Company

A reputed Semiconductor Services company is on the cusp of major growth due to recent Brand Recognition and happy customers. The company is looking for a capable, motivated senior engineer or developer who wants to take the next step toward technical/architecture leadership, team leadership and opportunities to make lasting impressions on customers in order to grow the business and themselves. Some questions to ask yourself before you apply:
a) Do you have 2+ years of experience in LabVIEW/TestStand/PXI with a strong foundation in Electrical/Electronics/Communications/Computer Engineering
b) Do you feel that your technical skills in the LabVIEW/TesStand/PXI space have evolved to the level that you can punch above your weight compared to the number of years of experience. We are looking for go-getters who may be 2-3 years experience but make a lasting impression on any customers and come across as 4-5 years of experience because of your innate smartness, command of engineering/architectural concepts, communication skills and can-do attitude
c) Are you driven by a sense of integrity, respect to your colleagues and a strong team spirit
d) Do you believe that every meeting and deliverable to a customer is a vehicle for company and personal growth?
e) Do you enter every project and opportunity with a view to ensuring customer delight and loyalty?
f) Are you fearless about entering new allied technologies such as LabVIEW FPGA/Xilinx//Altera based FPGA/ Microcontroller programming and system design
If the answer to these questions is yes, please email [email protected] with your most updated resume and prepare to embark on a career that will fuel your  job satisfaction and growth in the years to come. A strong technical background in the areas mentioned is essential and will be tested.
Company Information:
Soliton Technologies Inc. is a value-driven Engineering Services company with over 15 years of experience and steady services growth in the Semiconductor, Automotive, Biomedical and Test and Measurement industries. (www.solitontech.com). Soliton's services range from LabVIEW and TestStand based Validation Automation (often PXI based), GUI Frameworks, Embedded Development Services on NI Embedded targets as well as Microcontrollers, High Speed FPGA Design, Enterprise Software Development on Multiple programming platforms ( C, C++, C#, .NET, Python, Java, HTML5 etc) and Vision Based Test Systems. The company has a strong Semiconductor focus in the past decade with multiple Fortune 500 customers with steady growth and a track record of customer retention.
Compensation: Not a constraint for the right candidate.

Hi,
Kindly arrange an interview process.
I have attached my resume
Regards,
Bharath Kumar

Similar Messages

  • NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

    This problem seems similar to the post "Resource not found error in executable on developmen​t machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
    I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards. 
    I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010.  The code was using a custom executive and my task was to rewrite the test using TestStand 2010.  I reused the majority of the old code.  The old code used NI-5660 to control the 5600 and 5620.  When I run my sequence using the LV Development System and TestStand, it runs without any issues.  When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues.  It warns that the nipxi5600u​.dll was not initialized correctly.  Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter.  The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again. 
    I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace.  I also used Dependency Walker to track down the problems with the nipxi5600u​.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32).  I have also performed a Mass Compile to make sure everything was running in LV 2010.  If I skip the steps involving the 5660, my entire sequence runs fine. 
    The previous code was running with the LabVIEW Run-Time Engine without any issues.  Is there just a step I am missing?  Has anyone seen anything like this before?  I can send screenshots of errors to provide more detail if necessary. 

    I have tried some more things and still can't get it to work.  I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs.  This did not change the results. 
    When I try to run my sequence, The first error I get is shown in Error 1445.bmp.  This happens when I try to use the NI 5660 initialize.vi.  If I click ignore, the next error I see is shown in Error -20551.bmp.  When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp.  When I close TestStand, I get the error LabVIEW Fatal Error.bmp. 
    Attachments:
    Error1445.JPG ‏164 KB
    Error -20551.JPG ‏174 KB
    Error loading nipxi5600u.JPG ‏9 KB

  • Teststand error states that a vi failed to load in the Labview Run-Time Engine

    I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
    If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
    How do I get this VI to run on this system when it is called by test Stand?
    Thank you

    The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
    I do not have labview loaded on this system, only the run time engines from running my deployment.
    When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
    Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
    I have attached the teststand sequence if this helps.
    Thanks
    Attachments:
    QuantumDigitalBd.seq ‏13 KB

  • LabVIEW / TestStand Opening in Rockleigh NJ

    Crestron is looking for a talented individual to fill the position of Test Engineer III at our corporate headquarters in Rockleigh NJ (07647). This position will be part of our Test Framework Development team, and will develop advanced production test platforms using National Instruments’ LabVIEW, TestStand and Visual Studio C#. This role will focus heavily on creating the underlying structure for Crestron’s automated test platforms and on designing modular test systems that can be adapted to a wide variety of applications and products. The systems that you produce will be used by downstream engineering teams to develop final acceptance tests for Crestron’s products.
    Key responsibilities:
    Create LabVIEW VIs to interface with a variety of test instrumentation, and with Crestron equipment and software
    Use MS Visual Studio to create C# code that will exercise Crestron hardware. We will provide extensive training on how to work with Crestron systems 
    Support TestStand automation of production tests
    Assist in the selection and adoption of test instrumentation
    Work closely with product designers and firmware developers during the new product development process
    Work closely with other test engineers during the test development, integration and implementation of production tests
    Other duties as assigned
    Crestron is looking for a highly motivated, results-driven individual with exceptionally strong computer programming and technical skills. A successful candidate will have extreme proficiency with LabVIEW, TestStand and C#, Java or C++. General electrical engineering knowledge and experience with product testing in a manufacturing environment is essential.
    Required Skills and Experience:
    Bachelor’s of Science degree in Electrical Engineering, Computer Engineering, or Computer Science; Masters preferred
    Extremely strong proficiency with NI LabVIEW, NI TestStand and C#, Java or C++. This position will rely heavily on these skills and we will focus on them during the interview
    6 - 10 years of engineering experience with at least 4 years in a test or software engineering related role
    Comprehensive understanding of product test methodologies and techniques
    Superior written and oral communication skills; the ability to work closely with a diverse group of individuals
    A desire to be an essential part of a fast paced, innovative engineering team 
    A passion for quality and a drive for excellence
    https://www2.apply2jobs.com/crestron/ProfExt/index.cfm?fuseaction=mExternal.showJob&RID=2728
    If your interested and able to work in New Jersey USA without requiring sponsorship, etc please either apply through the link above or send me PM with your resume.
    Regards,
    Shaun

    Hi Enquiry,
    The reason for giving personal mail id is: "it is convenient to access
    personal mail id than official id.. I have no intent to hijack your
    cv 
    If you are interested, then you may send your CV @
    [email protected]  . You may ask why not HR mail id ... reason is
    obvious I want to get referral money: smileywink: 
    Regards,
    Naresh.K
    Naresh
    Software Engineer

  • UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71

    UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE。PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
    Uninstalled DAQ and reinstalled.  MAX still throws an error. 
    Any Isead besides uninstalling 3/4 of my software?
    Merry Christmas!
    Matthew Fitzsimons
    Certified LabVIEW Architect
    LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

    To clean up your system, you will need to uninstall the LabVIEW 7.1 run-time engine, and the "LVBroker," and the "LVBrokerAux71" components using the MSI Blast utility.  To obtain this utility, please create a service request for phone or e-mail support, and contact one of our Applications Engineers about this issue.  Thank you!

  • LabView/TestStand Developer - Herndon, VA

    Senior Production Test Engineer
    Job Description:
    ABOUT THE COMPANY iDirect is dedicated to providing next generation solutions for broadband IP networking via satellite networks. For more than 20 years, the VT iDirect organization has focused on meeting the economic and technology challenges across the satellite industry. Today, the product portfolio, branded under the name iDirect, sets new standards in performance and efficiency, making it possible to deliver voice, video and data connectivity anywhere in the world. As the leading innovators in the satellite communications industry, our diverse and talented team of Internet, satellite and telecommunications professionals continues to break new ground and create significant opportunities for network operators, for service providers and resellers, and for corporate networking professionals. If you are ready for the challenges, responsibilities, and rewards that come with working in a high-energy, fast-paced environment, then this is the job for you!
    ABOUT THE POSITION
    We are looking for a true leader in the area of production test development and implementation to significantly upgrade our capabilities and sophistication in an outsourced manufacturing environment. This is a unique opportunity to develop, implement and lead the vision for production test engineering. The Senior Production Test Engineer will be in integral part of the global manufacturing operations team and will interact with the Software and Design test functions. This is a great opportunity to join a growing company in a rapidly developing industry.
    RESPONSIBILITIES:
    Participate in all aspects of product testing within the manufacturing environment.
    Develop, debug and maintain LabView/TestStand code to support production test.
    Partner with Manufacturing Engineering, Quality and Reliability teams to monitor, measure and improve production yields. Develop and optimize the debugging approach incorporating a closed loop corrective action process for root cause identification and correction.
    Identify test process cost savings opportunities and work with other Supply Chain teams to identify and realize regular efficiency improvements and cost reductions.
    Lead projects to improve existing test systems and solve any issues that prevent delivery of professional testing capabilities.
    REQUIRED EXPERIENCE:
    The ideal candidate will come from a communications electronics environment with emphasis in wireless communication, and have a thorough understanding of current test strategies and approaches. In addition, the candidate should have the ability to develop and articulate a clear vision for effective and cost efficient production testing in outsourced manufacturing.
    BS in Engineering required. BSEE preferred, BSEET, computer science/engineering or equivalent experience will be considered.
    10+ years in test engineering or related areas in complex electronics manufacturing environment.
    5+ years of experience working at or with a Contract Manufacturer.
    Experience with LabView/TestStand, Boundary Scan, BIST, POST.
    Strong technical documentation skills including test requirements and test plan development.
    Solid understanding of software design and debug.
    DESIRED EXPERIENCE:
    Experience using databases such as SQL.
    Experience with a variety of programmable instruments; such as Spectrum Analyzers, power dividers, signal generators, logic analyzers, etc.
    Significant RF experience and wireless communications strongly preferred.
    Knowledge of application of test methods (ICT, AOI, and RF communications) desirable.
    Experience with National Instruments hardware a plus.
    Experience programming and interfacing ATE's in VB, C, C++, LabView, shell scripts, Perl, programming language skills for measurement, data acquisition and instrumentation control a plus.
    Equal Opportunity Employer M/F/D/V

    Hi,
    Kindly arrange an interview process.
    I have attached my resume
    Regards,
    Bharath Kumar

  • Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

    I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
    ErrorCode: -17600,
    Failed to load a required step's associated module.
    LabVIEW Run-Time Engine version 9.0.1f3.
    When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
    My TestStand Engine Version is 2012 f1 (5.0.0.262).
    I'd appreciate any help on this issue.
    Roman

    Hi Roman,
    There are a couple of things you can try:
    1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
    Check if the simple VI is loadable and runs without errors in TestStand.
    If the step generates the same error, you should try a re-install of the LabVIEW development system.
    If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
    1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
    Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
    Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
    2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
        Right-click "Build Specifications" and choose "New->Application(EXE)".
        In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
        Save the properties.
        Right-click on the newly created build specification and choose Build.
    Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
    You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
    Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
    If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
    Regards,
    TRJ

  • LabVIEW Run Time Engine and ActiveX Automation Server

    Hi,
    I have a question related to LabVIEW Run Time Engine and ActiveX Automation Server:
    We have a tool developed in LabVIEW and TestStand. End user interface is a LabVIEW GUI (it's an executable) which executes TestStand sequences. Some TestStand sequences call lower level LabVIEW VIs.
    Everything works fine with LabVIEW installed, but I was wondering if I could run this tool on deployment machine with only LabVIEW run time engine installed. We are using LabVIEW 6.1 and with only the run time engine installed, I get the error message: "Unable to launch the 'LabVIEW.Application' ActiveX automation server ". 
    BTW, we are planning to upgrade the versions soon.
    Is it possible to make things work only with the run time engine?
    Thank you.

    Thanks for the response, Brian.
    I did upgrade to LabVIEW 8.0 and TestStand 3.5. Everything works fine on the development computer where LabVIEW and TestStand is installed. On the target computer in the lab, I installed LV RTE 8.0 and TestStand 3.5, and now when a VI is called in a sequence file, I get the following:
    RunState.PreviousStep.Result.Error.Code  -18002 
    RunState.PreviousStep.Result.Error.Msg  "LabVIEW: The VI is not executable"
    So, the executable opens and works fine (which means that the LV RTE is installed properly), but when a sequence calls a low level VI, it does not make it through.
    comments/suggestions are appreciated. Thanks.

  • System error 999 while loading the Labview Run-Time Engin

    Bonjour à tous,
    J’ai un PC avec un Runtime LV71.1 qui me retourne l’erreur suivante. Je ne trouve pas d’info sur cette erreur. Une Idée sur la cause ?
    System error 999 while loading the Labview Run-Time Engin(c:\program files\National Instruments\Shared\Labview Run-Time\7.1\\lvrt.dll)
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW
    Résolu !
    Accéder à la solution.

    Bonjour Maxime, merci pour ta réponse qui est très intéressante. Le soft est en LV7.1.1 est fonctionne depuis plusieurs années. Le PC est chez un client, dans un pays très « hostile », je n’ai donc pas accès à ce dernier. Un superviseur local m’a fait le retour qu’après redémarrage du PC ce dernier indiquait un problème, avec photo pour descriptif. Je n’ai pas plus d’info pour le moment. Je viens donc de demander un CHKDSK c: /F
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

  • Error -18004 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

    Hi to all,
    I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
    The Problem is that I get the following error, saying that my VIs cannot be executed:
    -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
    All my VIs were masscompiled with LabVIEW 7.1.1
    How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
    Thanks for you help,
    - Caribe -
    PS: I configured the adapter to use the  LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

    Hi Caribe,
    Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
    I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
    If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
     Thank you,
    Sasi

  • LabVIEW Run-Time Engine in Developer Suite DVDs

    Hi!
    I need to install the Labview Run-Time Engine on a PC.
    Where can I find it on my Developer Suite DVDs?
    (I'd like to avoid downloading LV RTE from NI website)
    Thanks in advance for any help,
    Marco
    Solved!
    Go to Solution.

    I'm pretty sure it is on the Device Drivers disk.
    Using LabVIEW 2010SP1 and TestStand 4.5

  • HCL America Needs: ATE, Labview/Teststand Engineer: Lake Forest, CA

    Domain: RF/Communication/SATCOM (Aerospace industry)
    Required Skills:
    - Labview
    - Teststand
    - SQL
    - MS Access
    - RF / Antenna knowledge
    Forwared responses to: jc[dot]hcltech[at]gmail[dot]com.
     

    Dear Sir/ Madam,
    I am writing in response to your job notification for Embedded Testing.
    I am a B.E ECE with an aggregate of 7.73% marks.
    - I have good knowledge of programming languages like C, C++, Embedded C,Assembly and Basics of LABVIEW.
    - I’m compatible on working various operating systems like Linux, windows, etc.
    - I have also done 6 months internship from Electro System Associates(ESA) Bangalore.
    Also I have an Experience in the Field of Testing and Measuring Instruments.
    I am from Electronics background .Please provide me an opportunity .
    Some of my personal qualities which you may find useful for this role are:
    - Ability to learn quickly coupled with innovative ideas for problem solving
    - Ability to work in a team with strong communication skills
    - Hardworking and sincere towards work with an ability to take directions
    Please find my detailed CV for your consideration. If you need any more details, please let me know.
    Thanking you for your time and looking forward to hear from you.
    Sincerely
    Gopinath.s
    Ph:9535569115

  • Labview / Teststand programør søges !!

    Vi leder efter en programmør, som skal indgå i et team i vore Manufacturing
    engineering afdeling.
    Vi beskæftige os med produktion af internetudstyr, printerservere, m.m.
    Vi skal igang med at designe en ny testplatform, baseret på
    Labview/Teststand til brug på vore fabrikker rundt om i verden.
    Hvis du er interesseret kan du kontakte undertegnet
    Allan Koch

    Hej
    Hvilket firma repræsentere du??
    Måske intersseret.
    E
    Click here for Free Video!!
    http://www.gohip.com/freevideo/
    Allan Koch wrote in message
    news:89jsvf$4oe$[email protected]..
    > Vi leder efter en programmør, som skal indgå i et team i vore
    Manufacturing
    > engineering afdeling.
    > Vi beskæftige os med produktion af internetudstyr, printerservere, m.m.
    > Vi skal igang med at designe en ny testplatform, baseret på
    > Labview/Teststand til brug på vore fabrikker rundt om i verden.
    >
    > Hvis du er interesseret kan du kontakte undertegnet
    >
    > Allan Koch
    >
    >

  • Error involving Report Generation Toolkit and Labview Run Time Engine

    Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

    I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
    Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
    I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
    I displayed my App.Property of APP.DI
    R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
    Any ideas ?
    Greg Klocek

  • LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

    I'm having a problem building an installer in LabVIEW 2011SP1.
    It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
    Now when I try to build the installer I get "The build was unsuccessful."
    Possible reasons: Error generating preview for My Application 3.1.7.
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    *** Error: An internal error occurred for which the cause is unknown. (Error code -41)
    *** Error Details:
    Error in MDF API function: _MDFCommon_GetNextLogMessage
    Error in MDF::GetInstance - MDF static instance is not initialized!
    *** End Error Report
    Loading product deployment information
    *** WARNING ***
    NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
    The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
    Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle
    Solved!
    Go to Solution.

    I do have the LabVIEW 2013 discs but didn't install it.
    I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
    I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
    Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
    So now I need to distribute 2 runtimes with my application?!?!
    Troy
    CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
    I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
    Beware of the man who won't be bothered with details. - William Feather
    The greatest of faults is to be conscious of none. - Thomas Carlyle

Maybe you are looking for