Date: Sat, 19 May 2012 17:45:56 -0700 (PDT)
From: Daid <daid...@gmail.com>
To: ultimaker@googlegroups.com
Cc: Daid <daid...@gmail.com>
Message-Id: <e604d857-488b-4eae-b41d-98d73e435353@googlegroups.com>
In-Reply-To: <4FB83CD8.3080508@tjeb.nl>
References: <095a01cd35c9$627b9fa0$2772dee0$@Vinland.com> <b80b4686-f9c7-4f1b-aea8-bac9564f6570@googlegroups.com> <097101cd35dc$03e9e5b0$0bbdb110$@Vinland.com> <c1cc4248-a6b7-40e5-9407-8c7985dd89c4@googlegroups.com> <4FB7D5EF.8010203@tjeb.nl> <4e73d9f0-67d0-4b57-8d1a-93a9fb5574ff@googlegroups.com>
 <4FB83CD8.3080508@tjeb.nl>
Subject: Re: Cura comments
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1663_17471093.1337474756963"

------=_Part_1663_17471093.1337474756963
Content-Type: multipart/alternative; 
	boundary="----=_Part_1664_1826543.1337474756963"

------=_Part_1664_1826543.1337474756963
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

FYI: The 250000 baud problem on Linux is a PySerial/Kernel combination 
problem. They removed an old kernel interface to set custom baudrates, and 
replaced it with a new one. But PySerial is only using the old interface.

On Sunday, May 20, 2012 2:37:44 AM UTC+2, Jelte wrote:
>
> -----BEGIN PGP SIGNED MESSAGE----- 
> Hash: SHA1 
>
> On 05/19/2012 07:37 PM, Daid wrote: 
> > Hello cousin, 
> > 
>
> hey :) 
>
> > It kind of depends on how you print. For me the files are 
> > temporary, because I copy them to my SD card for printing. If you 
> > print from within Cura, they are sort of temporary, because you 
> > don't ever touch them. 
> > 
>
> Of course. Currently I am at still at the stage of 'oooh, i wonder 
> what this button does', and randomly modifying settings just to see 
> what type of failures they result in ;) (good job on the defaults btw! 
> Oh, except the baud rate; 250000 didn't work for my linux systems, it 
> seems the allowed rates are fixed; 230400 does appear to work fine) 
>
> As for me, I have a laptop currently dedicated to the slicing (and 
> therefore wish that it was faster) and direct control of my ulti. But 
> even if I had SD support, I probably wouldn't want to bother with 
> moving physical things around for each print. Probably related to the 
> trying-out-lots-of-stuff phase. 
>
> > As for storing the profile settings, you can automaticly store the 
> > whole profile with the preference option designed for it. And you 
> > can also edit your start code to include the tags of the important 
> > settings you want to have with your GCode file. If you add a line 
> > like this in your start code: G21 ; Layer height: {layer_height} 
> > Walls: {wall_thickness} Fill: {fill_density} Then you will have the 
> > most important settings listed in at the start of the GCode file. 
> > (The G21 needs to be in front because SF currently still eats up 
> > all lines which only have comments) For more tags, just check the 
> > contents of a profile ini, because those names match. 
> > 
>
> Right, the thing is, should every slice result in a separate file, I'd 
> want the settings to be stored in the file itself, by default, and not 
> globally. And every setting, not just the big ones (but a good order 
> would be nice). Once again, probably related to the trying out phase. 
>
> Note this is just thinking aloud, not a feature request. Still want to 
> look at the actual code, but having too much fun with the machine 
> itself right now :) 
>
> Jelte 
>
> -----BEGIN PGP SIGNATURE----- 
> Version: GnuPG v1.4.11 (GNU/Linux) 
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 
>
> iEYEARECAAYFAk+4PNcACgkQ4nZCKsdOncU5BgCeOl7DVCkbXZVt8aug14vltKss 
> 0iEAnjydoOXXmSmNahopIWcw/OBgrZoi 
> =zJle 
> -----END PGP SIGNATURE----- 
>

------=_Part_1664_1826543.1337474756963
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

FYI: The 250000 baud problem on Linux is a PySerial/Kernel combination problem. They removed an old kernel interface to set custom baudrates, and replaced it with a new one. But PySerial is only using the old interface.<br><br>On Sunday, May 20, 2012 2:37:44 AM UTC+2, Jelte wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">-----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1
<br>
<br>On 05/19/2012 07:37 PM, Daid wrote:
<br>&gt; Hello cousin,
<br>&gt; 
<br>
<br>hey :)
<br>
<br>&gt; It kind of depends on how you print. For me the files are
<br>&gt; temporary, because I copy them to my SD card for printing. If you
<br>&gt; print from within Cura, they are sort of temporary, because you
<br>&gt; don't ever touch them.
<br>&gt; 
<br>
<br>Of course. Currently I am at still at the stage of 'oooh, i wonder
<br>what this button does', and randomly modifying settings just to see
<br>what type of failures they result in ;) (good job on the defaults btw!
<br>Oh, except the baud rate; 250000 didn't work for my linux systems, it
<br>seems the allowed rates are fixed; 230400 does appear to work fine)
<br>
<br>As for me, I have a laptop currently dedicated to the slicing (and
<br>therefore wish that it was faster) and direct control of my ulti. But
<br>even if I had SD support, I probably wouldn't want to bother with
<br>moving physical things around for each print. Probably related to the
<br>trying-out-lots-of-stuff phase.
<br>
<br>&gt; As for storing the profile settings, you can automaticly store the
<br>&gt; whole profile with the preference option designed for it. And you
<br>&gt; can also edit your start code to include the tags of the important
<br>&gt; settings you want to have with your GCode file. If you add a line
<br>&gt; like this in your start code: G21 ; Layer height: {layer_height}
<br>&gt; Walls: {wall_thickness} Fill: {fill_density} Then you will have the
<br>&gt; most important settings listed in at the start of the GCode file.
<br>&gt; (The G21 needs to be in front because SF currently still eats up
<br>&gt; all lines which only have comments) For more tags, just check the
<br>&gt; contents of a profile ini, because those names match.
<br>&gt; 
<br>
<br>Right, the thing is, should every slice result in a separate file, I'd
<br>want the settings to be stored in the file itself, by default, and not
<br>globally. And every setting, not just the big ones (but a good order
<br>would be nice). Once again, probably related to the trying out phase.
<br>
<br>Note this is just thinking aloud, not a feature request. Still want to
<br>look at the actual code, but having too much fun with the machine
<br>itself right now :)
<br>
<br>Jelte
<br>
<br>-----BEGIN PGP SIGNATURE-----
<br>Version: GnuPG v1.4.11 (GNU/Linux)
<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a>
<br>
<br>iEYEARECAAYFAk+<wbr>4PNcACgkQ4nZCKsdOncU5BgCeOl7DV<wbr>CkbXZVt8aug14vltKss
<br>0iEAnjydoOXXmSmNahopIWcw/<wbr>OBgrZoi
<br>=zJle
<br>-----END PGP SIGNATURE-----
<br></blockquote>
------=_Part_1664_1826543.1337474756963--

------=_Part_1663_17471093.1337474756963--