- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
The reasons your job is stopping can be one of a few things; It could be because there is a memory issue with the TinyG. I'm not certain what it's limit is, but I'd imagine it's rather large From what reading I've done, the chilipepper is a program that runs in Windows or Mac environment. So, the memory doesn't seem to be an issue.
So, what does that leave us with? A bad g-code or calculation that is causing it to fail. Without seeing the file, it's not the easiest thing to render an opinion on. You could export and upload the .f3d file and that might give us some clues. File > Export > Save to Local folder. Return to thread and attach the .f3d
To answer your question though about reducing file size; Smoothing is an awesome tool to employ and it can often reduce the file size by as much as 70% (going off memory) There is an excellent thread exploring what Smoothing can do for you, available HERE. Note; not all operations allow for smoothing.
The idea that metal requires more "memory"..yes and no. Metal often requires more conservative cuts, yielding more lines of code. Hence, the memory consumption. However, even moderate complexity molds (in metal) should fit in most modern controls
The difference between each post processor is as subtle as a small code here and there, or to the other extreme, completely different formats using numbers and letters that are completely foreign to many people outside that small circle of users.
Fortunately for you, there is a Tiny-G post processor, so that would be the one you would use.
If you can share your file as well as indicate where in the cut it stopped, that would go quite a ways in getting you sorted out
Seth Madore
Owner, Liberty Machine, Inc.
Good. Fast. Cheap. Pick two.
Fusion