<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>Tajima DG by Pulse Community - DG16 Bug Reports - DG16  Stop Command issue - Messages</title>
<link>https://dgcommunity.pulsemicro.com/topic496-dg--stop-command-issue.aspx</link>
<description>Tajima DG by Pulse Community - DG16 Bug Reports - DG16  Stop Command issue - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<generator>Jitbit AspNetForum</generator>
<pubDate>Sat, 19 Apr 2025 02:17:47 GMT</pubDate>
<lastBuildDate>Sat, 19 Apr 2025 02:17:47 GMT</lastBuildDate>
<item>
<link>https://dgcommunity.pulsemicro.com/topic496-dg--stop-command-issue.aspx</link>
<title>Message from TheFinishingTouch</title>
<description><![CDATA[I believe I may be experiencing something similar with the STOP command.  When I digitize a design and want it to stop (say for example I'm putting solvy on the portion of the design already sewn), the TEHX's I have do not stop.  They change thread color, make ONE STITCH, and then change to the next color and proceed sewing (which throws the colors off, since the machine was supposed to stop while I did something) and then, sew the segment that only got one stitch. Am I doing something wrong in my digitizing? Is a setting on all my TEHX's wrong? I have DG16.5.3.7660 Maestro.<br/><i>edited by TheFinishingTouch on 4/19/2025</i>]]></description>
<pubDate>Sat, 19 Apr 2025 02:17:47 GMT</pubDate>
</item>
<item>
<link>https://dgcommunity.pulsemicro.com/topic496-dg--stop-command-issue.aspx</link>
<title>Message from Tajima Software</title>
<description><![CDATA[Thank you both for bringing this issue to our attention. <br/>We have been able to solve this internally and a fix for this problem will be included in the next DG16 maintenance release.]]></description>
<pubDate>Thu, 24 Jan 2019 16:15:55 GMT</pubDate>
</item>
<item>
<link>https://dgcommunity.pulsemicro.com/topic496-dg--stop-command-issue.aspx</link>
<title>Message from hlgearheart</title>
<description><![CDATA[From Hirsch Support <br/><br/>Unfortunately, the stop code is being put there by DG16, we are aware of this issue and have taken the necessary steps to alert Pulse. <br/><br/>Pulse has let us know that they are working to resolve this issue.<br/><i>edited by hlgearheart on 1/19/2019</i>]]></description>
<pubDate>Sat, 19 Jan 2019 17:03:43 GMT</pubDate>
</item>
<item>
<link>https://dgcommunity.pulsemicro.com/topic496-dg--stop-command-issue.aspx</link>
<title>Message from hlgearheart</title>
<description><![CDATA[<b>Chameleon</b> wrote:<br/><blockquote>Has anyone experienced DG16 composer putting in a stop command when sending any design to a Tajima TFMX? There is no stop command in the design itself, and it worked fine with DG15</blockquote><br/><br/>Yes same thing for me. Always after the first color. If I import it to the machine and DO NOT read the condition and there is not another file on the screen it doesn't. Haven't found a setting in Composer yet to stop it from doing it. And my TFMX-IIC1504 will not let me delete the stop via the thread selection screen.<br/><i>edited by hlgearheart on 1/17/2019</i>]]></description>
<pubDate>Thu, 17 Jan 2019 18:11:39 GMT</pubDate>
</item>
<item>
<link>https://dgcommunity.pulsemicro.com/topic496-dg--stop-command-issue.aspx</link>
<title>Message from Chameleon</title>
<description><![CDATA[Has anyone experienced DG16 composer putting in a stop command when sending any design to a Tajima TFMX? There is no stop command in the design itself, and it worked fine with DG15]]></description>
<pubDate>Thu, 17 Jan 2019 16:31:53 GMT</pubDate>
</item>
</channel>
</rss>
