]> pere.pagekite.me Git - homepage.git/blob - blog/tags/robot/robot.rss
810b46f1809a1397971b588566413a45159933ef
[homepage.git] / blog / tags / robot / robot.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged robot</title>
5 <description>Entries tagged robot</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>My own self balancing Lego Segway</title>
11 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
13 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
14 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
15 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
16 present. It had been on my wishlist for a while, because I wanted to
17 build a Segway like balancing lego robot. I had already built
18 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
19 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
20 NXT kit as the balance sensor, but it was not working very well. It
21 could balance for a while, but was very sensitive to the light
22 condition in the room and the reflective properties of the surface and
23 would fall over after a short while. I wanted something more robust,
24 and had
25 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
26 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
27 wishlist for some years before it suddenly showed up as a gift from my
28 loved ones. :)&lt;/p&gt;
29
30 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
31 since then. But that changed some days ago, when I was searching for
32 lego segway information and came across a recipe from HiTechnic for
33 building
34 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
35 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
36 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
37 code&lt;/a&gt; was included, so it was just a question of putting it all
38 together. And thanks to the great work of many Debian developers, the
39 compiler needed to build the source for the NXT is already included in
40 Debian, so I was read to go in less than an hour. The resulting robot
41 do not look very impressive in its simplicity:&lt;/p&gt;
42
43 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-robot.jpeg&quot;&gt;&lt;/p&gt;
44
45 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
46 design from HiTechnic, I had to comment out the last task
47 (taskControl). I simply placed /* and */ around it get the program
48 working without that sensor present. Now it balances just fine until
49 the battery status run low:&lt;/p&gt;
50
51 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
52 &lt;source src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-balancing.ogv&quot; type=&quot;video/ogg&quot;&gt;
53 &lt;/video&gt;&lt;/p&gt;
54
55 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
56 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
57
58 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
59 they need to work with LEGO in Debian and all our derivative
60 distributions like Ubuntu, check out
61 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
62 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
63 RCX and NXT controller (no EV3), and would like to make sure the
64 Debian tools needed to program the systems I own work as they
65 should.&lt;/p&gt;
66 </description>
67 </item>
68
69 <item>
70 <title>All drones should be radio marked with what they do and who they belong to</title>
71 <link>http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html</link>
72 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html</guid>
73 <pubDate>Thu, 21 Nov 2013 15:40:00 +0100</pubDate>
74 <description>&lt;p&gt;Drones, flying robots, are getting more and more popular. The most
75 know ones are the killer drones used by some government to murder
76 people they do not like without giving them the chance of a fair
77 trial, but the technology have many good uses too, from mapping and
78 forest maintenance to photography and search and rescue. I am sure it
79 is just a question of time before &quot;bad drones&quot; are in the hands of
80 private enterprises and not only state criminals but petty criminals
81 too. The drone technology is very useful and very dangerous. To have
82 some control over the use of drones, I agree with Daniel Suarez in his
83 TED talk
84 &quot;&lt;a href=&quot;https://archive.org/details/DanielSuarez_2013G&quot;&gt;The kill
85 decision shouldn&#39;t belong to a robot&lt;/a&gt;&quot;, where he suggested this
86 little gem to keep the good while limiting the bad use of drones:&lt;/p&gt;
87
88 &lt;blockquote&gt;
89
90 &lt;p&gt;Each robot and drone should have a cryptographically signed
91 I.D. burned in at the factory that can be used to track its movement
92 through public spaces. We have license plates on cars, tail numbers on
93 aircraft. This is no different. And every citizen should be able to
94 download an app that shows the population of drones and autonomous
95 vehicles moving through public spaces around them, both right now and
96 historically. And civic leaders should deploy sensors and civic drones
97 to detect rogue drones, and instead of sending killer drones of their
98 own up to shoot them down, they should notify humans to their
99 presence. And in certain very high-security areas, perhaps civic
100 drones would snare them and drag them off to a bomb disposal facility.&lt;/p&gt;
101
102 &lt;p&gt;But notice, this is more an immune system than a weapons system. It
103 would allow us to avail ourselves of the use of autonomous vehicles
104 and drones while still preserving our open, civil society.&lt;/p&gt;
105
106 &lt;/blockquote&gt;
107
108 &lt;p&gt;The key is that &lt;em&gt;every citizen&lt;/em&gt; should be able to read the
109 radio beacons sent from the drones in the area, to be able to check
110 both the government and others use of drones. For such control to be
111 effective, everyone must be able to do it. What should such beacon
112 contain? At least formal owner, purpose, contact information and GPS
113 location. Probably also the origin and target position of the current
114 flight. And perhaps some registration number to be able to look up
115 the drone in a central database tracking their movement. Robots
116 should not have privacy. It is people who need privacy.&lt;/p&gt;
117 </description>
118 </item>
119
120 <item>
121 <title>Perl library to control the Spykee robot moved to github</title>
122 <link>http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html</link>
123 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html</guid>
124 <pubDate>Sat, 19 Oct 2013 10:20:00 +0200</pubDate>
125 <description>&lt;p&gt;Back in 2010, I created a Perl library to talk to
126 &lt;a href=&quot;http://en.wikipedia.org/wiki/Spykee&quot;&gt;the Spykee robot&lt;/a&gt;
127 (with two belts, wifi, USB and Linux) and made it available from my
128 web page. Today I concluded that it should move to a site that is
129 easier to use to cooperate with others, and moved it to github. If
130 you got a Spykee robot, you might want to check out
131 &lt;a href=&quot;https://github.com/petterreinholdtsen/libspykee-perl&quot;&gt;the
132 libspykee-perl github repository&lt;/a&gt;.&lt;/p&gt;
133 </description>
134 </item>
135
136 <item>
137 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
138 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
139 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
140 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
141 <description>&lt;P&gt;In January,
142 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
143 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
144 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
145 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
146 marvellous construction system from Denmark. We also created
147 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
148 a place to take notes and write down our plans and hopes. And several
149 people showed up to help. I was very happy to see the effect of my
150 call. Since the small start, we have a debtags tag
151 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
152 tag for LEGO related packages, and now count 10 packages related to
153 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
154
155 &lt;p&gt;&lt;table&gt;
156 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/brickos&quot;&gt;brickos&lt;/a&gt;&lt;/td&gt;&lt;td&gt;alternative OS for LEGO Mindstorms RCX. Supports development in C/C++&lt;/td&gt;&lt;/tr&gt;
157 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/leocad&quot;&gt;leocad&lt;/a&gt;&lt;/td&gt;&lt;td&gt;virtual brick CAD software&lt;/td&gt;&lt;/tr&gt;
158 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/libnxt&quot;&gt;libnxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;utility library for talking to the LEGO Mindstorms NX&lt;/td&gt;&lt;/tr&gt;
159 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/lnpd&quot;&gt;lnpd&lt;/a&gt;&lt;/td&gt;&lt;td&gt;daemon for LNP communication with BrickOS&lt;/td&gt;&lt;/tr&gt;
160 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nbc&quot;&gt;nbc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;compiler for LEGO Mindstorms NXT bricks&lt;/td&gt;&lt;/tr&gt;
161 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nqc&quot;&gt;nqc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Not Quite C compiler for LEGO Mindstorms RCX&lt;/td&gt;&lt;/tr&gt;
162 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt&quot;&gt;python-nxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;python driver/interface/wrapper for the Lego Mindstorms NXT robot&lt;/td&gt;&lt;/tr&gt;
163 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt-filer&quot;&gt;python-nxt-filer&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple GUI to manage files on a LEGO Mindstorms NXT&lt;/td&gt;&lt;/tr&gt;
164 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/scratch&quot;&gt;scratch&lt;/a&gt;&lt;/td&gt;&lt;td&gt;easy to use programming environment for ages 8 and up&lt;/td&gt;&lt;/tr&gt;
165 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/t2n&quot;&gt;t2n&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple command-line tool for Lego NXT&lt;/td&gt;&lt;/tr&gt;
166 &lt;/table&gt;&lt;/p&gt;
167
168 &lt;p&gt;Some of these are available in Wheezy, and all but one are
169 currently available in Jessie/testing. leocad is so far only
170 available in experimental.&lt;/p&gt;
171
172 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
173 adding the rest of the great free software tools available on Linux
174 for LEGO designers.&lt;/p&gt;
175 </description>
176 </item>
177
178 <item>
179 <title>Moved the pymissile Debian packaging to collab-maint</title>
180 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
181 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
182 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
183 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
184 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
185 Launcher and updated the Debian package
186 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
187 sure udev will fix the device permissions when it is plugged in. I
188 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
189 hopefully make the package be proposed by jockey in Ubuntu when a user
190 plug in his rocket launcher. In the process I moved the source to a
191 git repository under collab-maint, to make it easier for any DD to
192 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
193 is not very active, but the software still work for me even after five
194 years of relative silence. The new git repository is not listed in
195 the uploaded package yet, because I want to test the other changes a
196 bit more before I upload the new version. If you want to check out
197 the new version with a .desktop file included, visit the
198 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
199 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
200 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
201 </description>
202 </item>
203
204 <item>
205 <title>New IRC channel for LEGO designers using Debian</title>
206 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
207 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
208 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
209 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
210 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
211 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
212 discovered I had to build all the tools myself because none were
213 already in Debian Squeeze. If Debian support for LEGO is something
214 you care about, please join me on the IRC channel
215 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
216 irc.debian.org). There is a lot that could be done to improve the
217 Debian support for LEGO designers. For example both CAD software
218 and Mindstorm compilers are missing. :)&lt;/p&gt;
219
220 &lt;p&gt;Update 2012-01-03: A
221 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
222 including links to Lego related packages is now available.&lt;/p&gt;
223 </description>
224 </item>
225
226 <item>
227 <title>First version of a Perl library to control the Spykee robot</title>
228 <link>http://people.skolelinux.org/pere/blog/First_version_of_a_Perl_library_to_control_the_Spykee_robot.html</link>
229 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_version_of_a_Perl_library_to_control_the_Spykee_robot.html</guid>
230 <pubDate>Sat, 9 Oct 2010 14:00:00 +0200</pubDate>
231 <description>&lt;p&gt;This summer I got the chance to buy cheap Spykee robots, and since
232 then I have worked on getting Linux software in place to control them.
233 The firmware for the robot is available from the producer, and using
234 that source it was trivial to figure out the protocol specification.
235 I&#39;ve started on a perl library to control it, and made some demo
236 programs using this perl library to allow one to control the
237 robots.&lt;/p&gt;
238
239 &lt;p&gt;The library is quite functional already, and capable of controlling
240 the driving, fetching video, uploading MP3s and play them. There are
241 a few less important features too.&lt;/p&gt;
242
243 &lt;p&gt;Since a few weeks ago, I ran out of time to spend on this project,
244 but I never got around to releasing the current source. I decided
245 today that it was time to do something about it, and uploaded the
246 source to my Debian package store at people.skolelinux.org.&lt;/p&gt;
247
248 &lt;p&gt;Because it was simpler for me, I made a Debian package and
249 published the source and deb. If you got a spykee robot, grab the
250 source or binary package:&lt;/p&gt;
251
252 &lt;p&gt;&lt;ul&gt;
253 &lt;li&gt;&lt;a href=&quot;http://people.skolelinux.org/~pere/debian/packages/lenny/libspykee-perl_0.0.20101009-1.tar.gz&quot;&gt;libspykee-perl_0.0.20101009-1.tar.gz&lt;/a&gt;&lt;/li&gt;
254 &lt;li&gt;&lt;a href=&quot;http://people.skolelinux.org/~pere/debian/packages/lenny/libspykee-perl_0.0.20101009-1.dsc&quot;&gt;libspykee-perl_0.0.20101009-1.dsc&lt;/a&gt;&lt;/li&gt;
255 &lt;li&gt;&lt;a href=&quot;http://people.skolelinux.org/~pere/debian/packages/lenny/libspykee-perl_0.0.20101009-1_all.deb&quot;&gt;libspykee-perl_0.0.20101009-1_all.deb&lt;/a&gt;&lt;/li&gt;
256 &lt;/ul&gt;&lt;/p&gt;
257
258 &lt;p&gt;If you are interested in helping out with developing this library,
259 please let me know.&lt;/p&gt;
260 </description>
261 </item>
262
263 <item>
264 <title>My first perl GUI application - controlling a Spykee robot</title>
265 <link>http://people.skolelinux.org/pere/blog/My_first_perl_GUI_application___controlling_a_Spykee_robot.html</link>
266 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/My_first_perl_GUI_application___controlling_a_Spykee_robot.html</guid>
267 <pubDate>Wed, 1 Sep 2010 21:00:00 +0200</pubDate>
268 <description>&lt;p&gt;This evening I made my first Perl GUI application. The last few
269 days I have worked on a Perl module for controlling my recently
270 aquired Spykee robots, and the module is now getting complete enought
271 that it is possible to use it to control the robot driving at least.
272 It was now time to figure out how to use it to create some GUI to
273 allow me to drive the robot around. I picked PerlQt as I have had
274 positive experiences with the Qt API before, and spent a few minutes
275 browsing the web for examples. Using Qt Designer seemed like a short
276 cut, so I ended up writing the perl GUI using Qt Designer and
277 compiling it into a perl program using the puic program from
278 libqt-perl. Nothing fancy yet, but it got buttons to connect and
279 drive around.&lt;/p&gt;
280
281 &lt;p&gt;The perl module I have written provide a object oriented API for
282 controlling the robot. Here is an small example on how to use it:&lt;/p&gt;
283
284 &lt;p&gt;&lt;pre&gt;
285 use Spykee;
286 Spykee::discover(sub {$robot{$_[0]} = $_[1]});
287 my $host = (keys %robot)[0];
288 my $spykee = Spykee-&gt;new();
289 $spykee-&gt;contact($host, &quot;admin&quot;, &quot;admin&quot;);
290 $spykee-&gt;left();
291 sleep 2;
292 $spykee-&gt;right();
293 sleep 2;
294 $spykee-&gt;forward();
295 sleep 2;
296 $spykee-&gt;back();
297 sleep 2;
298 $spykee-&gt;stop();
299 &lt;/pre&gt;&lt;/p&gt;
300
301 &lt;p&gt;Thanks to the release of the source of the robot firmware, I could
302 peek into the implementation at the other end to figure out how to
303 implement the protocol used by the robot. I&#39;ve implemented several of
304 the commands the robot understand, but is still missing the camera
305 support to make it possible to control the robot from remote. First I
306 want to implement support for uploading new firmware and configuring
307 the wireless network, to make it possible to bootstrap a Spykee robot
308 without the producers Windows and MacOSX software (I only have Linux,
309 so I had to ask a friend to come over to get the robot testing
310 going. :).&lt;/p&gt;
311
312 &lt;p&gt;Will release the source to the public soon, but need to figure out
313 where to make it available first. I will add a link to
314 &lt;a href=&quot;http://wiki.nuug.no/grupper/robot/&quot;&gt;the NUUG wiki&lt;/a&gt; for
315 those that want to check back later to find it.&lt;/p&gt;
316 </description>
317 </item>
318
319 <item>
320 <title>Robot, reis deg...</title>
321 <link>http://people.skolelinux.org/pere/blog/Robot__reis_deg___.html</link>
322 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Robot__reis_deg___.html</guid>
323 <pubDate>Sat, 21 Aug 2010 22:10:00 +0200</pubDate>
324 <description>&lt;p&gt;I dag fikk jeg endelig tittet litt på mine nyinnkjøpte roboter, og
325 har brukt noen timer til å google etter interessante referanser og
326 aktuell kildekode for bruk på Linux. Det mest lovende så langt er
327 &lt;a href=&quot;http://ispykee.toyz.org/&quot;&gt;ispykee&lt;/a&gt;, som har en
328 BSD-lisensiert linux-daemon som står som mellomledd mellom roboter på
329 lokalnettet og en sentral tjeneste der en iPhone kan koble seg opp for
330 å fjernstyre roboten. Linux-daemonen implementerer deler av
331 protokollen som roboten forstår. Etter å ha knotet litt med å oppnå
332 kontakt med roboten (den oppretter et eget ad-hoc wifi-nett, så jeg
333 måtte gå av mitt vanlige nett for å få kontakt), og kommet frem til at
334 den lytter på IP-port 9000 og 9001, gikk jeg i gang med å finne ut
335 hvordan jeg kunne snakke med roboten vha. disse portene. Robotbiten
336 av protokollen er publisert av produsenten med GPL-lisens, slik at det
337 er mulig å se hvordan protokollen fungerer. Det finnes en java-klient
338 for Android som så ganske snasen ut, men fant ingen kildekode for
339 denne. Derimot hadde iphone-løsningen kildekode, så jeg tok
340 utgangspunkt i den.&lt;/p&gt;
341
342 &lt;p&gt;Daemonen ville i utgangspunktet forsøke å kontakte den sentrale
343 tjenesten som iphone-programmet kobler seg til. Jeg skrev dette om
344 til i stedet å sette opp en nettverkstjeneste på min lokale maskin,
345 som jeg kan koble meg opp til med telnet og gi kommandoer til roboten
346 (act, forward, right, left, etc). Det involverte i praksis å bytte ut
347 socket()/connect() med socket()/bind()/listen()/accept() for å gjøre
348 klienten om til en tjener.&lt;/p&gt;
349
350 &lt;p&gt;Mens jeg har forsøkt å få roboten til å bevege seg har min samboer
351 skrudd sammen resten av roboten for å få montert kamera og plastpynten
352 (armer, plastfiber for lys). Nå er det hele montert, og roboten er
353 klar til bruk. Må få flyttet den over til mitt vanlige trådløsnett
354 før det blir praktisk, men de bitene av protokollen er ikke
355 implementert i ispykee-daemonen, så der må jeg enten få tak i en mac
356 eller en windows-maskin, eller implementere det selv.&lt;/p&gt;
357
358 &lt;p&gt;Vi var tre som kjøpte slike roboter, og vi har blitt enige om å
359 samle notater og referanser på &lt;a
360 href=&quot;http://wiki.nuug.no/grupper/robot/&quot;&gt;NUUGs wiki&lt;/a&gt;. Ta en titt
361 der hvis du er nysgjerrig.&lt;/p&gt;
362 </description>
363 </item>
364
365 <item>
366 <title>2 Spykee-roboter i hus, nå skal det lekes</title>
367 <link>http://people.skolelinux.org/pere/blog/2_Spykee_roboter_i_hus__n__skal_det_lekes.html</link>
368 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/2_Spykee_roboter_i_hus__n__skal_det_lekes.html</guid>
369 <pubDate>Wed, 18 Aug 2010 13:30:00 +0200</pubDate>
370 <description>&lt;p&gt;Jeg kjøpte nettopp to
371 &lt;a href=&quot;http://www.spykee-robot.com/&quot;&gt;Spykee&lt;/a&gt;-roboter, for test og
372 leking. Kjøpte to da det var så billige, og gir meg mulighet til å
373 eksperimentere uten å være veldig redd for å ødelegge alt ved å bytte
374 ut firmware og slikt. Oppdaget at lekebutikken på Bryn senter hadde
375 en liten stabel på lager som de ikke hadde klart å selge ut etter
376 fjorårets juleinnkjøp, og var villig til å selge for en femtedel av
377 vanlig pris. Jeg, Ronny og Jarle har skaffet oss restbeholdningen, og
378 det blir morsomt å se hva vi får ut av dette.&lt;/p&gt;
379
380 &lt;p&gt;Roboten har belter styrt av to motorer, kamera, høytaler, mikrofon
381 og wifi-tilkobling. Det hele styrt av en GPL-lisensiert databoks som
382 jeg mistenker kjører linux. Firmware-kildekoden ble visst publisert i
383 mai. Eneste utfordringen er at kontroller-programvaren kun finnes til
384 Windows, men det må en kunne jobbe seg rundt når vi har kildekoden til
385 firmwaren. :)&lt;/p&gt;
386
387 &lt;ul&gt;
388 &lt;li&gt;&lt;a href=&quot;http://en.wikipedia.org/wiki/Spykee&quot;&gt;Wikipedia-oppføring&lt;/a&gt;&lt;/li&gt;
389 &lt;li&gt;&lt;a href=&quot;http://www.spykeeworld.com/spykee/US/freeSoftware.html&quot;&gt;Nedlasting av firmware-kilden&lt;/a&gt;&lt;/li&gt;
390 &lt;li&gt;&lt;a href=&quot;http://wiki.nuug.no/grupper/robot&quot;&gt;prosjektwiki hos NUUG&lt;/a&gt;&lt;/li&gt;
391 &lt;/ul&gt;
392 </description>
393 </item>
394
395 </channel>
396 </rss>