11-10-2012 02:03 PM
Hi,
I noticed that the examples shipped with NI Softmotion module is not updated (SoftMotion>Mechatronics). Although the directory has been changed, the example still points to LabVIEW 2009 folder. I also would like to ask whether these examples was tested with LabVIEW 2012 as it doesn't run with my machine which has LabVIEW 2012 and Solidworks 2010 SP4.
Your help is much appreciated.
P.S: I apologize for double posting since no single reply was mentioned on Motion forum.
11-11-2012 02:42 PM
The problem seems to be with Scan Engine.
Here is a screenshot of the error mesage when deployment:
Configuration:
OS: Windows 8 Final
LabVIEW Version: 2012 with all updates installed
NI SoftMotion Version: 2012
Solidworks Version: 2010 SP4
I doubt the problem lies in OS as all examples are running flawlessly except that with Mechatronics Examples. Hope to get any response from NI SoftMotion Team. Thanks for your assistance in advance.
11-12-2012 06:51 PM
Hi Waleed,
I think this actually is an OS issue. It looks like certain dependencies that SoftMotion requires for SolidWorks simulations are not getting installed properly in Windows 8. I'm going to have to look at this closer to see what dependencies those are. I'll keep you updated.
Thanks,
11-13-2012 07:19 AM
11-14-2012 11:44 AM
Hi Waleed,
You were right that this is not a Windows 8 issue. It is actually caused because SoftMotion is not installing the dlls required to use SolidWorks. One workaround is to install the LabVIEW Real-Time module, which will install the missing dlls and will allow you to use SolidWorks.
I am working on a workaround that won't require you to install more software; unfortunatley, it is not as simple as copying the missing dlls to the computer. I will keep you updated on my progress.
Thanks,
11-15-2012 12:22 PM
Thanks Pauls,
I'll try to install the real time module and re-run the shipped examples. Hope to get this fixed in an upcoming patch for SoftMotion Module. I'll report the result as soon as I reach my development machine.
Thanks Paul once more for your response to my issue.