<?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[2-relay vs 4-relay]]></title><description><![CDATA[<p dir="auto">Why is the program interface to the 2-relay and 4-relay modules different? Given that they do the same thing, having incompatible interfaces seems like a really bad idea.</p>
]]></description><link>https://community.m5stack.com/topic/5013/2-relay-vs-4-relay</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 14:08:37 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/5013.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 27 Jan 2023 15:53:35 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to 2-relay vs 4-relay on Sun, 29 Jan 2023 18:15:02 GMT]]></title><description><![CDATA[<p dir="auto">Ahh sorry, misread.</p>
]]></description><link>https://community.m5stack.com/post/19965</link><guid isPermaLink="true">https://community.m5stack.com/post/19965</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Sun, 29 Jan 2023 18:15:02 GMT</pubDate></item><item><title><![CDATA[Reply to 2-relay vs 4-relay on Sun, 29 Jan 2023 22:31:05 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ajb2k3" aria-label="Profile: ajb2k3">@<bdi>ajb2k3</bdi></a>  You are talking about the 2Relay-UNIT ... with the black (analog/digital) grove port !!<br />
The M5Stack MODULE 13.2 we are talking about ( <a href="https://shop.m5stack.com/products/2-relay-13-2-module" target="_blank" rel="noopener noreferrer nofollow ugc">https://shop.m5stack.com/products/2-relay-13-2-module</a>) has a STM32F030 controller acting as an I2C interface controlling the 2 relais : The I2C address according to their documentation is 0x25 (mentioned in the features section) or 0x26 (according to their arduino or blockly section). The firmware is +/- the same as with the 4Relay module and the 4Relay Unit (<a href="https://shop.m5stack.com/products/4-relay-unit" target="_blank" rel="noopener noreferrer nofollow ugc">https://shop.m5stack.com/products/4-relay-unit</a> with the red I2C grove port, I2C address 0x26).</p>
]]></description><link>https://community.m5stack.com/post/19961</link><guid isPermaLink="true">https://community.m5stack.com/post/19961</guid><dc:creator><![CDATA[crami25]]></dc:creator><pubDate>Sun, 29 Jan 2023 22:31:05 GMT</pubDate></item><item><title><![CDATA[Reply to 2-relay vs 4-relay on Sun, 29 Jan 2023 09:08:27 GMT]]></title><description><![CDATA[<p dir="auto">The 2Relay is directly driven by the two GPIO's in the grove port.<br />
The 4Relay can not be driven in the same way as the grove port has only two GPIO wires and so a controller is needed to handle the multiple relays.</p>
]]></description><link>https://community.m5stack.com/post/19958</link><guid isPermaLink="true">https://community.m5stack.com/post/19958</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Sun, 29 Jan 2023 09:08:27 GMT</pubDate></item><item><title><![CDATA[Reply to 2-relay vs 4-relay on Fri, 27 Jan 2023 17:02:12 GMT]]></title><description><![CDATA[<p dir="auto">M5Stack have messed up with their xRelay modules and units. They are all adressed by I2C, but all require different commands depending on the firmware they have used, So using the  proposed uiflow blocks won't work, you have to use the I2C blocks (See my forum post for the 4-relay module).</p>
<p dir="auto">For the 2-relay module the documents tell you that the I2C-Address is 0x26 (as for the 4-Relay Module). In the uiflow demo they are talking about address 0x25 ?? writing to control register 0xFF you can probaly change the I2C address of the module.<br />
So you have to try out  which commands work for you ...</p>
]]></description><link>https://community.m5stack.com/post/19944</link><guid isPermaLink="true">https://community.m5stack.com/post/19944</guid><dc:creator><![CDATA[crami25]]></dc:creator><pubDate>Fri, 27 Jan 2023 17:02:12 GMT</pubDate></item></channel></rss>