I can't find anything wrong with that STL with either NetFabb or OpenSCAD, so I don't understand how they can do more with an STL from FreeCAD. As far as I know there are only ASCII and binary STLs and they contain the same information. I don't think there is any way to embed any more information. It might be worth checking if it is a binary / ASCII issue but it seems very unlikely if they can open it. On Wed, 16 Nov 2022 at 04:56, William F. Adams via Discuss < discuss@lists.openscad.org> wrote: > > > > ---------- Forwarded message ---------- > From: "William F. Adams" <willadams@aol.com> > To: "discuss@lists.openscad.org" <discuss@lists.openscad.org> > Cc: > Bcc: > Date: Wed, 16 Nov 2022 04:55:43 +0000 (UTC) > Subject: [OpenSCAD] Re: SolidWorks & OpenSCAD interoperability > Unfortunately, CAD software importing STLs is an operation fraught w/ > problems and incompatibilities. > > Best thing to do is to create DXFs which mimic the sorts of > drawings/prints which these folks work with and expect (annotate them well, > and try to design them for ease of machining/manufacture) --- then they can > recreate the file in Solidworks which they can then use their CAM software > to create G-code. > > William > > > > ---------- Forwarded message ---------- > From: "William F. Adams via Discuss" <discuss@lists.openscad.org> > To: "discuss@lists.openscad.org" <discuss@lists.openscad.org> > Cc: "William F. Adams" <willadams@aol.com> > Bcc: > Date: Wed, 16 Nov 2022 04:55:43 +0000 (UTC) > Subject: [OpenSCAD] Re: SolidWorks & OpenSCAD interoperability > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org >

Sorry I meant to send it to the list. On Wed, 16 Nov 2022 at 06:57, nop head <nop.head@gmail.com> wrote: > I can't find anything wrong with that STL with either NetFabb or OpenSCAD, > so I don't understand how they can do more with an STL from FreeCAD. As far > as I know there are only ASCII and binary STLs and they contain the same > information. I don't think there is any way to embed any more information. > > It might be worth checking if it is a binary / ASCII issue but it seems > very unlikely if they can open it. > > On Wed, 16 Nov 2022 at 04:56, William F. Adams via Discuss < > discuss@lists.openscad.org> wrote: > >> >> >> >> ---------- Forwarded message ---------- >> From: "William F. Adams" <willadams@aol.com> >> To: "discuss@lists.openscad.org" <discuss@lists.openscad.org> >> Cc: >> Bcc: >> Date: Wed, 16 Nov 2022 04:55:43 +0000 (UTC) >> Subject: [OpenSCAD] Re: SolidWorks & OpenSCAD interoperability >> Unfortunately, CAD software importing STLs is an operation fraught w/ >> problems and incompatibilities. >> >> Best thing to do is to create DXFs which mimic the sorts of >> drawings/prints which these folks work with and expect (annotate them well, >> and try to design them for ease of machining/manufacture) --- then they can >> recreate the file in Solidworks which they can then use their CAM software >> to create G-code. >> >> William >> >> >> >> ---------- Forwarded message ---------- >> From: "William F. Adams via Discuss" <discuss@lists.openscad.org> >> To: "discuss@lists.openscad.org" <discuss@lists.openscad.org> >> Cc: "William F. Adams" <willadams@aol.com> >> Bcc: >> Date: Wed, 16 Nov 2022 04:55:43 +0000 (UTC) >> Subject: [OpenSCAD] Re: SolidWorks & OpenSCAD interoperability >> _______________________________________________ >> OpenSCAD mailing list >> To unsubscribe send an email to discuss-leave@lists.openscad.org >> >

You're absolutely right. I had to infer what the problem was. I think they confused ".stl" file with ".stp" file. It's only a one letter difference. Sent with [Proton Mail](https://proton.me/) secure email. ------- Original Message ------- On Wednesday, November 16th, 2022 at 12:57 AM, nop head <nop.head@gmail.com> wrote: > I can't find anything wrong with that STL with either NetFabb or OpenSCAD, so I don't understand how they can do more with an STL from FreeCAD. As far as I know there are only ASCII and binary STLs and they contain the same information. I don't think there is any way to embed any more information. > > It might be worth checking if it is a binary / ASCII issue but it seems very unlikely if they can open it. > > On Wed, 16 Nov 2022 at 04:56, William F. Adams via Discuss <discuss@lists.openscad.org> wrote: > >> ---------- Forwarded message ---------- >> From: "William F. Adams" <willadams@aol.com> >> To: "discuss@lists.openscad.org" <discuss@lists.openscad.org> >> Cc: >> Bcc: >> Date: Wed, 16 Nov 2022 04:55:43 +0000 (UTC) >> Subject: [OpenSCAD] Re: SolidWorks & OpenSCAD interoperability >> >> Unfortunately, CAD software importing STLs is an operation fraught w/ problems and incompatibilities. >> >> Best thing to do is to create DXFs which mimic the sorts of drawings/prints which these folks work with and expect (annotate them well, and try to design them for ease of machining/manufacture) --- then they can recreate the file in Solidworks which they can then use their CAM software to create G-code. >> >> William >> >> ---------- Forwarded message ---------- >> From: "William F. Adams via Discuss" <discuss@lists.openscad.org> >> To: "discuss@lists.openscad.org" <discuss@lists.openscad.org> >> Cc: "William F. Adams" <willadams@aol.com> >> Bcc: >> Date: Wed, 16 Nov 2022 04:55:43 +0000 (UTC) >> Subject: [OpenSCAD] Re: SolidWorks & OpenSCAD interoperability >> _______________________________________________ >> OpenSCAD mailing list >> To unsubscribe send an email to discuss-leave@lists.openscad.org