IfI install the solidworks extension and save as the assembly using the data Smith extension, and then import the assembly: it is visible but without any materials or decals and often elements are missing.
Can you show your output log?
The first thing that comes to mind is that your sldprt files used in your assembly are not in a folder that is looked for by datasmith. Where are your sldprt files? are they next to your sldasm?
Some CAD application separate parts and assembly files. Solidworks does it and usually you have an assembly file that refers to other assemblies or part files directly. So when loading an assembly file Datasmith or Solidworks will look for the parts that are referenced in the assembly. Here they are missing, hence the warning you get.
I got the same loading in solidworks directly.
In some 3D viewer I can visualise the model but I guess it is some lightweight version of the model that is stored in the assembly for previsualisation. In your case this model might not be the best to work on.
You can look at some automotive materials here Automotive Materials in Epic Content - UE Marketplace
and for replacing material you can do it manually or automate it Visual Dataprep Unreal Engine 4.27 Documentation
If that means you are a member of EPIC Games, I would like to take this opportunity to thank you all for giving us UE 5. I come from a software with many limitations, and right now Unreal seems like a beast to me. A beast with almost unlimited potential. Also, the staff and the community here are all super friendly and I like it.
Theorically the best way to get solidworks into UE are to either load the solidworks file directly in UE or use the solidworks exporter to udatasmith file and then import that in UE.
Solidworks importer is still under work but should get better as version are released.
Hey guys I have a pretty large project that I am working on, with many different moving components. I have made many of the assemblies already and I need to integrate them together. I realize that I could put all the parts together and in one large project and it will work fine, but I don't really feel like doing all my hard work of mating everything all over again. Is there a way to insert assemblies into other assemblies and have the inserted assembly still work. So far every time I insert an assembly into another one none of the mechanical mechanisms work, it is just one large hunk of stuff. Is this possible? Thanks
If you click on an assmebly or a new part you create you will notice an option that says Form New Sub Assembly Here. You should be able to create sub assemblies with out any problems but ive never tried to carry constraints into them so ill have to play with that a bit.
I have the same methods as shift and I will have to agree that there are always fiddling to do at the end of every stage. I like to get my assemblies together where there are joints. for example an engine. I would assemle the pistons in one assembly, then insert multiple assemblies into the block. even then it takes me a long time : /. the way I got my practice on these things was to find a complex assembly online then disassemble it and try to reassemble it again.
When running a simulation, you must have the Scan Engine in Active Mode, rather than Configuration Mode. To switch between the two is simple: just right click My ComputerUtilitiesScan Engine ModeActive Mode:
Whenever any configuration changes are deployed, the Scan Engine will automatically switch back into Configuration Mode. If the deployment operation did not cause the Scan Engine to transition to Active Mode, you must ensure to set it to Active Mode before running your code.
Your drive must also be enabled whenever you are commanding a move. There are two ways to enable the drive. One of these is through the Interactive Test Panel for each axis. Right click on the Axis in your project and choose Interactive Test Panel. The buttons on the bottom (#1 in the figure below) can be used to enable or disable the drive. Once enabled, the Drive Enabled indicator (#2 in the figure below) should be green.
To ensure that the drive is enabled each time you switch to Active Mode, you can check Enable Drive on Transition to Active Mode. This is found in the Axis Configuration dialog for each axis in your project (right click AxisProperties to pull up the Axis Configuration dialog).
The SolidWorks Assembly in the LabVIEW project and in SolidWorks must match. If any changes are made to the assembly in SolidWorks, you must also apply the changes to LabVIEW. To do this, simply right click on the SolidWorks Assembly in the LabVIEW project and choose Synchronize to Assembly.
To use SoftMotion with SolidWorks, you must activate the SolidWorks Motion Add-Ins. To do this, select ToolsAdd-Ins in SolidWorks and check the boxes for Start-Up to ensure that you don't have to re-enable the add-in every time you restart SolidWorks. Note that you must have SolidWorks Premium to have the SolidWorks motion add-in option. See the SolidWorks getting started guide for more information.
SoftMotion for SolidWorks only works with motors configured as motor type distance. Ensure that you are using the proper type of motors in your assembly. By default, when adding a motor to a SolidWorks assembly, it will be a Constant Speed motor. This must be changed to distance mode to interact properly with LabVIEW SoftMotion for SolidWorks.
It is possible that you have run out of RAM to run the simulation. SolidWorks recommends 6GB of RAM or more on a Windows 7 x64 operating system for optimal performance. See the linked website for more details about the minimum and recommended system requirements for SolidWorks.
Check to ensure that your motors are set up with the proper conversion rates. For a linear motor, this is assumed to be 1 count/mm for encoder counts/unit. For a rotary motor, this is 1 count/degree for encoder counts/unit.
Because of the intensity of the calculations required to perform a SolidWorks simulation, the speed of the models movements may appear to be slower than real life. These movements are correct with respect to simulation time. Setting a slower scan period will speed up the simulation speed. The scan engine period is set in the target properties of the LabVIEW project (right-click My ComputerProperties or RT TargetProperties).
Here you can see what makes this a double-acting engine. The piston is double-sided, and there is a combustion chamber at each end of the piston travel. While one side is drawing in a fresh charge on its intake stroke, the other side has just finished compressing its charge and will soon fire its spark plug.
All material, including the SolidWorks drawings, relating to the construction of the Snow Engine Model presented on this site is free to use any way you see fit. However, no guarantees are made regarding the accuracy or correctness of the material presented here.
The above assembly files need the following part and sub-assemblies. The parts in the zip archives below are named according to their designations within the book and include only the solid models. If you need dimensioned drawings, purchase the book.
NI SoftMotion for SolidWorks enables mechanical, electrical and control engineers to collaborate by creating a virtual prototype of the motion control system that integrates mechanical simulation, motion control software, and sensor feedback. As soon as you have a CAD drawing, you can begin prototyping the machine design long before you incur the expense of building a physical machine. The new tools enable you to:
To find shipping examples that demonstrate all of the different motion commands available, launch LabVIEW 2009 and navigate to Help>Find Examples. Then in the Example Finder go to Toolkits and Modules>Motion Control>NI SoftMotion. You can find SolidWorks specific examples under the Mechatronics>SolidWorks subfolder.
Post your questions and comments to the Virtual Prototyping Community portal. Please also use the community site to discuss your application, share tips and tricks and comment on the virtual prototyping tools.
NI SoftMotion for SolidWorks requires an additional activation that must be applied in addition to the NI SoftMotion activation. This additional activation is included at no additional charge with the purchase of the NI SoftMotion Module Standard or Premium. The activation is done by applying a special serial number.
Now you can link to the assembly from LabVIEW and use NI SoftMotion function blocks to create motion profiles using any available move type. Complete the following steps to add a SolidWorks assembly to the LabVIEW Project:
1.) Deploy an NI SoftMotion resource either for the first time or with updated information. You can deploy all resources at the same time by clicking each resource while pressing , then selecting Deploy from the shortcut menu.
Note: If you deploy an axis but have not made any configuration changes to any of the associated resources, the simulation does not start because the NI Scan Engine did not switch to Active mode. In this case you must manually switch to Active mode using one of the other methods.
2.) Switch to Active mode manually by right-clicking the SolidWorks assembly in the Project Explorer window and selecting UtilitiesScan Engine ModeSwitch to Active from the shortcut menu. You must have already deployed your motion items for this to work correctly.
1.) Switch to Configuration mode manually by right-clicking the SolidWorks assembly item in the Project Explorer window and selecting UtilitiesScan Engine ModeSwitch to Configuration from the shortcut menu.
Note: It is not recommended to click Stop from within SolidWorks. In this situation, NI SoftMotion returns fault FF82 (External Termination Fault) on all axes and the NI Scan Engine remains in Active mode, but SolidWorks does not perform further motion calculations. You must manually switch to Configuration mode, then back to Active mode to restart a simulation.
3a8082e126