-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Radoslaw Koneczny May 16, 2010 7:12 AM (in response to Jason Nicholson)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
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Robert Conklin May 20, 2010 3:25 PM (in response to Radoslaw Koneczny)The recording, capturing the steps, of a rebuild seems like a plausible idea. To use this in an older version to recreate would be cool. Can it be done? Even if it came thru with errors I am Always fixing those anyway.
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jacob Cordingley May 20, 2010 3:52 PM (in response to Jason Nicholson)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
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson May 21, 2010 9:37 PM (in response to Jacob Cordingley)I am going to give these idea a try. Time to learn to code in the API!!!!!!!!!!!! I am excited.
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Kieran Choy May 23, 2010 3:17 AM (in response to Jason Nicholson)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
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Simon Richardson May 23, 2010 5:10 AM (in response to Kieran Choy)Seriously? why do people insist on going backwards?
Maybe I am missing something, but surely you want to get rid of the design tree (and lock the part or assembly down) especially if you are sending it out to a customer or another designer.....less chance of fiddling or corruption?
If you really do need to get a body or surface, a single part or full assembly, into an older version of SW, just lock it down using parasolid format, and reopen it in the older SW.
You will need to set the "save as" options to go to an earlier parasolid version - eg version v18.0 = sw2008 v19.0 =sw2009?
This should prevent any errors, or loss of minor any details, and save time as you wont have to track down and repair any rebuild errors, and you will have a robust part that will not suffer from future version rebuild errors.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Van Stokes May 23, 2010 8:20 PM (in response to Simon Richardson)The argument is been hashed over and over again and over again.
Solidworks does NOT want to support older versions because it's a marketing scam to force their customers to purchase the subscription. It's that simple. There is NO valid logical reasoning for the lack of this feature. I've heard all their excuses and technical mumbo-jumbo. I'm also a programmer and their reasoning just doesn't pan out. But stop and consider this: Why would a vendor program its software to export/import using other vendor formats but not their own format? I mean, review Simon's solution he just advanced:
Simon Richardson wrote:
You will need to set the "save as" options to go to an earlier parasolid version - eg version v18.0 = sw2008 v19.0 =sw2009?
This should prevent any errors, or loss of minor any details, and save time as you wont have to track down and repair any rebuild errors, and you will have a robust part that will not suffer from future version rebuild errors.
Really!?! This is the best way for a vendor to Save-As to a previous SW version? This is just pathetic.
I'm not picking on you Simon, I know you are trying to help. Thanks!
Simon Richardson wrote:
Seriously? why do people insist on going backwards?
The reality is many of us nedd this feature because we have to interface with other vendors and customers running different versions of SW. Not everyone upgrades to the latestest and bugiest SW version. Those of us who have been around a very long while know to NEVER upgrade production to the latest SW version until it reaches at least SP4 (semi-stable release). Anything before SP4 is just a release candidate.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Simon Richardson May 24, 2010 12:57 AM (in response to Van Stokes)Hey Van-
I am a SW user, not a vendor, (please dont swear at me like that!)
Yup I do hear where you guys are coming from.
I just have to scratch this scab though- I still dont see why one would need to have a "live" SW file to communicate with others....what am I missing? Even when I am working with someone else running the same version of SW as myself, I generally still only send out parasolids (or PDFs for drawings).
I guess if you are using configured parts it would help minimise the number of files, but otherwise? Just give them a dumb file that they can chop, and add to, as much as they want, without upsetting the apple cart!
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Kieran Choy May 24, 2010 9:59 PM (in response to Simon Richardson)A lot of contractors do work with multiple customers, all on different versions of SolidWorks. It's very easy to accidentally open up an old file in a new version and then save. Granted, you should have backups but this whole going backwards thing is a case of: it doesn't happen very often, but when it does, you REALLY need to be able to go backwards.
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Roland Schwarz May 25, 2010 8:12 AM (in response to Van Stokes)Solidworks does NOT want to support older versions because it's a marketing scam to force their customers to purchase the subscription. It's that simple. There is NO valid logical reasoning for the lack of this feature
I know conspiracy theories are fun, but this one is as valid as the rest. There is at least one reason. Every new release of SW has new internal parameters that are not in the previous version. In some cases (like lofts), the entire algorithm to develop a feature may chage, even if the user interface looks largely the same. If you're going to write to previous versions, that is the single biggest issue.
AutoCrayon can go back to previous versions because it is basically the same repackaged flan it has always been for the last twenty years.
A couple years ago a Baren-Boym was promising a program to go back to previous versions. It never really materialized.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
chris misztur Jun 12, 2010 7:04 PM (in response to Van Stokes)SW is an extensible CAD Platform therefore it grows and changes. If you look at the OpenDoc function, it has gone through 7 iterations. The reason why the old signatures are left is for backward compatibility. If the code did not chang with addition of new functionality then SW would not be where it is now.
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Dan Miel May 24, 2010 10:12 AM (in response to Simon Richardson)For some of us it can just be the challenge of making a program like this work that makes it worth writing.
Dan Miel
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Brian Lindahl May 24, 2010 10:37 AM (in response to Dan Miel)If this is a potential reality, of writing a chunk of code to make a parametric model in earlier versions, it seems it should work WITHOUT having to rebuild the existing model, as that would require the current version that the model is to be exported from. It would be WAY neater if something like SWDocManager.dll would access the feature names and property manager input values to a sufficient level that the model could be extracted. This would (or might) allow for all features that are recognized at the current version of the SWDocManager to be written to the XML file, and the current version of SW on the the machine should then recognize all feature types in the XML file. Problem is, I don't think the features are accessible from the current SWDocManager. Just things like external references and custom properties is what I am familiar with. Add this to the wish list!!
-
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Dougal Hiscock May 24, 2010 11:59 PM (in response to Jason Nicholson)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.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Luke Malpass Jun 7, 2010 5:54 PM (in response to Dougal Hiscock)I think it is certainly a viable program/solution. However, the simple fact that the time it would take to create such a program would not be worth the reward (else I would of made it a long time ago).
The more you work with the SW API in depth the more you learn its little quirks and bugs, and the first thing that comes to mind when contemplating a solution like this is that it would be far too problematic and the maintenance of such a program would be quite simply crazy.
Nice thoughts though.
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Tim Turpin Jun 10, 2010 12:52 PM (in response to Jason Nicholson)Currently can convert SW 2001 through SW 2008. Convert SW 2008 models back to earlier versions. Full feature tree converted (features, sketches, planes etc).
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Don Vanzile Jun 10, 2010 12:55 PM (in response to Tim Turpin)I'm sure for simple things this works great. But I'm sure there are huge obvious limitations with something like this.
Don
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Roland Schwarz Jun 10, 2010 3:31 PM (in response to Tim Turpin)This is where Acc-u-Trans literally builds the model feature by feature right in the target CAD system.
(from http://www.translationtech.com)
Interesting. Not really a conversion. More like an automated rebuild. I would be interested in seeing some results.
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Craig Siebert Jun 11, 2010 4:03 PM (in response to Jason Nicholson)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.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Anna Wood Jun 11, 2010 4:13 PM (in response to Craig Siebert)Sorry to be a wet blanket here......
If it was just as easy as you all are thinking wouldn't you think some enterprising company would have created a feature by feature translator already. Years ago.....
Just Sayin'
Cheers,
Anna
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 11, 2010 4:16 PM (in response to Anna Wood)If i could delete useless posts of this thread I would. Anna, http://www.translationtech.com/
http://www.translationtech.com/ claims to have a fully parametric conversion from 2008 back to 2001. I think that's worth a look.
I have not had time to explorer this yet. Does anyone want to help me with the coding?
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Don Vanzile Jun 11, 2010 8:06 PM (in response to Jason Nicholson)Multibody parts were introduced in 2003. Does anyone know how to open multibody parts in 2001 if the code isnt' there for it.....
That's just one of doznes.
Guys, come on. There will be LIMITATIONS!
Why does everyone think software is magic!? Why doesn't my 2010 mustang gt engine compatible with my 1964 mustang? It's amazing how many mechanical engineers think you can just make everything work with older technology. The point is, why would you rework such an older model when software tchnology is moving forward so fast? Why doesn't my blu-ray work in my DVD? Are we that naive?
If you want backwards compatibility sitck with dumb 2d geometry where things never change.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Dougal Hiscock Jun 11, 2010 9:01 PM (in response to Don Vanzile)Yes there will be limitations. But in models where no such limitations exist, why is there no backwards compatibility?
Probably 99% of the models I use are extrudes, cuts and revolves. Most (in fact almost all) were created in prior versions, yet once opened in a later version they won't work even in the version they came from.
A 2010 mustang engine can work in a 1964 car, similar transplants are common place, so your analogy is a little lacking. This is not about physical limitations, this is users attempting to fix a problem solidworks has created.
Software technology moving forward so fast? I don't see it. I see new features of dubious value and poor reliability.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Lenny Bucholz Jun 12, 2010 11:15 AM (in response to Dougal Hiscock)Ok Dougal more from me!
SO you may only use the same features cuts, bosses, fillets and so on, but other uses features that have had things added to them thru out the SW evolution.
lets take your boss extrude for example, depends how far you want to go back, you were'n't able to a offset extrude, meaning your sketch is on a plain that is in the wrong position and you want it to start higher than the plane or you select the vector portion in the propoties to push the extrude where you want it to go, those option might not be in the older version you want to save back to.
You build a part with a feature not in the older version, you put extrudes, cuts, sweeps, fillets and so on on to the model, you try to save it back, remember ther is history involed in this whole proccess, the new feature can't be made....there is no feature for it and every feature after that is gone, thear is no parent to create it, no face, no edges...NADA!
Ok so the mustang engin, not quite. So here is mine 62 bug, 6 volt system........now try to put a 12 volt battery in it....BOOM!
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Dougal Hiscock Jun 12, 2010 6:29 PM (in response to Lenny Bucholz)As I've said, there will always be limitations. I notice all the detractors are quiet on the issue of parts designed in an older version of solidworks which have been resaved in a newer version. This is in fact my biggest need, getting library parts usable for sub-contractors who don't have the same version of SW that I have. Sometimes I am that sub contractor.
It's not hard to convert a 6v vehicle to 12v. Getting a decent stereo is a good motivator there. Not to mention indicators that people can see.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Lenny Bucholz Jun 12, 2010 10:45 PM (in response to Dougal Hiscock)lets take a lesson from the ProE days! we would have 2 to 4 versions of Pro on the computer so if a client had an older one we would work in that.
On my computer I have 7 versons back of SW so that I can do the same thing. I do know of some companies that bought the lastest version of SW and need a older version because of a vender so they asked SW/VAR to get a regcode(SW2007sp2 and older) to be able to make parts in that. as for people complaining about saving an older file in the lastest version, no one complaining because thats what they upgraded for. most will finish the project in the older version and start new stuff in the current.
bigger companies sometimes don't upgrade until sp5/6 or even until the next release is in beta. I know I tech supported 3 yrs and heard the samething over and over again.
I have the samething if i want to save to an older version of SurfCam..it can't because they have changed how they calulate the tool path and it fails. the geom, can go back but not the NC portion.
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 13, 2010 12:35 AM (in response to Lenny Bucholz)Offset extrude = project sketch offset distance onto new plane.
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 13, 2010 12:35 AM (in response to Don Vanzile)1. Multibody Parts = two files for each body in an assembly with incontext references. That's how you deal with Multibody parts.
Please highlight more of the difficulties so I can see them before I run into them.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
John Layne Jun 13, 2010 7:12 AM (in response to Jason Nicholson)Some possible difficulties:-
Curvature continuous fillets
Raised Degree splines
Boundary surface
Filled Surface - with "fix up boundary" checked
Negative dimensions
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Lenny Bucholz Jun 11, 2010 8:28 PM (in response to Jason Nicholson)so you buy the new software to translate back to a older version....well you just payed for your upgrade...didn't you???????????? just asking
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Anna Wood Jun 13, 2010 12:12 AM (in response to Jason Nicholson)Jason,
Sorry if you feel my post was stupid.
After looking through their website I will stand by my post.
I am sure there is a reason the Translation Tech folks have not marketed any new translation code in the last couple of years. Looks like they have not updated their code since 2008 with Windows XP as an OS for any of the major software packages they offer translation services for. It is probably expensive and not enough customers are willing to pay to get the software.
Another confirmation that this is a non-trivial task.....
You do not have any of the experienced coders here beating a path to your door to help you create a program.
How much are you willing to pay the coders here to spend hundreds and hundreds of hours helping you do programming? They are not going to do it for free.
Also, be sure that I understand that the reason none of the major vendors will allow you to save as an older version is to lock customers in to the upgrade path. It is a business decision no doubt. Not sure that if I was in their shoes that I wouldn't do the same thing.
Cheers,
Anna
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 13, 2010 12:33 AM (in response to Anna Wood)Ann,
I am sorry. I am fustrated with the quibble and none helpful posts. I wish I had control so I could take down nonrelated posts.
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
David Oustifine Jun 11, 2010 4:35 PM (in response to Anna Wood)If I had a dollar for every time this question came up in a demo, training class or tech support call....
If you can pull that off you would no doubt be inundated with customers!
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 13, 2010 12:37 AM (in response to Jason Nicholson)I accidentally clicked "correct answer." Sorry. Please don't stop the posts.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
1-1H9DGPXX Jun 14, 2010 8:11 AM (in response to Jason Nicholson)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
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 14, 2010 10:00 AM (in response to 1-1H9DGPXX)I understand this is a big under taking. I don't think it will be simple. If I could get paid to work on stuff like this, I would work on it full time. However, I don't see getting paid to work on it.
With respect to a time line on this kind of a project. I think it will take me a year. So basically, I am saying don't hold your breath and wait on me. This is still the exploration phase.
.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Maynard Viersen Jun 14, 2010 12:08 PM (in response to Jason Nicholson)I think it would be a great "Group" project. if you could keep the code online, where anyone could add to it, and keep posting problems so they could give answers, it would probably be a great learning experience for all of us and would get done quicker.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jacob Cordingley Jun 14, 2010 12:17 PM (in response to Maynard Viersen)That a good idea
here is a web site that is just for that
there is an place for
- Downloads
- Discussions
- Issue Tracker
- Source Code
- People
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jacob Cordingley Jun 14, 2010 3:30 PM (in response to Jacob Cordingley)I look in to some thing and got this
my Idea is to open the new Cersion run a program that captures each feature then save it to a user setting Var
then open the old SW Version run a program that reads the user setting Var and insert the features
what i have in this version
it will store all Feature in userSetting
and read the features
but I can't find a way to add a Feature to a new document
also to make sure this will even work i just trying it on Sw2010 to SW2010 if it works then I will go to the next step on older version
-
SWConvertBack.zip 726.2 KB
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 15, 2010 3:36 PM (in response to Jacob Cordingley)Jacob,
Thank you for help and contribution. It is much appreciated!!!!!!!!!!! I will take a look at what you have done probably on Friday night. The next couple of days are full for me.
-Jason
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jacob Cordingley Jun 15, 2010 4:12 PM (in response to Jason Nicholson)I create a codeplex project at
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jacob Cordingley Jun 15, 2010 5:02 PM (in response to Jacob Cordingley)I will add people I just need there CodePlex UserName
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jason Nicholson Jun 16, 2010 8:12 AM (in response to Jacob Cordingley)You sound well versed in the API. I appreciate your expertise.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Roland Schwarz Jun 16, 2010 12:19 PM (in response to Jason Nicholson)Anna and Luke are also well-versed in SW API.
-
-
- Downloads
-
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Rick McWilliams Jun 15, 2010 5:33 PM (in response to Jason Nicholson)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.
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
chris misztur Jun 16, 2010 8:39 AM (in response to Rick McWilliams)Rick, when you're on the space station, there should be a direct link up with one of the satellites.
Are you talking about recreating it from scratch or driving an existing part with external data?
-
model data communication between SW versions
Rick McWilliams Jun 17, 2010 2:15 PM (in response to chris misztur)I think that the essence of the problem is a plug in that will read the feature tree, sketches, and relations of a solidworks part. This data is very much more compact than the solidworks file. The plug in would run inside another version of solidworks, read the data file, and recreate the part. This requires both the source of the file and the receiver of the file to run the add in.
I would use this to compress files for transmission over bandwidth limited systems. The satphone that I use is a very old tracphone II that has proven to be most reliable for voice or data. It uses transponders on the geosynchronous direct TV satellite. The transmission delay makes voice communication a bit un-natural. I could carry every Solidworks file that I have ever seen on a stick.
My vessel is somewhat limited in speed; 8 knots is far short of escape velocity. I am lucky that there are accessible desert islands with beautiful beaches and reefs. Now I am stuck at the office.
-
-
-
Re: Creating a Plugin to convert new SolidWorks file to old Solidworks Versions
Jacob Cordingley Jun 17, 2010 1:22 PM (in response to Jason Nicholson)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