08-19-2009 02:36 PM
08-19-2009 05:17 PM
Usually this is caused by a motion control command that caused the axis to go into a fault protection mode. Here are some debugging suggestions:
- Make sure the the SolidWorks Motion is active, navigate in SolidWorks to Tools->Add Ins and mark the check boxes on the left and the right of the SolidWorks Motion item.
- In the LabVIEW project, right-click on My Computer and got to Properties. Then go to the Scan Engine tab and make sure the box is checked next to Start Scan Engine on Deploy. You may also want to set the Scan Period to 10 ms if it's not already. If the value is above 5 ms, you'll get a warning message when you deploy but this is usually just fine for simulation with SolidWorks.
- Individually select each of the motion axes in your project and do the following: Select Properties and then click on the left-most button to configure the Axis Setup. Make sure the box is checked for Enable Drive on Transition to Active Mode.
- Now select all of the motion items (including My Computer) in the LabVIEW Project, right-click and select Deploy. Normally, since this is your first deployment it will start the SolidWorks simulation running and so your are ready to run the LabVIEW shipping example. If not, right-click on My Computer and select Utilities>Scan Engine Mode>Switch to Active.
- Once you are in active mode and the simulation is running, right-click on the motion axis and go to the Interactive Test Panel. This should show you that the axis is enabled and there are no faults or errors. When you are finished, close the test panel and run your LabVIEW motion control application.
10-21-2009 04:30 AM
I found a way to reproduce this error is to stop the Motion Study in SolidWorks. I have already addressed this issue at R&D.
Here is a workaround:
I hope this helps,
Jochen
03-02-2010 05:53 PM
I have a problem deploying the axis using one of my assemblies, the error than i get is "(Hex 0x80040423) The operation failed because of conflicts, in general", i upload 2 videos where i assembly the "Axis1-Across" of the example from zero, the first one is http://www.youtube.com/watch?v=HCSErjd4IFc and the second one is http://www.youtube.com/watch?v=75cwPA4sjBw please check out my videos and tell me how i've done wrong. Thanks a lot.
Ing. Cuauhtemoc Luna
UNAM
Mexico City
04-27-2010 10:20 PM
I have the same problem here.
(Hex 0x80040423) The operation failed because of conflicts, in general
Someone know how to solve it?
04-28-2010 12:26 PM
Hi friends.
Finally i get it!
I only get updates for my software. The Labview 2009 SP1 and the softmotion 2009 SP1 and thats all, everything works now in solidworks 2009 and 2010. The updates can be download in the NI web page. I hope than this information be useful for you. Regards.
08-10-2010 09:13 AM
08-16-2017 12:05 PM
Does anyone have any ideas for similar solutions for LabVIEW 2016? I'm running into a similar problem. Please see my forum post https://forums.ni.com/t5/Motion-Control-and-Motor-Drives/Error-70217-softMotion-cRio-Axis-a-required....
08-17-2017 11:44 AM
Hi aphilipps,
I recently tried this tutorial and it worked on LabVIEW 2016 https://www.youtube.com/watch?v=Q21IxELwGhQ.
If this doesn't throw the error, you need to debug your code and extrapolate the configuration to your application.
There is, though, a bug found in the interface with SolidWorks. If you are moving a rotatory motor eventually fails to converge and the only possible workaround is to use a linear motor instead of a rotary motor.
Regards,
PedroR