By Gan Uesli Starling
We have a gage supplied by a company that shipped it with a *.exe application targeted for LVRTE 2009. I need to retarget it for 2017, but don't have the source code. The supplier had said they'd gladly supply me with a copy of the *.LV source, but they have looked and cannot find their own copy in-house.
History of Need: Our global corporate mother ship's IT department, in their infinite wisdom, is mandating an upgrade from Win7 to Win10. That with yet even further constraints. They enforce a list of "approved versions" of "approved applications". And for LVRTE, they are insisting upon 2017, with 2009 being a red light.
So, then, my query. Is converting an app without the source for a higher LVRTE doable at all? File is attached.
If it is doable, instructions on how?
When I try to install LabVIEW 8.5.1 runtime or visa 4.1 on an Intel NUC with CPU i5 7260U I get:
Microsoft Visual C++ Runtime Library
Program ........\LV RunTime 8.5.1\setup.exe
This application has requested the Runtime to terminate it in
an unusual way.
Please contact the application's support team for more
Just in case I installed Visual C++ 2005 redistribution and checked under add remove programs that the Windows feature of allowing version under .net 3.5 to run was enabled.
This is not an ARM based processor so why does LabVIEW has a problem installing on the NUC?
Iâ€™m having issues with a LabVIEW application that I made.
The application is used for reliability tests.
Users can configure profiles/experiments. These are translated to a voltage/current output.
Experiments can be started to run parallel on a rack of power supplies.
The application is OO-based. Each active experiment is an â€˜experiment executorâ€™ object which is a class with an active object. The process vi is a very simple statemachine which handles init of the hardware (VISA (Powersupplies connected via Ethernet, VISA TCP/IP)), iteration handling of the test, summary logfiles, UI and a few other things.
Typical usage of the application is:
16 samples tested in parallel. Most of them run the same experiment (== same output) but on different powersupplies.
These samples are tested simultaneously, and started at the same time.
LabVIEW2011 SP1 (32bit) // VISA 5.4.1
I can simultaneously start 16 samples summary file of the experiment settings are written to disk (16times in parallel == 16 samples and all viâ€™s are set to reentrant) duration is about 10s for each file. (depends on the length of the experiment, different profile steps that are used etc) it is a simple ini format file, about 136KB size Experiments start execution. (== output and measurement on the power supplies) Parallel reentrant VISA communication with power supplies works perfect, internal looprate in the â€˜avtiveâ€™state of the process is about 500ms (with 16 parallel samples)
When I start the samples, the parallel processes are started BUT:
Writing if the ini summary file gets slower and slower each time a new clone/sample is launched. I see this, because for debug I open the FP of that vi. Writing of the file gets slower and slowerâ€¦ fastest file == 30s, slowest (== last sample started == 250s) Parallel reentrant VISA communication, looprate is 20-30 SECONDS (iso 500msec in development) Can someone help me with this ?
16 parallel process isn â€˜t that much.
I always thought that runtime would be faster than development env.
My current company is in the process of expanding, and we are seeking experienced LabVIEW developers for our Denver office location. Please see below for position details:
Automation Engineer – LabVIEW Control Systems
DMC has openings in several automation engineering positions, based on experience level.
With a broad understanding of engineering fundamentals, DMC Automation Engineers provide programming, troubleshooting, testing & measurement, and technical support & solutions to a wide range of clients. Automation Engineers quickly learn new technologies and absorb specific industry knowledge to provide custom software engineering, problem solving, and helpful assistance during each phase of a project. Working both independently and within teams, Automation Engineers assist with project management, meeting deadlines and keeping excellent communications and feedback channels with team members and clients.
Engineer Level I (1-3 years relevant experience):Bachelor of Science in Mechanical, Electrical, or Computer Engineering, Computer Science or related field Background in LabVIEW Programming
Engineer Level II (2-5+ years relevant experience):
In addition to the above requirements, several years of experience with design and implementation of LabVIEW projects Certified LabVIEW Developer or Certified LabVIEW Architect Project-based development experience
Desired ExperienceReal-Time FPGA cRIO PXI RF Vision CAN Modbus
Engineer Level I
Programming Quickly Learn New Technologies Complete grasp of scientific method of problem solving Ability to follow patterns & build upon established models Understanding complex system designs Estimation of time to complete familiar tasks. Identify & communicate through proper channels new opportunities for DMC
Engineer Level II (In addition to above skills)Experience with current test and measurement as well as data acquisition hardware and devices. Ability to specify correct hardware based on system requirement. Project Planning/System Architecture Design Program Implementation Debug System Testing Communication with team members and clients Documentation Ability to create methodology to solve novel problems Ability to design systems based upon previously used system Convey knowledge in presentations, SOPs, Knowledgebase articles, client case studies, and white papers Estimation of own and others' time for completion of familiar tasks Project proposal writing
Customer Service Communications Technical Writing General Admin
Engineer Level IProgram applications to meet & exceed customer requirements Develop robust applications in accordance with DMC programming standards & best practices Project Planning/System Architecture Design Assistance Program Implementation Debug System Testing Communication with team members and clients Documentation Respond to customer needs
Engineer Level II (In addition to above responsibilities)
Perform programming and engineering tasks in supportive and leading roles at all stages of projects. System design and design assistance. Help Train/Orient/Bring Up to Speed new employees. Convey knowledge in presentations, SOPs, Knowledgebase articles, client case studies, and white papers. Develop & maintain relationships with key contacts with vendors. Develop & maintain relationships with clients, keeping feedback channels open and healthy. Assist in writing project proposals. Seek, identify, and discuss new opportunities with new & existing clients, through proper DMC channels.
Email your resume and cover letter to: email@example.com
Full Listing: http://www.dmcinfo.com/employment/automation-engineer-labview-control-systems
General Information: http://www.dmcinfo.com
I am a small-time application builder on Labview, I have tried to find answers to the following two questions a lot on the NI site but could not get any definite yes or no answer
So here are the questions
1) I know that DSC module requires run-time license on the end-users computer, my question is, that if I use the datasocket binding on the controls/indicators property box and assign a couple of OPC tags (like 20-30 max) and not use the shared variable engine, do I still have to get a dsc runtime license, or is there anything like OPC tag-based license for the end-users PC?
2) Does database connectivity toolset and report generation toolkit also require runtime license on end-user PC's?