<p>I purchased two DQ542MA drivers in order to run two NEMA 17 steppers. After about five days of use I noticed that the green indicator light had gone out on both drivers. </p>

<p>The DQ542MA driver running my NEMA 23 High Torque stepper was still running and it has been connected to that stepper for five months now. Using an Ohm meter to check I found that the <a href="https://www.mouser.com/ProductDetail/Littelfuse/0451010MRL?qs=sGAEpiMZZMtxU2g%2F1juGqdRmCQF0%252bT4VCAcmqQZMjh4%3D" rel="nofollow noreferrer">10amp 125v</a> LittleFuse connected to the power pins had blown on both drivers connected to the NEMA 17 steppers cutting off the power. </p>

<p>I decided to test the still working driver by disconnecting it from the NEMA 23 stepper and corresponding pins on the motherboard and connecting and resetting it to work with one of the NEMA 17 steppers. The minute I turned my printer back on, the still working stepper (now attached to the NEMA 17 stepper) immediately blew the same fuse. I don't understand why the NEMA 17 steppers blew the fuses of the drivers, seeing as how both are properly set to a RMS of 1.69 and a pulse/rev of 400, and both are connected to a 24v PSU. </p>

<p><strong>My question is:</strong> "When I fix the drivers should I solder in a <a href="https://www.mouser.com/ProductDetail/Littelfuse/0476015MRSN?qs=sGAEpiMZZMtxU2g%2F1juGqTi%252bNtKN7qu4p8sgPytjpHvp9IQs9yJn3A%3D%3D" rel="nofollow noreferrer">15amp 125v</a> LittleFuse to better help the power flow and prevent any further blown fuses?"</p>

[{'answer_id': 6222, 'author': '0scar', 'author_id': 5740, 'author_profile': 'https://3dprinting.stackexchange.com/users/5740', 'pm_score': 2, 'selected': False, 'text': '<p>There are a lot of problems with the CH340 chipset drivers to be found on 3D SE and various forums on the internet. To use this cheap CH340 chip that is used by a number of Arduino compatible (clone) boards to provide USB connectivity (a USB bus converter chip that converts USB bus signals to serial interface) you need to install a correct working driver. </p>\n\n<p>For Mac OS X you can try to download a working version for the OS system you are using. You can try to use <a href="https://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/" rel="nofollow noreferrer">this driver installer</a> or <a href="https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver" rel="nofollow noreferrer">this driver installer</a>. Both reported to work with Mac OS.</p>\n\n<hr>\n\n<p><strong>Edit</strong>: If you are using OSX El Capitan, please read <a href="https://www.kiwi-electronics.nl/blog?journal_blog_post_id=7&amp;lang=en" rel="nofollow noreferrer">this</a>. To  get the CH340 drivers to work you need to use the tool <strong>csrutil</strong>.</p>\n\n<blockquote>\n  <ul>\n  <li>Reboot and press CMD+R immediately after hearing the startup sound to boot to Recovery Mode</li>\n  <li>Open Terminal</li>\n  <li>Execute the following command: <code>csrutil enable --without kext</code></li>\n  <li>Reboot</li>\n  </ul>\n</blockquote>\n\n<p>More information is found <a href="https://tzapu.com/making-ch340-ch341-serial-adapters-work-under-el-capitan-os-x/" rel="nofollow noreferrer">here</a>!</p>\n'}, {'answer_id': 6227, 'author': 'Greenonline', 'author_id': 4762, 'author_profile': 'https://3dprinting.stackexchange.com/users/4762', 'pm_score': 2, 'selected': False, 'text': '<p><em>You are using OSX El Capitan. The version of OSX is <strong>particularly</strong> relevant w.r.t. the CH340 drivers. A driver that works on one OSX version, <strong>will not necessarily work</strong> with a different version of OSX - even minor version changes of OSX can be affected (as the answers to <a href="https://arduino.stackexchange.com/questions/19059/problem-with-serial-driver-for-ch340g-board">Problem with serial driver for CH340G board</a> demonstrate.</em></p>\n\n<hr>\n\n<h3>Important Note</h3>\n\n<p>Before installing <em>any</em> new drivers, it is always worth backing up the original file, just to avoid any unpleasantness later. For example:</p>\n\n<pre><code>sudo mv /System/Library/Extensions/usb.kext /System/Library/Extensions/usb.kext.old\n</code></pre>\n\n<hr>\n\n<p>I seem to remember having the same issue, not with a 3D printer, but just with a cloned Arduino board. I thought that I had written a lengthy blog about it but can\'t locate it at the moment (I will update this answer when I find it)<sup>1</sup>. </p>\n\n<p>The CH34x ICs are infamous for their poor support on OSX. On Windows they generally fare a little better, and TBH it is probably well worth considering a WinTel option just to save yourself time, frustration and headaches...</p>\n\n<p>Nevertheless, I think that I found this site to be useful, <a href="https://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html" rel="nofollow noreferrer">How To Use Cheap Chinese Arduinos That Come With With CH340G / CH341G Serial/USB Chip (Windows &amp; Mac OS-X)</a>.</p>\n\n<p>See also <a href="https://arduino.stackexchange.com/questions/71/compatibility-between-arduino-and-arduino-clones/13414#13414">Compatibility between Arduino and Arduino clones</a>:</p>\n\n<blockquote>\n  <p>The most annoying issue, and even then it is quite minor, is that a lot of Chinese clones do not use an ATMega for the USB and instead use a CH340G. These chips, while fine when connecting to a PC running Windows 7, have great difficulties with the drivers on OS X, and end up just not being recognised. It is possible <a href="https://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html" rel="nofollow noreferrer">to find a driver for the CH340G</a>, but when I installed it, it immediately crashed the MacBook, upon plugging in the cloned UNO..!</p>\n</blockquote>\n\n<p>This advice also proved to be invaluable, from <a href="https://forum.arduino.cc/index.php?topic=198539.msg2151505#msg2151505" rel="nofollow noreferrer">Post #47 - Arduino in OS X 10.9 Mavericks - Serial Port Issues</a></p>\n\n<blockquote>\n  <p>For any others who haven\'t been able to solve this one yet: if, like\n  me, you decided to go with the cheaper chinese kick off arduino clone\n  boards and had problems similar to this one, please check the\n  following forum post, as it solved the problem for me:</p>\n  \n  <p><a href="http://forum.arduino.cc/index.php?topic=289518.0" rel="nofollow noreferrer">http://forum.arduino.cc/index.php?topic=289518.0</a></p>\n  \n  <p>And another blog site that explains the whole process really simply\n  for noobs like me:</p>\n  \n  <p><a href="http://kiguino.moos.io/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html" rel="nofollow noreferrer">http://kiguino.moos.io/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html</a></p>\n  \n  <p>Actually the dude has even mirrored the relevant driver that solves\n  the problem without having to find it on an all chinese or all russian\n  website!</p>\n</blockquote>\n\n<hr>\n\n<p>Finally, I have just had a problem with an Arduino Nano and my Mac (running Mountain Lion). Using this link, <a href="https://medium.com/@thuc/connect-arduino-nano-with-mac-osx-f922a46c0a5d" rel="nofollow noreferrer">Connect Arduino Nano with Mac OSX</a>:</p>\n\n<blockquote>\n  <ol>\n  <li>Download the driver from <a href="https://github.com/ledongthuc/example/blob/master/file/CH34x_Install_V1.3.zip" rel="nofollow noreferrer">url</a>: link</li>\n  <li>Extract and install file <code>CH34x_Install.pkg</code></li>\n  <li>Run the command: <code>sudo nvram boot-args="kext-dev-mode=1"</code></li>\n  <li>Restart the Mac.</li>\n  <li>Replace the text <code>-P{serial.port}</code> to <code>"-P{serial.port}"</code> in 2 files:\n  <code>/Applications/Arduino.app/Contents/Java/hardware/arduino/avr/platform.txt</code> (1 instance)\n  <code>/Applications/Arduino.app/Contents/Java/hardware/arduino/avr/programmers.txt</code> (4 instances)</li>\n  </ol>\n</blockquote>\n\n<p>However, this did not work for me, but I am running OS X 10.8.5 and the driver is meant for 10.9 (according to the <code>ReadMe.pdf</code>). My <code>/System/Library/Extensions/usb.kext</code> file remained unchanged (i.e. the date did not change), so maybe the installer will not work for 10.8.5.</p>\n\n<p>I tried the second of 0scar\'s suggestions, but this didn\'t work for me either (on <strong>Mountain Lion</strong>): <a href="https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver" rel="nofollow noreferrer">adrianmihalko/CH340G CH34G CH34X Mac OS X driver</a> - The <code>usb.kext</code> file was never installed in <code>/System/Library/Extensions/</code> by either the 1.3 or 1.4 versions. </p>\n\n<p>The first of 0scar\'s links, <a href="https://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/" rel="nofollow noreferrer">Signed Mac OS Driver for Winchiphead CH340 serial bridge</a>, interestingly pointed out that, <em>after</em> installation (and the associated reboot), one may have to copy the <code>usbserial.ktext</code> file manaually to /System/Library/Extensions/`. So after locating the installed file I did the following:</p>\n\n<pre><code>sudo mv /Library/Extensions/usbserial.kext /System/Library/Extensions/usb.kext\n</code></pre>\n\n<p>and then rebooted once again.</p>\n\n<p>Note the change of the filename - this may or may not be necessary. Either way, when I used both <code>usbserial.kext</code> and <code>usb.kext</code>, <em>yet again</em>, this did not help me on Mountain Lion. However, the documents do state that this particular driver is for 10.9 (Mavericks) through to 10.13 (High Sierra).</p>\n\n<p><a href="https://arduino.stackexchange.com/questions/53139/uploading-to-a-ch340-nano-board-using-a-mac-with-osx-high-sierra#answer-53611">The answer</a> to this question, <a href="https://arduino.stackexchange.com/questions/53139/uploading-to-a-ch340-nano-board-using-a-mac-with-osx-high-sierra">Uploading to a CH340 “Nano” board using a Mac with Osx High Sierra</a>, may help you on <strong>OSX High Sierra</strong>.</p>\n\n<p>It might be worth trawling through this list of questions on the Arduino.SE site: <a href="https://arduino.stackexchange.com/search?q=osx%20nano"><code>osx nano</code></a>, such as this one <a href="https://arduino.stackexchange.com/questions/3700/rename-device-name-ch340-usb-to-serial-mac-os/13344">Rename device name (ch340 usb to serial) Mac OS</a>.</p>\n\n<hr>\n\n<h3>Additional note</h3>\n\n<p>Another pitfall is that some drivers may be named <code>CH341xx.xxx</code>, but they may work for both the CH340 <em>and</em> the CH340... then again, they may not. The docs don\'t always say whether they will or not work for both ICs.</p>\n\n<hr>\n\n<h3>Footnotes</h3>\n\n<p><sup>1</sup> I think it might be this <a href="https://forum.arduino.cc/index.php?topic=198539.msg2151553#msg2151553" rel="nofollow noreferrer">Re: Arduino in OS X 10.9 Mavericks - Serial Port Issues</a>:</p>\n\n<blockquote>\n  <p>Yes, I have been struggling for a month or so, and finally realised\n  (after reading\n  <a href="http://forum.arduino.cc/index.php?topic=198539.15#msg1720630" rel="nofollow noreferrer">http://forum.arduino.cc/index.php?topic=198539.15#msg1720630</a>) that\n  other chips were being used, in lieu of the FTDI chip, for example the\n  Prolific 2305. After inspecting the board with a magnifying glass, I\n  saw that I did not have an FTDI chip in my Chinese clones of an Uno\n  and a Mega, but a CH340G instead. </p>\n  \n  <p>Once I realised that I found the <a href="http://wch.cn/product/CH340.html" rel="nofollow noreferrer">http://wch.cn/product/CH340.html</a>\n  site, but the Mac driver doesn\'t appear to be there. After a bit more\n  googling I found <a href="http://kiguino.moos.io/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html" rel="nofollow noreferrer">the kiguino site</a>. I downloaded the mirrored driver,\n  rebooted the mac, and when I connected the Uno, my MacBook died and\n  restarted with the grey serious error screen and refused to boot.\n  After disconnecting the Uno, the Mac rebooted as normal, so no lasting\n  damage done, but I am a bit wary of trying to plug the clone in again.</p>\n  \n  <p>Anyway, note that the chip says CH340 on it, but the drivers are\n  CH341. I assume that they are compatible.</p>\n</blockquote>\n'}, {'answer_id': 7794, 'author': 'Programming Maniac', 'author_id': 13974, 'author_profile': 'https://3dprinting.stackexchange.com/users/13974', 'pm_score': -1, 'selected': False, 'text': '<p>What Cura version do you have?\nCura only works with the Anet A8 via USB on versions 2.3 and lower according to this <a href="https://www.thingiverse.com/groups/anet-a8-prusa-i3/forums/general/topic:12212" rel="nofollow noreferrer">page</a>. The page is from thingiverse(A 3d printing forum + print files page)</p>\n'}, {'answer_id': 16583, 'author': 'Sevasuslik', 'author_id': 29022, 'author_profile': 'https://3dprinting.stackexchange.com/users/29022', 'pm_score': 2, 'selected': False, 'text': '<p>The problem is not in drivers! In the file located at Ultimate Cura -&gt; Contents/Resources/USBPrinting/AutoDetectBaudJob.py in line 74 in the if statement you should replace <code>and</code> with <code>or</code>:</p>\n<pre><code>if b&quot;ok&quot; in line or b&quot;T:&quot; in line: # or instead of and\n</code></pre>\n'}]
['https://3dprinting.stackexchange.com/questions/6233', 'https://3dprinting.stackexchange.com', 'https://3dprinting.stackexchange.com/users/9861/']