<?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[AIN4-20ma Raspberry Pi Detection]]></title><description><![CDATA[<p dir="auto">I am trying connect the AIN4-20 current sensor to the raspberry pi and communicate directly with i2c. i2cdetect fails to find the device (I've tried both the single channel unit and the 4 channel stack). I've enabled and tried the built in ARM i2c (bus 1), and also the software i2c (bus 3). Other i2c devices show up on these busses, just not the m5 products. Should these be detected, or are they not compatible without a M5 host? I have a raspberry pi project that uses another company's industrial i2c current receivers, but they are 12-bit units, and was hoping to easily upgrade to m5 units.</p>
]]></description><link>https://community.m5stack.com/topic/7444/ain4-20ma-raspberry-pi-detection</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 17:14:56 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/7444.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 26 Mar 2025 18:10:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Mon, 15 Dec 2025 22:24:55 GMT]]></title><description><![CDATA[<p dir="auto">Dear @Steve-Mack <a class="plugin-mentions-user plugin-mentions-a" href="/user/andrew.winton" aria-label="Profile: andrew.winton">@<bdi>andrew.winton</bdi></a>,<br />
Did you solve the problem? I have the same issue with a Raspberry PI Zero W (no detection with "i2cdetect -y 1"). As I have 2 AIN4-20ma and 2 raspberry PI Zero W, I tried to exchange them but it is never detected. Other I2C devices are working well.<br />
Thanks,<br />
Seb</p>
]]></description><link>https://community.m5stack.com/post/30315</link><guid isPermaLink="true">https://community.m5stack.com/post/30315</guid><dc:creator><![CDATA[sebastien.lecomte]]></dc:creator><pubDate>Mon, 15 Dec 2025 22:24:55 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 04 Dec 2025 13:20:05 GMT]]></title><description><![CDATA[<p dir="auto">@andrew-winton<br />
Hi, did you ever solve this problem?<br />
Thanks</p>
]]></description><link>https://community.m5stack.com/post/30275</link><guid isPermaLink="true">https://community.m5stack.com/post/30275</guid><dc:creator><![CDATA[Steve.Mack]]></dc:creator><pubDate>Thu, 04 Dec 2025 13:20:05 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Tue, 01 Apr 2025 18:41:27 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/robski" aria-label="Profile: robski">@<bdi>robski</bdi></a> Yeah I had seen that behavior with it jumping to the right address and then crawling after not finding it.</p>
]]></description><link>https://community.m5stack.com/post/28754</link><guid isPermaLink="true">https://community.m5stack.com/post/28754</guid><dc:creator><![CDATA[andrew.winton]]></dc:creator><pubDate>Tue, 01 Apr 2025 18:41:27 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Mon, 31 Mar 2025 18:21:34 GMT]]></title><description><![CDATA[<p dir="auto">@andrew-winton tday I had a chance to test AIN with raspberry pico 2 W and it is detetcting ok</p>
<p dir="auto"><img src="/assets/uploads/files/1743445263676-ain_0.png" alt="RaspberryPico2W with AIN" class=" img-fluid img-markdown" /></p>
]]></description><link>https://community.m5stack.com/post/28727</link><guid isPermaLink="true">https://community.m5stack.com/post/28727</guid><dc:creator><![CDATA[robski]]></dc:creator><pubDate>Mon, 31 Mar 2025 18:21:34 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Sat, 29 Mar 2025 08:29:30 GMT]]></title><description><![CDATA[<p dir="auto">@andrew-winton I've checked my AIN module with RPi4 and i can confirm that it is not detecting it, plugged in ENV module, ACCEL module, ultrasound module and i2c scan detects it straight in, when AIN is plugged in scan goes fast to place where it should be detected ( 0x55 i think) and then without its  ID detection scan continues but slowly like 1s for every next ID field till the scan end</p>
]]></description><link>https://community.m5stack.com/post/28707</link><guid isPermaLink="true">https://community.m5stack.com/post/28707</guid><dc:creator><![CDATA[robski]]></dc:creator><pubDate>Sat, 29 Mar 2025 08:29:30 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Fri, 28 Mar 2025 12:20:12 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> RP has the pull-ups by default. Although these are brand new wires, I've tried different ones. I've also tried it with and without the power to the stack. I've also tried speeds of 50k, 100k, and 400k, which have all worked for other i2c devices on the Pi.</p>
]]></description><link>https://community.m5stack.com/post/28702</link><guid isPermaLink="true">https://community.m5stack.com/post/28702</guid><dc:creator><![CDATA[andrew.winton]]></dc:creator><pubDate>Fri, 28 Mar 2025 12:20:12 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Fri, 28 Mar 2025 10:12:58 GMT]]></title><description><![CDATA[<p dir="auto">I'm bk home tday for weekend and I have AIN single chnl unit so I'll try to check it out.</p>
]]></description><link>https://community.m5stack.com/post/28699</link><guid isPermaLink="true">https://community.m5stack.com/post/28699</guid><dc:creator><![CDATA[robski]]></dc:creator><pubDate>Fri, 28 Mar 2025 10:12:58 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Fri, 28 Mar 2025 09:52:05 GMT]]></title><description><![CDATA[<p dir="auto">Hello @andrew-winton</p>
<p dir="auto">I don't have a RP4 nor do I have the AIN4-20mA module so my tests might be irrelevant for your setup.</p>
<p dir="auto">Using an RP3 and about every M5Stack I2C unit I have (RFID, Relay4, PaHub, PbHub, EXTIO, etc.), all of them get detected just fine using <code>i2cdetect -y 1</code>.</p>
<p dir="auto">That said:</p>
<ul>
<li>have you verified that there are proper pull-up resistors on SCL and SDA? (RP should have them by default.)</li>
<li>have you tried with different wires?</li>
<li>have you tried w/o supplying 12 v? I think it's redundant looking at the schematic. (External 12 V power also produces BUS_5V which might clash with the 5 V from RP.)</li>
<li>have you tried to reduce the I2C speed? (default seems to be 100k)</li>
</ul>
<p dir="auto">Thanks<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/28698</link><guid isPermaLink="true">https://community.m5stack.com/post/28698</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Fri, 28 Mar 2025 09:52:05 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 14:45:27 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/robski" aria-label="Profile: robski">@<bdi>robski</bdi></a> I do not. I was considering getting a core and base to make sure it worked with those first to rule out the device.</p>
]]></description><link>https://community.m5stack.com/post/28692</link><guid isPermaLink="true">https://community.m5stack.com/post/28692</guid><dc:creator><![CDATA[andrew.winton]]></dc:creator><pubDate>Thu, 27 Mar 2025 14:45:27 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 14:43:53 GMT]]></title><description><![CDATA[<p dir="auto">@andrew-winton do you have any other M5Stack unit on i2c to be checked possibly, not AIN unit I mean.</p>
]]></description><link>https://community.m5stack.com/post/28691</link><guid isPermaLink="true">https://community.m5stack.com/post/28691</guid><dc:creator><![CDATA[robski]]></dc:creator><pubDate>Thu, 27 Mar 2025 14:43:53 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 14:35:42 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/robski" aria-label="Profile: robski">@<bdi>robski</bdi></a> Yes, the single channel unit was behaving the exact same way.</p>
]]></description><link>https://community.m5stack.com/post/28690</link><guid isPermaLink="true">https://community.m5stack.com/post/28690</guid><dc:creator><![CDATA[andrew.winton]]></dc:creator><pubDate>Thu, 27 Mar 2025 14:35:42 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 14:23:25 GMT]]></title><description><![CDATA[<p dir="auto">so you have M5base here not sure about that as there is M-bus in it.<br />
But you also mentioned single channel unit was behiving same right?</p>
]]></description><link>https://community.m5stack.com/post/28689</link><guid isPermaLink="true">https://community.m5stack.com/post/28689</guid><dc:creator><![CDATA[robski]]></dc:creator><pubDate>Thu, 27 Mar 2025 14:23:25 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 14:20:34 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/robski" aria-label="Profile: robski">@<bdi>robski</bdi></a> <img src="/assets/uploads/files/1743084532968-pxl_20250327_140552083.mp.jpg" alt="PXL_20250327_140552083.MP.jpg" class=" img-fluid img-markdown" /> <img src="/assets/uploads/files/1743084533088-pxl_20250327_140606609.mp.jpg" alt="PXL_20250327_140606609.MP.jpg" class=" img-fluid img-markdown" /></p>
<p dir="auto">I was hoping there wasn't something unique about the I2C on these, so I'm glad you confirmed that, however it's still confusing why I can't even detect it. Here it is with the stack module hooked up <a href="https://docs.m5stack.com/en/module/AIN4-20mA%20Module%2013.2" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/module/AIN4-20mA%20Module%2013.2</a>. When I have SDA and SCL disconnected, an i2cdetect immediately returns no results. When I hook them up, i2cdetect crawls through each address until they time out. I've double checked the pinouts, and made sure I'm supplying 12v (also tried 24v) to the 9-24V high voltage plug, and that it's getting 5v from the Pi.</p>
<p dir="auto">Yellow - 5v<br />
Brown - Ground<br />
Orange - SDA<br />
Red - SCL</p>
]]></description><link>https://community.m5stack.com/post/28688</link><guid isPermaLink="true">https://community.m5stack.com/post/28688</guid><dc:creator><![CDATA[andrew.winton]]></dc:creator><pubDate>Thu, 27 Mar 2025 14:20:34 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 13:39:22 GMT]]></title><description><![CDATA[<p dir="auto">AIN needs 5v in to its Vcc pin, then i2c is on 3.3V same as Rpi, there is nothing special in it like only M5Stack compatibility its just a sensor on i2c at the end</p>
]]></description><link>https://community.m5stack.com/post/28687</link><guid isPermaLink="true">https://community.m5stack.com/post/28687</guid><dc:creator><![CDATA[robski]]></dc:creator><pubDate>Thu, 27 Mar 2025 13:39:22 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 13:15:14 GMT]]></title><description><![CDATA[<p dir="auto">@andrew-winton did you connect the sensor +5V to the +5V and GND to GND of the RPi? Are you sure not having crossed the clock/data pins? I speak from experience... spent more than one hour for a simple failure like this.<br />
When powering on the 5V can you measure if the 3.3V inside the sensor is correct?</p>
]]></description><link>https://community.m5stack.com/post/28686</link><guid isPermaLink="true">https://community.m5stack.com/post/28686</guid><dc:creator><![CDATA[holofloh]]></dc:creator><pubDate>Thu, 27 Mar 2025 13:15:14 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 12:07:55 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/holofloh" aria-label="Profile: holofloh">@<bdi>holofloh</bdi></a> Thanks for the reply. I'm using a raspberry pi 4 with 5v that draws directly from it's own power supply <a href="https://pinout.xyz/pinout/i2c" target="_blank" rel="noopener noreferrer nofollow ugc">https://pinout.xyz/pinout/i2c</a>. I tried hooking up to an external 5v power supply and it still doesn't detect either the unit or the module.</p>
]]></description><link>https://community.m5stack.com/post/28684</link><guid isPermaLink="true">https://community.m5stack.com/post/28684</guid><dc:creator><![CDATA[andrew.winton]]></dc:creator><pubDate>Thu, 27 Mar 2025 12:07:55 GMT</pubDate></item><item><title><![CDATA[Reply to AIN4-20ma Raspberry Pi Detection on Thu, 27 Mar 2025 06:49:25 GMT]]></title><description><![CDATA[<p dir="auto">I guess this is a voltage level issue on the power supply for the sensor. M5 Groove Ports use 5V, RPi use 3.3V. Internally the AIN4-20mA use 3.3V (there is a voltage regulator between Groove port and the converter, see the schematic on <a href="https://docs.m5stack.com/en/unit/AIN4-20mA%20Unit" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/unit/AIN4-20mA Unit</a>) and 5V for the OP-Amp. You may supply the unit with 5V.</p>
]]></description><link>https://community.m5stack.com/post/28678</link><guid isPermaLink="true">https://community.m5stack.com/post/28678</guid><dc:creator><![CDATA[holofloh]]></dc:creator><pubDate>Thu, 27 Mar 2025 06:49:25 GMT</pubDate></item></channel></rss>