<?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>ACE - Blog #2 - Building the wearable</title><link>/challenges-projects/design-challenges/design-for-a-cause-2021/b/blog/posts/ace---blog-2---building-the-wearable</link><description>When designing the wearable device, we need to make some functional decisions, namelywhere to wear the devicehow to power the device (how many batteries? with which capacity?)how to keep costs down Let&amp;#39; start from the most important topic: where...</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: ACE - Blog #2 - Building the wearable</title><link>https://community.element14.com/challenges-projects/design-challenges/design-for-a-cause-2021/b/blog/posts/ace---blog-2---building-the-wearable</link><pubDate>Sun, 23 May 2021 15:38:52 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:9821fd0a-b652-4f2f-af63-00cd62ce516a</guid><dc:creator>jduchniewicz</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;A side note, the code for setting the sleep duration may overflow for bigger values (1 second or more) - it will result in the duration equal to the overflowed value (obviously wrong), or even worse - &lt;strong&gt;a totally random value&lt;/strong&gt; &lt;strong&gt;(Undefined Behavior)&lt;/strong&gt;. So it would be better to replace the multiplication like this (taken from your GitHub):&lt;/p&gt;&lt;p&gt;[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:3ef06e6b-9b7d-4651-b12d-db8be7f5e991:type=xhtml&amp;amp;text=uint32_t+preset+%3D+%28micros+*+10%29+%2F+305%3B%0A++preset+%3D+preset+%2F+1000%3B]&lt;/p&gt;&lt;div&gt;&lt;/div&gt;&lt;p&gt;And even better it would be to split the computation into the upper and lower part. &lt;strong&gt;Overflows are nasty!&lt;/strong&gt;&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=11082&amp;AppID=279&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: ACE - Blog #2 - Building the wearable</title><link>https://community.element14.com/challenges-projects/design-challenges/design-for-a-cause-2021/b/blog/posts/ace---blog-2---building-the-wearable</link><pubDate>Fri, 07 May 2021 17:22:07 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:9821fd0a-b652-4f2f-af63-00cd62ce516a</guid><dc:creator>jduchniewicz</dc:creator><slash:comments>2</slash:comments><description>&lt;p&gt;Hi, I like how you interact with the clocks on per-register basis! &lt;br /&gt;I plan to use the batteries in my solution as well, is the peak 3.7V of the battery not too much for direct powering of the Arduino Nano 33 IoT? I am afraid to repeat my MCU burning mistakes &lt;span&gt;[View:/resized-image/__size/16x16/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-9821fd0a-b652-4f2f-af63-00cd62ce516a/contentimage_5F00_1.png:16:16]&lt;/span&gt;&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=11082&amp;AppID=279&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: ACE - Blog #2 - Building the wearable</title><link>https://community.element14.com/challenges-projects/design-challenges/design-for-a-cause-2021/b/blog/posts/ace---blog-2---building-the-wearable</link><pubDate>Sun, 02 May 2021 18:02:47 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:9821fd0a-b652-4f2f-af63-00cd62ce516a</guid><dc:creator>DAB</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;Good start.&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=11082&amp;AppID=279&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>