<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[COMMU design&#x2F;scematic error]]></title><description><![CDATA[<p dir="auto">The RS485 interface design for the COMMU appears to be wrong.  As shown, the transmit data (TXD) is used to enable/disable the driver on the DE/RE pins, while the driver data input, DI is permanently strapped low.</p>
<p dir="auto">This means that sending data will drive a 'one' or float the line, but never drive a 'zero'.</p>
<p dir="auto">The correct implementation should be TXD connected to the DI pin and a third signal used to control the DE/RE pins.</p>
<p dir="auto">Since there is no third signal available, this design is fundamentally broken and won't interoperate with my existing systems.</p>
<p dir="auto">V</p>
<p dir="auto"><img src="http://community.m5stack.com/assets/uploads/files/1557829994400-4ce5a99c-28ed-4d77-bcbe-a7abdb8e1116-image.png" alt="alt text" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.m5stack.com/topic/1414/commu-design-scematic-error</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Apr 2026 06:05:53 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/1414.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 22 Oct 2019 15:54:18 GMT</pubDate><ttl>60</ttl></channel></rss>