CAD Forum - tips, tricks, discussion and utilities for AutoCAD, Inventor, Revit and other Autodesk products [www.cadforum.cz] ARKANCE | CONTACT - CZ | SK | EN | DE
RSS channel - CAD tips RSS tips
RSS discussions

Discussion Discussion forum

?
CAD discussions, advices, exchange of experience

CAD Forum - Homepage CAD discussion forum - ask any CAD-related questions here, share your CAD knowledge on AutoCAD, Inventor, Revit and other Autodesk software with your peers from all over the world. To start a new topic, choose an appropriate forum.

Please abide by the rules of this forum.
This is a peer-to-peer forum. The forum doesn't replace the official direct technical support provided by ARKANCE for its customers.
How to post questions: register or login, go to the specific forum and click the NEW TOPIC button.
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Topic ClosedAutoCAD 2015 script error using ScriptPro

 Post Reply Post Reply
Author
emuspe163 View Drop Down
Newbie
Newbie


Joined: 05.May.2015
Location: United States
Using: AutoCAD MEP 2015, Revit 2015, Navisworks 2015
Status: Offline
Points: 3
Direct Link To This Post Topic: AutoCAD 2015 script error using ScriptPro
    Posted: 05.May.2015 at 15:28
I have written a script file for use with AutoCad 2015 with the purposes of running multiple files (about 50) from ScriptPro
 
The file is designed to:
Open the file
Turn off pop ups
Bind all Xref's
Purge the drawing twice
NWCout to Navisworks (2015)
Turn popups back on
Then close without saving
 
When I run the script file within AutoCad it works perfectly but when run from ScriptPro I get the following error:
 
nwexport_FAILED_TO_SAVE_DOC
 
The error does not freeze ScriptPro. It just gives me a FAILED status and continues on to the next file in line.
 
Dows anyone know what this error is reffering to?
 
A copy of my script is below:
 
-------------------------------------
filedia
0
xrefinsert
all
_AecbBldSysPurge
-purge
a
n
-purge
r
n
nwcout
filedia
1
quit
y
-------------------------------------
John Clous
MEP/BIM Coordinator
Gibson Electric
Back to Top
Vladimir Michl View Drop Down
Moderator Group
Moderator Group

Arkance Systems CZ

Joined: 26.Jul.2007
Location: Czech Republic
Using: Autodesk software
Status: Offline
Points: 2124
Direct Link To This Post Posted: 05.May.2015 at 15:42
Not remembering exactly but doesn't NWCOUT need any filenames or overwrite confirmations?
Isn't the Navis file opened? Have you considered using directly DWG files in Navisworks (instead of the exported formats)?
Vladimir Michl (moderator)
ARKANCE - https://arkance.world - Autodesk Platinum Partner
Back to Top
emuspe163 View Drop Down
Newbie
Newbie


Joined: 05.May.2015
Location: United States
Using: AutoCAD MEP 2015, Revit 2015, Navisworks 2015
Status: Offline
Points: 3
Direct Link To This Post Posted: 05.May.2015 at 16:22
Thanks for the reply!
 
Yes, NWCOUT does propt for a file name but when you turn FILEDIA to (0) there are no pop up menus and it prompts you for a default file name with the dwg extension changed to nwc. Then the following line in the script is left blank to denote an "enter" command confirming that default file name.
 
No, the Navisworks drawing is not opened. This would explain the problem if it were and the eror woud occur on the second fle when it tried to write but this is not the case. Running the script within AutoCad just simply creates the nwc file in the parent location.
 
I can not simply append the files into Navis from their current location. The script was created to perform several maintence tasks on each file prior to exporting. I frequently have to perform this procedure across hundreds of files at a time. This process takes an eternity to do one at a time and if I were to simply append into Navisworks I would first have to open the file, elevate the file to the proper elevation, purge the file, save the new file as a "clean, elevated version" then append that file into Navis. the repeat this process 250 times.
 
As I stated in the post, the script runs perfectly within AutoCAD so it's apparently a ScriptPro issue.
John Clous
MEP/BIM Coordinator
Gibson Electric
Back to Top

Related CAD tips:


 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0,176 seconds.