LabVIEW deveoper required for Kitchener On. Canada

Hi all,
Meikle Automation is looking for a LabVIEW Programmer. An overview of the MASS software can be found at: http://www.meikleautomation.com/products/mass.php
This position is in our facility in Kitchener Ontario Canada.
Apply at: [email protected]
Dean Mills

Im a 30 years Electronic Engineer interested in your position please see my resume and advanteges
Is this position available for non canadian residents?
[email protected]
Attachments:
curriculo raul lopez ingles.doc ‏370 KB

Similar Messages

  • Is LabVIEW Runtime required for a DLL created by LabVIEW ?

    Hi
    Could some one advice me on this matter please.
    I am trying to build a DLL for a set of functions created in LabVIEW. Now I am  wondering if I need to use it with some other language like VB or C++, do I need to install the LabVIEW runtime of the same version as the original functions ?
    Any settings required while creating the DLL ?
    I am trying to create it in LV 7.0
    Thanks in advance
    Deepu.

    Alright Mike,
    Thanks !
    I was hoping it would work without the LabVIEW runtime. Anyway, thanks for the quick reply.
    Rgds
    Deepu.

  • LabView Programmer required for free small project

    I am looking for a Labview developer who can spend a few hours for free developing a small Labview project.
    Please email [email protected] if you are avaible ASAP
    Many Thanks
    Dave

    Why not learn LabVIEW and do it yourself.
    The help within the LabVIEW forum is free and you get to learn a language as an added benefit.

  • Are there requirements for deterministic data messaging for distributed LabVIEW applications across an Ethernet/IP network?

    Our company, RTI, just entered the Alliance program at NI recently. We are curious if power users of LabVIEW have requirements for running distributed, networked multiple LabVIEW applications in a real-time, deterministic manner? We are not attempting to make this a sales call, but if we should move forward with development of VI's that would allow distributed LabVIEW applications. We have already scoped out the effort but would desire guidance on VI layout, descriptions and ways to give a "LabVIEW" experience and not a disjointed VI that looks unprofessional. We are not sure if demand exists for this requirement. We would like to talk with
    and investigate what LabVIEW users want. We have attached a brochure on this real-time data messaging technology for your review. Maybe there is no need and we apologize for taking up NI Developer Zone bandwidth and your valuable time. We look forward to your responses.
    Attachments:
    NDDSProductBrief3-022.pdf ‏299 KB

    We are developing applications which have a distributed layout. E. g. we have 2 or more test places which have no user interface and 1 place where all configuration and monitoring and data storage takes place. We use TCP/IP for the inter computer communication. For this purpose we have developed a library which has a similar interface and usage as the queue VIs from LV 6.0.2. We support automatic reconnect on TCP/IP level and an acknowledged transfer so the application programmer can choose to do some temporary storage on the local machine if the server part is not running for sometime. We have not seen any market for that so we do not plan to sell it.
    From a lecture at the NI VIP days in Munich in 2001 personal from Siemens A&D stated to
    get a real time like behaviour over ethernet with TCP/IP you have to take care that the load will not exceed 30% of the bandwidth.
    For more information you can contact me at [email protected]
    Waldemar
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

  • Adobe Reader error when downloading a Form (IMM5257E - required for CIC - Canadá)

    I received an error when downloading a file viwh the Adobe Reader version 11.0.07.
    A message like this appear:
    To view the full contents of this document, you need a later version of the PDF viewer.

    Pat Willener!
    GREAT THANKS! GREAT THANKS! GREAT THANKS!
    I was using Google Chrome, and did not suspect that this could be the
    problem.
    I used I.E. and the download worked. So that's it.
    Great thanks again.
    Vilson Drehmer
    Rua Balduíno Pedro Vier, 693
    CEP 95.880-000 - Estrela - RS
    Fone: (51) 8401.2253
    E-mail: [email protected] <[email protected]>
    CRA-RS 6364
    2014-05-28 5:26 GMT-03:00 Pat Willener <[email protected]>:
        Adobe Reader error when downloading a Form (IMM5257E - required for
    CIC - Canadá)  created by Pat Willener<https://forums.adobe.com/people/pwillener>in *Adobe
    Reader* - View the full discussion<https://forums.adobe.com/message/6414530#6414530>

  • Installer LV7.1 - LabVIEW load error code 21: An external subroutine required for execution could not be found.

    Bonjour,
    Je cherche à créer un installer portatif utilisant les drivers NI-DAQmx 8.7.1 et NI-CAN 2.6.0.
    Je dispose d'un code LV 7.1 et j'ai installé l'application builder 7.1.
    Mais une fois l'application installé sur un PC vierge de Labview, j'obtiens le message suivant:
    load error code 21: An external subroutine required for execution could not be found.
    Ce message est répété plusieurs fois (pour différents VIs) puis le programme ne se lance pas.
    J'ai bien veillé à installer les drivers NI-CAN et NI-DAQmx correspondant au préalable sur la machine cible.
    En chercant sur le forum, plusieurs pistes m'ont été proposé:
    La version NI-DAQ
    L'intégration du Run time Engine
    Un problème de DLL
    J'ai vérifié ces 3 points mais cela n'a pas règlé mon problème.
    Résolu !
    Accéder à la solution.

    Bonjour,
    Merci de ta réponse.
    En fait, j'ai bien inclu le runtime engine de Labview qui était effectivement la source de l'erreur.
    L'installation de NI-DAQmx v 8.7.1 provoque la mise à jour de la version du runtime engine (passage de 7.1 à 7.1.1).
    J'ai donc désinstallé Le runtime engine 7.1.1 (ce qui a provoqué la désinstallation de labview et NI-DAQ).
    Puis je suis passé par une version plus ancienne de NI-DAQ (7.2) que j'ai adapté (inclusions de DLL et de VIs).
    Les messages d'erreurs ont alors tout simplement disparus!

  • Requirements for Desktop PCs as LabVIEW Real-Time Targets

    Hello
    I have read the Requirements for Desktop PCs as LabVIEW Real-Time Targets
    http://www.ni.com/white-paper/8239/en/
    and i have 2 questions:
    Supported Ethernet Chipsets:   Is Intel® i210AT Controller supported?
    Supported Processors: Is E3 and E5 Xeon Supported?
    thank you

    Dear goltnum9,
    Here some Whitepapers where you can read which Requirements must be given and also how do convert.
    Requirements for Desktop PCs as LabVIEW Real-Time Targets
    How do I Create a Desktop Real-Time System?
    Kind Regards,
    SG3 | Applications Engineering | National Instruments | NIG |

  • Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

    We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
    'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
    This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
    As the editor and its compiler do not see the error  and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
    Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
    Our project  comprises hundreds of Vis over several libraries.
    Thanks,
    Chris

    Thanks Craig for all your suggestions.
    We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
    It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
    We will post about this in detail after we have positively proven that this actually was the case.
    The .net version issue was already checked.
    Performance was the same on all machines we tested on including the dev machine.
    Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
    In relation to your remark: 
    'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
    Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
    Ragrds,
    Chris

  • Minimum computer system requirements for LabVIEW 7.1

    What are the minimum computer system requirements for LabVIEW 7.1?  I have a PC with the following specifications:  1.7 GHz Pentium-4, 512 MB RAM, and a 60 GB hard drive running Windows ME.  I tried installing LabVIEW on the system but kept getting the "This computer does not meet the minimum requirements for this product" message.  What's the problem here?
    Thank you.

    Hi Enhan,
    You're problem may be related to the OS "Win-ME". 
    Your system appears fine, if there is room available on the HD.
    Ray

  • To read COMTRADE file in Labview there is an example provided. Can somebody provide the sample .cfg and .dat files required for its working?

    To read COMTRADE file in Labview there is an example provided. Can somebody provide the sample .cfg and .dat files required for its working?

    Thanks for the reply.
    But this library doesn't contain any sample .cfg and .dat files which can be read and understood. Can you please provide the same?

  • Windows 2000 requirements for LabVIEW 8.5.1 & DAQmx 8.7.1

    Greetings,
    I've been looking around for a detailed set of requirements for LabVIEW 8.5.1 and DAQmx 8.7.1 for the Windows 2000 platform. 
    So far I know I'll need Service Pack 4 and probably Explorer 6 and .Net 2   But I can't find confirmation on the last two things, and I'm not sure if there are any more. 
    Does anyone have a link to this information on  ni.com? 
    Thanks. 
    Patrick Allen

    Thanks for the reply Denis,
    I'd found both of those previously actually.  But I wasn't sure they were "complete". 
    I can't say 100%,  But I'm pretty sure I had to install .Net 2 on a system once before for DAQmx.  (Or maybe there was a warning...or something) 
    Just thought I'd try and find out as much as I could before I go and do a remote upgrade where I won't have any Internet access. 
    Patrick Allen

  • Minimum PC requirements for LabVIEW 7.0 Executable

    I was wondering what the minimum PC requirements for a PC with the LabVIEW
    run
    time engine on it running an executable that I build with LabVIEW?

    That answer is going to vary greatly with the application itself. I've written big applications that require 500 MB of RAM to do all their processing. One good way to gage minimum requirements is to look at how the application performs on the development PC. Use your Task Manager to show the available RAM before you run the executable and when its running. Generally speaking, I don't recommend anything less than the hoursepower of the development PC. What I can say is that I haven't had any showstopping issues with any of my oun applications compiled by LabVIEW 7 on my PIII 800 with 512 MB of RAM and W2kPro.
    Of course, there's always trial and error. I would avoid operating systems older than 4 years.
    Daniel L. Press
    PrimeTest Corp.
    www.primetest.c
    om

  • Exciting LabVIEW Development role in Calgary, Alberta, CANADA

    Exciting LabVIEW Development position Available – Calgary, Alberta, Canada
    Want to work for a Great company that truly values it’s employees?  This is a highly respected oil and gas services company that offers a Corporate Culture second to none.  We are looking for a LabVIEW developer to join the R&D Team; this is a challenging role ideally suited for someone with an Instrumentation and/or Mechanical Engineering background.
    Role Overview:
    This is a busy and growing oil and gas services company with a long stable history, a strong balance sheet and a corporate culture of success and flexibility.  The candidate will be responsible for software research and design activities.  You’ll actively participate in feasibility studies to develop concepts into products (Prototypes).  You will also evaluate and design software products using Labview that control electric/mechanical and electric/hydraulic systems for the oil and gas service industry.  Developing and executing test plans and specifications along with data analysis are also part of this role.
    Duties:
    Initiates and leads team activities to evaluate and develop creative solutions to optimize products and technologies
    Designs software for control, human interaction, reporting and logging as required for feasibility studies
    Confirms system and product capabilities by designing feasibility and testing methods and testing properties. Evaluates testing data to reach design decisions.
    Supports evaluation of performance of equipment in the field, resolution of problems and recommendation of improvements.
    Provides information to be included in proposals, specifications and applications.
    Analyzes opportunities to strengthen product / company performance including soliciting customer requirements and observations from oil and gas clients
    Conducts training and mentoring.
    Supports project management of software development activities.
    Documents designs regarding configuration, operation, and capabilities.
    Follows corporate standards for software development.
    Qualifications:
    Demonstrated ability in software design and product design using National Instruments LabVIEW and potentially other high level languages
    University degree in Physics, Engineering or equivalent experience.  Engineering Degree and Professional Certification preferred.
    Demonstrated learning from experience, including analyzing information, identifying client needs, developing action plans, and delivering recommendations.
    Extensive background in data acquisition and control systems in oil and gas services and instrumentation in general
    Hands-on experience with demonstrated innovation and creativity.
    Excellent analytic skills and experience trouble shooting complex software problems.
    Experience functioning within teams to address and solve business and engineering issues.
    Demonstrated ability to communicate effectively both verbally and in writing. Strong technical writing.  Demonstrated experience using the Microsoft Office Suite.
    Familiar with industry standard practices and tools for creation, development, testing and documentation of software. 
    Demonstrated effective resource and project planning, decision making, results delivery, team building, and the ability to stay current with relevant technology and innovation.
    Ability to be effective while simultaneously involved in multiple projects.
    We will consider intermediate to senior level candidates; compensation is commensurate to experience. This is a permanent, full time role located in Calgary, Alberta, CANADA; candidates must be Canadian Citizens or have legal working status in Canada.  Candidates from outside of Canada without legal Canadian working status will not be considered.
    PLEASE contact:  Marcello Barone at [email protected] for immediate consideration.
    Attachments:
    LabVIEW Developer.docx ‏18 KB

    Have you filled this position?  I'm interested, but don't know about the Canadian work requirements.  I'm a U.S. citizen, working in the U.S.  I'd assume that it wouldn't be that difficult to get the Canadian permission...
    Also, would you consider someone for remote employment with occasional trips to the facility?
    Thanks!

  • Charting data from text file in LabVIEW 5.1 for Windows

    I am having some difficulties trying to figure out how to plot a chart with
    data from a file. I would like to be able to read data from a text file
    into a chart using LabVIEW 5.1 for Windows. I have looked in the help
    within the program and online. I have also looked in the user manual and
    the book "LabVIEW for Everyone". Could you please give me specific
    instructions on how I would construct the program to be able to do this.
    Thank you.

    Hi Ellie,
    It depends on how data is stored in that txt file. Usually you load the data into an array either using or , the array if necessary and send it to the graph indicator in required form. If you want a more detailed answer, send me a sample data file ([email protected]).

  • I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

    I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
    I have the professional development system
    I can run the main VI
    all the required DLL's are in the dependencies section of the project window.
    I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
    Thanks in advance to all labview users for your help
    Attachments:
    project window.PNG ‏36 KB

    other PNG
    Attachments:
    Broken Arrow on EXE.PNG ‏179 KB

Maybe you are looking for