<?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[I2C issues on the TAB5]]></title><description><![CDATA[<p dir="auto">Hi,<br />
I'm trying to handle some stepper motors using the "stepmotor driver module V1.1" on the UIflow 2.3.8 IDE.<br />
I'm connecting the module to the M-Bus at the back of the TAB5, but the TAB5 won't recognize it and won't show it on the I2C list using the default scanner that comes with the official TAB5 UIflow2 firmware.<br />
It does recognize an 8Servo unit when connected to the I2C Port.A at the side of the TAB5.<br />
I've tried also connecting a 4in8out module on the TAB5 M-Bus, but it is not recognized as well.<br />
The 2 modules (stepmotoer driver and 4in8out ) <strong>do</strong> work when connected to a Core2 M-Bus, so these units are OK.<br />
It's either my TAB5 arrived faulty, or there is an issue with the I2C on the M-Bus of the TAB5, at least when using UIFlow2 IDE.<br />
Any suggestions?</p>
]]></description><link>https://community.m5stack.com/topic/7912/i2c-issues-on-the-tab5</link><generator>RSS for Node</generator><lastBuildDate>Tue, 28 Apr 2026 20:59:54 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/7912.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 26 Nov 2025 14:51:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to I2C issues on the TAB5 on Tue, 02 Dec 2025 12:49:36 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/br123456" aria-label="Profile: BR123456">@<bdi>BR123456</bdi></a><br />
Problem solved. See:<br />
<a href="https://community.m5stack.com/post/30264">https://community.m5stack.com/post/30264</a></p>
]]></description><link>https://community.m5stack.com/post/30267</link><guid isPermaLink="true">https://community.m5stack.com/post/30267</guid><dc:creator><![CDATA[BR123456]]></dc:creator><pubDate>Tue, 02 Dec 2025 12:49:36 GMT</pubDate></item><item><title><![CDATA[Reply to I2C issues on the TAB5 on Sun, 30 Nov 2025 08:42:32 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/felmue" aria-label="Profile: felmue">@<bdi>felmue</bdi></a> Hi Felix,<br />
I will try your suggestion, thanks!</p>
<p dir="auto">Boaz</p>
]]></description><link>https://community.m5stack.com/post/30254</link><guid isPermaLink="true">https://community.m5stack.com/post/30254</guid><dc:creator><![CDATA[BR123456]]></dc:creator><pubDate>Sun, 30 Nov 2025 08:42:32 GMT</pubDate></item><item><title><![CDATA[Reply to I2C issues on the TAB5 on Wed, 26 Nov 2025 16:53:57 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/br123456" aria-label="Profile: BR123456">@<bdi>BR123456</bdi></a></p>
<p dir="auto">it looks like the internal scan in UIFlow 2.3.8 default scanner is broken - I do not get any results either.</p>
<p dir="auto">However if I scan the internal bus via I2C blocks it picks up all internal I2C addresses and what's connected to the M-Bus. The example is called <em>M5Tab5_I2C_Scan_Test_UIFlow2.3.8</em> and you can find it in the UIFlow2 Project Zone.</p>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/30240</link><guid isPermaLink="true">https://community.m5stack.com/post/30240</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Wed, 26 Nov 2025 16:53:57 GMT</pubDate></item></channel></rss>