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