Parasolid error

[mmetzinger]

I have imported a parasolid from Solidworks, it comes in, and when I shade it, there are 2 surfaces that won't shade ( or aren't there). Then, when I try to machine the solid, I get this:

 

Parasolid® Kernel Interface Error:

KI error code: 993

Failure to represent entity in B-spline form

 

What does this message mean and how do I get this solid to come in without a problem?

[MACHINEMASTERG]

first let me ask what version mcam???what version solidworks(sw2003????)and did you convert parasolid x-t or a direct conversion from native solidworkfiles( sldprt)????????ive had simaler errors when converting x-t but have virtualy error free convertions doing a convert from the sldprt files >>>>>

[mark l]

I've had this same problem with UG files, 99.9% of the time it is a problem with the parent file. If you zoom in really close you may be able to see where the surface loops back into itself around one of the corners, it looks fine in UG but if they zoom in really close they see the loop. I would suspect it has something to do with the parent file tolorence and the Mastercam tolorence

[specprogrammer]

I'm having a similar problem, but the error i get says sp curve lies off surface. but i have got the same error as you before. we are using mcam version 8.1 and solidworks version 2003. i have tried different parasolid version numbers but havent had any luck. I convert from x_t. how do you convert from a sldprt file?

 

[ 02-28-2003, 10:33 AM: Message edited by: specprogrammer ]

[MACHINEMASTERG]

quote:

---

how do you convert from a sldprt file?

 

---

if your using v8 and sw2003 you have to run the sw2003 chook other wise to convert sldprt under convert parasolid when the file box opens up at the bottom change it to sldprt defalt and the sldprt files will only show up and then pick it and convert it

[Guest CNC Apps Guy 1]

If the problem persists, you should e-mail the file to [email protected] and describt the problem. I had that problem with a certain file in V8 but in V9 the problem was fixed actually it was a kernel issue.