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 Well Suited for:
Integrated designs performed by multiple designers simultaneously (designs requiring a Product Lifecycle Management system); Designs requiring a high degree of parameterisation; Large companies where specific standards and best practices are applied to all models and drawings created. Not Well Suited for:
Personal use in designing one-off models and drawings; Small business use where very few of the expensive features are actually used. Read full review Pros NI (National Instruments)
Automation. I/O. Data Processing. Read full review It has very good user interface in classic or ordered environment. In 2D or drafting, you can give any Geometric tolerancing and symbols to any dimension. There is a wide range of options available. You can convert any files in step file (.stp) and can open it in other designing applications easily. After converting 3D drawings in 2D you can make changes in 2D drawing by converting it in the draft. You can also add details like cross-sections and detailed view. You can directly make threads without creating holes. 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 Being used to 2-key and 3-key commands from the keyboard, it would be nice if this was more robust in Solid Edge. The capability of programming keystroke commands exists in Solid Edge, but it would be more user friendly in that regard. Editing hatches can be a challenge. I'm not a fan of the ribbon bar, but that seems to be a feature across software platforms in Windows. Read full review Usability NI (National Instruments)
As mentioned previously, Siemens Solid Edge is not the most user-friendly of products at all. It requires intense training to make sure that the basics are understood, and after that, there are numerous other training interventions needed to be able to perform expert-level CAD functions. The GUI is not intuitive, as many other packages are, and the features built-in are not well defined. The process to use many of these features is counter-intuitive and requires a mind-shift.
Read full review Support Rating NI (National Instruments)
I have been involved with support and training of Solid Edge for 24 years. Given that I based my business model on support, and have been successful for all these years, I know excellent support. Siemens support for Solid Edge, "GTAC", is the definition of support for a product in every aspect.
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 FreeCAD is often better than Solid Edge 2021 when converting files, but I hope this changes with 2023 NX is overall more powerful, but that is to be expected (and you cant add it above because it is too short for whatever reason).
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 It took about 20 hours of use to get the basics of Synchronous Technology, and with just a basic competency I was able to make useful changes to the design. One of those changes was impossible to do our other CAD program. My use lately has mostly been on personal time and self-driven, so learning other aspects and features of Solid Edge has been slower. Creating a drawing for a part required a few hours to learn and do the first time, but luckily there were YouTube videos for examples. With practice, I would expect the time to reflect what it takes in SolidWorks (about 30 minutes). Read full review ScreenShots