<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
           xmlns:content="http://purl.org/rss/1.0/modules/content/"
           xmlns:wfw="http://wellformedweb.org/CommentAPI/"
          >
<channel>
<title><![CDATA[iFixit - Answers With Device &quot;Epson_ET-3750&quot;]]></title>
<link>https://www.ifixit.com/Answers/Device/Epson_ET-3750?rss=yes</link>
<description><![CDATA[Top Questions according to your query. Only showing &quot;Epson_ET-3750&quot; questions.]]></description>
<language>en-US</language>
<pubDate>Sun, 26 Apr 2026 22:52:43 -0700</pubDate>
<item>
<title><![CDATA[Epson ET-3750: Epson ET-3750 no ink output after replacing fuse F301 and printhead.]]></title>
<description><![CDATA[<p>The print head shorted out during use of a print head cleaning kit, blew main board fuse F301, and threw the 031006 error code. One of the traces of the print head ribbon cable burnt off the silver colored finish and revealed copper color.</p>

<p>Replaced F301 and print head, ensured ink flow to and through the regulators, and re-assembled everything. Printer powered up and all functions work, no errors, but no ink of any color comes out, even after multiple print checks, cleanings, and printing test pages.</p>

<p>If it is a bad, non-conducting cable trace, I would expect it to throw an error, but it does not. Before I take it apart again to continuity check from mainboard connector to end of ribbon cable trace, has anyone out there seen something similar or have any thoughts other than the obvious possible faulty mainboard, cable, and print head? E.g., why no error(s), all other functions work, etc.? Why no ink of any color? If the 'burnt' trace is common to all colors, e.g., ground or power to print head, why doesn't the mainboard detect a non-powered / non-functioning print head?</p>]]></description>
<link>https://www.ifixit.com/Answers/View/940185/Epson+ET-3750+no+ink+output+after+replacing+fuse+F301+and+printhead.</link>
<guid isPermaLink="false" >https://www.ifixit.com/Answers/View/940185</guid>
<pubDate>Wed, 11 Feb 2026 00:35:48 -0700</pubDate>
</item>
</channel>
</rss>