<?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[need your advice for data transfer from a CORE2 to an ATOM display !]]></title><description><![CDATA[<p dir="auto">What is the simplest and fastest communication solution (Modbus, UART, CAN,...) to communicate around 20 variables from a CORE2 to an ATOM DISPLAY? the two controllers will be in the same box at 10cm.<br />
Should the data be sent as a list? do you have any examples in UIFLOW?</p>
]]></description><link>https://community.m5stack.com/topic/4653/need-your-advice-for-data-transfer-from-a-core2-to-an-atom-display</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 01:00:41 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/4653.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 27 Sep 2022 17:03:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to need your advice for data transfer from a CORE2 to an ATOM display ! on Tue, 27 Sep 2022 20:56:24 GMT]]></title><description><![CDATA[<p dir="auto">Thanks Teastain<br />
I have the expansion module for CORE 2<br />
I am looking for advice on the mode of communication to use to transfer from CORE2 to the ATOM Display, and how to transmit around 20 digital variables?</p>
]]></description><link>https://community.m5stack.com/post/18748</link><guid isPermaLink="true">https://community.m5stack.com/post/18748</guid><dc:creator><![CDATA[Arno]]></dc:creator><pubDate>Tue, 27 Sep 2022 20:56:24 GMT</pubDate></item><item><title><![CDATA[Reply to need your advice for data transfer from a CORE2 to an ATOM display ! on Tue, 27 Sep 2022 19:17:54 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/arno" aria-label="Profile: arno">@<bdi>arno</bdi></a> The built-in SPI would provide the fastest frame rate but trickier to access the SPI on the Core2, second choice is the built-in I2C interface accessible by the standard Grove port on the left side.<br />
The Core2 is bereft of GPIO as a nod to WiFi BLE I2C ESP_NOW, etc, whereas the foundational Core Basic is better equipped with I/O options!!!<br />
I think M5Stack announced recently a GPIO base to convert the Core2.<br />
I have a Core2 running a simulated nixie-tube clock and two Core Basics.<br />
<a href="https://shop.m5stack.com/collections/m5stack-new-arrival/products/extension-port-module-for-core2?variant=43165402398977" target="_blank" rel="noopener noreferrer nofollow ugc">https://shop.m5stack.com/collections/m5stack-new-arrival/products/extension-port-module-for-core2?variant=43165402398977</a></p>
<p dir="auto">Extension Port Module for Core2<br />
SKU: M123   Regular price$6.95     Out Of Stock</p>
]]></description><link>https://community.m5stack.com/post/18744</link><guid isPermaLink="true">https://community.m5stack.com/post/18744</guid><dc:creator><![CDATA[teastain]]></dc:creator><pubDate>Tue, 27 Sep 2022 19:17:54 GMT</pubDate></item></channel></rss>