Able to generate s3g file in batch from a gcode file?

[Richard K]

I have created something to print on my makerbot and generated the
gcode file (took awhile). But, after generating the gcode file,
ReplicatorG was unresponsive, with Java hogging over 200+mb of memory
(on both WinXP SP3 and Windows 7 64 bit OS). Only difference between
the two systems was the speed at generating the file. The process did
output a file, and the resulting gcode is about 34mb, give or take,
which is too big to post. The stl file is 57K.

As such, have looked around and am unable to find the necessary
command to launch the s3g generation from the command line. Doing a
search of the file contents it seemed like this piece of the puzzle is
embedded in the java portion of ReplicatorG.

Believe the item is a little oversized to print on the makerbot, but
am willing to try just for the sheer "joy" of reaching a maximum
height. Am going to make this a little smaller, but it is a part for
a post, so the fewer I can print the happier I am..

Any thoughts/ideas?

Looking at the replicatorG section on github, did see something in
there, slated for release 19.

If anyone wants to try this I can past the stl file in here so
everyone can copy/paste.

[Fido]

I don't know about the .s3g file but if you'll upload the .stl file
here, we can take a look at it and see what might be wrong with it.

[Richard K]

Have uploaded the files to google docs.. Will need the following URL
to access it:
https://docs.google.com/leaf?id=0B3Q7ZmfM9jW-Y2Y5NTk1ZGYtNjZjZC00YzY1LWExMTctNTA1Nzc2ODJkNGU2&hl=en&authkey=COfwx_kG

Couldn't figure out how to upload to the files section (maybe my brain
isn't working today yet).

Have included 3 files, the original one (porch_post), a smaller
version but still unable to generate the s3g file (porch_post_small)
and a version which was finally able to generate a build file
(porch_post_mini).

Be forewarned, it will take a long while to generate if doing the
gcode.

Thanks for taking a peek!

[Fido]

Yeah uploading files in these threads is kind of odd process and out
of norm but that method you used worked equally well.

Took a look on the porch_post.stl and everything seemed ok.
Process to .gcode took about 29min with fill value of 0.2 resulting
file size about 4mb.
Second process run with fill value of 0.05 took about 20min and file
size of 2.5mb.
The print time was said to be about 15h and 10h. ( I have slowed down
some travel moves on my bot so with norm settings this part could be
completed quicker.)

If your skeingforge still takes over hours to process and gives really
large .gcode files, I think you might have some values out of tune.
Have you tried the skeingforge 0007 with default settings? I haven't
changed mine that much so you might get better results from that.


Janne

On 8 elo, 17:45, Richard K <kutch2...@gmail.com> wrote:
> Have uploaded the files to google docs..  Will need the following URL

> to access it:https://docs.google.com/leaf?id=0B3Q7ZmfM9jW-Y2Y5NTk1ZGYtNjZjZC00YzY1...

[Richard K]

Haven't done much other than fine tuning my printer settings and can
print smaller version almost fine, except for some warping on edges,
which am working on.. :) Glad you could get it do generate so
something on my end for sure.

The fill value I have is:
Infill Solidity (ratio): 0.23

Also not sure what this is:
Interior Infill Density over Exterior Density (ratio): 0.9

Have uploaded my current settings/preferences for ReplicatorG in a zip
file:
https://docs.google.com/leaf?id=0B3Q7ZmfM9jW-ZjA5YzgxMTAtMmJmYS00YjgxLWE4YjktZTVlNmMxZmJiYzIz&hl=en&authkey=CL2n55MG

Thanks! Will play around a little.