<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>F. L. I. G. (Posts about dinky)</title><link>https://www.flig.org/</link><description></description><atom:link href="https://www.flig.org/categories/dinky.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 &lt;a href="mailto:n.tesla@example.com"&gt;flig.org&lt;/a&gt; </copyright><lastBuildDate>Sun, 07 Jul 2024 14:12:05 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Arm Design</title><link>https://www.flig.org/posts/2022/05/dinky-arm-design/</link><dc:creator>Pal Denes</dc:creator><description>&lt;div&gt;&lt;p&gt;&lt;img alt="Back to the Drawing Board" src="https://www.flig.org/images/cards/back-to-the-drawing-board.png" style="width: 200px; float: right; margin-left: 20px; margin-top: 0px;"&gt;&lt;/p&gt;
&lt;p&gt;At the start of this project, I decided to build a robot arm with a “classic”, articulated design: a rotating base, with “shoulder”, “elbow” and “wrist” joints. I wanted to make something that’s suitable for picking apples, but not specific to this task, something that could maybe even used or developed further in the future for other applications.&lt;/p&gt;
&lt;p&gt;To be able to reach any point in any orientation of the end effector (or gripper), we need seven degrees of freedom: this means seven servos for joints + one more for operating the gripper. We don’t necessarily need that to be useful though. If we’re happy with limited orientations, we can get away with less.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.flig.org/posts/2022/05/dinky-arm-design/"&gt;Read more…&lt;/a&gt; (8 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>arm</category><category>dinky</category><category>robot</category><guid>https://www.flig.org/posts/2022/05/dinky-arm-design/</guid><pubDate>Wed, 25 May 2022 11:00:00 GMT</pubDate></item><item><title>Why ROS?</title><link>https://www.flig.org/posts/2022/04/why-ros/</link><dc:creator>Pal Denes</dc:creator><description>&lt;div&gt;&lt;p&gt;&lt;img alt="Write Software" src="https://www.flig.org/images/cards/write-software.png" style="width: 200px; float: left; margin-right: 20px; margin-top: 0px;"&gt;&lt;/p&gt;
&lt;p&gt;If your day job title is some variation of “developer” (maybe as opposed to “programmer”!), chances are that you spend more time on figuring out how to use various libraries and frameworks and how to “glue” things together, rather than creating a lot of novel code from scratch or inventing things. Doing Pi Wars can be an escape from all this, with complete freedom to experiment – which also means that reinventing the wheel is perfectly fine! But the opposite can also be true: figuring out what existing building blocks you need and how to fit them together efficiently to achieve a goal can be an interesting puzzle in itself. And creating from scratch “yet another” variant of everything that’s been done by others before can also feel wasteful after a while.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.flig.org/posts/2022/04/why-ros/"&gt;Read more…&lt;/a&gt; (6 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>dinky</category><category>robot</category><category>ROS</category><category>software</category><guid>https://www.flig.org/posts/2022/04/why-ros/</guid><pubDate>Sat, 30 Apr 2022 11:00:00 GMT</pubDate></item><item><title>Servos for Dinky</title><link>https://www.flig.org/posts/2022/02/servos-for-dinky/</link><dc:creator>Pal Denes</dc:creator><description>&lt;div&gt;&lt;p&gt;&lt;img alt="Build a Prototype" src="https://www.flig.org/images/cards/build-a-prototype.png" style="width: 200px; float: left; margin-right: 20px; margin-top: 0px;"&gt;&lt;/p&gt;
&lt;p&gt;Until now, I’ve only had some experience with simple hobby servos (the cheaper the better, I thought, never bothering with much research or trying to pick specific types/brands or looking at parameters like torque – just tried to use whatever I could get, hoping for the best). Hobby servos are of course well understood and work reasonably well for robots, but their control method is a bit crude (no position feedback) and not very accurate.&lt;/p&gt;
&lt;p&gt;When looking around for various robot arm projects for inspiration, I frequently came across the &lt;a href="http://www.dynamixel.com/whatisdxl.php"&gt;Dynamixel&lt;/a&gt; servos from Robotis and was intrigued, wanting to try something “serious” this time.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.flig.org/posts/2022/02/servos-for-dinky/"&gt;Read more…&lt;/a&gt; (12 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>dinky</category><category>half-duplex</category><category>robot</category><category>servos</category><guid>https://www.flig.org/posts/2022/02/servos-for-dinky/</guid><pubDate>Sat, 05 Feb 2022 12:00:00 GMT</pubDate></item><item><title>Finding Apples with OpenCV</title><link>https://www.flig.org/posts/2021/12/see-apples/</link><dc:creator>Pal Denes</dc:creator><description>&lt;div&gt;&lt;p&gt;&lt;img alt="Solve Challenge" src="https://www.flig.org/images/cards/solve-challenge.png" style="width: 200px; float: left; margin-right: 20px; margin-top: 0px;"&gt;&lt;/p&gt;
&lt;p&gt;When I first started to think about the Nature’s Bounty challenge, I decided to try and find a way to automatically detect apples using a camera and OpenCV. My thinking was roughly:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Apples are of a known size and colour (and there is nothing else around that’s round or red).&lt;/li&gt;
&lt;li&gt;Apple detection should be relatively generic, in the sense that we shouldn’t rely too much on knowledge about their expected positions on the tree.&lt;/li&gt;
&lt;li&gt;We’re only detecting apples, not tree branches (so apples are just “floating” in space, and we can grab them freely – but we might try to do this “cautiously”, expecting some invisible branches might be in the way).&lt;/li&gt;
&lt;li&gt;Apple detection should be as simple and efficient as possible (better to refine readings continuously as we get closer than to try something “perfect” that might be too slow or resource-hungry).&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="https://www.flig.org/posts/2021/12/see-apples/"&gt;Read more…&lt;/a&gt; (8 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>apples</category><category>camera</category><category>dinky</category><category>OpenCV</category><category>robot</category><guid>https://www.flig.org/posts/2021/12/see-apples/</guid><pubDate>Fri, 31 Dec 2021 12:00:00 GMT</pubDate></item></channel></rss>