machineiop.blogg.se

Ironcad version history
Ironcad version history




ironcad version history
  1. IRONCAD VERSION HISTORY UPDATE
  2. IRONCAD VERSION HISTORY SOFTWARE
  3. IRONCAD VERSION HISTORY CODE
  4. IRONCAD VERSION HISTORY WINDOWS

The first version of Synchronous Technology had some limitations and usability problems. I’ve been guilty, more than once in my career, of seeing what’s possible, rather than what’s immediate.* I was, possibly, guilty of this with Synchronous Technology. If you hear someone say ‘that’s nothing new,’ don’t believe them. The synchronous solver doesn’t use a history tree, but rather holds user-defined constraints in groups associated with the surfaces to which they apply…Ultimately, though, I believe this to be a transformative technology - one that represents an important inflection point in the CAD industry.

ironcad version history

“ Siemens’ synchronous solver overcomes the order dependencies that have plagued history-based CAD programs by solving for the explicit and inferred constraints at the same time. I was (and still am) quoted on the Siemens PLM website: In 2008, the game changed for Solid Edge, with the introduction of Synchronous Technology: a system supporting both traditional history-based (ordered) modeling, and history-free direct (unordered) modeling. Able to compete with SolidWorks, Pro/E, and Autodesk Inventor. Over time, Solid Edge matured into a capable mainstream CAD system. And they sold the product, and its entire development organization, to EDS Unigraphics (now known as Siemens PLM.)įor many years, the Solid Edge team (which Unigraphics seemed to have left largely intact) continued to develop new and improved versions of the software. Ultimately, three major changes saved Solid Edge: the developers pulled out all the extraneous Jupiter overhead that wasn’t necessary for an MCAD program, and changed from ACIS to the Parasolid geometric modeling kernel. Not only did SolidWorks soundly trounce Solid Edge, they pummeled PTC, and bloodied Autodesk. Watching SolidWorks take on the competition was like watching Mike Tyson (in his prime) take on other boxers. The competition between SolidWorks and Solid Edge was more of a blowout than a brawl.

  • They didn’t have their sales channel strategy together.
  • They used the ACIS geometric modeling kernel, which, at the time, was not a match for Parasolid.
  • As a result, Solid Edge didn’t ship until about 6 months after SolidWorks.

    IRONCAD VERSION HISTORY CODE

  • In the middle of development, they went back and re-worked the core program code to use the (newly available) Microsoft Foundation Class (MFC) object model, instead of their internally developed object model.
  • This added a lot of program overhead that made Solid Edge fatter and slower than it would have been were it to be fine-tuned for MCAD.
  • They built Jupiter to be a universal CAD platform.
  • Unfortunately, Intergraph made a number of missteps with Solid Edge: Both were clean-sheet products that promised to challenge the hegemony of PTC’s seemingly unassailable Pro/Engineer CAD program. The SolidWorks versus Solid Edge competition was shaping up to be a major brawl. SolidWorks was also hard at work on a similar product. Yet, Intergraph wasn’t the only company working on a Windows-based MCAD program. My sense, at the time, was that Solid Edge was pretty impressive. I was one of a number of industry writers who was flown out to Intergraph’s Huntsville headquarters to get an up-close look at Solid Edge. To me, the jewel of Jupiter project was Solid Edge: a 3D feature-based solid modeling MCAD system. The goal was to develop a platform that could be used to create a number of graphics applications, including 2D CAD, AEC CAD, mapping, P&ID, and more. NT promised to be a game changer (and it was.) For CAD vendors, it heralded a shift from Unix-based engineering workstations to Windows-based PCs.

    ironcad version history

    IRONCAD VERSION HISTORY WINDOWS

    If you’re old, like me, you may remember that as the time when Microsoft was working on Windows NT, their 32-bit version of Windows. The product started out as a part of the Jupiter project, a next-gen CAD initiative at Intergraph Corp, in the early 1990s. Let me start with a little history of Solid Edge. But Solid Edge matters more than you may realize.

    IRONCAD VERSION HISTORY UPDATE

    Is this just another update of another mainstream CAD package? Yes.

    IRONCAD VERSION HISTORY SOFTWARE

    Siemens PLM Software has announced that Solid Edge ST5 will be available soon.






    Ironcad version history