<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>[Pi IoT] Alarm Clock #11: Clock Display</title><link>/challenges-projects/design-challenges/pi-iot/b/blog/posts/pi-iot-alarm-clock-11-clock-display</link><description>Enabling I2C 


 Connecting Hardware 

 3.3V vs 5V ? 



 Python Library 


 7-Segment Display 


 8x8 LED Matrix 


 Demo 

 This post will be about the display of the actual alarm clock. It will consist of two components, visualising different information</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: [Pi IoT] Alarm Clock #11: Clock Display</title><link>https://community.element14.com/challenges-projects/design-challenges/pi-iot/b/blog/posts/pi-iot-alarm-clock-11-clock-display</link><pubDate>Sat, 30 Jul 2016 18:15:59 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:7e252006-c27a-431d-8a09-4e66f86fe01a</guid><dc:creator>balearicdynamics</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Great post. It includes a good quick-start guide to manage I2C.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thank you!&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Enrico&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=1754&amp;AppID=138&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: [Pi IoT] Alarm Clock #11: Clock Display</title><link>https://community.element14.com/challenges-projects/design-challenges/pi-iot/b/blog/posts/pi-iot-alarm-clock-11-clock-display</link><pubDate>Sat, 30 Jul 2016 18:12:39 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:7e252006-c27a-431d-8a09-4e66f86fe01a</guid><dc:creator>DAB</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Very nice detailed post.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;DAB&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=1754&amp;AppID=138&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: [Pi IoT] Alarm Clock #11: Clock Display</title><link>https://community.element14.com/challenges-projects/design-challenges/pi-iot/b/blog/posts/pi-iot-alarm-clock-11-clock-display</link><pubDate>Sat, 30 Jul 2016 00:01:15 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:7e252006-c27a-431d-8a09-4e66f86fe01a</guid><dc:creator>mcb1</dc:creator><slash:comments>1</slash:comments><description>&lt;blockquote class="jive-quote"&gt;&lt;p&gt;power the displays using 5V instead of 3.3V and not damage my Pi&amp;#39;s I2C pins&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;I had the same issue with a wireless receiver using the 3v3 RFM69 devices and an I2C LCD display.&lt;/p&gt;&lt;p&gt;Luckily the I2C is pulled up on the sender end, hence it remained at 3v3 ...&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Very useful post.&lt;/p&gt;&lt;p&gt;Cheers&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=1754&amp;AppID=138&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>