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>All drones should be radio marked with what they do and who they belong to
</title>
11 <link>http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html
</link>
12 <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>
13 <pubDate>Thu,
21 Nov
2013 15:
40:
00 +
0100</pubDate>
14 <description>Drones, flying robots, are getting more and more popular. The most
15 know ones are the killer drones used by some government to murder
16 people they do not like without giving them the chance of a fair
17 trial, but the technology have many good uses too, from mapping and
18 forest maintenance to photography and search and rescue. I am sure it
19 is just a question of time before
"bad drones
" are in the hands of
20 private enterprises and not only state criminals but petty criminals
21 too. The drone technology is very useful and very dangerous. To have
22 some control over the use of drones, I agree with Daniel Suarez in his
24 "<a href=
"https://archive.org/details/DanielSuarez_2013G
">The kill
25 decision shouldn
't belong to a robot
</a
>", where he suggested this
26 little gem to keep the good while limiting the bad use of drones:
</p
>
30 <p
>Each robot and drone should have a cryptographically signed
31 I.D. burned in at the factory that can be used to track its movement
32 through public spaces. We have license plates on cars, tail numbers on
33 aircraft. This is no different. And every citizen should be able to
34 download an app that shows the population of drones and autonomous
35 vehicles moving through public spaces around them, both right now and
36 historically. And civic leaders should deploy sensors and civic drones
37 to detect rogue drones, and instead of sending killer drones of their
38 own up to shoot them down, they should notify humans to their
39 presence. And in certain very high-security areas, perhaps civic
40 drones would snare them and drag them off to a bomb disposal facility.
</p
>
42 <p
>But notice, this is more an immune system than a weapons system. It
43 would allow us to avail ourselves of the use of autonomous vehicles
44 and drones while still preserving our open, civil society.
</p
>
48 <p
>The key is that
<em
>every citizen
</em
> should be able to read the
49 radio beacons sent from the drones in the area, to be able to check
50 both the government and others use of drones. For such control to be
51 effective, everyone must be able to do it. What should such beacon
52 contain? At least formal owner, purpose, contact information and GPS
53 location. Probably also the origin and target position of the current
54 flight. And perhaps some registration number to be able to look up
55 the drone in a central database tracking their movement. Robots
56 should not have privacy. It is people who need privacy.
</p
>
61 <title>Perl library to control the Spykee robot moved to github
</title>
62 <link>http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html
</link>
63 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html
</guid>
64 <pubDate>Sat,
19 Oct
2013 10:
20:
00 +
0200</pubDate>
65 <description><p
>Back in
2010, I created a Perl library to talk to
66 <a href=
"http://en.wikipedia.org/wiki/Spykee
">the Spykee robot
</a
>
67 (with two belts, wifi, USB and Linux) and made it available from my
68 web page. Today I concluded that it should move to a site that is
69 easier to use to cooperate with others, and moved it to github. If
70 you got a Spykee robot, you might want to check out
71 <a href=
"https://github.com/petterreinholdtsen/libspykee-perl
">the
72 libspykee-perl github repository
</a
>.
</p
>
77 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
78 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
79 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
80 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
81 <description><P
>In January,
82 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
83 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
84 channel #debian-lego
</a
>, for those of us in the Debian and Linux
85 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
86 marvellous construction system from Denmark. We also created
87 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
88 a place to take notes and write down our plans and hopes. And several
89 people showed up to help. I was very happy to see the effect of my
90 call. Since the small start, we have a debtags tag
91 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
92 tag for LEGO related packages, and now count
10 packages related to
93 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
95 <p
><table
>
96 <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
>
97 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
98 <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
>
99 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
100 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
101 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
102 <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
>
103 <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
>
104 <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
>
105 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
106 </table
></p
>
108 <p
>Some of these are available in Wheezy, and all but one are
109 currently available in Jessie/testing. leocad is so far only
110 available in experimental.
</p
>
112 <p
>If you care about LEGO in Debian, please join us on IRC and help
113 adding the rest of the great free software tools available on Linux
114 for LEGO designers.
</p
>
119 <title>Moved the pymissile Debian packaging to collab-maint
</title>
120 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
122 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
123 <description><p
>As part of my investigation on how to improve the support in Debian
124 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
125 Launcher and updated the Debian package
126 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
127 sure udev will fix the device permissions when it is plugged in. I
128 also added a
"Modaliases
" header to test it in the Debian archive and
129 hopefully make the package be proposed by jockey in Ubuntu when a user
130 plug in his rocket launcher. In the process I moved the source to a
131 git repository under collab-maint, to make it easier for any DD to
132 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
133 is not very active, but the software still work for me even after five
134 years of relative silence. The new git repository is not listed in
135 the uploaded package yet, because I want to test the other changes a
136 bit more before I upload the new version. If you want to check out
137 the new version with a .desktop file included, visit the
138 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
139 view
</a
> or use
"<tt
>git clone
140 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
145 <title>New IRC channel for LEGO designers using Debian
</title>
146 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
147 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
148 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
149 <description><p
>During Christmas, I have worked a bit on the Debian support for
150 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
151 NXT
</a
>. My son and I have played a bit with my NXT set, and I
152 discovered I had to build all the tools myself because none were
153 already in Debian Squeeze. If Debian support for LEGO is something
154 you care about, please join me on the IRC channel
155 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
156 irc.debian.org). There is a lot that could be done to improve the
157 Debian support for LEGO designers. For example both CAD software
158 and Mindstorm compilers are missing. :)
</p
>
160 <p
>Update
2012-
01-
03: A
161 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
162 including links to Lego related packages is now available.
</p
>
167 <title>First version of a Perl library to control the Spykee robot
</title>
168 <link>http://people.skolelinux.org/pere/blog/First_version_of_a_Perl_library_to_control_the_Spykee_robot.html
</link>
169 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_version_of_a_Perl_library_to_control_the_Spykee_robot.html
</guid>
170 <pubDate>Sat,
9 Oct
2010 14:
00:
00 +
0200</pubDate>
171 <description><p
>This summer I got the chance to buy cheap Spykee robots, and since
172 then I have worked on getting Linux software in place to control them.
173 The firmware for the robot is available from the producer, and using
174 that source it was trivial to figure out the protocol specification.
175 I
've started on a perl library to control it, and made some demo
176 programs using this perl library to allow one to control the
179 <p
>The library is quite functional already, and capable of controlling
180 the driving, fetching video, uploading MP3s and play them. There are
181 a few less important features too.
</p
>
183 <p
>Since a few weeks ago, I ran out of time to spend on this project,
184 but I never got around to releasing the current source. I decided
185 today that it was time to do something about it, and uploaded the
186 source to my Debian package store at people.skolelinux.org.
</p
>
188 <p
>Because it was simpler for me, I made a Debian package and
189 published the source and deb. If you got a spykee robot, grab the
190 source or binary package:
</p
>
193 <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
>
194 <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
>
195 <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
>
196 </ul
></p
>
198 <p
>If you are interested in helping out with developing this library,
199 please let me know.
</p
>
204 <title>My first perl GUI application - controlling a Spykee robot
</title>
205 <link>http://people.skolelinux.org/pere/blog/My_first_perl_GUI_application___controlling_a_Spykee_robot.html
</link>
206 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_first_perl_GUI_application___controlling_a_Spykee_robot.html
</guid>
207 <pubDate>Wed,
1 Sep
2010 21:
00:
00 +
0200</pubDate>
208 <description><p
>This evening I made my first Perl GUI application. The last few
209 days I have worked on a Perl module for controlling my recently
210 aquired Spykee robots, and the module is now getting complete enought
211 that it is possible to use it to control the robot driving at least.
212 It was now time to figure out how to use it to create some GUI to
213 allow me to drive the robot around. I picked PerlQt as I have had
214 positive experiences with the Qt API before, and spent a few minutes
215 browsing the web for examples. Using Qt Designer seemed like a short
216 cut, so I ended up writing the perl GUI using Qt Designer and
217 compiling it into a perl program using the puic program from
218 libqt-perl. Nothing fancy yet, but it got buttons to connect and
219 drive around.
</p
>
221 <p
>The perl module I have written provide a object oriented API for
222 controlling the robot. Here is an small example on how to use it:
</p
>
226 Spykee::discover(sub {$robot{$_[
0]} = $_[
1]});
227 my $host = (keys %robot)[
0];
228 my $spykee = Spykee-
>new();
229 $spykee-
>contact($host,
"admin
",
"admin
");
234 $spykee-
>forward();
239 </pre
></p
>
241 <p
>Thanks to the release of the source of the robot firmware, I could
242 peek into the implementation at the other end to figure out how to
243 implement the protocol used by the robot. I
've implemented several of
244 the commands the robot understand, but is still missing the camera
245 support to make it possible to control the robot from remote. First I
246 want to implement support for uploading new firmware and configuring
247 the wireless network, to make it possible to bootstrap a Spykee robot
248 without the producers Windows and MacOSX software (I only have Linux,
249 so I had to ask a friend to come over to get the robot testing
252 <p
>Will release the source to the public soon, but need to figure out
253 where to make it available first. I will add a link to
254 <a href=
"http://wiki.nuug.no/grupper/robot/
">the NUUG wiki
</a
> for
255 those that want to check back later to find it.
</p
>
260 <title>Robot, reis deg...
</title>
261 <link>http://people.skolelinux.org/pere/blog/Robot__reis_deg___.html
</link>
262 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Robot__reis_deg___.html
</guid>
263 <pubDate>Sat,
21 Aug
2010 22:
10:
00 +
0200</pubDate>
264 <description><p
>I dag fikk jeg endelig tittet litt på mine nyinnkjøpte roboter, og
265 har brukt noen timer til å google etter interessante referanser og
266 aktuell kildekode for bruk på Linux. Det mest lovende så langt er
267 <a href=
"http://ispykee.toyz.org/
">ispykee
</a
>, som har en
268 BSD-lisensiert linux-daemon som står som mellomledd mellom roboter på
269 lokalnettet og en sentral tjeneste der en iPhone kan koble seg opp for
270 å fjernstyre roboten. Linux-daemonen implementerer deler av
271 protokollen som roboten forstår. Etter å ha knotet litt med å oppnå
272 kontakt med roboten (den oppretter et eget ad-hoc wifi-nett, så jeg
273 måtte gå av mitt vanlige nett for å få kontakt), og kommet frem til at
274 den lytter på IP-port
9000 og
9001, gikk jeg i gang med å finne ut
275 hvordan jeg kunne snakke med roboten vha. disse portene. Robotbiten
276 av protokollen er publisert av produsenten med GPL-lisens, slik at det
277 er mulig å se hvordan protokollen fungerer. Det finnes en java-klient
278 for Android som så ganske snasen ut, men fant ingen kildekode for
279 denne. Derimot hadde iphone-løsningen kildekode, så jeg tok
280 utgangspunkt i den.
</p
>
282 <p
>Daemonen ville i utgangspunktet forsøke å kontakte den sentrale
283 tjenesten som iphone-programmet kobler seg til. Jeg skrev dette om
284 til i stedet å sette opp en nettverkstjeneste på min lokale maskin,
285 som jeg kan koble meg opp til med telnet og gi kommandoer til roboten
286 (act, forward, right, left, etc). Det involverte i praksis å bytte ut
287 socket()/connect() med socket()/bind()/listen()/accept() for å gjøre
288 klienten om til en tjener.
</p
>
290 <p
>Mens jeg har forsøkt å få roboten til å bevege seg har min samboer
291 skrudd sammen resten av roboten for å få montert kamera og plastpynten
292 (armer, plastfiber for lys). Nå er det hele montert, og roboten er
293 klar til bruk. Må få flyttet den over til mitt vanlige trådløsnett
294 før det blir praktisk, men de bitene av protokollen er ikke
295 implementert i ispykee-daemonen, så der må jeg enten få tak i en mac
296 eller en windows-maskin, eller implementere det selv.
</p
>
298 <p
>Vi var tre som kjøpte slike roboter, og vi har blitt enige om å
299 samle notater og referanser på
<a
300 href=
"http://wiki.nuug.no/grupper/robot/
">NUUGs wiki
</a
>. Ta en titt
301 der hvis du er nysgjerrig.
</p
>
306 <title>2 Spykee-roboter i hus, nå skal det lekes
</title>
307 <link>http://people.skolelinux.org/pere/blog/
2_Spykee_roboter_i_hus__n__skal_det_lekes.html
</link>
308 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
2_Spykee_roboter_i_hus__n__skal_det_lekes.html
</guid>
309 <pubDate>Wed,
18 Aug
2010 13:
30:
00 +
0200</pubDate>
310 <description><p
>Jeg kjøpte nettopp to
311 <a href=
"http://www.spykee-robot.com/
">Spykee
</a
>-roboter, for test og
312 leking. Kjøpte to da det var så billige, og gir meg mulighet til å
313 eksperimentere uten å være veldig redd for å ødelegge alt ved å bytte
314 ut firmware og slikt. Oppdaget at lekebutikken på Bryn senter hadde
315 en liten stabel på lager som de ikke hadde klart å selge ut etter
316 fjorårets juleinnkjøp, og var villig til å selge for en femtedel av
317 vanlig pris. Jeg, Ronny og Jarle har skaffet oss restbeholdningen, og
318 det blir morsomt å se hva vi får ut av dette.
</p
>
320 <p
>Roboten har belter styrt av to motorer, kamera, høytaler, mikrofon
321 og wifi-tilkobling. Det hele styrt av en GPL-lisensiert databoks som
322 jeg mistenker kjører linux. Firmware-kildekoden ble visst publisert i
323 mai. Eneste utfordringen er at kontroller-programvaren kun finnes til
324 Windows, men det må en kunne jobbe seg rundt når vi har kildekoden til
325 firmwaren. :)
</p
>
328 <li
><a href=
"http://en.wikipedia.org/wiki/Spykee
">Wikipedia-oppføring
</a
></li
>
329 <li
><a href=
"http://www.spykeeworld.com/spykee/US/freeSoftware.html
">Nedlasting av firmware-kilden
</a
></li
>
330 <li
><a href=
"http://wiki.nuug.no/grupper/robot
">prosjektwiki hos NUUG
</a
></li
>