I've added some info into the 2.5 manual about calling files and that 
the names are case sensitive.

John

On 12/23/2011 10:08 PM, BRIAN GLACKIN wrote:
> I have been working to add the ability of using part files that are called
> from a "part production" program.
>
> The NGC file I am using is found here
>
> http://pastebin.com/3mB7Ma9c
>
> When Line 19 calls o<square>   (square.ngc found here
> http://pastebin.com/QDfNDmek)  THe routine generates 2 parts with cuts down
> to 0.75"
>
> If line 19 calls 0<b_5in_3>  (b_5in_3.ngc found here
> http://pastebin.com/pvuYzZCN) the file will abort loading with an error
> message telling me I have an unknown o command around line 81.
>
> I was originally able to generate the parts when I cut and pasted in the
> code.  When I used the file call, this error occurred which prompted me to
> create the square.ngc file as a simpler test.  Since square.ngc works, I am
> completely baffled by the error.  If anyone can take a quick look at this,
> I would be most appreciative.
>
> Brian
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
> _______________________________________________
> Emc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-users

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to