Likelihood to Recommend NI (National Instruments)
LabView is a great tool to connect your sensors to your data aquisition hardware. It makes it really easy to set-up a data acquisition routine that meets your individual requirements. I, as an engine researcher, find it very well suited for engine experimentation. For any other programming needs, i.e. not data acquisition, I would not recommend using LabView because of its graphical programming architecture. The architecture makes it a great tool for Data Aquisition but puts at a disadvantage when it comes to other computational tasks, e.g. making a thermodynamic engine model. For those applications having text-based programming is better suited
Read full review PTC Creo is great for assemblies that multiple users are collaborating on. Models can reference other models that someone in another department has released and when those models are changed, the referenced parts and assemblies are changed. These changes are very helpful when working on collaborative machine designs and comparing forging dies with the final parts.
Read full review Pros NI (National Instruments)
Automation. I/O. Data Processing. Read full review PTC Creo contains many advanced tools with better optimization for creating part models and other production related drawings. The initial concept designs can be done more adequately. The parameters of 2D drawings can be changed easily by editing the 3D model. The productivity can be increased by customized tools for modeling. Read full review Cons NI (National Instruments)
Sometimes backwards compatibility issues arise. Error messages can be confusing. Although it is a graphical programming interface, it has a pretty steep learning curve at first. Read full review PTC Creo could grow a help-line staff of highly experienced individuals to aid the existing knowledge base article searchers. It would include experts with deep knowledge of certain Creo modules (SMEs) and provide help staff a go to for deeper levels of help when it is needed. Read full review Support Rating NI (National Instruments)
I liked the training manuals I used to learn some, as I didn’t have CAD background in college or before this job. My coworkers were able to share with me what they learned in PTC training and I was able to get support online and through reading.
Read full review Alternatives Considered NI (National Instruments)
We chose LabVIEW over
MATLAB due to the integration with hardware and the graphical programming interface. Also, the ability to use LabVIEW with FPGAs and real-time processors without having to make large changes to the code base or swapping to a separate programming environment was a big benefit since we don't know what hardware will be suitable for each customer application.
Read full review Learning curve of
SOLIDWORKS is higher compared to Creo, however, stability and more design control is provided by Creo. Creo also have more robust and stable interfaces. For larger assemblies, Creo works better than
SOLIDWORKS . New upgrades of Creo has given liberty to open different file data of different software without any file conversion. Creo costs comparable to
SOLIDWORKS cost, with more capabilities.
Read full review Return on Investment NI (National Instruments)
Allows us to spend more time on analysis and less time on coding Read full review Creo is our standard design package and as such we have had a negative impact on time spent designing because it is less user-friendly. In difficult design situations, we have had a positive impact because Creo is better suited for complex designs. Read full review ScreenShots