Creating a Plugin to convert new SolidWorks file to old Solidworks Versions

Hi

In my opinion... If you can record macro which will register all steps of full document rebuild "ForceRebuild" (Crtl+Q), then you are able to record whole structure of feature manager tree.
Then just play macro in older version, and ... here we go.
I dont know how to use API and if such recording is possible but I think that such procedure should be considered if we would like to read files.

Non API method is to save parts in neutral format (parasolid, igs, step etc) and import in older SW version then use FeatureWorks functionality for features recognition and parametrization.

Regards

RadeK

If this is possibe you would have to run the marco in the new version of SW and save the infomation in to a file  then open the old solidwork and run an differnt macro that will read the file and create the part with error catch so it dose not error out on features that don't exist in the old version

I would use the ModelDoc2.FirstFeature  Traverse all Feature and save it in a xml file.  Look up FirstFeature in the API help and there are examples how to Traverse an part

I don't have time to try this but it dose sound like it might work if you can capture the feature info and re-write it

When i have some free time i will try it out

Dammit, I have had this EXACT idea for abhout 6 months now, but I've been sitting on it because I don't know how to program. Also, I will admit that I am a bit selfish and would like to have had the glory

Anyway, since the cat is out of the bag here are my thoughts - in all cases examples are moving backwards from 2010 to 2009 and are working on parts only:

Three main parts to this:

1. Check - Specify the version you wish to go backward (eg 2009) and then this macro will run through the part and check for 2010-specific features (parametric equation-driven curves, multi-body sheet metal) and throw up warnings if any are present - maybe allow parametric equation driven curves to be converted to fit splines. Things such as extend surface, which have changed between 2009 and 2010 in certain circumstances may throw up a warning but proceed anway.

     This can probably be implemented last, since users can just hope for the best on most stuff.

2. Export - saves Feature Tree info to a readable format - TXT or XML, etc. (ever opened an SLDPRT in Notepad? - not like this!!)  Users should be able to open the file and modify values directly (consequences of which notwithstanding).

     Basic features like extrudes should be easy to do. Have the options laid out similarly to the actual feature

     Feature:Extrude

          From:SketchPlane

          To:Blind

          Direction:1

          Distance:10

          Merge Result:1

          Direction2:0

          ...etc, etc.

     Sketches may be more difficult - is it possible to capture and assign entity names? This is important if you have gone back and edited sketch entities such as adding a new line and then deleting an old one.

          How are splines handled?

     What about Features that rely on picks on screen - Delete face, Surface Trim, etc.? Can macros capture this information and export/import it correctly?

3. Import - fairly straight forward - reads the XML file, recreates the part. One consideration here is to somehow make sure that the XML format remains futureproof - make sure that when 2011 comes along and adds a new option for extrudes, the new output won't confuse the 2009 Importer, otherwise you will have to update it.

So that's my 5c - look forward to seeing how this goes! Who knows, if I start on API stuff one day I may even be able to contribute meaningfully

I think this is an excellent idea.  The stark reality is there are very few features ever used which are unique to the newer version of solidworks.  Mostly we are using exactly the same features, just in the newer version of solidworks.

As for parasolids.  I personally much prefer IGES.  Colours are preserved and I've never had an IGES open up with a model standing on it's head (front and top planes swap).  It's ironic that an external format works better for me than solidworks internal formats.  It also means other users regardless of software package can be sent files without having to resave in another format.  Inventor, Pro-E, solidedge, no problems.

For backwards compatibility I archive all of my models before changing to a newer version.  So if I get stuck with a bug riddled service pack or release I can go backwards and still have everything available.

www.translationtech.com

Currently can convert SW 2001 through SW 2008.  Convert SW 2008 models back to earlier versions.  Full feature tree converted (features, sketches, planes etc).

It's totally possible.  The question is, would you really want to go there?  We all know that fresh SP's have new features that don't exist in previous versions, so the models will not be stable even if work-arounds are made to help with that.  Design intent can and will probably be lost within "more complicated" or feature driven models.  And don't forget about the external reference nightmares within assemblies.  It's like you are trying to create the 1,000 mpg carburetor.  If you some how you did develop a retro file conversion program, you my friend would simply dissapear, and know one will know what happend to you.  Just kidding.  Dude, you have SW finest working against you.  They would stand to loose millions in sales.  People not being forced to updgrade every stink'n year to read their customer's "newer" files.  There is definately a market for it.

Jason,

Maybe if you had control, you could delete your own post.

"Time to learn to code in the API!!!!!!!!!!!! I am excited."

"Does anyone want to help me with the coding?"

The SolidWorks community will all be holding it's breath while we wait for you to learn how to code and write your macro, which has been thought about by just about everyone who uses SolidWorks, and has not been done not because it wouldn't have some value, but because the development of the software is focused on moving the kernel forward, not backwards. Its easy to extrude a sketch in 2001 and 2010, and record a macro of both, look at them both, and say hey, I bet I could create a macro to convert this 2010 extrusion back to a 2001 format. These posts you wish you could delete are tring to save you some time, because as your wax wings start to melt when you give these 'ideas a try', you'll understand that some of the veterans here are trying to give a greenhorn some good advice. You are opening a can of worms, and some stones are better left unturned.

If you have the time to just play around for the sake of learning, then thats cool. Good Luck. Wish I had time like that.

Ryan

This type of plug in would allow a very high compression of a Solidworks file. I made a table of all of the information for an examble part and found that the information required to re-create the part is 1200 times smaller than the  solidworks file. Of course solidworks saves a bunch of data to make files open quickly.

This is important to me as I would like to send and receive very compressed files when I am on my boat. My satphone communicates at 4800 baud and $1.19 per minute. I will find work impossible on the cloud over a satphone. Just have to walk the beach instead.

I just got ask from fixitchris[Codeplex]  is it Legal  to redistributed Interop assemblies

This will make it Impractical to create this becase the use would need the the new version of SW then They would not need to convert it back