<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[SoliForum - 3D Printing Community — Manually setting temperature messes up display time]]></title>
		<link>https://www.soliforum.com/topic/17076/manually-setting-temperature-messes-up-display-time/</link>
		<atom:link href="https://www.soliforum.com/feed/rss/topic/17076/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Manually setting temperature messes up display time.]]></description>
		<lastBuildDate>Fri, 26 Jan 2018 16:21:15 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Manually setting temperature messes up display time]]></title>
			<link>https://www.soliforum.com/post/142007/#p142007</link>
			<description><![CDATA[<p>Sadly not. I&#039;ve since discovered Threedubber sets filament length to 1 when it encrypts, and that&#039;s causing my issue. Unfortunately I don&#039;t know enough to change the source code.</p>]]></description>
			<author><![CDATA[null@example.com (Magic Matt)]]></author>
			<pubDate>Fri, 26 Jan 2018 16:21:15 +0000</pubDate>
			<guid>https://www.soliforum.com/post/142007/#p142007</guid>
		</item>
		<item>
			<title><![CDATA[Re: Manually setting temperature messes up display time]]></title>
			<link>https://www.soliforum.com/post/141989/#p141989</link>
			<description><![CDATA[<p>try delete one of them and see if that fix the problem.</p>]]></description>
			<author><![CDATA[null@example.com (yizhou.he)]]></author>
			<pubDate>Thu, 25 Jan 2018 20:15:06 +0000</pubDate>
			<guid>https://www.soliforum.com/post/141989/#p141989</guid>
		</item>
		<item>
			<title><![CDATA[Re: Manually setting temperature messes up display time]]></title>
			<link>https://www.soliforum.com/post/141984/#p141984</link>
			<description><![CDATA[<p>Ahhhh... when I&#039;m decoding it, there&#039;s two print times in the file... I guess that&#039;s a bug in this version of Threedubber?</p>]]></description>
			<author><![CDATA[null@example.com (Magic Matt)]]></author>
			<pubDate>Thu, 25 Jan 2018 18:58:02 +0000</pubDate>
			<guid>https://www.soliforum.com/post/141984/#p141984</guid>
		</item>
		<item>
			<title><![CDATA[Re: Manually setting temperature messes up display time]]></title>
			<link>https://www.soliforum.com/post/141964/#p141964</link>
			<description><![CDATA[<p>The estimated print time is in the front of the gcode. (x will be numbers in your file.) <br />&#039; Print time= xxx<br />&#039; total-filament= xxx<br />&#039; extruder filament=xxx</p><p>Check the gcode before and after Threedubber conversion to see if Threedubber carry over the information correctly.</p>]]></description>
			<author><![CDATA[null@example.com (yizhou.he)]]></author>
			<pubDate>Thu, 25 Jan 2018 00:08:43 +0000</pubDate>
			<guid>https://www.soliforum.com/post/141964/#p141964</guid>
		</item>
		<item>
			<title><![CDATA[Manually setting temperature messes up display time]]></title>
			<link>https://www.soliforum.com/post/141963/#p141963</link>
			<description><![CDATA[<p>I don&#039;t understand why this happens, or more impo tortantly, how to prevent it...</p><p>I&#039;m printing filament at 230C in my Da Vinci Junior 1.0, by decoding the 3w file to gcode, changing the commands to set nozzle temperature, then converting back into 3w. I&#039;m using a Windows version of Threedubber to encode and decode.</p><p>This works, except the printer them shows the job as a 1 minute job, and after that minute, says 100% done, even though it happily carries on printing, even if it&#039;s a 10 hour print.</p><p>Is there something I should be doing to prevent this happening on the display? I know I could make a note of the time needed for the print as displayed on the software, and put it on a note next to the printer, but I&#039;d rather have a correct display.</p>]]></description>
			<author><![CDATA[null@example.com (Magic Matt)]]></author>
			<pubDate>Wed, 24 Jan 2018 23:22:34 +0000</pubDate>
			<guid>https://www.soliforum.com/post/141963/#p141963</guid>
		</item>
	</channel>
</rss>
