![]() If the EE moves a hole, it doesn't break the reference in SOLIDWORKS when it imports, it's still there. While using MCAD CoDesigner, this is no longer a problem. Every time you import a new STEP file, you have to manually, individually go through, and relink each of the references. Jin adds, “as a result, if you design with any sort of reference to geometry, everything is broken. And that's just such a huge increase in efficiency, where before when we were exporting STEP files and sending those back and forth, SOLIDWORKS really isn't capable of importing a new STEP file and then recognizing what references should be carried over.” MCAD CoDesigner-as part of Altium 365-played an especially large role in easing the design process by making it possible for team members to seamlessly communicate, collaborate, and iterate during their late-night working sessions.Īccording to Team Lead and Mechanical Engineer, David Jin, “one of the biggest advantages that I've found while using MCAD CoDesigner is that when passing a board back and forth between ECAD and MCAD, the references on MCAD, especially SOLIDWORKS in particular, aren't broken. With so many lessons learned in real-time, knowledge-transfer and communication between MCAD and ECAD engineers was imperative to making their next bot the best it could be. This was also when they implemented Altium 365 and Altium Designer-two tools that would prove invaluable in helping them make a run at winning the Giant Nut.Ī 250-lb robot was a total shot in the dark considering up until then the team hadn't attempted anything above 120 lbs… and that caught fire. This was when they decided to apply for a chance at BattleBots. ![]() ![]() Putting the Right Pieces Together With AltiumĪfter realizing their failure was largely due to an off-the-shelf part, the Ribbot team decided their next bot would be built with custom parts they could rely on. ![]()
0 Comments
Leave a Reply. |