<?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[Strange issue using 8Encoder with AtomS3 and TailBat]]></title><description><![CDATA[<p dir="auto">Hi<br />
I am brand new to the M5Stack (and hardware hacking in general) and love the potential.<br />
I have run into an issue on my first project (a custom lighting controller prototype).</p>
<p dir="auto">I have an AtomS3 connected to an 8Encoder.<br />
On direct USB power, the Atom recognizes the 8Encoder on I2C address 0x41 as expected in the spec and everything works fine.</p>
<p dir="auto">I want to make the prototype portable, so I got a TailBat to provide power on the go.<br />
The documentation says the Port.A pins are connected straight through, so everything should work the same.<br />
HOWEVER, when I connect the 8Encoder through the TailBat, the 8Encoder is no longer found on 0x41.<br />
Instead, when doing an I2C scan, I get a peripheral come up on 0x54, and my encoder is no longer recognized.  (The encoder doesn't work on 0x54.)</p>
<p dir="auto">FURTHER, on disconnecting the TailBat, the encoder CONTINUES to "register as 0x54" (or whatever is going on) for a while even when connected directly to the AtomS3.<br />
I have no idea why or how this could be possible!</p>
<p dir="auto">My only guess is that something is happening in the signal path to mess with the encoder, and it is retaining some charge that means it doesn't reset for several minutes.</p>
<p dir="auto">If someone could shed some light on it, I would be grateful!</p>
<p dir="auto">Evidence..</p>
<p dir="auto"><strong>Connected directly - works!</strong></p>
<p dir="auto"><img src="/assets/uploads/files/1700841994844-encworking.jpg" alt="0_1700841988447_encworking.jpg" class=" img-fluid img-markdown" /></p>
<p dir="auto"><strong>Connected via TailBat - doesn't work</strong></p>
<p dir="auto"><img src="/assets/uploads/files/1700841973422-encbatbroken.jpg" alt="0_1700841968241_encbatbroken.jpg" class=" img-fluid img-markdown" /></p>
<p dir="auto"><strong>Connected directly again - STILL doesn't work!!</strong></p>
<p dir="auto"><img src="/assets/uploads/files/1700841983414-encbrokennobat.jpg" alt="0_1700841976999_encbrokennobat.jpg" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.m5stack.com/topic/5847/strange-issue-using-8encoder-with-atoms3-and-tailbat</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 17:04:37 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/5847.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 24 Nov 2023 16:10:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Strange issue using 8Encoder with AtomS3 and TailBat on Sat, 25 Nov 2023 15:56:36 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/dozauk" aria-label="Profile: dozauk">@<bdi>dozauk</bdi></a> Check the pins on the tail bat, I have had the grove connector that plugged into the atom fail on one battery.</p>
]]></description><link>https://community.m5stack.com/post/22895</link><guid isPermaLink="true">https://community.m5stack.com/post/22895</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Sat, 25 Nov 2023 15:56:36 GMT</pubDate></item></channel></rss>