save as parasolid favor

[grunt58]

Can someone open the attached Fanuc robot saved as SW2011 and resave as a parasolid? We haven't upgraded yet still stuck on 09.

Wouldn't let me upload it all in 1 zip file so attached is zip 1.

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[grunt58]

zip 2

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[CorBlimeyLimey]

Here's a version 20 parasolid.

 

[grunt58]

Thanks. It gave me a "inconsistent modeler version" error, not sure what that means.

Do you mind trying as something else? step? Different parasolid version?

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[TheTick]

You may need to dial back to an earlier version of Parasolid.

 

[grunt58]

Me? How do I do that?

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[CorBlimeyLimey]

Look to see what version of parasolid you can export.

 

[grunt58]

19.1 is the latest version I have.

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[CorBlimeyLimey]

OK, try that version then.

 

[grunt58]

Perfect. Thanks for the help.

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0

 

[looslib]

FYI - The "inconsistent modeler version" error is from Parasolid when you try to open a newer version file in an older version of the kernel. It has detected a schema mismatch.

I use to keep a spreadsheet showing the Parasolid version used in which version of UG/NX, SW and SE.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[KevinDeSmet]

That's the funny thing with Parasolid, I've always wondered if STEP has this issue too, it doesn't right? Unless you're exchanging different flavours of it (203, 214, 203ed) so I guess from an end user perspective, it does actually also have this problem because each flavour is just called .step and it may fail to import in older systems.

Certified SolidWorks Professional

 

[kellnerp]

Here's a version 20 parasolid.

CBL did not know that 2009 used 19.1, not 20.
The OP should have specified the version rather than let the group guess which version of parasolid '09 used.

Lesson learned, never assume that the group has access to your setup.

Parasolid, unlike VDAFS, STEP and IGES is version specific.


TOP
CSWP, BSSE

http://www.engtran.com

http://www.niswug.org

http://www.linkedin.com/in/engineeringtransport

Phenom IIx6 1100T = 8GB = FX1400 = XP64SP2 = SW2009SP3
"Node news is good news."

 

[grunt58]

I was unaware that parasolid had so many versions and was version specific. I've never had a problem like that when importing parasolids. My mistake, as you said lesson learned.

Thanks for every ones help. If Fanuc would make it a little easier to get 3D models of their robots I wouldn't of had to ask. I went through the process on their website to be sent an iges but never received it. Found this model on grabcad.com

http://grabcad.com/library/fanuc-m-10ia-robot

Thanks again.

Certified SolidWorks Associate
SW2009 X64 SP 1.0
Dell Precision T5400
Nvidia Quadro FX 5600
Xeon 2.5GHz Quad Core, 4GB RAM
XP Pro X64 SP2.0