public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tuxic@posteo.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] [OT] Extracting printer settings from a gcode file?
Date: Tue, 31 Oct 2017 01:54:12 +0100	[thread overview]
Message-ID: <20171031005412.xha4udbxnyqu5qh4@solfire> (raw)

Hi,

currently I am starting with 3D-printing.  I have watched a lot of videos of
how to create models, do bed leveling, (bad leveling, sometimes ;) choose
filaments, and what else...

Say one use a 3D-printer, which uses the a SDcard to read the gcode files.
Beside some basic settings (hot end temprature, bed temperature, filament feed
speed...I think that's it) all informations about the print process are in the
gcode file. There is no other way of feeding informations to the printer as the
gcode on that certain SDcard.

And slicer settings optimzed for a certain printer are seemingly one of the
treasures hunted a lot...

The printer I ordered (and which still hasn't arrived yet ...) comes with some
example gcode files. I would guess that the manufacturer has trimmed the slicer
settings he has used for these example files, are optimized to give the best
results with this printer -- its kind of an advertising.

Would be nice, if it could be possible to extract them from the gcode example
files in a way, that made it possible to feed them back into the slicer
software manually (not expecting to get a config file ready to be read directly
with that certain slicer software I want to use...) 

And as one has already feared...the question:    ;)
How can I do this?   

Cheers 
Meino

PS: I know qcode is an ASCII format...but understanding the codes to extract the
slicer settings is a totally different kind of task... ;)




             reply	other threads:[~2017-10-31  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31  0:54 tuxic [this message]
2017-11-01  1:15 ` [gentoo-user] [OT] Extracting printer settings from a gcode file? Adam Carter
2017-11-01  1:24   ` tuxic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171031005412.xha4udbxnyqu5qh4@solfire \
    --to=tuxic@posteo.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox