-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not start #67
Comments
The exporter creates a log file in sw_logs in your home directory. Could you please attach an archive of that directory? It might shed light on the issue. |
The other user on rosanswers just posted that installing with full admin privileges cleared the issue for him. As soon as I have access to the Solidworks machine again I will first try re-install making sure to use full admin, and if that fails will pull the log. |
Oh good to know. I'll work on creating a more transparent installer in that regard. |
OK, have an update. My M.E. workmate is working remotely today, so I don't have the SW machine with me. they tried this and report the following:
They neglected to send me a log, but I will ask for one and attach it when I get it. |
We are on service pack 4 of SW2018. Exporting a single part, not an assembly. |
Past the permission issue but stuck on the object reference crash. It appears to me that the message: "Object reference not set to in instance of an object." is a generic Windows scripting error message. (I may be wrong here, as I do little Windows development.) In any case, I am thinking that this message could come from a number of causes that all end up in the "null reference" category. So... maybe something changed in recent service packs of Solidworks such that the sw2urdf script doesn't fetch something any more? Is there some setting missing in the SW model that we may have overlooked? |
Looks like the install issue was resolved and the object reference crash has been resolved in #72. |
I would like to re-open this issue because I experience exactly the same behavior on SW2018 SP4/SP5 - the plug-in installs just fine, but would never run thereafter. I tried to run the plug-in installer and SW on behalf on regular user as well as "Run as Administrator" - still nothing. When I check the checbox in the "Add-ins" menu in SW and hit "OK", nothing appears under "Menu -> File", and the checkbox becomes unchecked when I open "Add-ins" after that. |
And the log files are pretty much empty:
|
Also have the issue on Solidworks Premium 2020 SP3.0 I have a few logs that look like @mbait 's above and some that have the two additional lines as below
I am working on an admin account and tried installing the plugin using the installer with "Run as admin" |
Checked by going through the development instructions and running the plugin in debug mode from visual studio 2017. It looks as if the "ConnectToSW()" method is never called on my machine (which explains the log output). Any help is much appreciated .. |
I figured that I can download older Solidworks versions through the customer portal with my license. Have the exporter working now, Solidworks Premium 2019 SP3.0 (<= guessed this one according to release date) Log now looks like this:
So summary:
|
See this Q on rosanswers: https://answers.ros.org/question/325713/sw2urdf-v15-wont-activate-in-sw2018/
In addition to my report, another user reports that sw2urdf seems to install correctly but does not start. I'm not really sure where to start debugging this, and I am not set up for Windows development. Is there something I can do to start debugging this without having to spin up a Windows development environment?
The text was updated successfully, but these errors were encountered: